Skip to content

Commit 898ac9f

Browse files
authored
Merge pull request #101647 from orspod/2020-1-BYOK-docs
added message re: follower cluster/BYOK support
2 parents af8db12 + c982739 commit 898ac9f

File tree

3 files changed

+8
-6
lines changed

3 files changed

+8
-6
lines changed

articles/data-explorer/customer-managed-keys-csharp.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,8 @@ ms.date: 01/06/2020
1212
# Configure customer-managed-keys using C#
1313

1414
> [!div class="op_single_selector"]
15-
> * [C#](create-cluster-database-csharp.md)
16-
> * [Azure Resource Manager template](create-cluster-database-resource-manager.md)
15+
> * [C#](customer-managed-keys-csharp.md)
16+
> * [Azure Resource Manager template](customer-managed-keys-resource-manager.md)
1717
1818
[!INCLUDE [data-explorer-configure-customer-managed-keys](../../includes/data-explorer-configure-customer-managed-keys.md)]
1919

articles/data-explorer/customer-managed-keys-resource-manager.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,8 @@ ms.date: 01/06/2020
1212
# Configure customer-managed-keys using the Azure Resource Manager template
1313

1414
> [!div class="op_single_selector"]
15-
> * [C#](create-cluster-database-csharp.md)
16-
> * [Azure Resource Manager template](create-cluster-database-resource-manager.md)
15+
> * [C#](customer-managed-keys-csharp.md)
16+
> * [Azure Resource Manager template](customer-managed-keys-resource-manager.md)
1717
1818
[!INCLUDE [data-explorer-configure-customer-managed-keys](../../includes/data-explorer-configure-customer-managed-keys.md)]
1919

includes/data-explorer-configure-customer-managed-keys.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,10 @@ ms.author: orspodek
88

99
Azure Data Explorer encrypts all data in a storage account at rest. By default, data is encrypted with Microsoft-managed keys. For additional control over encryption keys, you can supply customer-managed keys to use for data encryption. Customer-managed keys must be stored in an [Azure Key Vault](/azure/key-vault/key-vault-overview). You can create your own keys and store them in a key vault, or you can use an Azure Key Vault API to generate keys. The Azure Data Explorer cluster and the key vault must be in the same region, but they can be in different subscriptions. For a detailed explanation on customer-managed keys, see [customer-managed keys with Azure Key Vault](/azure/storage/common/storage-service-encryption). This article shows you how to configure customer-managed keys.
1010

11-
> [!Note]
12-
> To configure customer-managed keys with Azure Data Explorer, you must [set two properties on the key vault](/azure/key-vault/key-vault-ovw-soft-delete): **Soft Delete** and **Do Not Purge**. These properties aren't enabled by default. To enable these properties, use [PowerShell](/azure/key-vault/key-vault-soft-delete-powershell) or [Azure CLI](/azure/key-vault/key-vault-soft-delete-cli). Only RSA keys and key size 2048 are supported.
11+
To configure customer-managed keys with Azure Data Explorer, you must [set two properties on the key vault](/azure/key-vault/key-vault-ovw-soft-delete): **Soft Delete** and **Do Not Purge**. These properties aren't enabled by default. To enable these properties, use [PowerShell](/azure/key-vault/key-vault-soft-delete-powershell) or [Azure CLI](/azure/key-vault/key-vault-soft-delete-cli). Only RSA keys and key size 2048 are supported.
12+
13+
> [!NOTE]
14+
> Data encryption using customer managed keys is not supported on [leader and follower clusters](/azure/data-explorer/follower).
1315
1416
## Assign an identity to the cluster
1517

0 commit comments

Comments
 (0)