Seamless Migration from Azure AD B2C to Microsoft Entra External ID (Retaining Existing Consents)

Dear Microsoft Support Team,

We are planning to migrate our application from Azure AD B2C to Microsoft Entra External ID. This migration is coupled with a major rebranding effort, including changes to our application’s name and URL. We currently have numerous customers who have granted admin consent to our app on behalf of their organizations, and we are concerned about the potential need for them to re-consent in the new environment.

Current Scenario

1. Existing Setup
   • Our application is registered in Azure AD B2C.
   • Many customers have already integrated their Azure AD tenants with our app, granting admin consent on behalf of their organizations.
2. Upcoming Changes
   • We intend to migrate our current Azure AD B2C setup to Microsoft Entra External ID.
   • A rebranding initiative will change the name and URL of the application.
   • Update our Application in the App Gallery is also needed (new URL, new Name, new authentication endpoint)
3. Key Concern
   • We fear that existing consents may become invalid after the migration and rebranding, forcing each organization’s admin to grant consent again. This would be disruptive and risk losing user trust and adoption.

If retaining consents is not entirely feasible, what alternative approaches might simplify or streamline the admin consent process for our customers? Like registering a second application in the app gallery?

We greatly appreciate any guidance you can offer.