Skip to content

Commit 132757b

Browse files
authored
Merge pull request #126373 from Sudeshna190287/patch-5
Update configure-customer-managed-key.md
2 parents 6e17924 + ffe2bb4 commit 132757b

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
@@ -616,7 +616,9 @@ If you require a higher level of assurance that your data is secure, you can ena
616616

617617
When infrastructure encryption is enabled, data in the Azure Service Bus is encrypted twice, once at the service level and once at the infrastructure level, using two different encryption algorithms and two different keys. Hence, infrastructure encryption of Azure Service Bus data protects against a scenario where one of the encryption algorithms or keys can be compromised.
618618

619-
You can enable infrastructure encryption by updating the Azure Resource Manager template with `requireInfrastructureEncryption` property in the **UpdateServiceBusNamespaceWithEncryption.json** as shown in the following example.
619+
Also, infrastructure encryption can be enabled only while switching from "Microsoft-managed key" to "Customer-managed key".
620+
621+
You can enable infrastructure encryption later even by updating the Azure Resource Manager template with `requireInfrastructureEncryption` property in the **UpdateServiceBusNamespaceWithEncryption.json** as shown in the following example.
620622

621623
```json
622624
"properties":{

0 commit comments

Comments
 (0)