Study/AZ-104-MicrosoftAzureAdministrator
1
0
Fork 0
mirror of https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator.git synced 2026-02-06 16:49:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update LAB_03-Manage_Azure_Resources_by_Using_ARM_Templates.md

Browse Source
This commit is contained in:
staleycyn 2023-12-13 06:48:29 -08:00 committed by GitHub
parent b9a5228a87
commit 7188670e1e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
New Instructions/Lab/LAB_03-Manage_Azure_Resources_by_Using_ARM_Templates.md
View File

@ -152,11 +152,7 @@ In this task, you verify that the deployment has finished successfuly. All prior
1. If necessary, use the **Advanced** settings to create disk storage for the Cloud Shell. 1. If necessary, use the **Advanced** settings to create disk storage for the Cloud Shell.
1. On the local drive, locate the parameters JSON file. 1. In the Cloud Shell, use the **Upload** icon to upload the template and parameters files. You will need to upload each file separately.
1. Edit the file and change the disk name. For example, change the disk name to **az104-disk2**.
1. In the Cloud Shell, use the **Upload** icon to upload the template and parameters files. You will need to upload each separately.
1. Verify your files are available in the Cloud Shell storage. 1. Verify your files are available in the Cloud Shell storage.
@ -164,6 +160,10 @@ In this task, you verify that the deployment has finished successfuly. All prior
dir dir
``` ```
1. In the Cloud Shell, select the **Editor** icon and navigate to the parameters JSON file.
1. Make a change. For example, change the disk name to **az104-disk2**.
>**Note**: You can target your template deployment to a resource group, subscription, management group, or tenant. Depending on the scope of the deployment, you use different commands. >**Note**: You can target your template deployment to a resource group, subscription, management group, or tenant. Depending on the scope of the deployment, you use different commands.
1. To deploy to a resource group, use **New-AzResourceGroupDeployment**. 1. To deploy to a resource group, use **New-AzResourceGroupDeployment**.
@ -179,11 +179,7 @@ In this task, you verify that the deployment has finished successfuly. All prior
1. If necessary, use the **Advanced** settings to create disk storage for the Cloud Shell. 1. If necessary, use the **Advanced** settings to create disk storage for the Cloud Shell.
1. On the local drive, locate the parameters JSON file. 1. In the Cloud Shell, use the **Upload** icon to upload the template and parameters files. You will need to upload each file separately.
1. Edit the file and change the disk name. For example, change the disk name to **az104-disk2**.
1. In the Cloud Shell, use the **Upload** icon to upload the template and parameters files. You will need to upload each separately.
1. Verify your files are available in the Cloud Shell storage. 1. Verify your files are available in the Cloud Shell storage.
@ -191,7 +187,11 @@ In this task, you verify that the deployment has finished successfuly. All prior
dir dir
``` ```
>**Note**: You can target your template deployment to a resource group, subscription, management group, or tenant. Depending on the scope of the deployment, you use different commands. 1. In the Cloud Shell, select the **Editor** icon and navigate to the parameters JSON file.
1. Make a change. For example, change the disk name to **az104-disk2**.
>**Note**: You can target your template deployment to a resource group, subscription, management group, or tenant. Depending on the scope of the deployment, you use different commands.
1. To deploy to a resource group, use **az deployment group create**. 1. To deploy to a resource group, use **az deployment group create**.