> For the complete documentation index, see [llms.txt](https://www.osdcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.osdcloud.com/osdcloud-v1/osdcloud-azure/azure-setup/azure-portal/storage-containers.md).

# Storage Containers

{% embed url="<https://docs.microsoft.com/en-us/azure/storage/common/storage-introduction>" %}

Storage Containers exist within the Azure Storage Account.  These can be set to be Public, but for the scope of OSDCloud Azure, these should be kept Private and Secure.

## Container Naming

Containers can be named whatever you want them to be to help you organize your Windows Images.  In the example below, I've created Storage Containers to separate the different Windows Image types

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVSV22dcsjKDdOxDA6n%2Fuploads%2FABRg6hSoVkYc0ZgdhLBk%2Fimage.png?alt=media\&token=aaf67d53-581a-45bf-8592-07f05b3311e1)

Containers can also be named to separate your Teams, there isn't a wrong way to design this

* [ ] Client Image Development Team
* [ ] Client Image Deployment Team
* [ ] Server Image Development Team
* [ ] Server Image Deployment Team

One thing to remember is that each Container can have different Roles for Access

## Create an Images Storage Container

In this example, I will create a simple Storage Container called Images that will contain my Windows Images

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVSV22dcsjKDdOxDA6n%2Fuploads%2FVyR8eL7SjRmWwJjkNGpn%2Fimage.png?alt=media\&token=d469f5f0-11c2-4be1-85c9-c93f7662eff9)

## Upload WIM

Now you can upload a WIM to your images Container. Select Upload and then browse to your WIM.  You will need to select Overwrite since we have not added any Access Control yet, and use the Account key option for the upload

![](https://344220114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MVSV22dcsjKDdOxDA6n%2Fuploads%2FchwBvTbNmQHOTRMO9C3V%2Fimage.png?alt=media\&token=3bf47f6e-3a98-4412-b548-9bee8c40f713)

## Sponsor

{% embed url="<https://www.recastsoftware.com/?utm_source=osdeploy&utm_medium=ad&utm_campaign=web>" %}
OSDeploy is sponsored by Recast Software
{% endembed %}


---

# 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://www.osdcloud.com/osdcloud-v1/osdcloud-azure/azure-setup/azure-portal/storage-containers.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.