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

SharePoint Azure ACS retirement

Full guidance and history · All guidance changes

SharePoint · Official Microsoft guidance

Observed content change

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 articlehttps://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 announcementretirement-announcement-for-add-ins
  • Added link: retirement announcementretirement-announcement-for-add-ins
Changed wording view
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.
EditedAzure ACS retirement in Microsoft 365
Azure ACS [removed: will stop] [added: stopped] working for new [added: SharePoint Online] tenants [removed: as of] [added: on] November [removed: 1st,] [added: 1,] 2024 and [removed: it will stop working] for existing tenants [removed: and will be fully retired as of] [added: on] April [removed: 2nd,] [added: 2,] 2026. This applies to all environments[added: ,] including [removed: Government Clouds] [added: government clouds] and [added: the U.S.] Department of Defense.
Before: Azure ACS will stop working for new tenants as of November 1st, 2024 and it will stop working for existing tenants and will be fully retired as of April 2nd, 2026. This applies to all environments including Government Clouds and Department of Defense.
After: Azure ACS stopped working for new SharePoint Online tenants on November 1, 2024 and for existing tenants on April 2, 2026. This applies to all environments, including government clouds and the U.S. Department of Defense.
EditedAzure ACS retirement in Microsoft 365
If [removed: you are using] [added: your] custom [removed: developed] applications [removed: or are using SharePoint provider hosted Add-Ins, we recommend switching those applications] [added: depended on Azure ACS, migrate their authorization and authentication] to [removed: use] Microsoft Entra [removed: ID for authorization and] [added: ID. SharePoint provider hosted Add-Ins also require migration away from the retired Add-in model; changing] authentication [removed: needs. Aligned with] [added: alone does not restore them. See] the [removed: Azure ACS retirement also] SharePoint [removed: Add-Ins are retired, check out this support article for more information.] [added: Add-In retirement announcement.] There [removed: will not be an] [added: is no] option to extend [removed: using] Azure ACS [added: use] with SharePoint Online beyond April [removed: 2nd,] [added: 2,] 2026.
Before: If you are using custom developed applications or are using SharePoint provider hosted Add-Ins, we recommend switching those applications to use Microsoft Entra ID for authorization and authentication needs. Aligned with the Azure ACS retirement also SharePoint Add-Ins are retired, check out this support article for more information. There will not be an option to extend using Azure ACS with SharePoint Online beyond April 2nd, 2026.
After: If your custom applications depended on Azure ACS, migrate their authorization and authentication to Microsoft Entra ID. SharePoint provider hosted Add-Ins also require migration away from the retired Add-in model; changing authentication alone does not restore them. See the SharePoint Add-In retirement announcement. There is no option to extend Azure ACS use with SharePoint Online beyond April 2, 2026.
EditedAzure ACS usage in SharePoint Online
Azure ACS [removed: is] [added: was] used in SharePoint Online [removed: for providing auth for] [added: to authenticate] provider hosted SharePoint Add-Ins [removed: plus it’s used] [added: and] to grant applications access to SharePoint Online, [removed: optionally using] [added: including] application permissions [removed: and] [added: with] granular scopes.
Before: Azure ACS is used in SharePoint Online for providing auth for provider hosted SharePoint Add-Ins plus it’s used to grant applications access to SharePoint Online, optionally using application permissions and granular scopes.
After: Azure ACS was used in SharePoint Online to authenticate provider hosted SharePoint Add-Ins and to grant applications access to SharePoint Online, including application permissions with granular scopes.
NewAzure ACS usage in SharePoint Online
[added: For the provider hosted Add-In use case, see the Add-In retirement announcement. Applications that accessed SharePoint Online through Azure ACS must transition to Microsoft Entra ID.]
Before: No saved wording on this side.
After: For the provider hosted Add-In use case, see the Add-In retirement announcement. Applications that accessed SharePoint Online through Azure ACS must transition to Microsoft Entra ID.
EditedAzure ACS usage by Project Online
Project Online [removed: is an extension on top of SharePoint Online and Project Online] custom developments could also have used Azure ACS. [removed: The retirement of] Azure ACS [removed: applies to Project Online as well, any Azure ACS] usage in Project Online [removed: will follow] [added: followed] the same retirement [removed: path] [added: timeline] as [removed: Azure ACS usage in] SharePoint [removed: Online.] [added: Online and retired on April 2, 2026.]
Before: Project Online is an extension on top of SharePoint Online and Project Online custom developments could also have used Azure ACS. The retirement of Azure ACS applies to Project Online as well, any Azure ACS usage in Project Online will follow the same retirement path as Azure ACS usage in SharePoint Online.
After: Project Online custom developments could also have used Azure ACS. Azure ACS usage in Project Online followed the same retirement timeline as SharePoint Online and retired on April 2, 2026.
NewTurn off the use of Azure ACS on your tenant
[added: Before retirement, tenant admins could turn off Azure ACS app-only access after migrating dependent applications. The following command is retained for historical context:]
Before: No saved wording on this side.
After: Before retirement, tenant admins could turn off Azure ACS app-only access after migrating dependent applications. The following command is retained for historical context:
NewTurn off the use of Azure ACS on your tenant
[added: This setting did not control Azure ACS usage by SharePoint provider hosted Add-Ins. Changing it cannot re-enable Azure ACS authentication in SharePoint Online after retirement.]
Before: No saved wording on this side.
After: This setting did not control Azure ACS usage by SharePoint provider hosted Add-Ins. Changing it cannot re-enable Azure ACS authentication in SharePoint Online after retirement.
NewMore information
[added: The retirement was also communicated through the Microsoft 365 admin center Message Center.]
Before: No saved wording on this side.
After: The retirement was also communicated through the Microsoft 365 admin center Message Center.
RemovedAzure ACS retirement in Microsoft 365
[removed: Microsoft strives to deliver utmost value to our customers through modern, optimized, secure solutions in this newly evolved world focused on digital transformation. As part of this evolution of Microsoft 365 solutions we will be retiring the use of Azure ACS (Access Control Services) for SharePoint Online auth needs and believe Microsoft 365 customers will be better served by modern auth offered via Microsoft Entra ID.]
Before: Microsoft strives to deliver utmost value to our customers through modern, optimized, secure solutions in this newly evolved world focused on digital transformation. As part of this evolution of Microsoft 365 solutions we will be retiring the use of Azure ACS (Access Control Services) for SharePoint Online auth needs and believe Microsoft 365 customers will be better served by modern auth offered via Microsoft Entra ID.
After: No saved wording on this side.
RemovedAzure ACS usage in SharePoint Online
[removed: To learn more about the provider hosted Add-In use case please check out the respective retirement articles, granting applications access to SharePoint Online will need to be transitioned to Microsoft Entra ID.]
Before: To learn more about the provider hosted Add-In use case please check out the respective retirement articles, granting applications access to SharePoint Online will need to be transitioned to Microsoft Entra ID.
After: No saved wording on this side.
RemovedTurn off the use of Azure ACS on your tenant
[removed: We recommend tenant admins to turn off the usage of Azure ACS app-only access once they’ve ensured there is no business relevant Azure ACS usage anymore. The assessment tool should give administrators the usage information to understand where and when Azure ACS principals are being used.]
Before: We recommend tenant admins to turn off the usage of Azure ACS app-only access once they’ve ensured there is no business relevant Azure ACS usage anymore. The assessment tool should give administrators the usage information to understand where and when Azure ACS principals are being used.
After: No saved wording on this side.
RemovedTurn off the use of Azure ACS on your tenant
[removed: This setting will not impact the Azure ACS usage by SharePoint provider hosted Add-Ins. You can use the same command to re-enable the usage Azure ACS app-only access if required.]
Before: This setting will not impact the Azure ACS usage by SharePoint provider hosted Add-Ins. You can use the same command to re-enable the usage Azure ACS app-only access if required.
After: No saved wording on this side.
RemovedMore information
[removed: A Message Center post in the Microsoft 365 admin center is being sent to all tenants, and the post will be updated periodically with timelines.]
Before: A Message Center post in the Microsoft 365 admin center is being sent to all tenants, and the post will be updated periodically with timelines.
After: No saved wording on this side.

Source: Microsoft source · © Microsoft · CC BY 4.0.

Read the current Microsoft source · Link to this observation · Compare any two versions

Observation details
Observed by ChangeIntel
29 Oct 01:42 UTC
Source update metadata
28 Oct 10:43 UTC
Microsoft's latest commit in that period
SPFx 1.24 GA docs updates - with Copilot Components GA (#11075) · committed 28 Oct 10:38 UTC · View diff
First observed on this installation
8 Oct 23:29 UTC
Last successful check
today 06:50 UTC
Next check due
today 12:50 UTC

Observation time is not publication time, and a comparison does not establish an effective date. Full source bodies are not published; this page holds generated summaries, section headings and, as the page's license allows, Microsoft's changed wording. A documentation edit does not confirm feature availability in an environment. Article references show literal targets and labels, including relative addresses; image bytes are not captured or compared.

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 18 Nov 07:49 UTC · 273 of 275 readable · 249 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current