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

# Integrazioni PAM esterne

Colleghi Devolutions Cloud a provider PAM esterni come Entra ID e AWS IAM per un accesso privilegiato e un audit centralizzati.

Le integrazioni PAM esterne collegano i flussi di lavoro di accesso privilegiato di Devolutions Cloud a sistemi di identità o piattaforme gestiti al di fuori di Devolutions. Attraverso i provider Devolutions PAM, Devolutions Cloud può rappresentare origini di identità esterne come Entra ID, AWS IAM, database o provider PAM personalizzati, centralizzando al contempo il controllo degli accessi e l'audit.

In Devolutions Cloud, queste integrazioni consentono di eseguire il rilevamento degli account privilegiati, la rotazione delle password e i flussi di lavoro di check-out su sistemi esterni, mentre approvazioni, reportistica e criteri restano in Devolutions Cloud. Uno scenario comune è la gestione di account Entra ID con privilegi elevati tramite provider PAM, mentre gli operatori richiedono e utilizzano l'accesso direttamente dall'interfaccia di Devolutions Cloud.

#### Argomenti correlati

* [PAM con Devolutions Cloud](https://docs.devolutions.net/pam/it/pam-with-devolutions-cloud)
* [Provider](https://docs.devolutions.net/pam/it/concepts/providers)
* [Provider PAM personalizzati](https://docs.devolutions.net/pam/it/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 dynamically 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/it/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 `build a script that syncs our docs to a CMS` 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.