> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/platform/variables/azure-key-vault-vaults.md).

# Azure Key Vault vaults

Register Azure Key Vault as a first-class secret vault in PowerShell Universal for secret variables and credentials.

PowerShell Universal can register Azure Key Vault as a first-class secret vault. Registered vaults are managed in-process, appear in vault selectors for secret variables and credentials, and are stored in `.universal/secretVaults.ps1`.

## Create a vault

1. Go to **Manage > Variables & Secrets > Vaults** and select **Create**.
2. Enter a vault name and its Azure Key Vault URI, such as `https://production.vault.azure.net/`.
3. Select an authentication method and supply its required values.
4. Save the vault, then select it when creating a secret variable or credential.

Existing SecretManagement registrations remain available, but are list-only on the Vaults page. Use this flow for new Azure Key Vault registrations.

## Authentication methods

| Method           | Configuration                                                                                                                                                                                  |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Default          | Uses `DefaultAzureCredential` from the host environment.                                                                                                                                       |
| Managed identity | Uses the system-assigned managed identity by default. Provide a managed identity client ID for a user-assigned identity.                                                                       |
| Client secret    | Provide the Entra tenant ID, application client ID, and the name of a PSU secret variable that stores the application client secret. The secret value is not stored in the vault registration. |

## Use PowerShell

Create a registration that uses the system-assigned managed identity:

```powershell
New-PSUSecretVault -Name 'Production Key Vault' `
    -VaultUri 'https://production.vault.azure.net/' `
    -AuthenticationType ManagedIdentity
```

Create a registration that uses an Entra application registration:

```powershell
New-PSUSecretVault -Name 'Customer Key Vault' `
    -VaultUri 'https://customer.vault.azure.net/' `
    -AuthenticationType ClientSecret `
    -TenantId '00000000-0000-0000-0000-000000000000' `
    -ClientId '11111111-1111-1111-1111-111111111111' `
    -ClientSecretVariable 'AzureKeyVaultClientSecret'
```

Use `Get-PSUSecretVault`, `Set-PSUSecretVault`, and `Remove-PSUSecretVault` to manage registrations remotely. The value referenced by `ClientSecretVariable` must be a PSU secret variable.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/powershell-universal/platform/variables/azure-key-vault-vaults.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.