> For the complete documentation index, see [llms.txt](https://docs.guardianservice.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardianservice.app/technical-information/users/mgs-vault/microsoft-azure-key-vault/microsoft-azure-key-vault-integration-with-mgs.md).
# Microsoft Azure Key Vault Integration with MGS
1. Register a new user on MGS. When it’s created, you’ll be redirected to the Finish Setup page to finalize your user profile. To proceed with the Azure Key Vault as your Vault solution, please select the “Azure Key Vault” option in the available vaults list and click Next.
2. Enter the appropriate data into the fields:
* Vault Name – Key vault name from the step 9.
* Tenant Id – Directory (tenant) ID from the step 4.
* Client Id – Application (client) ID from the step 4.
* Client Secret – Secret Value from the step 6.
* Prefix for secrets – prefix to be added to the beginning of the key name (in case one vault is used for many accounts).
3. On the next step, enter your Hedera Account and Name of the secret that was added to the Azure Key Vault, click Next to finalize the setup process.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.guardianservice.app/technical-information/users/mgs-vault/microsoft-azure-key-vault/microsoft-azure-key-vault-integration-with-mgs.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.