# LocalStack Azure Emulator Enters Public Preview With Functional Gaps LocalStack launches Azure emulation for local testing while highlighting significant security enforcement limitations. - **Source:** [InfoQ](https://brifing.si/source/68ac18af-a4f3-4f7c-9c2c-44d4af8f89dd) - **Published:** 2026-10-31 - **Topic:** [Software & Engineering](https://brifing.si/c/engineering) - **Original article:** - **On Brifing:** https://brifing.si/s/867fc704-36ee-41b4-9745-42f22b618e03 ## LocalStack Azure Public Preview LocalStack has released its Azure emulator into public preview, offering a free, self-serve environment for developers. The project aims to support ARM and Bicep templates, Terraform modules, and Pulumi programs without requiring code rewrites. General availability is currently targeted for early 2027, providing a sandbox for testing cloud applications locally. ## Leadership and Fidelity Goals The project is led by Paolo Salvatori, a former Microsoft principal with 28 years of experience and creator of Service Bus Explorer. He established a clear fidelity contract for the team: if a solution functions correctly on Azure but fails within the emulator, the team considers it a bug requiring a fix. ## Scope of Resource Support The emulator supports a broad range of services including AKS, Functions, Cosmos DB, and Key Vault. However, implementation depth varies significantly across providers. For instance, Storage Accounts currently covers only 13 of 81 operations, while App Service supports 143 out of 616, indicating that many advanced cloud features remain partially implemented. ## Security Enforcement Limitations A critical caveat is that many security settings are stored but not enforced. Configurations like httpsOnly, access restrictions, and authentication settings are accepted by the emulator but do not actually restrict traffic. Consequently, applications may pass local security tests while remaining vulnerable or misconfigured when deployed to the actual Azure production environment. ## Networking and Data Gaps The emulator does not route network traffic or enforce security rules, and features like VNet integration, peering, and VPN gateways are currently unimplemented. Data-plane requests often succeed with any bearer token if RBAC enforcement is disabled. Furthermore, the emulator fails to validate specific request headers, leading to potential discrepancies between local and cloud. ## Runtime and Hardware Constraints Developers should note that web apps created on Windows plans run in Linux containers within the emulator. Additionally, the Oryx build image is limited to amd64 architecture, causing build failures on Apple Silicon machines. App Service state is held exclusively in memory, meaning all data is lost once the emulator process stops. ## Comparison to Microsoft Tooling Microsoft provides isolated local tools like Azurite for storage, the Cosmos DB emulator, and Azure Functions Core Tools. Unlike these individual utilities, LocalStack attempts to compose a unified environment where full ARM or Bicep deployments can be exercised end-to-end. This integration is the primary value proposition for architects seeking streamlined local development workflows. ## Strategic Implications for Testing While the emulator offers a sandbox for AI agents and rapid iteration without live credentials, the lack of enforcement creates a false sense of security. Developers must remain aware that local success does not guarantee production readiness. Future updates are expected to address these gaps before the transition to general availability in 2027. ## Sources covering this story - https://www.infoq.com/news/2026/10/localstack-azure-preview/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._