Clarification on ACS Retirement Impact for Power Apps and Power Automate

Question

Hi,

We are aware that the retirement of Azure Access Control Services (ACS) impacts custom applications that authenticate to SharePoint. Could you confirm whether this change will also affect Power Apps or Power Automate flows that connect to SharePoint, please?

For reference, Microsoft’s announcement regarding ACS retirement is available here:

https://learn.microsoft.com/en-gb/sharepoint/dev/sp-add-ins/retirement-announcement-for-azure-acs

Regards,

Answer 1

Hi @Nanjappa, Ashwini 

Thank you for posting your question in the Microsoft Q&A forum. 

The retirement of Azure Access Control Services (ACS) does not affect Power Apps or Power Automate flows that connect to SharePoint using the standard SharePoint connector. These services authenticate through Microsoft Entra ID (modern OAuth) and do not rely on ACS. ACS retirement is limited to legacy SharePoint Add‑Ins and custom applications registered using the SharePoint Add‑In model. 

However, it could still be relevant indirectly in the following scenarios: 

-A Power Automate flow uses the HTTP or HTTP with Azure AD action to call a custom API that still depends on ACS. 

-You have legacy integrations outside the standard SharePoint connector that were originally built on the SharePoint Add‑In model. 

In those cases, the custom endpoint, not Power Automate itself, would need to be modernized to use Entra ID authentication. 

I hope this clarifies the impact. 

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

Answer 2

ACS retirement specifically affects solutions that use Azure Access Control Services–based authentication to SharePoint Online, such as:

• SharePoint Add-Ins (provider-hosted and low-trust add-ins)
• Custom applications or services that obtain SharePoint access tokens from ACS (for example, using the classic OAuth flows described for SharePoint Add-Ins)

The documentation states that:

• Using Azure ACS for SharePoint Online has been retired as of November 27th, 2023 and will stop working from April 2nd, 2026.
• The SharePoint Add-In model in SharePoint Online is also retired on April 2nd, 2026, with SharePoint Framework (SPFx) as the primary replacement.

The provided context only describes impact on:

• SharePoint Add-Ins and custom apps that rely on ACS-based auth
• Related OAuth flows and app-only models using ACS

It does not state that Power Apps or Power Automate flows that connect to SharePoint are impacted by ACS retirement, nor does it describe those products as using ACS in this way. The impact described is limited to ACS-based authentication patterns and the SharePoint Add-In model.

---

References:

• Azure ACS retirement in Microsoft 365
• Modernization guidance for existing SharePoint Add-In model implementations in Microsoft 365
• (Retired!) Granting access using SharePoint Azure ACS App-Only
• Access SharePoint from mobile and native device apps
• Three authorization systems for SharePoint Add-ins
• Authorization and authentication of SharePoint Add-ins
• Create provider-hosted SharePoint Add-ins to access SAP data by using the SAP Gateway for Microsoft