Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Guidance changes

Observed changes to selected Microsoft guidance. Review in My radar · Timelines and exceptions

469 of 469 selected pages have a baseline. 401 pages have an observed change; the newest was seen today.

Coverage and checks

469 of 469 selected pages have a baseline · 401 with observed changes · 469 current checks

Observed changes

RSS
‹ September 2022 ›
MonTueWedThuFriSatSun123456789101112131415161718192021222324252627282930

September 2022 in brief

No change observed this month under these filters.

Week of 16 Nov 2026

  1. 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).

    Changed wording view
    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.

    Observed today 11:14 UTC · current page · MIT

  2. 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 accesspolicy-require-identity-verification#configure-a-resource-access-policy
    • Added link: Protect onboarding and recoverypolicy-require-identity-verification#configure-an-onboarding-and-recovery-policy
    • Added link: onboarding and recovery control limitationspolicy-require-identity-verification#review-control-limitations

    12 new passages (about 280 words).

    New section: Require identity verification

    Also changed: Grant access

    Changed wording view
    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

    Observed today 11:14 UTC · current page · MIT

Week of 2 Nov 2026

  1. 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).

    Changed wording view
    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

  2. May need admin actionCheck whether a default changed for your tenant or devices; check the roles and permissions you grant.

    2 new passages (about 100 words), 1 edited passage (28 words changed).

    Changed in: Require remediation for high-risk users

    Changed wording view
    EditedRequire remediation for high-risk users
    This policy requires users identified as high risk by Microsoft Entra ID Protection to remediate their risk before continuing to access organizational resources. A new security group [added: named “Conditional Access: User Risk remediation”] is created alongside this policy to scope the affected users. [added: Microsoft populates this group with eligible active users registered for MFA, up to the tenant’s available Microsoft Entra ID P2 license count.] Instead of blocking access entirely, this policy uses adaptive risk remediation to guide users through the appropriate recovery flow based on their authentication method and the type of threat detected. For more information about the remediation experience, see User self-remediation …
    Before: This policy requires users identified as high risk by Microsoft Entra ID Protection to remediate their risk before continuing to access organizational resources. A new security group is created alongside this policy to scope the affected users. Instead of blocking access entirely, this policy uses adaptive risk remediation to guide users through the appropriate recovery flow based on their authentication method and the type of threat detected. For more information about the remediation experience, see User self-remediation …
    After: This policy requires users identified as high risk by Microsoft Entra ID Protection to remediate their risk before continuing to access organizational resources. A new security group named “Conditional Access: User Risk remediation” is created alongside this policy to scope the affected users. Microsoft populates this group with eligible active users registered for MFA, up to the tenant’s available Microsoft Entra ID P2 license count. Instead of blocking access entirely, this policy uses adaptive risk remediation to guide users through the appropriate recovery flow based on their authentication method and the type of threat detected. For more information about the remediation experience, see User self-remediation …
    NewRequire remediation for high-risk users
    [added: Organizations that don't already have an enabled customer-managed Conditional Access policy targeting user risk. Microsoft skips tenants that already have an enabled customer-managed Conditional Access policy targeting user risk. Existing user risk policies in Report-only or Off state don't prevent this Microsoft-managed policy from being created. This check is specific to user risk policies, not all Conditional Access policies.]
    Before: No saved wording on this side.
    After: Organizations that don't already have an enabled customer-managed Conditional Access policy targeting user risk. Microsoft skips tenants that already have an enabled customer-managed Conditional Access policy targeting user risk. Existing user risk policies in Report-only or Off state don't prevent this Microsoft-managed policy from being created. This check is specific to user risk policies, not all Conditional Access policies.

    1 more changed passage · see them all

    Microsoft's commit: Update user risk remediation policy details

    Observed 4 Nov 09:01 UTC · current page · MIT

Week of 12 Oct 2026

  1. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 13 Oct 00:55 UTC · current page

  2. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

    The page title or its body outside the tracked passages changed. Review the source for its effect.

    Observed 13 Oct 00:55 UTC · current page

  3. 11 pages · same-day observations 12 Oct 2026 · 11 changes 0 may need admin action · 11 read to decide · 0 no action expected
    1. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

      The page title or its body outside the tracked passages changed. Review the source for its effect.

      Observed 12 Oct 23:53 UTC · current page

    2. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

      The page title or its body outside the tracked passages changed. Review the source for its effect.

      Observed 12 Oct 19:50 UTC · current page

    3. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

      The page title or its body outside the tracked passages changed. Review the source for its effect.

      Observed 12 Oct 19:50 UTC · current page

    4. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

      The page title or its body outside the tracked passages changed. Review the source for its effect.

      Observed 12 Oct 19:50 UTC · current page

    5. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

      The page title or its body outside the tracked passages changed. Review the source for its effect.

      Observed 12 Oct 19:50 UTC · current page

    6. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

      The page title or its body outside the tracked passages changed. Review the source for its effect.

      Observed 12 Oct 19:50 UTC · current page

    7. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

      The page title or its body outside the tracked passages changed. Review the source for its effect.

      Observed 12 Oct 19:50 UTC · current page

    8. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

      The page title or its body outside the tracked passages changed. Review the source for its effect.

      Observed 12 Oct 19:35 UTC · current page

    9. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

      The page title or its body outside the tracked passages changed. Review the source for its effect.

      Observed 12 Oct 19:19 UTC · current page

    10. Entra Conditional Access

      Read to decideThe wording changed without matching a rule; read the changed passages to decide.

      The page title or its body outside the tracked passages changed. Review the source for its effect.

      Observed 12 Oct 19:19 UTC · current page

    11. Read to decideThe wording changed without matching a rule; read the changed passages to decide.

      The page title or its body outside the tracked passages changed. Review the source for its effect.

      Observed 12 Oct 19:19 UTC · current page

Quoted wording: © Microsoft Corporation · source and applicable license beside each change.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 17 Nov 14:26 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current