Update verbiage from Azure to Entra in SSPR policy doc#1913
Open
SamErde wants to merge 1 commit intoMicrosoftDocs:mainfrom
Open
Update verbiage from Azure to Entra in SSPR policy doc#1913SamErde wants to merge 1 commit intoMicrosoftDocs:mainfrom
SamErde wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
Contributor
|
@SamErde : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
Bot
added
authentication/subsvc
Change sent to author
entra-id/svc
labels
Contributor
There was a problem hiding this comment.
Pull request overview
Updates SSPR policy documentation terminology to align administrator role references with Microsoft Entra branding, improving consistency within the identity docs set.
Changes:
- Replaced “Azure administrator(s)” references with “Entra administrator(s)” in SSPR policy explanations.
- Updated role list intro text from “Azure administrator roles” to “Entra administrator roles.”
You can also share your feedback on Copilot code review. Take the survey.
| In Microsoft Entra ID, there's a password policy that defines settings like the password complexity, length, or age. There's also a policy that defines acceptable characters and length for usernames. | ||
|
|
||
| When self-service password reset (SSPR) is used to change or reset a password in Microsoft Entra ID, the password policy is checked. If the password doesn't meet the policy requirements, the user is prompted to try again. Azure administrators have some restrictions on using SSPR that are different to regular user accounts, and there are minor exceptions for trial and free versions of Microsoft Entra ID. | ||
| When self-service password reset (SSPR) is used to change or reset a password in Microsoft Entra ID, the password policy is checked. If the password doesn't meet the policy requirements, the user is prompted to try again. Entra administrators have some restrictions on using SSPR that are different to regular user accounts, and there are minor exceptions for trial and free versions of Microsoft Entra ID. |
| In Microsoft Entra ID, there's a password policy that defines settings like the password complexity, length, or age. There's also a policy that defines acceptable characters and length for usernames. | ||
|
|
||
| When self-service password reset (SSPR) is used to change or reset a password in Microsoft Entra ID, the password policy is checked. If the password doesn't meet the policy requirements, the user is prompted to try again. Azure administrators have some restrictions on using SSPR that are different to regular user accounts, and there are minor exceptions for trial and free versions of Microsoft Entra ID. | ||
| When self-service password reset (SSPR) is used to change or reset a password in Microsoft Entra ID, the password policy is checked. If the password doesn't meet the policy requirements, the user is prompted to try again. Entra administrators have some restrictions on using SSPR that are different to regular user accounts, and there are minor exceptions for trial and free versions of Microsoft Entra ID. |
| ## Administrator reset policy differences | ||
|
|
||
| By default, administrator accounts are enabled for self-service password reset, and a strong default *two-gate* password reset policy is enforced. This policy may be different from the one you defined for your users, and this policy can't be changed. You should always test password reset functionality as a user without any Azure administrator roles assigned. | ||
| By default, administrator accounts are enabled for self-service password reset, and a strong default *two-gate* password reset policy is enforced. This policy may be different from the one you defined for your users, and this policy can't be changed. You should always test password reset functionality as a user without any Entra administrator roles assigned. |
| A two-gate policy applies in the following circumstances: | ||
|
|
||
| * All the following Azure administrator roles are affected: | ||
| * All the following Entra administrator roles are affected: |
Contributor
|
Learn Build status updates of commit 1977d20: ✅ Validation status: passed
For more details, please refer to the build report. |
Contributor
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request updates documentation to improve consistency in terminology regarding administrator roles and policies in Microsoft Entra ID. The most important changes clarify references to "Entra administrator" instead of "Azure administrator" throughout the self-service password reset (SSPR) policy documentation.
Terminology consistency:
concept-sspr-policy.md. [1] [2]