SharePoint Azure ACS retirement
Microsoft's edit ·
Microsoft's commit message in SharePoint/sp-dev-docs · commit f59497d · +12 −10 lines · also on GitHub
11
---
22
title: Azure ACS retirement in Microsoft 365
33
description: Describes the details around the retirement of Azure ACS (Access Control Services) for SharePoint Online in Microsoft 365.
4
−ms.date: 11/13/2023
4
+ms.date: 10/25/2026
55
ms.localizationpriority: high
66
ms.service: sharepoint
77
---
88
99
# Azure ACS retirement in Microsoft 365
1010
11
−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](/azure/active-directory/develop/).
11
+[!INCLUDE [sp-add-in-deprecation](../../includes/snippets/sp-add-in-deprecation.md)]
1212
13
−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.
13
+Azure ACS (Access Control Services) authentication for SharePoint Online was retired on April 2, 2026. Use modern authentication through [Microsoft Entra ID](/entra/identity-platform/) instead.
1414
15
−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](https://aka.ms/retirement/addins/support) for more information. There will not be an option to extend using Azure ACS with SharePoint Online beyond April 2nd, 2026.
15
+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.
1616
17
+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](retirement-announcement-for-add-ins.md). There is no option to extend Azure ACS use with SharePoint Online beyond April 2, 2026.
18
+
1719
To learn more about how to migrate Azure ACS usage for SharePoint Online and how to migrate SharePoint Add-Ins to alternative solutions check out these [articles](https://aka.ms/retirement/addins/guidance) and accompanying [videos](https://aka.ms/sp/add-in/modernize/videos).
1820
1921
## Overview
2022
2123
### Azure ACS usage in SharePoint Online
2224
23
−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.
25
+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.
2426
25
−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](/azure/active-directory/develop/).
27
+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](/entra/identity-platform/).
2628
2729
### Azure ACS usage by SharePoint Server
2830
⋯ 1 unchanged line
3032
3133
### Azure ACS usage by Project Online
3234
33
−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.
35
+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.
3436
3537
## Call to Action Guidance
3638
⋯ 8 unchanged lines
4547
4648
### Turn off the use of Azure ACS on your tenant
4749
48
−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.
50
+Before retirement, tenant admins could turn off Azure ACS app-only access after migrating dependent applications. The following command is retained for historical context:
4951
5052
```PowerShell
5153
Connect-SPOService -Url https://<tenant>-admin.sharepoint.com
5254
Set-SPOTenant -DisableCustomAppAuthentication $true
5355
```
5456
55
−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.
57
+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.
5658
5759
## How do I get help?
5860
⋯ 10 unchanged lines
6971
- Friendly link to the SharePoint Add-In retirement article: https://aka.ms/retirement/addins/support
7072
- Friendly link to Migration Guidance: https://aka.ms/retirement/acs/guidance
7173
72
−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.
74
+The retirement was also communicated through the Microsoft 365 admin center Message Center.
Microsoft's Markdown source from SharePoint/sp-dev-docs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 29 Oct 01:12 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.