What was announced
Temporal announced at Microsoft Ignite that Temporal Cloud is available as a public preview on Microsoft Marketplace. Access to the Azure preview is limited and will be granted on a rolling basis. The Business Wire release is dated November 18, 2026. Temporal's own changelog entry is dated November 17. The available sources don't explain the one-day gap.
The Azure preview follows an earlier stage. Temporal's changelog shows an invite-only pre-release of Temporal Cloud on Azure on June 1, 2026. The public preview extends that work to more customers. It is not a fresh start.
It's a new place to run the same service
Temporal describes Azure as a new deployment option for the existing service, not a separate product or a new set of features. The practical points:
- Teams can run Temporal Cloud namespaces in supported Azure regions alongside their existing namespaces on AWS and Google Cloud.
- Temporal operates the managed service, including the control plane and persistence layer. Customers still deploy and run the Workers that execute their application code.
- Customer code stays in the customer's environment, and Workers initiate the connections to Temporal Cloud.
- The programming model, SDKs, tools and APIs match those on AWS and Google Cloud, so Workflows and Activities work the same way on every cloud.
- Temporal says Azure namespace pricing is the same as on AWS and Google Cloud. No price schedule was published in the material reviewed.
Where it runs and how to get in
The preview supports production workloads in Central US (centralus) and Australia East (australiaeast). Access is by approval so Temporal can plan capacity around each workload. Temporal says existing pre-release customers will be onboarded first.
To request access, contact your Temporal account team or Temporal Support with your preferred region, use case, and expected workload. Temporal's changelog says other regions can be requested but aren't guaranteed.
For this reason, "public preview" is a loose label. Temporal's release-stage guide says public-preview features are available to everyone in principle. It also says Temporal Cloud may limit onboarding to keep the service stable. That is what is happening here.
Resilience limits to check first
Temporal's Azure region reference lists the regional endpoints:
- Central US:
centralus.azure.api.temporal.io:7233, with Cloud API codeazure-centralus. - Australia East:
australiaeast.azure.api.temporal.io:7233, with Cloud API codeazure-australiaeast.
The same reference says same-region replication is not available in either region. It also lists no Azure-to-Azure multi-region replication. Cross-cloud replication targets are listed instead:
- Central US can replicate to AWS regions ca-central-1, us-east-1, us-east-2 and us-west-2, and to GCP regions us-central1, us-west1 and us-east4.
- Australia East can replicate to AWS ap-southeast-2.
Temporal's changelog says Azure namespaces are independent from namespaces in other clouds unless you configure replication. Cross-cloud replication and failover work within the same geography, in North America and within Europe. Cross-continent replication and migration, for example from the US to Asia, is not supported today.
A Temporal documentation pull request on GitHub gives a likely reason for the gaps. It says same-region and Azure-to-Azure multi-region pairs aren't listed yet because each Azure region currently runs one cell and each geography has one Azure region. The same pull request says the Temporal Cloud SLA applies during the Azure public preview. That is documentation-in-progress rather than a finished policy page, so check the SLA terms with Temporal before relying on them.
For disaster-recovery planning, the practical conclusion is that high availability here means cross-cloud pairing. It is not an Azure-only paired-region design.
Security and connectivity
Temporal says Azure namespaces support API key or mTLS authentication. Role-based access control and SAML single sign-on are available. For private connectivity, Temporal lists Azure Private Link with Connectivity Rules. Its region reference says each account must request its Private Link service alias from Temporal Dev Success.
Temporal's namespace documentation adds some mechanics:
- Azure regions become selectable only after access is enabled for your account.
- A namespace needs a name, a region and cloud provider, a retention period of 1 to 90 days, and an authentication method.
- If you use mTLS, you also need the CA certificate.
- Temporal also lists an optional Codec Server endpoint.
- For API or CLI management of Azure namespaces, use
azure-centralusorazure-australiaeastas the region identifier, along with the Temporal CLI Cloud extension. Temporal saystcldis not supported for this task.
The Microsoft AI angle
The press release says Temporal is also delivering integrations with Microsoft Foundry and Microsoft Agent Framework, and that both work with Temporal Cloud on Azure. Per the company, developers can deploy Temporal-powered agents through Microsoft Foundry, connecting Foundry's hosting and runtime experience with Durable Execution. Developers can also use Temporal to run Agent Framework workflows, with progress preserved through crashes, timeouts and restarts.
These integration descriptions, the executive quotes, and the list of customers using Temporal technology (Alaska Airlines, Cloudflare, Coinbase and Netflix) all come from the company's press release. Temporal's changelog and documentation confirm the Azure deployment and its operating terms. They don't detail the Foundry or Agent Framework integrations. The customer names are also not evidence that any of those organizations use the Azure preview.
What is still unknown
The material reviewed does not establish:
- Marketplace billing mechanics
- Azure-native support terms beyond the SLA note above
- Dates for additional regions
- Performance or reliability benchmarks for the Azure preview
Temporal says the participation limits exist so it can work with early customers, evaluate performance and reliability, and prepare for general availability.
Checklist before requesting access
- Confirm that Central US or Australia East meets your data-location and latency needs.
- Prepare a concrete request: region, use case and expected workload.
- Decide who will deploy and operate the Workers.
- Choose between API keys and mTLS, and decide whether you need Private Link.
- Design any cross-cloud replication deliberately, because it is not on by default.
- Ask Temporal about the SLA, Marketplace billing and support terms before committing production workloads.
For teams already on Azure, the draw is an Azure-hosted option for the same Temporal service. The preview limits, the lack of Azure-to-Azure replication and the approval step all mean it needs planning rather than a quick signup.
References
- Temporal Cloud Enters Public Preview on Microsoft Azure - The Joplin Globe The Joplin Globe · 2026-11-18T19:00:06+00:00
- Document Azure public preview by bechols · Pull Request #5698 · temporalio/documentation · GitHub github.com
- Temporal Cloud on Azure is in Public Preview temporal.io