![Specifying client ID and secret when creating an Azure ACS principal via AppRegNew.aspx will be removed [MC898388]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pixabay-221185-1024x683.webp)
When 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.
Source: Microsoft
![Stay current with your OS to keep your Microsoft Teams desktop client supported [MC898394]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pixabay-461929-150x150.webp)
![Planned maintenance for all certified and supported Teams Android Devices to Company Portal version [MC898390]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-googledeepmind-17483868-150x150.webp)
The upcoming update regarding the removal of the option to specify client ID and secret when creating an Azure ACS principal via AppRegNew.aspx will have an impact on both admins and users. Admins who are used to specifying specific client IDs for renewing service principal secrets will need to switch to the recommended model for renewing secrets. As for users, they will experience a more streamlined process with each Azure ACS principal having a unique client ID and system-generated secret.
In terms of criticality, this change is important as it aligns with the retirement of Azure ACS in Microsoft 365 by April 2, 2026. The gradual rollout starting in early October 2024 ensures a smooth transition for organizations using Azure ACS.
Admins and users, rest assured that this change will happen automatically by the specified date, requiring no additional action on your part. So, sit back, relax, and let the system do the work for you!
Remember, change is the only constant in the tech world, so embrace it like a software update – necessary for better performance and security!