Specifying client ID and secret when creating an Azure ACS principal via AppRegNew.aspx will be removed
Starting from early October 2024, Azure ACS (Access Control Service) will remove the option to specify client ID and secret when creating principals. Instead, each created Azure ACS principal will have a system-generated client ID and secret, which will be unique. This change requires no admin action and will automatically roll out by early November 2024, closer to the Azure ACS retirement date of April 2, 2026. After creating the Azure ACS principal, you'll be redirected to a page showing the generated client ID and secret. If your organization used to specify a specific client ID to renew the associated service principal secret, please switch to the recommended model for renewing Azure ACS service principal secrets. To ensure a smooth transition, users must adopt the new system-generated client ID and secret. You can learn more about the Azure ACS retirement through the retirement announcement or MC693863.
The post Specifying client ID and secret when creating an Azure ACS principal via AppRegNew.aspx will be removed appeared first on M365 Admin.
Published on:
Learn more
Related posts
WCF Authentication with Azure Active Directory by username and password using JWT(JSON Web Token)
Looking to incorporate Azure Active Directory (AAD) into your WCF authentication process? This tutorial explores how to accomplish just that b...
Regenerating secrets for Azure DevOps OAuth applications
Azure DevOps has introduced a new feature that allows users to self-regenerate new client secrets for applications built on its OAuth platform...
Azure ACS retirement in Microsoft 365
Microsoft is retiring Azure ACS (Access Control Services) as an authentication platform for SharePoint Online. Since its first use by SharePoi...
Migrate to the Authentication methods policy in Azure Active Directory by September 30, 2025
Attention Azure Active Directory users! On September 30th, 2025, Microsoft will be retiring the management of authentication methods in the le...
Azure OpenAI Service achieves FedRAMP high authorization
The Azure OpenAI Service has recently achieved a significant milestone, receiving the US Federal Risk and Authorization Management Program (Fe...
Introducing Service Principal and Managed Identity support on Azure DevOps
Azure DevOps has recently introduced support for Service Principals and Managed Identities to enable teams' access to their Azure DevOps organ...
Duplicate Azure Active Directory Conditional Access policies
This post provides valuable insights on managing Azure Active Directory Conditional Access policies. The focus is on the process of duplicatin...
Azure Active Directory: Tenant Creation Lockdown
Azure Active Directory has introduced a new capability that gives administrators the power to lock down tenant creation so they can decide if ...
Azure Government Secret expands DoD IL6 services, receives highest level information categorization
Azure Government Secret has earned the highest level information categorization and a Provisional Authorization (PA) at Department of Defense ...
Azure Active Directory Conditional Access
If you want to know more about Conditional Access in Azure Active Directory, this podcast episode is a must-listen. In this episode, Daniel Wo...