Skip to content

Commit 7450827

Browse files
committed
edit pass: event-hubs-articles-batch1
1 parent fd8d7dd commit 7450827

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/event-hubs/event-hubs-premium-overview.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,9 @@ The Premium tier is a multitenant offering, so it can dynamically scale more fle
4747

4848
## Encryption of events
4949

50-
Event Hubs provides encryption of data at rest with Azure Storage Service Encryption. The Event Hubs service uses Azure Storage to store the data. All the data that's stored with Azure Storage is encrypted by using Microsoft-managed keys. If you use your own key (also referred to as Bring Your Own Key [BYOK] or customer-managed key), the data is still encrypted by using the Microsoft-managed key. In addition, the Microsoft-managed key is encrypted by using the customer-managed key. This feature enables you to create, rotate, disable, and revoke access to customer-managed keys that are used for encrypting Microsoft-managed keys. Enabling the BYOK feature is a one-time setup process on your namespace. For more information, see [Configure customer-managed keys for encrypting Azure Event Hubs data at rest](configure-customer-managed-key.md).
50+
Event Hubs provides encryption of data at rest with Azure Storage Service Encryption. The Event Hubs service uses Azure Storage to store the data. All the data that's stored with Azure Storage is encrypted by using Microsoft-managed keys. If you use your own key (also referred to as Bring Your Own Key [BYOK] or customer-managed key), the data is still encrypted by using the Microsoft-managed key.
51+
52+
In addition, the Microsoft-managed key is encrypted by using the customer-managed key. This feature enables you to create, rotate, disable, and revoke access to customer-managed keys that are used for encrypting Microsoft-managed keys. Enabling the BYOK feature is a one-time setup process on your namespace. For more information, see [Configure customer-managed keys for encrypting Azure Event Hubs data at rest](configure-customer-managed-key.md).
5153

5254
> [!NOTE]
5355
> All Event Hubs namespaces enabled for the Apache Kafka RPC protocol by default can be used by your existing Kafka-based applications. Having Kafka enabled on your cluster doesn't affect your non-Kafka use cases. There's no option or need to disable Kafka on a cluster.

0 commit comments

Comments
 (0)