Merge pull request #189693 from meenasaravanan02/main

SF Scaling limitations update

Author: PRMerger16

articles/service-fabric/how-to-managed-cluster-autoscale.md

@@ -17,7 +17,7 @@ ms.date: 2/14/2022
 * Only [Azure Monitor published metrics](../azure-monitor/essentials/metrics-supported.md) are supported.
 
 >[!NOTE] 
-> If using an OS Image "-with-containers” memory metrics from Azure Monitor will not be available. 
+> If using Windows OS image with Hyper-V role enabled, ie. the VM will be configured for nested virtualization, the Available Memory Metric will not be available, since the dynamic memory driver within the VM will be in a stopped state.
 
 
 A common scenario where autoscaling is useful is when the load on a particular service varies over time. For example, a service such as a gateway can scale based on the amount of resources necessary to handle incoming requests. Let's take a look at an example of what those scaling rules could look like and we'll use them later in the article:

articles/service-fabric/service-fabric-cluster-scale-in-out.md

@@ -24,7 +24,7 @@ Virtual machine scale sets are an Azure compute resource that you can use to dep
 >
 >
 > [!NOTE]
-> If using an OS Image "-with-containers” memory metrics from Azure Monitor will not be available.
+> If using Windows OS image with Hyper-V role enabled, ie. the VM will be configured for nested virtualization, the Available Memory Metric will not be available, since the dynamic memory driver within the VM will be in a stopped state.
 >
 >