> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/container-image-scanning/cloud-provider-registries/image-scanning-for-azure-container-registry.md).

# Azure Container Registry

You can integrate your Azure Container Registry with Aikido to scan your containers for known vulnerabilities.

Follow the simple steps below to activate this feature:

**Step 1:** Log into your Azure account and navigate to the container registry you wish to link. We'll have to gather the registry name (login server), a secret token and the token username. The registry name can be found at the top of the detail page of the registry (see screenshot)

![Azure resource details: group, location, login server, and creation date displayed.](/files/74I0h4EZC4V2JpRUR5Ux)

**Step 2:** To create a secret token that can pull the containers, scroll down in the left-hand menu to the 'Repository permission' section and click 'Tokens'. Name the token 'aikido' and create a new scope map. Aikido will need the 'content/read' scope to pull the images and the 'metadata/read' scope to list the images and tags available in your registry.

You can give Aikido access to all the images in the registry by using the '\*' wildcard character in the repository field. Alternatively, you can only give Aikido access to certain images by adding the permissions for each one.

![Creating a token with custom scope map and read-only repository permissions.](/files/eJCKtiiiOS63X8hPlyHR)

After creating the token you have to click it again to generate a password. That screen should look like the one below:

![Password generation screen prompting user to securely save new password and Docker login command.](/files/fJ1U5UNzVh7qWoflYucC)

**Step 3:** Back in Aikido, go to settings, then [containers](https://app.aikido.dev/settings/container-image-registry). Click 'Connect registry' and pick

Azure Container Registry. Enter the data from the previous steps. Username being the Token name.

![Login form for accessing a private Azure container registry.](/files/hGG5lY3qPZ5eM7sYnwLs)

**Step 4:** Aikido will now find all container repositories you can access and list them.

**Step 5:** Repositories can be linked to a code repository in order to perform better deduplication of findings. This step is optional!

**Step 6:** In the action menu next to the registry, click 'Scan containers in registry' to get started. Results will appear in the Feed!

### &#x20;<a href="#set-up-azure-container-registry-scanning" id="set-up-azure-container-registry-scanning"></a>


---

# 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://help.aikido.dev/container-image-scanning/cloud-provider-registries/image-scanning-for-azure-container-registry.md?ask=<question>&goal=<endgoal>
```

`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.
