Skip to content

Commit 465bbbd

Browse files
authored
Merge pull request #288207 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents 75454c1 + 90f845d commit 465bbbd

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ There are some caveats to the customer managed key for service side encryption.
1414

1515
You can use Azure Key Vault (including Azure Key Vault Managed HSM) to manage your keys and audit your key usage. You can either create your own keys and store them in a key vault, or you can use the Azure Key Vault APIs to generate keys. For more information about Azure Key Vault, see [What is Azure Key Vault?](/azure/key-vault/general/overview)
1616

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) for that.
18+
1719
## Enable customer-managed keys (Azure portal)
1820

1921
To enable customer-managed keys in the Azure portal, follow these steps:

0 commit comments

Comments
 (0)