Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit fcb817f

Browse files
committedSep 27, 2021
update the screenshots
1 parent 8d664d5 commit fcb817f

File tree

4 files changed

+15
-6
lines changed

4 files changed

+15
-6
lines changed
 

‎articles/container-registry/container-registry-get-started-bicep.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to create an Azure container registry by using a Bicep fi
44
services: azure-resource-manager
55
author: mumian
66
ms.author: jgao
7-
ms.date: 09/23/2021
7+
ms.date: 09/27/2021
88
ms.topic: quickstart
99
ms.service: azure-resource-manager
1010
---
@@ -13,7 +13,7 @@ ms.service: azure-resource-manager
1313

1414
This quickstart shows how to create an Azure Container Registry instance by using a Bicep file.
1515

16-
[!INCLUDE [About Azure Resource Manager](../../includes/resource-manager-quickstart-introduction.md)]
16+
[!INCLUDE [About Azure Resource Manager](../../includes/resource-manager-quickstart-bicep-introduction.md)]
1717

1818
## Prerequisites
1919

@@ -84,17 +84,17 @@ When the deployment finishes, you should see a message indicating the deployment
8484

8585
Use the Azure portal or a tool such as the Azure CLI to review the properties of the container registry.
8686

87-
1. In the portal, search for Container Registries, and select the container registry you created.
87+
1. In the portal, search for **Container Registries**, and select the container registry you created.
8888

8989
1. On the **Overview** page, note the **Login server** of the registry. Use this URI when you use Docker to tag and push images to your registry. For information, see [Push your first image using the Docker CLI](container-registry-get-started-docker-cli.md).
9090

91-
:::image type="content" source="media/container-registry-get-started-geo-replication-template/registry-overview.png" alt-text="Registry overview":::
91+
:::image type="content" source="media/container-registry-get-started-bicep/registry-overview.png" alt-text="Registry overview":::
9292

9393
## Clean up resources
9494

95-
When you no longer need them, delete the resource group, the registry, and the registry replica. To do so, go to the Azure portal, select the resource group that contains the registry, and then select **Delete resource group**.
95+
When you no longer need the resource, delete the resource group, and the registry. To do so, go to the Azure portal, select the resource group that contains the registry, and then select **Delete resource group**.
9696

97-
:::image type="content" source="media/container-registry-get-started-geo-replication-template/delete-resource-group.png" alt-text="Delete resource group":::
97+
:::image type="content" source="media/container-registry-get-started-bicep/delete-resource-group.png" alt-text="Delete resource group":::
9898

9999
## Next steps
100100

Loading
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
author: mumian
3+
ms.service: azure-resource-manager
4+
ms.topic: include
5+
ms.date: 09/27/2021
6+
ms.author: jgao
7+
---
8+
9+
[Bicep](../articles/azure-resource-manager/bicep/overview.md) is a domain-specific language (DSL) that uses declarative syntax to deploy Azure resources. It provides concise syntax, reliable type safety, and support for code reuse. Bicep offers the best authoring experience for your infrastructure-as-code solutions in Azure.

0 commit comments

Comments
 (0)
Please sign in to comment.