Skip to content

Commit 93f080f

Browse files
authored
Merge pull request #54120 from staleycyn/patch-3
Content drift changes to the design network solutions module
2 parents 3e3c734 + 4d6efb5 commit 93f080f

5 files changed

Lines changed: 32 additions & 24 deletions

learn-pr/wwl-azure/design-network-solutions/includes/4-design-outbound-connectivity-routing.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,15 @@
11

22
Part of the planning for your Azure AI-ready network solution includes exploring how to support outbound network connectivity and traffic communication routing.
33

4-
Around the globe, IPv4 address ranges are in short supply. Trying to purchase an IP address in the v4 range can be an expensive way to grant access to your internet resources. To address this issue, architects use Network Address Translation (NAT) to enable internal resources on a private network to share routable IPv4 addresses. The internal resources use the routable IPv4 addresses to access external resources on a public network. Instead of buying an IPv4 address for each resource that needs internet access, you can use a NAT service to map outgoing requests from your internal resources to external IP addresses. Azure provides this technology via the Azure Virtual Network NAT service.
5-
64
Azure [routes communication traffic](/azure/virtual-network/virtual-networks-udr-overview) between your on-premises internal resources and external internet resources by using _route tables_. When you create a virtual network, Azure automatically creates a routing table for each subnet in the network. A routing table contains many different types of routes, including system, service endpoints, and subnet defaults. The table also has route entries for the Border Gateway Protocol (BGP), user-defined routes (UDRs), and routes from other virtual networks.
75

86
> [!VIDEO https://learn-video.azurefd.net/vod/player?id=76dd401c-0669-4693-87fc-1ba82d27782d]
97
8+
> [!IMPORTANT]
9+
> Default outbound access retirement: As of March 31, 2026, new virtual networks no longer receive default outbound internet access. Private subnets are now the default behavior. For new Azure deployments that require outbound internet connectivity, you must explicitly configure NAT Gateway or another outbound method (Azure Firewall, public IP, Load Balancer outbound rules).
10+
11+
12+
1013
#### Business scenarios
1114

1215
- Support on-demand outbound-to-internet connectivity without preallocation.
@@ -51,4 +54,4 @@ There are many networking scenarios where defining and overriding routes can be
5154

5255
- **Consider overriding routes**. Plan for route overrides to control traffic flow.
5356
- Flow through NVA: [Configure route tables to force traffic between subnets to flow through an NVA](/azure/virtual-network/tutorial-create-route-table-portal).
54-
- Forced tunneling: [Force all internet-bound traffic through an NVA, or on-premises, through an Azure VPN gateway](/azure/vpn-gateway/vpn-gateway-forced-tunneling-rm).
57+
- Forced tunneling: [Force all internet-bound traffic through an NVA, or on-premises, through an Azure VPN gateway](/azure/vpn-gateway/vpn-gateway-forced-tunneling-rm).

learn-pr/wwl-azure/design-network-solutions/includes/5-design-for-premises-connectivity-to-azure-virtual-networks.md

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -38,12 +38,3 @@ The Azure Virtual WAN architecture includes the benefits of standard hub-spoke n
3838
- Mixed use of user VPN to the site
3939
- Virtual network-to-network connectivity
4040

41-
## Compare services
42-
43-
The following table compares the benefits and challenges of the network connectivity options. Review the scenarios, and think about which services can enhance the network solution for Tailwind Traders.
44-
45-
| Compare | Azure VPN Gateway | Azure ExpressRoute | ExpressRoute + VPN failover | Azure Virtual WAN + hub-spoke |
46-
| --- | --- | --- | --- | ---
47-
| **Benefits** | - Simple to configure <br> - High bandwidth available (up to 10 Gbps depending on VPN Gateway SKU) | - High bandwidth available (up to 10 Gbps depending on connectivity provider) <br> - Supports dynamic scaling of bandwidth to help reduce costs during periods of lower demand (not supported by all connectivity providers) <br> - Enables direct organizational access to national clouds (depends on connectivity provider) | - High availability if ExpressRoute circuit fails (fallback connection on lower bandwidth network | - Reduced operational overhead by replacing existing hubs with fully managed service <br> - Cost savings by using managed service, which removes need for NVA <br> - Improved security via centrally managed secured hubs with Azure Firewall and Virtual WAN <br> - Separates concerns between central IT (SecOps, InfraOps) and workloads (DevOps) |
48-
| **Challenges** | - Requires on-premises VPN device | - Can be complex to set up <br> - Requires working with non-Microsoft connectivity provider <br> - Provider responsible for provisioning network connection <br> - Requires high-bandwidth routers on-premises | - Complex to configure <br> - Must set up both VPN connection and ExpressRoute circuit <br> - Requires redundant hardware (VPN appliances) <br> - Requires redundant Azure VPN Gateway connection for which you pay charges | **Note**: Azure Virtual WAN is designed to reduce previously listed connectivity challenges. |
49-
| **Scenarios** | - Hybrid apps with light traffic between on-premises hardware and the cloud <br><br> - Able to trade slightly extended latency for flexibility and processing power of the cloud | - Hybrid apps running large-scale, mission-critical workloads that require high degree of scalability | - Hybrid apps that require higher bandwidth of ExpressRoute and highly available network connectivity | - Connectivity among workloads requires central control and access to shared services <br><br> - Enterprise requires central control over security aspects like a firewall and segregated management for workloads in each spoke |

learn-pr/wwl-azure/design-network-solutions/includes/7-design-for-application-delivery-services.md

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,10 @@ Azure offers several AI-ready networking services to help deliver applications.
33

44
| Feature/Service | Azure Front Door | Application Gateway | Traffic Manager | Load Balancer |
55
| --- |--- | ---| --- | --- |
6-
| Type | Global | Regional | Global | Regional/Global |
6+
| Type | Global CDN/ADN | Regional | Global | Regional/Global |
77
| Layer | Layer 7 (HTTP/HTTPS) | Layer 7 (HTTP/HTTPS) | DNS-based | Layer 4 (TCP/UDP) |
8-
| Primary Use Case | Web traffic load balancing, application acceleration, and global routing | Web application firewall, TLS/SSL termination, and HTTP load balancing | DNS-based traffic routing for high availability and performance | Internal and external load balancing for non-HTTP(S) traffic |
9-
| Key Features | Path-based routing, TLS/SSL offload, Web Application Firewall (WAF), URL-based routing | Path-based routing, TLS/SSL offload, Web Application Firewall (WAF), URL-based routing | DNS-based routing, geographic routing, priority routing, weighted routing | High availability, low latency, zonal and zone-redundant endpoints |
8+
| Primary Use Case | Web traffic load balancing, application acceleration, global routing, and CDN content delivery | Web application firewall, TLS/SSL termination, and HTTP load balancing | DNS-based traffic routing for high availability and performance | Internal and external load balancing for non-HTTP(S) traffic |
9+
| Key Features | Path-based routing, TLS/SSL offload, Web Application Firewall (WAF), URL-based routing, CDN/edge caching | Path-based routing, TLS/SSL offload, Web Application Firewall (WAF), URL-based routing | DNS-based routing, geographic routing, priority routing, weighted routing | High availability, low latency, zonal and zone-redundant endpoints |
1010
| Scalability | High | High | High | High |
1111
| Cost | Based on data processed and rules applied | Based on data processed, rules applied, and SKU | Based on DNS queries, health checks, and data points processed | Based on rules and data processed |
1212

@@ -17,16 +17,22 @@ The different load balancers can work together in your networking architecture.
1717

1818
### Azure Front Door
1919

20-
[Azure Front Door](/azure/frontdoor/front-door-overview) lets you define, manage, and monitor the global routing for your web traffic by optimizing for best performance and instant global failover for high availability. With Front Door, you can transform your global (multi-region) consumer and enterprise applications into robust, high-performance personalized modern applications, APIs, and content that reaches a global audience with Azure.
21-
20+
[Azure Front Door Standard and Premium](/azure/frontdoor/front-door-overview) lets you define, manage, and monitor the global routing for your web traffic by optimizing for best performance and instant global failover for high availability. With Front Door, you can transform your global (multi-region) consumer and enterprise applications into robust, high-performance personalized modern applications, APIs, and content that reaches a global audience with Azure.
21+
22+
> [!NOTE]
23+
> Azure Front Door (classic) is being retired March 31, 2027. Use Front Door Standard or Premium tiers for new deployments.
24+
2225
#### Business scenarios
2326

2427
- Low latency: Ensure requests are sent to the lowest latency backends.
2528
- Priority: Support primary and secondary backends.
2629
- Weighted: Distribute traffic by using weight coefficients.
2730
- Affinity: Ensure requests from the same end user are sent to the same backend.
2831
- Support WAF and CDN integration for HTTP(S) traffic.
29-
- Support for content delivery services.
32+
- Support for content delivery services.
33+
- Private Link integration for private origins (Premium tier).
34+
- CDN content delivery for static workloads across 118+ edge locations.
35+
3036

3137
### Azure Traffic Manager
3238

learn-pr/wwl-azure/design-network-solutions/includes/8-design-for-application-protection-services.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,17 @@ Azure offers several networking services to help protect your network resources.
55

66
### Azure DDoS Protection (distributed denial of service protection)
77

8-
[Azure DDoS Protection](/azure/ddos-protection/manage-ddos-protection) provides countermeasures against the most sophisticated DDoS threats. The service provides enhanced DDoS mitigation capabilities for your application and resources deployed in your virtual networks. Additionally, customers who use Azure DDoS Protection have access to DDoS Rapid Response support to engage DDoS experts during an active attack.
8+
[Azure DDoS Protection](/azure/ddos-protection/ddos-protection-overview) provides countermeasures against the most sophisticated DDoS threats with [two tiers](/azure/ddos-protection/ddos-protection-sku-comparison#tiers).
9+
10+
- **DDoS Network Protection**: VNet-level protection plan covering multiple resources, includes DDoS Rapid Response support and cost protection guarantees
11+
- **DDoS IP Protection**: Pay-per-protected-IP model, no protection plan required, suitable for individual workloads.
912

1013
#### Business scenarios
1114

1215
- Implement always-on traffic monitoring, adaptive tuning, and mitigation scale.
1316
- Access multi-layered protection, including attack analytics, metrics, and alerting.
14-
- Receive support from the DDoS rapid response team.
17+
- Network protection with centralized management and Rapid Response support.
18+
- IP protection for individual workloads or cost-sensitive architectures.
1519

1620
### Azure Private Link
1721

@@ -25,7 +29,11 @@ Azure offers several networking services to help protect your network resources.
2529

2630
### Azure Firewall
2731

28-
Azure Firewall is a managed, cloud-based network security service that protects your Azure Virtual Network resources. It's a fully stateful firewall as a service with built-in high availability and unrestricted cloud scalability. Azure Firewall uses a static public IP address for your virtual network resources, which allows outside firewalls to identify traffic originating from your virtual network. Azure Firewall provides inbound protection for non-HTTP/S protocols (such as RDP, SSH, and FTP), outbound network-level protection for all ports and protocols, and application-level protection for outbound HTTP/S.
32+
[Azure Firewall](/azure/firewall/overview) is a managed, cloud-based network security service available in three tiers:
33+
- **Basic**: Limited features, alert-only threat intelligence (not recommended for production).
34+
- **Standard**: Full stateful firewall, FQDN filtering, threat intelligence, log analytics.
35+
- **Premium**: Adds TLS inspection, IDPS with 67,000+ signatures, URL filtering, web categories, scales to 100 Gbps, PCI DSS compliance.
36+
2937

3038
#### Business scenarios
3139

@@ -45,7 +53,7 @@ Azure Firewall is a managed, cloud-based network security service that protects
4553
- React faster to security threats by centrally patching known vulnerabilities instead of securing individual web apps.
4654
- Deploy Web Application Firewall with Application Gateway, Front Door, and Content Delivery Network.
4755

48-
### Azure virtual network security groups
56+
### Azure network security groups
4957

5058
You can filter network traffic to and from Azure resources in an Azure virtual network with [Azure network security group (NSGs)](/azure/virtual-network/network-security-groups-overview). You can use a network virtual appliance (NVA) such as Azure Firewall or firewalls from other vendors.
5159

@@ -58,4 +66,4 @@ NSGs contain two sets of rules: inbound and outbound. The priority for a rule mu
5866
- Control how Azure routes traffic from subnets.
5967
- Limit the users in an organization who can work with resources in virtual networks.
6068
- Restrict traffic to an individual NIC by associating an NSG directly to a NIC.
61-
- Combine NSGs with JIT access to restrict access to your virtual machine management ports.
69+
- Combine NSGs with JIT access to restrict access to your virtual machine management ports.

learn-pr/wwl-azure/design-network-solutions/index.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ metadata:
55
prefetch-feature-rollout: true
66
title: Design Network Solutions
77
description: "Azure Architects design and recommend network solutions."
8-
ms.date: 01/26/2026
8+
ms.date: 03/23/2026
99
author: wwlpublish
1010
ms.author: cynthist
1111
ms.topic: module

0 commit comments

Comments
 (0)