What LocalStack for Azure is
It is an Azure emulator that runs in a container, and teams can use it to build and test Azure apps without provisioning live resources. The container runs on infrastructure you control. The idea is to point development and test workloads at the local endpoint, then deploy validated code to real Azure for staging or production. Teams point workloads at the container endpoint using existing application code and Infrastructure as Code files.
It is LocalStack's third product, following its AWS and Snowflake emulators. LocalStack says those products are used by more than 1,500 organizations and see more than 18 million weekly active user sessions. These are company figures, and I haven't seen any independent audit of them.
The tool is for development and testing. LocalStack says it speeds up work before you deploy to Azure and doesn't replace Azure.
What the preview covers
LocalStack's launch post names these targets:
- Containers: Azure Kubernetes Service (AKS) and Azure Container Apps.
- Serverless and data: Azure Functions, Web Apps, Storage Account and Cosmos DB.
- Security and networking: Key Vault, Managed Identity and Private Endpoint. Private Endpoint is mocked where applicable.
- Infrastructure as code: ARM templates, Bicep templates and Terraform modules.
The company says it is deliberately not claiming parity with all of Azure. It points users to a supported-services page that lists known limitations and workarounds for each service. Check that page against your own architecture before you commit.
The launch post makes broad claims such as "no rewrites needed" and "high-fidelity" behavior. Treat these as vendor claims for supported services and tools, not a guarantee that everything behaves like Azure. LocalStack's own documentation lists workflow options beyond the launch post's IaC list. These include the Azure CLI, Azure PowerShell and SDKs. One summary of the product page also mentions Pulumi, though that summary was cut off, so I can't confirm the full list.
What's missing at launch
This matters because the news coverage leans on features the preview doesn't have.
- No App Inspector, snapshots or chaos APIs. LocalStack says developer experience features, including App Inspector, snapshots, and chaos APIs, aren't included at preview launch. According to LocalStack, some may arrive during the preview and others after GA.
- No snapshot claims for Azure yet. IT Brief UK says the containerised setup can make environments easier to snapshot and reproduce. LocalStack's own materials say snapshots aren't in the Azure preview at launch. Futurum's analyst described the beta as basic emulation of a short list of services. Futurum says the features that differentiate LocalStack on AWS are planned for Azure at general availability.
- Preview access is temporary. Preview access ends at GA, and LocalStack says it will give at least 30 days' notice and publish transition steps ahead of time.
Cost and timeline
The preview is free. Nothing is charged during the preview, pricing will be announced at GA, and GA is currently expected in early 2027. If you build CI pipelines around the preview now, you don't yet know what they will cost later. Budget for that uncertainty.
How to try it
- Sign up for the Azure preview plan on the LocalStack for Azure pricing page. If you already use LocalStack for AWS, sign in with your existing account and add the Azure preview plan.
- Follow the Getting Started guide to start the emulator and run your first workload.
- Share issues and requests in the LocalStack GitHub discussions.
LocalStack describes access as self-serve. WindowsForum's own hands-on write-up mentions token requirements and no state persistence. It says service gaps, token requirements and no state persistence limit the tool's use before real Azure. Expect an auth token step when you set it up.
Why developers might care
The pitch is familiar to anyone who has waited on a cloud deployment. LocalStack describes the usual Azure loop as deploying to a dev environment, waiting, checking logs, fixing and redeploying. It adds that access requests and shared environments can turn a one-line fix into an afternoon.
LocalStack lists these benefits:
- Faster feedback. Supported services run on your machine, so you aren't waiting on remote provisioning.
- Isolated sandboxes. Each developer, or each AI agent, can have a separate environment, so tests don't collide.
- Less dev/test spend. LocalStack says local runs don't consume Azure resources.
- A bounded place for AI agents. Agents can deploy, break and retry without live credentials.
HyperFRAME Research's Stephanie Walter says local simulation is becoming a safety and verification layer for autonomous software development. Co-founder and CTO Waldemar Hummer says the company saw strong demand from its community to bring LocalStack to Azure. Both statements are perspectives, not measured results. No independent testing in the material I reviewed confirms emulator fidelity or security outcomes.
Caveats before adopting it
- An emulator is not Azure. Identity policies, service integrations, quotas, networking and production configuration can behave differently. Keep a live Azure staging step in your pipeline.
- "Safe" still needs work. Running locally removes the need for live cloud credentials in the sandbox. It doesn't secure the host, container, secrets or CI runners for you.
- Check coverage first. Other Azure services may appear in the documentation catalogue, such as Event Hubs. LocalStack's October 14 tutorial covers building an Event Hubs app locally. Still, only the services in the launch post are named as preview targets. Confirm each service you depend on, and note its limitations.
- Beta churn. A preview can change, and pricing is undecided. Avoid making it a hard dependency on critical paths until GA terms are known.
Bottom line
LocalStack for Azure gives Azure teams a free way to test supported services and IaC locally before they touch a subscription. That is useful for AKS, Functions, Cosmos DB and Terraform or Bicep workflows. The tool is also early. It has a short service list, no snapshots, App Inspector or chaos tooling yet, and no pricing. The sensible approach is to try it on a non-critical project, compare the supported-services notes with your architecture, and keep validating against real Azure.
Update: Additional details (October 31, 2026)
InfoQ reports that several security settings are stored but not enforced in the preview. App Service access restrictions and HTTPS-only settings do not take effect, and the emulator does not route virtual network traffic or enforce network security rules.
For Storage, InfoQ says data-plane requests with any bearer token succeed unless RBAC enforcement is enabled. It also reports that apps created on a Windows App Service plan run in a Linux runtime locally. These differences mean a successful local test may not validate security or runtime behavior in Azure.
References
- LocalStack for Azure Enters Public Preview with Security Settings Stored but Not Enforced - infoq.com infoq.com · 2026-10-31T07:57:00+00:00
- LocalStack launches public beta for Azure developers - IT Brief UK IT Brief UK · 2026-10-22T16:30:00+00:00
- LocalStack for Azure localstack.cloud