General Availability: Azure Files geo-redundancy for standard large file shares
Azure Files is excited to announce that geo-redundancy for 100 TiB standard SMB file shares is now generally available, enabling customers to achieve higher resiliency for production scale workloads.
We previously offered 100 TiB standard SMB shares for locally redundant storage (LRS) and zone-redundant storage (ZRS) options but geo-redundant storage (GRS/GZRS) was limited to 5 TiB, restricting higher capacity and performance workloads from using this resiliency option.
Geo-redundancy is critical to ensure high availability and to meet various compliance and regulatory requirements for your production workloads (for example, line-of-business (LOB) applications). Geo-redundant storage asynchronously replicates to a secondary region enabling you to failover to the secondary region, if the primary region becomes unavailable.
You don't have to compromise on performance and scale or geo-redundancy for your SMB file shares anymore! All standard SMB file shares that are geo-redundant (both new and existing) can now scale up to 100TiB capacity and have much higher performance limits:
|
Azure Files (GRS and GZRS file shares) |
Previous limits |
New limits |
|
Capacity per share |
5 TiB |
100 TiB (20x increase) |
|
Max IOPS per share |
1,000 IOPS |
Up to storage account limit (20x increase) |
|
Max throughput per share |
Up to 60 MiB/s |
Up to storage account limit (150x increase) |
For more information on Azure storage redundancy and choosing what’s right for you, see Azure Storage redundancy.
Pricing and availability
Pricing is based on the standard file share tier and redundancy option configured for the storage account. To learn more, see Azure Files Pricing.
Azure Files geo-redundancy for large file shares is now generally available in 30 regions and we will be expanding to all regions in the coming months. To view the latest information, see regional availability.
Getting started
Getting started is simple and can be accomplished in a few steps:
- Register for the feature using portal or PowerShell.
- Enable geo-redundancy and large file shares for your standard file shares.
Note: We will enable large file shares by default for all new and existing standard storage accounts within the next few months and feature registration will no longer be required.
To learn more, see the Azure Files geo-redundancy for large file shares documentation.
Feedback
If you have questions or feedback, please reach out to us at [email protected].
Published on:
Learn moreRelated posts
Scalable AI with Azure Cosmos DB: Tredence Intelligent Document Processing (IDP) | March 2026
Azure Cosmos DB enables scalable AI-driven document processing, addressing one of the biggest barriers to operational scale in today’s enterpr...
Announcing the end of support for Node.js 20.x in the Azure SDK for JavaScript
After July 9, 2026, the Azure SDK for JavaScript will no longer support Node.js 20.x. Upgrade to an Active Node.js Long Term Support (LTS) ver...
MCP Apps on Azure Functions: Quickstart with TypeScript
Learn how to build and deploy MCP (Model Context Protocol) apps on Azure Functions using TypeScript. This guide covers MCP tools, resources, l...
Setting up Power BI Version Control with Azure Dev Ops
In this blog post is a way set up version control for Power BI semantic models (and reports) using the PBIP (Power BI Project) format, Azure D...
Azure Developer CLI (azd) – March 2026: Run and Debug AI Agents Locally, GitHub Copilot Integration, & Container App Jobs
Run, invoke, and monitor AI agents locally or in Microsoft Foundry with the new azd AI agent extension commands. Plus GitHub Copilot-powered p...
Writing Azure service-related unit tests with Docker using Spring Cloud Azure
This post shows how to write Azure service-related unit tests with Docker using Spring Cloud Azure. The post Writing Azure service-related uni...
Azure SDK Release (March 2026)
Azure SDK releases every month. In this post, you find this month's highlights and release notes. The post Azure SDK Release (March 2026) appe...
Specifying client ID and secret when creating an Azure ACS principal via AppRegNew.aspx will be removed
The option to specify client ID and secret when creating Azure ACS principals will be removed. Users must adopt the system-generated client ID...