---
schema_version: "1"
id: 8eed2360f231ec06442b1e614372496d726e2b994694bae65c8f38df028791b4
title: Azure Key Vault Connector 1.2
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/azure-key-vault-connector/latest/index.md
canonical_url: https://docs.mulesoft.com/azure-key-vault-connector/latest/
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 93c98e70b3a80c593a6197b1b943584573daa7793eec1800be0ae4d1da40a583
description: MuleSoft Documentation Site
release: "1.2"
latest: true
---
---
product: Azure Key Vault Connector
version: 1.2
is-latest-version: true
---

# Azure Key Vault Connector 1.2

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Azure Key Vault (Azure Key Vault Connector) enables you to retrieve secrets,
keys, or certificates, and encrypt or decrypt content.

For information about compatibility and fixed issues, refer to the Azure Key Vault Connector Release
Notes.

## Before You Begin

To use this connector, you must be familiar with:

- The Azure Key Vault Secrets API

- Anypoint Connectors

- Mule runtime engine (Mule)

- Elements and global elements in a Mule flow

- How to create a Mule app using Anypoint Studio

Before creating an app, you must have:

- Credentials to access the Azure Key Vault target resource

- Anypoint Platform

- Anypoint Studio or Anypoint Code Builder

## Common Use Cases for the Connector

Some common use cases for Azure Key Vault Connector include:

- Authenticating to Azure Key Vault via Client Secret Credential to access Key Vault secrets without
  exposing sensitive credentials in code, thus improving resilience and security

- Enabling other applications in a Mule flow to have access to encrypt and decrypt operations using
  Azure Key Vault keys to avoid key rotations

- Authenticating to other database and HTTP connectors in a more secure and automated way to fetch
  and use credentials to access other endpoints

- Retrieving a certificate and saving the certificate into a file

## Connection Types

Azure Key Vault connections use the Connection authentication type, which uses a client ID, client
secret, and cryptography client cache.

## Environment Variables

When setting **Use Azure Default Credential** to `True`, you must set one of the following
environment variables `AZURE_CLIENT_ID`, `AZURE_CLIENT_SECRET`, or `AZURE_TENANT_ID`. Refer to
[Setting environment variables](https://docs.mulesoft.com/mule-runtime/latest/setting-environment-variables)
documentation for details.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Use Exchange to Discover Connectors, Templates, and Examples](https://docs.mulesoft.com/connectors/introduction/intro-use-exchange)

- [Azure Key Vault Connector Reference](https://docs.mulesoft.com/azure-key-vault-connector/latest/azure-key-vault-connector-reference)

- [Salesforce Help](https://help.salesforce.com)