Store credentials in Azure Key Vault - Azure Data Factory (2024)

APPLIES TO: Azure Data Factory Azure Synapse Analytics

You can store credentials for data stores and computes in an Azure Key Vault. Azure Data Factory retrieves the credentials when executing an activity that uses the data store/compute.

Currently, all activity types except custom activity support this feature. For connector configuration specifically, check the "linked service properties" section in each connector topic for details.

Prerequisites

This feature relies on the data factory managed identity. Learn how it works from Managed identity for Data factory and make sure your data factory have an associated one.

Steps

To reference a credential stored in Azure Key Vault, you need to:

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.
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.
3. Create a linked service pointing to your Azure Key Vault. Refer to Azure Key Vault linked service.
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.

Azure Key Vault linked service

The following properties are supported for Azure Key Vault linked service:

Using authoring UI:

Select Connections -> Linked Services -> New. In New linked service, search for and select "Azure Key Vault":

Select the provisioned Azure Key Vault where your credentials are stored. You can do Test Connection to make sure your AKV connection is valid.

JSON example:

{ "name": "AzureKeyVaultLinkedService", "properties": { "type": "AzureKeyVault", "typeProperties": { "baseUrl": "https://<azureKeyVaultName>.vault.azure.net" } }}

Reference secret stored in key vault

The following properties are supported when you configure a field in linked service referencing a key vault secret:

Using authoring UI:

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.

JSON example: (see the "password" section)

{ "name": "DynamicsLinkedService", "properties": { "type": "Dynamics", "typeProperties": { "deploymentType": "<>", "organizationName": "<>", "authenticationType": "<>", "username": "<>", "password": { "type": "AzureKeyVaultSecret", "secretName": "<secret name in AKV>", "store":{ "referenceName": "<Azure Key Vault linked service>", "type": "LinkedServiceReference" } } } }}

Related content

For a list of data stores supported as sources and sinks by the copy activity in Azure Data Factory, see supported data stores.