issue with Azure Language Studio

The error indicates that the signed-in account does not belong to the Microsoft Entra tenant that the Azure Language Studio application is using, so it cannot access the app.

Use these steps to resolve it:

1. Confirm the correct account/tenant
   • The message shows tenant Microsoft Services. This is typically the default tenant for personal Microsoft accounts (Outlook, Hotmail, etc.) and is not where Azure resources or app registrations usually live.
   • Make sure to use the work/school account that belongs to the tenant where Azure Language Studio (and the Azure subscription) is set up.
2. Sign out and clear existing sessions
   • Sign out from all Microsoft accounts in the browser.
   • Clear browser cookies/site data for Microsoft sign-in pages.
   • Open a new InPrivate/Incognito window and try to access Azure Language Studio again.
   • When prompted, select Use another account and sign in with the correct work/school account.
3. If using the wrong tenant (personal vs. organization)
   • If a personal Microsoft account is being used but the app is registered in an organization tenant, switch to the organization tenant account.
   • For My Apps–style access, ensure the correct tenant is targeted (for example, using a tenant-specific URL as described in the My Apps troubleshooting article) and then sign in with the organization account.
4. If the account truly belongs to a different tenant
   • If the account is from another organization and needs access to the tenant where Azure Language Studio is configured, the tenant admin must:
     • Invite that account as a guest user to the tenant.
     • Or, if the app requires user assignment, explicitly assign that user (or a group containing it) to the application.
5. If the app is single-tenant but needs external access
   • If the Language Studio–backing app registration is single-tenant, users from other tenants cannot sign in.
   • In that case, the app registration must be recreated with a supported signInAudience (for example, AzureADMultipleOrgs or AzureADandPersonalMicrosoftAccount) if cross-tenant or personal account access is required.
6. If the error appears in a “Pick an account” dialog
   • This is the same pattern as the documented Web API SPA sample: the selected account is not in the app’s tenant.
   • Resolution is to choose an account that belongs to the same Microsoft Entra tenant as the registered application.

If none of the above helps and the correct tenant/account combination still fails, the tenant admin should review sign-in logs in Microsoft Entra ID for the failing user to confirm which tenant and identity provider are being used, and adjust guest invitations or app assignments accordingly.

References:

• Error AADSTS50020 - User account from identity provider does not exist in tenant
• Quickstart: Web API with client-side JavaScript and Visual Studio Code
• Troubleshoot problems with the My Apps portal