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
RSSWeek of 26 Oct 2026
2 pages · shared source commit 29 Oct 2026 · 2 changes 2 may need admin action · 0 read to decide · 0 no action expected
sharepoint/sp-dev-docs · commit
f59497d632dbae53eb2d03bdbb89fa0527ec93da- SharePoint SharePoint Azure ACS retirement
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 · 4 added · 1 removed
- Removed link: support article
https://aka.ms/retirement/addins/support - 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: SharePoint Add-In retirement announcement
retirement-announcement-for-add-ins - Added link: retirement announcement
retirement-announcement-for-add-ins
6 new passages (about 230 words), 4 edited passages (107 words changed), 5 removed passages (about 200 words).
Changed in: Azure ACS retirement in Microsoft 365 · Azure ACS usage in SharePoint Online · Azure ACS usage by Project Online · Turn off the use of Azure ACS on your tenant and 1 more
NewAzure ACS 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.
NewAzure ACS retirement in Microsoft 365 [added: Azure ACS (Access Control Services) authentication for SharePoint Online was retired on April 2, 2026. Use modern authentication through Microsoft Entra ID instead.]
Before: No saved wording on this side.
After: Azure ACS (Access Control Services) authentication for SharePoint Online was retired on April 2, 2026. Use modern authentication through Microsoft Entra ID instead.
13 more changed passages · see them all
Microsoft's commit: SPFx 1.24 GA docs updates - with Copilot Components GA (#11075)
Observed 29 Oct 01:42 UTC · current page · CC BY 4.0
- Removed link: support article
- SharePoint Overview of the SharePoint Framework
May need admin actionCheck whether new requirements apply to your setup; check whether a default changed for your tenant or devices; check the roles and permissions you grant.
Changed article references · 9 added · 5 removed
- Removed link: Microsoft 365 Copilot
copilot/overview-copilot-apps - Removed link: Overview of SharePoint Copilot Apps
copilot/overview-copilot-apps - Removed link: full add-in model retirement announcement
https://aka.ms/retirement/addins/support - Removed link: multiple applications
office/overview - Removed link: SharePoint Framework Yeoman Generator
set-up-your-development-environment - Added link: Develop and deploy Copilot UX components
copilot/development-and-deployment - Added link: Copilot UX components
copilot/overview-copilot-apps - Added link: Overview of Copilot UX components
copilot/overview-copilot-apps - Added link: licensing and supported-client requirements
copilot/overview-copilot-apps#availability - Added link: Copilot UX component samples
https://aka.ms/spfx/copilot/samples - Added link: SPFx web part samples
https://pnp.github.io/sp-dev-fx-webparts/ - Added link: supported applications
office/overview - Added link: Publish SharePoint Framework applications to the marketplace
publish-to-marketplace-overview - Added link: SharePoint Framework development environment and generator
set-up-your-development-environment
8 new passages (about 230 words), 3 edited passages (36 words changed), 7 removed passages (about 240 words).
Changed in: Overview of the SharePoint Framework · Key features of the SharePoint Framework · See also
NewOverview of the SharePoint Framework [added: Start with the SharePoint Framework development environment and generator. Tooling extensions, such as the SharePoint Framework Toolkit, can assist with supported scenarios; check their SPFx and component-type requirements. Share UI and business logic across hosts while using the appropriate component type, host adapter, manifest, and deployment configuration.]
Before: No saved wording on this side.
After: Start with the SharePoint Framework development environment and generator. Tooling extensions, such as the SharePoint Framework Toolkit, can assist with supported scenarios; check their SPFx and component-type requirements. Share UI and business logic across hosts while using the appropriate component type, host adapter, manifest, and deployment configuration.
NewOverview of the SharePoint Framework [added: Integrated authentication – Use the framework-provided clients for supported signed-in-user API access. Authentication doesn't grant access to data: tenant consent, user permissions, API requirements, and host behavior still apply.]
Before: No saved wording on this side.
After: Integrated authentication – Use the framework-provided clients for supported signed-in-user API access. Authentication doesn't grant access to data: tenant consent, user permissions, API requirements, and host behavior still apply.
16 more changed passages · see them all
Microsoft's commit: SPFx 1.24 GA docs updates - with Copilot Components GA (#11075)
Observed 29 Oct 00:56 UTC · current page · CC BY 4.0
- Removed link: Microsoft 365 Copilot
Quoted wording: © Microsoft Corporation · source and applicable license beside each change.