Fix it now
Entra ID accepted the credentials but could not find that account in the tenant that owns the application, so it was turned away at the door. It is not a password fault, a licence fault or an outage. Either the identity lives in another directory and was never invited in, or it is in the tenant but has not been assigned to the application.
- Open a private browsing window and sign in again with the account you actually intend to use. A large share of these errors is a second, cached account being sent instead of the right one.
- In the Microsoft Entra admin center, go to Microsoft Entra ID then Users and search for the account. If it is not listed, it is not in this tenant, and that is the entire explanation.
- If it is listed, check the application before the account: open the enterprise application and look at whether assignment is required. A user who is not assigned, directly or through a group, gets this error even though they are unquestionably in the tenant.
- If the person should be a guest, invite them: Microsoft Entra ID then Users then New user then Invite external user, sending it to the exact address they will sign in with. User Administrator is the role that can do it.
- If the guest is listed with an invitation state that is not Accepted, open the user, find the B2B collaboration tile on the Overview tab and resend the invitation.
- Recheck the attempt in Entra ID then Monitoring & health then Sign-in logs, and read the record to see which tenant rejected it.
An invitation does not expire, so an old one that was never redeemed is still usable. What it cannot survive is being sent to an alias rather than the address the person actually signs in with.
If the sign-in completes from a clean browser session, you are done. If it still fails, the next section covers which of the two tenants is refusing and why.
Why it happens
Two tenants are involved in nearly every one of these failures. The home tenant holds the identity and checks the password. The resource tenant owns the application and issues the token that grants access. For the resource tenant to issue anything, a principal for that person has to exist inside it: their own user object if they are an employee, or a guest object created by an invitation and linked back to their home directory if they are not.
The authority the application uses decides which tenant gets asked. A tenant-specific endpoint only ever looks in that one directory, so a multitenant application pointed at https://login.microsoftonline.com/<TenantID> will refuse accounts from anywhere else. The multitenant endpoints are /organizations for work and school accounts, /common for those plus personal Microsoft accounts, and /consumers for personal accounts only. An application registered to accept accounts from a single organisation behaves the same way whichever endpoint the client calls, because the registration is the tighter constraint.
The trap is that being in the tenant is not sufficient. If the enterprise application has assignment required set to Yes, only users assigned to it directly or through a group can obtain a token, and everyone else gets AADSTS50020 despite being a perfectly ordinary member of the directory. That case looks nothing like a guest problem and is the one most likely to be misdiagnosed, because the account is right there in the user list.
The application requires assignment and the user is not assigned
You have this one if The account is plainly in the tenant, colleagues can use the application, and this person cannot.
- Open the application under Enterprise applications and check whether assignment is required.
- Assign the user directly, or add them to a group that is already assigned.
- Retry the sign-in. Nothing about the account itself needed changing.
This is the case that wastes the most time, because every check aimed at guest invitations comes back clean.
The external user was never invited into the resource tenant
You have this one if The account signs into its own organisation without trouble and fails only against this one application.
- Go to Microsoft Entra ID then Users then New user then Invite external user, as a User Administrator or higher.
- Use the address the person will actually sign in with. An invitation sent to an alias cannot be redeemed by the primary account.
- Have them open the invitation and complete redemption before retrying.
- If invitations are restricted, check the external collaboration settings and the cross-tenant access settings for the partner organisation.
The invitation exists but was never redeemed
You have this one if The guest appears in the user list with an invitation state that is not Accepted, and AADSTS50014 shows in the sign-in record.
- Open the guest under Microsoft Entra ID then Users, find the B2B collaboration tile on the Overview tab, and resend the invitation.
- Confirm the person is redeeming with the same account the invitation was addressed to.
- If they redeemed with a different identity by mistake, reset the redemption status rather than deleting and re-inviting.
The application only accepts accounts from its own organisation
You have this one if Every external account fails identically, including ones you know exist elsewhere, and the application was written in-house.
- Open the app registration’s Authentication settings and read the supported account types.
- If it is meant to serve other organisations, set the registration to accept accounts in any organisational directory, and use
/organizationsrather than a tenant-specific authority. - If it is meant to serve only your own people plus named partners, leave it single-tenant and invite those partners as guests instead.
Widening the supported account types changes who can consent to the application. Review the permissions it requests before you do it.
The account exists only in on-premises Active Directory
You have this one if You can see the user in Active Directory Users and Computers but not in the Microsoft Entra admin center.
- Check whether the user’s organisational unit is inside the synchronisation scope on your directory sync server.
- Force a cycle with
Start-ADSyncSyncCycle -PolicyType Delta. - Recheck the user list before retrying the sign-in.
AADSTS90072 can also mean an ImmutableID mismatch between Active Directory and Entra ID on an account that is synchronised, which looks like a missing account and is not.
Full reference
Which authority the application should be using
| Application type | Authority |
|---|---|
| Single organisation only | https://login.microsoftonline.com/<TenantID> |
| Multitenant, work and school accounts | https://login.microsoftonline.com/organizations |
| Multitenant plus personal Microsoft accounts | https://login.microsoftonline.com/common |
| Personal Microsoft accounts only | https://login.microsoftonline.com/consumers |
A multitenant application pointed at a tenant-specific authority is a common cause of this error and is invisible from the directory, because nothing about the account is wrong.
Matching the symptom to the missing piece
| What you are seeing | Where the gap is |
|---|---|
| The account belongs to another company and was never invited | No guest object exists in the resource tenant |
| The user is listed but shows an unaccepted invitation state | An invitation was issued and never redeemed |
| Colleagues can sign in, one person cannot | Assignment is required and that person is not assigned |
| Only one person, and they are freshly created on premises | The account exists only on premises and has not synchronised |
| Every external account fails the same way | The app registration accepts a single organisation only |
| The sign-in page shows personal account branding | A personal Microsoft account being used where a work account is required |
Recreated accounts, and why re-inviting is the wrong instinct
When a guest’s home tenant account is deleted and recreated, the guest object in your tenant no longer lines up with it. Deleting and re-inviting works but discards everything attached to the old object. Resetting the redemption status is the supported route: it re-invites the user while keeping the object ID, group memberships and app assignments, and when they redeem the new invitation their user principal name does not change even though their sign-in name does.
- In the admin center: Entra ID then Users, select the user, Overview tab, B2B collaboration tile, Reset redemption status.
- In PowerShell:
New-MgInvitationwith-ResetRedemption,-InvitedUser $userand the new email address. - Use it when the person wants to sign in with a different email or identity provider, when their home account was recreated, or when they have moved to another company but still need the same access.
- It is also the answer when a guest redeemed with the wrong identity by mistake.
Finding out which tenant refused
The error page carries a request identifier and a timestamp. Take both to Entra ID then Monitoring & health then Sign-in logs in the tenant that owns the application, and search for the matching entry. The record names the directory that handled the request, which settles the argument about whose problem it is faster than any amount of discussion between two IT teams. Reports Reader is enough to read it.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
AADSTS50020 |
UserUnauthorized: the account from that identity provider does not exist in the tenant and cannot access the application in it. It also appears when the application requires assignment and the user is not assigned | Microsoft Learn |
AADSTS50034 |
UserAccountNotFound: to sign in to this application the account must be added to the directory. A mistyped username, or an account that is not in the tenant | Microsoft Learn |
AADSTS51004 |
UserAccountNotInDirectory: the user account does not exist in the directory, commonly because the application chose the wrong tenant to sign in to | Microsoft Learn |
AADSTS90072 |
PassThroughUserMfaError: the external account does not exist on the tenant signed into, so the user cannot satisfy that tenant’s MFA requirement. It can also indicate an ImmutableID mismatch between Active Directory and Entra ID | Microsoft Learn |
AADSTS50014 |
GuestUserInPendingState: the guest object exists but the invitation has not been redeemed | Microsoft Learn |
Confirm the fix worked
- The account appears in the user list with the expected user type and, for a guest, an accepted invitation state.
- If the application requires assignment, the user is assigned directly or through a group.
- A fresh sign-in from a private browsing window opens the application without the error.
- The sign-in logs show a successful entry for that user against that application.
- No conditional access failure sits underneath the successful entry.
Questions people ask about this
Do I have to buy anything to fix this?
No. Creating a guest object, sending an invitation and assigning a user to an application are standard directory operations available to every tenant. Nothing in this article is gated behind a paid plan.
The user is definitely in the tenant. Why does it still say they are not?
Check whether the enterprise application requires assignment. If it does and the user is not assigned directly or through a group, they get this error despite being an ordinary member of the directory.
Why does the same account work in Teams but not in this application?
Because they are different resources, and often different tenants. Access to one service says nothing about whether a principal exists, or an assignment exists, for the application you are now trying to open.
The user was deleted and recreated. Why is it still failing?
A recreated account is a new object with a new identifier, so the guest relationship attached to the old one no longer lines up. Reset the redemption status rather than deleting and re-inviting; it keeps the object ID, group memberships and app assignments.
How do I find out which tenant rejected the sign-in?
The error page carries a request identifier and a timestamp. Take those to the sign-in logs in the tenant that owns the application; the record names the directory that handled the request.
