> 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/rdm/es/knowledge-base/how-to-articles/enable-single-sign-on-with-windows-accounts.md).

# Activar el inicio de sesión único con cuentas de Windows

Habilite el inicio de sesión único con cuentas de Windows en las sesiones de sitio web de Remote Desktop Manager para reutilizar una sesión autenticada sin que se soliciten las credenciales de nuevo.

La opción ***Enable Single-Sign-On with Windows accounts*** de Remote Desktop Manager permite reutilizar automáticamente una sesión de usuario de Windows autenticada para acceder a determinados servicios y recursos sin volver a solicitar las credenciales.

Para localizar la opción, abra Remote Desktop Manager y vaya a ***File*** – ***Settings*** – ***Entry types*** – ***Sessions*** – ***Website***.

#### Las sesiones de Edge inician sesión en el tenant de Microsoft 365 incorrecto

Al crear un perfil de Microsoft Edge en Remote Desktop Manager para iniciar sesión en Microsoft 365 con un tenant secundario, Edge puede volver a abrirse utilizando el tenant principal que está unido a Azure Active Directory. Tras el reinicio, al volver al tenant secundario se le solicita iniciar sesión de nuevo.

Esto se debe a que la opción ***Enable single-sign-on with Windows account*****s** utiliza el mismo inicio de sesión único que se usa fuera de Remote Desktop Manager. Por lo tanto, debe establecerse en ***No***.


---

# 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/rdm/es/knowledge-base/how-to-articles/enable-single-sign-on-with-windows-accounts.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.