Azure Files – Partition & Performance Simulator

Azure Files uses file shares as the unit of performance. Unlike Blob/Table storage, partitioning isn't controlled via naming — performance depends on share size, tier, protocol, and IOPS/throughput limits. This simulator helps you model whether your share configuration meets workload needs.

⚙️ Configuration

Storage Tier

Protocol

Number of File Shares Azure limit: 1 – 50 (Premium) / 250 (Standard) per storage account

Provisioned Size per Share (GiB) Azure limit: 100 – 102,400 GiB (100 TiB) per share

Total Files (across all shares) 500,000

Average File Size (KiB) Max single file: 4 TiB (4,194,304 KiB)

Target IOPS Azure limit: Premium up to 100,000 / Standard up to 10,000 per share

Target Throughput (MiB/s) Azure limit: Premium up to 10,240 / Standard up to 300 MiB/s

Concurrent Users / Connections Up to 10,000 concurrent connections per share

File Distribution Across Shares

📊 Results Summary

Total Provisioned IOPS

Total Provisioned Throughput

IOPS Utilization

Throughput Utilization

📏 Capacity & Limits Gauges

📈 Per-Share Load Distribution

Files, IOPS, and throughput allocated per share

🌡️ IOPS per Share vs. Limit

💡 Recommendations

📚 Azure Files Performance Tiers

Azure Files limits are per-share, based on tier and provisioned size:

Tier	Baseline IOPS	IOPS Formula	Max Throughput	Max Share Size
Premium (SSD)	3,000	3,000 + 1 × provisioned GiB	~100 MiB/s + 0.04 × GiB	100 TiB
Transaction Optimized	10,000	Up to 10,000	Up to 300 MiB/s	100 TiB
Cool	10,000	Up to 10,000	Up to 300 MiB/s	100 TiB