Study guide

8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations

AZ-104 Microsoft Azure Administrator Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Orientation and Microsoft Learn Source Control

1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log

2 Chapter 2: Identity, RBAC, and Governance Foundations

2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab

3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization

3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab

4 Chapter 4: Storage Accounts, Access, and Data Protection

4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab

5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep

5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab

6 Chapter 6: Containers, App Service, and Platform Compute

6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab

7 Chapter 7: Virtual Networking, Routing, and Secure Access

7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab

8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting

8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab

9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery

9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab

10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs

10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab

11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path

11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths

8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations

Key Takeaways Explain This Topic AI

Hybrid connectivity combines network reachability, routing, name resolution, security rules, and service endpoint design.

Site-to-site VPN uses encrypted tunnels over the internet, while ExpressRoute uses private connectivity through a provider.

Gateway subnet, local network gateway, route propagation, BGP, and address space planning are core VPN design elements.

ExpressRoute does not automatically solve DNS, NSG, private endpoint, or application listener problems.

Hybrid troubleshooting should validate DNS, routes, gateway health, tunnel status, firewall rules, and return paths.

Last updated: May 2026

Hybrid connectivity foundations

Hybrid networking connects Azure VNets with on-premises networks. The common options for AZ-104 are site-to-site VPN and ExpressRoute. Site-to-site VPN uses IPsec/IKE tunnels over the internet through a VPN gateway. ExpressRoute uses private connectivity through a connectivity provider and can offer more predictable performance and private peering paths.

Connectivity alone is not the full design. You also need non-overlapping address spaces, correct routes, DNS forwarding, NSG allowances, on-premises firewall rules, and application listeners. Many case study failures happen after the tunnel or circuit is technically connected because the name resolves incorrectly, the next hop is wrong, or a firewall blocks the port.

Requirement Site-to-site VPN ExpressRoute

Encrypted tunnel over internet Yes Not the normal defining feature; private provider path.

Private connectivity through provider No Yes.

Lower cost and faster simple setup Often Usually more planning and provider coordination.

Predictable enterprise connectivity Possible, but internet dependent Stronger fit.

BGP support Supported with compatible devices Supported and commonly used.

DNS solved automatically No No. DNS still needs design.

Site-to-site VPN components

A site-to-site VPN design includes a virtual network gateway in Azure, a gateway subnet, a public IP for the gateway, a local network gateway representing the on-premises VPN device and prefixes, and a connection object with a shared key or appropriate authentication settings. The on-premises VPN device must be configured with matching IPsec/IKE settings.

The gateway subnet is dedicated. Do not place VMs or other resources in it. Size it with future needs in mind because gateway features can require enough address capacity. The local network gateway must accurately represent on-premises address prefixes unless BGP dynamically exchanges routes.

  • Basic CLI outline: az network vnet subnet create \
  • g rg-network \
  • -vnet-name vnet-hub \
  • n GatewaySubnet \
  • -address-prefixes 10.0.255.0/27
  • az network local-gateway create \
  • g rg-network \
  • n lgw-datacenter \
  • -gateway-ip-address 203.0.113.10 \
  • -local-address-prefixes 172.16.0.0/16

In exam questions, if on-premises routes change frequently, BGP is often a better answer than manually editing static prefixes. If address spaces overlap, routing cannot cleanly distinguish destinations. Fix address planning rather than trying to patch every subnet with UDRs.

ExpressRoute considerations

ExpressRoute uses circuits and peerings, most often private peering for access to Azure VNets through an ExpressRoute gateway. It is not a public internet VPN. It can connect multiple VNets through gateway connections and can be part of hub-and-spoke designs.

ExpressRoute does not bypass every security control. NSGs still apply to VM traffic. Azure Firewall or network virtual appliances still enforce their policies if traffic is routed through them. Private endpoints still require DNS resolution to private IP addresses. Service firewalls may still require trusted network configuration depending on the service.

If a question says an ExpressRoute circuit is connected but a VM cannot reach an on-premises server, check route tables, BGP learned routes, gateway connection state, NSGs, on-premises firewall, and return routes. If the failure is by FQDN only, check DNS forwarding before changing the circuit.

DNS in hybrid designs

Hybrid DNS is frequently the hidden problem. Azure clients may use VNet DNS settings pointing to domain controllers or DNS forwarders. On-premises clients may need conditional forwarders that send Azure private zone queries to Azure. Azure DNS Private Resolver can provide inbound endpoints for on-premises queries and outbound endpoints with forwarding rules from Azure to other DNS servers.

Private endpoints add another layer. If on-premises clients need to reach an Azure PaaS service through a private endpoint, their DNS queries for the service FQDN must resolve to the private endpoint IP. That usually requires forwarding the relevant privatelink zone to Azure or hosting equivalent records in the enterprise DNS system.

DNS troubleshooting tree: Hybrid client cannot reach Azure service by name

|-- Does the name resolve from the affected client?

| |-- No: inspect client DNS server and conditional forwarding.

| |-- Yes: continue.

|-- Does it resolve to the intended private or public IP?

| |-- No: inspect private DNS zone records and forwarding rules.

| |-- Yes: continue.

|-- Does routing reach that IP over VPN or ExpressRoute?

| |-- No: inspect gateway, BGP, UDRs, and route propagation.

| |-- Yes: inspect NSGs, firewalls, service firewall, and app listener.

Routing, security, and return path

Hybrid routing must work in both directions. Azure may know how to reach on-premises, but on-premises must also know how to return to the Azure address space. Firewalls and network virtual appliances are stateful, so asymmetric routing can cause dropped responses even if each side has some route.

Route propagation can be disabled on route tables. That is useful in controlled hub-and-spoke designs, but it can also break expected gateway-learned routes. If a subnet suddenly cannot reach on-premises after a route table change, inspect whether gateway route propagation is disabled and whether UDRs override expected BGP routes.

Security controls exist at multiple layers:

  • Layer Azure-side example On-premises example
  • Network route UDR, BGP route, gateway route Router or firewall route table
  • Network filtering NSG, Azure Firewall Datacenter firewall ACL
  • Name resolution Private DNS, VNet DNS servers AD DNS, conditional forwarder
  • Service access Storage firewall, private endpoint Proxy or firewall rule
  • Host access Guest firewall, app binding Server firewall, daemon listener
  • Practical diagnostics

Use both Azure and on-premises tools. In Azure, use Network Watcher next hop, effective routes, IP flow verify, and Connection troubleshoot. On-premises, inspect VPN device logs, firewall logs, routing tables, and DNS server forwarding results.

  • Commands and checks: az network vpn-connection show -g rg-network -n conn-datacenter --query connectionStatus
  • az network watcher show-next-hop -g rg-network --vm vm-app-1 --source-ip 10.0.2.4 --dest-ip 172.16.10.20
  • nslookup sql01.corp.local
  • Test-NetConnection sql01.corp.local -Port 1433
  • Exam traps

Do not say ExpressRoute automatically encrypts all traffic like a site-to-site VPN. Do not assume either VPN or ExpressRoute provides DNS. Do not use public DNS for private endpoint resolution when clients must stay on private paths. Do not forget that NSGs and service firewalls remain active after hybrid connectivity is established.

A frequent AZ-104 pattern says on-premises users can reach a VM by IP but not by name. That is a DNS issue first. Another says DNS returns the correct private IP but the connection times out. That moves the investigation to routes, NSGs, firewalls, and the application listener.