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/service-bus-messaging/configure-customer-managed-key.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,13 @@ You can use Azure Key Vault (including Azure Key Vault Managed Hardware Security
16
16
17
17
If you only need to encrypt certain properties of your messages, consider using a library like [NServiceBus](https://docs.particular.net/nservicebus/security/property-encryption).
18
18
19
+
> [!NOTE]
20
+
> A customer-managed keys for is considered disabled in the following scenarios:
21
+
> - Revoking access: If Service Bus no longer has permission to access the key in Azure Key Vault.
22
+
> - Disabling the key: Manually disabling the key in Key Vault renders it unusable.
23
+
> - Letting the key expire: If the key reaches its expiration date without renewal. Letting a key expire has the same effect as revoking or disabling it. Always rotate or renew keys before they expire to avoid unintended outages.
24
+
> - Deleting the key: Once deleted, the key is permanently inaccessible.
25
+
19
26
## Enable customer-managed keys (Azure portal)
20
27
21
28
To enable customer-managed keys in the Azure portal, follow these steps:
0 commit comments