Skip to main content

AADSTS50105: the user isn't assigned to the application

AADSTS50105

Sign-in to the app is refused because the app requires user assignment and the user has no assignment to it, either directly or through a group they belong to directly.

From Microsoft's documentation, checked 20 Nov 2026.

Microsoft Entra ID enterprise applications (user assignment)App assignmentHigh
Error text as Microsoft documents it
AADSTS50105: EntitlementGrantsNotFound - The signed in user isn't assigned to a role for the signed in app.

Also searched as: EntitlementGrantsNotFound · The signed in user is not assigned to a role for the application · user not assigned to a role · Assignment required

What it means

When an enterprise application has "Assignment required?" set to Yes, Microsoft Entra ID only issues tokens to users who are assigned to the app. Everyone else is blocked at sign-in with AADSTS50105. The user can be assigned directly, or through a group assigned to the app that they are a direct member of. Assigning them to Default Access is enough when the app defines no roles of its own.

Common causes

  • The app's "Assignment required?" property is set to Yes, and the user has no app role assignment.
  • The user is only in the assigned group through a nested group. Group-based assignment doesn't cascade to nested groups.

From Microsoft's documentation

How to fix it

  1. Find the failing sign-in

    List recent sign-ins with Microsoft Graph PowerShell (needs AuditLog.Read.All) and find the one whose status.errorCode is 50105; note its application. Then in the Microsoft Entra admin center go to Entra ID > Enterprise apps > All applications, select that app, open Properties and check "Assignment required?".

    $since = (Get-Date).ToUniversalTime().AddDays(-7).ToString("yyyy-MM-ddTHH:mm:ssZ")
    Get-MgAuditLogSignIn -Filter "createdDateTime ge $since" -Top 10
  2. List who is assigned to the app

    List the app role assignments on the app's service principal (needs Application.Read.All) and look for the user, or a group the user is a direct member of. Membership through a nested group doesn't count.

    Get-MgServicePrincipalAppRoleAssignedTo -ServicePrincipalId <service-principal-object-id>
  3. Assign the user, or stop requiring assignment

    As a Cloud Application Administrator, Application Administrator or owner of the service principal: open the app, select Users and groups > Add user/group, pick the user or a group they are directly in, choose a role (Default Access if the app defines none) and select Assign. Only if every user in the tenant should be able to get tokens for the app, set "Assignment required?" to No and save instead; Conditional Access still applies.

How to confirm it's fixed

  • Sign in again as the affected user, not as a Global Administrator: Microsoft notes the assignment check doesn't apply to Global Administrators, so their test proves nothing.
  • The newest sign-in record for that user and app has no 50105 in status.errorCode.

Related notes

Group-based assignment needs Microsoft Entra ID P1 or P2. Some apps can only have assignment required turned on or off through PowerShell, with the service principal's appRoleAssignmentRequired property.

Copyable operational controls

Related engineering templates

Continue the investigation

The KBY Brief

Follow Microsoft Entra ID failures and fixes

A short email about twice a week with new runbooks, configuration traps and fixes from KBY Technologies.