> 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/fr/knowledge-base/troubleshooting-articles/switch-between-sql-azure-workspaces-with-mfa.md).

# Basculer entre les espaces de travail SQL Azure avec l'AMF

Corrigez l'absence d'invites AMF lors du changement d'espaces de travail SQL Azure dans Remote Desktop Manager en configurant le démarrage pour demander l'espace de travail.

Dans Remote Desktop Manager, lorsque vous basculez entre des espaces de travail SQL Azure qui prennent en charge l'authentification multifacteur (AMF), la connexion fonctionnera uniquement pour le premier espace de travail, mais pas pour les suivants; l'utilisateur ne recevra pas d'invite lors du changement d'espace de travail.

### Solution

Pour contourner ce problème, la solution consiste à faire en sorte que Remote Desktop Manager demande à l'utilisateur l'espace de travail au démarrage.

1. Allez dans ***Fichier – Espaces de travail***.
2. Au bas de la fenêtre, dans le menu déroulant ***Au démarrage***, sélectionnez ***Demander l'espace de travail***.
3. Cliquez sur ***OK***.
4. Fermez Remote Desktop Manager et rouvrez-le, puis choisissez l'espace de travail. L'invite AMF devrait maintenant être disponible.


---

# 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/fr/knowledge-base/troubleshooting-articles/switch-between-sql-azure-workspaces-with-mfa.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.