There is no single IOPS limit for Azure Storage. The applicable target depends on whether you use Azure Files, Blob Storage, or VM disks—and on whether the figure applies to an account, share, file, blob, or partition. Microsoft’s published figures are targets, not guaranteed application performance; identify the service and resource scope before comparing them with your workload.
Azure Storage IOPS targets by service
The figures below are Microsoft-published targets or maximums for the stated resource scopes, as reflected in Microsoft’s service documentation reviewed on September 28, 2026. They are not results from an independent performance test. Regional availability, configuration, and documented targets can change; consult the relevant Microsoft page for current details before sizing a deployment.
| Service and configuration | Published figure | Scope and qualification |
|---|---|---|
| Azure Files, provisioned v2 SSD share | 3,000 minimum and 102,400 maximum provisioned IOPS | Provisioned share IOPS. Microsoft also lists a maximum of 12,000 data IOPS for an individual SSD file; that per-file figure is not the share target. |
| Standard Azure Storage account | 40,000 requests per second in the regions named by Microsoft; 20,000 requests per second in regions not named | Account request-rate targets, not a guarantee that an arbitrary workload will achieve the same application-level IOPS. Check Microsoft’s current regional list. |
| Blob Storage, single object | Up to 3,000 requests per second for a single block blob; up to 500 requests per second for a single page blob | Per-blob request-rate targets. A hot partition can encounter performance issues before the overall account target is reached. |
| VM disks using a standard storage account | Maximum total request rate of 20,000 IOPS | Microsoft states that the total IOPS of unmanaged VM disks in the account should not exceed this account limit. This is not a general limit for every managed-disk SKU. |
These values are not interchangeable. A share target, per-file maximum, account request rate, per-blob target, and unmanaged-disk account limit describe different bottlenecks. Azure Files account and share limits also matter; do not assume the per-file figure is available to every file at once.
What IOPS means in Azure
IOPS means input/output operations per second. Azure documentation may instead describe requests or transactions per second for a particular API or resource. Those rates do not automatically translate into the number of useful operations an application completes: request size, operation type, concurrency, and client behavior all affect the relationship.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →#1 Best Overall
IOPS is only one part of performance. Throughput measures how much data moves over time; latency measures how long an operation takes. A workload with large I/O can reach a throughput ceiling before it reaches an IOPS target, while many small operations may stress request rate or latency. Queue depth, read/write mix, access pattern, client capacity, and network distance also shape observed results. Microsoft’s Azure Files performance guidance identifies I/O size and queue depth as relevant factors.
Why a published target is not a guaranteed result
Microsoft describes scalability figures as targets because achieved request rate and bandwidth depend on object size, access patterns, and workload. Its Blob Storage performance guidance also notes that some target values can be increased upon request. Neither statement means every workload will reach the published figure, or that a quota increase removes other service, partition, client, or network bottlenecks.
Blob performance can be limited locally: a hot partition may develop latency or return HTTP 500 Operation Timeout and HTTP 503 Server Busy responses even when aggregate account use remains below the account-wide target. Treat those responses and rising latency as signs to investigate request distribution and workload shape, not just the account total.
How to find the relevant limit for your workload
- Identify the service and SKU. Establish whether the workload uses Azure Files, Blob Storage, or VM disks, and record the tier or provisioning model. Do not compare a standard-account request target with a premium share or a specific disk SKU as if they were the same measure.
- Pin down the resource scope. Determine whether the candidate bottleneck is the account, share, file, blob, partition, or disk. For VM disks, confirm whether the documented standard-account guidance applies to unmanaged disks.
- Record the deployment context. Note the region, redundancy configuration, and relevant account or share settings. For regional targets, verify that the deployment’s region appears in Microsoft’s current list.
- Measure representative traffic. Capture request or I/O size, read/write mix, concurrency or queue depth, throughput, latency, and errors under a workload that resembles production. A single peak IOPS number is not enough to establish whether the system meets the application’s needs.
- Correlate symptoms with scope. Check whether rising latency or HTTP 500/503 responses coincide with a hot partition or a service/account ceiling. Compare measurements at the affected resource as well as at the account level.
Ways to improve storage performance
- Reduce concentrated traffic. Where the design permits, distribute Blob requests across partitions instead of directing a disproportionate share to one hot partition. Smooth sudden bursts when possible.
- Back off on service-busy responses. For Blob requests receiving HTTP 503, use exponential backoff rather than immediately retrying at full speed; aggressive retries can add load during a spike.
- Choose a tier suited to the workload. Microsoft recommends SSD shares for Azure Files workloads that need high IOPS, fast transfer, or low latency. Confirm the relevant account, share, and file constraints for the chosen configuration.
- Evaluate Blob design options against measured needs. For workloads that need higher transaction rates or lower latency than standard targets provide, assess premium block blob accounts. Locating the storage account in the same region as clients can reduce network latency, but neither choice guarantees a particular end-to-end IOPS result.
- Use the supported client tooling. For custom Blob applications, Microsoft recommends its Storage client libraries, which incorporate performance practices. Client code and connection behavior remain part of the end-to-end result.
- Retest after changes. Validate the actual application workload after changing tiers, request distribution, client behavior, or deployment location; published service targets alone cannot confirm the outcome.
How to compare Azure storage options
Before choosing or resizing a service, compare like with like. A useful decision record includes:
Rank #3
- 8 DI (Dry contact)，4 DO Relay output control，8 AI 4-20mA interface can be connected to sensors of various specifications.
- Supports Multiple Industry-Standard Communication Protocols: Modbus TCP, SNMP, BACnet, and MQTT. Our system is compatible with all these protocols and can deliver data in multiple formats simultaneously. Comprehensive support for SNMP v1/v2/v3 and SNMP Trap v2c/v3. High security product: supports TLS encrypted communication, featuring both unidirectional and bidirectional certificate authentication capabilities.
- Proactive Alerts – Instant email notifications when thresholds are exceeded (fully customizable triggers). IFTTT Automation – Trigger smart actions (e.g., activate HVAC, log to Google Sheets, or Telegram alerts) via Webhook integration.
- Using the standard MQTT protocol, a real IoT direct connected product, building a cost-effective application system for AWS/Azure/Tuya.
- Support Lua scripts for on-site logic programming, allows users to perform secondary development.
- service, tier, and provisioning model;
- resource scope for each performance figure;
- region and redundancy configuration;
- published IOPS or request-rate target and throughput target, if stated for that exact scope;
- per-file, per-blob, per-disk, or partition considerations;
- your workload’s I/O size, read/write mix, concurrency, latency requirement, and client location;
- any regional availability or quota-increase condition.
If a comparable figure is not published for the exact configuration, do not infer one from another service or scope. Use the applicable Microsoft service documentation and validate performance with a representative workload.
Quick Recap
Best Value
Rank #4
- Compact Design: The Throwing Star LAN Tap features compact design that makes it incredibly portable. This passive Ethernet tap J1 J2 seamlessly integrates into your network without requiring power, allowing for easy installation and monitoring. By simply connecting it with Ethernet cables, users can obtain network traffic effectively, making it an essential tool for network monitoring.
- Efficient Monitoring: With dedicated monitoring ports, J3 and J4, the Throwing Star LAN Tap focuses on specific traffic directions, providing accurate and detailed insights. This targeted approach ensures that no vital network data is lost. It's suitable for users aiming to monitor IPTV source connections or obtain network packets efficiently.
- User Friendly Setup: Designed for convenience, this tap allows easy connection to existing network setups without complicated configurations. Simply attach the device to a network segment to start capturing data packets with your preferred software like tcpdump or . Its adaptable nature makes it suitable for both novices and experienced users looking to improve their network monitoring capabilities.
- Reliable Construction: Housed in a plastic shell, the Throwing Star LAN Tap is built to withstand the rigors of frequent use. The robust design ensures longevity and reliable performance in diverse environments, making it a trusted module for net monitoring.
- Versatile Compatibility: Compatible with various network equipment, making it a versatile tool for different monitoring scenarios. It operates seamlessly with a variety of Ethernet standards and configurations, accommodating users' unique needs. Whether assessing network traffic or establishing connectivity, this device consistently delivers excellent performance and flexibility.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
