Skip to content

Commit 7c6fe81

Browse files
authored
Merge pull request #49732 from mumian/0822-arm-overview
0822 arm overview
2 parents d05912a + def7309 commit 7c6fe81

File tree

3 files changed

+13
-3
lines changed

3 files changed

+13
-3
lines changed

articles/azure-resource-manager/resource-manager-quickstart-create-templates-use-the-portal.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.service: azure-resource-manager
1111
ms.workload: multiple
1212
ms.tgt_pltfrm: na
1313
ms.devlang: na
14-
ms.date: 07/17/2018
14+
ms.date: 08/22/2018
1515
ms.topic: quickstart
1616
ms.author: jgao
1717

@@ -75,7 +75,9 @@ In this section, you create a storage account using the Azure portal. Before you
7575
7676
## Edit and deploy the template
7777

78-
In this section, you open the saved template from the template library, edit the template inside the portal, and deploy the revised template. To edit a more complex template, consider using Visual Studio Code which provides richer edit functionalities.
78+
In this section, you open the saved template from the template library, edit the template inside the portal, and deploy the revised template. To edit a more complex template, consider using [Visual Studio Code](./resource-manager-quickstart-create-templates-use-visual-studio-code.md) which provides richer edit functionalities.
79+
80+
Azure requires that each Azure service has a unique name. The deployment fails if you enter a storage account name that already exists. To avoid this issue, you can use a template function call uniquestring() to generate a unique storage account name.
7981

8082
1. In the Azure portal, select **All services** from the left menu, enter **template** in the filter box, and then select **Template (PREVIEW)**.
8183

@@ -159,7 +161,7 @@ In this section, you open the saved template from the template library, edit the
159161
8. Select **Deploy**.
160162
9. Enter the following values:
161163

162-
- **Subsription**: select your Azure subscription.
164+
- **Subscription**: select your Azure subscription.
163165
- **Resource group**: name your resource group with a unique name.
164166
- **Location**: select a location for the resource group.
165167
- **Location**: select a location for the storage account. You can use the same location as the resource group.
@@ -175,6 +177,14 @@ In this section, you open the saved template from the template library, edit the
175177
10. Select **Purchase**.
176178
11. Select the bell icon (notifications) from the top of the screen to see the deployment status.
177179

180+
![Azure Resource Manager templates deployment notification](./media/resource-manager-quickstart-create-templates-use-the-portal/azure-resource-manager-template-tutorial-portal-notification.png)
181+
182+
12. Select **Go to resource group** from the notification pane. You shall see a screen similar to:
183+
184+
![Azure Resource Manager templates deployment resource group](./media/resource-manager-quickstart-create-templates-use-the-portal/azure-resource-manager-template-tutorial-portal-deployment-resource-group.png)
185+
186+
You can see the deployment status was successful, and there is only one storage account in the resource group. The storage account name is a unique string generated by the template. To learn more about using Azure storage accounts, see [Quickstart: Upload, download, and list blobs using the Azure portal](../storage/blobs/storage-quickstart-blobs-portal.md).
187+
178188
## Clean up resources
179189

180190
When the Azure resources are no longer needed, clean up the resources you deployed by deleting the resource group.

0 commit comments

Comments
 (0)