You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/disks-cross-tenant-customer-managed-keys.md
+55-40Lines changed: 55 additions & 40 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to use customer-managed keys with your Azure disks in dif
4
4
author: roygara
5
5
ms.service: storage
6
6
ms.topic: how-to
7
-
ms.date: 11/11/2022
7
+
ms.date: 11/30/2022
8
8
ms.author: rogarana
9
9
ms.subservice: disks
10
10
---
@@ -29,13 +29,62 @@ If you have questions about cross-tenant customer-managed keys with managed disk
29
29
30
30
## Create a disk encryption set
31
31
32
-
Now that you've created your Azure Key Vault and performed the required Azure AD configurations, deploy a disk encryption set configured to work across tenants and associate it with a key in the key vault. You can do this using an ARM template, REST API, Azure PowerShell, or Azure CLI.
32
+
Now that you've created your Azure Key Vault and performed the required Azure AD configurations, deploy a disk encryption set configured to work across tenants and associate it with a key in the key vault. You can do this using the Azure portal, Azure PowerShell, or Azure CLI. You can also use an [ARM template](#use-an-arm-template) or [REST API](#use-rest-api).
33
33
34
-
# [ARM/REST](#tab/azure-portal)
34
+
# [Portal](#tab/azure-portal)
35
35
36
-
Use an ARM template or REST API.
36
+
To use the Azure portal, sign in to the portal and follow these steps.
37
37
38
-
### ARM
38
+
1. Select **+ Create a resource**, search for **Disk encryption set**, and select **Create > Disk encryption set**.
39
+
1. Under **Project details**, select the subscription and resource group in which to create the disk encryption set.
40
+
1. Under **Instance details**, provide a name for the disk encryption set.
41
+
42
+
:::image type="content" source="media/disks-cross-tenant-customer-managed-keys/create-disk-encryption-set.png" alt-text="Screenshot showing how to enter the project and instance details to create a new disk encryption set." border="true":::
43
+
44
+
1. Select the **Region** in which to create the disk encryption set.
45
+
1. For **Encryption type**, select **Encryption at-rest with a customer-managed key**.
46
+
1. Under **Encryption key**, select the **Enter key from URI** radio button, and then enter the Key URI of the key created in the customer's tenant.
47
+
1. Under **User-assigned identity**, select **Select an identity**.
48
+
1. Select the user-assigned managed identity that you created previously in the ISV's tenant, and then select **Add**.
49
+
1. Under **Multi-tenant application**, select **Select an application**.
50
+
1. Select the multi-tenant registered application that you created previously in the ISV's tenant, and click **Select**.
51
+
1. Select **Review + create**.
52
+
53
+
# [PowerShell](#tab/azure-powershell)
54
+
55
+
To use Azure PowerShell, install the latest Az module or the Az.Storage module. For more information about installing PowerShell, see [Install Azure PowerShell on Windows with PowerShellGet](/powershell/azure/install-Az-ps).
In the script below, `-FederatedClientId` should be the application ID (client ID) of the multi-tenant application. You'll also need to provide the subscription ID, resource group name, and identity name.
In the command below, `myAssignedId` should be the resource ID of the user-assigned managed identity that you created earlier, and `myFederatedClientId` should be the application ID (client ID) of the multi-tenant application.
@@ -92,7 +141,7 @@ Use an ARM template or REST API.
92
141
}
93
142
```
94
143
95
-
### REST API
144
+
### Use REST API
96
145
97
146
Use bearer token as authorization header and application/JSON as content type in BODY. (Network tab, filter to management.azure while performing any ARM request on portal.)
To use Azure PowerShell, install the latest Az module or the Az.Storage module. For more information about installing PowerShell, see [Install Azure PowerShell on Windows with PowerShellGet](/powershell/azure/install-Az-ps).
In the script below, `-FederatedClientId` should be the application ID (client ID) of the multi-tenant application. You'll also need to provide the subscription ID, resource group name, and identity name.
In the command below, `myAssignedId` should be the resource ID of the user-assigned managed identity that you created earlier, and `myFederatedClientId` should be the application ID (client ID) of the multi-tenant application.
0 commit comments