Skip to content

Commit 34aee6a

Browse files
committed
Learn Editor: Update configure-customer-managed-key.md
1 parent c8bb6f9 commit 34aee6a

File tree

2 files changed

+20
-17
lines changed

2 files changed

+20
-17
lines changed

articles/service-bus-messaging/configure-customer-managed-key.md

Lines changed: 20 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -19,10 +19,12 @@ To enable customer-managed keys in the Azure portal, follow these steps:
1919

2020
1. Navigate to your Service Bus Premium namespace.
2121
2. On the **Settings** page of your Service Bus namespace, select **Encryption**.
22-
3. Select the **Customer-managed key encryption at rest** as shown in the following image.
23-
24-
![Enable customer managed key](./media/configure-customer-managed-key/enable-customer-managed-key.png)
22+
1. Select the **Customer-managed key encryption at rest** as shown in the following image.
2523

24+
![Enable customer managed key.](media/configure-customer-managed-key/enable-customer-managed-key.png)
25+
26+
27+
2628
> [!NOTE]
2729
> Currently you can't configure Azure Key Vault Managed HSM through the portal.
2830
@@ -62,25 +64,25 @@ After you enable customer-managed keys, you need to associate the customer manag
6264
```
6365
---
6466
65-
4. Create keys by following these steps:
66-
1. To create a new key, select **Generate/Import** from the **Keys** menu under **Settings**.
67-
68-
![Select Generate/Import button](./media/configure-customer-managed-key/select-generate-import.png)
69-
70-
1. Set **Options** to **Generate** and give the key a name.
71-
72-
![Create a key](./media/configure-customer-managed-key/create-key.png)
73-
74-
1. You can now select this key to associate with the Service Bus namespace for encrypting from the drop-down list.
75-
76-
![Select key from key vault](./media/configure-customer-managed-key/select-key-from-key-vault.png)
77-
> [!NOTE]
67+
1. Create keys by following these steps:
68+
1. To create a new key, select **Generate/Import** from the **Keys** menu under **Settings**.
69+
70+
![Select Generate/Import button](./media/configure-customer-managed-key/select-generate-import.png)
71+
72+
1. Set **Options** to **Generate** and give the key a name.
73+
74+
![Create a key](./media/configure-customer-managed-key/create-key.png)
75+
76+
1. You can now select this key to associate with the Service Bus namespace for encrypting from the drop-down list.
77+
78+
![Select key from key vault](./media/configure-customer-managed-key/select-key-from-key-vault.png)
79+
> [!NOTE]
7880
> For redundancy, you can add up to 3 keys. In the event that one of the keys has expired, or is not accessible, the other keys will be used for encryption.
7981
8082
1. Fill in the details for the key and click **Select**. This enables the encryption of the Microsoft-managed key with your key (customer-managed key).
8183
8284
83-
> [!IMPORTANT]
85+
> [!IMPORTANT]
8486
> If you are looking to use Customer managed key along with [Geo-Disaster Recovery](service-bus-geo-dr.md), please review this section.
8587
>
8688
> To enable encryption of Microsoft-managed key with a customer managed key, an [access policy](/azure/key-vault/general/security-features) is set up for the Service Bus' managed identity on the specified Azure KeyVault. This ensures controlled access to the Azure KeyVault from the Azure Service Bus namespace.
@@ -683,4 +685,5 @@ Use the [`resource__versionless_id` or `versionless_id`](https://registry.terraf
683685
## Next steps
684686
See the following articles:
685687
- [Service Bus overview](service-bus-messaging-overview.md)
688+
686689
- [Key Vault overview](/azure/key-vault/general/overview)
41.2 KB
Loading

0 commit comments

Comments
 (0)