# Azure Key Vault Credential Provider

The SailPoint Azure Key Vault Credential Provider provides credential cycling functionality to fetch refreshed credentials from Azure Key Vault for authenticating sources in the Credential Provider.

For information on creating a new Azure Key Vault credential provider, refer to [Adding a New Credential Provider in SailPoint](<https://documentation.sailpoint.com/connectors/credential_providers/azure_key_vault/help/config_new_cred_prov.html>).

## Prerequisites

Before you configure your credential provider, you must consider the following prerequisite items.

- You must configure an application in Azure that has the appropriate role assigned to it to interact with Azure Key Vault. For more information, refer to:

  - For authorization - [OAuth 2.0 client credentials grant](<https://learn.microsoft.com/en-us/entra/identity-platform/v2-oauth2-client-creds-grant-flow>).
  - For permissions - [Use an Azure RBAC for managing access](<https://learn.microsoft.com/en-us/azure/key-vault/general/rbac-guide?tabs=azure-cli>).

  > **Caution**
  >
  > The Azure Key Vault documentation referenced in this page is not managed by SailPoint, and is subject to change without notice.
- For VA-based Deep Governance connectors, the source and credential provider virtual appliances must be in the same cluster.
- VA-based Deep Governance connectors, SaaS-based Deep Governance, Discovery, and Quick Compliance connectors now support the use of credential providers.

## Supported Platforms

This credential provider supports the following platforms:

- Azure Key Vault

  > **Note**
  >
  > Supported API Version: 7.4 and onwards