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

Merge pull request #1019 from kbakdev/patch-24

Browse Source 
Refine Azure VM creation instructions
This commit is contained in:
staleycyn 2025-10-21 06:58:32 -07:00 committed by GitHub
commit 9efa03b56f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 25 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -39,7 +39,7 @@ In this task, you create a core services virtual network with a virtual machine.
1. Search for and select `Virtual Machines`.
1. From the virtual machines page, select **Create** then select **Azure Virtual Machine**.
1. From the virtual machines page, select **Create** then select **Virtual machine**.
1. On the Basics tab, use the following information to complete the form, and then select **Next : Disks >**. For any setting not specified, leave the default value.
@ -51,7 +51,7 @@ In this task, you create a core services virtual network with a virtual machine.
| Region | **(US) East US** |
| Availability options | No infrastructure redundancy required |
| Security type | **Standard** |
| Image | **Windows Server 2019 Datacenter: x64 Gen2** (notice your other choices) |
| Image | **Windows Server 2019 Datacenter - x64 Gen2** (notice your other choices) |
| Size | **Standard_DS2_v3** |
| Username | `localadmin` |
| Password | **Provide a complex password** |
@ -72,9 +72,9 @@ In this task, you create a core services virtual network with a virtual machine.
| Subnet Name | `Core` |
| Subnet address range | `10.0.0.0/24` |
1. Select the **Monitoring** tab. For Boot Diagnostics, select **Disable**.
1. Select the **Monitoring** tab. For Boot diagnostics, select **Disable**.
1. Select **Review + Create**, and then select **Create**.
1. Select **Review + create**, and then select **Create**.
1. You do not need to wait for the resources to be created. Continue on to the next task.
@ -86,7 +86,7 @@ In this task, you create a manufacturing services virtual network with a virtual
1. From the Azure portal, search for and navigate to **Virtual Machines**.
1. From the virtual machines page, select **Create** then select **Azure Virtual Machine**.
1. From the virtual machines page, select **Create** then select **Virtual machine**.
1. On the Basics tab, use the following information to complete the form, and then select **Next : Disks >**. For any setting not specified, leave the default value.
@ -98,7 +98,7 @@ In this task, you create a manufacturing services virtual network with a virtual
| Region | **(US) East US** |
| Security type | **Standard** |
| Availability options | No infrastructure redundancy required |
| Image | **Windows Server 2019 Datacenter: x64 Gen2** |
| Image | **Windows Server 2019 Datacenter - x64 Gen2** |
| Size | **Standard_DS2_v3** |
| Username | `localadmin` |
| Password | **Provide a complex password** |
@ -119,7 +119,7 @@ In this task, you create a manufacturing services virtual network with a virtual
1. Select the **Monitoring** tab. For Boot Diagnostics, select **Disable**.
1. Select **Review + Create**, and then select **Create**.
1. Select **Review + create**, and then select **Create**.
## Task 3: Use Network Watcher to test the connection between virtual machines
@ -136,7 +136,7 @@ In this task, you verify that resources in peered virtual networks can communica
| --- | --- |
| Source type | **Virtual machine** |
| Virtual machine | **CoreServicesVM** |
| Destination type | **Virtual machine** |
| Destination type | **Select a virtual machine** |
| Virtual machine | **ManufacturingVM** |
| Preferred IP Version | **Both** |
| Protocol | **TCP** |
@ -148,7 +148,7 @@ In this task, you verify that resources in peered virtual networks can communica
1. Select **Run diagnostic tests**.
>**Note**: It may take a couple of minutes for the results to be returned. The screen selections will be greyed out while the results are being collected. Notice the **Connectivity test** shows **UnReachable**. This makes sense because the virtual machines are in different virtual networks.
>**Note**: It may take a couple of minutes for the results to be returned. The screen selections will be greyed out while the results are being collected. Notice the **Connectivity test** shows **Unreachable**. This makes sense because the virtual machines are in different virtual networks.
## Task 4: Configure virtual network peerings between virtual networks
@ -163,13 +163,13 @@ In this task, you create a virtual network peering to enable communications betw
| **Parameter** | **Value** |
| --------------------------------------------- | ------------------------------------- |
| Peering link name | `CoreServicesVnet-to-ManufacturingVnet` |
| Virtual network | **ManufacturingVM-net (az104-rg5)** |
| Allow ManufacturingVnet to access CoreServicesVnet | selected (default) |
| Allow ManufacturingVnet to receive forwarded traffic from CoreServicesVnet | selected |
| Peering link name | `ManufacturingVnet-to-CoreServicesVnet` |
| Allow CoreServicesVnet to access the peered virtual network | selected (default) |
| Allow CoreServicesVnet to receive forwarded traffic from the peered virtual network | selected |
| Virtual network | **ManufacturingVnet (az104-rg5)** |
| Allow 'CoreServicesVnet' to access 'ManufacturingVnet' | selected (default) |
| Allow 'CoreServicesVnet' to receive forwarded traffic from 'ManufacturingVnet' | selected |
| Peering link name | `CoreServicesVnet-to-ManufacturingVnet` |
| Allow 'ManufacturingVnet' to access 'CoreServicesVnet' | selected (default) |
| Allow 'ManufacturingVnet' to receive forwarded traffic from 'CoreServicesVnet' | selected |
4. Click **Add**.
@ -200,7 +200,7 @@ In this task, you retest the connection between the virtual machines in differen
```Powershell
Test-NetConnection <CoreServicesVM private IP address> -port 3389
```
1. It may take a couple of minutes for the script to time out. The top of the page shows an informational message *Script execution in progress.*
1. It may take a couple of minutes for the script to time out. The top of the page shows an informational message *Script execution in progress...*
1. The test connection should succeed because peering has been configured. Your computer name and remote address in this graphic may be different.
@ -223,7 +223,7 @@ In this task, you want to control network traffic between the perimeter subnet a
1. In the Azure portal, search for and select `Route tables`, select **+ Create**.
1. Enter the following details, select **Review + Create**, and then select **Create**.
1. Enter the following details, select **Review + create**, and then select **Create**.
| Setting | Value |
| --- | --- |
@ -237,7 +237,7 @@ In this task, you want to control network traffic between the perimeter subnet a
1. Select the resource (not the checkbox) **rt-CoreServices**
1. Expand **Settings** then select **Routes** and then **Add**. Create a route from a future Network Virtual Appliance (NVA) to the CoreServices virtual network.
1. Expand **Settings** then select **Routes** and then **+ Add**. Create a route from a future Network Virtual Appliance (NVA) to the CoreServices virtual network.
| Setting | Value |
| --- | --- |
@ -247,13 +247,13 @@ In this task, you want to control network traffic between the perimeter subnet a
| Next hop type | **Virtual appliance** (notice your other choices) |
| Next hop address | `10.0.1.7` (future NVA) |
1. Select **+ Add**. The last thing to do is associate the route with the subnet.
1. Select **Add**. The last thing to do is associate the route with the subnet.
1. Select **Subnets** and then **+ Associate**. Complete the configuration.
| Setting | Value |
| --- | --- |
| Virtual network | **CoreServicesVnet** |
| Virtual network | **CoreServicesVnet (az104-rg5)** |
| Subnet | **Core** |
>**Note**: You have created a user defined route to direct traffic from the DMZ to the new NVA.