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

Update LAB_04-Implement_Virtual_Networking.md

Browse Source 
Added steps to get around vm size not available error
This commit is contained in:
Yas 2021-11-30 12:19:50 +11:00 committed by GitHub
parent d1b2ae9bac
commit 4f89b01dd4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
Instructions/Labs/LAB_04-Implement_Virtual_Networking.md
View File

@ -111,6 +111,13 @@ In this task, you will deploy Azure virtual machines into different subnets of t
>**Note**: Wait for the deployment to complete before proceeding to the next task. This should take about 2 minutes.
>**Note**: If you got an error stating the VM size is not available in the region, follow the following steps:
> 1. Click on the `{}` button in your CloudShell, select the **az104-04-vms-loop-parameters.json** from the left hand side bar and take a note of the `vmSize` parameter value.
> 1. Check the location in which the 'az104-04-rg1' resource group is deployed. You can run `az group show -n az104-04-rg1 --query location` in your CloudShell to get it.
> 1. Run `az vm list-skus --location <Replace with your location> -o table --query "[? contains(name,'Standard_D2s')].name"` in your CloudShell.
> 1. Replace the value of `vmSize` parameter with one of the values returned by the command you just run.
> 1. Now redeploy your templates by running the `New-AzResourceGroupDeployment` command again. You can press the up button a few times which would bring the last executed command.
1. Close the Cloud Shell pane.
#### Task 3: Configure private and public IP addresses of Azure VMs