Reputation: 5870
Why is "user.assignedroles" null, and resulting in not being sent in token?
I am encountering this scenario know. And even though I can see that I am assigned roles within azure and Active Directory, this value still must be set to null.
that it states that with respect to user.assignedroles "If the role claim value is null, then Azure AD will not send this value in the token and this is default as per design."
This is how I know that it is null. (because it is not being sent)
Upvotes: 2
Views: 2807
Reputation: 16448
You assigned your user a role whose value is "null".
You can check it in Microsoft Graph Explorer:
https://graph.microsoft.com/beta/servicePrincipals/{Object ID of your Enterprise App}
In the response, check the role you have assigned. If the the value of "value" is null, Azure AD will not send this value in the token.
So when you update an existing role, remember to set the "value" to a meaningful value.
Upvotes: 2