Skip to content

Commit 6aa48a6

Browse files
authored
Describe approach for encrypting only certain properties of messages rather than everything
1 parent d31efc2 commit 6aa48a6

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

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

Lines changed: 3 additions & 1 deletion
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
To enable customer-managed keys in the Azure portal, follow these steps:
1921

@@ -683,4 +685,4 @@ 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)
686-
- [Key Vault overview](/azure/key-vault/general/overview)
688+
- [Key Vault overview](/azure/key-vault/general/overview)

0 commit comments

Comments
 (0)