Azure portal login issue.

AADSTS50020/AADSTS16000 in this scenario matches a known Azure portal sign-in pattern for personal Microsoft accounts. When a personal account signs in to Azure, it can be connected to the Microsoft Services tenant by default. That tenant does not provide a usable directory for Azure administration, so the portal can initially load and then fail when it requests another token for portal components.

What to check and do:

1. Confirm whether the session is landing in the wrong tenant
   • In the error text, verify that the identity provider is live.com and the tenant is Microsoft Services.
   • That combination indicates the portal is authenticating the personal Microsoft account against the Microsoft Services tenant instead of a tenant that contains the Azure subscription.
2. Rule out an active session mismatch
   • Sign out of all Microsoft sessions.
   • Open a different browser or an InPrivate/Incognito session.
   • Sign in again with only the intended account.
   • This is the documented fix when an existing session is using the wrong personal or organizational account.
3. If the account is a personal Microsoft account and no usable tenant exists, create an Azure account with a new tenant
   • Go to the Azure account sign-up flow and create a new Azure account.
   • A new tenant is created with that Azure account, and the account becomes the Global Administrator for that tenant.
   • This is the documented resolution when signing in with a personal Microsoft account results in being placed in the Microsoft Services tenant.
4. If the subscription already exists, verify the selected directory in Azure portal
   • In Azure portal, select the account menu at the top right.
   • Choose Switch directory and select the correct directory.
   • If the correct directory is already selected and the subscription still does not appear, the account might not have sufficient permissions on that subscription.
5. If the issue is specifically with a guest or cross-tenant sign-in, verify the account is actually present in the target tenant
   • If the account is expected to access a different tenant, it must be added there as an external user first.
   • If it was never invited, it cannot sign in to resources in that tenant.

Based on the described behavior across multiple browsers and devices, the most likely documented cause is that the personal Microsoft account is being authenticated into the Microsoft Services tenant rather than a tenant created for the Azure subscription. The supported self-service path is to sign in with a clean browser session and, if no usable tenant exists, create a new Azure account so a new tenant is provisioned.

• Error AADSTS50020 - User account from identity provider does not exist in tenant
• No subscriptions found sign in error for Azure portal
• Azure portal authentication issue - Microsoft Q&A
• Can't use Azure Portal - Microsoft Q&A
• How can I reset my Azure account - Microsoft Q&A
• How to fix subscription issues - Microsoft Q&A