> 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/pam/knowledge-base/how-to-articles.md). # How-to articles This section walks you through setting up and managing Privileged Access Management (PAM) providers, from initial deployment to ongoing maintenance. If you're just getting started, you'll find a quick guide to deploying AD PAM in your environment, along with instructions for creating specific provider types, a Windows user provider, an Entra ID provider for either Devolutions Cloud or Devolutions Server, and a domain account provider configured through Devolutions Gateway. You can also import computers from your existing domain user providers to bring them under PAM management. Once your providers are up and running, this section covers the day-to-day tasks that keep them secure: rotating PAM provider credentials on a schedule, configuring a provider to rotate its own password, and setting up temporary accounts with just-in-time (JIT) provisioning. You'll also find guidance on elevating management tools with a privileged account and configuring Devolutions Server PAM directly from Remote Desktop Manager. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.devolutions.net/pam/knowledge-base/how-to-articles.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.