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
1. Set **Options** to **Generate** and give the key a name.
73
+
74
+

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
+

79
+
> [!NOTE]
78
80
> 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.
79
81
80
82
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).
81
83
82
84
83
-
> [!IMPORTANT]
85
+
> [!IMPORTANT]
84
86
> If you are looking to use Customer managed key along with [Geo-Disaster Recovery](service-bus-geo-dr.md), please review this section.
85
87
>
86
88
> 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
683
685
## Next steps
684
686
See the following articles:
685
687
-[Service Bus overview](service-bus-messaging-overview.md)
0 commit comments