Skip to content

Commit 1623c2a

Browse files
authored
Merge pull request #110939 from Samantha-Yu/adfupdate0410-2
Updated according to UI changes
2 parents 7369584 + 7e84886 commit 1623c2a

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed
-59.8 KB
Loading
11.5 KB
Loading
-171 KB
Loading

articles/data-factory/store-credentials-in-key-vault.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.workload: data-services
1111

1212

1313
ms.topic: conceptual
14-
ms.date: 01/16/2020
14+
ms.date: 04/13/2020
1515
ms.author: jingwang
1616
---
1717

@@ -30,7 +30,7 @@ This feature relies on the data factory managed identity. Learn how it works fro
3030
To reference a credential stored in Azure Key Vault, you need to:
3131

3232
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).
33-
2. **Grant the managed identity access to your Azure Key Vault.** In your key vault -> Access policies -> Add new -> search this managed identity to grant **Get** permission in Secret permissions dropdown. It allows this designated factory to access secret in key vault.
33+
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** permission in Secret permissions dropdown. It allows this designated factory to access secret in key vault.
3434
3. **Create a linked service pointing to your Azure Key Vault.** Refer to [Azure Key Vault linked service](#azure-key-vault-linked-service).
3535
4. **Create data store linked service, inside which reference the corresponding secret stored in key vault.** Refer to [reference secret stored in key vault](#reference-secret-stored-in-key-vault).
3636

@@ -45,13 +45,13 @@ The following properties are supported for Azure Key Vault linked service:
4545

4646
**Using authoring UI:**
4747

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

50-
![Search AKV](media/store-credentials-in-key-vault/search-akv.png)
50+
![Search Azure Key Vault](media/store-credentials-in-key-vault/search-akv.png)
5151

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

54-
![Configure AKV](media/store-credentials-in-key-vault/configure-akv.png)
54+
![Configure Azure Key Vault](media/store-credentials-in-key-vault/configure-akv.png)
5555

5656
**JSON example:**
5757

@@ -85,7 +85,7 @@ Select **Azure Key Vault** for secret fields while creating the connection to yo
8585
>[!TIP]
8686
>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.
8787
88-
![Configure AKV secret](media/store-credentials-in-key-vault/configure-akv-secret.png)
88+
![Configure Azure Key Vault secret](media/store-credentials-in-key-vault/configure-akv-secret.png)
8989

9090
**JSON example: (see the "password" section)**
9191

0 commit comments

Comments
 (0)