Skip to content

Commit 77cfb00

Browse files
committed
Line edits2
1 parent 0c71fce commit 77cfb00

8 files changed

+11
-11
lines changed

learn-pr/azure/azure-vmware-solution/9-exercise-configure-custom-router.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -32,16 +32,16 @@ quiz:
3232
explanation: "Incorrect. Azure vWAN can create and inject default route."
3333
- content: "How many private IP addresses are assigned to Azure Route Server?"
3434
choices:
35-
- content: "0"
35+
- content: "Zero"
3636
isCorrect: false
3737
explanation: "Incorrect. Two private IP addresses are assigned to Azure Route Server."
38-
- content: "1"
38+
- content: "One"
3939
isCorrect: false
4040
explanation: "Incorrect. Two private IP addresses are assigned to Azure Route Server."
41-
- content: "2"
41+
- content: "Two"
4242
isCorrect: true
4343
explanation: "Correct. Two private IP addresses are assigned to Azure Route Server."
44-
- content: "3"
44+
- content: "Three"
4545
isCorrect: false
4646
explanation: "Incorrect. Two private IP addresses are assigned to Azure Route Server."
4747

learn-pr/azure/azure-vmware-solution/includes/10-network-security-management.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Azure Firewall is configured in "block by default" design. It means any network
66

77
## Outbound network rules
88

9-
While "block by default" is a good principle, you need legitimate traffic to be excluded from this principle. You can use one of the two features provided by Azure Firewall to exclude legitimate traffic from "block by default" configuration.
9+
While "block by default" is a good principle, you need legitimate traffic to be excluded from this principle. You can use one of the two features provided by Azure Firewall to exclude legitimate traffic from "block by default" configuration.
1010

1111
The first feature is called "classic rules" or just "rules." Each Azure Firewall instance is configured with a rule, which consists of a protocol, source IP address space, source ports, destination IP address space, and destination ports. This is an excellent choice for smaller deployments. But for enterprise-grade deployments, this approach has limited scalability as the rules are defined per Azure Firewall instance. When there are multiple Azure Firewall instances, the process of defining rules becomes repetitive and difficult to manage. This is where the second feature, which uses Azure Firewall policy, becomes handy. By using Azure Firewall policy, rules are defined only once and then applied to multiple Azure Firewall instances.
1212

learn-pr/azure/azure-vmware-solution/includes/2-outbound-internet-connectivity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Choosing the right way for outbound internet connectivity depends upon whether y
88

99
## Controlling internet traffic
1010

11-
Contoso has very prescriptive requirements on how workloads should be connected to the internet. Such requirements allow Contoso to have a centralized exit for internet bound traffic from all applications running inside and outside of Azure VMware Solution. To meet these requirements, Contoso wants to implement customized internet outbound connectivity on top of options provided by Azure VMware Solution.
11+
Contoso has very prescriptive requirements on how workloads should be connected to the internet. Such requirements allow Contoso to have a centralized exit for internet bound traffic from all applications running inside and outside of Azure VMware Solution. To meet these requirements, Contoso wants to implement customized internet outbound connectivity on top of options provided by Azure VMware Solution.
1212

1313
### Disable outbound internet connectivity
1414

learn-pr/azure/azure-vmware-solution/includes/4-exchange-routes-with-avs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
## Network paths in Azure VMware Solution private cloud
44

5-
Azure VMware Solution private cloud contains a management segment which is used to run infrastructure services such as vSAN, NSX Data Center, private cloud management, etc. Additionally, there can be one or more network segments for running applications, commonly referred to as workload segments. Management and workload segments both use the private IP address space. Virtual machines (VMs) running on a workload segment can communicate with each other. However, extra configuration is required for workload segment VMs to communicate outside of Azure VMware Solution private cloud which is discussed in the [Default outbound internet connectivity for Azure VMware Solution](../2-outbound-internet-connectivity.yml) unit.
5+
Azure VMware Solution private cloud contains a management segment, which is used to run infrastructure services such as vSAN, NSX Data Center, private cloud management, etc. Additionally, there can be one or more network segments for running applications, commonly referred to as workload segments. Management and workload segments both use the private IP address space. Virtual machines (VMs) running on a workload segment can communicate with each other. However, extra configuration is required for workload segment VMs to communicate outside of Azure VMware Solution private cloud, which is discussed in the [Default outbound internet connectivity for Azure VMware Solution](../2-outbound-internet-connectivity.yml) unit.
66

77
## Network paths in Azure
88

learn-pr/azure/azure-vmware-solution/includes/6-securing-network-communication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,6 @@ Contoso has multiple Azure Virtual Networks (VNets). Each VNet has multiple subn
1010

1111
## Firewall Internet Route
1212

13-
After Contoso evaluated the requirements around protection and controlling of network traffic, they chose to use Azure Firewall. It's a stateful, managed firewall as a service. Azure Firewall provides traffic filtering through hybrid network connectivity using ExpressRoute and VPN gateways, which is relevant for Azure VMware Solution private cloud. While Azure Firewall can be used for traffic filtering, it needs direct access to the internet itself which is achieved by configuring the appropriate rules on the subnet in which Azure Firewall is deployed.
13+
After Contoso evaluated the requirements around protection and controlling of network traffic, they chose to use Azure Firewall. It's a stateful, managed firewall as a service. Azure Firewall provides traffic filtering through hybrid network connectivity using ExpressRoute and VPN gateways, which is relevant for Azure VMware Solution private cloud. While Azure Firewall can be used for traffic filtering, it needs direct access to the internet itself, and that's achieved by configuring the appropriate rules on the subnet in which Azure Firewall is deployed.
1414

1515
Use instructions in the following unit for technical implementation of Azure Firewall and network traffic controls. This implementation helps to meet key network security requirements discussed in this unit.

learn-pr/azure/azure-vmware-solution/includes/8-using-frrouting-nva.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ As part of Contoso's IT team, you developed deep knowledge of the NVA over the y
1010

1111
## Open-source
1212

13-
NVAs can either be proprietary or open source. Open source NVAs are developed by the technical community as opposed to a commercial vendor. Proprietary NVAs incur additional costs but provide guaranteed support. With open source NVAs, you have access to source code and rely upon the technical community for any support. At Contoso, you use an open-source implementation for the NVA. Such an implementation gives you flexibility to use open protocols such as BGP. You can use NVA capability to generate a default route. NVAs offers simple integration with VMs and networks running in Azure.
13+
NVAs can either be proprietary or open source. The technical community develops open source NVAs as opposed to a commercial vendor. Proprietary NVAs incur additional costs but provide guaranteed support. With open source NVAs, you have access to source code and rely upon the technical community for any support. At Contoso, you use an open-source implementation for the NVA. Such an implementation gives you flexibility to use open protocols such as BGP. You can use NVA capability to generate a default route. NVAs offers simple integration with VMs and networks running in Azure.
1414

1515
The considerations previously discussed are the key reasons why Contoso uses FRRouting (FRR), an open source and free implementation for network routing.
1616

learn-pr/azure/azure-vmware-solution/includes/9-exercise-configure-custom-router.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -130,6 +130,6 @@ The following steps establish a BGP peer relationship between the FRR NVA and Az
130130

131131
:::image type="content" source="../media/9-config-bgp-route-table.png" alt-text="Screenshot of Azure portal menu. The menu entry titled “ToInternet” route table highlights default route configured with Internet as next hop.":::
132132

133-
At this point, you configured Azure VMware Solution private cloud to implement secure outbound internet connectivity. You deployed Azure Route Server for an effective route exchange between Azure VMware Solution private cloud and the NVA. You then deployed Azure Firewall as the exit point for all internet-bound traffic. This was followed-up by using FRR, a custom router which injects a default route with Azure Firewall as the next hop into Azure VMware Solution private cloud.
133+
At this point, you configured Azure VMware Solution private cloud to implement secure outbound internet connectivity. You deployed Azure Route Server for an effective route exchange between Azure VMware Solution private cloud and the NVA. You then deployed Azure Firewall as the exit point for all internet-bound traffic. This was followed-up by using FRR, a custom router that injects a default route with Azure Firewall as the next hop into Azure VMware Solution private cloud.
134134

135135
In the next unit, you'll learn how to implement fine-grained access controls in Azure Firewall, which allows/denies network traffic from Azure VMware Solution private cloud.

learn-pr/azure/azure-vmware-solution/index.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ uid: learn.azure.azure-vmware-solution
33
title: Secure outbound internet connectivity for Azure VMware Solution
44
metadata:
55
title: Secure Outbound Internet Connectivity for Azure VMware Solution
6-
description: Secure outbound internet connectivity for Azure VMware Solution using Azure Route Server, Azure Firewall and third-party NVA
6+
description: Secure outbound internet connectivity for Azure VMware Solution using Azure Route Server, Azure Firewall, and third-party NVA
77
ms.date: 07/08/2025
88
author: Mahesh-MSFT
99
ms.author: maksh

0 commit comments

Comments
 (0)