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
‹ October 2014 ›
MonTueWedThuFriSatSun12345678910111213141516171819202122232425262728293031

October 2014 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; check the roles and permissions you grant; check the dates against your plans.

    Changed article references · 11 added · 1 removed
    • Removed link: Authentication methods in Microsoft Entra IDoverview-authentication
    • Added image: Illustrative screenshot of John Doe's authentication methods showing a usable passkey with High assurance and an expired Temporary Access Pass with no assurance level.media/concept-authentication-methods-manage/credential-assurance.png
    • Added image: Screenshot of John Doe's user overview with the example account [email protected], an identity verification status summary, and an Identity verification card with View details.media/concept-authentication-methods-manage/user-overview-identity-verification.png
    • Added link: Identity verification licensing../../fundamentals/licensing#identity-verification
    • Added link: Verified ID audit activities../monitoring-health/reference-audit-activities#verified-id
    • Added link: Security Reader../role-based-access-control/permissions-reference#security-reader
    • Added link: Credential assurance classificationconcept-authentication-passkeys-fido2#credential-assurance-classification-preview
    • Added link: Passkey credential provenanceconcept-authentication-passkeys-fido2#credential-provenance
    • Added link: Identity verification collection prerequisitesconcept-authentication-verified-id#prerequisites
    • Added link: Migrate to the Authentication methods policyhow-to-authentication-methods-manage
    • Added link: media/concept-authentication-methods-manage/credential-assurance.png#lightbox
    • Added link: media/concept-authentication-methods-manage/user-overview-identity-verification.png#lightbox

    28 new passages (about 710 words), 1 removed passage (about 70 words).

    New sections: Authentication methods policy overview · Credential provenance (preview) · Identity verification status and history · Manage identity verification for a user and 1 more

    Also changed: Usable and non-usable methods for users · Manage authentication methods for Microsoft Entra ID

    Changed wording view
    NewAuthentication methods policy overview
    [added: The Authentication methods policy in Microsoft Entra ID is a policy that lets administrators configure authentication methods for users and groups. You can configure methods to meet your organization's goals for user experience and security.]
    Before: No saved wording on this side.
    After: The Authentication methods policy in Microsoft Entra ID is a policy that lets administrators configure authentication methods for users and groups. You can configure methods to meet your organization's goals for user experience and security.
    NewAuthentication methods policy overview
    [added: This article covers the core policy and related user authentication information first, including method usability, credential provenance, and identity verification history. The second section covers migration from legacy multifactor authentication (MFA) and self-service password reset (SSPR) policies.]
    Before: No saved wording on this side.
    After: This article covers the core policy and related user authentication information first, including method usability, credential provenance, and identity verification history. The second section covers migration from legacy multifactor authentication (MFA) and self-service password reset (SSPR) policies.

    18 more changed passages · see them all

    Observed today 08:42 UTC · current page · MIT

Week of 26 Oct 2026

  1. Read to decideNew content in “Change a password in My Sign-Ins”; read it to see whether it concerns you.

    Changed article references · 1 added · 0 removed
    • Added link: Allow password change after secure sign-in.https://review.learn.microsoft.com/en-us/entra/identity/authentication/concept-sspr-howitworks?branch=pr-en-us-14357&tabs=secure-sign-in#tab/secure-sign-in

    2 new passages (about 80 words), 2 edited passages (45 words changed).

    New section: Change a password in My Sign-Ins

    Also changed: Change a password in MySignIns

    Changed wording view
    EditedChange a password in My Sign-Ins
    A user navigates to Security info. After signing in, the user can change their password. If the user authenticates with a password and a multifactor authentication method, [removed: they're able to use the enhanced user experience to] [added: they can] change their password without entering [removed: their existing password. When finished, the user has the new password updated on the Security info page. Authentication methods such as Temporary Access Pass (TAP) aren't supported for password change unless the user knows] their existing password.
    Before: A user navigates to Security info. After signing in, the user can change their password. If the user authenticates with a password and a multifactor authentication method, they're able to use the enhanced user experience to change their password without entering their existing password. When finished, the user has the new password updated on the Security info page. Authentication methods such as Temporary Access Pass (TAP) aren't supported for password change unless the user knows their existing password.
    After: A user navigates to Security info. After signing in, the user can change their password. If the user authenticates with a password and a multifactor authentication method, they can change their password without entering their existing password.
    NewChange a password in My Sign-Ins
    [added: An organization can also allow users to change their cloud password after they sign in with Microsoft Entra certificate-based authentication (CBA), a passkey (FIDO2), or a Microsoft Authenticator passwordless phone sign-in notification. Users don't need to know or enter their current password, and they don't need to be registered for SSPR. For administrator configuration, user steps, and limitations, see Allow password change after secure sign-in.]
    Before: No saved wording on this side.
    After: An organization can also allow users to change their cloud password after they sign in with Microsoft Entra certificate-based authentication (CBA), a passkey (FIDO2), or a Microsoft Authenticator passwordless phone sign-in notification. Users don't need to know or enter their current password, and they don't need to be registered for SSPR. For administrator configuration, user steps, and limitations, see Allow password change after secure sign-in.

    1 more changed passage · see them all

    Observed 30 Oct 01:49 UTC · current page · MIT

Week of 12 Oct 2026

  1. May need admin actionCheck whether new requirements apply to your setup; check the roles and permissions you grant.

    14 new passages (about 460 words), 4 edited passages (107 words changed), 7 removed passages (about 220 words).

    New sections: How passkey registration nudges are evaluated · Step 1: Determine how the passkey profile affects the nudge · Step 2: Evaluate the platform, when required

    Also changed: Examples · Can users be nudged within an SSO session? · Passkey nudge evaluation by platform · How the passkey profile affects the nudge evaluation

    Changed wording view
    NewHow passkey registration nudges are evaluated
    [added: After a user meets the registration campaign’s eligibility requirements, their passkey profile determines whether existing registered passkeys suppress the nudge across all platforms or only for the current operating system and browser combination (platform). Start with the profile table. Use the platform table only when platform-specific evaluation applies.]
    Before: No saved wording on this side.
    After: After a user meets the registration campaign’s eligibility requirements, their passkey profile determines whether existing registered passkeys suppress the nudge across all platforms or only for the current operating system and browser combination (platform). Start with the profile table. Use the platform table only when platform-specific evaluation applies.
    NewHow passkey registration nudges are evaluated
    [added: These rules apply to passkey campaigns in both the Enabled and Microsoft managed states. They are separate from passkey profile eligibility for the Microsoft managed registration campaign. In the Microsoft managed state, only users assigned to at least one eligible passkey profile are nudged. In contrast, when the registration campaign is set to Enabled, any user who is enabled for passkeys can be nudged, regardless of their passkey profile.]
    Before: No saved wording on this side.
    After: These rules apply to passkey campaigns in both the Enabled and Microsoft managed states. They are separate from passkey profile eligibility for the Microsoft managed registration campaign. In the Microsoft managed state, only users assigned to at least one eligible passkey profile are nudged. In contrast, when the registration campaign is set to Enabled, any user who is enabled for passkeys can be nudged, regardless of their passkey profile.

    18 more changed passages · see them all

    Microsoft's commit: Merge pull request #14574 from JasSuri/docs/clarify-registration-campaign-sso-nudge

    Observed 12 Oct 19:50 UTC · current page · MIT

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 12:19 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current