The failure occurs because the app’s current configuration doesn’t support changing the supported account types directly in the Authentication blade. Specifically, the underlying signInAudience and related properties (such as the App ID URI) must be valid for multi‑tenant or personal Microsoft accounts.
Use the app registration manifest to adjust the supported account types instead of the Authentication (Preview) pane:
- In the Microsoft Entra admin center, go to Entra ID → App registrations and select the application.
- Select Manifest.
- Download the JSON manifest.
- Locate the
signInAudience property and set it to the value that matches the required audience, for example:
-
AzureADMyOrg – single tenant
-
AzureADMultipleOrgs – any organizational directory (multitenant)
-
AzureADandPersonalMicrosoftAccount – any Entra ID tenant + personal Microsoft accounts
-
PersonalMicrosoftAccount – personal Microsoft accounts only
- Save the JSON file and upload it back in the Manifest editor.
If changing to a multitenant or personal‑account audience still fails, check the Application ID URI (App ID URI):
- For a multitenant app, the App ID URI must be globally unique and its host name must match one of the tenant’s verified domains (for example,
https://contoso.com/myapp if contoso.com is a verified domain).
- If the App ID URI does not follow this pattern, converting the app registration to multi‑tenant fails. In that case, update the App ID URI to use a verified domain and then try changing the supported account types again.
If the app was originally created as single‑tenant and the signInAudience cannot be changed (or the portal blocks the change), re‑create the app registration with the correct account type selected from the start and migrate configuration (redirect URIs, permissions, secrets/certificates) to the new registration.
References: