User assignment required off with common tenant gives error AADSTS50105

Avery Scott 1 Reputation point
2021-03-04T00:07:41.493+00:00

We have an Enterprise application configured in Azure Active Directory with "User assignment required" turned off (screenshot attached for reference).74032--azure-enterprise-props.jpg

We want Microsoft users to be able to authenticate with it using the 'common' tenant. But some users are getting the error code AADSTS50105 when they try to authenticate.

Is there something we need to adjust to allow for all users to authenticate with our app using the 'common' tenant? Or is there something users need to adjust within their own tenants to authenticate?

Microsoft Security | Microsoft Entra | Microsoft Entra ID
{count} votes

1 answer

Sort by: Most helpful
  1. AmanpreetSingh-MSFT 56,871 Reputation points Moderator
    2021-04-08T07:12:32.35+00:00

    Hi @Avery Scott · Thank you for sharing required information.

    I tracked the details in our backend database. Please find my findings below:

    • The application is a multi-tenant app published at reliancenetwork.
    • User Assignment Required is set to NO in the publisher tenant.
    • When this application was accessed and consented by a user of your tenant, a service principal corresponding to this application was registered in your tenant.
    • In the service principal properties, User Assignment Required is set to YES in your tenant. This is why when a user, who is not assigned a role to the application in your tenant, access the application, ends up with AADSTS50105 error.

    Looking at the screenshot that you have provided, I suspect the portal is not reflecting correct settings. I would suggest you to use below PowerShell Cmdlets:

    To see the setting:
    Run Get-AzureADServicePrincipal -ObjectId object_id_of_service_principal | fl app* and make sure AppRoleAssignmentRequired is set False in the output.

    If the value is true, run Set-AzureADServicePrincipal -ObjectId object_id_of_service_principal -AppRoleAssignmentRequired $false to set it to False.

    Note: You need to use Global Admin or Application Admin account to run the above cmdlet.

    -----------------------------------------------------------------------------------------------------------

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.