Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 258/260 feeds/APIs · 416/439 docs · checked 00:57 UTC Customize Public modeDiscuss ChangeIntel on Discord

SharePoint Azure ACS retirement

This page's changes and edits · All guidance changes

Microsoft's edit ·

Archive legacy Modernization Scanner guidance (#10959)

Microsoft's commit message in SharePoint/sp-dev-docs · commit fe38473 · +3 −3 lines · also on GitHub

⋯ 7 unchanged lines
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](https://learn.microsoft.com/azure/active-directory/develop/).
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/).
1212
1313 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.
1414
⋯ 7 unchanged lines
2222
2323 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.
2424
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](https://learn.microsoft.com/azure/active-directory/develop/).
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/).
2626
2727 ### Azure ACS usage by SharePoint Server
2828
⋯ 7 unchanged lines
3636
3737 ### Microsoft 365 Assessment tool
3838
39 −To understand if your organization is using Azure ACS or begin planning transition to Microsoft Entra ID, we recommend that customers run the [Microsoft 365 Assessment tool](https://aka.ms/assessment/addinsacs) to scan their tenants for Azure ACS usage. Using the Power BI [Azure ACS Report](https://aka.ms/assessment/addinsacsreport) generated by the scanner tool, you can:
39 +To understand if your organization is using Azure ACS or begin planning transition to Microsoft Entra ID, we recommend that customers run the Microsoft 365 Assessment tool to scan their tenants for Azure ACS usage. Using the Power BI **Azure ACS Report** generated by the scanner tool, you can:
4040
4141 - Identify all used Azure ACS application principals with their key properties such as permission scopes and whether app-only was allowed or not
4242 - For each identified Azure ACS application principal see a list of all sites that can be accessed via the Azure ACS application principal
⋯ 30 unchanged lines

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 10 Oct 01:29 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.

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 21 Oct 00:57 UTC · 258 of 260 readable · 256 fully read · documentation 416/439 current