Kloud Course Academy

Azure Load Balancer Health Probe 

Azure load balancer health probe

Azure load balancer health probe:

Azure load balancer health probe are essential components for maintaining the reliability and performance of applications deployed on the Azure cloud platform. These probes continuously monitor the health and availability of virtual machines, virtual machine scale sets, and application endpoints. By periodically sending requests to designated endpoints and analyzing their responses, health probes can detect issues such as application failures, connectivity problems, or performance degradation in real-time. Azure health probes enable automatic detection of unhealthy instances and facilitate seamless traffic redirection to healthy instances, ensuring high availability and optimal user experience.   

What Are Azure Health Probes? 

An Azure Load Balancer health probe is a powerful feature that monitors the health status of your application instances. Here’s how it works:  

Detection of Health Status:

The health probe sends requests to your application instances to check if they are available and responsive. It acts like a diligent detective, ensuring that your services are up and running.  

Protocol Flexibility: You can configure the health probe to use different protocols such as TCP, HTTP, or HTTPS. This flexibility allows you to tailor the probe to your specific application needs.  

Importance: Why is this important? Well, health probes help you:  

  • Detect application failures promptly.  
  • Manage load efficiently. 
  • Plan for scheduled downtime.  


Load Balancer Rules: Azure Load Balancer rules rely on health probes to determine the status of endpoints. The configuration of the health probe and its responses directly impact which backend pool instances receive new connections. 

Flow Control: When a health probe detects a failure, the load balancer intelligently stops sending new connections to the unhealthy instance. Outbound connectivity remains unaffected, but inbound connections are rerouted.  

Probe Protocols :

Health probes support multiple protocols, and their availability varies based on the Load Balancer SKU:  

Standard SKU:  

TCP, HTTP, and HTTPS protocols are supported.  

All probes down: Existing TCP flows continue.  

All probes down: Existing TCP flows expire.  

Basic SKU:  

TCP and HTTP protocols are available.  

All probes down: Existing TCP flows expire.   

Health Probe Properties   

Let’s explore the properties of health probes:  

Name: You get to define a name for your health probe.  

Protocol: Choose the protocol type (TCP, HTTP, or HTTPS).   

Port: Specify the destination port for the health probe.  

Interval: Set the time (in seconds) between consecutive health check attempts.  

Used By: List of load balancer rules using this specific health probe.  

Configuring Health Probes   

Azure Portal:  

  • Sign in to the Azure portal.  
  • Search for “Load balancer. 
  • Select your load balancer.  
  • Navigate to Health probes under Settings. 
  •   Add a new health probe with the desired properties.  

Azure Container Apps:  

  • Health probes allow the Container Apps runtime to inspect the status of your container apps. 
  • Set up probes using either TCP or HTTP(S) exclusively. 


Benefits of Azure load balancer health probe :

Detecting Application Failures:

Imagine your application as a busy intersection. Health probes act as traffic lights, constantly checking the health status of your application instances. When an instance fails a health check, it’s like spotting a red light. The probe swiftly redirects traffic away from the unhealthy instance, minimizing downtime and ensuring a smoother user experience. 

Custom Responses 

Health probes allow you to customize your application’s response. Maybe your app needs a moment to catch its breath during peak traffic. With custom responses, you can gracefully handle requests, avoiding sudden failures and maintaining user satisfaction. 

Flow Control and Load Management 

Managing load is crucial for optimal performance. Health probes play a pivotal role here. If an instance is struggling, the probe diverts new connections elsewhere—like rerouting traffic during roadwork. This flow control ensures that healthy instances bear the load, maintaining overall system stability. 

Planned Downtime 

When you intentionally take an instance offline (for updates, maintenance, or scaling), health probes ensure a smooth transition. They communicate with the load balancer, signaling that the instance is temporarily unavailable. Users experience minimal disruption, and your application remains reliable. 

Now, let’s dive deeper into the conclusion 

The Unsung Heroes 

Health probes often operate in the background, quietly ensuring the stability of your applications. They don’t seek the spotlight, but their impact is profound. Here’s why they deserve recognition. 

Reliability: Health probes act as guardians, tirelessly checking the pulse of your services. When an instance falters, they swiftly reroute traffic, preventing disruptions.  

Efficiency: By directing new connections away from unhealthy instances, health probes optimize resource utilization. They ensure that your system operates smoothly even during peak loads.  

Predictability: Scheduled maintenance or updates? Health probes allow you to gracefully drain traffic from an instance, minimizing user impact. 

Best Practices 

When working with health probes, consider these best practices 

Customization: Tailor your health probes to match your application’s behavior. Choose the right protocol, set an appropriate interval, and fine-tune the parameters.   

Monitoring: Regularly review health probe logs and metrics. Detect patterns, identify bottlenecks, and fine-tune your setup.  

Documentation: Document your health probe configurations. Share knowledge within your team to ensure consistent practices.  

Conclusion :

Azure load balancer health probe serve as a critical component in maintaining the reliability, performance, and availability of applications deployed on the Azure cloud platform. By continuously monitoring the health of resources and endpoints, these probes enable proactive identification of issues, automatic remediation, and optimization of resource performance. This proactive approach not only minimizes downtime but also enhances the overall user experience by ensuring optimal performance. With customizable configurations, Azure Health Probes offer flexibility to adapt to diverse environments and specific application needs. Ultimately, incorporating Azure Health Probes into your Azure infrastructure strategy is essential for achieving high availability, mitigating risks, and delivering a seamless user experience. 

Frequently asked questions (FAQs) about Azure Load Balancer Health Probes

 An Azure load balancer health probe is a monitoring mechanism used to check the health and availability of an application or service running on Azure. 

A Azure load balancer health probe periodically sends requests to a specified endpoint (such as a URL) to determine if the application or service is responding correctly. Based on the response, Azure determines the health status of the endpoint. 

Azure supports two types of health probes: HTTP and TCP probes. HTTP probes check the health of an endpoint by sending an HTTP request, while TCP probes check the health at the TCP level without interpreting the response. 

Use an HTTP probe when you need to check the health of an endpoint based on the HTTP response (e.g., checking for specific status codes). Use a TCP probe when you only need to verify if the endpoint is reachable at the network level. 


You can configure a Azure Load Balancer health probe by defining probe settings in the Azure Load Balancer or Application Gateway associated with your application. Specify the probe type, interval, timeout, and other parameters as needed. 

 Probe settings allow you to customize how frequently Azure checks the health of your endpoints and how long it waits for a response before considering the endpoint unhealthy. 

If an endpoint fails a Azure load balancer health probe, Azure may stop routing traffic to that endpoint, directing traffic only to healthy endpoints. This helps ensure that users are not directed to unhealthy instances of your application or service. 

Yes, for HTTP probes, you can define custom criteria for a successful response, such as specific status codes or response body content. This allows you to tailor the health check to the requirements of your application. 

  There is no additional cost for using Azure health probes. However, standard Azure service charges may apply based on the resources used to host your application or service. 

Yes, Azure provides monitoring and alerting capabilities that allow you to monitor the results of Azure Load Balancer health probes and set up notifications based on specific health states or thresholds. You can use Azure Monitor and Azure Alerts for this purpose. 

Let's Share and Learn Together !



Lost password?

New to site? Create an Account

Call us for any query
Call +91 7993300102Available 24x7 for your queries