You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/data-factory/store-credentials-in-key-vault.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,8 +3,8 @@ title: Store credentials in Azure Key Vault
3
3
description: Learn how to store credentials for data stores used in an Azure Key Vault that Azure Data Factory can automatically retrieve at runtime.
4
4
author: nabhishek
5
5
ms.subservice: security
6
-
ms.topic: conceptual
7
-
ms.date: 02/13/2025
6
+
ms.topic: how-to
7
+
ms.date: 04/28/2025
8
8
ms.author: abnarain
9
9
---
10
10
@@ -25,9 +25,11 @@ This feature relies on the data factory managed identity. Learn how it works fro
25
25
To reference a credential stored in Azure Key Vault, you need to:
26
26
27
27
1.**Retrieve data factory managed identity** by copying the value of "Managed Identity Object ID" generated along with your factory. If you use ADF authoring UI, the managed identity object ID will be shown on the Azure Key Vault linked service creation window; you can also retrieve it from Azure portal, refer to [Retrieve data factory managed identity](data-factory-service-identity.md#retrieve-managed-identity).
28
-
2.**Grant the managed identity access to your Azure Key Vault.** In your key vault -> Access policies -> Add Access Policy, search this managed identity to grant **Get** and **List** permissions in the Secret permissions dropdown. It allows this designated factory to access secret in key vault.
29
-
3.**Create a linked service pointing to your Azure Key Vault.** Refer to [Azure Key Vault linked service](#azure-key-vault-linked-service).
30
-
4.**Create the data store linked service. In its configuration, reference the corresponding secret stored in Azure Key Vault.** Refer to [Reference a secret stored in Azure Key Vault](#reference-secret-stored-in-key-vault).
28
+
1.**Grant the managed identity access to your Azure Key Vault.** You can use either access policies or access control permissions:
29
+
1._Access policy_ - In your key vault select **Access policies** -> **Add access Policy** -> search for your Azure Data Factory managed identity and grant **Get** and **List** permissions in the Secret permissions dropdown.
30
+
1._Access control_ - In your key vault select **Access control (IAM)** -> **+ Add** -> **Add role assignment**. Select **Key Vault Secrets** user, and then select **Next**. Under **Members** select **Managed identity** then **Select members** and search for your Azure Data Factory managed identity. Then select **Review + assign**.
31
+
1.**Create a linked service pointing to your Azure Key Vault.** Refer to [Azure Key Vault linked service](#azure-key-vault-linked-service).
32
+
1.**Create the data store linked service. In its configuration, reference the corresponding secret stored in Azure Key Vault.** Refer to [Reference a secret stored in Azure Key Vault](#reference-secret-stored-in-key-vault).
31
33
32
34
## Azure Key Vault linked service
33
35
@@ -75,10 +77,10 @@ The following properties are supported when you configure a field in linked serv
75
77
76
78
**Using authoring UI:**
77
79
78
-
Select **Azure Key Vault** for secret fields while creating the connection to your data store/compute. Select the provisioned Azure Key Vault Linked Service and provide the **Secret name**. You can optionally provide a secret version as well.
80
+
Select **Azure Key Vault** for secret fields while creating the connection to your data store/compute. Select the provisioned Azure Key Vault Linked Service and provide the **Secret name**. You can optionally provide a secret version as well.
79
81
80
82
>[!TIP]
81
-
>For connectors using connection string in linked service like SQL Server, Blob storage, etc., you can choose either to store only the secret field e.g. password in AKV, or to store the entire connection string in AKV. You can find both options on the UI.
83
+
>For connectors using connection string in linked service like SQL Server, Blob storage, etc., you can choose either to store only the secret field. For example, password in AKV, or to store the entire connection string in AKV. You can find both options on the UI.
0 commit comments