Skip to content

Commit 8c961db

Browse files
EldertGrootenboerMSEldertGrootenboerMS
committed
Styling fixes
1 parent 6d102b5 commit 8c961db

File tree

1 file changed

+106
-106
lines changed

1 file changed

+106
-106
lines changed

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

Lines changed: 106 additions & 106 deletions
Original file line numberDiff line numberDiff line change
@@ -37,33 +37,33 @@ After you enable customer-managed keys, you need to associate the customer manag
3737
3838
# [Key Vault](#tab/Key-Vault)
3939

40-
1. To turn on both soft delete and purge protection when creating a vault, use the [az keyvault create](/cli/azure/keyvault#az-keyvault-create) command.
40+
2. To turn on both soft delete and purge protection when creating a vault, use the [az keyvault create](/cli/azure/keyvault#az-keyvault-create) command.
4141

4242
```azurecli-interactive
4343
az keyvault create --name contoso-SB-BYOK-keyvault --resource-group ContosoRG --location westus --enable-soft-delete true --enable-purge-protection true
4444
```
45-
1. To add purge protection to an existing vault (that already has soft delete enabled), use the [az keyvault update](/cli/azure/keyvault#az-keyvault-update) command.
45+
3. To add purge protection to an existing vault (that already has soft delete enabled), use the [az keyvault update](/cli/azure/keyvault#az-keyvault-update) command.
4646
4747
```azurecli-interactive
4848
az keyvault update --name contoso-SB-BYOK-keyvault --resource-group ContosoRG --enable-purge-protection true
4949
```
5050
5151
# [Key Vault Managed HSM](#tab/Key-Vault-Managed-HSM)
5252
53-
1. To turn on both soft delete and purge protection when creating a vault, use the [az keyvault create](/cli/azure/keyvault#az-keyvault-create) command.
53+
2. To turn on both soft delete and purge protection when creating a vault, use the [az keyvault create](/cli/azure/keyvault#az-keyvault-create) command.
5454
5555
```azurecli-interactive
5656
az keyvault create --hsm-name contoso-SB-BYOK-keyvault --resource-group ContosoRG --location westus --enable-soft-delete true --enable-purge-protection true
5757
```
58-
1. To add purge protection to an existing vault (that already has soft delete enabled), use the [az keyvault update](/cli/azure/keyvault#az-keyvault-update) command.
58+
3. To add purge protection to an existing vault (that already has soft delete enabled), use the [az keyvault update](/cli/azure/keyvault#az-keyvault-update) command.
5959
6060
```azurecli-interactive
6161
az keyvault update --hsm-name contoso-SB-BYOK-keyvault --resource-group ContosoRG --enable-purge-protection true
6262
```
6363
6464
---
6565
66-
1. Create keys by following these steps:
66+
4. Create keys by following these steps:
6767
1. To create a new key, select **Generate/Import** from the **Keys** menu under **Settings**.
6868
6969
![Select Generate/Import button](./media/configure-customer-managed-key/select-generate-import.png)
@@ -287,49 +287,49 @@ In this step, you update the Service Bus namespace with key vault information.
287287
288288
# [Key Vault](#tab/Key-Vault)
289289
290-
```json
291-
{
292-
"$schema":"https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
293-
"contentVersion":"1.0.0.0",
294-
"parameters":{
295-
"namespaceName":{
296-
"value":"<ServiceBusNamespaceName>"
297-
},
298-
"location":{
299-
"value":"<Location>"
300-
},
301-
"keyName":{
302-
"value":"<KeyName>"
303-
},
304-
"keyVaultUri":{
305-
"value":"https://<KeyVaultName>.vault.azure.net"
306-
}
307-
}
308-
}
309-
```
290+
```json
291+
{
292+
"$schema":"https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
293+
"contentVersion":"1.0.0.0",
294+
"parameters":{
295+
"namespaceName":{
296+
"value":"<ServiceBusNamespaceName>"
297+
},
298+
"location":{
299+
"value":"<Location>"
300+
},
301+
"keyName":{
302+
"value":"<KeyName>"
303+
},
304+
"keyVaultUri":{
305+
"value":"https://<KeyVaultName>.vault.azure.net"
306+
}
307+
}
308+
}
309+
```
310310

311311
# [Key Vault Managed HSM](#tab/Key-Vault-Managed-HSM)
312312

313-
```json
314-
{
315-
"$schema":"https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
316-
"contentVersion":"1.0.0.0",
317-
"parameters":{
318-
"namespaceName":{
319-
"value":"<ServiceBusNamespaceName>"
320-
},
321-
"location":{
322-
"value":"<Location>"
323-
},
324-
"keyName":{
325-
"value":"<KeyName>"
326-
},
327-
"keyVaultUri":{
328-
"value":"https://<KeyVaultName>.managedhsm.azure.net"
329-
}
330-
}
331-
}
332-
```
313+
```json
314+
{
315+
"$schema":"https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
316+
"contentVersion":"1.0.0.0",
317+
"parameters":{
318+
"namespaceName":{
319+
"value":"<ServiceBusNamespaceName>"
320+
},
321+
"location":{
322+
"value":"<Location>"
323+
},
324+
"keyName":{
325+
"value":"<KeyName>"
326+
},
327+
"keyVaultUri":{
328+
"value":"https://<KeyVaultName>.managedhsm.azure.net"
329+
}
330+
}
331+
}
332+
```
333333

334334
---
335335

@@ -478,73 +478,73 @@ This section gives you an example that shows you how to do the following tasks u
478478
479479
# [Key Vault](#tab/Key-Vault)
480480
481-
```json
482-
{
483-
"$schema":"https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
484-
"contentVersion":"1.0.0.0",
485-
"parameters":{
486-
"namespaceName":{
487-
"value":"<ServiceBusNamespaceName>"
488-
},
489-
"location":{
490-
"value":"<Location>"
491-
},
492-
"keyVaultUri":{
493-
"value":"https://<KeyVaultName>.vault.azure.net"
494-
},
495-
"keyName":{
496-
"value":"<KeyName>"
497-
},
498-
"identity": {
499-
"value": {
500-
"userAssignedIdentity": "/subscriptions/<AZURE SUBSCRIPTION ID>/resourceGroups/<RESOURCE GROUP NAME>/providers/Microsoft.ManagedIdentity/userAssignedIdentities/<USER MANAGED IDENTITY NAME>"
501-
}
502-
}
503-
}
504-
}
505-
```
481+
```json
482+
{
483+
"$schema":"https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
484+
"contentVersion":"1.0.0.0",
485+
"parameters":{
486+
"namespaceName":{
487+
"value":"<ServiceBusNamespaceName>"
488+
},
489+
"location":{
490+
"value":"<Location>"
491+
},
492+
"keyVaultUri":{
493+
"value":"https://<KeyVaultName>.vault.azure.net"
494+
},
495+
"keyName":{
496+
"value":"<KeyName>"
497+
},
498+
"identity": {
499+
"value": {
500+
"userAssignedIdentity": "/subscriptions/<AZURE SUBSCRIPTION ID>/resourceGroups/<RESOURCE GROUP NAME>/providers/Microsoft.ManagedIdentity/userAssignedIdentities/<USER MANAGED IDENTITY NAME>"
501+
}
502+
}
503+
}
504+
}
505+
```
506506

507507
# [Key Vault Managed HSM](#tab/Key-Vault-Managed-HSM)
508508

509-
```json
510-
{
511-
"$schema":"https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
512-
"contentVersion":"1.0.0.0",
513-
"parameters":{
514-
"namespaceName":{
515-
"value":"<ServiceBusNamespaceName>"
516-
},
517-
"location":{
518-
"value":"<Location>"
519-
},
520-
"keyVaultUri":{
521-
"value":"https://<KeyVaultName>.managedhsm.azure.net"
522-
},
523-
"keyName":{
524-
"value":"<KeyName>"
525-
},
526-
"identity": {
527-
"value": {
528-
"userAssignedIdentity": "/subscriptions/<AZURE SUBSCRIPTION ID>/resourceGroups/<RESOURCE GROUP NAME>/providers/Microsoft.ManagedIdentity/userAssignedIdentities/<USER MANAGED IDENTITY NAME>"
529-
}
530-
}
531-
}
532-
}
533-
```
509+
```json
510+
{
511+
"$schema":"https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
512+
"contentVersion":"1.0.0.0",
513+
"parameters":{
514+
"namespaceName":{
515+
"value":"<ServiceBusNamespaceName>"
516+
},
517+
"location":{
518+
"value":"<Location>"
519+
},
520+
"keyVaultUri":{
521+
"value":"https://<KeyVaultName>.managedhsm.azure.net"
522+
},
523+
"keyName":{
524+
"value":"<KeyName>"
525+
},
526+
"identity": {
527+
"value": {
528+
"userAssignedIdentity": "/subscriptions/<AZURE SUBSCRIPTION ID>/resourceGroups/<RESOURCE GROUP NAME>/providers/Microsoft.ManagedIdentity/userAssignedIdentities/<USER MANAGED IDENTITY NAME>"
529+
}
530+
}
531+
}
532+
}
533+
```
534534

535535
---
536536

537-
In the parameter file, replace placeholders with appropriate values.
538-
539-
| Placeholder | value |
540-
| ----------- | ----- |
541-
| `<ServiceBusNamespaceName>` | Name of the Service Bus namespace. |
542-
| `<Location>` | Location where you want the namespace to be created. |
543-
| `<KeyVaultName>` | Name of the key vault. |
544-
| `<KeyName>` | Name of the key in the key vault. |
545-
| `<AZURE SUBSCRIPTION ID>` | Your Azure subscription ID. |
546-
| `<RESOURCE GROUP NAME>` | Resource group of the user-managed identity. |
547-
| `<USER MANAGED IDENTITY NAME>` | Name of the user-managed identity. |
537+
In the parameter file, replace placeholders with appropriate values.
538+
539+
| Placeholder | value |
540+
| ----------- | ----- |
541+
| `<ServiceBusNamespaceName>` | Name of the Service Bus namespace. |
542+
| `<Location>` | Location where you want the namespace to be created. |
543+
| `<KeyVaultName>` | Name of the key vault. |
544+
| `<KeyName>` | Name of the key in the key vault. |
545+
| `<AZURE SUBSCRIPTION ID>` | Your Azure subscription ID. |
546+
| `<RESOURCE GROUP NAME>` | Resource group of the user-managed identity. |
547+
| `<USER MANAGED IDENTITY NAME>` | Name of the user-managed identity. |
548548

549549
3. Run the following PowerShell command to deploy the Resource Manager template. Replace `{MyRG}` with the name of your resource group before running the command.
550550

0 commit comments

Comments
 (0)