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 2026 ›
MonTueWedThuFriSatSun123456178910111221314151617183193202211222312422526274282292308312

Wednesday 28 October 2026 · day in brief

2 changes to 2 pages

2 may need admin action

Entra 1 · SharePoint 1

← 27 Oct29 Oct →All days

Week of 26 Oct 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 · 1 added · 0 removed
    • Added link: exclude the Microsoft Authenticator Credential Registration resource#workarounds-for-an-authentication-strength-conditional-access-policy-loop

    2 new passages (about 170 words), 1 edited passage (1 word changed), 1 removed passage (about 80 words).

    Changed in: Workarounds for an authentication strength Conditional Access policy loop · Users who can't register passkeys because of Require approved client app or Require app protection policy Conditional Access grant controls

    Changed wording view
    NewWorkarounds for an authentication strength Conditional Access policy loop
    [added: You can exclude the Microsoft Authenticator Credential Registration resource from the Conditional Access policy. Note The Microsoft Authenticator Credential Registration resource will be available in November 2026. Before you can exclude the resource from a Conditional Access policy, you must provision the Microsoft Authenticator Credential Registration enterprise application in your tenant. As a Cloud Application Administrator or Application Administrator: Manually provision the Microsoft Authenticator Credential Registration app by using one of the supported methods for creating an enterprise application from a multitenant app. Use the following details: App ID: 6aa00308-ea33-4caa-90d6-ae905d8cb51b Required role: Cloud Application Administrator or Application Administrator For example, use Microsoft Graph Explorer to make a POST request to https://graph.microsoft.com/v1.0/servicePrincipals with the following body: { "appId": "6aa00308-ea33-4caa-90d6-ae905d8cb51b" } After you provision the app, Microsoft Authenticator Credential Registration appears as a resource in Conditional Access. Exclude it from any Conditional Access policies scoped to All resources to unblock passkey registration in Microsoft Authenticator.]
    Before: No saved wording on this side.
    After: You can exclude the Microsoft Authenticator Credential Registration resource from the Conditional Access policy. Note The Microsoft Authenticator Credential Registration resource will be available in November 2026. Before you can exclude the resource from a Conditional Access policy, you must provision the Microsoft Authenticator Credential Registration enterprise application in your tenant. As a Cloud Application Administrator or Application Administrator: Manually provision the Microsoft Authenticator Credential Registration app by using one of the supported methods for creating an enterprise application from a multitenant app. Use the following details: App ID: 6aa00308-ea33-4caa-90d6-ae905d8cb51b Required role: Cloud Application Administrator or Application Administrator For example, use Microsoft Graph Explorer to make a POST request to https://graph.microsoft.com/v1.0/servicePrincipals with the following body: { "appId": "6aa00308-ea33-4caa-90d6-ae905d8cb51b" } After you provision the app, Microsoft Authenticator Credential Registration appears as a resource in Conditional Access. Exclude it from any Conditional Access policies scoped to All resources to unblock passkey registration in Microsoft Authenticator.
    EditedWorkarounds for an authentication strength Conditional Access policy loop
    Note With [removed: either] [added: any] workaround, users must also satisfy any Conditional Access policy that targets Register security info or they can't register the passkey. If you have other conditions set up with the All resources policies, those conditions must be met when the passkey …
    Before: Note With either workaround, users must also satisfy any Conditional Access policy that targets Register security info or they can't register the passkey. If you have other conditions set up with the All resources policies, those conditions must be met when the passkey …
    After: Note With any workaround, users must also satisfy any Conditional Access policy that targets Register security info or they can't register the passkey. If you have other conditions set up with the All resources policies, those conditions must be met when the passkey …

    2 more changed passages · see them all

    Microsoft's commit: Merge pull request #14558 from tilarso/docs/migrate-passkey-pr-2124

    Observed 28 Oct 23:20 UTC · current page · MIT

  2. May need admin actionCheck whether new requirements apply to your setup; check the dates against your plans.

    Changed article references · 3 added · 1 removed
    • Removed link: SharePoint Framework (SPFx)https://aka.ms/spfx
    • Added link: Add-in migration guidance../sp-add-ins-modernize/sp-add-in-modernize
    • Added link: SharePoint Framework (SPFx)../spfx/sharepoint-framework-overview
    • Added link: retirement announcementretirement-announcement-for-add-ins

    6 new passages (about 320 words), 3 edited passages (60 words changed), 7 removed passages (about 310 words).

    Changed in: SharePoint Add-In retirement in Microsoft 365 · SharePoint Add-Ins · SharePoint Server support for SharePoint Add-Ins · Project Online support for SharePoint Add-Ins and 2 more

    Changed wording view
    NewSharePoint Add-In retirement in Microsoft 365
    [added: Important SharePoint Add-ins reached end of life in SharePoint Online on April 2, 2026. Both SharePoint-hosted and provider-hosted Add-ins are retired and no longer work in SharePoint Online, including government clouds. Add-in development, deployment, and usage guidance is retained for historical reference and for applicable SharePoint Server scenarios, not for new SharePoint Online solutions. SharePoint Server Add-ins deployed through an on-premises app catalog are not retired by this change. Acquiring SharePoint Add-ins from the public marketplace ended on April 2, 2026 for SharePoint Server. This retirement does not retire SharePoint REST APIs, CSOM, JSOM, or SharePoint Framework (SPFx). For SharePoint Online, use SPFx for user interface extensions and Microsoft Entra ID for authentication to external applications. See the retirement announcement and Add-in migration guidance.]
    Before: No saved wording on this side.
    After: Important SharePoint Add-ins reached end of life in SharePoint Online on April 2, 2026. Both SharePoint-hosted and provider-hosted Add-ins are retired and no longer work in SharePoint Online, including government clouds. Add-in development, deployment, and usage guidance is retained for historical reference and for applicable SharePoint Server scenarios, not for new SharePoint Online solutions. SharePoint Server Add-ins deployed through an on-premises app catalog are not retired by this change. Acquiring SharePoint Add-ins from the public marketplace ended on April 2, 2026 for SharePoint Server. This retirement does not retire SharePoint REST APIs, CSOM, JSOM, or SharePoint Framework (SPFx). For SharePoint Online, use SPFx for user interface extensions and Microsoft Entra ID for authentication to external applications. See the retirement announcement and Add-in migration guidance.
    EditedSharePoint Add-In retirement in Microsoft 365
    SharePoint Add-Ins [removed: will stop] [added: stopped] working for new [added: SharePoint Online] tenants [removed: as of] [added: on] November [removed: 1st, 2024; they will stop working] [added: 1, 2024 and] for all [added: SharePoint Online] tenants [removed: as of] [added: on] April [removed: 2nd,] [added: 2,] 2026. This applies to all environments[added: ,] including [removed: Government Clouds] [added: government clouds] and the U.S. Department of Defense.
    Before: SharePoint Add-Ins will stop working for new tenants as of November 1st, 2024; they will stop working for all tenants as of April 2nd, 2026. This applies to all environments including Government Clouds and the U.S. Department of Defense.
    After: SharePoint Add-Ins stopped working for new SharePoint Online tenants on November 1, 2024 and for all SharePoint Online tenants on April 2, 2026. This applies to all environments, including government clouds and the U.S. Department of Defense.

    14 more changed passages · see them all

    Microsoft's commit: SPFx 1.24 GA docs updates - with Copilot Components GA (#11075)

    Observed 28 Oct 11:12 UTC · current page · CC BY 4.0

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 16 Nov 08:58 UTC · 274 of 275 readable · 252 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current