Skip to content

Commit 956b736

Browse files
authored
Update setup-steps-for-extensible-key-management-using-the-azure-key-vault.md
1 parent 2e850f3 commit 956b736

1 file changed

Lines changed: 4 additions & 13 deletions

File tree

docs/relational-databases/security/encryption/setup-steps-for-extensible-key-management-using-the-azure-key-vault.md

Lines changed: 4 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Set up Transparent Data Encryption (TDE) Extensible Key Management with Azure Key Vault"
33
description: Install and configure the SQL Server Connector for Azure Key Vault.
44
ms.custom: seo-lt-2019
5-
ms.date: "06/11/2020"
5+
ms.date: "06/15/2020"
66
ms.prod: sql
77
ms.reviewer: vanto
88
ms.technology: security
@@ -89,11 +89,7 @@ To grant your SQL Server instance access permissions to your Azure key vault, yo
8989

9090
Select the method you want to use to create a key vault.
9191

92-
::: moniker range="azureportal"
93-
|||||
94-
|-|-|-|-|
95-
**_\*PowerShell \*_**   | [The Azure portal](setup-steps-for-extensible-key-management-using-the-azure-key-vault.md?view=azureportal)|||
96-
|||||
92+
## [Azure portal](#tab/portal)
9793

9894
### Create a key vault by using the Azure portal
9995

@@ -145,12 +141,7 @@ You can use the Azure portal to create the key vault and then add an Azure AD pr
145141

146142
![Screenshot of the Save button on the "Add access policy" pane](../../../relational-databases/security/encryption/media/ekm/ekm-part2-save-access-policy.png)
147143

148-
::: moniker-end
149-
::: moniker range="powershell"
150-
|||||
151-
|-|-|-|-|
152-
[PowerShell](setup-steps-for-extensible-key-management-using-the-azure-key-vault.md?view=powershell) |**_\* The Azure portal \*_**  |
153-
|||||
144+
## [PowerShell](#tab/powershell)
154145

155146
### Create a key vault and key by using PowerShell
156147

@@ -330,7 +321,7 @@ Id : https://contosoekmkeyvault.vault.azure.net:443/
330321
> [!IMPORTANT]
331322
> The key vault supports multiple versions of the same named key, but keys to be used by the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Connector should not be versioned or rolled. If the administrator wants to roll the key that's used for [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] encryption, a new key with a different name should be created in the key vault and used to encrypt the DEK.
332323
333-
::: moniker-end
324+
---
334325
335326
## Step 3: Install the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Connector
336327

0 commit comments

Comments
 (0)