Skip to content

Commit b4bd509

Browse files
authored
Merge pull request #291339 from rolyon/rolyon-rbac-elevate-access-manage-users
[Azure RBAC] Remove elevated access for users
2 parents a8783ad + 2649390 commit b4bd509

File tree

4 files changed

+70
-24
lines changed

4 files changed

+70
-24
lines changed

articles/role-based-access-control/elevate-access-global-admin.md

Lines changed: 70 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,13 @@ author: rolyon
55
manager: amycolannino
66
ms.service: role-based-access-control
77
ms.topic: how-to
8-
ms.date: 02/16/2024
8+
ms.date: 12/10/2024
99
ms.author: rolyon
1010
ms.custom: devx-track-azurecli
1111
---
1212
# Elevate access to manage all Azure subscriptions and management groups
1313

14-
As a Global Administrator in Microsoft Entra ID, you might not have access to all subscriptions and management groups in your directory. This article describes the ways that you can elevate your access to all subscriptions and management groups.
14+
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.
1515

1616
[!INCLUDE [gdpr-dsr-and-stp-note](~/reusable-content/ce-skilling/azure/includes/gdpr-dsr-and-stp-note.md)]
1717

@@ -26,9 +26,9 @@ If you are a Global Administrator, there might be times when you want to do the
2626

2727
## How does elevated access work?
2828

29-
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](../active-directory/roles/permissions-reference.md#global-administrator) in Microsoft Entra ID, you can assign yourself access to all Azure subscriptions and management groups in your directory. 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.
29+
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](/entra/identity/role-based-access-control/permissions-reference#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.
3030

31-
When you elevate your access, you will be assigned the [User Access Administrator](built-in-roles.md#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 directory. User Access Administrator role assignments can be removed using Azure PowerShell, Azure CLI, or the REST API.
31+
When you elevate your access, you are assigned the [User Access Administrator](built-in-roles.md#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.
3232

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

@@ -44,38 +44,36 @@ Follow these steps to elevate access for a Global Administrator using the Azure
4444

4545
1. Sign in to the [Azure portal](https://portal.azure.com) as a Global Administrator.
4646

47-
If you are using Microsoft Entra Privileged Identity Management, [activate your Global Administrator role assignment](../active-directory/privileged-identity-management/pim-how-to-activate-role.md).
47+
If you are using Microsoft Entra Privileged Identity Management, [activate your Global Administrator role assignment](/entra/id-governance/privileged-identity-management/pim-how-to-activate-role).
4848

49-
1. Open **Microsoft Entra ID**.
50-
51-
1. Under **Manage**, select **Properties**.
49+
1. Browse to **Microsoft Entra ID** > **Manage** > **Properties**.
5250

5351
![Select Properties for Microsoft Entra properties - screenshot](./media/elevate-access-global-admin/azure-active-directory-properties.png)
5452

5553
1. Under **Access management for Azure resources**, set the toggle to **Yes**.
5654

5755
![Access management for Azure resources - screenshot](./media/elevate-access-global-admin/aad-properties-global-admin-setting.png)
5856

59-
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 directory. This toggle is only available to users who are assigned the Global Administrator role in Microsoft Entra ID.
57+
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.
6058

61-
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 directory. You can view and manage only the Azure subscriptions and management groups to which you have been granted access.
59+
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.
6260

6361
> [!NOTE]
64-
> If you're using [Privileged Identity Management](../active-directory/privileged-identity-management/pim-configure.md), 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.
62+
> If you're using [Privileged Identity Management](/entra/id-governance/privileged-identity-management/pim-configure), 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.
6563
66-
1. Click **Save** to save your setting.
64+
1. Select **Save** to save your setting.
6765

6866
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.
6967

7068
1. Sign out and sign back in to refresh your access.
7169

72-
You should now have access to all subscriptions and management groups in your directory. When you view the Access control (IAM) pane, you'll notice that you have been assigned the User Access Administrator role at root scope.
70+
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.
7371

7472
![Subscription role assignments with root scope - screenshot](./media/elevate-access-global-admin/iam-root.png)
7573

7674
1. Make the changes you need to make at elevated access.
7775

78-
For information about assigning roles, see [Assign Azure roles using the Azure portal](role-assignments-portal.yml). If you are using Privileged Identity Management, see [Discover Azure resources to manage](../active-directory/privileged-identity-management/pim-resource-roles-discover-resources.md) or [Assign Azure resource roles](../active-directory/privileged-identity-management/pim-resource-roles-assign-roles.md).
76+
For information about assigning roles, see [Assign Azure roles using the Azure portal](role-assignments-portal.yml). If you are using Privileged Identity Management, see [Discover Azure resources to manage](/entra/id-governance/privileged-identity-management/pim-resource-roles-discover-resources) or [Assign Azure resource roles](/entra/id-governance/privileged-identity-management/pim-resource-roles-assign-roles).
7977

8078
1. Perform the steps in the following section to remove your elevated access.
8179

@@ -85,11 +83,11 @@ To remove the User Access Administrator role assignment at root scope (`/`), fol
8583

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

88-
1. In the navigation list, click **Microsoft Entra ID** and then click **Properties**.
86+
1. Browse to **Microsoft Entra ID** > **Manage** > **Properties**.
8987

9088
1. 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.
9189

92-
If you try to remove the User Access Administrator role assignment on the Access control (IAM) pane, 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.
90+
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.
9391

9492
![Remove role assignments with root scope](./media/elevate-access-global-admin/iam-root-remove.png)
9593

@@ -98,7 +96,7 @@ To remove the User Access Administrator role assignment at root scope (`/`), fol
9896
If you are using Privileged Identity Management, deactivate your Global Administrator role assignment.
9997

10098
> [!NOTE]
101-
> If you're using [Privileged Identity Management](../active-directory/privileged-identity-management/pim-configure.md), 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.
99+
> If you're using [Privileged Identity Management](/entra/id-governance/privileged-identity-management/pim-configure), 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.
102100
103101
# [PowerShell](#tab/powershell)
104102

@@ -291,17 +289,17 @@ When you call `elevateAccess`, you create a role assignment for yourself, so to
291289
292290
Save the ID from the `name` parameter, in this case `18d7d88d-d35e-4fb5-a5c3-7773c20a72d9`.
293291
294-
1. You also need to list the role assignment for the directory administrator at directory scope. List all assignments at directory scope for the `principalId` of the directory administrator who made the elevate access call. This will list all assignments in the directory for the objectid.
292+
1. 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.
295293
296294
```http
297295
GET https://management.azure.com/providers/Microsoft.Authorization/roleAssignments?api-version=2022-04-01&$filter=principalId+eq+'{objectid}'
298296
```
299297
300-
>[!NOTE]
301-
>A directory administrator should not have many assignments, if the previous query returns too many assignments, you can also query for all assignments just at directory scope level, then filter the results:
298+
> [!NOTE]
299+
> 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:
302300
> `GET https://management.azure.com/providers/Microsoft.Authorization/roleAssignments?api-version=2022-04-01&$filter=atScope()`
303301
304-
1. 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 directory administrator.
302+
1. 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.
305303
306304
Sample role assignment:
307305
@@ -337,6 +335,54 @@ When you call `elevateAccess`, you create a role assignment for yourself, so to
337335
338336
---
339337
338+
## View users with elevated access
339+
340+
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.
341+
342+
### Option 1
343+
344+
1. In the Azure portal, browse to **Microsoft Entra ID** > **Manage** > **Properties**.
345+
346+
1. Under **Access management for Azure resources**, look for the following banner.
347+
348+
`You have X users with elevated access. Microsoft Security recommends deleting access for users who have unnecessary elevated access. Manage elevated access users`
349+
350+
:::image type="content" source="./media/elevate-access-global-admin/elevated-access-users-banner.png" alt-text="Screenshot of banner that indicates there are users with elevated access." lightbox="./media/elevate-access-global-admin/elevated-access-users-banner.png":::
351+
352+
1. Select the **Manage elevated access users** link to view a list of users with elevated access.
353+
354+
### Option 2
355+
356+
1. In the Azure portal, browse to a subscription.
357+
358+
1. Select **Access control (IAM)**.
359+
360+
1. At the top of the page, look for the following banner.
361+
362+
`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`
363+
364+
:::image type="content" source="./media/elevate-access-global-admin/elevated-access-users-iam-banner.png" alt-text="Screenshot of banner on Access control (IAM) page that indicates there are users with elevated access." lightbox="./media/elevate-access-global-admin/elevated-access-users-iam-banner.png":::
365+
366+
1. Select the **View role assignments** link to view a list of users with elevated access.
367+
368+
## Remove elevated access for users
369+
370+
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.
371+
372+
1. Sign in to the [Azure portal](https://portal.azure.com) as a Global Administrator.
373+
374+
1. Browse to **Microsoft Entra ID** > **Manage** > **Properties**.
375+
376+
1. Under **Access management for Azure resources**, set the toggle to **Yes** as described earlier in [Step 1: Elevate access for a Global Administrator](#step-1-elevate-access-for-a-global-administrator).
377+
378+
1. Select the **Manage elevated access users** link.
379+
380+
The **Users with elevated access appears** pane appears with a list of users with elevated access in your tenant.
381+
382+
:::image type="content" source="./media/elevate-access-global-admin/elevated-access-users-pane.png" alt-text="Screenshot of Users with elevated access pane that lists users with elevated access." lightbox="./media/elevate-access-global-admin/elevated-access-users-pane.png":::
383+
384+
1. To remove elevated access for users, add a check mark next to the user and select **Remove**.
385+
340386
## View elevate access log entries in the Directory Activity logs
341387
342388
When access is elevated, an entry is added to the logs. As a Global Administrator in Microsoft Entra ID, you might want to check when access was elevated and who did it. Elevate access log entries do not appear in the standard activity logs, but instead appear in the Directory Activity logs. This section describes different ways that you can view the elevate access log entries.
@@ -345,7 +391,7 @@ When access is elevated, an entry is added to the logs. As a Global Administrato
345391
346392
1. Sign in to the [Azure portal](https://portal.azure.com) as a Global Administrator.
347393
348-
1. Open **Monitor** > **Activity log**.
394+
1. Browse to **Monitor** > **Activity log**.
349395
350396
1. Change the **Activity** list to **Directory Activity**.
351397
@@ -392,13 +438,13 @@ When access is elevated, an entry is added to the logs. As a Global Administrato
392438
393439
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.
394440
395-
1. Open **Microsoft Entra ID** > **Groups**.
441+
1. Browse to **Microsoft Entra ID** > **Groups**.
396442
397443
1. Create a new security group and note the group object ID.
398444
399445
1. Use the [az login](/cli/azure/reference-index#az-login) command to sign in as Global Administrator.
400446
401-
1. Use the [az role assignment create](/cli/azure/role/assignment#az-role-assignment-create) command to assign the [Reader](built-in-roles.md#reader) role to the group who can only read logs at the directory level, which are found at `Microsoft/Insights`.
447+
1. Use the [az role assignment create](/cli/azure/role/assignment#az-role-assignment-create) command to assign the [Reader](built-in-roles.md#reader) role to the group who can only read logs at the tenant level, which are found at `Microsoft/Insights`.
402448
403449
```azurecli
404450
az role assignment create --assignee "{groupId}" --role "Reader" --scope "/providers/Microsoft.Insights"
20.3 KB
Loading
45.4 KB
Loading
44.1 KB
Loading

0 commit comments

Comments
 (0)