> 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/adding-a-new-entry-in-the-user-vault-on-sql-azure-does-not-work.md).

# Adding a new entry in the user vault on SQL Azure does not work

Fix new entries not appearing in the SQL Azure user vault by verifying the user exists under Administration Users in Remote Desktop Manager.

You are able to create new entries inside the shared vault, but not in the user vault You create the new entry, but it never appears under the user vault.

### Solution

Make sure that the user that you are using to authenticate on the Azure SQL workspace has been created under ***Administration – Users*** in Remote Desktop Manager.

If the user is missing, the user vault feature for this user will not work.


---

# 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/adding-a-new-entry-in-the-user-vault-on-sql-azure-does-not-work.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.