> 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/knowledge-base/how-to-articles/configure-mfa-for-pam-checkout-in-devolutions-cloud.md).

# Configure MFA for PAM checkout in Devolutions Cloud

Administrators can enforce multifactor authentication for all users on Devolutions Cloud, or require it specifically when a privileged entry is checked out. 

Before you begin, users must have MFA enabled in the[ Devolutions Portal](https://portal.devolutions.com/security), under ***Sign-in & security***, for MFA to be enforced on checkout. To enforce multifactor verification for all users on Devolutions Cloud, go to ***Administration*** – ***Access & authentication*** – ***General*** – ***Enforce multifactor verification on Devolutions Account***.

#### MFA on PAM checkout

MFA can be required on privileged accounts through a [checkout policy](https://docs.devolutions.net/cloud/web-interface/administration/modules/privileged-access/checkout-policies). The ***MFA on checkout*** setting can be set to ***Default***, ***None***, ***Mandatory***, or ***Mandatory on JIT elevation only***.

{% hint style="warning" %}
MFA enforced at login through an external identity provider (Entra ID, PingOne, Okta, etc.) does not automatically satisfy the MFA on checkout requirement. These are two separate verifications.

Even if MFA is already enforced at login, the user still needs an MFA method configured for MFA on checkout to work. This method does not need to be enforced at login, only available for use at checkout.
{% endhint %}

1. Go to ***Administration*** – ***Privileged access management (PAM)*** – ***Checkout policies***.
2. Select an existing checkout policy to edit, or create a new one.
3. Set ***MFA on checkout*** to ***Default***, ***None***, ***Mandatory***, or ***Mandatory on JIT elevation only***, depending on when MFA should be enforced.
4. To apply this policy automatically to every entry and folder, enable ***Is default***. Otherwise, apply it to specific entries or folders by editing them, then going to ***Properties*** – ***Checkout policies***.
5. Select ***Update*** to save. The requirement applies the next time the entry is checked out.

#### See also

* [MFA on PAM Checkout: Prove it's really you before checking out a privileged account](https://www.youtube.com/watch?v=aWcV1HwJxTY)


---

# 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/cloud/knowledge-base/how-to-articles/configure-mfa-for-pam-checkout-in-devolutions-cloud.md?ask=<question>&goal=<endgoal>
```

`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.