> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/overview-2/azure-services/infra-secrets.md). # Infra Secrets Create Infra Secrets to use with DuploCloud Infra Secrets in DuploCloud are used to securely store sensitive information, such as API keys, client secrets, or connection strings, needed for your infrastructure and application configurations. These secrets are managed within DuploCloud and can be used for secure access to services and resources. Infra Secrets provide a way to keep your sensitive data safe while allowing seamless integration with various DuploCloud services. ## Adding an Infra Secret 1. In the DuploCloud Portal, navigate to **Cloud Settings** → **Key Vault**. 2. Select the **Infra Secrets** tab. 3. Click **Add**. The **Add Infra Secret** pane displays.

4. Complete the fields:


Name	Enter the name of the Infra Secret. DuploCloud suggests using the Tenant name as a prefix.
Value	Enter the secret value (e.g., API key, client secret, connection string). This will be securely stored and used by DuploCloud services.
Type	Specify the type of secret, such as `API Key`, `Client Secret`, or `Connection`.

4. Click **Save** to store the Infra Secret securely. --- # 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.duplocloud.com/docs/automation-platform/overview-2/azure-services/infra-secrets.md?ask=&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.