Merge pull request #260163 from hilaryw29/patch-21

Update virtual-machine-scale-sets-health-extension.md

Author: prmerger-automator[bot]

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*.
+> 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).
 
 > [!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.
@@ -258,6 +258,7 @@ PUT on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/
 ```json
 {
   "name": "myHealthExtension",
+  "location": "<location>", 
   "properties": {
     "publisher": "Microsoft.ManagedServices",
     "type": "ApplicationHealthWindows",
@@ -383,6 +384,7 @@ PUT on `/subscriptions/subscription_id/resourceGroups/myResourceGroup/providers/
 ```json
 {
   "name": "myHealthExtension",
+  "location": "<location>",
   "properties": {
     "publisher": "Microsoft.ManagedServices",
     "type": "ApplicationHealthWindows",