A tool for managing user identities, credentials, and access across on-premises and cloud environments
The error indicates that the personal Microsoft account now only exists in the default “Microsoft Services” tenant and not in any Microsoft Entra (Azure AD) tenant that can host applications or resources. This matches the documented behavior where personal Microsoft accounts that sign in to the Microsoft Entra admin center are connected only to the Microsoft Services tenant and have no linked directory.
To regain the ability to manage applications and resources, a new Azure tenant must be created and associated with the personal Microsoft account:
- Create an Azure account and tenant
- Browse to the Azure account website using the “Try Azure for free” entry point.
- Follow the steps to create an Azure account with the existing personal Microsoft account.
- As part of this process, a new Microsoft Entra tenant is created and linked to the account.
- The account is automatically assigned the Global Administrator role in this new tenant, restoring full access to Microsoft Entra and Azure resources in that tenant.
- Recreate or reconfigure app registrations
- After the new tenant is created, recreate any required app registrations in that tenant and configure OAuth settings there.
- If the application must be accessible to other organizations or personal accounts, ensure the app registration’s sign-in audience (
signInAudience) is set appropriately (for example, multitenant or multitenant + personal accounts) and that the correct sign-in URL (/organizations,/common, or/consumers) is used in the application’s authority configuration.
- If guest access is needed
- For access to applications in another tenant, the personal account must be invited as a guest user to that tenant before it can sign in.
These steps restore a functional tenant for the personal account and resolve the “user account does not exist in tenant ‘Microsoft Services’” error when trying to manage applications.
References: