account not founf in tenant

This error usually means the account being used is not available in the tenant being targeted, or the wrong account/tenant endpoint is being used.

Try these fixes in order:

1. Sign out of all Microsoft sessions, then sign in again
   • Open a new InPrivate/Incognito browser window or use a different browser.
   • Sign out of any existing Microsoft account sessions.
   • Sign in again with the intended account.
   • This helps when the browser is reusing the wrong personal or work account session.
2. Check whether the correct account type is being used
   • This error can happen if a personal Microsoft account is used where an organizational account is expected, or the reverse.
   • Verify that the account matches the tenant and application being accessed.
3. If the account is a guest account, make sure it was invited to the tenant
   • The account must exist as an external user in the target tenant before it can access the application.
   • A tenant administrator should invite the guest user.
4. If this is an application sign-in issue, verify the app registration supports the account type
   • In Azure portal > App registrations > select the app > Manifest.
   • Check signInAudience.
   • Supported values for cross-tenant or personal-account scenarios are:
     • AzureADandPersonalMicrosoftAccount
     • AzureADMultipleOrgs
     • PersonalMicrosoftAccount
   • If the app was created as single-tenant, it must be re-created with the correct account type. The signInAudience value cannot currently be changed in the manifest.
5. Use the correct sign-in endpoint for the app type
   • Multitenant applications: https://login.microsoftonline.com/organizations
   • Multitenant and personal accounts: https://login.microsoftonline.com/common
   • Personal accounts only: https://login.microsoftonline.com/consumers
   • If a tenant-specific endpoint such as https://login.microsoftonline.com/<YourTenantNameOrID> is used, users from other organizations cannot access unless they are added as guests in that tenant.
6. If signing in to Microsoft Entra admin center with a personal Microsoft account
   • Personal Microsoft accounts connect to the Microsoft Services tenant by default, which does not provide a linked directory for admin actions.
   • If a directory is needed, create an Azure account and a new tenant.

If the scenario is simply accessing a tenant as an external user, the most common fixes are:

• sign out and retry in a private browser session
• use the correct account
• have the tenant admin invite the account as a guest

References:

• Error AADSTS50020 - User account from identity provider does not exist in tenant