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

Merge branch 'master' of https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator into MicrosoftLearningMaster

Browse Source
This commit is contained in:
Roman Korecky 2021-02-20 20:44:00 +01:00
commit 5cc3d060b6
9 changed files with 773 additions and 186 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
Allfiles/Labs/04/az104-04-vms-loop-parameters .json Normal file
View File

@ -0,0 +1,15 @@
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"vmSize": {
"value": "Standard_D2s_v3"
},
"adminUsername": {
"value": "Student"
},
"adminPassword": {
"value": "Pa55w.rd1234"
}
}
}

162
Allfiles/Labs/04/az104-04-vms-loop-template.json Normal file
View File

@ -0,0 +1,162 @@
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"vmSize": {
"type": "string",
"defaultValue": "Standard_D2s_v3",
"metadata": {
"description": "VM size"
}
},
"vmName": {
"type": "string",
"defaultValue": "az104-04-vm",
"metadata": {
"description": "VM name Prefix"
}
},
"vmCount": {
"type": "int",
"defaultValue": 2,
"metadata": {
"description": "Number of VMs"
}
},
"adminUsername": {
"type": "string",
"metadata": {
"description": "Admin username"
}
},
"adminPassword": {
"type": "securestring",
"metadata": {
"description": "Admin password"
}
},
"virtualNetworkName": {
"type": "string",
"defaultValue": "az104-04-vnet1",
"metadata": {
"description": "Virtual network name"
}
}
},
"variables": {
"nic": "az104-04-nic",
"virtualNetworkName": "[parameters('virtualNetworkName')]",
"subnetName": "subnet",
"subnet0Name": "subnet0",
"subnet1Name": "subnet1",
"computeApiVersion": "2018-06-01",
"networkApiVersion": "2018-08-01"
},
"resources": [
{
"name": "[concat(parameters('vmName'),copyIndex())]",
"copy": {
"name": "VMcopy",
"count": "[parameters('vmCount')]"
},
"type": "Microsoft.Compute/virtualMachines",
"apiVersion": "[variables('computeApiVersion')]",
"location": "[resourceGroup().location]",
"comments": "Creating VMs",
"dependsOn": [
"[concat(variables('nic'),copyIndex())]"
],
"properties": {
"osProfile": {
"computerName": "[concat(parameters('vmName'),copyIndex())]",
"adminUsername": "[parameters('adminUsername')]",
"adminPassword": "[parameters('adminPassword')]",
"windowsConfiguration": {
"provisionVmAgent": "true"
}
},
"hardwareProfile": {
"vmSize": "[parameters('vmSize')]"
},
"storageProfile": {
"imageReference": {
"publisher": "MicrosoftWindowsServer",
"offer": "WindowsServer",
"sku": "2019-Datacenter",
"version": "latest"
},
"osDisk": {
"createOption": "fromImage"
},
"dataDisks": []
},
"networkProfile": {
"networkInterfaces": [
{
"properties": {
"primary": true
},
"id": "[resourceId('Microsoft.Network/networkInterfaces', concat(variables('nic'),copyIndex()))]"
}
]
}
}
},
{
"type": "Microsoft.Network/virtualNetworks",
"name": "[variables('virtualNetworkName')]",
"apiVersion": "[variables('networkApiVersion')]",
"location": "[resourceGroup().location]",
"comments": "Virtual Network",
"properties": {
"addressSpace": {
"addressPrefixes": [
"10.40.0.0/22"
]
},
"subnets": [
{
"name": "[variables('subnet0Name')]",
"properties": {
"addressPrefix": "10.40.0.0/24"
}
},
{
"name": "[variables('subnet1Name')]",
"properties": {
"addressPrefix": "10.40.1.0/24"
}
}
]
}
},
{
"name": "[concat(variables('nic'),copyIndex())]",
"copy":{
"name": "nicCopy",
"count": "[parameters('vmCount')]"
},
"type": "Microsoft.Network/networkInterfaces",
"apiVersion": "[variables('networkApiVersion')]",
"location": "[resourceGroup().location]",
"comments": "Primary NIC",
"dependsOn": [
"[concat('Microsoft.Network/virtualNetworks/', variables('virtualNetworkName'))]"
],
"properties": {
"ipConfigurations": [
{
"name": "ipconfig1",
"properties": {
"subnet": {
"id": "[resourceId('Microsoft.Network/virtualNetworks/subnets', variables('virtualNetworkName'), concat(variables('subnetName'),copyIndex()))]"
},
"privateIPAllocationMethod": "Dynamic"
}
}
]
}
}
],
"outputs": {}
}

15
Allfiles/Labs/05/az104-05-vnetvm-loop-parameters.json Normal file
View File

@ -0,0 +1,15 @@
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"vmSize": {
"value": "Standard_D2s_v3"
},
"adminUsername": {
"value": "Student"
},
"adminPassword": {
"value": "Pa55w.rd1234"
}
}
}

202
Allfiles/Labs/05/az104-05-vnetvm-loop-template.json Normal file
View File

@ -0,0 +1,202 @@
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"vmSize": {
"type": "string",
"defaultValue": "Standard_D2s_v3",
"metadata": {
"description": "Virtual machine size"
}
},
"location1": {
"type": "string",
"metadata": {
"description": "First Azure Region"
}
},
"location2": {
"type": "string",
"metadata": {
"description": "Second Azure Region"
}
},
"adminUsername": {
"type": "string",
"metadata": {
"description": "Admin username"
}
},
"adminPassword": {
"type": "securestring",
"metadata": {
"description": "Admin password"
}
}
},
"variables": {
"locationNames": "[createArray(parameters('location1'),parameters('location1'),parameters('location2'))]",
"vmName": "az104-05-vm",
"nicName": "az104-05-nic",
"subnetName": "subnet0",
"VnetName": "az104-05-vnet",
"pipName": "az104-05-pip",
"nsgName": "az104-05-nsg",
"computeApiVersion": "2018-06-01",
"networkApiVersion": "2018-08-01"
},
"resources": [
{
"name": "[concat(variables('vmName'),copyIndex())]",
"copy": {
"name": "VMcopy",
"count": "[length(variables('locationNames'))]"
},
"type": "Microsoft.Compute/virtualMachines",
"apiVersion": "[variables('computeApiVersion')]",
"location": "[variables('locationNames')[copyIndex()]]",
"dependsOn": [
"[concat(variables('nicName'),copyIndex())]"
],
"properties": {
"osProfile": {
"computerName": "[concat(variables('vmName'),copyIndex())]",
"adminUsername": "[parameters('adminUsername')]",
"adminPassword": "[parameters('adminPassword')]",
"windowsConfiguration": {
"provisionVmAgent": "true"
}
},
"hardwareProfile": {
"vmSize": "[parameters('vmSize')]"
},
"storageProfile": {
"imageReference": {
"publisher": "MicrosoftWindowsServer",
"offer": "WindowsServer",
"sku": "2019-Datacenter",
"version": "latest"
},
"osDisk": {
"createOption": "fromImage"
},
"dataDisks": []
},
"networkProfile": {
"networkInterfaces": [
{
"properties": {
"primary": true
},
"id": "[resourceId('Microsoft.Network/networkInterfaces',concat(variables('nicName'),copyIndex()))]"
}
]
}
}
},
{
"type": "Microsoft.Network/virtualNetworks",
"name": "[concat(variables('VnetName'),copyIndex())]",
"copy": {
"name": "VNetCopy",
"count": "[length(variables('locationNames'))]"
},
"apiVersion": "[variables('networkApiVersion')]",
"location": "[variables('locationNames')[copyIndex()]]",
"comments": "Virtual Network",
"properties": {
"addressSpace": {
"addressPrefixes": [
"[concat('10.5',copyIndex(),'.0.0/22')]"
]
},
"subnets": [
{
"name": "[variables('subnetName')]",
"properties": {
"addressPrefix": "[concat('10.5',copyIndex(),'.0.0/24')]"
}
}
]
}
},
{
"name": "[concat(variables('nicName'),copyIndex())]",
"copy": {
"name": "nicCopy",
"count": "[length(variables('locationNames'))]"
},
"type": "Microsoft.Network/networkInterfaces",
"apiVersion": "[variables('networkApiVersion')]",
"location": "[variables('locationNames')[copyIndex()]]",
"comments": "Primary NIC",
"dependsOn": [
"[concat(variables('pipName'),copyIndex())]",
"[concat(variables('nsgName'),copyIndex())]",
"[concat(variables('VnetName'),copyIndex())]"
],
"properties": {
"ipConfigurations": [
{
"name": "ipconfig1",
"properties": {
"subnet": {
"id": "[resourceId('Microsoft.Network/virtualNetworks/subnets', concat(variables('VnetName'),copyIndex()), variables('subnetName'))]"
},
"privateIPAllocationMethod": "Dynamic",
"publicIpAddress": {
"id": "[resourceId('Microsoft.Network/publicIpAddresses', concat(variables('pipName'),copyIndex()))]"
}
}
}
],
"networkSecurityGroup": {
"id": "[resourceId('Microsoft.Network/networkSecurityGroups', concat(variables('nsgName'),copyIndex()))]"
}
}
},
{
"name": "[concat(variables('pipName'),copyIndex())]",
"copy": {
"name": "pipCopy",
"count": "[length(variables('locationNames'))]"
},
"type": "Microsoft.Network/publicIpAddresses",
"apiVersion": "[variables('networkApiVersion')]",
"location": "[variables('locationNames')[copyIndex()]]",
"comments": "Public IP for Primary NIC",
"properties": {
"publicIpAllocationMethod": "Dynamic"
}
},
{
"name": "[concat(variables('nsgName'),copyIndex())]",
"copy": {
"name": "nsgCopy",
"count": "[length(variables('locationNames'))]"
},
"type": "Microsoft.Network/networkSecurityGroups",
"apiVersion": "[variables('networkApiVersion')]",
"location": "[variables('locationNames')[copyIndex()]]",
"comments": "Network Security Group (NSG) for Primary NIC",
"properties": {
"securityRules": [
{
"name": "default-allow-rdp",
"properties": {
"priority": 1000,
"sourceAddressPrefix": "*",
"protocol": "Tcp",
"destinationPortRange": "3389",
"access": "Allow",
"direction": "Inbound",
"sourcePortRange": "*",
"destinationAddressPrefix": "*"
}
}
]
}
}
],
"outputs": {}
}

15
Allfiles/Labs/06/az104-06-vms-loop-parameters.json Normal file
View File

@ -0,0 +1,15 @@
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"vmSize": {
"value": "Standard_D2s_v3"
},
"adminUsername": {
"value": "Student"
},
"adminPassword": {
"value": "Pa55w.rd1234"
}
}
}

237
Allfiles/Labs/06/az104-06-vms-loop-template.json Normal file
View File

@ -0,0 +1,237 @@
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"vmSize": {
"type": "string",
"defaultValue": "Standard_D2s_v3",
"metadata": {
"description": "VM size"
}
},
"vmName": {
"type": "string",
"defaultValue": "az104-06-vm",
"metadata": {
"description": "VM name Prefix"
}
},
"vmCount": {
"type": "int",
"defaultValue": 4,
"metadata": {
"description": "Number of VMs"
}
},
"adminUsername": {
"type": "string",
"metadata": {
"description": "Admin username"
}
},
"adminPassword": {
"type": "securestring",
"metadata": {
"description": "Admin password"
}
}
},
"variables": {
"vmExtensionName": "customScriptExtension",
"nic": "az104-06-nic",
"virtualNetworkNames": "[createArray('az104-06-vnet01','az104-06-vnet01','az104-06-vnet2','az104-06-vnet3')]",
"virtualNetworkNamestbc": "[createArray('az104-06-vnet01','az104-06-vnet2','az104-06-vnet3')]",
"VNetPrefixes":"[createArray('10.60','10.62','10.63')]",
"nsgNames": "[createArray('az104-06-nsg01','az104-06-nsg01','az104-06-nsg2','az104-06-nsg3')]",
"nsgNamestbc": "[createArray('az104-06-nsg01','az104-06-nsg2','az104-06-nsg3')]",
"subnetName": "subnet",
"subnetRefs": "[createArray(0,1,0,0)]",
"computeApiVersion": "2018-06-01",
"networkApiVersion": "2018-08-01"
},
"resources": [
{
"name": "[concat(parameters('vmName'),copyIndex())]",
"copy": {
"name": "VMcopy",
"count": "[parameters('vmCount')]"
},
"type": "Microsoft.Compute/virtualMachines",
"apiVersion": "[variables('computeApiVersion')]",
"location": "[resourceGroup().location]",
"comments": "Creating VMs",
"dependsOn": [
"[concat(variables('nic'),copyIndex())]"
],
"properties": {
"osProfile": {
"computerName": "[concat(parameters('vmName'),copyIndex())]",
"adminUsername": "[parameters('adminUsername')]",
"adminPassword": "[parameters('adminPassword')]",
"windowsConfiguration": {
"provisionVmAgent": "true"
}
},
"hardwareProfile": {
"vmSize": "[parameters('vmSize')]"
},
"storageProfile": {
"imageReference": {
"publisher": "MicrosoftWindowsServer",
"offer": "WindowsServer",
"sku": "2019-Datacenter",
"version": "latest"
},
"osDisk": {
"createOption": "fromImage"
},
"dataDisks": []
},
"networkProfile": {
"networkInterfaces": [
{
"properties": {
"primary": true
},
"id": "[resourceId('Microsoft.Network/networkInterfaces', concat(variables('nic'),copyIndex()))]"
}
]
}
}
},
{
"type": "Microsoft.Compute/virtualMachines/extensions",
"name": "[concat(concat(parameters('vmName'),copyIndex()), '/', variables('vmExtensionName'))]",
"copy": {
"name": "Extopy",
"count": "[parameters('vmCount')]"
},
"apiVersion": "[variables('computeApiVersion')]",
"location": "[resourceGroup().location]",
"dependsOn": [
"[concat('Microsoft.Compute/virtualMachines/', concat(parameters('vmName'),copyIndex()))]"
],
"properties": {
"publisher": "Microsoft.Compute",
"type": "CustomScriptExtension",
"typeHandlerVersion": "1.7",
"autoUpgradeMinorVersion": true,
"settings": {
"commandToExecute": "powershell.exe Install-WindowsFeature -name Web-Server -IncludeManagementTools && powershell.exe remove-item 'C:\\inetpub\\wwwroot\\iisstart.htm' && powershell.exe Add-Content -Path 'C:\\inetpub\\wwwroot\\iisstart.htm' -Value $('Hello World from ' + $env:computername)"
}
}
},
{
"type": "Microsoft.Network/virtualNetworks",
"name": "[variables('virtualNetworkNamestbc')[copyIndex()]]",
"copy": {
"name": "VnetCopy",
"count": "[length(variables('virtualNetworkNamestbc'))]"
},
"apiVersion": "[variables('networkApiVersion')]",
"location": "[resourceGroup().location]",
"comments": "Virtual Network",
"properties": {
"addressSpace": {
"addressPrefixes": [
"[concat(variables('VNetPrefixes')[copyIndex()],'.0.0/22')]"
]
},
"subnets": [
{
"name": "[concat(variables('subnetName'),'0')]",
"properties": {
"addressPrefix": "[concat(variables('VNetPrefixes')[copyIndex()],'.0.0/24')]"
}
}
]
}
},
{ "type": "Microsoft.Network/virtualNetworks/subnets",
"apiVersion": "[variables('networkApiVersion')]",
"location": "[resourceGroup().location]",
"comments": "Virtual Network Subnet for VNet01",
"name": "az104-06-vnet01/subnet1",
"properties": {
"addressPrefix": "10.60.1.0/24"
},
"dependsOn": [
"Microsoft.Network/virtualNetworks/az104-06-vnet01"
]
},
{
"name": "[concat(variables('nic'),copyIndex())]",
"copy":{
"name": "nicCopy",
"count": "[parameters('vmCount')]"
},
"type": "Microsoft.Network/networkInterfaces",
"apiVersion": "[variables('networkApiVersion')]",
"location": "[resourceGroup().location]",
"comments": "Primary NIC",
"dependsOn": [
"[variables('nsgNames')[copyindex()]]",
"[concat('Microsoft.Network/virtualNetworks/', variables('virtualNetworkNames')[copyIndex()])]"
],
"properties": {
"ipConfigurations": [
{
"name": "ipconfig1",
"properties": {
"subnet": {
"id": "[resourceId('Microsoft.Network/virtualNetworks/subnets', variables('virtualNetworkNames')[copyIndex()], concat(variables('subnetName'),variables('subnetRefs')[copyindex()]))]"
},
"privateIPAllocationMethod": "Dynamic"
}
}
],
"networkSecurityGroup": {
"id": "[resourceId('Microsoft.Network/networkSecurityGroups', variables('nsgNames')[copyIndex()])]"
}
}
},
{
"name": "[variables('nsgNamestbc')[copyIndex()]]",
"copy": {
"name": "nsgCopy",
"count": 3
},
"type": "Microsoft.Network/networkSecurityGroups",
"apiVersion": "[variables('networkApiVersion')]",
"location": "[resourceGroup().location]",
"comments": "Network Security Group (NSG) for Primary NIC",
"properties": {
"securityRules": [
{
"name": "default-allow-rdp",
"properties": {
"priority": 1000,
"sourceAddressPrefix": "*",
"protocol": "Tcp",
"destinationPortRange": "3389",
"access": "Allow",
"direction": "Inbound",
"sourcePortRange": "*",
"destinationAddressPrefix": "*"
}
},
{
"name": "default-allow-http",
"properties": {
"priority": 1100,
"sourceAddressPrefix": "*",
"protocol": "Tcp",
"destinationPortRange": "80",
"access": "Allow",
"direction": "Inbound",
"sourcePortRange": "*",
"destinationAddressPrefix": "*"
}
}
]
}
}
],
"outputs": {}
}

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

@ -45,27 +45,27 @@ In this task, you will create a virtual network with multiple subnets by using t
| Resource Group | the name of a **new** resource group **az104-04-rg1** |
| Name | **az104-04-vnet1** |
| Region | the name of any Azure region available in the subscription you will use in this lab |
1. Click **Next : IP Addresses** and enter the following values
| Setting | Value |
| --- | --- |
| --- | --- |
| IPv4 address space | **10.40.0.0/20** |
1. Click **+ Add subnet** enter the following values then click **Add**
| Setting | Value |
| --- | --- |
| --- | --- |
| Subnet name | **subnet0** |
| Subnet address range | **10.40.0.0/24** |
| Subnet address range | **10.40.0.0/24** |
1. Accept the defaults and click **Review and Create**. Let validation occur, and hit **Create** again to submit your deployment.
>**Note:** Wait for the virtual network to be provisioned. This should take less than a minute.
1. Click on **Go to resource**
1. On the **az104-04-vnet1** virtual network blade, click **Subnets** and then click **+ Subnet**.
1. On the **az104-04-vnet1** virtual network blade, click **Subnets** and then click **+ Subnet**.
1. Create a subnet with the following settings (leave others with their default values):
@ -75,7 +75,7 @@ In this task, you will create a virtual network with multiple subnets by using t
| Address range (CIDR block) | **10.40.1.0/24** |
| Network security group | **None** |
| Route table | **None** |
1. Click **Save**
#### Task 2: Deploy virtual machines into the virtual network
@ -84,11 +84,11 @@ In this task, you will deploy Azure virtual machines into different subnets of t
1. In the Azure portal, open the **Azure Cloud Shell** by clicking on the icon in the top right of the Azure Portal.
1. If prompted to select either **Bash** or **PowerShell**, select **PowerShell**.
1. If prompted to select either **Bash** or **PowerShell**, select **PowerShell**.
>**Note**: If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and click **Create storage**.
>**Note**: If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and click **Create storage**.
1. In the toolbar of the Cloud Shell pane, click the **Upload/Download files** icon, in the drop-down menu, click **Upload** and upload the files **\\Allfiles\\Labs\\04\\az104-04-vms-template.json** and **\\Allfiles\\Labs\\04\\az104-04-vms-parameters.json** into the Cloud Shell home directory.
1. In the toolbar of the Cloud Shell pane, click the **Upload/Download files** icon, in the drop-down menu, click **Upload** and upload the files **\\Allfiles\\Labs\\04\\az104-04-vms-loop-template.json** and **\\Allfiles\\Labs\\04\\az104-04-vms-loop-parameters.json** into the Cloud Shell home directory.
>**Note**: You might need to upload each file separately.
@ -99,8 +99,8 @@ In this task, you will deploy Azure virtual machines into different subnets of t
New-AzResourceGroupDeployment `
-ResourceGroupName $rgName `
-TemplateFile $HOME/az104-04-vms-template.json `
-TemplateParameterFile $HOME/az104-04-vms-parameters.json
-TemplateFile $HOME/az104-04-vms-loop-template.json `
-TemplateParameterFile $HOME/az104-04-vms-loop-parameters.json
```
>**Note**: This method of deploying ARM templates uses Azure PowerShell. You can perform the same task by running the equivalent Azure CLI command **az deployment create** (for more information, refer to [Deploy resources with Resource Manager templates and Azure CLI](https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deploy-cli).
@ -121,7 +121,7 @@ In this task, you will configure static assignment of public and private IP addr
1. On the **az104-04-vnet1** virtual network blade, review the **Connected devices** section and verify that there are two network interfaces **az104-04-nic0** and **az104-04-nic1** attached to the virtual network.
1. Click **az104-04-nic0** and, on the **az104-04-nic0** blade, click **IP configurations**.
1. Click **az104-04-nic0** and, on the **az104-04-nic0** blade, click **IP configurations**.
>**Note**: Verify that **ipconfig1** is currently set up with a dynamic private IP address.
@ -138,9 +138,9 @@ In this task, you will configure static assignment of public and private IP addr
1. Back on the **ipconfig1** blade, save the changes.
1. Navigate back to the **az104-04-vnet1** blade
1. Navigate back to the **az104-04-vnet1** blade
1. Click **az104-04-nic1** and, on the **az104-04-nic1** blade, click **IP configurations**.
1. Click **az104-04-nic1** and, on the **az104-04-nic1** blade, click **IP configurations**.
>**Note**: Verify that **ipconfig1** is currently set up with a dynamic private IP address.
@ -161,8 +161,7 @@ In this task, you will configure static assignment of public and private IP addr
1. Navigate back to the **az104-04-rg1** resource group blade, in the list of its resources, click **az104-04-vm1**, and from the **az104-04-vm1** virtual machine blade, note the public IP address entry.
>**Note**: You will need both IP addresses in the last task of this lab.
>**Note**: You will need both IP addresses in the last task of this lab.
#### Task 4: Configure network security groups
@ -186,14 +185,14 @@ In this task, you will configure network security groups in order to allow for r
| Resource Group | **az104-04-rg1** |
| Name | **az104-04-nsg01** |
| Region | the name of the Azure region where you deployed all other resources in this lab |
1. Click **Review and Create**. Let validation occur, and hit **Create** to submit your deployment.
1. Click **Review and Create**. Let validation occur, and hit **Create** to submit your deployment.
>**Note**: Wait for the deployment to complete. This should take about 2 minutes.
1. On the deployment blade, click **Go to resource** to open the **az104-04-nsg01** network security group blade.
1. On the deployment blade, click **Go to resource** to open the **az104-04-nsg01** network security group blade.
1. On the **az104-04-nsg01** network security group blade, in the **Settings** section, click **Inbound security rules**.
1. On the **az104-04-nsg01** network security group blade, in the **Settings** section, click **Inbound security rules**.
1. Add an inbound rule with the following settings (leave others with their default values):
@ -240,12 +239,12 @@ In this task, you will configure DNS name resolution within a virtual network by
| Subscription | the name of the Azure subscription you are using in this lab |
| Resource Group | **az104-04-rg1** |
| Name | **contoso.org** |
1. Click Review and Create. Let validation occur, and hit Create again to submit your deployment.
1. Click Review and Create. Let validation occur, and hit Create again to submit your deployment.
>**Note**: Wait for the private DNS zone to be created. This should take about 2 minutes.
1. Click **Go to resource** to open the **contoso.org** DNS private zone blade.
1. Click **Go to resource** to open the **contoso.org** DNS private zone blade.
1. On the **contoso.org** private DNS zone blade, in the **Settings** section, click **Virtual network links**
@ -257,8 +256,8 @@ In this task, you will configure DNS name resolution within a virtual network by
| Subscription | the name of the Azure subscription you are using in this lab |
| Virtual network | **az104-04-vnet1** |
| Enable auto registration | enabled |
1. Click **OK**.
1. Click **OK**.
>**Note:** Wait for the virtual network link to be created. This should take less than 1 minute.
@ -275,15 +274,16 @@ In this task, you will configure DNS name resolution within a virtual network by
```powershell
nslookup az104-04-vm1.contoso.org
```
1. Verify that the output of the command includes the private IP address of **az104-04-vm1** (**10.40.1.4**).
#### Task 6: Configure Azure DNS for external name resolution
In this task, you will configure external DNS name resolution by using Azure public DNS zones.
1. In the web browser, open a new tab and navigate to https://www.godaddy.com/domains/domain-name-search.
1. In the web browser, open a new tab and navigate to <https://www.godaddy.com/domains/domain-name-search>.
1. Use the domain name search to identify a domain name which is not in use.
1. Use the domain name search to identify a domain name which is not in use.
1. In the Azure portal, search for and select **DNS zones** and, on the **DNS zones** blade, click **+ Add**.
@ -294,10 +294,10 @@ In this task, you will configure external DNS name resolution by using Azure pub
| Subscription | the name of the Azure subscription you are using in this lab |
| Resource Group | **az104-04-rg1** |
| Name | the DNS domain name you identified earlier in this task |
1. Click Review and Create. Let validation occur, and hit Create again to submit your deployment.
>**Note**: Wait for the DNS zone to be created. This should take about 2 minutes.
1. Click Review and Create. Let validation occur, and hit Create again to submit your deployment.
>**Note**: Wait for the DNS zone to be created. This should take about 2 minutes.
1. Click **Go to resource** to open the blade of the newly created DNS zone.
@ -313,7 +313,7 @@ In this task, you will configure external DNS name resolution by using Azure pub
| TTL | **1** |
| TTL unit | **Hours** |
| IP address | the public IP address of **az104-04-vm0** which you identified in the third exercise of this lab |
1. Click **OK**
1. On the DNS zone blade, click **+ Record set**.
@ -328,25 +328,27 @@ In this task, you will configure external DNS name resolution by using Azure pub
| TTL | **1** |
| TTL unit | **Hours** |
| IP address | the public IP address of **az104-04-vm1** which you identified in the third exercise of this lab |
1. Click **OK**
1. Click **OK**
1. On the DNS zone blade, note the name of the **Name server 1** entry.
1. In the Azure portal, open the **PowerShell** session in **Cloud Shell** by clicking on the icon in the top right of the Azure Portal.
1. From the Cloud Shell pane, run the following to test external name resolution of the **az104-04-vm0** DNS record set in the the newly created DNS zone (replace the placeholder `[Name server 1]` with the name of **Name server 1** you noted earlier in this task and the `[domain name] placeholder with the name of the DNS domain you created earlier in this task):
1. From the Cloud Shell pane, run the following to test external name resolution of the **az104-04-vm0** DNS record set in the the newly created DNS zone (replace the placeholder `[Name server 1]` with the name of **Name server 1** you noted earlier in this task and the `[domain name]` placeholder with the name of the DNS domain you created earlier in this task):
```powershell
nslookup az104-04-vm0.[domain name] [Name server 1]
```
1. Verify that the output of the command includes the public IP address of **az104-04-vm0**.
1. From the Cloud Shell pane, run the following to test external name resolution of the **az104-04-vm1** DNS record set in the the newly created DNS zone (replace the placeholder `[Name server 1]` with the name of **Name server 1** you noted earlier in this task and the `[domain name] placeholder with the name of the DNS domain you created earlier in this task):
1. From the Cloud Shell pane, run the following to test external name resolution of the **az104-04-vm1** DNS record set in the the newly created DNS zone (replace the placeholder `[Name server 1]` with the name of **Name server 1** you noted earlier in this task and the `[domain name]` placeholder with the name of the DNS domain you created earlier in this task):
```powershell
nslookup az104-04-vm1.[domain name] [Name server 1]
```
1. Verify that the output of the command includes the public IP address of **az104-04-vm1**.
#### Clean up resources
@ -373,9 +375,9 @@ In this task, you will configure external DNS name resolution by using Azure pub
In this lab, you have:
- Created and configured a virtual network
- Deployed virtual machines into the virtual network
- Configured private and public IP addresses of Azure VMs
- Configured network security groups
- Configured Azure DNS for internal name resolution
- Configured Azure DNS for external name resolution
+ Created and configured a virtual network
+ Deployed virtual machines into the virtual network
+ Configured private and public IP addresses of Azure VMs
+ Configured network security groups
+ Configured Azure DNS for internal name resolution
+ Configured Azure DNS for external name resolution

100
Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.md
View File

@ -9,7 +9,7 @@ lab:
## Lab scenario
Contoso has its datacenters in Boston, New York, and Seattle offices connected via a mesh wide-area network links, with full connectivity between them. You need to implement a lab environment that will reflect the topology of the Contoso's on-premises networks and verify its functionality.
Contoso has its datacenters in Boston, New York, and Seattle offices connected via a mesh wide-area network links, with full connectivity between them. You need to implement a lab environment that will reflect the topology of the Contoso's on-premises networks and verify its functionality.
## Objectives
@ -17,7 +17,7 @@ In this lab, you will:
+ Task 1: Provision the lab environment
+ Task 2: Configure local and global virtual network peering
+ Task 3: Test intersite connectivity
+ Task 3: Test intersite connectivity
## Estimated timing: 30 minutes
@ -25,78 +25,47 @@ In this lab, you will:
#### Task 1: Provision the lab environment
In this task, you will deploy three virtual machines, each into a separate virtual network, with two of them in the same Azure region and the third one in another Azure region.
In this task, you will deploy three virtual machines, each into a separate virtual network, with two of them in the same Azure region and the third one in another Azure region.
1. Sign in to the [Azure portal](https://portal.azure.com).
1. In the Azure portal, open the **Azure Cloud Shell** by clicking on the icon in the top right of the Azure Portal.
1. If prompted to select either **Bash** or **PowerShell**, select **PowerShell**.
1. If prompted to select either **Bash** or **PowerShell**, select **PowerShell**.
>**Note**: If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and click **Create storage**.
>**Note**: If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and click **Create storage**.
1. In the toolbar of the Cloud Shell pane, click the **Upload/Download files** icon, in the drop-down menu, click **Upload** and upload the files **\\Allfiles\\Labs\\05\\az104-05-vnetvm-template.json** and **\\Allfiles\\Labs\\05\\az104-05-vnetvm-parameters.json** into the Cloud Shell home directory.
1. In the toolbar of the Cloud Shell pane, click the **Upload/Download files** icon, in the drop-down menu, click **Upload** and upload the files **\\Allfiles\\Labs\\05\\az104-05-vnetvm-loop-template.json** and **\\Allfiles\\Labs\\05\\az104-05-vnetvm-loop-parameters.json** into the Cloud Shell home directory.
1. From the Cloud Shell pane, run the following to create the first resource group that will be hosting the first virtual network and the pair of virtual machines (replace the `[Azure_region_1]` placeholder with the name of an Azure region where you intend to deploy these Azure virtual machines):
1. From the Cloud Shell pane, run the following to create the resource group that will be hosting the lab environment. The first two virtual networks and a pair of virtual machines will be deployed in `[Azure_region_1]`. The third virtual network and the third virtual machine will be deployed in the same resource group but another `[Azure_region_2]`. (replace the `[Azure_region_1]` and `[Azure_region_2]` placeholder with the names of two different Azure regions where you intend to deploy these Azure virtual machines):
```powershell
$location = '[Azure_region_1]'
$location1 = '[Azure_region_1]'
$rgName = 'az104-05-rg0'
$location2 = '[Azure_region_2]'
New-AzResourceGroup -Name $rgName -Location $location
```
>**Note**: In order to identify Azure regions, from a PowerShell session in Cloud Shell, run **(Get-AzLocation).Location**
1. From the Cloud Shell pane, run the following to create the first virtual network and deploy a virtual machine into it by using the template and parameter files you uploaded:
```powershell
New-AzResourceGroupDeployment `
-ResourceGroupName $rgName `
-TemplateFile $HOME/az104-05-vnetvm-template.json `
-TemplateParameterFile $HOME/az104-05-vnetvm-parameters.json `
-nameSuffix 0 `
-AsJob
```
1. From the Cloud Shell pane, run the following to create the second resource group that will be hosting the second virtual network and the second virtual machine
```powershell
$rgName = 'az104-05-rg1'
New-AzResourceGroup -Name $rgName -Location $location
New-AzResourceGroup -Name $rgName -Location $location1
```
1. From the Cloud Shell pane, run the following to create the second virtual network and deploy a virtual machine into it by using the template and parameter files you uploaded:
>**Note**: In order to identify Azure regions, from a PowerShell session in Cloud Shell, run **(Get-AzLocation).Location**
1. From the Cloud Shell pane, run the following to create the three virtual networks and deploy virtual machines into them by using the template and parameter files you uploaded:
```powershell
New-AzResourceGroupDeployment `
-ResourceGroupName $rgName `
-TemplateFile $HOME/az104-05-vnetvm-template.json `
-TemplateParameterFile $HOME/az104-05-vnetvm-parameters.json `
-nameSuffix 1 `
-TemplateFile $HOME/az104-05-vnetvm-loop-template.json `
-TemplateParameterFile $HOME/az104-05-vnetvm-loop-parameters.json `
-location1 $location1 `
-location2 $location2 `
-AsJob
```
1. From the Cloud Shell pane, run the following to create the third resource group that will be hosting the third virtual network and the third virtual machine (replace the `[Azure_region_2]` placeholder with the name of another Azure region where you can deploy Azure virtual machines, different from the Azure region you used for the other two deployments):
```powershell
$location = '[Azure_region_2]'
>**Note**: Wait for the deployment to complete before proceeding to the next task. This should take about 2 minutes.
$rgName = 'az104-05-rg2'
New-AzResourceGroup -Name $rgName -Location $location
```
1. From the Cloud Shell pane, run the following to create the third virtual network and deploy a virtual machine into it by using the template and parameter files you uploaded:
```powershell
New-AzResourceGroupDeployment `
-ResourceGroupName $rgName `
-TemplateFile $HOME/az104-05-vnetvm-template.json `
-TemplateParameterFile $HOME/az104-05-vnetvm-parameters.json `
-nameSuffix 2 `
-AsJob
```
>**Note**: Wait for the deployments to complete before proceeding to the next task. This should take about 2 minutes.
>**Note**: To verify the status of the deployments, you can examine the properties of the resource groups you created in this task.
>**Note**: To verify the status of the deployment, you can examine the properties of the resource group you created in this task.
1. Close the Cloud Shell pane.
@ -106,7 +75,7 @@ In this task, you will configure local and global peering between the virtual ne
1. In the Azure portal, search for and select **Virtual networks**.
1. Review the virtual networks you created in the previous task and verify that the first two are located in the same Azure region and the third one in a different Azure region.
1. Review the virtual networks you created in the previous task and verify that the first two are located in the same Azure region and the third one in a different Azure region.
>**Note**: The template you used for deployment of the three virtual networks ensures that the IP address ranges of the three virtual networks do not overlap.
@ -122,7 +91,7 @@ In this task, you will configure local and global peering between the virtual ne
| This virtual network: Traffic to remote virtual network | **Allow (default)** |
| This virtual network: Traffic forwarded from remote virtual network | **Block traffic that originates from outside this virtual network** |
| Virtual network gateway | **None** |
| Remote virtual network: Peering link name | **az104-05-vnet1_to_az104-05-vnet0** |
| Remote virtual network: Peering link name | **az104-05-vnet1_to_az104-05-vnet0** |
| Virtual network deployment model | **Resource manager** |
| I know my resource ID | unselected |
| Subscription | the name of the Azure subscription you are using in this lab |
@ -143,7 +112,7 @@ In this task, you will configure local and global peering between the virtual ne
| This virtual network: Traffic to remote virtual network | **Allow (default)** |
| This virtual network: Traffic forwarded from remote virtual network | **Block traffic that originates from outside this virtual network** |
| Virtual network gateway | **None** |
| Remote virtual network: Peering link name | **az104-05-vnet2_to_az104-05-vnet0** |
| Remote virtual network: Peering link name | **az104-05-vnet2_to_az104-05-vnet0** |
| Virtual network deployment model | **Resource manager** |
| I know my resource ID | unselected |
| Subscription | the name of the Azure subscription you are using in this lab |
@ -151,7 +120,7 @@ In this task, you will configure local and global peering between the virtual ne
| Traffic to remote virtual network | **Allow (default)** |
| Traffic forwarded from remote virtual network | **Block traffic that originates from outside this virtual network** |
| Virtual network gateway | **None** |
>**Note**: This step establishes two global peerings - one from az104-05-vnet0 to az104-05-vnet2 and the other from az104-05-vnet2 to az104-05-vnet0.
1. Navigate back to the **Virtual networks** blade and, in the list of virtual networks, click **az104-05-vnet1**.
@ -166,7 +135,7 @@ In this task, you will configure local and global peering between the virtual ne
| This virtual network: Traffic to remote virtual network | **Allow (default)** |
| This virtual network: Traffic forwarded from remote virtual network | **Block traffic that originates from outside this virtual network** |
| Virtual network gateway | **None** |
| Remote virtual network: Peering link name | **az104-05-vnet2_to_az104-05-vnet1** |
| Remote virtual network: Peering link name | **az104-05-vnet2_to_az104-05-vnet1** |
| Virtual network deployment model | **Resource manager** |
| I know my resource ID | unselected |
| Subscription | the name of the Azure subscription you are using in this lab |
@ -174,10 +143,10 @@ In this task, you will configure local and global peering between the virtual ne
| Traffic to remote virtual network | **Allow (default)** |
| Traffic forwarded from remote virtual network | **Block traffic that originates from outside this virtual network** |
| Virtual network gateway | **None** |
>**Note**: This step establishes two global peerings - one from az104-05-vnet1 to az104-05-vnet2 and the other from az104-05-vnet2 to az104-05-vnet1.
#### Task 3: Test intersite connectivity
#### Task 3: Test intersite connectivity
In this task, you will test connectivity between virtual machines on the three virtual networks that you connected via local and global peering in the previous task.
@ -200,7 +169,8 @@ In this task, you will test connectivity between virtual machines on the three v
```powershell
Test-NetConnection -ComputerName 10.51.0.4 -Port 3389 -InformationLevel 'Detailed'
```
>**Note**: The test uses TCP 3389 since this is this port is allowed by default by operating system firewall.
>**Note**: The test uses TCP 3389 since this is this port is allowed by default by operating system firewall.
1. Examine the output of the command and verify that the connection was successful.
@ -209,7 +179,8 @@ In this task, you will test connectivity between virtual machines on the three v
```powershell
Test-NetConnection -ComputerName 10.52.0.4 -Port 3389 -InformationLevel 'Detailed'
```
1. Switch back to the Azure portal on your lab computer and navigate back to the **Virtual machines** blade.
1. Switch back to the Azure portal on your lab computer and navigate back to the **Virtual machines** blade.
1. In the list of virtual machines, click **az104-05-vm1**.
@ -228,7 +199,8 @@ In this task, you will test connectivity between virtual machines on the three v
```powershell
Test-NetConnection -ComputerName 10.52.0.4 -Port 3389 -InformationLevel 'Detailed'
```
>**Note**: The test uses TCP 3389 since this is this port is allowed by default by operating system firewall.
>**Note**: The test uses TCP 3389 since this is this port is allowed by default by operating system firewall.
1. Examine the output of the command and verify that the connection was successful.
@ -256,6 +228,6 @@ In this task, you will test connectivity between virtual machines on the three v
In this lab, you have:
- Provisioned the lab environment
- Configured local and global virtual network peering
- Tested intersite connectivity
+ Provisioned the lab environment
+ Configured local and global virtual network peering
+ Tested intersite connectivity

125
Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md
View File

@ -11,7 +11,7 @@ lab:
You were tasked with testing managing network traffic targeting Azure virtual machines in the hub and spoke network topology, which Contoso considers implementing in its Azure environment (instead of creating the mesh topology, which you tested in the previous lab). This testing needs to include implementing connectivity between spokes by relying on user defined routes that force traffic to flow via the hub, as well as traffic distribution across virtual machines by using layer 4 and layer 7 load balancers. For this purpose, you intend to use Azure Load Balancer (layer 4) and Azure Application Gateway (layer 7).
>**Note**: This lab, by default, requires total of 8 vCPUs available in the Standard_Dsv3 series in the region you choose for deployment, since it involves deployment of four Azure VMs of Standard_D2s_v3 SKU. If your students are using trial accounts, with the limit of 4 vCPUs, you can use a VM size that requires only one vCPU (such as Standard_B1s).
>**Note**: This lab, by default, requires total of 8 vCPUs available in the Standard_Dsv3 series in the region you choose for deployment, since it involves deployment of four Azure VMs of Standard_D2s_v3 SKU. If your students are using trial accounts, with the limit of 4 vCPUs, you can use a VM size that requires only one vCPU (such as Standard_B1s).
## Objectives
@ -32,19 +32,19 @@ In this lab, you will:
#### Task 1: Provision the lab environment
In this task, you will deploy four virtual machines into the same Azure region. The first two will reside in a hub virtual network, while each of the remaining to will reside in a separate spoke virtual network.
In this task, you will deploy four virtual machines into the same Azure region. The first two will reside in a hub virtual network, while each of the remaining two will reside in a separate spoke virtual network.
1. Sign in to the [Azure portal](https://portal.azure.com).
1. In the Azure portal, open the **Azure Cloud Shell** by clicking on the icon in the top right of the Azure Portal.
1. If prompted to select either **Bash** or **PowerShell**, select **PowerShell**.
1. If prompted to select either **Bash** or **PowerShell**, select **PowerShell**.
>**Note**: If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and click **Create storage**.
>**Note**: If this is the first time you are starting **Cloud Shell** and you are presented with the **You have no storage mounted** message, select the subscription you are using in this lab, and click **Create storage**.
1. In the toolbar of the Cloud Shell pane, click the **Upload/Download files** icon, in the drop-down menu, click **Upload** and upload the files **\\Allfiles\\Labs\\06\\az104-06-vms-template.json**, **\\Allfiles\\Labs\\06\\az104-06-vm-template.json**, and **\\Allfiles\\Labs\\06\\az104-06-vm-parameters.json** into the Cloud Shell home directory.
1. In the toolbar of the Cloud Shell pane, click the **Upload/Download files** icon, in the drop-down menu, click **Upload** and upload the files **\\Allfiles\\Labs\\06\\az104-06-vms-loop-template.json** and **\\Allfiles\\Labs\\06\\az104-06-vms-loop-parameters.json** into the Cloud Shell home directory.
1. From the Cloud Shell pane, run the following to create the first resource group that will be hosting the first virtual network and the pair of virtual machines (replace the `[Azure_region]` placeholder with the name of an Azure region where you intend to deploy Azure virtual machines)(you can use the "(Get-AzLocation).Location" cmdlet to get the region list):
1. From the Cloud Shell pane, run the following to create the first resource group that will be hosting the lab environment (replace the `[Azure_region]` placeholder with the name of an Azure region where you intend to deploy Azure virtual machines)(you can use the "(Get-AzLocation).Location" cmdlet to get the region list):
```powershell
$location = '[Azure_region]'
@ -53,53 +53,20 @@ In this task, you will deploy four virtual machines into the same Azure region.
New-AzResourceGroup -Name $rgName -Location $location
```
1. From the Cloud Shell pane, run the following to create the first virtual network and deploy a pair of virtual machines into it by using the template and parameter files you uploaded:
1. From the Cloud Shell pane, run the following to create the three virtual networks and four virtual machines into them by using the template and parameter files you uploaded:
```powershell
New-AzResourceGroupDeployment `
-ResourceGroupName $rgName `
-TemplateFile $HOME/az104-06-vms-template.json `
-TemplateParameterFile $HOME/az104-06-vm-parameters.json `
-TemplateFile $HOME/az104-06-vms-loop-template.json `
-TemplateParameterFile $HOME/az104-06-vms-loop-parameters.json `
-AsJob
```
1. From the Cloud Shell pane, run the following to create the second resource group that will be hosting the second virtual network and the third virtual machine
>**Note**: Wait for the deployment to complete before proceeding to the next task. This should take about 5 minutes.
```powershell
$rgName = 'az104-06-rg2'
New-AzResourceGroup -Name $rgName -Location $location
```
1. From the Cloud Shell pane, run the following to create the second virtual network and deploy a virtual machine into it by using the template and parameter files you uploaded:
```powershell
New-AzResourceGroupDeployment `
-ResourceGroupName $rgName `
-TemplateFile $HOME/az104-06-vm-template.json `
-TemplateParameterFile $HOME/az104-06-vm-parameters.json `
-nameSuffix 2 `
-AsJob
```
1. From the Cloud Shell pane, run the following to create the third resource group that will be hosting the third virtual network and the fourth virtual machine:
```powershell
$rgName = 'az104-06-rg3'
New-AzResourceGroup -Name $rgName -Location $location
```
1. From the Cloud Shell pane, run the following to create the third virtual network and deploy a virtual machine into it by using the template and parameter files you uploaded:
```powershell
New-AzResourceGroupDeployment `
-ResourceGroupName $rgName `
-TemplateFile $HOME/az104-06-vm-template.json `
-TemplateParameterFile $HOME/az104-06-vm-parameters.json `
-nameSuffix 3 `
-AsJob
```
>**Note**: Wait for the deployments to complete before proceeding to the next task. This should take about 5 - 15 minutes.
>**Note**: To verify the status of the deployments, you can examine the properties of the resource groups you created in this task.
>**Note**: To verify the status of the deployment, you can examine the properties of the resource group you created in this task.
1. Close the Cloud Shell pane.
@ -109,7 +76,7 @@ In this task, you will configure local peering between the virtual networks you
1. In the Azure portal, search for and select **Virtual networks**.
1. Review the virtual networks you created in the previous task.
1. Review the virtual networks you created in the previous task.
>**Note**: The template you used for deployment of the three virtual networks ensures that the IP address ranges of the three virtual networks do not overlap.
@ -128,11 +95,11 @@ In this task, you will configure local peering between the virtual networks you
| Remote virtual network: Peering link name | **az104-06-vnet2_to_az104-06-vnet01** |
| Virtual network deployment model | **Resource manager** |
| Subscription | the name of the Azure subscription you are using in this lab |
| Virtual network | **az104-06-vnet2** |
| Virtual network | **az104-06-vnet2** |
| Traffic to remote virtual network | **Allow (default)** |
| Traffic forwarded from remote virtual network | **Allow (default)** |
| Virtual network gateway | **None (default)** |
>**Note**: Wait for the operation to complete.
>**Note**: This step establishes two local peerings - one from az104-06-vnet01 to az104-06-vnet2 and the other from az104-06-vnet2 to az104-06-vnet01.
@ -216,7 +183,7 @@ In this task, you will test transitivity of virtual network peering by using Net
| Setting | Value |
| --- | --- |
| Subscription | the name of the Azure subscription you are using in this lab |
| Resource group | **az104-06-rg2** |
| Resource group | **az104-06-rg1** |
| Source type | **Virtual machine** |
| Virtual machine | **az104-06-vm2** |
| Destination | **Specify manually** |
@ -224,7 +191,7 @@ In this task, you will test transitivity of virtual network peering by using Net
| Protocol | **TCP** |
| Destination Port | **3389** |
1. Click **Check** and wait until results of the connectivity check are returned. Note that the status is **Unreachable**.
1. Click **Check** and wait until results of the connectivity check are returned. Note that the status is **Unreachable**.
> **Note**: This is expected, since the two spoke virtual networks are not peered with each other (virtual network peering is not transitive).
@ -238,9 +205,9 @@ In this task, you will configure and test routing between the two spoke virtual
1. On the **az104-06-vm0** virtual machine blade, in the **Settings** section, click **Networking**.
1. Click the **az104-06-nic0** link next to the **Network interface** label, and then, on the **az104-06-nic0** network interface blade, in the **Settings** section, click **IP configurations**.
1. Click the **az104-06-nic0** link next to the **Network interface** label, and then, on the **az104-06-nic0** network interface blade, in the **Settings** section, click **IP configurations**.
1. Set **IP forwarding** to **Enabled** and save the change.
1. Set **IP forwarding** to **Enabled** and save the change.
> **Note**: This setting is required in order for **az104-06-vm0** to function as a router, which will route traffic between two spoke virtual networks.
@ -281,12 +248,12 @@ In this task, you will configure and test routing between the two spoke virtual
| Setting | Value |
| --- | --- |
| Subscription | the name of the Azure subscription you are using in this lab |
| Resource group | **az104-06-rg2** |
| Resource group | **az104-06-rg1** |
| Location | the name of the Azure region in which you created the virtual networks |
| Name | **az104-06-rt23** |
| Propagate gateway routes | **No** |
1. Click **Review and Create**. Let validation occur, and click **Create** to submit your deployment.
1. Click **Review and Create**. Let validation occur, and click **Create** to submit your deployment.
> **Note**: Wait for the route table to be created. This should take about 3 minutes.
@ -302,7 +269,7 @@ In this task, you will configure and test routing between the two spoke virtual
| Address prefix | **10.63.0.0/20** |
| Next hop type | **Virtual appliance** |
| Next hop address | **10.60.0.4** |
1. Click **OK**
1. Back on the **az104-06-rt23** route table blade, in the **Settings** section, click **Subnets**, and then click **+ Associate**.
@ -313,8 +280,8 @@ In this task, you will configure and test routing between the two spoke virtual
| --- | --- |
| Virtual network | **az104-06-vnet2** |
| Subnet | **subnet0** |
1. Click **OK**
1. Click **OK**
1. Navigate back to **Route tables** blade and click **+ Add**.
@ -323,13 +290,13 @@ In this task, you will configure and test routing between the two spoke virtual
| Setting | Value |
| --- | --- |
| Subscription | the name of the Azure subscription you are using in this lab |
| Resource group | **az104-06-rg3** |
| Resource group | **az104-06-rg1** |
| Region | the name of the Azure region in which you created the virtual networks |
| Name | **az104-06-rt32** |
| Propagate gateway routes | **No** |
1. Click Review and Create. Let validation occur, and hit Create to submit your deployment.
> **Note**: Wait for the route table to be created. This should take about 3 minutes.
1. Back on the **Route tables** blade, click **Refresh** and then click **az104-06-rt32**.
@ -344,7 +311,7 @@ In this task, you will configure and test routing between the two spoke virtual
| Address prefix | **10.62.0.0/20** |
| Next hop type | **Virtual appliance** |
| Next hop address | **10.60.0.4** |
1. Click **OK**
1. Back on the **az104-06-rt32** route table blade, in the **Settings** section, click **Subnets**, and then click **+ Associate**.
@ -355,7 +322,7 @@ In this task, you will configure and test routing between the two spoke virtual
| --- | --- |
| Virtual network | **az104-06-vnet3** |
| Subnet | **subnet0** |
1.Click **OK**
1. In the Azure portal, navigate back to the **Network Watcher - Connection troubleshoot** blade.
@ -365,7 +332,7 @@ In this task, you will configure and test routing between the two spoke virtual
| Setting | Value |
| --- | --- |
| Subscription | the name of the Azure subscription you are using in this lab |
| Resource group | **az104-06-rg2** |
| Resource group | **az104-06-rg1** |
| Source type | **Virtual machine** |
| Virtual machine | **az104-06-vm2** |
| Destination | **Specify manually** |
@ -375,8 +342,7 @@ In this task, you will configure and test routing between the two spoke virtual
1. Click **Check** and wait until results of the connectivity check are returned. Verify that the status is **Reachable**. Review the network path and note that the traffic was routed via **10.60.0.4**, assigned to the **az104-06-nic0** network adapter. If status is **Unreachable**, you should restart az104-06-vm0.
> **Note**: This is expected, since the traffic between spoke virtual networks is now routed via the virtual machine located in the hub virtual network, which functions as a router.
> **Note**: This is expected, since the traffic between spoke virtual networks is now routed via the virtual machine located in the hub virtual network, which functions as a router.
> **Note**: You can use **Network Watcher** to view topology of the network.
@ -398,11 +364,12 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur
| SKU | **Standard** |
| Public IP address | **Create new** |
| Public IP address name | **az104-06-pip4** |
| Availability zone | **No Zone** |
| Add a public IPv6 address | **No** |
1. Click Review and Create. Let validation occur, and hit Create to submit your deployment.
> **Note**: Wait for the Azure load balancer to be provisioned. This should take about 2 minutes.
> **Note**: Wait for the Azure load balancer to be provisioned. This should take about 2 minutes.
1. On the deployment blade, click **Go to resource**.
@ -415,11 +382,11 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur
| Name | **az104-06-lb4-be1** |
| Virtual network | **az104-06-vnet01** |
| IP version | **IPv4** |
| Virtual machine | **az104-06-vm0** |
| Virtual machine | **az104-06-vm0** |
| Virtual machine IP address | **ipconfig1 (10.60.0.4)** |
| Virtual machine | **az104-06-vm1** |
| Virtual machine IP address | **ipconfig1 (10.60.1.4)** |
1. Click **Add**
1. Wait for the backend pool to be created, in the **Settings** section, click **Health probes**, and then click **+ Add**.
@ -433,7 +400,7 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur
| Port | **80** |
| Interval | **5** |
| Unhealthy threshold | **2** |
1. Click **OK**
1. Wait for the health probe to be created, in the **Settings** section, click **Load balancing rules**, and then click **+ Add**.
@ -462,7 +429,7 @@ In this task, you will implement an Azure Load Balancer in front of the two Azur
1. Verify that the browser window displays the message **Hello World from az104-06-vm0** or **Hello World from az104-06-vm1**.
1. Open another browser window but this time by using InPrivate mode and verify whether the target vm changes (as indicated by the message).
1. Open another browser window but this time by using InPrivate mode and verify whether the target vm changes (as indicated by the message).
> **Note**: You might need to refresh the browser window or open it again by using InPrivate mode.
@ -523,7 +490,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw
> **Note**: The targets represent the private IP addresses of virtual machines in the spoke virtual networks **az104-06-vm2** and **az104-06-vm3**.
1. Click **Add**, click **Next: Configuration >** and, on the **Configuration** tab of the **Create an application gateway** blade, click **+ Add a routing rule**.
1. Click **Add**, click **Next: Configuration >** and, on the **Configuration** tab of the **Create an application gateway** blade, click **+ Add a routing rule**.
1. On the **Add a routing rule** blade, on the **Listener** tab, specify the following settings:
@ -536,7 +503,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw
| Port | **80** |
| Listener type | **Basic** |
| Error page url | **No** |
1. Switch to the **Backend targets** tab of the **Add a routing rule** blade and specify the following settings (leave others with their default values):
| Setting | Value |
@ -548,7 +515,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw
| Setting | Value |
| --- | --- |
| HTTP setting | **az104-06-appgw5-http1** |
| HTTP setting | **az104-06-appgw5-http1** |
| Backend protocol | **HTTP** |
| Backend port | **80** |
| Cookie-based affinity | **Disable** |
@ -569,7 +536,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw
1. Verify that the browser window displays the message **Hello World from az104-06-vm2** or **Hello World from az104-06-vm3**.
1. Open another browser window but this time by using InPrivate mode and verify whether the target vm changes (based on the message displayed on the web page).
1. Open another browser window but this time by using InPrivate mode and verify whether the target vm changes (based on the message displayed on the web page).
> **Note**: You might need to refresh the browser window or open it again by using InPrivate mode.
@ -599,9 +566,9 @@ In this task, you will implement an Azure Application Gateway in front of the tw
In this lab, you have:
- Provisioned the lab environment
- Configured the hub and spoke network topology
- Tested transitivity of virtual network peering
+ Provisioned the lab environment
+ Configured the hub and spoke network topology
+ Tested transitivity of virtual network peering
+ Task 4: Configure routing in the hub and spoke topology
+ Task 5: Implement Azure Load Balancer
+ Task 6: Implement Azure Application Gateway