Specifying client ID and secret when creating an Azure ACS principal via AppRegNew.aspx will be removed
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.What the notice says
Microsoft’s text, safely structuredWhen using the AppRegNew.aspx page to create Azure ACS (Access Control Service) principals today, you can generate a new client ID (default flow) and secret, but you can also specify the client ID or secret yourselves. Going forward, the option to specify the client ID and secret yourself will be removed. Each created Azure ACS principal will have a unique client ID (a GUID) and a system-generated secret. After the creation of the Azure ACS principal, you’ll be redirected to a page showing the created client ID and secret.
How this will affect your organization
If you used to specify a specific client ID as a way to renew the associated service principal secret then please switch the recommended model for renewing secrets for Azure ACS service principals.
We will gradually roll out this change in early October 2024, and we expect to complete by early November 2024.
Reminder: Azure ACS in Microsoft 365 is being retired with a final end date of April 2, 2026. You can learn more via the retirement announcement or via MC693863.
What you need to do to prepare
This change will happen automatically by the specified date. No admin action is required.
What changed
Between archive captures, newest first- Services
SharePoint Online, Microsoft OneDrive→ SharePoint Online, OneDrive for Business
- Services
- · first version seen
Learn more
Links from the notice and their documentation checks- recommended model for renewing secrets for Azure ACS service principalsNot read yet
- retirement announcementChecked 14 Nov 2026
Notices it cites
Other posts named in this one- MC693863 · Azure ACS retirement in Microsoft 365Plan for change · changed 2 Mar 2026From Microsoft 365 Message Center Archive by Merill Fernando
Related public changes
No related announcements were found in the saved public history. Check the source for newer announcements.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
- 1 linked page has not been read yet.