Skip to content
inetGeek

Amazon SQS vs Azure Queue Storage

SEPT 2026 audit

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.

Reviewed by Palash BagchiUpdated 23 criteria comparedSources last checked

The short answer

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.

Neither quite fits? Every other option, ranked by iScore: Amazon SQS alternatives · Azure Queue Storage alternatives

12 sourced criteria separate them — see where, with sources, below.

Visit Amazon SQS documentationVisit Azure Queue Storage documentation

No affiliate links, sponsored placements or paid rankings appear on this site. Ordering follows the sourced data and the stated criteria.

01.

At a glance.

CriterionAmazon SQSAzure Queue Storage
Pricing
Free tier
Yes
No
Kind of free offerFree tierFree credit
Pricing modelPer 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 region and per redundancy, metered on operations and on stored data; LRS, ZRS, GRS and GZRS are each priced separately.
Infrastructure
Uptime SLA99.9% monthly uptime per AWS Region, one figure with no configuration split.Not published as a web page. Microsoft consolidated its per-service SLAs into one downloadable document covering Azure, Dynamics 365, Office 365 and Intune; the former azure.microsoft.com SLA URLs now redirect to its licensing viewer.
Queues
Included per month1,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. Queue operations are metered from the first one at $0.004 per 10,000 Class 1 operations on LRS in East US.
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.
Message retention
4 days by default; configurable from 60 seconds up to 14 days per queue.
7 days by default, set per message with messagettl; since version 2017-07-29 it can be any positive number, or -1 for a message that never expires.
Maximum delay15 minutes maximum per-message delay (message timer) or per-queue delay; default is 0 seconds.Time-to-live defaults to seven days and can be set to any positive number, or to -1 for a message that never expires — the only queue here with an unbounded option.
Compliance
SOC 2
Listed as SOC-compliant on AWS's own compliance scope page.
Listed among Azure's compliance offerings (SOC 1, SOC 2, SOC 3) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service.
ISO 27001Covered under AWS's account-wide ISO/IEC 27001:2022 certification — not scoped per-service the way SOC, HIPAA and PCI DSS are on AWS's own site.Listed among Azure's compliance offerings (ISO 27001) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service.
HIPAA
Listed as a HIPAA-eligible service on AWS's own reference page.
Listed among Azure's compliance offerings (HIPAA) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service.
PCI DSS
Listed as PCI DSS-compliant on AWS's own compliance scope page.
Listed among Azure's compliance offerings (PCI DSS) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service.

Only criteria both providers publish appear here; a tinted cell marks a real difference. Criteria only one of them documents are listed below, and an absence there means we found no source — not that the feature is missing. How we source this.

The small bar above a value is inetGeek's own lean toward that side — computed from the same facts shown, never a number the provider published. See the picker below "The short answer" to weigh only the criteria you care about.

02.

Where they differ.

Free tier

Amazon SQS
Yes
Azure Queue Storage
No
Sources (2) →

Kind of free offer

Amazon SQS
Free tier
Azure Queue Storage
Free credit
Sources (2) →

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 region and per redundancy, metered on operations and on stored data; LRS, ZRS, GRS and GZRS are each priced separately.
Sources (2) →
  • 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 · Report a correction

  • Azure Retail Prices API — Queues v2, East US ↗

    “{"currencyCode":"USD","tierMinimumUnits":0.0,"retailPrice":0.004,"unitPrice":0.004,"armRegionName":"eastus","location":"US East","effectiveStartDate":"2017-11-01T00:00:00Z","meterId":"994899e2-0f8f-4696-80a6-d9bae770c13b","meterName":"LRS Class 1 Operations"," [...] {"currencyCode":"USD","tierMinimumUnits":0.0,"retailPrice":0.045,"unitPrice":0.045,"armRegionName":"eastus","location":"US East","effectiveStartDate":"2017-11-01T00:00:00Z","meterId":"d6b6271c-3113-44a9-9d62-b2da937da902","meterName":"LRS Data Stored"," [...] {"currencyCode":"USD","tierMinimumUnits":0.0,"retailPrice":0.0598,"unitPrice":0.0598,"armRegionName":"eastus","location":"US East","effectiveStartDate":"2022-09-01T00:00:00Z","meterId":"2187dabd-0f89-4dae-b031-8ba726c1f598","meterName":"GRS Data Stored","”

    Read 2026-09-13 · official pricing · Report a correction

Uptime SLA

Amazon SQS
99.9% monthly uptime per AWS Region, one figure with no configuration split.
Azure Queue Storage
Not published as a web page. Microsoft consolidated its per-service SLAs into one downloadable document covering Azure, Dynamics 365, Office 365 and Intune; the former azure.microsoft.com SLA URLs now redirect to its licensing viewer.
Sources (2) →

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. Queue operations are metered from the first one at $0.004 per 10,000 Class 1 operations on LRS in East US.
Sources (2) →
  • 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 · Report a correction

  • Azure Retail Prices API — Queues v2, East US ↗

    “{"currencyCode":"USD","tierMinimumUnits":0.0,"retailPrice":0.004,"unitPrice":0.004,"armRegionName":"eastus","location":"US East","effectiveStartDate":"2017-11-01T00:00:00Z","meterId":"994899e2-0f8f-4696-80a6-d9bae770c13b","meterName":"LRS Class 1 Operations"," [...] {"currencyCode":"USD","tierMinimumUnits":0.0,"retailPrice":0.004,"unitPrice":0.004,"armRegionName":"eastus","location":"US East","effectiveStartDate":"2017-11-01T00:00:00Z","meterId":"fcf5a755-9fce-4c78-8931-af0ff4562395","meterName":"Class 2 Operations","”

    Read 2026-09-13 · official pricing · Report a correction

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.

Sources (2) →

Message retention

Amazon SQS

4 days by default; configurable from 60 seconds up to 14 days per queue.

Azure Queue Storage

7 days by default, set per message with messagettl; since version 2017-07-29 it can be any positive number, or -1 for a message that never expires.

Sources (2) →

Maximum delay

Amazon SQS
15 minutes maximum per-message delay (message timer) or per-queue delay; default is 0 seconds.
Azure Queue Storage
Time-to-live defaults to seven days and can be set to any positive number, or to -1 for a message that never expires — the only queue here with an unbounded option.
Sources (2) →

SOC 2

Amazon SQS
Listed as SOC-compliant on AWS's own compliance scope page.
Azure Queue Storage
Listed among Azure's compliance offerings (SOC 1, SOC 2, SOC 3) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service.
Sources (2) →

ISO 27001

Amazon SQS
Covered under AWS's account-wide ISO/IEC 27001:2022 certification — not scoped per-service the way SOC, HIPAA and PCI DSS are on AWS's own site.
Azure Queue Storage
Listed among Azure's compliance offerings (ISO 27001) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service.
Sources (2) →

HIPAA

Amazon SQS
Listed as a HIPAA-eligible service on AWS's own reference page.
Azure Queue Storage
Listed among Azure's compliance offerings (HIPAA) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service.
Sources (2) →

PCI DSS

Amazon SQS
Listed as PCI DSS-compliant on AWS's own compliance scope page.
Azure Queue Storage
Listed among Azure's compliance offerings (PCI DSS) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service.
Sources (2) →

When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.

Confirm by email; unsubscribe from any issue. Your address goes to Kit and nowhere else — what we do with it.

03.

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 — except where we say we read the other provider's own page on a given date and it does not state it. Those rows lean, and the provider can correct them with a link.

What the free plan includesAzure Queue Storage: $200 of Azure credit for 30 days on a new account; no standing Queue Storage allowance is published.
When the free offer endsAzure Queue Storage: 30 days.
Entry paid planAmazon SQS: No paid plan or minimum fee; billed per request after the free 1 million requests a month.
RegionsAmazon SQS: 34 commercial AWS Regions plus 2 AWS GovCloud (US) Regions listed in the SQS service endpoints table.
ConcurrencyAmazon SQS: Approximately 120,000 in-flight messages per standard queue (received but not yet deleted); API call rate on standard queues is nearly unlimited.
Dead letter queueAmazon SQS: Supported
GDPR / data residencyAmazon SQS: AWS customers can process personal data on all AWS services in compliance with GDPR, and choose the storage type and geographic region for their data.
Encryption at restAmazon SQS: Server-side encryption of queue contents with SQS-managed keys (SSE-SQS) or AWS KMS keys (SSE-KMS).
Customer-managed keysAmazon SQS: Supported via SSE-KMS: queues can use a customer managed KMS key created and policy-controlled in AWS KMS.
Role-based access controlAmazon SQS: IAM identity-based policies on users, groups and roles plus resource-based queue policies control access to queues and actions.
Private networking / VPCAmazon SQS: Interface VPC endpoints (AWS PrivateLink) let a VPC reach SQS privately, including FIPS endpoints; HTTPS endpoints only.
04.

Questions this comparison answers.

Free tier: Amazon SQS or Azure Queue Storage?

Amazon SQS: Yes

Azure Queue Storage: No

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.

Provider pages

Amazon SQSAWS managed message queue, billed per request with standard and FIFO rates and a permanent free tier.Azure Queue StorageMicrosoft's managed queue, billed per 10,000 operations with queued messages charged as stored data.

Related comparisons

Amazon SQS vs Cloudflare QueuesAmazon SQS vs Google Cloud Pub/SubAmazon SQS vs HatchetAmazon SQS vs InngestAmazon SQS vs TemporalAmazon SQS vs Trigger.devAmazon SQS vs ZeploAzure Queue Storage vs Google Cloud Pub/Sub

Comments

Every page here is sourced and dated.