> 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/concepts/intermediate-concepts/authentication.md). # Authentication Devolutions Cloud authentication covers local sign-in, session timeouts, password complexity, and single sign-on with Microsoft Entra ID or Okta. Authentication in Devolutions Cloud controls how users sign in to the Devolutions Cloud instance and proves their identity before any access is granted. Administrators can configure options such as mandatory login prompts, session timeouts, and password complexity for local authentication. Devolutions Cloud also supports single sign on with Microsoft Entra ID or Okta, allowing users to authenticate with their corporate identity provider while still benefiting from Devolutions Cloud specific security controls. Authentication settings integrate with system permissions and roles, so that once a user is authenticated, their effective access is determined by centrally managed policies. #### Related topics * [Access & authentication](/cloud/web-interface/administration/configuration-and-security/access-and-authentication.md) * [Get started with SSO in Devolutions Cloud](/cloud/getting-started/get-started-with-sso-in-devolutions-cloud.md) --- # 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/concepts/intermediate-concepts/authentication.md?ask=&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.