Guidance changes
Observed changes to selected Microsoft guidance. Review in My radar · Timelines and exceptions
469 of 469 selected pages have a baseline. 403 pages have an observed change; the newest was seen today.
Coverage and checks
469 of 469 selected pages have a baseline · 403 with observed changes · 469 current checks
Observed changes
RSSOctober 2017 in brief
No change observed this month under these filters.
Week of 16 Nov 2026
2 pages · shared source commit 17 Nov 2026 – 18 Nov 2026 · 2 changes 2 may need admin action · 0 read to decide · 0 no action expected
microsoftdocs/entra-docs · commit
d55e8547df234acc92ef02b03f863c8c04b47ddf-
May need admin actionCheck whether new requirements apply to your setup; check whether a default changed for your tenant or devices.
Changed article references · 5 added · 0 removed
- Added link: create an eligible identity verification profile
../authentication/concept-authentication-verified-id#create-and-manage-identity-verification-profiles - Added link: Require identity verification with Conditional Access
policy-require-identity-verification#configure-an-onboarding-and-recovery-policy - Added link: Enable the global onboarding and recovery exclusion
policy-require-identity-verification#enable-the-global-onboarding-and-recovery-exclusion-preview - Added link: enable the global onboarding and recovery exclusion
policy-require-identity-verification#enable-the-global-onboarding-and-recovery-exclusion-preview - Added link: control limitations
policy-require-identity-verification#review-control-limitations
8 new passages (about 280 words), 1 edited passage (2 words changed).
New sections: Exclude onboarding and recovery from All resources policies (preview) · Account onboarding and recovery (preview)
Also changed: User actions
NewExclude onboarding and recovery from All resources policies (preview) [added: Policies targeting All resources also apply to onboarding and account recovery events unless you enable the global user-action exclusion. These policies can require credentials or other controls that users can't satisfy before they establish or restore their authentication methods.]
Before: No saved wording on this side.
After: Policies targeting All resources also apply to onboarding and account recovery events unless you enable the global user-action exclusion. These policies can require credentials or other controls that users can't satisfy before they establish or restore their authentication methods.
NewExclude onboarding and recovery from All resources policies (preview) [added: Under Entra ID > Conditional Access > Settings (Preview), Global exclusions exposes the Account onboarding and recovery (Preview) setting. When enabled, it excludes the Account onboarding and recovery user action from policies targeting All resources. Policies that directly target the user action still apply.]
Before: No saved wording on this side.
After: Under Entra ID > Conditional Access > Settings (Preview), Global exclusions exposes the Account onboarding and recovery (Preview) setting. When enabled, it excludes the Account onboarding and recovery user action from policies targeting All resources. Policies that directly target the user action still apply.
5 more changed passages · see them all
Microsoft's commit: Publish Ignite 2026 High Assurance documentation release (#15002)
Observed today 05:01 UTC · current page · MIT
- Added link: create an eligible identity verification profile
-
May need admin actionCheck whether new requirements apply to your setup; check the roles and permissions you grant.
Changed article references · 7 added · 0 removed
- Added link: Require identity verification
#require-identity-verification - Added link: Identity verification licensing
../../fundamentals/licensing#identity-verification - Added link: Configure risk policies
../../id-protection/howto-identity-protection-configure-risk-policies - Added link: identity verification profile
../authentication/concept-authentication-verified-id#create-and-manage-identity-verification-profiles - Added link: Require identity verification for resource access
policy-require-identity-verification#configure-a-resource-access-policy - Added link: Protect onboarding and recovery
policy-require-identity-verification#configure-an-onboarding-and-recovery-policy - Added link: onboarding and recovery control limitations
policy-require-identity-verification#review-control-limitations
12 new passages (about 280 words).
New section: Require identity verification
Also changed: Grant access
NewGrant access [added: Require identity verification]
Before: No saved wording on this side.
After: Require identity verification
NewRequire identity verification [added: The identity verification grant control requires users to verify their identity for protected access. Configure an eligible verification profile and apply the requirement to the supported resource or action scope in your tenant.]
Before: No saved wording on this side.
After: The identity verification grant control requires users to verify their identity for protected access. Configure an eligible verification profile and apply the requirement to the supported resource or action scope in your tenant.
10 more changed passages · see them all
Microsoft's commit: Publish Ignite 2026 High Assurance documentation release (#15002)
Observed 17 Nov 11:14 UTC · current page · MIT
- Added link: Require identity verification
-
-
May need admin actionCheck whether new requirements apply to your setup.
Changed article references · 1 added · 0 removed
- Added link: Conditional Access and sign-in frequency
../../identity-platform/concept-native-authentication#conditional-access-and-sign-in-frequency
1 new passage (about 60 words).
NewOverview [added: Sign-in frequency applies to both Microsoft-hosted and native authentication. For native authentication, the policy prevents token issuance during refresh token grants when reauthentication is required. Your app must handle the failed token refresh and prompt the user to sign in again. Persistent browser session controls apply to browser-based sessions. For more information, see Conditional Access and sign-in frequency.]
Before: No saved wording on this side.
After: Sign-in frequency applies to both Microsoft-hosted and native authentication. For native authentication, the policy prevents token issuance during refresh token grants when reauthentication is required. Your app must handle the failed token refresh and prompt the user to sign in again. Persistent browser session controls apply to browser-based sessions. For more information, see Conditional Access and sign-in frequency.
Microsoft's commit: Publish Ignite 2026 External ID documentation release (#15007)
Observed 17 Nov 11:14 UTC · current page · MIT
- Added link: Conditional Access and sign-in frequency
Week of 2 Nov 2026
-
May need admin actionCheck whether new requirements apply to your setup; check the roles and permissions you grant.
1 new passage (about 60 words), 1 removed passage (about 60 words).
NewRequire device to be marked as compliant [added: Microsoft Authenticator requires UserAuthenticationMethod.ReadWrite access to register credentials. When this permission is used in a delegated context by Microsoft Authenticator, access required for credential registration isn't blocked by the Require device to be marked as compliant grant control. This exception doesn't apply to application permissions. Requests using the UserAuthenticationMethod.ReadWrite application permission remain subject to the Require device to be marked as compliant check.]
Before: No saved wording on this side.
After: Microsoft Authenticator requires UserAuthenticationMethod.ReadWrite access to register credentials. When this permission is used in a delegated context by Microsoft Authenticator, access required for credential registration isn't blocked by the Require device to be marked as compliant grant control. This exception doesn't apply to application permissions. Requests using the UserAuthenticationMethod.ReadWrite application permission remain subject to the Require device to be marked as compliant check.
RemovedRequire device to be marked as compliant [removed: Similarly, the Require device to be marked as compliant doesn't block Microsoft Authenticator app access to the UserAuthenticationMethod.Read scope. Authenticator needs access to the UserAuthenticationMethod.Read scope during Authenticator registration to determine which credentials a user can configure. Authenticator needs access to UserAuthenticationMethod.ReadWrite to register credentials, which doesn't bypass the Require device to be marked as compliant check.]Before: Similarly, the Require device to be marked as compliant doesn't block Microsoft Authenticator app access to the UserAuthenticationMethod.Read scope. Authenticator needs access to the UserAuthenticationMethod.Read scope during Authenticator registration to determine which credentials a user can configure. Authenticator needs access to UserAuthenticationMethod.ReadWrite to register credentials, which doesn't bypass the Require device to be marked as compliant check.
After: No saved wording on this side.
Microsoft's commit: Update Microsoft Authenticator access requirements
Observed 5 Nov 15:42 UTC · current page · MIT
Quoted wording: © Microsoft Corporation · source and applicable license beside each change.