> 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/kubernetes-overview/configs-and-secrets/using-kubernetes-secrets-with-azure-storage-connection-data.md).

# Using Kubernetes Secrets with Azure Storage connection data

Using K8s Secrets with Azure Storage Accounts

### **Creating a Storage Account and File Shares**

Refer to the [DupoCloud documentation](#creating-a-storage-account-and-file-shares) to configure Storage Account and File Share in Azure.

Copy the Storage Account Key and File Share Name from the DuploCloud Portal to prepare to create Kubernetes Secrets in the next step.

### **Creating Kubernetes Secret**

Navigate to **Kubernetes** -> **Secrets**. Create a Kubernetes Secret Object using an Azure Storage Account.

For more information, see [Kubernetes Configs and Secrets](/docs/automation-platform/kubernetes-overview/configs-and-secrets.md).

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2FvefFSuUy1dGEk3Tg0HTK%2Fimage.png?alt=media&amp;token=af137a03-df06-4734-bbd2-3876011cb42d" alt=""><figcaption><p>Kubernetes Storage Account Secret</p></figcaption></figure>

{% code title="SecretDetails example" %}

```
azurestorageaccountkey: >-
    <storage-account-key>
azurestorageaccountname: <storage-account-name>
```

{% endcode %}

### Mounting the Azure Storage connection in your deployment

While creating a deployment, provide the configuration below under **Other Pod Config** and **Other Container Config** to create and mount the storage volume for your Service. In the configuration below, `shareName` is the [File Share name, ](/docs/automation-platform/overview-2/azure-services/storage-account.md#create-and-view-file-shares)which you can get from the **Storage Account** screen.

{% code title="Other Pod Config" overflow="wrap" %}

```
PodLabels:
  app: azuretest
Volumes:
  - name: azurefileshare
    azureFile:
      secretName: my-storage-account-key
      shareName: fileshare1
      readOnly: false
```

{% endcode %}

{% code title="Other Container Config" %}

```
VolumesMounts:
  - name: azurefileshare
    mountPath: /myfileshare
```

{% endcode %}

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fe1GkquuBNWmlZpImBuv4%2Fimage.png?alt=media&amp;token=02605bf1-53f2-43a4-8f4f-0cf35dde27ee" alt=""><figcaption><p>Service Deployment Screen with K8s Secret example</p></figcaption></figure>


---

# 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/kubernetes-overview/configs-and-secrets/using-kubernetes-secrets-with-azure-storage-connection-data.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.
