Study guide

8.4 Load Balancing Troubleshooting Workflow

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.4 Load Balancing Troubleshooting Workflow

Key Takeaways Explain This Topic AI

Troubleshooting should follow the packet path from client DNS to frontend IP, rule, probe, backend listener, NSG, route, and application response.

A healthy VM is not the same as a healthy load balancer backend; probe status controls new flow eligibility.

Standard Load Balancer failures frequently involve NSG rules, probe mismatch, backend pool membership, or asymmetric routing.

Testing from the right source network is critical because public, private, peered, and hybrid clients can see different results.

Use Network Watcher and guest OS tests together; neither view alone proves the whole path.

Last updated: May 2026

Troubleshoot by path, not by guessing

When a load-balanced service fails, the symptoms can be misleading. Users say the website is down, but the cause might be DNS, a public IP change, an NSG deny, a wrong probe path, a backend pool that is empty, a user-defined route to a firewall, or an application process that stopped listening. The administrator's job is to reduce the problem to a specific hop.

Use this workflow for most Azure Load Balancer cases: Client reports failure

|-- Step 1: Does the client resolve the expected name to the load balancer frontend IP?

|-- Step 2: Is the client connecting to the expected protocol and port?

|-- Step 3: Does the load balancer rule exist for that frontend, protocol, and port?

|-- Step 4: Does the rule reference the correct backend pool and health probe?

|-- Step 5: Are backends in the pool and marked healthy?

|-- Step 6: Do NSGs allow client traffic and probe traffic?

|-- Step 7: Do routes deliver traffic to the backend and return traffic correctly?

|-- Step 8: Is the application listening and returning a valid response?

This order matters because it prevents unnecessary rebuilds. If DNS points to an old public IP, changing the health probe is wasted effort. If the probe is unhealthy because the app is down, changing the load balancer SKU does not solve the problem.

Step 1: DNS and frontend IP

Confirm that the user is connecting to the intended endpoint. Public clients should resolve to the public frontend IP. Internal clients should resolve to the internal frontend IP. Hybrid clients may use conditional forwarding and private DNS, so test from a client on the affected network.

  • Commands: nslookup api.contoso.com
  • Test-NetConnection api.contoso.com -Port 443
  • curl -v https://api.contoso.com/health
  • az network public-ip show -g rg-network -n pip-web --query ipAddress -o tsv

If the name resolves incorrectly, fix DNS before changing the load balancer. For internal load balancers, check the private DNS zone record and VNet links. For public load balancers, check the public A or CNAME record, TTL, and whether the public IP changed during redeployment.

Step 2: Rule and backend pool

The rule must match the user traffic. A TCP rule on frontend port 443 does not handle UDP. A rule on frontend port 80 does not handle HTTPS unless clients really connect to 80. The backend pool must contain the intended instances.

Portal path: Load balancer > Load balancing rules , then inspect the frontend IP, protocol, frontend port, backend port, backend pool, and health probe. Then go to Backend pools and confirm membership.

  • CLI checks: az network lb rule list -g rg-network --lb-name lb-web-public -o table
  • az network lb address-pool show -g rg-network --lb-name lb-web-public -n be-web
  • Step 3: Probe health

Probe state explains many one-backend and no-backend failures. If all probes fail, the load balancer has no healthy destinations for new flows. If one probe fails, traffic distribution may look uneven because Azure correctly avoids that instance.

Test the probe endpoint from the backend itself first. If curl http://localhost:8080/health fails, fix the app before changing Azure. Then test from another VM in the VNet. If local succeeds but network test fails, look at the OS firewall, NSG, route table, and application binding address. An app bound only to 127.0.0.1 may pass local tests but fail from the network.

The NSG must also allow the probe. In many designs, an inbound allow from the AzureLoadBalancer service tag to the probe port is required. For client traffic, allow the client source or internet source to the application port as appropriate. Do not open broad ranges if a narrow source and port satisfy the requirement.

Step 4: Routes and asymmetric paths

User-defined routes can break load balancing. A subnet route might send traffic through a network virtual appliance, firewall, or gateway. That can be valid, but return traffic must be symmetric enough for stateful devices, and the appliance must allow the flow. If the client is on-premises, check ExpressRoute or VPN routes and whether the on-premises firewall knows the return path.

  • Next hop inspection is useful when the packet seems to vanish: az network watcher show-next-hop \
  • g rg-network \
  • -vm vm-web-1 \
  • -source-ip 10.20.2.4 \
  • -dest-ip 10.10.1.20

For inbound public load balancing, remember that the backend sees traffic according to Azure's load balancing behavior and the application response must route back correctly. UDRs that force default traffic to a firewall can alter outbound paths. If a firewall is in the path, inspect firewall logs and rules.

Step 5: Guest OS and application

Azure can route only to a listener that exists. On Linux, check ss -lntp , systemctl status , and app logs. On Windows, check netstat -ano , Windows Firewall, IIS bindings, service status, and event logs. If the process listens on IPv6 only, loopback only, or a different port, the load balancer will not fix it.

Guest OS firewalls are easy to miss because Azure NSGs may look correct. Windows Defender Firewall or Linux firewall rules can block the backend port or probe port. In exam scenarios, if Azure configuration is correct but only a specific VM fails, the guest firewall or application listener becomes likely.

Fast comparison of symptoms

Symptom Most likely area First diagnostic

FQDN resolves to old address DNS nslookup from affected client.

Frontend IP reachable from one network but not another NSG, route, firewall, DNS split horizon Test from both sources.

No backends receive traffic Probe, rule, backend pool, NSG Check probe health and pool membership.

Only one backend receives traffic Other backends unhealthy or session persistence Inspect probe result per instance.

Backend works by direct IP but not through load balancer Rule, probe, frontend, DNS Compare direct listener test with frontend test.

Probe healthy but app response broken Application path or dependency Review app logs and dependency connectivity.

Exam approach

AZ-104 often describes a failure after a single change. Anchor on that change. If public network access was disabled on a service, DNS for a private endpoint becomes likely. If an NSG was tightened, check the application and probe ports. If a VM was replaced, check backend pool membership. If a new /healthz endpoint was deployed but the probe still checks / , update the probe.

Do not jump to deleting and recreating a load balancer. Most failures are configuration mismatches. A disciplined path test is faster and safer.