Skip to content

Commit 3497d6d

Browse files
Merge pull request #26701 from MicrosoftDocs/VanMSFT-patch-1
removing incorrect info per PG
2 parents c9669e0 + 03ecceb commit 3497d6d

1 file changed

Lines changed: 1 addition & 2 deletions

File tree

azure-sql/database/transparent-data-encryption-byok-identity.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Bring Your Own Key (BYOK) support for transparent data encryption (
44
author: GithubMirek
55
ms.author: mireks
66
ms.reviewer: vanto
7-
ms.date: 11/22/2022
7+
ms.date: 04/11/2023
88
ms.service: sql-db-mi
99
ms.subservice: security
1010
ms.topic: conceptual
@@ -57,7 +57,6 @@ In addition to the system-assigned managed identity that is already supported fo
5757
- `The managed identity with ID '/subscriptions/subsriptionID/resourcegroups/resource_name/providers/Microsoft.ManagedIdentity/userAssignedIdentities/umi_name' requires the following Azure Key Vault permissions: 'Get, WrapKey, UnwrapKey' to the key 'https://keyvault_name/keys/key_name'. Please grant the missing permissions to the identity. (https://aka.ms/sqltdebyokcreateserver).`
5858
- If you get the above error, check if the key vault is behind a virtual network or firewall, and make sure the option **Allow Trusted Microsoft Services to bypass this firewall** is enabled.
5959
- The **Allow Trusted Microsoft Services to bypass this firewall** option is currently not available in [National clouds](/azure/active-directory/develop/authentication-national-cloud).
60-
- A system-assigned managed identity can be used without the option to **Allow Trusted Microsoft Services to bypass this firewall** enabled. For more information, see [Configure Azure Key Vault firewalls and virtual networks](/azure/key-vault/general/network-security).
6160
- User Assigned Managed Identity for SQL Managed Instance is currently not supported when AKV firewall is enabled.
6261
- When multiple user-assigned managed identities are assigned to the server or managed instance, if a single identity is removed from the server using the *Identity* blade of the Azure portal, the operation succeeds but the identity doesn't get removed from the server. Removing all user-assigned managed identities together from the Azure portal works successfully.
6362
- When the server or managed instance is configured with customer-managed TDE and both system-assigned and user-assigned managed identities are enabled on the server, removing the user-assigned managed identities from the server without first giving the system-assigned managed identity access to the key vault results in an *Unexpected error occurred* message. Ensure the system-assigned managed identity has been provided key vault access prior to removing the primary user-assigned managed identity (and any other user-assigned managed identities) from the server.

0 commit comments

Comments
 (0)