Skip to content

Commit c719920

Browse files
authored
Document Global Administrator exception
1 parent 2ec3cdc commit c719920

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/key-vault/managed-hsm/access-control.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ tags: azure-resource-manager
88
ms.service: key-vault
99
ms.subservice: managed-hsm
1010
ms.topic: conceptual
11-
ms.date: 01/04/2023
11+
ms.date: 01/26/2023
1212
ms.author: mbaldwin
1313
# Customer intent: As the admin for managed HSMs, I want to set access policies and configure the Managed HSM, so that I can ensure it's secure and auditors can properly monitor all activities for these managed HSMs.
1414
---
@@ -35,7 +35,7 @@ When a managed HSM is created, the requestor also provides a list of data plane
3535
Permission model for both planes uses the same syntax, but they're enforced at different levels and role assignments use different scopes. Management plane Azure RBAC is enforced by Azure Resource Manager while data plane Managed HSM local RBAC is enforced by managed HSM itself.
3636

3737
> [!IMPORTANT]
38-
> Granting a security principal management plane access to an managed HSM does not grant them any access to data plane to access keys or data plane role assignments Managed HSM local RBAC). This isolation is by design to prevent inadvertent expansion of privileges affecting access to keys stored in Managed HSM.
38+
> Granting a security principal management plane access to an managed HSM does not grant them any access to data plane to access keys or data plane role assignments Managed HSM local RBAC). This isolation is by design to prevent inadvertent expansion of privileges affecting access to keys stored in Managed HSM. The one exception is members of Azure Active Directory Global Administrator role are implicitly part of the Managed HSM Administrator role for recovery purposes in scenarios where there are no longer any valid Managed HSM administrator accounts. Follow [Azure Active Directory best practices for securing the Global Adminstrator role](../../active-directory/roles/best-practices.md#5-limit-the-number-of-global-administrators-to-less-than-5).
3939
4040
For example, a subscription administrator (since they have "Contributor" permission to all resources in the subscription) can delete an managed HSM in their subscription, but if they don't have data plane access specifically granted through Managed HSM local RBAC, they can't gain access to keys or manage role assignment in the managed HSM to grant themselves or others access to data plane.
4141

@@ -87,4 +87,4 @@ You grant a security principal access to execute specific key operations by assi
8787

8888
- For a getting-started tutorial for an administrator, see [What is Managed HSM?](overview.md)
8989
- For a role management tutorial, see [Managed HSM local RBAC](role-management.md)
90-
- For more information about usage logging for Managed HSM logging, see [Managed HSM logging](logging.md)
90+
- For more information about usage logging for Managed HSM logging, see [Managed HSM logging](logging.md)

0 commit comments

Comments
 (0)