A cloud-based identity and access management service for securing user authentication and resource access
Hey Jennifer – thanks for all the details. Seeing “Contributor” in the Roles tab but not in the picker (plus that classic-admin server error) usually boils down to one of a few things:
- Shadowed by a custom role It’s possible someone created a custom role also named “Contributor” whose assignableScopes don’t include your subscription. The portal shows all roles on the Roles tab, but the Add-role dialog only lists roles assignable at that scope.
- Run in Azure Cloud Shell or PowerShell:
Get-AzRoleDefinition -Name "Contributor"Do you see more than one definition? Check each one’s AssignableScopes. - If there is a custom “Contributor” with limited scopes, either delete/rename it or scope it correctly.
- You can force the built-in role assignment via CLI:
or by GUID:az role assignment create \ --assignee ******@yourdomain.com \ --role "Contributor" \ --scope "/subscriptions/<your-subscription-ID>"az role assignment create \ --assignee ******@yourdomain.com \ --role "b24988ac-6180-42a0-ab88-20f7382dd24c" \ --scope "/subscriptions/<your-subscription-ID>"
- Run in Azure Cloud Shell or PowerShell:
- Portal/UI glitch or deny-assignment is filtering it out
- Try the same assignment in CLI or PowerShell. If it succeeds, the portal UX is mis-filtering.
- Check for denyAssignments on your subscription or management group via Resource Explorer under:
/subscriptions/<id>/providers/Microsoft.Authorization/denyAssignments
- Conditional/PIM policies on Azure RBAC roles
- If you have Azure AD (Microsoft Entra) conditional access or PIM policies that restrict which roles can be assigned (or which principals can receive them), the portal picker will only show the allowed roles.
Quick things to try right away:
• Run that Get-AzRoleDefinition check for duplicate “Contributor” roles and review AssignableScopes.
• Attempt the assignment via CLI or PowerShell to see if it bypasses the portal filter.
• Confirm whether you can see Owner or Reader in the “Add role assignment” picker (helps narrow if it’s a global filter).
A few follow-up questions to zero in on the root cause:
- When you run
Get-AzRoleDefinition -Name "Contributor", how many entries come back and what are their AssignableScopes? - Does the CLI/PowerShell approach to assign Contributor at the subscription scope succeed or give an error?
- In the portal picker, can you see any of the built-in roles like Owner or Reader?
- Do you have any deny assignments on that subscription or its parent management group?
- Are there any conditional-access or PIM policies targeting Azure RBAC roles in your directory?
- Are your developers fully redeemed as Guests in Microsoft Entra ID (i.e., they show up under Entra ID → Users)?
Answering those will help pinpoint exactly why the portal is hiding the Contributor role. Let me know!
Note: This content was drafted with the help of an AI system. Please verify the information before relying on it for decision-making.