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 #975 from awillslo/master

Browse Source 
Update LAB_05-Implement_Intersite_Connectivity.md
This commit is contained in:
staleycyn 2025-05-13 15:02:01 -07:00 committed by GitHub
commit 227a6542ea
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -181,6 +181,8 @@ In this task, you create a virtual network peering to enable communications betw
| Allow CoreServicesVnet to access the peered virtual network | selected (default) |
| Allow CoreServicesVnet to receive forwarded traffic from the peered virtual network | selected |
1. Click **Add**.
1. In CoreServicesVnet | Peerings, verify that the **CoreServicesVnet-to-ManufacturingVnet** peering is listed. Refresh the page to ensure the **Peering status** is **Connected**.
1. Switch to the **ManufacturingVnet** and verify the **ManufacturingVnet-to-CoreServicesVnet** peering is listed. Ensure the **Peering status** is **Connected**. You may need to **Refresh** the page.
@ -221,7 +223,7 @@ In this task, you want to control network traffic between the perimeter subnet a
1. Search for select the `CoreServicesVnet`.
1. Select **Subnets** and then **+ Create**. Be sure to **Save** your changes.
1. Select **Subnets** and then **+ Subnet**. Be sure to select **Add** to save your changes.
| Setting | Value |
| --- | --- |
@ -239,9 +241,11 @@ In this task, you want to control network traffic between the perimeter subnet a
| Name | `rt-CoreServices` |
| Propagate gateway routes | **No** |
1. After the route table deploys, select **Go to resource**.
1. After the route table deploys, Search for and select the **Route Tables**.
1. Select **Routes** and then **+ Add**. Create a route from a future Network Virtual Appliance (NVA) to the CoreServices virtual network.
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.
| Setting | Value |
| --- | --- |
@ -251,9 +255,9 @@ 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** when the route is completed. 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.
1. Select **Subnets** and then **+ Associate**. Complete the configuration.
| Setting | Value |
| --- | --- |