Skip to content

Commit dce60c6

Browse files
authored
Merge pull request #224308 from msmbaldwin/ade-misc
Allow key management operations through ARM
2 parents 652544a + b342191 commit dce60c6

File tree

2 files changed

+40
-0
lines changed

2 files changed

+40
-0
lines changed
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
title: Allow key management operations through Azure Resource Manager
3+
description: Learn how to allow key management operations through ARM
4+
services: key-vault
5+
author: mbaldwin
6+
tags: azure-resource-manager
7+
8+
ms.service: key-vault
9+
ms.subservice: managed-hsm
10+
ms.topic: tutorial
11+
ms.date: 11/14/2022
12+
ms.author: mbaldwin
13+
14+
# Customer intent: As a managed HSM administrator, I want to authorize Azure Resource Manager to perform key management operations via Azure Managed HSM
15+
---
16+
17+
# Allow key management operations through Azure Resource Manager
18+
19+
For many asynchronous operations in the Portal and Template deployments, Azure Resource Manager must be trusted to act on behalf of users. Azure Key Vault trusts Azure Resource Manager but, for many higher assurance environments, such trust in the Azure portal and Azure Resource Manager may be considered a risk.
20+
21+
Azure Managed HSM doesn't trust Azure Resource Manager by default. However, for environments where such risk is an acceptable tradeoff for the ease of use of the Azure portal and template deployments, Managed HSM offers a way for an administrator to opt in to this trust.
22+
23+
For the Azure portal or Azure Resource Manager to interact with Azure Managed HSM in the same way as Azure Key Vault Standard and Premium, an authorized Managed HSM administrator must allow Azure Resource Manager to act on behalf of the user. To change this behavior and allow users to use Azure portal or Azure Resource Manager to create new keys or list keys, make the following Azure Managed HSM setting update:
24+
25+
```azurecli-interactive
26+
az rest --method PATCH --url "https://<managed-hsm-url>/settings/AllowKeyManagementOperationsThroughARM" --body "{\"value\":\"true\"}" --headers "Content-Type=application/json" --resource "https://managedhsm.azure.net"
27+
```
28+
29+
To disable this trust and revert to the default behavior of Managed HSM:
30+
31+
```azurecli-interactive
32+
az rest --method PATCH --url "https://<managed-hsm-url>/settings/AllowKeyManagementOperationsThroughARM" --body "{\"value\":\"false\"}" --headers "Content-Type=application/json" --resource "https://managedhsm.azure.net"
33+
```
34+
35+
## Next steps
36+
37+
- [Control your data with Managed HSM](mhsm-control-data.md)
38+
- [Azure Managed HSM access control](access-control.md)

articles/key-vault/managed-hsm/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,8 @@ items:
4747
href: multi-region-replication.md
4848
- name: Integrate Managed HSM with Azure Policy
4949
href: azure-policy.md
50+
- name: Authorize Azure Resource Manager
51+
href: authorize-azure-resource-manager.md
5052

5153
- name: Concepts
5254
items:

0 commit comments

Comments
 (0)