Overview
LocalStack’s developer tools build on the emulator and take care of the work around it. They start and stop LocalStack for you, keep its configuration in one place, and let your AI assistant drive it. The Azure Portal Emulator gives you a visual way to browse and manage what you’ve deployed: it’s a local version of the Azure Portal, served by the emulator itself. All of this lets you spend your time on the Azure application you’re actually building.
This section covers the tools that work with LocalStack for Azure today.
Limitations
Section titled “Limitations”LocalStack for Azure is younger than LocalStack for AWS, and not every developer tool of the AWS emulator is available for Azure yet. If you’re coming from the AWS side, this is what you won’t find here:
- Snapshots and persistence: The Azure emulator can’t save or restore its state yet. Cloud Pods and the
lstk saveandlstk loadcommands don’t work with it, and the resources you create are gone once the emulator’s container stops. - App Inspector, Chaos Engineering, and AWS Replicator: These tools are built around AWS services and work with the AWS emulator only.
- Security Testing: The IAM tools, such as IAM Policy Stream and Explainable IAM, are specific to AWS. For Azure, you can have the emulator enforce role assignments instead; see Enabling RBAC enforcement.
- Lambda Tools: Hot reloading and remote debugging are made for AWS Lambda, and there’s no equivalent for Azure Functions yet.
- Cloud Sandbox: Ephemeral Instances and Application Previews aren’t available for the Azure emulator yet.
- LocalStack Desktop: The desktop app doesn’t support the Azure emulator, and its Resource Browser can’t show Azure resources.
Missing a tool you rely on? Let us know at support@localstack.cloud, so we can prioritize it.