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

# Cambiar entre espacios de trabajo de SQL Azure con MFA

Solucione la ausencia de solicitudes de MFA al cambiar entre espacios de trabajo de SQL Azure en Remote Desktop Manager configurando el inicio para que solicite el espacio de trabajo.

En Remote Desktop Manager, al cambiar entre espacios de trabajo de SQL Azure que tienen compatibilidad con la autenticación multifactor (MFA), la conexión funcionará únicamente para el primer espacio de trabajo, pero no para los siguientes; no se solicitará nada al usuario al cambiar de espacio de trabajo.

### Solución

Para eludir este problema, la solución consiste en hacer que Remote Desktop Manager solicite al usuario el espacio de trabajo al iniciarse.

1. Vaya a ***Archivo – Espacios de trabajo***.
2. En la parte inferior de la ventana, en el menú desplegable ***Al iniciar***, seleccione ***Solicitar espacio de trabajo***.
3. Haga clic en ***Aceptar***.
4. Cierre Remote Desktop Manager y vuelva a abrirlo, luego elija el espacio de trabajo. La solicitud de MFA ya debería estar 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/es/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.