The error code AADSTS50034 appears in Microsoft 365 when a user attempts to sign in with a non-existent or unidentified account within the service tenant. This issue is common among both IT administrators and users, especially when switching between different work environments or using inactive email addresses.
Error AADSTS50034 typically indicates that the username is not registered in Azure Active Directory or that the account is not properly linked to the organization. In some cases, the cause may be an incorrect email address, a deleted account, or an identity synchronization issue between on-premises and cloud systems.
Understanding why error code AADSTS50034 appears helps resolve the issue quickly and minimize downtime. In this guide, you'll learn about common causes of the error, account verification steps, and the best ways to easily regain access to Microsoft 365.
Quick tips
- Always check your primary username (UPN) before logging in, especially if your organization uses multiple domains.
- Make sure the tenant's URL is correct when accessing Microsoft 365 applications to avoid logging into the wrong directory.
- Ask your system administrator to check your account type and synchronization status if you have recently changed roles or domains or have been recently added to the organization.
If you're trying to sign in to your Microsoft 365 account or access a connected app and suddenly get an error message, you might be puzzled. One less common option is: “AADSTS50034: The user account {email} is not in the directory. To sign in to this app, the account must be added to the directory.”
This error indicates that the account does not exist (the same account you were using). More specifically, the Entra ID cannot find the user directory you are trying to sign in to. The good news is that there is a fix for error code AADSTS50034 that may appear in Microsoft 365 applications.
Solution 1: Check your account type (member or guest) to resolve the AADSTS50034 error code issue in Microsoft 365.
The most common reason for the AADSTS50034 error is that your account is set to “Guest” instead of “Member” in your Microsoft Entra ID. Many applications (especially third-party tools and migration services) prevent guest accounts from authenticating. Even if you are a full-time employee, your account may have been created or configured in error as a guest instead of a member.
You will need to use the Microsoft Entra admin center.
Step 1: Open a web browser and go to https://entra.microsoft.com Log in using an administrator account.
Step 2: In the left sidebar, click on “identity"then on"UsersTo display all users.
To step 3Locate the user account you are trying to fix and click on it to open its profile.
Step 4Look at the field "User type"If it is written “.يف“That’s the problem.”
Step 5. Click on the buttonRelease"At the top, change the user type from "ض“Yef” to “Member".
Step 6. tap on "saveTo implement the change.
Step 7. Ask the user to log out permanently, close all browser windows, and then log back in.
Solution 2: Use the correct username format for error code AADSTS50034 in Microsoft 365
Microsoft Entra ID authenticates users using their primary username (UPN), not their email address. Although they often look similar, they are not identical. If you try to sign in using only an email address (such as [email protected]) when you should be using your primary username (such as [email protected]), you will receive error AADSTS50034.
Step 1. Open the management center Microsoft Entra (https://entra.microsoft.com) as an administrator.
Step 2. Go to “Identity” > “Users”"And look for the affected account."
Step 3. Look at the “Primary Username” field. This is your primary username, and it should be in the format [email protected] or [email protected].
Step 4Sign in using this primary username instead of your email address. For example, use [email protected] instead of [email protected].
Step 5. Test your arrival again.
Solution 3: Make sure you reach the correct tenant
If your company manages multiple Microsoft 365 accounts, you might be trying to sign in to the wrong account. Each user is a completely separate directory. Your account exists in one account but not in another. If you're trying to access an application associated with a different account, you'll receive error AADSTS50034 because your account doesn't actually exist in that directory.
Step 1Contact the IT department or system administrator to confirm which account your account belongs to.
Step 2: Look at the URL of the application or portal you are trying to access. It should tell you which account it is connecting to.
To step 3: Log out completely, including from all browser tabs and applications.
Step 4: Clear your browser's cookies and cache, or try logging in using a private/incognito browsing window.
Step 5: Log in again, and make sure you are using the correct account for the correct account.
Browser cache and cookies can sometimes cause you to be redirected to the wrong account. Clearing these files often resolves the issue.
Solution 4: Sync your local account with the cloud.
If your organization uses Azure AD Hybrid (which links on-premises Active Directory to a Microsoft Enterprise ID), your account must be synchronized between the two systems. If the synchronization fails or is incomplete, your account may exist in on-premises Active Directory but not in the cloud. This causes the AADSTS50034 error when you try to sign in to cloud applications.
To resolve this issue, please contact your IT administrator. Only administrators with access to Azure AD Connect can perform a full synchronization.
Error code AADSTS50034 is a common sign-in error in Microsoft 365, often related to a missing account or incorrect account definition within the system. Verifying your email address, reviewing your Azure Active Directory settings, and ensuring your accounts are properly synchronized will resolve the issue in most cases.
If the error persists despite performing the basic steps, it is recommended to contact your system administrator or Microsoft support to ensure that the tenant and accounts are configured correctly, and to avoid a recurrence of the problem in the future.
