> 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/cloud/da/concepts/advanced-concepts/external-pam-integrations.md).

# Eksterne PAM-integrationer

Forbind Devolutions Cloud med eksterne PAM-udbydere som Entra ID og AWS IAM for at samle privilegeret adgang og revision.

Eksterne PAM-integrationer forbinder arbejdsflows for privilegeret adgang i Devolutions Cloud med identitetssystemer eller platforme, der administreres uden for Devolutions. Via Devolutions PAM-udbydere kan Devolutions Cloud repræsentere eksterne identitetskilder som Entra ID, AWS IAM, databaser eller brugerdefinerede PAM-udbydere og samtidig centralisere adgangskontrol og revision.

I Devolutions Cloud gør disse integrationer det muligt at køre registrering af privilegerede konti, rotation af adgangskoder og arbejdsflows for udtjekning mod eksterne systemer, mens godkendelser, rapportering og politikker forbliver i Devolutions Cloud. Et almindeligt scenarie er at administrere ophøjede Entra ID-konti via PAM-udbydere, mens operatører anmoder om og bruger adgang direkte fra grænsefladen i Devolutions Cloud.

#### Relaterede emner

* [PAM med Devolutions Cloud](https://docs.devolutions.net/pam/pam-with-devolutions-cloud)
* [Udbydere](https://docs.devolutions.net/pam/concepts/providers)
* [Brugerdefinerede PAM-udbydere](https://docs.devolutions.net/pam/pam-with-devolutions-server/getting-started/custom-pam-providers)


---

# 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/cloud/da/concepts/advanced-concepts/external-pam-integrations.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.