Skip to content

Update how-to-use-azure-key-vault-secrets-pipeline-activities.md #126651

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update how-to-use-azure-key-vault-secrets-pipeline-activities.md #126651

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion articles/data-factory/how-to-use-azure-key-vault-secrets-pipeline-activities.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ This feature relies on the data factory managed identity. Learn how it works fr
Make a note of your secret URI that you want to get during your data factory pipeline run.

> [!CAUTION]
> The secret URI is structured like this: `{vaultBaseUrl}/secrets/{secret-name}/{secret-version}`. The _secret-version_ is optional; the latest version is returned when not specified. It is often desirable to specify a secret URI in a pipeline without a specific version so that the pipeline always uses the latest version of the secret.
> The secret URI is structured like this: `{vaultBaseUrl}/secrets/{secret-name}/{secret-version}?api-version=7.4`. The _secret-version_ is optional; the latest version is returned when not specified. It is often desirable to specify a secret URI in a pipeline without a specific version so that the pipeline always uses the latest version of the secret.

4. In your Data Factory pipeline, add a new Web activity and configure it as follows.

Expand Down