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

# Externe PAM-Integrationen

Verbinden Sie Devolutions Cloud mit externen PAM-Anbietern wie Entra ID und AWS IAM für zentralisierte privilegierte Zugriffsverwaltung und Auditing.

Externe PAM-Integrationen verbinden die Workflows für privilegierten Zugriff von Devolutions Cloud mit Identitätssystemen oder Plattformen, die außerhalb von Devolutions verwaltet werden. Über Devolutions PAM-Anbieter kann Devolutions Cloud externe Identitätsquellen wie Entra ID, AWS IAM, Datenbanken oder benutzerdefinierte PAM-Anbieter darstellen und dabei Zugriffskontrolle und Auditing zentralisieren.

In Devolutions Cloud ermöglichen diese Integrationen, dass Erkennung privilegierter Konten, Passwortrotation und Auschecken-Workflows gegen externe Systeme ausgeführt werden, während Genehmigungen, Berichte und Richtlinien in Devolutions Cloud verbleiben. Ein häufiges Szenario ist die Verwaltung erhöhter Entra ID-Konten über PAM-Anbieter, während Operatoren den Zugriff direkt über die Devolutions Cloud-Oberfläche anfordern und nutzen.

#### Verwandte Themen

* [PAM mit Devolutions Cloud](https://docs.devolutions.net/pam/de/pam-with-devolutions-cloud)
* [Anbieter](https://docs.devolutions.net/pam/de/concepts/providers)
* [Benutzerdefinierte PAM-Anbieter](https://docs.devolutions.net/pam/de/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/de/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.
