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

# Abilitare il single sign-on con account Windows

Abiliti il single sign-on con gli account Windows nelle sessioni di siti web di Remote Desktop Manager per riutilizzare una sessione autenticata senza doverla richiedere di nuovo.

L'impostazione ***Abilita il single sign-on con gli account Windows*** in Remote Desktop Manager consente di riutilizzare automaticamente una sessione utente Windows autenticata per accedere a determinati servizi e risorse senza richiedere nuovamente le credenziali.

Per individuare l'impostazione, apra Remote Desktop Manager e vada su ***File*** – ***Impostazioni*** – ***Tipi di voce*** – ***Sessioni*** – ***Sito web***.

#### Le sessioni Edge accedono al tenant Microsoft 365 errato

Quando si crea un profilo Microsoft Edge in Remote Desktop Manager per accedere a Microsoft 365 con un tenant secondario, Edge potrebbe riaprirsi utilizzando il tenant principale aggiunto ad Azure Active Directory. Dopo il riavvio, tornando al tenant secondario viene richiesto di accedere nuovamente.

Ciò accade perché l'impostazione ***Abilita il single sign-on con gli account Windows*****s** utilizza lo stesso single sign-on impiegato al di fuori di Remote Desktop Manager. Pertanto, deve essere impostata su ***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/it/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.