Azure Storage
Recursos únicos globalmente que proporcionan acceso a servicios de administración de datos y sirven como espacio de nombres primario para los servicios.
Azure Files SMB reports 5 TiB capacity instead of configured 100 TiB
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 83%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHC%3C/text%3E%3C/svg%3E)
Héctor Velasco
0
Puntos de reputación
We have an Azure File Share created in March 2020.
The File Share quota is configured to 102400 GiB (100 TiB).
Azure Portal shows:
- Maximum storage: 102400 GiB
- Used capacity: 4644.94 GiB
Azure CLI returns:
shareQuota = 102400
However, SMB clients receive a total capacity of only 5120 GiB.
Evidence:
- Windows Server: Get-PSDrive shows:
Used: 4645 GB Free: 475 GB - fsutil volume diskfree reports: Total bytes = 5497558138880 (5120 GiB)
- A second Windows 10 machine mapped the same Azure File Share and reports exactly the same 5 TiB capacity.
The Storage Account is:
- StorageV2
- Standard_GRS
- Access through Private Endpoint
- SMB 3.1.1
We would like Microsoft to verify why the SMB endpoint is advertising a 5 TiB capacity while ARM and the Portal report a 100 TiB quota.
Please also confirm whether the effective write limit is 100 TiB or 5 TiB.
Azure Storage
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 86%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHS%3C/text%3E%3C/svg%3E)
Harshavardhan Sriramula 0 Puntos de reputación Personal externo de Microsoft Moderador2026-07-06T17:15:42.3833333+00:00 Hello Héctor Velasco,
Thank you for providing the detailed information.
From the information shared, the Azure Portal and Azure CLI both report the file share quota as 102,400 GiB (100 TiB), while SMB clients consistently report a total capacity of approximately 5 TiB (5120 GiB). The SMB-reported values from both Windows Server and Windows 10 systems indicate that the share is being presented with a total capacity of roughly 5 TiB, despite the configured quota being significantly larger.
At this stage, we cannot conclusively determine whether:
- The SMB endpoint is advertising a 5 TiB capacity while the actual share quota remains 100 TiB, or
- There is an underlying configuration or service-side limitation causing the effective capacity exposed through SMB to remain at 5 TiB.
The documentation available confirms that Azure Files supports file shares up to 100 TiB and that quota configuration is managed independently of the client-reported capacity. However, the documentation does not specifically describe a scenario where SMB clients report a 5 TiB capacity while ARM and the Portal report a 100 TiB quota.
To help narrow this down, could you please provide:
- The Azure region of the storage account.
- The output of the following command :
1.az storage account show \
- --name <storage-account-name> \
3 --resource-group <resource-group-name>
- Whether any write operations have been attempted beyond the current usage level (~4.6 TiB).
- If available, whether writes start failing when the share usage approaches 5 TiB.
This information will help determine whether the issue is limited to SMB capacity reporting or whether the effective write capacity is also being enforced at approximately 5 TiB.
Can you please update us if the action plan provided was helpful?
Should there be any follow-up questions or concerns, please let us know and we shall try to address them.
If these answer your question, click "Upvote" which may be beneficial to other community members reading this thread.
-
Héctor Velasco 0 Puntos de reputación
2026-07-06T17:27:22.33+00:00 Thank you for your response.
Please find the requested information below.
Storage Account Region
- Region: North Central US
Storage Account configuration
The Storage Account configuration is attached. We reviewed it and did not find any configuration that would explain why SMB advertises only 5 TiB.
Key properties:
- StorageV2
- Standard_GRS
- Created: March 17, 2020
- Azure Files enabled
- File Share quota: 102400 GiB
Write operations beyond 5 TiB
We have not attempted to exceed the current usage (~4.6 TiB).
This Azure File Share is used by production IIS applications that continuously write business files.
Intentionally filling the remaining reported capacity to determine whether writes fail at approximately 5 TiB represents a production risk, therefore we cannot perform this validation.
At this point we have confirmed the following:
- Azure Portal reports a quota of 102400 GiB (100 TiB).
- Azure CLI reports shareQuota = 102400.
- Windows Server reports a total SMB capacity of 5120 GiB.
- A second Windows 10 client reports exactly the same 5120 GiB capacity.
- Therefore, the behavior is reproducible across multiple SMB clients.
Given these results, we believe this is no longer a client-side issue.
Could you please verify from the Azure backend whether this File Share is internally configured to support Large File Shares and whether the SMB endpoint is expected to advertise a 5 TiB capacity for a File Share created in March 2020?
Additionally, **could you please confirm from the service side whether the effective write limit is currently 100 TiB or 5 TiB, without requiring a production validation?**Thank you for your response.
Please find the requested information below.
Storage Account Region
- Region: North Central US
Storage Account configuration
The Storage Account configuration is attached. We reviewed it and did not find any configuration that would explain why SMB advertises only 5 TiB.
Key properties:
- StorageV2
- Standard_GRS
- Created: March 17, 2020
- Azure Files enabled
- File Share quota: 102400 GiB
Write operations beyond 5 TiB
We have not attempted to exceed the current usage (~4.6 TiB).
This Azure File Share is used by production IIS applications that continuously write business files.
Intentionally filling the remaining reported capacity to determine whether writes fail at approximately 5 TiB represents a production risk, therefore we cannot perform this validation.
At this point we have confirmed the following:
- Azure Portal reports a quota of 102400 GiB (100 TiB).
- Azure CLI reports shareQuota = 102400.
- Windows Server reports a total SMB capacity of 5120 GiB.
- A second Windows 10 client reports exactly the same 5120 GiB capacity.
- Therefore, the behavior is reproducible across multiple SMB clients.
Given these results, we believe this is no longer a client-side issue.
Could you please verify from the Azure backend whether this File Share is internally configured to support Large File Shares and whether the SMB endpoint is expected to advertise a 5 TiB capacity for a File Share created in March 2020?
Additionally, could you please confirm from the service side whether the effective write limit is currently 100 TiB or 5 TiB, without requiring a production validation?
Inicie sesión para escribir un comentario
Inicie sesión para responder