Microsoft.ContainerRegistry registries 2017-06-01-preview

Template format

To create a Microsoft.ContainerRegistry/registries resource, add the following JSON to the resources section of your template.

  "name": "string",
  "type": "Microsoft.ContainerRegistry/registries",
  "apiVersion": "2017-06-01-preview",
  "location": "string",
  "tags": {},
  "sku": {
    "name": "string"
  "properties": {
    "adminUserEnabled": "boolean",
    "storageAccount": {
      "id": "string"
  "resources": []

Property values

The following tables describe the values you need to set in the schema.

Microsoft.ContainerRegistry/registries object


In Bicep, type and apiVersion are specified in the first line of the resource declaration. Use the format <type>@<apiVersion>. Don't set those properties in the resource body.

Name Type Required Value
name string Yes The name of the container registry.
type enum Yes For JSON - Microsoft.ContainerRegistry/registries
apiVersion enum Yes For JSON - 2017-06-01-preview
location string Yes The location of the resource. This cannot be changed after the resource is created.
tags object No The tags of the resource.
sku object Yes The SKU of the container registry. - Sku object
properties object Yes The properties of the container registry. - RegistryProperties object
resources array No webhooks replications

Sku object

Name Type Required Value
name enum Yes The SKU name of the container registry. Required for registry creation. - Basic, Managed_Basic, Managed_Standard, Managed_Premium

RegistryProperties object

Name Type Required Value
adminUserEnabled boolean No The value that indicates whether the admin user is enabled.
storageAccount object No The properties of the storage account for the container registry. Only applicable to Basic SKU. - StorageAccountProperties object

StorageAccountProperties object

Name Type Required Value
id string Yes The resource ID of the storage account.

Quickstart templates

The following quickstart templates deploy this resource type.

Template Description
CI/CD using Jenkins on Azure Container Service (AKS)

Deploy to Azure
Containers make it very easy for you to continuously build and deploy your applications. By orchestrating deployment of those containers using Kubernetes in Azure Container Service, you can achieve replicable, manageable clusters of containers. By setting up a continuous build to produce your container images and orchestration, you can increase the speed and reliability of your deployment.
Azure Container Registry Template

Deploy to Azure
A template for creating a new Azure Container Registry.
Azure Container Registry with Geo-replication Template

Deploy to Azure
A template for creating a new Azure Container Registry with geo-replication
Advanced template for Azure Machine Learning workspace

Deploy to Azure
A template that creates Azure Machine Learning workspace with private endpoints and resources behind VNET
Enable encryption at rest for Azure Machine Learning

Deploy to Azure
A template that creates a new Azure Machine Learning workspace. Optionally, you can enable encryption for data at rest in the workspace, and data stored by the workspace in Azure Cosmos DB.
Create an AKS compute target with a Private IP address.

Deploy to Azure
This template creates an AKS compute target in given Azure Machine Learning service workspace with a private IP address.
AKS cluster with the Application Gateway Ingress Controller

Deploy to Azure
This sample shows how to deploy an AKS cluster with Application Gateway, Application Gateway Ingress Controller, Azure Container Registry, Log Analytics and Key Vault