This repository was archived by the owner on Oct 10, 2026. It is now read-only.
Repository navigation
Clarify AdminService username compatibility - #18
Merged
Merged
Conversation
Retain the 401 fallback behavior while removing an unsupported claim that ConfigMgr 2603 universally requires UPN-form usernames. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
401 UnauthorizedEvidence
Microsoft's published ConfigMgr 2603 and AdminService guidance does not establish a universal UPN-only username requirement. Authentication format, account policy, endpoint configuration, and environment-specific behavior must be validated together.
Validation
git diff --checkpassed