Merge pull request #274396 from mimckitt/pool-updates-5

Additional updates

Author: prmerger-automator[bot]

articles/virtual-machine-scale-sets/standby-pools-create.md

@@ -16,8 +16,6 @@ This article steps through creating a standby pool for Virtual Machine Scale Set
 > [!IMPORTANT]
 > Standby pools for Virtual Machine Scale Sets with Flexible Orchestration is currently in preview. Previews are made available to you on the condition that you agree to the [supplemental terms of use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). Some aspects of this feature may change prior to general availability (GA). 
 
-
-
 ## Prerequisites
 
 ### Feature Registration 
@@ -39,7 +37,7 @@ Alternatively, you can register directly in the Azure portal.
 
 
 ### Role-based Access Control Permissions
-In order for standby pools to successfully create Virtual Machines, you need to assign the appropriate RBAC permissions.
+To allow standby pools to create virtual machines, you need to assign the appropriate RBAC permissions.
 
 1) In the Azure portal, navigate to your subscriptions. 
 2) Select the subscription you want to adjust RBAC permissions. 

articles/virtual-machine-scale-sets/standby-pools-faq.md

@@ -17,25 +17,25 @@ ms.reviewer: ju-shim
 Get answers to frequently asked questions about standby pools for Virtual Machine Scale Sets in Azure.
 
 ### What are standby pools for Virtual Machine Scale Sets? 
-Azure standby pools is a feature for Virtual Machine Scale Sets Flexible Orchestration that enables faster scaling out of resources by creating a pool of pre-provisioned virtual machines ready to service your workload. 
+Azure standby pools is a feature for Virtual Machine Scale Sets with Flexible Orchestration that enables faster scaling out of resources by creating a pool of pre-provisioned virtual machines ready to service your workload. 
 
 ### When should I use standby pools for Virtual Machine Scale Sets? 
-Using a standby pool with your Virtual Machine Scale set can help scale out performance by performing various pre and post provisioning steps in the pool before the VM is placed into the scale set. 
+Using a standby pool with your Virtual Machine Scale Set can help improve scale-out performance by completing various pre and post provisioning steps in the pool before the instances are placed into the scale set. 
 
 ### What are the benefits of using Azure standby pools for Virtual Machine Scale Sets? 
-Standby pools is a powerful feature for accelerating your time to scale out and reducing the management needed for provisioning virtual machine resources and getting them ready to service your workload. If your applications are latency sensitive or have long initialization steps, standby pools can help with reducing that time and managing the steps to make your virtual machines ready on your behalf. 
+Standby pools is a powerful feature for accelerating your time to scale-out and reducing the management needed for provisioning virtual machine resources and getting them ready to service your workload. If your applications are latency sensitive or have long initialization steps, standby pools can help with reducing that time and managing the steps to make your virtual machines ready on your behalf. 
 
 ### Can I use standby pools on Virtual Machine Scale Sets with Uniform Orchestration?
-No. Standby pools is only supported on Virtual Machine Scale Sets with Flexible Orchestration.
+Standby pools is only supported on Virtual Machine Scale Sets with Flexible Orchestration.
 
 ### Can I use standby pools for Virtual Machine Scale Sets if I'm already using Azure autoscale? 
-No. Attaching a standby pool to a Virtual Machine Scale Set with Azure autoscale enabled is not supported.  
+Attaching a standby pool to a Virtual Machine Scale Set with Azure autoscale enabled isn't supported.  
 
 ### How many virtual machines can my standby pool for Virtual Machine Scale Sets have? 
 The maximum number of virtual machines between a scale set and a standby pool is 1,000. 
 
 ### Can my standby pool span multiple Virtual Machine Scale Sets? 
-No. A standby pool resource can't span multiple scale sets. Each scale set has its own standby pool attached to it. A standby pool inherits the unique properties of the scale set such as networking, virtual machine profile, extensions, and more. 
+A standby pool resource can't span multiple scale sets. Each scale set has its own standby pool attached to it. A standby pool inherits the unique properties of the scale set such as networking, virtual machine profile, extensions, and more. 
 
 ### How is the configuration of my virtual machines in the standby pool for Virtual Machine Scale Sets determined? 
 Virtual machines in the standby pool inherit the same virtual machine profile as the virtual machines in the scale set. Some examples are:  
@@ -49,12 +49,15 @@ Virtual machines in the standby pool inherit the same virtual machine profile as
 
 
 ### Can I change the size of my standby pool without needing to recreate it? 
-Yes. To change the size of your standby pool, simply update the max ready capacity setting.  
+Yes. To change the size of your standby pool update the max ready capacity setting.  
 
 
 ### I created a standby pool and I noticed that some virtual machines are coming up in a failed state. 
 Ensure you have enough quota to complete the standby pool creation. Insufficient quota results in the platform attempting to create the virtual machines in the standby pool but unable to successfully complete the create operation. Check for multiple types of quotas such as Cores, Network Interfaces, IP Addresses, etc.
 
+### I increased my scale set instance count but the virtual machines in my standby pool weren't used. 
+Ensure that the virtual machines in your standby pool are in the desired state prior to attempting a scale-out event. For example, if using a standby pool with the virtual machine states set to deallocated, the standby pool will only give out instances that are in the deallocated state. If instances are in any other states such as creating, running, updating, etc., the scale set will default to net new virtual machine creation. 
+
 
 ## Next steps
 

articles/virtual-machine-scale-sets/standby-pools-overview.md

@@ -21,22 +21,22 @@ Standby pools reduce the time to scale out by performing various initialization
 
 ## Scaling
 
-When your scale set requires more instances, rather than creating new instances from scratch, the scale set can instead pull virtual machines from the standby pool. This saves significant time as the virtual machines in the standby pool have already completed all post-provisioning steps. 
+When your scale set requires more instances, rather than creating new instances from scratch, the scale set instead uses virtual machines from the standby pool. This saves significant time as the virtual machines in the standby pool have already completed all post-provisioning steps. 
 
-When your scale set scales back down, the instances are deleted from your scale set based on the [scale-in policy](virtual-machine-scale-sets-scale-in-policy.md) and your standby pool will refill to meet the max ready capacity configured. If at any point in time your scale set needs to scale beyond the number of instances you have in your standby pool, the scale set defaults to standard scale-out methods and creates new instances directly in the Scale Set
+When scaling back down, the instances are deleted from your scale set based on the [scale-in policy](virtual-machine-scale-sets-scale-in-policy.md) and the standby pool refills to meet the max ready capacity configured. If at any point in time your scale set needs to scale beyond the number of instances you have in your standby pool, the scale set defaults to standard scale-out methods and creates new instances.
 
-Standby pools will only give out virtual machines from the pool that match the desired power state configured. For example, if your desired power state is set as deallocated, the standby pool will only give the Virtual Machine Scale Set instances matching that current power state. If virtual machines are in a creating, failed or any other state than the expected state, the scale set defaults to new virtual machine creation instead.
+Standby pools only give out virtual machines from the pool that match the desired power state configured. For example, if your desired power state is set as deallocated, the standby pool will only give the scale set instances matching that current power state. If virtual machines are in a creating, failed or any other state than the expected state, the scale set defaults to new virtual machine creation instead.
 
 
 ## Virtual machine states
 
 The virtual machines in the standby pool can be kept in a running state or a deallocated state. 
 
-**Deallocated:** Deallocated virtual machines are shut down and keep any associated disks, network interfaces, and any static IPs remain unchanged. [Ephemeral OS disks](../virtual-machines/ephemeral-os-disks.md) don't support the deallocated state. 
+**Deallocated:** Deallocated virtual machines are shut down and keep any associated disks, network interfaces, and any static IPs. [Ephemeral OS disks](../virtual-machines/ephemeral-os-disks.md) don't support the deallocated state. 
 
 :::image type="content" source="media/standby-pools/deallocated-vm-pool.png" alt-text="A screenshot showing the workflow when using deallocated virtual machine pools.":::
 
-**Running:** Using virtual machines in a running state is recommended when latency and reliability requirements are strict. 
+**Running:** Using virtual machines in a running state is recommended when latency and reliability requirements are strict. Virtual machines in a running state are fully provisioned. 
 
 :::image type="content" source="media/standby-pools/running-vm-pool.png" alt-text="A screenshot showing the workflow when using running virtual machine pools.":::
 
@@ -60,13 +60,13 @@ If the scale set reduces the instance count to 5, the standby pool would fill to
 
 
 ## Availability zones
-When using a standby pool with a Virtual Machine Scale Set using [availability zones](virtual-machine-scale-sets-use-availability-zones.md), the instances in the pool will be spread the same zones the Virtual Machine Scale Set is using. 
+When using standby pools with a Virtual Machine Scale Set spanning [availability zones](virtual-machine-scale-sets-use-availability-zones.md), the instances in the pool will be spread the same zones the Virtual Machine Scale Set is using. 
 
 When a scale out is triggered in one of the zones, a virtual machine in the pool in that same zone will be used. If a virtual machine is needed in a zone where you no longer have any pooled virtual machines left, the scale set creates a new virtual machine directly in the scale set. 
 
 ## Pricing
 
-There's no direct cost associated with using standby pools. Users are charged based on the resources deployed. For example, keeping virtual machines in a running state incurs compute, networking, and storage costs. While keeping virtual machines in a deallocated state doesn't incur any compute costs, but any persistent disks or networking configurations continue incur cost. For more information on virtual machine billing, see [states and billing status of Azure Virtual Machines](../virtual-machines/states-billing.md).
+Users are charged based on the resources deployed in the standby pool. For example, virtual machines in a running state incur compute, networking, and storage costs. Virtual machines in a deallocated state doesn't incur any compute costs, but any persistent disks or networking configurations continue incur cost. For more information on virtual machine billing, see [states and billing status of Azure Virtual Machines](../virtual-machines/states-billing.md).
 
 | State | Description |
 |---|---|