> 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/rdm/knowledge-base/knowledge-base-articles/entry-settings/azure-key-vault.md).

# Azure Key Vault

Configure the Azure Key Vault credential entry in Remote Desktop Manager to securely retrieve credentials, certificates, and keys from Azure.

The ***Azure Key Vault*** credential entry is used to securely retrieve and use credentials, certificates, and keys stored with Azure's Key Vault service. When creating a new entry, the ***Azure Key Vault*** is located in ***Credential management***, under ***Password management***.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located. Click the browse button to select a folder, or click the add (<em><strong>+</strong></em>) button to create a new one.</td></tr></tbody></table>

### General

<table><thead><tr><th width="238">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Host</strong></td><td>The <em><strong>DNS Name</strong></em> of your Vault Key in Azure, located under the <em><strong>Overview</strong></em> section of the Azure portal. Required, and it must be a valid URL.</td></tr><tr><td><strong>Tenant ID</strong></td><td>Your <em><strong>Tenant ID</strong></em>, as displayed under the <em><strong>Overview</strong></em> section of the Microsoft Entra ID Azure portal. Required.</td></tr><tr><td><strong>Use "My account settings"</strong></td><td>When checked, this option retrieves the <em><strong>Client ID</strong></em> and <em><strong>Client Secret</strong></em> stored under <em><strong>File</strong></em> – <em><strong>My account settings</strong></em>. If they have not been configured yet, the <em><strong>My account settings</strong></em> window opens when the secret is retrieved. When checked, <em><strong>Client ID</strong></em> and <em><strong>Client Secret</strong></em> are disabled. Hidden when a policy disables <em><strong>My account settings</strong></em>.</td></tr><tr><td><strong>Client ID</strong></td><td>The <em><strong>Application ID</strong></em> of your Key Vault in Azure, found in the <em><strong>Overview</strong></em> section of the Azure portal, under <em><strong>Properties</strong></em>. Required unless <em><strong>Use "My account settings"</strong></em> is checked.</td></tr><tr><td><strong>Client Secret</strong></td><td>Your app's <em><strong>Client Secret</strong></em> (<em><strong>Your app</strong></em> – <em><strong>Certificates &#x26; secrets</strong></em> – <em><strong>Client secrets</strong></em>). The value cannot be revealed in the field. Required unless <em><strong>Use "My account settings"</strong></em> is checked.</td></tr><tr><td><strong>Username</strong></td><td>The username returned with the secret. The value of the secret is used as the password.</td></tr><tr><td><strong>Secret</strong></td><td>The Azure Key Vault secret to use for credential injection. Click the browse button right of the field to choose a secret from your Azure secrets list. Required unless <em><strong>Always prompt with list</strong></em> is checked, in which case the field is disabled.</td></tr><tr><td><strong>Always prompt with list</strong></td><td>When checked, this option brings up the <em><strong>Azure Key Vault secrets list</strong></em> whenever the entry is used, whether directly or for credential injection.</td></tr></tbody></table>


---

# 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/rdm/knowledge-base/knowledge-base-articles/entry-settings/azure-key-vault.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.