Merge pull request #310326 from khdownie/kendownie010926

cleanup planning guide

Author: prmerger-automator[bot]

articles/storage/files/storage-files-planning.md

@@ -11,6 +11,7 @@ ms.custom: references_regions
 ---
 
 # Plan to deploy Azure Files
+
 You can deploy [Azure Files](storage-files-introduction.md) in two main ways: by directly mounting the serverless Azure file shares or by caching file shares on-premises using Azure File Sync. Deployment considerations differ based on which option you choose.
 
 - **Direct mount of an Azure file share**: Because Azure Files provides either Server Message Block (SMB) or Network File System (NFS) access, you can mount Azure file shares on-premises or in the cloud using the standard SMB or NFS clients available in your OS. Because Azure file shares are serverless, deploying for production scenarios doesn't require managing a file server or NAS device. This means you don't have to apply software patches or swap out physical disks. You can either choose to use Azure classic file shares or Microsoft.FileShares (preview) as your management model.
@@ -20,11 +21,12 @@ You can deploy [Azure Files](storage-files-introduction.md) in two main ways: by
 This article primarily addresses deployment considerations for deploying an Azure file share to be directly mounted by an on-premises or cloud client. To plan for an Azure File Sync deployment, see [Planning for an Azure File Sync deployment](../file-sync/file-sync-planning.md).
 
 ## Management concepts
+
 In Azure, a *resource* is a manageable item that you create and configure within your Azure subscriptions and resource groups. Resources are offered by *resource providers*, which are management services that deliver specific types of resources. While you may work with many resources to deploy a workload in Azure, Azure Files centers on two key resources:
 
 - **Storage accounts**, offered by the `Microsoft.Storage` resource provider. Storage accounts are top-level resources that represent a shared pool of storage, IOPS, and throughput in which you can deploy **classic file shares** or other storage resources, depending on the storage account kind. All storage resources that are deployed into a storage account share the limits that apply to that storage account. Classic file shares support both the SMB and NFS file sharing protocols.
 
-- **File shares** (preview), offered by the `Microsoft.FileShares` resource provider. File shares are a new top-level resource that simplify the deployment of Azure Files by eliminating the storage account. Unlike classic file shares, which must be deployed into a storage account, file shares are deployed directly into the resource group like storage accounts themselves, or other Azure resources you may be familiar with like virtual machines, disks, or virtual networks. File shares support the NFS file sharing protocol - if you require SMB, choose classic file shares for your deployment.
+- **File shares** (preview), offered by the `Microsoft.FileShares` resource provider. File shares are a new top-level resource that simplify the deployment of Azure Files by eliminating the need for a storage account. Unlike classic file shares, which must be deployed into a storage account, file shares are deployed directly into the resource group like storage accounts themselves, or other Azure resources like virtual machines, disks, or virtual networks. Currently, `Microsoft.FileShares` only supports the NFS file sharing protocol. If you require SMB, choose classic file shares.
 
 ![Image comparing file shares and classic Azure file shares](./media/storage-files-planning/file-share-comparison.png)
 
@@ -34,33 +36,36 @@ This video provides a comprehensive overview of the differences between the stor
 
 
 ### Classic file shares (Microsoft.Storage)
+
 Classic file shares, or file shares deployed in storage accounts, are the traditional way to deploy file shares for Azure Files. They support all of the key features that Azure Files supports including SMB and NFS, SSD and HDD media tiers, every redundancy type, and in every region. While classic file shares support the entire breadth of Azure Files features, they have important key limitations:
 
-- **Capacity planning**: Classic file shares, and the child objects for other storage services like blob containers, that live within the same storage account share a common pool of storage, IOPS, and throughput. This means placing multiple classic file shares in a storage account requires planning to avoid capacity bottlenecks. When capacity planning for classic file shares, you need to consider both the current and future needs of each classic file share placed in a storage account since the growth of one classic file share can crowd out other file shares.
+- **Capacity planning**: Classic file shares, as well as the child objects like blob containers that live within the same storage account, share a common pool of storage, IOPS, and throughput. This means placing multiple classic file shares in a storage account requires planning to avoid capacity bottlenecks. When planning for classic file shares, you need to consider both the current and future needs of each classic file share placed in a storage account, since the growth of one classic file share can crowd out other file shares.
 
-- **Shared settings**: Many important settings, such as network and security rules, are applied at the storage account level, so as a result, placing classic file shares in the same storage account requires careful consideration. You should consider the storage account to be a trust boundary and only place classic file shares in the same storage account if you're ok with them having the same security settings.
+- **Shared settings**: Many important settings, such as network and security rules, are applied at the storage account level. As a result, placing classic file shares in the same storage account requires careful consideration. You should consider the storage account to be a trust boundary and only place classic file shares in the same storage account if you're ok with them having the same security settings.
 
-- **Scaling complexity**: Large scale deployments of Azure Files can require managing many Azure subscriptions due the constraints on storage accounts from the `Microsoft.Storage` resource provider. See [storage account limits](./storage-files-scale-targets.md#storage-account-data-plane-limits) for more information.
+- **Scaling complexity**: Large scale Azure Files deployments can require managing many Azure subscriptions due the constraints on storage accounts from the `Microsoft.Storage` resource provider. See [storage account limits](./storage-files-scale-targets.md#storage-account-data-plane-limits) for more information.
 
 [!INCLUDE [storage-files-file-share-management-concepts](../../../includes/storage-files-file-share-management-concepts.md)]
 
 To learn more, see [Create a classic file share](./create-classic-file-share.md).
 
 ### File shares (Microsoft.FileShares)
-File shares (preview) are a new top-level Azure resource provided by the `Microsoft.FileShares` resource provider. File shares offer the following advantages over classic file shares:
 
-- **Simplified management**: File shares are created directly as top-level resources in the portal or through management APIs. This removes the requirement to manage a storage account and streamlines the deployment experience.
+File shares (preview) are a new top-level Azure resource provided by the `Microsoft.FileShares` resource provider. These file shares offer the following advantages over classic file shares:
+
+- **Simplified management**: File shares are created directly as top-level resources in the Azure portal or through management APIs. This removes the requirement to manage a storage account and streamlines the deployment experience.
 
-- **Independent capacity and performance**: Each file share has it's own dedicated storage, IOPS, and throughput. This avoids the need to do capacity planning against your storage accounts limited resources and enables file shares to freely grow as workload demands grow.
+- **Independent capacity and performance**: Each file share has its own dedicated storage, IOPS, and throughput. This avoids the need to do capacity planning against your storage account's limited resources and enables file shares to freely grow as workload demands grow.
 
 - **Granular configuration**: Networking and security settings are applied at the file share level, giving you precise control of access boundaries and isolation. This makes it easier to enforce security policies for specific apps, teams, or environments.
 
-- **Predictable, flexible billing**: File shares use the provisioned v2 billing model, which enables you to independently provision storage, IOPS, and throughput per share. Because billing in Azure is done per top-level Azure resource, using file shares enables you to easily track the costs of each individual share for cost attribution back to the project, team, or customer that is using the file share.
+- **Predictable, flexible billing**: File shares use the provisioned v2 billing model, which enables you to independently provision storage, IOPS, and throughput per share. Because billing in Azure is done per top-level Azure resource, this enables you to easily track the costs of each individual share for cost attribution back to the project, team, or customer that is using the file share.
 
 - **Improved scale and performance**: File shares support higher limits and lower deployment times than classic file shares. For more information, see [Azure Files scalability and performance targets](./storage-files-scale-targets.md).
 
 #### Regional availability
-Currently, creating a file share with Microsoft.FileShares (preview) is available in the following regions:
+
+Currently, creating a file share with Microsoft.FileShares (preview) is available in the following regions. Private endpoint support for file share with Microsoft.FileShares (preview) is available in all Azure public cloud regions.
 
 - Australia East
 - Australia Central
@@ -75,10 +80,6 @@ Currently, creating a file share with Microsoft.FileShares (preview) is availabl
 - South India
 - UAE Central
 
-Currently, private endpoint support for file share with Microsoft.FileShares (preview) is available in a limited subset of regions:
-
-- All Azure public cloud regions.
-
 #### Comparing resource providers: Microsoft.Storage versus Microsoft.FileShares
 
 | Feature | Classic file shares ![fileshareclassicicon1](./media/storage-files-planning/icon-service-file-share.svg) | File shares (Microsoft.FileShares) ![mfsicon](./media/storage-files-planning/icon-service-Managed-File-Shares.svg) |
@@ -105,6 +106,7 @@ Currently, private endpoint support for file share with Microsoft.FileShares (pr
 | Data plane REST APIs | ![Yes](../media/icons/yes-icon.png) | ![No](../media/icons/no-icon.png) |
 
 ## Available protocols
+
 Azure Files offers two industry-standard file system protocols for mounting Azure file shares: the [Server Message Block (SMB)](files-smb-protocol.md) protocol and the [Network File System (NFS)](files-nfs-protocol.md) protocol, allowing you to choose the protocol that is the best fit for your workload. Azure file shares don't support both the SMB and NFS protocols on the same file share, although you can create SMB and NFS Azure file shares within the same storage account.
 
 With both SMB and NFS file shares, Azure Files offers enterprise-grade file shares that can scale up to meet your storage needs and can be accessed concurrently by thousands of clients.
@@ -141,6 +143,7 @@ With both SMB and NFS file shares, Azure Files offers enterprise-grade file shar
 | File system transactions (TxF) | Not supported | N/A |
 
 ## Identity
+
 To access an Azure file share, the user of the file share must be authenticated and authorized to access the share. This is done based on the identity of the user accessing the file share. Azure Files supports the following methods of authentication:
 
 - **On-premises Active Directory Domain Services (AD DS, or on-premises AD DS)**: Azure storage accounts can be domain joined to a customer-owned Active Directory Domain Services, just like a Windows Server file server or NAS device. You can deploy a domain controller on-premises, in an Azure VM, or even as a VM in another cloud provider; Azure Files is agnostic to where your domain controller is hosted. Once a storage account is domain-joined, the end user can mount a file share with the user account they signed into their PC with. AD-based authentication uses the Kerberos authentication protocol.
@@ -251,7 +254,3 @@ The [migration overview article](storage-files-migration-overview.md) briefly co
 - [Deploying Azure Files](./storage-how-to-create-file-share.md)
 - [Deploying Azure File Sync](../file-sync/file-sync-deployment-guide.md)
 - [Check out the migration overview article to find the migration guide for your scenario](storage-files-migration-overview.md)
-
-
-
-