An Azure service that provides fine-grained access management for Azure resources, enabling you to grant users only the rights they need to perform their jobs.
Global Administrator or Privileged Role Administrator in Microsoft Entra ID does not automatically grant Azure RBAC permissions at the root management group. To assign RBAC roles at root scope, the signed-in account must first elevate access and obtain User Access Administrator at root scope (/).
Use this recovery path:
- Sign in to the Azure portal as a Global Administrator.
- If Privileged Identity Management is used, activate the Global Administrator role first.
- Go to Microsoft Entra ID > Manage > Properties.
- Under Access management for Azure resources, set the toggle to Yes, then select Save.
- This assigns User Access Administrator in Azure RBAC at root scope (
/). - This setting applies only to the currently signed-in user.
- This assigns User Access Administrator in Azure RBAC at root scope (
- Sign out and sign back in to refresh access.
- Open the root management group or the relevant Access control (IAM) page and create the required role assignment.
- To assign Azure roles, the account needs
Microsoft.Authorization/roleAssignments/write, such as User Access Administrator or Role Based Access Control Administrator at the target scope.
- To assign Azure roles, the account needs
- After the required changes are complete, remove the elevated access:
- Return to Microsoft Entra ID > Manage > Properties
- Set Access management for Azure resources back to No
- Sign out again
Important checks based on the reported symptoms:
- If Add role assignment is disabled or assignments fail with
AuthorizationFailed, the current account does not have effectiveMicrosoft.Authorization/roleAssignments/writeat that scope, or the role assignment is constrained by conditions. - If roles or principals are missing in the picker, check the roles already assigned to the account and whether a condition restricts which roles or principals can be assigned.
- If access was recently granted, refresh credentials by signing out and back in.
The available guidance supports elevation and permission recovery at root scope. It does not provide a documented self-service repair procedure for an orphaned or inconsistent root management group hierarchy beyond regaining root-scope access through elevation.