> 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-pim-privileged-identity-management.md).

# Azure PIM - Privileged Identity Management

Configure Azure PIM session entries in Remote Desktop Manager, including the username, tenant ID, account validation, and My account settings option.

This article details the many settings and options available for ***Azure PIM - Privileged Identity Management*** session entries in Remote Desktop Manager.

<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><tr><td><strong>Display</strong></td><td><p>How the entry opens:</p><ul><li><strong>Embedded (tabbed)</strong> — Opens the entry in a tab of the main window.</li><li><strong>Undocked</strong> — Opens the entry in a separate window. Additional lists let you choose the monitor and the virtual desktop where the window opens.</li></ul><p>On Linux, the list also offers <em><strong>Default (inherited)</strong></em>, which uses the display mode of the nearest parent folder that sets one, otherwise the default of the entry type. The mode it resolves to is shown next to the list.</p></td></tr></tbody></table>

**Azure PIM authorization**

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Use "My account settings"</strong></td><td>Use the Azure PIM account configured in <em><strong>File</strong></em> – <em><strong>My account settings</strong></em> instead of the account of the entry. When checked, <em><strong>Username</strong></em> and <em><strong>Tenant ID</strong></em> are disabled and the account status is hidden.</td></tr><tr><td><strong>Username</strong></td><td>The username of the account used to sign in to Azure. Filled automatically when the account is connected. Read-only once the account is validated.</td></tr><tr><td><strong>Tenant ID</strong></td><td>The ID of the Microsoft Entra tenant to sign in to. Read-only once the account is validated.</td></tr><tr><td><strong>Account status</strong></td><td>Shows whether the account of the entry is validated. The status reads "The account is not validated yet." until the account is connected, then "Account validated for tenant:" followed by the tenant name. If the stored validation can no longer be used when the entry is edited, the message "Validation is outdated." appears and the account returns to the not validated state.</td></tr><tr><td><strong>Connect account</strong></td><td>Shown when the account is not validated. Opens the Azure sign-in for the <em><strong>Tenant ID</strong></em>. Once signed in, the account is validated and the <em><strong>Username</strong></em> is filled with the signed-in account.</td></tr><tr><td><strong>Clear account</strong></td><td>Shown when the account is validated. Removes the validated account from the entry so that another account can be connected.</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-pim-privileged-identity-management.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.
