> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/fr/installation-setup/installation/microsoft-iis/azure-keyvault.md).

# Azure KeyVault

Vous pouvez également utiliser le  [Azure Key vault](https://azure.microsoft.com/en-us/services/key-vault/) pour stocker tous vos paramètres de configuration ngSurvey, y compris la connectionstring, au lieu d’utiliser le fichier web.config. \
\
Pour configurer votre keyvault, définissez les variables d’environnement suivantes avec les paramètres de votre keyvault.

* KeyVault:Name est le nom de votre Azure Key Vault
* AzureAd:ClientId est l’identifiant client (client id) pour accéder à votre key vault
* AzureAd:ClientSecret est le secret client pour accéder à votre Key vault


---

# 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.ngsurvey.com/fr/installation-setup/installation/microsoft-iis/azure-keyvault.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.