Merge pull request #130 from MicrosoftDocs/main

9/12 11:00 AM IST Publish

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-health-extension.md

@@ -24,7 +24,7 @@ This article assumes that you're familiar with:
 -	[Modifying](virtual-machine-scale-sets-upgrade-policy.md) Virtual Machine Scale Sets
 
 > [!CAUTION]
-> Application Health Extension expects to receive a consistent probe response at the configured port `tcp` or request path `http/https` in order to label a VM as *Healthy*. If no application is running on the VM, or you're unable to configure a probe response, your VM is going to show up as *Unhealthy* (Binary Health States) or *Unknown* (Rich Health States).
+> Application Health Extension expects to receive a consistent probe response at the configured port `tcp` or request path `http/https` in order to label a VM as *Healthy*. If no application is running on the VM, or you're unable to configure a probe response, your VM is going to show up as *Unhealthy* (Binary Health States) or *Unknown* (Rich Health States). See [application health samples](https://github.com/Azure-Samples/application-health-samples) for examples of emitting health probe responses to a local endpoint. 
 
 > [!NOTE]
 > Only one source of health monitoring can be used for a Virtual Machine Scale Set, either an Application Health Extension or a Health Probe. If you have both options enabled, you will need to remove one before using orchestration services like Instance Repairs or Automatic OS Upgrades.
@@ -506,6 +506,9 @@ az vmss update-instances \
 
 ## Troubleshoot
 
+### Need help configuring a probe response
+See [application health samples](https://github.com/Azure-Samples/application-health-samples) for examples of emitting health probe responses to a local endpoint. 
+
 ### View VMHealth - single instance
 ```azurepowershell-interactive
 Get-AzVmssVM 

articles/virtual-machines/extensions/health-extension.md

@@ -21,7 +21,7 @@ Application health monitoring is also available on virtual machine scale sets an
 This article assumes that you're familiar with [Azure virtual machine extensions](overview.md).
 
 > [!CAUTION]
-> Application Health Extension expects to receive a consistent probe response at the configured port `tcp` or request path `http/https` in order to label a VM as *Healthy*. If no application is running on the VM, or you're unable to configure a probe response, your VM is going to show up as *Unhealthy* (Binary Health States) or *Unknown* (Rich Health States).
+> Application Health Extension expects to receive a consistent probe response at the configured port `tcp` or request path `http/https` in order to label a VM as *Healthy*. If no application is running on the VM, or you're unable to configure a probe response, your VM is going to show up as *Unhealthy* (Binary Health States) or *Unknown* (Rich Health States).  See [application health samples](https://github.com/Azure-Samples/application-health-samples) for examples of emitting health probe responses to a local endpoint. 
 
 ## When to use the Application Health extension
 Application Health Extension reports on application health from inside the Virtual Machine. The extension probes on a local application endpoint and updates the health status based on TCP/HTTP(S) responses received from the application. This health status is used by Azure to monitor and detect patching failures during [Automatic VM Guest Patching](../automatic-vm-guest-patching.md).
@@ -419,6 +419,10 @@ The following example adds the Application Health extension to an existing virtu
 
 ---
 ## Troubleshoot
+
+### Need help configuring a probe response
+See [application health samples](https://github.com/Azure-Samples/application-health-samples) for examples of emitting health probe responses to a local endpoint. 
+
 ### View VMHealth
 
 # [REST API](#tab/rest-api)