Merge pull request #76852 from roygara/lfsStandard

Lfs standard

Author: ktoliver

articles/storage/common/storage-scalability-targets.md

@@ -40,6 +40,9 @@ For more information on the scale and performance targets for Azure Files and Az
 
 > [!IMPORTANT]
 > Storage account limits apply to all shares. Scaling up to the max for storage accounts is only achievable if there is only one share per storage account.
+>
+> Standard file shares larger than 5 TiB are in preview and have certain limitations.
+> For a list of limitations and to onboard to the preview of these larger file share sizes, see the [Standard file shares](../files/storage-files-planning.md#standard-file-shares) section of the Azure Files planning guide.
 
 [!INCLUDE [storage-files-scale-targets](../../../includes/storage-files-scale-targets.md)]
 

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

@@ -71,8 +71,23 @@ If you are using Azure File Sync to access your Azure file share, we will always
 
 Azure Files offers two performance tiers: standard and premium.
 
-* **Standard file shares** are backed by rotational hard disk drives (HDDs) that provide reliable performance for IO workloads that are less sensitive to performance variability such as general-purpose file shares and dev/test environments. Standard file shares are only available in a pay-as-you-go billing model.
-* **Premium file shares (preview)** are backed by solid-state disks (SSDs) that provide consistent high performance and low latency, within single-digit milliseconds for most IO operations, for the most IO-intensive workloads. This makes them suitable for a wide variety of workloads like databases, web site hosting, development environments, etc. Premium file shares are only available in a provisioned billing model. Premium file shares use a deployment model separate from standard file shares.
+### Standard file shares
+
+Standard file shares are backed by hard disk drives (HDDs). Standard file shares provide reliable performance for IO workloads that are less sensitive to performance variability such as general-purpose file shares and dev/test environments. Standard file shares are only available in a pay-as-you-go billing model.
+
+Standard file shares up to 5 TiB in size are available as a GA offering. While larger file shares, which are any shares larger than 5 TiB, up to a maximum of 100 TiB, are currently available as a preview offering.
+
+> [!IMPORTANT]
+> - Requires you to create a new general purpose storage account (cannot expand existing storage accounts).
+> - Are only available with LRS.
+> - Available in three regions: West US 2, West Europe, and SE Asia regions.
+> - LRS to GRS account conversion will not be possible on any new storage account created after the subscription is accepted to the larger file shares preview.
+
+If you'd like to onboard to the preview of these larger file share sizes, submit this [form](https://aka.ms/azurefilesatscalesurvey). 
+
+### Premium file shares (preview)
+
+Premium file shares (preview) are backed by solid-state disks (SSDs). Premium file shares provide consistent high performance and low latency, within single-digit milliseconds for most IO operations, for IO-intensive workloads. This makes them suitable for a wide variety of workloads like databases, web site hosting, development environments, etc. Premium file shares are only available in a provisioned billing model. Premium file shares use a deployment model separate from standard file shares.
 
 Azure Backup is available for premium file shares and Azure Kubernetes Service supports premium file shares in version 1.13 and above.
 

articles/storage/files/storage-files-scale-targets.md

@@ -40,7 +40,13 @@ For example: A single share can achieve 100,000 IOPS and a single file can scale
 Premium file shares are provisioned in a special storage account called **filestorage (preview)**. This account has slightly different scale targets than the storage account used for standard file shares. For the storage account scale targets, refer to the table in the [Azure storage account scale targets](#azure-storage-account-scale-targets) section.
 
 > [!IMPORTANT]
-> Storage account limits apply to all shares. Scaling up to the max for storage accounts is only achievable if there is only one share per storage account.
+> Storage account limits apply to all shares. Scaling up to the max for FileStorage accounts is only achievable if there is only one share per FileStorage account.
+
+### File share and file scale targets
+
+> [!NOTE]
+> Standard file shares larger than 5 TiB are in preview and have certain limitations.
+> For a list of limitations and to onboard to the preview of these larger file share sizes, see the [Standard file shares](storage-files-planning.md#standard-file-shares) section of the planning guide.
 
 [!INCLUDE [storage-files-scale-targets](../../../includes/storage-files-scale-targets.md)]
 

includes/azure-storage-limits.md

@@ -27,15 +27,15 @@ The following table describes default limits for Azure general-purpose v1, v2, a
 <sup>1</sup>Azure Standard Storage accounts support higher limits for ingress by request. To request an increase in account limits for ingress, contact [Azure Support](https://azure.microsoft.com/support/faq/).
 
 <sup>2</sup> [Azure Storage replication](https://docs.microsoft.com/azure/storage/common/storage-redundancy) options include:
-* **RA-GRS**: Read-access geo-redundant storage. If RA-GRS is enabled, egress targets for the secondary location are identical to those for the primary location.
-* **GRS**: Geo-redundant storage. 
-* **ZRS**: Zone-redundant storage.
-* **LRS**: Locally redundant storage. 
+- **RA-GRS**: Read-access geo-redundant storage. If RA-GRS is enabled, egress targets for the secondary location are identical to those for the primary location.
+- **GRS**: Geo-redundant storage.
+- **ZRS**: Zone-redundant storage.
+- **LRS**: Locally redundant storage.
 
 > [!NOTE]
 > We recommend that you use a general-purpose v2 storage account for most scenarios. You can easily upgrade a general-purpose v1 or an Azure Blob storage account to a general-purpose v2 account with no downtime and without the need to copy data.
 >
-> For more information on Azure Storage accounts, see [Storage account overview](../articles/storage/common/storage-account-overview.md). 
+> For more information on Azure Storage accounts, see [Storage account overview](../articles/storage/common/storage-account-overview.md).
 
 If the needs of your application exceed the scalability targets of a single storage account, you can build your application to use multiple storage accounts. You can then partition your data objects across those storage accounts. For information on volume pricing, see [Azure Storage pricing](https://azure.microsoft.com/pricing/details/storage/).
 

includes/storage-files-scale-targets.md

@@ -8,12 +8,12 @@ ms.author: rogarana
 | Resource | Standard file shares | Premium file shares (preview) |
 |----------|---------------|------------------------------------------|
 | Minimum size of a file share | No minimum; pay as you go | 100 GiB; provisioned |
-| Maximum size of a file share | 5 TiB | 100 TiB |
+| Maximum size of a file share | 5 TiB (GA), 100 TiB (preview) | 100 TiB |
 | Maximum size of a file in a file share | 1 TiB | 1 TiB |
 | Maximum number of files in a file share | No limit | No limit |
-| Maximum IOPS per share | 1,000 IOPS | 100,000 IOPS |
+| Maximum IOPS per share | 1,000 IOPS (GA), 10,000 IOPS (preview) | 100,000 IOPS |
 | Maximum number of stored access policies per file share | 5 | 5 |
-| Target throughput for a single file share | Up to 60 MiB/sec | See premium file share ingress and egress values|
+| Target throughput for a single file share | Up to 60 MiB/sec (GA), up to 300 MiB/sec (preview) | See premium file share ingress and egress values|
 | Maximum egress for a single file share | See standard file share target throughput | Up to 6,204 MiB/s |
 | Maximum ingress for a single file share | See standard file share target throughput | Up to 4,136 MiB/s |
 | Maximum open handles per file | 2,000 open handles | 2,000 open handles |