Managing external identities to enable secure access for partners, customers, and other non-employees
The error means the personal Microsoft account from live.com no longer exists as a user in that old client’s Entra ID tenant, so Azure Portal can’t sign in there with that account.
To resolve:
- Switch to a different tenant that the account can access
In the Azure Portal or Entra admin center sign-in page, use the tenant picker to select a different directory where thegmail.comaccount is actually a member. If necessary, sign out completely from all Microsoft accounts in the browser and sign back in, then choose the correct directory. - Remove or re-add the account in that tenant (admin required)
If access to that old client tenant is still required, an administrator in thexxxxxx Corp.tenant must add thegmail.comaccount as a guest user:- Sign in to the Microsoft Entra admin center as at least a user administrator or higher.
- Go to Entra ID > Users and verify whether the account exists. If not, add it as an external (guest) user and assign any required roles or app access.
- Use the correct sign-in endpoint for the account type
If using custom apps or tools, ensure the authority/endpoint matches the account type. For example, for personal Microsoft accounts or multi-tenant apps, use the appropriate sign-in URL instead of a tenant-specific one:- Multitenant apps:
https://login.microsoftonline.com/organizations - Multitenant + personal accounts:
https://login.microsoftonline.com/common - Personal accounts only:
https://login.microsoftonline.com/consumers
- Multitenant apps:
If the account should no longer access that client’s tenant, simply ensure a different directory is selected when opening Azure Portal and ignore that old tenant.
References: