Skip to content

Commit 8d4a3a6

Browse files
authored
Update overview-storage-keys.md
1 parent 759bdef commit 8d4a3a6

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/key-vault/secrets/overview-storage-keys.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,9 @@ ms.custom: devx-track-azurecli
1717
> [!IMPORTANT]
1818
> Key Vault Managed Storage Account Keys (legacy) is supported as-is with no more updates planned. Only Account SAS are supported with SAS definitions signed storage service version no later than 2018-03-28.
1919
20+
> [!IMPORTANT]
21+
> Support for Managed Storage Account Keys in **Azure CLI was removed in version 2.54**, you must use **Azure CLI version 2.53.1 or former** for commands in this tutorial.
22+
2023
> [!IMPORTANT]
2124
> We recommend using Azure Storage integration with Microsoft Entra ID, Microsoft's cloud-based identity and access management service. Microsoft Entra integration is available for [Azure blobs, queues, and tables](../../storage/blobs/authorize-access-azure-active-directory.md), and provides OAuth2 token-based access to Azure Storage (just like Azure Key Vault).
2225
> Microsoft Entra ID allows you to authenticate your client application by using an application or user identity, instead of storage account credentials. You can use an [Microsoft Entra managed identity](../../active-directory/managed-identities-azure-resources/index.yml) when you run on Azure. Managed identities remove the need for client authentication and storing credentials in or with your application. Use below solution only when Microsoft Entra authentication is not possible.

0 commit comments

Comments
 (0)