Azure Queue Storage vs Temporal
SEPT 2026 auditA comparison of Azure Queue Storage and Temporal built from values read directly from each provider's own documentation, with the source recorded against every figure.
The short answer
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
Choose Temporal if…
Long-running, stateful workflows where losing execution history is the failure that matters — Temporal keeps event history as first-class storage rather than logs that expire.
Editorial · Palash Bagchi · approved
Consider something else if…
- 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.
- Temporal: Entry is $100 a month before any usage, and the unit is an Action, which does not map onto messages or task runs — budgeting requires modelling your workflows, not counting jobs.
7 sourced criteria separate them — see where, with sources, below.
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.
Azure Queue Storage 0
Temporal 0
At a glance.
| Criterion | Azure Queue Storage | Temporal |
|---|---|---|
| Pricing | ||
| Pricing model | 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. | Per Action, with storage billed separately and split between open and closed workflows. Plans buy SLA tier and support response rather than volume — Essentials is 99.9% with one business day P0 response, Business adds scale. An open-source self-hosted edition runs the same service on your own infrastructure. |
| Queues | ||
| Included per month | 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. | 1,000,000 Actions a month on Essentials and 2.5 million on Business. An Action is Temporal's own unit — a workflow operation — and is not comparable to a message, an operation or an execution elsewhere in this category. |
| Maximum message size | 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. | 2 MB maximum payload per request (each Workflow/Activity argument or return value); 4 MB per Event History transaction, non-configurable. |
| Message retention | Messages in the queue are billed as stored data at $0.045 per GB-month on LRS, rather than granted as a retention window. Azure charges for depth, not for time. | Storage rather than a time window: 1 GB of active storage for open workflows and 40 GB retained for closed ones on Essentials, 2.5 GB active on Business. Temporal keeps workflow event history, so retention is bounded by bytes rather than by days — recorded without a magnitude because it is not the quantity this criterion ranks. |
| Maximum delay | 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. | Timers (durable sleeps) may run up to 100 years in Temporal Cloud. |
| Compliance | ||
| SOC 2 | 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. | SOC 2 Type II certified; trust center lists SOC 2 Type 2, GDPR, HIPAA and CCPA badges. |
| HIPAA | Listed among Azure's compliance offerings (HIPAA) on Microsoft's own compliance documentation — a platform-wide list, not scoped to this specific service. | Temporal Cloud is stated to be compliant with HIPAA regulations; HIPAA listed among trust-center certifications. |
Where they differ.
Pricing model
- 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.
- Temporal
- Per Action, with storage billed separately and split between open and closed workflows. Plans buy SLA tier and support response rather than volume — Essentials is 99.9% with one business day P0 response, Business adds scale. An open-source self-hosted edition runs the same service on your own infrastructure.
Sources (2) →Sources ↓
- 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
- Pricing — Temporal ↗
“Cloud platform 99.9% SLA, 99.99% HA options [...] Essentials support with 1 business day P0 response time [...] Host It Yourself Open Source Temporal Self-Hosted [...] Temporal Service Temporal SDKs Temporal CLI Temporal UI Community Support”
Read 2026-09-06 · official pricing
Included per month
- 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.
- Temporal
- 1,000,000 Actions a month on Essentials and 2.5 million on Business. An Action is Temporal's own unit — a workflow operation — and is not comparable to a message, an operation or an execution elsewhere in this category.
Sources (2) →Sources ↓
- 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
- Pricing — Temporal ↗
“Essentials Starting at $100/mo. [...] 1 M Actions 1 GB Active Storage 40 GB Retained Storage [...] Business [...] 2.5 M Actions 2.5 GB Active Storage”
Read 2026-09-06 · official pricing
Maximum message size
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.
2 MB maximum payload per request (each Workflow/Activity argument or return value); 4 MB per Event History transaction, non-configurable.
Sources (2) →Sources ↓
- 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
- Limits - Temporal Cloud | Temporal Documentation ↗
“The max payload for a single request is 2 MB. The max size limit for any given Event History transaction is 4 MB. This limit is non-configurable for Temporal Cloud.”
Read 2026-09-13 · official docs
Message retention
- Azure Queue Storage
- Messages in the queue are billed as stored data at $0.045 per GB-month on LRS, rather than granted as a retention window. Azure charges for depth, not for time.
- Temporal
- Storage rather than a time window: 1 GB of active storage for open workflows and 40 GB retained for closed ones on Essentials, 2.5 GB active on Business. Temporal keeps workflow event history, so retention is bounded by bytes rather than by days — recorded without a magnitude because it is not the quantity this criterion ranks.
Sources (2) →Sources ↓
- Azure Retail Prices API — Queues v2, eastus ↗
“"meterName": "LRS Data Stored", "unitOfMeasure": "1 GB/Month", "retailPrice": 0.045”
Read 2026-09-06 · official pricing
- Pricing — Temporal ↗
“EVENT HISTORY AND RETENTION Storage Temporal stores workflow event history as Active storage for open workflows and Retained Storage for closed workflows [...] 1 GB Active Storage 40 GB Retained Storage”
Read 2026-09-06 · official pricing
Maximum delay
- 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.
- Temporal
- Timers (durable sleeps) may run up to 100 years in Temporal Cloud.
Sources (2) →Sources ↓
- Introduction to Azure Queue Storage — Microsoft Learn ↗
“For version 2017-07-29 or later, the maximum time-to-live can be any positive number, or -1 indicating that the message doesn't expire. If this parameter is omitted, the default time-to-live is seven days.”
Read 2026-09-06 · official docs
- Limits - Temporal Cloud | Temporal Documentation ↗
“Timer duration limit Timers have a maximum duration of 100 years in Temporal Cloud.”
Read 2026-09-13 · official docs
SOC 2
- 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.
- Temporal
- SOC 2 Type II certified; trust center lists SOC 2 Type 2, GDPR, HIPAA and CCPA badges.
Sources (2) →Sources ↓
- Azure compliance documentation — Microsoft Learn ↗
“Compliance offerings [...] SOC 1 SOC 2 SOC 3”
Read 2026-09-12 · official site
- Security | Temporal ↗
“Compliance Temporal Cloud is SOC 2 Type II certified, and compliant with GDPR and HIPAA regulations.”
Read 2026-09-13 · official site
HIPAA
- 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.
- Temporal
- Temporal Cloud is stated to be compliant with HIPAA regulations; HIPAA listed among trust-center certifications.
Sources (2) →Sources ↓
- Azure compliance documentation — Microsoft Learn ↗
“Healthcare and life sciences [...] HIPAA (US)”
Read 2026-09-12 · official site
- Security | Temporal ↗
“Temporal Cloud is SOC 2 Type II certified, and compliant with GDPR and HIPAA regulations.”
Read 2026-09-13 · official site
When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.
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 Azure Queue Storage or Temporal?
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.
Pick Temporal if Long-running, stateful workflows where losing execution history is the failure that matters — Temporal keeps event history as first-class storage rather than logs that expire.