Why a Global Admin Must Elevate Before Removing an Azure Owner
Short answer
D First instruct Admin1, the Global Administrator, to enable Access management for Azure resources so they gain root-scope User Access Administrator and can remove User1's Owner role on Sub1.
Question
You have a user named User1 and a global administrator named Admin1.
You are informed that User1 created an Azure subscription named Sub1 under the MG2 management group and is the only owner of the subscription.
You need to ensure that Admin1 can remove the Owner role from User1 for Sub1.
What should you do first?
Key Takeaways
The question tests the separation between Microsoft Entra directory roles and Azure RBAC, and the trap is assuming Global Administrator automatically controls subscription role assignments.
This SC-500 scenario tests how a Microsoft Entra Global Administrator obtains Azure RBAC access when a user is the only Owner of a subscription. The correct first action is to enable Access management for Azure resources (D), not to assign an Azure role directly.
Common mistake: Option B is tempting because User Access Administrator is the precise role needed at Sub1, but Admin1 cannot assign that role first: it requires existing Azure RBAC access, and User1 is the only Owner.
Expert Analysis
The decisive qualifier is “first.” Admin1 is a Microsoft Entra Global Administrator, not an Azure subscription Owner. A Global Administrator does not, by default, have permissions to read or manage Azure resources or Azure RBAC role assignments. Because User1 is the only Owner of Sub1, there is no other subscription-level principal who could assign Admin1 a role there. Therefore the first move is not to assign an Azure role; it is to give Admin1 a path into the Azure control plane. Option D does that by enabling Access management for Azure resources, which elevates the Global Administrator and assigns User Access Administrator at root scope. After that, Admin1 can remove User1's Owner assignment on Sub1.
Why the other options fail. Option A, moving Sub1 to MG1, changes inheritance but does not grant Admin1 access; it assumes an unknown MG1 assignment. Option B describes the permission Admin1 will ultimately need at Sub1, but Admin1 cannot assign it to himself without previous Azure access, and the only owner is User1. Option C invokes Privileged Identity Management for Security Administrator, an Entra role that does not manage Azure RBAC assignments at subscription scope. Option D is the prerequisite step.
What the discussion adds. The comments note that the toggle is broad, comparable to root-level elevation, and should be disabled after use to respect least privilege. Another explanation emphasizes that enabling it automatically grants User Access Administrator. Both points support D as the first step; B is a later least-privilege scoping choice, not something Admin1 can do first.
Official Reference
https://learn.microsoft.com/en-us/azure/role-based-access-control/elevate-access-global-admin
This link opens the official vendor documentation in a new tab.
Exam Strategy
When a question puts a Microsoft Entra Global Administrator against an Azure RBAC assignment, first ask whether the administrator has ever elevated into the Azure control plane. Directory roles do not equal subscription permissions. Look for “Access management for Azure resources” when the user must manage subscriptions, management groups, or role assignments; reserve User Access Administrator assignments for after elevation and only at the narrowest scope.
Frequently Asked Questions
Why can't Admin1 assign User Access Administrator directly on Sub1?
Does enabling Access management for Azure resources violate least privilege?
Which role does the toggle grant?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 2 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 2
-
Eltooth 👍 3 Answered DD is correct answer. Elevates Global Admin Privileges: By default, a Microsoft Entra Global Administrator does not have permission to manage Azure subscriptions or management groups. Enabling the Access management for Azure resources toggle elevates the Global Administrator's access. Grants User Access Administrator Role: Turning this setting on automatically assigns the User Access Administrator role to the Global Admin at the absolute root management group level (/). This permission inherits down to all management groups (including MG2) and all subscriptions (including Sub1), giving Admin1 the necessary authority to modify permissions and remove User1 as an Owner.
-
volto 👍 1Of course, the “Manage access to Azure resources” feature solves many access-related problems, just like root privileges in Linux ;) However, this does not comply with the principle of least privilege. If you assign user Admin1 to subscription Sub1 with the “User Access Administrator” role, that user will also be able to revoke the owner role from user User1. BUT... not in this case. If User1 creates Subscription 1 in Management Group 2, they will likely have the Owner role at the management group level, and this role will be inherited at the subscription level. This means that the “User Access Administrator” role at the subscription level is not sufficient to revoke this permission. Therefore, answer D is correct.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SC-500 Questions
Access 100 questions with complete answers and detailed explanations.
View Full SC-500 Practice Test →