Amazon SQS vs Azure Queue Storage
A comparison of Amazon SQS and Azure Queue Storage built from values read directly from each provider's own documentation, with the source recorded against every figure.
The short answer
- Pick Amazon SQS if
- AWS-resident systems that want a queue with a permanent free million requests a month and no capacity to plan — SQS scales without a throughput setting to choose.
- Pick Azure Queue Storage if
- Azure-resident systems that want a queue billed like storage — operations plus depth, no plan to choose and no capacity to provision.
3 sourced criteria separate them:
- Pricing model
- Amazon SQS: Per request, not per message: every API action counts, and a 1 MiB payload is billed as 16 requests. FIFO queues cost $0.50 per million against standard's $0.40 in us-east-1, and fair queue requests add $0.10 per million on top of the standard rate.
- Azure Queue Storage: Per 10,000 operations plus stored data, with the rate set by redundancy: LRS Class 1 operations are $0.004 per 10,000, ZRS and GRS cost more for the same call. There is no plan fee and no included allowance.
- Included per month
- Amazon SQS: 1,000,000 requests a month free, permanently and across all regions. Beyond that, standard queues are $0.40 per million in us-east-1, falling to $0.30 above 100 billion and $0.24 above 200 billion.
- Azure Queue Storage: None included — every operation is billed. Class 1 operations are $0.004 per 10,000 on LRS in East US, which is $0.40 per million, matching Amazon SQS's standard rate exactly.
- Maximum message size
- Amazon SQS: 256 KB per message. A single request carries 1 to 10 messages up to 1 MiB total, and each 64 KB chunk of payload is billed as one request.
- Azure Queue Storage: 64 KB per message. A queue may hold millions of messages, bounded only by the storage account's capacity rather than a queue-level ceiling.
Pick the criteria you care about. The chart counts how many of them lean toward each provider — the same read as scanning the bars below, just totalled for the ones you chose.
Amazon SQS 0
Azure Queue Storage 0
At a glance.
| Criterion | Amazon SQS | Azure Queue Storage |
|---|---|---|
| Pricing | ||
| Pricing model | Per request, not per message: every API action counts, and a 1 MiB payload is billed as 16 requests. FIFO queues cost $0.50 per million against standard's $0.40 in us-east-1, and fair queue requests add $0.10 per million on top of the standard rate. | Per 10,000 operations plus stored data, with the rate set by redundancy: LRS Class 1 operations are $0.004 per 10,000, ZRS and GRS cost more for the same call. There is no plan fee and no included allowance. |
| Queues | ||
| Included per month | 1,000,000 requests a month free, permanently and across all regions. Beyond that, standard queues are $0.40 per million in us-east-1, falling to $0.30 above 100 billion and $0.24 above 200 billion. | None included — every operation is billed. Class 1 operations are $0.004 per 10,000 on LRS in East US, which is $0.40 per million, matching Amazon SQS's standard rate exactly. |
| Maximum message size | 256 KB per message. A single request carries 1 to 10 messages up to 1 MiB total, and each 64 KB chunk of payload is billed as one request. | 64 KB per message. A queue may hold millions of messages, bounded only by the storage account's capacity rather than a queue-level ceiling. |
Where they differ.
Pricing model
- Amazon SQS
- Per request, not per message: every API action counts, and a 1 MiB payload is billed as 16 requests. FIFO queues cost $0.50 per million against standard's $0.40 in us-east-1, and fair queue requests add $0.10 per million on top of the standard rate.
- Azure Queue Storage
- Per 10,000 operations plus stored data, with the rate set by redundancy: LRS Class 1 operations are $0.004 per 10,000, ZRS and GRS cost more for the same call. There is no plan fee and no included allowance.
Sources (2) →Sources ↓
- AWS Price List API — AWSQueueService, us-east-1 ↗
“"$0.50 per million Amazon SQS FIFO requests in Tier1 in US East" [...] "$0.40 per million Amazon SQS standard requests in Tier1" [...] "$0.10 per million Amazon SQS fair queue requests in US East"”
Read 2026-09-06 · official pricing
- Azure Retail Prices API — Queues v2, eastus ↗
“"LRS Class 1 Operations", "10K", 0.004 [...] "ZRS Class 2 Operations", "10K", 0.004 [...] "GRS Class 1 Operations", "10K", 0.008”
Read 2026-09-06 · official pricing
Included per month
- Amazon SQS
- 1,000,000 requests a month free, permanently and across all regions. Beyond that, standard queues are $0.40 per million in us-east-1, falling to $0.30 above 100 billion and $0.24 above 200 billion.
- Azure Queue Storage
- None included — every operation is billed. Class 1 operations are $0.004 per 10,000 on LRS in East US, which is $0.40 per million, matching Amazon SQS's standard rate exactly.
Sources (2) →Sources ↓
- AWS Price List API — AWSQueueService, us-east-1 ↗
“"First 1,000,000 Amazon SQS Requests per month are free" [...] "$0.40 per million Amazon SQS standard requests in Tier1 in US East" [...] "$0.30 per million ... Tier2" [...] "$0.24 per million ... Tier3"”
Read 2026-09-06 · official pricing
- Azure Retail Prices API — Queues v2, eastus ↗
“"productName": "Queues v2", "meterName": "LRS Class 1 Operations", "unitOfMeasure": "10K", "retailPrice": 0.004”
Read 2026-09-06 · official pricing
Maximum message size
256 KB per message. A single request carries 1 to 10 messages up to 1 MiB total, and each 64 KB chunk of payload is billed as one request.
64 KB per message. A queue may hold millions of messages, bounded only by the storage account's capacity rather than a queue-level ceiling.
Sources (2) →Sources ↓
- Amazon SQS Pricing — AWS ↗
“A single request can have from 1 to 10 messages, up to a maximum total payload of 1 MiB. [...] Each 64 KB chunk of a payload is billed as 1 request (for example, an API action with a 1 MiB payload is billed as 16 requests).”
Read 2026-09-06 · official docs
- Introduction to Azure Queue Storage — Microsoft Learn ↗
“A queue message can be up to 64 KB in size. A queue may contain millions of messages, up to the total capacity limit of a storage account.”
Read 2026-09-06 · official docs
When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.
Which should you choose?
Choose Amazon SQS if…
AWS-resident systems that want a queue with a permanent free million requests a month and no capacity to plan — SQS scales without a throughput setting to choose.
Editorial · Palash Bagchi · approved
Choose Azure Queue Storage if…
Azure-resident systems that want a queue billed like storage — operations plus depth, no plan to choose and no capacity to provision.
Editorial · Palash Bagchi · approved
Consider something else if…
- Amazon SQS: Billing is per request rather than per message, and a 1 MiB payload counts as sixteen, so chatty polling or large messages cost far more than the message count suggests.
- Azure Queue Storage: Queued messages are billed as stored data, so a backlog costs money by the gigabyte-month, and there is no free allowance at all where SQS gives a million requests a month.
Documented by only one.
These criteria are published by one provider and not the other. An absence here means we have not found a source, not that the feature is missing.
Questions this comparison answers.
Should I choose Amazon SQS or Azure Queue Storage?
Pick Amazon SQS if AWS-resident systems that want a queue with a permanent free million requests a month and no capacity to plan — SQS scales without a throughput setting to choose.
Pick Azure Queue Storage if Azure-resident systems that want a queue billed like storage — operations plus depth, no plan to choose and no capacity to provision.