Elevate access to manage all Azure subscriptions and management groups

As a Global Administrator in Microsoft Entra ID, you might not have access to all subscriptions and management groups in your tenant. This article describes the ways that you can elevate your access to all subscriptions and management groups.

Note

For information about viewing or deleting personal data, see General Data Subject Requests for the GDPR, Azure Data Subject Requests for the GDPR, or Windows Data Subject Requests for the GDPR, depending on your specific area and needs. For more information about GDPR, see the GDPR section of the Microsoft Trust Center and the GDPR section of the Service Trust portal.

Why would you need to elevate your access?

If you are a Global Administrator, there might be times when you want to do the following actions:

• Regain access to an Azure subscription or management group when a user has lost access
• Grant another user or yourself access to an Azure subscription or management group
• See all Azure subscriptions or management groups in an organization
• Allow an automation app (such as an invoicing or auditing app) to access all Azure subscriptions or management groups

How does elevated access work?

Microsoft Entra ID and Azure resources are secured independently from one another. That is, Microsoft Entra role assignments do not grant access to Azure resources, and Azure role assignments do not grant access to Microsoft Entra ID. However, if you are a Global Administrator in Microsoft Entra ID, you can assign yourself access to all Azure subscriptions and management groups in your tenant. Use this capability if you don't have access to Azure subscription resources, such as virtual machines or storage accounts, and you want to use your Global Administrator privilege to gain access to those resources.

When you elevate your access, you are assigned the User Access Administrator role in Azure at root scope (/). This allows you to view all resources and assign access in any subscription or management group in the tenant. User Access Administrator role assignments can be removed using Azure PowerShell, Azure CLI, or the REST API.

You should remove this elevated access once you have made the changes you need to make at root scope.

Perform steps at root scope

Azure portal

Step 1: Elevate access for a Global Administrator

Follow these steps to elevate access for a Global Administrator using the Azure portal.

1. Sign in to the Azure portal as a Global Administrator.

   If you are using Microsoft Entra Privileged Identity Management, activate your Global Administrator role assignment.

2. Browse to Microsoft Entra ID > Manage > Properties.

   

3. Under Access management for Azure resources, set the toggle to Yes.

   

   When you set the toggle to Yes, you are assigned the User Access Administrator role in Azure RBAC at root scope (/). This grants you permission to assign roles in all Azure subscriptions and management groups associated with this Microsoft Entra tenant. This toggle is only available to users who are assigned the Global Administrator role in Microsoft Entra ID.

   When you set the toggle to No, the User Access Administrator role in Azure RBAC is removed from your user account. You can no longer assign roles in all Azure subscriptions and management groups that are associated with this Microsoft Entra tenant. You can view and manage only the Azure subscriptions and management groups to which you have been granted access.

   Note

   If you're using Privileged Identity Management, deactivating your role assignment does not change the Access management for Azure resources toggle to No. To maintain least privileged access, we recommend that you set this toggle to No before you deactivate your role assignment.

4. Select Save to save your setting.

   This setting is not a global property and applies only to the currently signed in user. You can't elevate access for all members of the Global Administrator role.

5. Sign out and sign back in to refresh your access.

   You should now have access to all subscriptions and management groups in your tenant. When you view the Access control (IAM) page, you'll notice that you have been assigned the User Access Administrator role at root scope.

   

6. Make the changes you need to make at elevated access.

   For information about assigning roles, see Assign Azure roles using the Azure portal. If you are using Privileged Identity Management, see Discover Azure resources to manage or Assign Azure resource roles.

7. Perform the steps in the following section to remove your elevated access.

Step 2: Remove elevated access

To remove the User Access Administrator role assignment at root scope (/), follow these steps.

1. Sign in as the same user that was used to elevate access.

2. Browse to Microsoft Entra ID > Manage > Properties.

3. Set the Access management for Azure resources toggle back to No. Since this is a per-user setting, you must be signed in as the same user as was used to elevate access.

   If you try to remove the User Access Administrator role assignment on the Access control (IAM) page, you'll see the following message. To remove the role assignment, you must set the toggle back to No or use Azure PowerShell, Azure CLI, or the REST API.

   

4. Sign out as Global Administrator.

   If you are using Privileged Identity Management, deactivate your Global Administrator role assignment.

   Note

   If you're using Privileged Identity Management, deactivating your role assignment does not change the Access management for Azure resources toggle to No. To maintain least privileged access, we recommend that you set this toggle to No before you deactivate your role assignment.

PowerShell

Step 1: Elevate access for a Global Administrator

Use the Azure portal or REST API to elevate access for a Global Administrator.

Step 2: List role assignment at root scope (/)

Once you have elevated access, to list the User Access Administrator role assignment for a user at root scope (/), use the Get-AzRoleAssignment command.

Get-AzRoleAssignment | where {$_.RoleDefinitionName -eq "User Access Administrator" `
  -and $_.SignInName -eq "<username@example.com>" -and $_.Scope -eq "/"}

RoleAssignmentId   : /providers/Microsoft.Authorization/roleAssignments/11111111-1111-1111-1111-111111111111
Scope              : /
DisplayName        : username
SignInName         : username@example.com
RoleDefinitionName : User Access Administrator
RoleDefinitionId   : 18d7d88d-d35e-4fb5-a5c3-7773c20a72d9
ObjectId           : 22222222-2222-2222-2222-222222222222
ObjectType         : User
CanDelegate        : False

Step 3: Remove elevated access

To remove the User Access Administrator role assignment for yourself or another user at root scope (/), follow these steps.

1. Sign in as a user that can remove elevated access. This can be the same user that was used to elevate access or another Global Administrator with elevated access at root scope.

2. Use the Remove-AzRoleAssignment command to remove the User Access Administrator role assignment.

   Remove-AzRoleAssignment -SignInName <username@example.com> `
     -RoleDefinitionName "User Access Administrator" -Scope "/"
   

Azure CLI

Step 1: Elevate access for a Global Administrator

Use the following basic steps to elevate access for a Global Administrator using the Azure CLI.

1. Use the az rest command to call the elevateAccess endpoint, which grants you the User Access Administrator role at root scope (/).

   az rest --method post --url "/providers/Microsoft.Authorization/elevateAccess?api-version=2016-07-01"
   

2. Make the changes you need to make at elevated access.

   For information about assigning roles, see Assign Azure roles using the Azure CLI.

3. Perform the steps in a later section to remove your elevated access.

Step 2: List role assignment at root scope (/)

Once you have elevated access, to list the User Access Administrator role assignment for a user at root scope (/), use the az role assignment list command.

az role assignment list --role "User Access Administrator" --scope "/"

[
  {
    "canDelegate": null,
    "id": "/providers/Microsoft.Authorization/roleAssignments/11111111-1111-1111-1111-111111111111",
    "name": "11111111-1111-1111-1111-111111111111",
    "principalId": "22222222-2222-2222-2222-222222222222",
    "principalName": "username@example.com",
    "principalType": "User",
    "roleDefinitionId": "/providers/Microsoft.Authorization/roleDefinitions/18d7d88d-d35e-4fb5-a5c3-7773c20a72d9",
    "roleDefinitionName": "User Access Administrator",
    "scope": "/",
    "type": "Microsoft.Authorization/roleAssignments"
  }
]

Step 3: Remove elevated access

To remove the User Access Administrator role assignment for yourself or another user at root scope (/), follow these steps.

1. Sign in as a user that can remove elevated access. This can be the same user that was used to elevate access or another Global Administrator with elevated access at root scope.

2. Use the az role assignment delete command to remove the User Access Administrator role assignment.

   az role assignment delete --assignee username@example.com --role "User Access Administrator" --scope "/"
   

REST API

Prerequisites

You must use the following versions:

• 2015-07-01 or later to list and remove role assignments
• 2016-07-01 or later to elevate access
• 2018-07-01-preview or later to list deny assignments

For more information, see API versions of Azure RBAC REST APIs.

Step 1: Elevate access for a Global Administrator

Use the following basic steps to elevate access for a Global Administrator using the REST API.

1. Using REST, call elevateAccess, which grants you the User Access Administrator role at root scope (/).

   POST https://management.azure.com/providers/Microsoft.Authorization/elevateAccess?api-version=2016-07-01
   

2. Make the changes you need to make at elevated access.

   For information about assigning roles, see Assign Azure roles using the REST API.

3. Perform the steps in a later section to remove your elevated access.

Step 2: List role assignments at root scope (/)

Once you have elevated access, you can list all of the role assignments for a user at root scope (/).

• Call Role Assignments - List For Scope where {objectIdOfUser} is the object ID of the user whose role assignments you want to retrieve.

  GET https://management.azure.com/providers/Microsoft.Authorization/roleAssignments?api-version=2022-04-01&$filter=principalId+eq+'{objectIdOfUser}'
  

Step 3: List deny assignments at root scope (/)

Once you have elevated access, you can list all of the deny assignments for a user at root scope (/).

• Call Deny Assignments - List For Scope where {objectIdOfUser} is the object ID of the user whose deny assignments you want to retrieve.

  GET https://management.azure.com/providers/Microsoft.Authorization/denyAssignments?api-version=2022-04-01&$filter=gdprExportPrincipalId+eq+'{objectIdOfUser}'
  

Step 4: Remove elevated access

When you call elevateAccess, you create a role assignment for yourself, so to revoke those privileges you need to remove the User Access Administrator role assignment for yourself at root scope (/).

1. Call Role Definitions - Get where roleName equals User Access Administrator to determine the name ID of the User Access Administrator role.

   GET https://management.azure.com/providers/Microsoft.Authorization/roleDefinitions?api-version=2022-04-01&$filter=roleName+eq+'User Access Administrator'
   

   {
     "value": [
       {
         "properties": {
     "roleName": "User Access Administrator",
     "type": "BuiltInRole",
     "description": "Lets you manage user access to Azure resources.",
     "assignableScopes": [
       "/"
     ],
     "permissions": [
       {
         "actions": [
           "*/read",
           "Microsoft.Authorization/*",
           "Microsoft.Support/*"
         ],
         "notActions": []
       }
     ],
     "createdOn": "0001-01-01T08:00:00.0000000Z",
     "updatedOn": "2016-05-31T23:14:04.6964687Z",
     "createdBy": null,
     "updatedBy": null
         },
         "id": "/providers/Microsoft.Authorization/roleDefinitions/18d7d88d-d35e-4fb5-a5c3-7773c20a72d9",
         "type": "Microsoft.Authorization/roleDefinitions",
         "name": "18d7d88d-d35e-4fb5-a5c3-7773c20a72d9"
       }
     ],
     "nextLink": null
   }
   

   Save the ID from the name parameter, in this case 18d7d88d-d35e-4fb5-a5c3-7773c20a72d9.

2. You also need to list the role assignment for the tenant administrator at tenant scope. List all assignments at tenant scope for the principalId of the tenant administrator who made the elevate access call. This will list all assignments in the tenant for the objectid.

   GET https://management.azure.com/providers/Microsoft.Authorization/roleAssignments?api-version=2022-04-01&$filter=principalId+eq+'{objectid}'
   

   Note

   A tenant administrator should not have many assignments. If the previous query returns too many assignments, you can also query for all assignments just at tenant scope, then filter the results: GET https://management.azure.com/providers/Microsoft.Authorization/roleAssignments?api-version=2022-04-01&$filter=atScope()

3. The previous calls return a list of role assignments. Find the role assignment where the scope is "/" and the roleDefinitionId ends with the role name ID you found in step 1 and principalId matches the objectId of the tenant administrator.

   Sample role assignment:

   {
     "value": [
       {
         "properties": {
           "roleDefinitionId": "/providers/Microsoft.Authorization/roleDefinitions/18d7d88d-d35e-4fb5-a5c3-7773c20a72d9",
           "principalId": "{objectID}",
           "scope": "/",
           "createdOn": "2016-08-17T19:21:16.3422480Z",
           "updatedOn": "2016-08-17T19:21:16.3422480Z",
           "createdBy": "22222222-2222-2222-2222-222222222222",
           "updatedBy": "22222222-2222-2222-2222-222222222222"
         },
         "id": "/providers/Microsoft.Authorization/roleAssignments/11111111-1111-1111-1111-111111111111",
         "type": "Microsoft.Authorization/roleAssignments",
         "name": "11111111-1111-1111-1111-111111111111"
       }
     ],
     "nextLink": null
   }
   

   Again, save the ID from the name parameter, in this case 11111111-1111-1111-1111-111111111111.

4. Finally, Use the role assignment ID to remove the assignment added by elevateAccess:

   DELETE https://management.azure.com/providers/Microsoft.Authorization/roleAssignments/11111111-1111-1111-1111-111111111111?api-version=2022-04-01
   

View users with elevated access

If you have users with elevated access, banners are displayed in a couple locations of the Azure portal. This section describes how to determine if you have users that have elevated access in your tenant. This capability is being deployed in stages, so it might not be available yet in your tenant.

Option 1

1. In the Azure portal, browse to Microsoft Entra ID > Manage > Properties.

2. Under Access management for Azure resources, look for the following banner.

   You have X users with elevated access. Microsoft Security recommends deleting access for users who have unnecessary elevated access. Manage elevated access users

   

3. Select the Manage elevated access users link to view a list of users with elevated access.

Option 2

1. In the Azure portal, browse to a subscription.

2. Select Access control (IAM).

3. At the top of the page, look for the following banner.

   Action required: X users have elevated access in your tenant. You should take immediate action and remove all role assignments with elevated access. View role assignments

   

4. Select the View role assignments link to view a list of users with elevated access.

Remove elevated access for users

If you have users with elevated access, you should take immediate action and remove that access. To remove these role assignments, you must also have elevated access. This section describes how to remove elevated access for users in your tenant using the Azure portal. This capability is being deployed in stages, so it might not be available yet in your tenant.

1. Sign in to the Azure portal as a Global Administrator.

2. Browse to Microsoft Entra ID > Manage > Properties.

3. Under Access management for Azure resources, set the toggle to Yes as described earlier in Step 1: Elevate access for a Global Administrator.

4. Select the Manage elevated access users link.

   The Users with elevated access appears pane appears with a list of users with elevated access in your tenant.

   

5. To remove elevated access for users, add a check mark next to the user and select Remove.

View elevate access log entries

When access is elevated or removed, an entry is added to the logs. As an administrator in Microsoft Entra ID, you might want to check when access was elevated and who did it.

Elevate access log entries appear in both the Microsoft Entra directory audit logs and the Azure activity logs. Elevated access log entries for directory audit logs and activity logs include similar information. However, the directory audit logs are easier to filter and export. Also, the export capability enables you to stream access events, which can be used for your alert and detection solutions, such as Microsoft Sentinel or other systems. For information about how to send logs to different destinations, see Configure Microsoft Entra diagnostic settings for activity logs.

This section describes different ways that you can view the elevate access log entries.

Microsoft Entra audit logs

Important

Elevate access log entries in the Microsoft Entra directory audit logs is currently in preview. This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see Supplemental Terms of Use for Microsoft Azure Previews.

1. Sign in to the Azure portal as a Global Administrator.

2. Browse to Microsoft Entra ID > Monitoring > Audit logs.

3. In the Service filter, select Azure RBAC (Elevated Access) and then select Apply.

   Elevated access logs are displayed.

   

4. To view details when access was elevated or removed, select these audit log entries.

   User has elevated their access to User Access Administrator for their Azure Resources

   The role assignment of User Access Administrator has been removed from the user

   

5. To download and view the payload of the log entries in JSON format, select Download and JSON.

   

Azure activity logs

View elevate access log entries using the Azure portal

1. Sign in to the Azure portal as a Global Administrator.

2. Browse to Monitor > Activity log.

3. Change the Activity list to Directory Activity.

4. Search for the following operation, which signifies the elevate access action.

   Assigns the caller to User Access Administrator role

   

View elevate access log entries using Azure CLI

1. Use the az login command to sign in as Global Administrator.

2. Use the az rest command to make the following call where you will have to filter by a date as shown with the example timestamp and specify a filename where you want the logs to be stored.

   The url calls an API to retrieve the logs in Microsoft.Insights. The output will be saved to your file.

   az rest --url "https://management.azure.com/providers/Microsoft.Insights/eventtypes/management/values?api-version=2015-04-01&$filter=eventTimestamp ge '2021-09-10T20:00:00Z'" > output.txt
   

3. In the output file, search for elevateAccess.

   The log will resemble the following where you can see the timestamp of when the action occurred and who called it.

     "submissionTimestamp": "2021-08-27T15:42:00.1527942Z",
     "subscriptionId": "",
     "tenantId": "33333333-3333-3333-3333-333333333333"
   },
   {
     "authorization": {
       "action": "Microsoft.Authorization/elevateAccess/action",
       "scope": "/providers/Microsoft.Authorization"
     },
     "caller": "user@example.com",
     "category": {
       "localizedValue": "Administrative",
       "value": "Administrative"
     },
   

Delegate access to a group to view elevate access log entries using Azure CLI

If you want to be able to periodically get the elevate access log entries, you can delegate access to a group and then use Azure CLI.

1. Browse to Microsoft Entra ID > Groups.

2. Create a new security group and note the group object ID.

3. Use the az login command to sign in as Global Administrator.

4. Use the az role assignment create command to assign the Reader role to the group who can only read logs at the tenant level, which are found at Microsoft/Insights.

   az role assignment create --assignee "{groupId}" --role "Reader" --scope "/providers/Microsoft.Insights"
   

5. Add a user who will read logs to the previously created group.

A user in the group can now periodically run the az rest command to view elevate access log entries.

az rest --url "https://management.azure.com/providers/Microsoft.Insights/eventtypes/management/values?api-version=2015-04-01&$filter=eventTimestamp ge '2021-09-10T20:00:00Z'" > output.txt

Detect elevate access events using Microsoft Sentinel

To detect elevate access events and gain visibility into potentially fraudulent activities, you can use Microsoft Sentinel. Microsoft Sentinel is a security information and event management (SIEM) platform that provides security analytics and threat response capabilities. This section describes how to connect Microsoft Entra audit logs to Microsoft Sentinel so that you can detect elevate access in your organization.

Step 1: Enable Microsoft Sentinel

To get started, add Microsoft Sentinel to an existing Log Analytics workspace or create a new one.

• Enable Microsoft Sentinel by following the steps at Enable Microsoft Sentinel.

  

Step 2: Connect Microsoft Entra data to Microsoft Sentinel

In this step, you install the Microsoft Entra ID solution and use the Microsoft Entra ID connector to collect data from Microsoft Entra ID.

Your organization might have already configured a diagnostic setting to integrate the Microsoft Entra audit logs. To check, view your diagnostic settings as described in How to access diagnostic settings.

1. Install the Microsoft Entra ID solution by following the steps at Discover and manage Microsoft Sentinel out-of-the-box content.

   

2. Use the Microsoft Entra ID connector to collect data from Microsoft Entra ID by following the steps at Connect Microsoft Entra data to Microsoft Sentinel.

3. On the Data connectors page, add a check mark for Audit Logs.

   

Step 3: Create an elevate access rule

In this step, you create a scheduled analytics rule based on a template to examine the Microsoft Entra audit logs for elevate access events.

1. Create an elevate access analytics rule by following the steps at Create a rule from a template.

2. Select the Azure RBAC (Elevate Access) template then select the Create rule button on the details pane.

   If you don't see the details pane, on the right edge, select the expand icon.

   

3. In the Analytics rule wizard, use the default settings to create a new scheduled rule.

   

Step 4: View incidents of elevate access

In this step, you view and investigate elevate access incidents.

• Use the Incidents page to view incidents of elevate access by following the steps at Navigate and investigate incidents in Microsoft Sentinel.

  

Next steps

• Understand the different roles
• Assign Azure roles using the REST API