changed files by pdets auto publish service, publishid[41efcb61-67af-419e-8444-1608664e8be0] and do [publish].

wwlpublish · web-flow · commit b1cad494980e · 2025-05-20T01:23:48.000+08:00
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/1-introduction.yml b/learn-pr/wwl-azure/configure-vnet-peering/1-introduction.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.configure-vnet-peering.introduction
 title: Introduction
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Introduction
   description: "Introduction"
-  ms.date: 12/13/2024
+  ms.date: 05/19/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/2-determine-uses.yml b/learn-pr/wwl-azure/configure-vnet-peering/2-determine-uses.yml
@@ -2,14 +2,16 @@
 uid: learn.wwl.configure-vnet-peering.determine-uses
 title: Determine Azure Virtual Network peering uses
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Determine Azure Virtual Network peering uses
   description: "Determine usage scenarios for Azure Virtual Network peering."
-  ms.date: 12/13/2024
+  ms.date: 05/19/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - N/A
-durationInMinutes: 3
+durationInMinutes: 5
 content: |
   [!include[](includes/2-determine-uses.md)]
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/3-determine-gateway-transit-connectivity.yml b/learn-pr/wwl-azure/configure-vnet-peering/3-determine-gateway-transit-connectivity.yml
@@ -2,14 +2,16 @@
 uid: learn.wwl.configure-vnet-peering.determine-gateway-transit-connectivity
 title: Determine gateway transit and connectivity
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Determine gateway transit and connectivity
   description: "Determine gateway transit and connectivity"
-  ms.date: 12/13/2024
+  ms.date: 05/19/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - N/A
-durationInMinutes: 2
+durationInMinutes: 6
 content: |
   [!include[](includes/3-determine-gateway-transit-connectivity.md)]
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/4-create.yml b/learn-pr/wwl-azure/configure-vnet-peering/4-create.yml
@@ -2,14 +2,16 @@
 uid: learn.wwl.configure-vnet-peering.create
 title: Create virtual network peering
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Create virtual network peering
   description: "Create a virtual network peering in the Azure portal."
-  ms.date: 12/13/2024
+  ms.date: 05/19/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - N/A
-durationInMinutes: 9
+durationInMinutes: 10
 content: |
   [!include[](includes/4-create.md)]
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/5-determine-service-chaining-uses.yml b/learn-pr/wwl-azure/configure-vnet-peering/5-determine-service-chaining-uses.yml
@@ -2,14 +2,16 @@
 uid: learn.wwl.configure-vnet-peering.determine-service-chaining-uses
 title: Extend peering with user-defined routes and service chaining
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Extend peering with user-defined routes and service chaining
   description: "Use a hub and spoke network with user-defined routes and service chaining to extend peering capabilities."
-  ms.date: 12/13/2024
+  ms.date: 05/19/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - N/A
-durationInMinutes: 2
+durationInMinutes: 5
 content: |
   [!include[](includes/5-determine-service-chaining-uses.md)]
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/6-simulation-peering.yml b/learn-pr/wwl-azure/configure-vnet-peering/6-simulation-peering.yml
@@ -1,15 +1,17 @@
 ### YamlMime:ModuleUnit
 uid: learn.wwl.configure-vnet-peering.interactive-simulation-peering
-title: Interactive lab simulation
+title: Exercise - Implement Intersite Connectivity
 metadata:
-  title: Interactive lab simulation
-  description: "Interactive lab simulation"
-  ms.date: 12/13/2024
+  adobe-target: true
+  prefetch-feature-rollout: true
+  title: Exercise - Implement Intersite Connectivity
+  description: "Exercise - Implement Intersite Connectivity"
+  ms.date: 05/19/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - N/A
-durationInMinutes: 12
+durationInMinutes: 5
 content: |
   [!include[](includes/6-simulation-peering.md)]
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/7-knowledge-check.yml b/learn-pr/wwl-azure/configure-vnet-peering/7-knowledge-check.yml
@@ -2,9 +2,11 @@
 uid: learn.wwl.configure-vnet-peering.knowledge-check
 title: Module assessment
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Module assessment
   description: "Knowledge check"
-  ms.date: 12/13/2024
+  ms.date: 05/19/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/8-summary-resources.yml b/learn-pr/wwl-azure/configure-vnet-peering/8-summary-resources.yml
@@ -2,14 +2,16 @@
 uid: learn.wwl.configure-vnet-peering.summary-resources
 title: Summary and resources
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Summary and resources
   description: "Summary and resources"
-  ms.date: 12/13/2024
+  ms.date: 05/19/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: unit
   ms.custom:
   - N/A
-durationInMinutes: 1
+durationInMinutes: 2
 content: |
   [!include[](includes/8-summary-resources.md)]
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/includes/2-determine-uses.md b/learn-pr/wwl-azure/configure-vnet-peering/includes/2-determine-uses.md
@@ -1,5 +1,7 @@
 Perhaps the simplest and quickest way to connect your virtual networks is to use Azure Virtual Network peering. Virtual Network peering enables you to seamlessly connect two Azure virtual networks. After the networks are peered, the two virtual networks operate as a single network, for connectivity purposes.
 
+> [!VIDEO https://learn-video.azurefd.net/vod/player?id=dc8c31e3-7c1a-4377-a0c2-e415bfc1d638]
+
 ### Things to know about Azure Virtual Network peering
 
 Let's examine some prominent characteristics of Azure Virtual Network peering.
@@ -20,6 +22,8 @@ Let's examine some prominent characteristics of Azure Virtual Network peering.
 
 - After you create a peering between virtual networks, the individual virtual networks are still managed as separate resources.
 
+- Virtual networks can be peered across subscriptions and tenants. 
+
 ### Things to consider when using Azure Virtual Network peering
 
 Consider the benefits of using Azure Virtual Network peering.
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/includes/3-determine-gateway-transit-connectivity.md b/learn-pr/wwl-azure/configure-vnet-peering/includes/3-determine-gateway-transit-connectivity.md
@@ -1,9 +1,19 @@
 When virtual networks are peered, you can configure Azure VPN Gateway in the peered virtual network as a _transit point_. In this scenario, a peered virtual network uses the remote VPN gateway to gain access to other resources.
 
+> [!VIDEO https://learn-video.azurefd.net/vod/player?id=548335d7-68af-4444-9c4d-0abf73e66d55] 
+
+### Transit and connectivity use
+
 Consider a scenario where three virtual networks in the same region are connected by virtual network peering. Virtual network A and virtual network B are each peered with a hub virtual network. The hub virtual network contains several resources, including a gateway subnet and an Azure VPN gateway. The VPN gateway is configured to allow VPN gateway transit. Virtual network B accesses resources in the hub, including the gateway subnet, by using a remote VPN gateway. 
 
 :::image type="content" source="../media/gateway-transit-173a51a0.png" alt-text="Diagram of a regional virtual network peering. One network allows VPN gateway transit and uses a remote VPN gateway to access resources in a hub virtual network." border="false":::
 
+
+
+The Azure portal doesn't specifically mention *gateway transit* and *connectivity*. Instead, you have choices for allowing and forwarding network traffic. Can you tell the differences in the selections?
+
+:::image type="content" source="../media/peering-settings.png" alt-text="Screenshot of the peering options in the portal." border="false":::
+
 ### Things to know about Azure VPN Gateway
 
 Let's take a closer look at how Azure VPN Gateway is implemented with Azure Virtual Network peering.
@@ -19,4 +29,8 @@ Let's take a closer look at how Azure VPN Gateway is implemented with Azure Virt
 
 - Gateway transit allows peered virtual networks to share the gateway and get access to external resources. With this implementation, you don't need to deploy a VPN gateway in the peered virtual network.
 
-- You can apply network security groups in a virtual network to block or allow access to other virtual networks or subnets. When you configure virtual network peering, you can choose to open or close the network security group rules between the virtual networks.
+- You can apply network security groups in a virtual network to block or allow access to other virtual networks or subnets. When you configure virtual network peering, you can choose to open or close the network security group rules between the virtual networks.
+
+
+
+
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/includes/4-create.md b/learn-pr/wwl-azure/configure-vnet-peering/includes/4-create.md
@@ -4,7 +4,7 @@ Azure Virtual Network peering can be configured for virtual networks by using Po
 
 There are a few points to review before we look at how to create the peering in the Azure portal.
 
-- To implement virtual network peering, your Azure account must be assigned to the `Network Contributor` or `Classic Network Contributor` role. Alternatively, your Azure account can be assigned to a custom role that can complete the necessary peering actions. For details, see [Permissions](/azure/virtual-network/virtual-network-manage-peering?tabs=peering-portal#permissions).
+- To implement virtual network peering, your Azure account must be assigned to the `Network Contributor` role. Alternatively, your Azure account can be assigned to a custom role that can complete the necessary peering actions. For details, see [Permissions](/azure/virtual-network/virtual-network-manage-peering?tabs=peering-portal#permissions).
 
 - To create a peering, you need two virtual networks. 
 
@@ -15,7 +15,7 @@ There are a few points to review before we look at how to create the peering in
 
 ## How to connect virtual networks across Azure regions with Azure Global virtual network peering 
 
-<iframe width="854" height="480" src="https://www.youtube.com/embed/pSqDlQlcsLo" title="How to move Azure Storage Blobs between containers" allowfullscreen></iframe>
+<iframe width="854" height="480" src="https://www.youtube.com/embed/pSqDlQlcsLo" title="How to connect virtual networks through peering" allowfullscreen></iframe>
 
 
 ## How to check your peering status
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/includes/5-determine-service-chaining-uses.md b/learn-pr/wwl-azure/configure-vnet-peering/includes/5-determine-service-chaining-uses.md
@@ -2,21 +2,21 @@ Virtual network peering is nontransitive. The communication capabilities in a pe
 
 Suppose you have three virtual networks: A, B, and C. You establish virtual network peering between networks A and B, and also between networks B and C. You don't set up peering between networks A and C. The virtual network peering capabilities that you set up between networks B and C don't automatically enable peering communication capabilities between networks A and C. 
 
+> [!VIDEO https://learn-video.azurefd.net/vod/player?id=04973850-eeb2-495c-a4e0-1f6e13fad5f4]
+
 ### Things to know about extending peering
 
-There are a few ways to extend the capabilities of your peering for resources and virtual networks outside your peering network:
-- Hub and spoke networks
-- User-defined routes
-- Service chaining
+There are a few ways to extend the capabilities of your peering for resources and virtual networks outside your peering network.
+
+| Mechanism | Description |
+| --- | --- |
+| **Hub and spoke network** | When you deploy a hub-and-spoke network, the hub virtual network can host infrastructure components like a network virtual appliance (NVA) or Azure VPN gateway. All the spoke virtual networks can then peer with the hub virtual network. Traffic can flow through NVAs or VPN gateways in the hub virtual network. |
+| **User-defined route (UDR)** | Virtual network peering enables the next hop in a [user-defined route](/azure/virtual-network/virtual-networks-udr-overview#user-defined) to be the IP address of a virtual machine in the peered virtual network, or a VPN gateway. |
+| **Service chaining** | [Service chaining](/azure/virtual-network/virtual-network-peering-overview#service-chaining) is used to direct traffic from one virtual network to a virtual appliance or gateway. To enable service chaining, configure UDRs that point to virtual machines in peered virtual networks as the next hop IP address. UDRs could also point to virtual network gateways to enable service chaining. |
 
-You can implement these mechanisms and create a multi-level hub and spoke architecture. These options can help overcome the limit on the number of virtual network peerings per virtual network.
 
-The next diagram shows a hub and spoke virtual network with an NVA and VPN gateway. The hub and spoke network is accessible to other virtual networks via user-defined routes and service chaining.
+The following diagram shows a hub and spoke virtual network with an NVA and VPN gateway. The hub and spoke network is accessible to other virtual networks via user-defined routes and service chaining.
 
 :::image type="content" source="../media/service-chains-5c9286d1.png" alt-text="Diagram that shows a hub virtual network with an NVA and VPN gateway that are accessible to other virtual networks." border="false":::
 
-| Mechanism | Description |
-| --- | --- |
-| **Hub and spoke network** | When you deploy a hub-and-spoke network, the hub virtual network can host infrastructure components like a network virtual appliance (NVA) or Azure VPN gateway. All the spoke virtual networks can then peer with the hub virtual network. Traffic can flow through NVAs or VPN gateways in the hub virtual network. |
-| **User-defined route (UDR)** | Virtual network peering enables the next hop in a user-defined route to be the IP address of a virtual machine in the peered virtual network, or a VPN gateway. |
-| **Service chaining** | Service chaining is used to direct traffic from one virtual network to a virtual appliance or gateway. A user-defined route defines the peered networks. |
+
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/includes/6-simulation-peering.md b/learn-pr/wwl-azure/configure-vnet-peering/includes/6-simulation-peering.md
@@ -1,33 +1,25 @@
 ## Lab scenario
 
-Your organization has three datacenters connected with a mesh wide-area network. As the Azure Administrator, you need to implement the on-premises infrastructure in Azure. 
-
-+ There are two offices, New York and Boston, in one region.
-+ There's one office, Seattle, in another region.
-+ All the offices need to be networked together so they can share information. 
-+ This simulation focuses on the connectivity of the offices, and not creating the individual Azure resources. 
+Your organization segments core IT apps and services (such as DNS and security services) from other parts of the business, including your manufacturing department. However, in some scenarios, apps and services in the core area need to communicate with apps and services in the manufacturing area. In this lab, you configure connectivity between the segmented areas. Separating production from development or separating one subsidiary from another is a common networking scenario. 
 
 ## Architecture diagram
 
 :::image type="content" source="../media/lab-05.png" alt-text="Architecture diagram as explained in the tasks." border="false":::
 
-## Objectives
+## Job skills
 
-> [!NOTE]
-> You may find slight differences between the interactive simulation and the Azure environment, but the core concepts and ideas being demonstrated are the same.
+- Create a virtual machine in a virtual network.
+- Create a virtual machine in a different virtual network.
+- Use Network Watcher to test the connection between virtual machines.
+- Configure virtual network peerings between different virtual networks.
+- Use Azure PowerShell to test the connection between virtual machines.
+- Create a custom route. (optional)
 
-+ **Task 1**: Create the infrastructure environment. In this task, you deploy three virtual machines. Virtual machines are deployed in different regions and virtual networks. 
-    + Use a template to create the virtual networks and virtual machines in the different regions. You can review the [lab templates](https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator/tree/master/Allfiles/Interactive%20Lab%20Simulation%20Files/05).
-    + Use Azure PowerShell to deploy the template. 
-+ **Task 2**: Configure local and global virtual network peering. 
-    + Create a local virtual network peering between the two virtual networks in the same region.
-    + Create a global virtual network peering between virtual networks in different regions. 
-+ **Task 3**: Test intersite connectivity between virtual machines on the three virtual networks.
-    + Test the virtual machine connections in the same region.
-    + Test the virtual machine connections in different regions. 
+> [!IMPORTANT]
+> Estimated time: 30 minutes. 
+> To complete the exercise, you need an [Azure subscription](https://azure.microsoft.com/free/).
 
-> [!NOTE]
-> select the thumbnail image to start the lab simulation. When you're done, be sure to return to this page so you can continue learning. 
+Launch the exercise, and follow the instructions. When finished, be sure to return to this page so you can continue learning.
 
-[![Screenshot of the simulation page.](../media/simulation-intersite-thumbnail.jpg)](https://mslabs.cloudguides.com/guides/AZ-104%20Exam%20Guide%20-%20Microsoft%20Azure%20Administrator%20Exercise%209?azure-portal=true)
 
+[![Button to launch exercise.](../media/launch-exercise.png)](https://microsoftlearning.github.io/AZ-104-MicrosoftAzureAdministrator/Instructions/Labs/LAB_05-Implement_Intersite_Connectivity.html)
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/index.yml b/learn-pr/wwl-azure/configure-vnet-peering/index.yml
@@ -1,12 +1,15 @@
 ### YamlMime:Module
 uid: learn.wwl.configure-vnet-peering
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Configure Azure Virtual Network peering
   description: "Learn to configure an Azure Virtual Network peering connection and address transit and connectivity concerns."
-  ms.date: 12/13/2024
+  ms.date: 05/19/2025
   author: wwlpublish
   ms.author: cynthist
   ms.topic: module
+  ms.collection: N/A
   ms.custom:
   - N/A
   ms.service: azure-virtual-network
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/media/lab-05.png b/learn-pr/wwl-azure/configure-vnet-peering/media/lab-05.png
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/media/launch-exercise.png b/learn-pr/wwl-azure/configure-vnet-peering/media/launch-exercise.png
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/media/peering-settings.png b/learn-pr/wwl-azure/configure-vnet-peering/media/peering-settings.png
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/media/service-chains-5c9286d1.png b/learn-pr/wwl-azure/configure-vnet-peering/media/service-chains-5c9286d1.png
diff --git a/learn-pr/wwl-azure/configure-vnet-peering/media/simulation-intersite-thumbnail.jpg b/learn-pr/wwl-azure/configure-vnet-peering/media/simulation-intersite-thumbnail.jpg
