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

# Switch between SQL Azure workspaces with MFA

Fix MFA prompts not appearing when switching SQL Azure workspaces in Remote Desktop Manager by setting startup to prompt for workspace.

In Remote Desktop Manager, when switching between SQL Azure workspaces that have multifactor authentication (MFA) support, the connection will work only for the first workspace but not for subsequent ones; the user will not be prompted when switching workspaces.

### Solution

To circumvent this problem, the solution is make Remote Desktop Manager prompt the user for the workspace on start up.

1. Go to ***File – Workspaces***.
2. At the bottom of the window, in the ***On start up*** drop-down menu, select ***Prompt for workspace***.
3. Click ***OK***.
4. Close Remote Desktop Manager and open it back up, then choose the workspace. The MFA prompt should now be available.


---

# 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/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.