Module 2: Azure Architecture and Services

Azure Load Balancer
VPN Gateway & ExpressRoute

Master Azure networking services that distribute traffic, provide secure connectivity, and connect on-premises networks to Azure. Learn Load Balancer, VPN Gateway, ExpressRoute, and Traffic Manager.

Learning Objectives

After completing this session, you'll be ready for Quiz 14 and able to:

Understand Azure Load Balancer types and SKUs
Configure health probes and load balancing rules
Compare Load Balancer vs Application Gateway
Implement VPN Gateway connectivity (Site-to-Site, Point-to-Site)
Understand ExpressRoute private connections
Configure Traffic Manager for global load balancing
Know Azure Front Door capabilities
Choose appropriate connectivity solutions for scenarios

Azure Load Balancer - Distributing Network Traffic

Azure Load Balancer is like a traffic director at a busy intersection, intelligently distributing incoming network traffic across multiple servers to ensure no single server gets overwhelmed while maintaining high availability.

🏢 Restaurant Host Analogy: Understanding Load Balancers

👥 Incoming Customers

Like network requests arriving at your application

🎯 Smart Host (Load Balancer)

Directs customers to available tables/servers based on capacity

🍽️ Restaurant Tables (Servers)

Multiple servers/VMs ready to serve requests efficiently

⚖️ Azure Load Balancer Types and Features

Load Balancer Types
External (Public):

Distributes internet traffic to VMs

Internal (Private):

Distributes traffic within VNet

Layer 4 (Transport):

Works with IP addresses and ports

Load Balancer SKUs
Basic SKU:

Up to 300 instances, single availability zone

Standard SKU:

Up to 1000 instances, zone redundant, higher SLA (99.99%)

Gateway SKU:

For third-party network virtual appliances

🏥 Health Probes and Load Balancing Rules

Health Probe Protocols
TCP Connection-based
HTTP Status code 200
HTTPS Secure health check
Load Balancing Algorithms
5-tuple hash Source IP, port, destination IP, port, protocol
Source IP affinity Session persistence

💡 Quiz Tip: Health probes determine which backend instances can receive traffic!

Application Gateway vs Load Balancer

⚖️ Load Balancer vs Application Gateway Comparison

Feature Load Balancer Application Gateway
OSI Layer Layer 4 (Transport) Layer 7 (Application)
Protocol Support TCP, UDP HTTP, HTTPS, WebSocket
URL-based Routing ❌ No ✅ Yes
SSL Termination ❌ No ✅ Yes
Web Application Firewall ❌ No ✅ Yes
Best Use Case Non-HTTP traffic, high performance Web applications, advanced routing

🚪 Application Gateway Advanced Features

🛣️ URL-based Routing
  • • Route /api/* to API servers
  • • Route /images/* to media servers
  • • Route based on host headers
  • • Path-based backend selection
🔐 SSL Features
  • • SSL termination
  • • End-to-end SSL
  • • Certificate management
  • • SSL policy configuration
🛡️ Web Application Firewall
  • • OWASP protection
  • • SQL injection prevention
  • • Cross-site scripting (XSS) protection
  • • Custom rules and bot protection

Key Point: Application Gateway is for web applications, Load Balancer is for all TCP/UDP traffic!

Azure VPN Gateway - Secure Network Connectivity

Azure VPN Gateway is like a secure tunnel connecting your on-premises network to Azure or individual devices to Azure, providing encrypted connectivity over the internet.

🔐 VPN Gateway Connection Types

🏢 Site-to-Site VPN

Connects entire on-premises network to Azure
Requires VPN device on-premises
Multiple users through single connection
IPSec/IKE encryption

👤 Point-to-Site VPN

Individual client devices to Azure
Remote workers, home users
Certificate or Azure AD authentication
VPN client software required

⚙️ VPN Gateway Configuration and Features

VPN Gateway SKUs
Basic:

10 S2S tunnels, 128 P2S connections, 100 Mbps

VpnGw1/2/3:

More tunnels, BGP support, zone redundancy

VpnGw1/2/3AZ:

Availability zone support, higher SLA

Authentication Methods
Certificates:

Root certificate for Point-to-Site

Azure AD:

Enterprise authentication with MFA

RADIUS:

Third-party authentication servers

🌐 Common VPN Scenarios

🏢 Branch Office

Connect branch offices securely

• Site-to-Site VPN

• Always-on connection

• Multiple users

🏠 Remote Workers

Individual access from home

• Point-to-Site VPN

• On-demand connection

• Personal devices

🔄 Hybrid Cloud

Extend on-premises to Azure

• Site-to-Site VPN

• Burst to cloud

• Data replication

🔑 Quiz Tip: Site-to-Site connects networks, Point-to-Site connects individual devices!

Azure ExpressRoute - Private High-Speed Highway

ExpressRoute is like having a private highway between your on-premises infrastructure and Azure - dedicated, fast, reliable, and never touching the public internet.

🛣️ ExpressRoute vs VPN Gateway

🔒 VPN Gateway

  • Connection: Over internet
  • Speed: Up to 10 Gbps
  • Encryption: IPSec encrypted
  • Latency: Variable (internet dependent)
  • Cost: Lower cost
  • Setup: Quick and easy
  • SLA: 99.9% (Standard)

🚀 ExpressRoute

  • Connection: Private, dedicated
  • Speed: 50 Mbps to 100 Gbps
  • Encryption: Private (optional encryption)
  • Latency: Consistent, low latency
  • Cost: Higher cost
  • Setup: Complex, requires provider
  • SLA: 99.95%

🎯 ExpressRoute Connectivity Models and Features

Connectivity Models
Co-location:

Direct connection at Exchange provider facility

Point-to-Point Ethernet:

Dedicated fiber connection

Any-to-Any IPVPN:

Through MPLS provider

Bandwidth Options
Standard:

50 Mbps - 10 Gbps, regional connectivity

Premium:

Global connectivity, higher route limits

Direct:

100 Gbps at peering locations

🌍 ExpressRoute Global Reach

Global Reach enables direct connectivity between your on-premises locations through Microsoft's backbone network

🏢 Office A

Connected to Azure via ExpressRoute

☁️ Microsoft Backbone

Global Reach connection

🏢 Office B

Connected to Azure via ExpressRoute

🌐 Benefit: Offices communicate directly without going through internet or Azure!

Azure Traffic Manager - Global DNS Load Balancing

🌐 Traffic Manager - DNS-based Global Load Balancing

🎯 How it Works

1. User requests DNS resolution

2. Traffic Manager responds with IP of best endpoint

3. User connects directly to selected endpoint

4. Traffic Manager monitors endpoint health

⚡ Key Features
  • • Global load balancing
  • • Health monitoring
  • • Multiple routing methods
  • • Supports any internet-facing service

🧭 Traffic Manager Routing Methods

Primary Routing Methods
🚀 Performance

Routes to endpoint with lowest latency

⚖️ Weighted

Distributes traffic based on assigned weights

🏆 Priority

Primary endpoint with failover to secondary

Advanced Methods
🌍 Geographic

Routes based on user's geographic location

🎯 MultiValue

Returns multiple healthy endpoints

🌐 Subnet

Routes based on source IP subnet ranges

🚪 Azure Front Door - Global Application Delivery Platform

🌐 Global CDN
  • • Edge locations worldwide
  • • Static content caching
  • • Dynamic content acceleration
  • • SSL termination
⚖️ Load Balancing
  • • Global load balancing
  • • Health probes
  • • Session affinity
  • • URL-based routing
🛡️ Security
  • • Web Application Firewall
  • • DDoS protection
  • • Bot protection
  • • Rules engine

Key Difference: Traffic Manager is DNS-only, Front Door provides full application delivery platform!

Scenario-Based Decision Making

Let's explore real-world scenarios to understand when to use each Azure networking service. These scenarios are commonly tested in the AZ-900 exam.

1

Scenario: E-commerce Web Application

You need to distribute HTTP/HTTPS traffic for a shopping website across multiple web servers

❓ Requirements Analysis:

  • • Need SSL termination for secure shopping
  • • Route /api calls to backend servers
  • • Route /images to media servers
  • • Need Web Application Firewall protection

✅ Recommended Solution: Application Gateway

Why: Layer 7 load balancing, URL-based routing, SSL termination, and WAF capabilities make Application Gateway perfect for web applications.

2

Scenario: Database Cluster Load Balancing

You need to distribute TCP database connections across multiple SQL servers

❓ Requirements Analysis:

  • • High-performance TCP connection distribution
  • • Session persistence for database connections
  • • No need for HTTP-specific features
  • • Internal load balancing within VNet

✅ Recommended Solution: Azure Load Balancer (Internal)

Why: Layer 4 load balancing provides optimal performance for TCP traffic, with session affinity for persistent database connections.

3

Scenario: Remote Employee Access

Your company needs to provide secure access to Azure resources for remote employees

❓ Requirements Analysis:

  • • Individual employee access from personal devices
  • • Need authentication with Azure AD
  • • Occasional connections (not always-on)
  • • Cost-effective solution

✅ Recommended Solution: Point-to-Site VPN

Why: Perfect for individual remote access with Azure AD authentication, cost-effective for occasional connections.

4

Scenario: Branch Office Connectivity

Connect a branch office network permanently to Azure for shared resources

❓ Requirements Analysis:

  • • Always-on connectivity for entire office
  • • Multiple users through single connection
  • • Shared access to Azure file shares and applications
  • • Budget-conscious solution

✅ Recommended Solution: Site-to-Site VPN

Why: Cost-effective always-on connection for entire office networks with encrypted connectivity over internet.

5

Scenario: Mission-Critical Enterprise Application

Financial company needs highest performance, predictable latency, and complete security

❓ Requirements Analysis:

  • • Guaranteed bandwidth and performance
  • • Predictable, low latency
  • • Private connection (compliance requirement)
  • • 99.95% SLA requirement

✅ Recommended Solution: ExpressRoute

Why: Private, dedicated connection with guaranteed bandwidth, predictable performance, and highest SLA for mission-critical applications.

🧠 Get Ready for Quiz 14 - Sample Questions

Here are example questions similar to what you'll see in Quiz 14. Make sure you understand these networking connectivity concepts!

Sample Question 1:

"What is the main advantage of ExpressRoute over VPN Gateway?"

  • A) Lower cost
  • B) Dedicated bandwidth and consistent performance ✅
  • C) Easier setup
  • D) Better security

Sample Question 2:

"Which Azure service operates at Layer 7 and provides URL-based routing?"

  • A) Azure Load Balancer
  • B) Application Gateway ✅
  • C) Traffic Manager
  • D) VPN Gateway

📝 Quiz 14 Topics: Load Balancer, Application Gateway, VPN Gateway, ExpressRoute, Traffic Manager, Front Door

Take Quiz 14 Now

Session 14 Summary

🎯 Key Takeaways - Everything You Need for Quiz 14

⚖️ Load Balancing Services:

  • Load Balancer: Layer 4 (TCP/UDP), high performance, internal/external
  • Application Gateway: Layer 7 (HTTP/HTTPS), URL routing, WAF, SSL termination
  • Traffic Manager: DNS-based global load balancing
  • Front Door: Global application delivery platform with CDN

🔍 Health Probes:

  • TCP, HTTP, HTTPS protocols supported
  • Determine healthy backend instances

🔒 Connectivity Solutions:

  • Site-to-Site VPN: Connect networks, always-on, encrypted over internet
  • Point-to-Site VPN: Individual devices, on-demand, Azure AD auth
  • ExpressRoute: Private connection, guaranteed bandwidth, 99.95% SLA

🎯 Key Differences:

  • Layer 4 vs Layer 7 load balancing
  • VPN (over internet) vs ExpressRoute (private)
  • Regional vs Global load balancing

🎉 Azure Networking Services Mastered!

You now understand how to distribute traffic with Load Balancers, secure connectivity with VPN Gateway, high-performance private connections with ExpressRoute, and global traffic management with Traffic Manager. You can choose the right networking solution for any scenario!

Load Balancing ✓ VPN Connectivity ✓ ExpressRoute ✓ Traffic Manager ✓ Application Gateway ✓

🚀 Ready for Quiz 14?

Excellent! You've mastered Azure networking services for connectivity and traffic distribution. Now test your knowledge with Quiz 14, which covers all the Load Balancer, VPN Gateway, ExpressRoute, and Traffic Manager topics from this session.