Azure ACS retirement in Microsoft 365 and using app context with id and secret

Question

We are using SharePoint online. We are seeing the below notice on SharePoint app registration page since few months now:

Starting April 2, 2026, Azure Access Control service (ACS) usage will be retired for SharePoint in Microsoft 365 and users will no longer be able to create or use Azure ACS principals to access SharePoint.

We have been registering the app in Entra ID and giving the app Full Control access on SharePoint tenant by navigating to https://{tenant}-admin.sharepoint.com/_layouts/15/appinv.aspx and then adding below XML permission request (removed tags as adding XML is not working in the question):

AppPermissionRequests AllowAppOnlyPolicy="true"
   AppPermissionRequest Scope="http://sharepoint/content/tenant" Right="FullControl" 
AppPermissionRequests

While accessing SharePoint content, we use the client ID and client secret created from the app registered in Entra ID. We use PnP and SharePoint CSOM package. Our app service is running on .NET Framework 4.6 and 4.8.

Will our app get affected due to the Azure ACS retirement since we use lot of app context using client ID and client secret?

Answer 1

Dear Sushrut Paranjape,

Good day to you!

I hope you are doing well. Thanks for reaching out to our Microsoft Community Forum. We will be happy to help you.

Yes, your app will may be affected by the Azure ACS retirement. Starting April 2, 2026, Azure ACS will no longer be available for SharePoint in Microsoft 365, and Azure ACS principals will no longer function.

To ensure continued functionality, transition to Microsoft Entra ID for authentication and authorization. This requires registering your app in Entra ID and updating it to use the new authentication model. SharePoint Add-Ins and Azure ACS retirement FAQ | Microsoft Learn.

For more clarification, I sincerely recommend you may post your concern to specific channels. Microsoft has a specific channel Microsoft Entra ID - Microsoft Q&A. You may ask the question in this community. The members and engineers there are highly knowledgeable about Development related issue. I’m confident that their expertise can help address your query effectively and accurately.

The reason I emphasize avoiding incorrect information is to ensure clarity, accuracy, and reliability in communication. Providing precise and well-detailed responses fosters trust and helps prevent confusion or misunderstandings.

I do apologize for any inconvenience.

Thank you for your understanding. Your cooperation and contributions are greatly appreciated.

Kind Regards,

Nahid Sultan