| Announcement ID | MC898388 | Published Date | 09-26-2024 | |
| Service | General | Last Updated | 09-26-2024 | |
| Category | Plan for change | Expiration Date | 04-30-2026 | |
| Roadmap ID | Action Required by Date | |||
| Tags | Admin impact, Retirement | |||
| Summary |
|---|
| The option to specify client ID and secret when creating Azure ACS principals will be removed. Users must adopt the system-generated client ID and secret. This change will start in early October 2024 and end by early November 2024. No admin action is required for this automatic change. Azure ACS is retiring on April 2, 2026. |
| More Information |
|---|
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. |