Add references to the Pv2 model in AFS documentation.

Author: wmgries

articles/storage/file-sync/file-sync-deployment-guide.md

@@ -21,9 +21,10 @@ We strongly recommend that you read [Planning for an Azure Files deployment](../
 
 # [Portal](#tab/azure-portal)
 
-1. An **Azure file share** in the same region that you want to deploy Azure File Sync. For more information, see:
+1. An **Azure file share** in the same region that you want to deploy Azure File Sync. We recommended provisioned v2 file shares for all new deployments. For more information, see:
     - [Region availability](file-sync-planning.md#azure-file-sync-region-availability) for Azure File Sync.
     - [Create a file share](../files/storage-how-to-create-file-share.md?toc=/azure/storage/filesync/toc.json) for a step-by-step description of how to create a file share.
+    - [Understanding the provisioned v2 billing model](../files/understanding-billing.md#provisioned-v2-model) for information on the how to use the provisioned v2 model.
 2. The following **storage account** settings must be enabled to allow Azure File Sync access to the storage account:  
     -  **SMB security settings** must allow **SMB 3.1.1** protocol version, **NTLM v2** authentication and **AES-128-GCM** encryption. To check the SMB security settings on the storage account, see [SMB security settings](../files/files-smb-protocol.md#smb-security-settings).
     -  **Allow storage account key access** must be **Enabled**. To check this setting, navigate to your storage account and select Configuration under the Settings section. 

includes/storage-file-sync-cost-categories.md

@@ -14,14 +14,15 @@
 
 - **Per server licensing cost for servers registered with Azure File Sync.** To use Azure File Sync with a specific Windows File Server, you must first register it with Azure File Sync's Azure resource, the Storage Sync Service. Each server that you register after the first server has a flat monthly fee. Although this fee is very small, it is one component of your bill to consider. To see the current price of the server registration fee for your desired region, see [the File Sync section on Azure Files pricing page](https://azure.microsoft.com/pricing/details/storage/files/).
 
-- **Azure Files costs.** Because Azure File Sync is a synchronization solution for Azure Files, it will cause you to consume Azure Files resources. Some of these resources, like storage consumption, are relatively obvious, while others such as transaction and snapshot utilization may not be. For most customers, we recommend using standard file shares with Azure File Sync, although Azure File Sync is fully supported with premium file shares if desired.
-    - **Storage utilization.** Azure File Sync will replicate any changes you have made to the path on your Windows File Server specified on your server endpoint to your Azure file share, thus causing storage to be consumed. On standard file shares, this means that adding or increasing the size of existing files on server endpoints will cause storage costs to grow, because the changes will be replicated. On premium file shares, changes will be consume provisioned space - it is your responsibility to periodically increase provisioning as needed to account for file share growth.
+- **Azure Files costs.** Because Azure File Sync is a synchronization solution for Azure Files, it will cause you to consume Azure Files resources. Some of these resources, like storage consumption, are relatively obvious, while others such as transaction and snapshot utilization may not be. For most customers, we recommend using HDD provisioned v2 file shares with Azure File Sync, although Azure File Sync on all Azure Files billing models (SSD provisioned v2, SSD provisioned v1, or HDD pay-as-you-go).
+    - **Storage utilization.** Azure File Sync will replicate any changes you have made to the path on your Windows File Server specified on your server endpoint to your Azure file share, thus causing storage to be consumed. On provisioned file shares, changes will be consume provisioned space, so it is your responsibility to periodically increase provisioning as needed to account for file share growth. On pay-as-you-go file shares, this means that adding or increasing the size of existing files on server endpoints will cause storage costs to grow, because the changes will be replicated. 
 
     - **Snapshot utilization.** Azure File Sync takes share and file-level snapshots as part of regular usage. Although snapshot utilization is always differential, this can contribute in a noticeable way to the total Azure Files bill.
 
-    - **Transactions from churn.** As files change on server endpoints, the changes are uploaded to the cloud share, which generates transactions. When cloud tiering is enabled, additional transactions are generated for managing tiered files, including I/O happening on tiered files, in addition to egress costs. Although the quantity and type of transactions is difficult to predict due to churn rates and cache efficiency, you can use your previous transaction patterns to estimate future costs if you believe your future usage will be similar to your current usage. 
-    
-    - **Transactions from cloud enumeration.** Azure File Sync enumerates the Azure File Share in the cloud once per day to discover changes that were made directly to the share so that they can sync down to the server endpoints. This scan generates transactions which are billed to the storage account at a rate of one `ListFiles` transaction per directory per day. You can put this number into the [pricing calculator](https://azure.microsoft.com/pricing/calculator/) to estimate the scan cost.  
+    - **IOPS / throughput utilization**: Azure File Sync will drive IOPS and throughput utilization to transfer changes from your server endpoints to your Azure file share. If you are using a provisioned file share, you should monitor your file share usage to ensure that you have enough IOPS and throughput provisioned that you aren't throttled. If you are using a pay-as-you-go file share, you are charged for the IOPS utilization in the form of transactions. Generally, there are two types of transactions to consider:
+        - **Transactions from churn.** As files change on server endpoints, the changes are uploaded to the cloud share, which generates transactions. When cloud tiering is enabled, additional transactions are generated for managing tiered files, including I/O happening on tiered files, in addition to egress costs. Although the quantity and type of transactions is difficult to predict due to churn rates and cache efficiency, you can use your previous transaction patterns to estimate future costs if you believe your future usage will be similar to your current usage. 
+        
+        - **Transactions from cloud enumeration.** Azure File Sync enumerates the Azure File Share in the cloud once per day to discover changes that were made directly to the share so that they can sync down to the server endpoints. This scan generates transactions which are billed to the storage account at a rate of one `ListFiles` transaction per directory per day. You can put this number into the [pricing calculator](https://azure.microsoft.com/pricing/calculator/) to estimate the scan cost.  
 
-    > [!Tip]  
-    > If you don't know how many folders you have, check out the TreeSize tool from JAM Software GmbH.
+        > [!Tip]  
+        > If you don't know how many folders you have, check out the TreeSize tool from JAM Software GmbH.