> 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/de/knowledge-base/troubleshooting-articles/azure-sql-error-connection-failed-due-to-mismatch-of-users-during-the-authentication-process.md).

# Azure SQL-Fehler: Verbindung aufgrund einer Benutzerabweichung während des Authentifizierungsvorgangs fehlgeschlagen

Beheben Sie Azure SQL-Verbindungsfehler, die durch eine UserPrincipalName-Abweichung verursacht werden, indem Sie das Konto neu erstellen und einen SQL-Login-Fix ausführen.

In einem neuen Remote Desktop Manager-Konto erscheint eine Fehlermeldung, wenn der ***UserPrincipalName*** (UPN) des vorherigen Kontos geändert wurde, um den Verlust der tresorspezifischen Einstellungen des Benutzers zu vermeiden.

### Lösung

1. Bearbeiten Sie den ***Azure-Datenbankbesitzer*** im Azure-Portal.
2. Löschen Sie das durch ***Expecting*** in der Fehlermeldung identifizierte Konto im ***Sicherheitsbereich*** der Azure-Datenbank in SQL Server Management Studio.
3. Erstellen Sie das Konto im ***Sicherheitsbereich*** der Azure-Datenbank in SQL Server Management Studio neu.
4. Führen Sie einen ***SQL Login fix*** für das Konto unter ***Administration*** – ***Benutzer*** in Remote Desktop Manager durch.


---

# 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/de/knowledge-base/troubleshooting-articles/azure-sql-error-connection-failed-due-to-mismatch-of-users-during-the-authentication-process.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.