Changelog

What's new in Locally

What's in each release of Locally - new features, improvements and fixes.

Preview

During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in

v2026.11.03

This release contains:

Bug Fixes

  • Container DNS: fixing an issue on macOS where, when Podman or Docker was started after Locally, the containers Locally then launched (including Web Apps) couldn't resolve *.locally host names, so couldn't connect to Locally's services. Locally now starts its DNS forwarder once the container runtime comes up.
  • Container Runtime: fixing an issue where Locally failed to start when LOCALLY_CONTAINER_RUNTIME was set and the container runtime was slow to respond the first time, as Podman can be on a fresh CI runner. Locally now waits up to 30 seconds for it.
  • Startup: fixing an issue where, when one of Locally's services failed to start, locally build and locally ci kept waiting for it and then reported a connection error, rather than stopping straight away with the reason it failed.
  • Web Apps: fixing an issue on Linux where a Web App couldn't connect to another Web App, a Storage Account, a Key Vault or most other Locally services named in its app settings, since their *.locally host names resolved to the app's own container. This affected apps calling each other using .NET Aspire's service discovery.

v2026.11.02

This release contains:

Enhancements

  • Containers: a new Launch Timeout feature flag sets how long a container backing a resource is given to start, for machines where pulling the image takes longer than the default 300 seconds, such as CI runners. It can be changed in Settings -> Feature Flags.

v2026.11.01

This release contains:

Bug Fixes

  • Locally Snapshots: fixing an issue where comparing two snapshots of the same instance showed a token signing key as one removed and one added. Signing keys are now left out of the comparison, as tokens are - locally snapshot diff --all still compares them.
  • Managed Identities: fixing an issue where the search box did nothing when adding a role assignment to a managed identity in the Dashboard.
  • Monitor: fixing an issue where the Telemetry page in the Dashboard listed every standard Log Analytics table for a workspace, almost all of them empty. It now lists the tables holding data, with a search box for the rest.
  • Monitor: fixing an issue where a query on the Telemetry page in the Dashboard failed with a time range selected when it summarised by something other than time, as three of the common queries do.
  • Policy: fixing an issue where choosing resource types for a policy parameter in the Dashboard (such as Allowed resource types) saved names that matched no resources, and didn't show the types already chosen. The list can now be filtered by name.

v2026.11

Locally Snapshots and Multiple Tenants

This release contains Locally Snapshots, Management Groups and Tenants, many more Chaos Engineering faults, and a number of bug fixes:

Breaking Changes

  • App Configuration: updating the subdomain from config.locally to azconfig.locally in order to align with the Azure SDKs. This requires updating the TLS certificate used by Locally (for example via locally certificate generate --update-config). The older config.locally domain will be removed in the next release.
  • Log Analytics: KQL queries in Log Analytics, Application Insights and Azure Resource Graph are now type-checked before they run, as in Azure - as such a query that compares values of incompatible types (e.g. TimeGenerated > "2024-01-01"), or uses an operator or function in the wrong case (e.g. Count()), now fails with a SemanticError rather than returning an incorrect result.

Features

  • Architecture Diagram: these are now drawn in 3D, with each Resource Group as a platform on the Subscription, and the estimated monthly cost optionally shown as the height (Standard plan and above).
  • Chaos Engineering: support for injecting faults into every Data Plane Emulator within Locally, including over AMQP, MQTT, WebSockets, gRPC, the MongoDB wire protocol and database connections - with each fault returning the service's own errors, so that a client's retry handling can be tested.
  • Chaos Engineering: support for scheduled faults which act on a running service rather than a single request: incident, failover, freeze, exit, restart and cold-start.
  • Chaos Engineering: support for messaging faults in Service Bus, Event Hubs, Event Grid and IoT Hub, where messages and events can be delayed, dropped, repeated or reordered, and a message lock can be lost.
  • Chaos Engineering: support for regional faults in Cosmos DB, App Configuration and Storage, so that the Azure SDKs can be tested failing over to another region (or replica), alongside stale reads.
  • Chaos Engineering: support for connection faults on PostgreSQL, MySQL, SQL Database, Redis and HorizonDB, and for freezing, stopping or restarting Container Instances and Virtual Machines.
  • Chaos Engineering: support for faults on sign-in and tokens via the new Identity surface (locally chaos identity), including throttling, outages, rejected refresh tokens, clock skew and a failing managed identity endpoint.
  • Chaos Engineering: support for finer control over each fault: a duration or range (e.g. --seconds 5-20), how often it starts (--interval), the retry hint a throttled client is given (--retry-after) and limiting it to a single resource (--name).
  • CI: support for CI Keys for running Locally in CI environments where Workload Identity Federation (OIDC) is not available, such as Bamboo, AWS CodeBuild or Jenkins without its OpenID Connect plugin. A CI Key can be created for a Team or yourself in your Locally Account, and set as LOCALLY_CI_KEY (or LOCALLY_CI_KEY_FILE) - OIDC remains the better choice wherever your CI system supports it.
  • Locally Snapshots: support for taking a snapshot of all of your resources and data in Locally, restoring it later, comparing it with another snapshot, and sharing it with your Team, using locally snapshot or Settings > Locally Snapshots in the Dashboard. Requires the Standard plan or above (sharing with your Team requires the Team plan).
  • Management Groups (Beta): support for Management Groups, including nesting them, moving Subscriptions between them, assigning policies and role assignments, and deploying ARM Templates at Management Group scope (via locally deploy --management-group or the Dashboard). Available on every plan: one Management Group on Starter, up to three on Standard, and unlimited on Team and above.
  • Persistence: support for keeping your resources across restarts using locally build --persist (or --persist=<name> to keep a separate state per project). Requires the Standard plan or above.
  • Tenants (Beta): support for multiple Tenants, from the Azure CLI, Terraform or the Subscriptions page in the Dashboard. Deploying ARM Templates at Tenant scope isn't supported yet, but will be in a future release. Available on every plan: the default Tenant on Starter, up to three Tenants on Standard, and unlimited on Team and above.

Enhancements

  • Chaos Engineering: faults are now shown on the Tracing page for every service (including databases and containers), with a new Chaos only filter.
  • Chaos Engineering: enabling a fault from the Chaos page now turns on Chaos for the Subscription (or Tenant) if it was off, and faults can now be edited whilst Chaos is off.
  • CLI: locally redis connection-string now supports Azure Managed Redis.
  • Containers: the Starter plan can now launch containers.
  • Emulators: the Service Bus, Event Hubs, Event Grid, IoT Hub and Storage Queue emulators now show messages as an inbox, newest first and updating as they arrive, with the selected message's body (formatted for JSON and XML) and properties alongside.
  • Event Hubs: support for Capture, archiving events to a blob container as Avro files and raising Microsoft.EventHub.CaptureFileCreated for Event Grid.
  • Log Analytics: KQL errors now return the same codes and messages as Azure (e.g. SEM0064 and SYN0002), and support for over 100 more functions (including the geo_*, series_* and IP address functions) and the parse-kv and top-hitters operators.
  • Log Analytics: series_decompose, series_decompose_forecast and series_seasonal now detect seasonality when no period is given.
  • Microsoft Graph: support for Microsoft Teams' teams, channels and channel messages, including change notifications for channel messages.
  • Monitor: an action group's webhook, Function or Logic App receiver is now retried when a delivery times out, or returns a 408, 429, 503 or 504.
  • Regions: Use Locations From now offers Azure Public (Europe only) and Azure Public (US only), for when you only deploy within one of those areas. Requires the Team plan or above.
  • Service Bus: support for deleting messages in batches, as used by the Azure SDKs' DeleteMessages and PurgeMessages methods.
  • Storage: support for API version 2027-03-07, including Blob sessions and layouts, and looking up Files by file ID, hard links and a change feed per share. Read-access geo-redundant accounts (Standard_RAGRS and Standard_RAGZRS) now also serve their (read-only) secondary endpoint.
  • Web Apps: support for sidecar containers (SITECONTAINERS), with .NET Aspire apps now sending their telemetry through an OpenTelemetry collector sidecar.

Bug Fixes

  • API Management: fixing an issue where the gateway and developer portal URLs used the default instance's port, rather than the port of the Locally instance the service was created in.
  • App Configuration: fixing an issue where values encrypted with a customer-managed key were decrypted by Locally rather than the store's managed identity - as such the Key Vault's access policies and role assignments now apply, and a store whose identity can't use its key now returns a 403.
  • App Configuration and Key Vault: fixing an issue where changing public network access (or local authentication) from the Dashboard wasn't saved on the resource itself, so the next update switched it back.
  • ARM Templates and Bicep: fixing an issue where environment().suffixes.storage returned storage.locally, which doesn't exist. Both suffixes.storage and suffixes.keyvaultDns now return the domain and port that Storage and Key Vault are served on - as these include the port, a Private DNS Zone named from them is now refused as invalid.
  • ARM Templates and Bicep: fixing an issue where a deployment's page in the Dashboard linked a policy definition, policy assignment, role assignment or role definition to a page that didn't exist.
  • CI: fixing an issue where the OIDC token exchange failed when the token file given in LOCALLY_OIDC_TOKEN_FILE ended in a newline.
  • CLI: fixing an issue where locally deploy printed the reason a deployment failed to standard output without a line ending - this is now printed to standard error, on its own line.
  • Container Apps, Container Instances and Web Apps: fixing a security issue where a container image or registry server starting with a dash was passed to the container runtime as an option - these are now refused, as in Azure.
  • Container Apps and Web Apps: fixing an issue where a container launch (including a slow image pull, such as the Aspire Dashboard's) was cancelled when the request that started it gave up, so it never finished.
  • Container Registry: fixing a security issue where an ACR Tasks run passed a build tag, git source or cmd image starting with a dash to the container runtime as an option, and where its cleanup could remove images it hadn't created. A task's source location must now be a repository URL, so the scp-style git@host:repo form is now refused.
  • Container Registry: fixing a security issue where deleting a registry named "." or ".." removed files outside of that registry, and an issue where deleting a registry whose name contains capital letters left its images behind.
  • Container Registry: fixing an issue where a manifest could be pushed with any content type - these are now refused with MANIFEST_INVALID, as in the Docker and OCI registries.
  • Cosmos DB: fixing an issue where, after an account was deleted and its name reused, the new account was deleted when the old account's retention period ended.
  • Cosmos DB: fixing an issue where committing a MongoDB transaction which had expired reported success, whilst its writes were discarded - this now fails with NoSuchTransaction, so that the MongoDB drivers retry the transaction.
  • Cosmos DB: fixing an issue where a multi-region account didn't list its regions to the Azure SDKs, so they could never fail over.
  • Cosmos DB: fixing an issue where a throttled request could ask the client to retry after only a few milliseconds, so the Azure SDKs used up their retries at once.
  • Dashboard: fixing an issue where Minimum Necessary Permissions (and locally permissions) left out the resources created by an ARM Template deployment started from the Deploy ARM Template page.
  • Event Grid: fixing an issue where an event subscription delivering to a webhook with Microsoft Entra authentication never delivered, since issuing its token always failed.
  • Event Grid: fixing a security issue where a namespace's MQTT webhook authentication could be issued a token for any audience, including Microsoft first-party APIs such as Microsoft Graph and Azure Resource Manager.
  • Event Grid: fixing an issue where a namespace whose primary key had never been set could accept an empty access key.
  • Event Grid: fixing an issue where deleting a namespace left its events, deliveries and retained MQTT messages behind, so a namespace recreated with the same name started with them.
  • Event Hubs: fixing an issue where a receiver already waiting on a partition over AMQP wasn't sent events published after it was opened.
  • Event Hubs: fixing an issue where Schema Registry checked Microsoft Entra callers against the permission to receive events, rather than the Schema Registry Reader and Schema Registry Contributor roles.
  • Function Apps: fixing a security issue where a trigger polling the host named in its connection string could send an internal Locally credential to that host.
  • Function Apps: fixing a security issue where your function code, build steps and Kudu commands were started with Locally's own sign-in token in their environment.
  • Function Apps, Web Apps and Container Apps: fixing a security issue where a Key Vault reference ignored the vault's tenant and permission model, so it could resolve through an access policy the vault itself no longer honours.
  • Key Vault: fixing an issue where an access policy for a user acting through a specific application (a compound identity) granted that user access through any application.
  • Key Vault: fixing an issue where a 403 for a user signed in through an application (e.g. the Azure CLI) returned the user's object ID as the caller's appid.
  • Key Vault: fixing an issue where importing an EC key whose private component didn't match its public components, or a certificate with a private key that isn't its own, was accepted - these are now refused with 400 BadParameter, as in Azure.
  • Key Vault: fixing an issue where creating a secret, key or certificate with the name of one that's deleted but recoverable didn't return ObjectIsDeletedButRecoverable (so clients such as Terraform couldn't offer to recover it), and where importing or restoring onto such a name overwrote it.
  • Log Analytics: fixing an issue where a retention period too large to represent as a date deleted all of a workspace's (or Application Insights component's) telemetry, and where a workspace with local authentication disabled still accepted shared-key ingestion.
  • Log Analytics: fixing an issue where a log search alert rule only evaluated the first 1,000 rows its query returned, so a Count rule with a threshold of 1,000 or more never fired.
  • Log Analytics: improving behavioural consistency of KQL queries in Log Analytics, Application Insights and Azure Resource Graph, including a query naming a column that doesn't exist now failing with SEM0100 (rather than returning no rows), NaN and infinite values now being returned rather than an empty response, and null handling, %, between, top, strlen and substring now matching Azure.
  • Managed HSM and Managed Identities: fixing a security issue where a resource's managed identity endpoint (or a Managed HSM backup or restore using a managed identity) could issue a token for an identity other than the resource's own managed identity, such as one of Locally's own or a disabled one.
  • Microsoft Entra ID: fixing a security issue where an application could claim the identifier URI of a Microsoft first-party API (such as Azure Resource Manager), or a service principal could be created for a Microsoft first-party application.
  • Microsoft Entra ID: fixing a security issue where an application or service principal whose appId, identifier URI or service principal name only looked like a Microsoft one (using characters such as ſ for s) could be mistaken for the Microsoft service when issuing a token.
  • Microsoft Entra ID: fixing an issue where signing in with a username and password through MSAL (e.g. the Azure SDKs' username/password credential) failed, since Locally didn't answer MSAL's user realm lookup.
  • Microsoft Entra ID: fixing a security issue where an on-behalf-of exchange still issued a token for a user disabled after signing in, and where refreshing a token or redeeming a device code didn't check whether the application had since been removed, disabled or set to require an assignment.
  • Microsoft Entra ID: improved behavioural consistency with Entra by accepting a client assertion whose nbf and exp are strings, as MSAL sends them - fixing an issue where certificate credentials (e.g. ClientCertificateCredential in the Azure SDK for .NET, or MSAL's WithCertificate) failed with AADSTS50027.
  • Microsoft Entra ID: improved behavioural consistency with Entra by accepting any of an application's current client secrets, rather than only the most recently added one - as such a client secret can now be rotated without downtime, by adding the new secret before removing the old one.
  • Microsoft Entra ID: fixing a security issue where the authorize endpoint issued an ID token or access token directly (the implicit and hybrid flows) to an application whose implicit grant settings don't allow it - these are now refused with AADSTS700054 or AADSTS700051, as in Entra.
  • Microsoft Entra ID: fixing a security issue where SAML single sign-on issued an assertion for a service provider no application had registered, and sent it to any assertion consumer service URL the request named - these are now refused with AADSTS700016 and AADSTS50011 respectively, as in Entra.
  • Microsoft Graph: change-notification subscriptions no longer follow redirects, and are only sent to the notificationUrl's own host.
  • Monitor: fixing an issue where the Activity Log could list events from the same second out of order.
  • Policy: fixing an issue where a policy conditioned on the type of an extension resource (e.g. a management lock) didn't apply, since the extension resource was given the type of the resource it extends.
  • Resource Graph: fixing an issue where every failed query returned the same BadRequest - a rejected query now returns the same error details as Azure (e.g. InvalidQuery and ParserFailure), and booleans are now returned as 1 and 0.
  • Resource Groups: fixing a security issue where deleting a Resource Group (or deleting a resource from the Dashboard) could remove a resource protected by a management lock, when the resource's name contained a %.
  • Resource Providers: fixing a security issue where a Resource Provider plugin's internal endpoints could be reached through its Azure Resource Manager routes, allowing a signed-in client to read resource details across Subscriptions.
  • Resource Providers: fixing a security issue where the Subscription, Resource Group, tenant or caller passed to a Resource Provider plugin could be supplied by the request itself.
  • Resource Providers: fixing a security issue where a resource could be named "." or ".." - these are now refused with 400 InvalidResourceName.
  • Resource Providers: fixing an issue where a request whose path contained a percent-encoded character wasn't found when it spelled subscriptions, resourceGroups or providers in a different case, and where a predefined tag value containing /, %, ?, # or \ was stored percent-encoded.
  • Resources: fixing an issue where editing a resource's tags in the Dashboard ignored a ReadOnly management lock.
  • Service Bus: fixing an issue where a scheduled message reported the time it was sent as its enqueued time, so it could expire early.
  • Storage: fixing an issue where Incremental Copy Blob read each changed page range into memory in one piece, so copying a large page blob could use a large amount of memory.
  • Storage: fixing a security issue where deleting a File Share or directory named "." removed files outside of it. File Share names now follow Azure's naming rules, and are otherwise refused, as in Azure.
  • Storage: fixing an issue where a user delegation SAS that signs request headers or query parameters was always refused.
  • Virtual Machines: fixing an issue where a VM whose guest had stopped running was still reported as running, so az vm start didn't start it again.
  • Virtual Machines: fixing an issue where choosing Shut down VM in a locally connect session left the VM's guest running.
  • Web Apps: fixing a security issue where pulling a custom container image with a managed identity could exchange the identity's token with a host other than a Container Registry within Locally.
  • Web Apps, Function Apps and Container Apps: fixing an issue where a request's Connection header could stop headers set by Locally (including App Service Authentication's and X-Forwarded-*) from reaching the app.

v2026.10.03

This release contains:

Bug Fixes

  • CI: fixing an issue where locally ci didn't start the App Configuration and API Management data planes for a team's CI runs - Locally now logs when a service isn't started because of the plan.
  • CI: fixing an issue where when running in CI Mode, blob events from Storage weren't sent to Event Grid.
  • Containers: fixing an issue where, on Linux, containers launched by Locally couldn't reach Locally itself - for example a Deployment Script couldn't sign in or connect to an Azure SQL Database, as when .NET Aspire grants an app access to its database. Locally now reaches the host through slirp4netns under rootless Podman, and under Docker relays its ports from the container network's gateway, to containers on that network only.

v2026.10.02

This release contains:

Bug Fixes

  • CLI: fixing an issue where az sql db show-connection-string failed under locally run with CloudSuffixNotSetException. The Azure CLI always outputs port 1433, so take the port from fullyQualifiedDomainName for now.
  • Function Apps: fixing an issue where a deployment failed when the app took more than 30 seconds to start. Locally now waits as long as Azure does: 230 seconds by default, or the number of seconds in the WEBSITES_CONTAINER_START_TIME_LIMIT app setting, up to 1800.
  • SQL Database: fixing an issue where a service principal couldn't sign in with Microsoft Entra ID when its database user had been created with its object ID as the SID, as .NET Aspire does under locally run aspire run. Locally now looks for the user by the principal's client ID first, as Azure does, then by its object ID.

v2026.10.01

This release contains:

Enhancements

  • Container Runtime: set LOCALLY_CONTAINER_RUNTIME to podman or docker to force Locally to use that runtime, instead of detecting one.
  • Durable Task Scheduler: SDK workers now run durable entities, including locks, entity queries and cleanup, and the task hub page lists each hub's entities.
  • Durable Task Scheduler: the task hub dashboard no longer asks you to sign in.
  • Function Apps: a Durable tab in each app's emulator UI shows its orchestrations, instance histories and entities, wherever its task hub lives.
  • Function Apps: Durable Functions can keep their task hub using the MSSQL storage provider.
  • Key Vault Data Plane: now supports API versions 2026-04-01 and 2026-07-01-preview.

Bug Fixes

  • ARM Templates and Bicep: fixing an issue where an output that loops over a copied resource returned the last instance's values for every element.
  • ARM Templates and Bicep: fixing an issue where list* functions didn't send their third argument as the request body, such as the input to a custom provider's action.
  • Durable Task Scheduler: fixing an issue where signalling an entity from an SDK client could stop Function Apps and Web Apps from running.
  • Durable Task Scheduler: fixing an issue where an entity could reply to, or grant a lock to, an orchestration that had already finished or restarted.
  • Durable Task Scheduler: fixing an issue where cleaning entity storage could lose a signal sent at the same moment, or undo an entity's latest changes.
  • Function Apps: fixing an issue where two Durable Functions orchestrations locking the same entities could wait on each other forever, or an operation waiting for a lock could be dropped.
  • Function Apps: fixing an issue where a Durable Functions orchestration read a stale current time after calling or locking an entity.
  • Function Apps: fixing an issue where a Durable Functions orchestration whose instance ID contains characters such as %, / or a space could be started but then not read, terminated or purged.
  • Function Apps: fixing an issue where a redeploy applied the previous deployment's Durable Functions settings from host.json.
  • Function Apps: fixing an issue where a stopped app's Durable tab still tried to read and manage its orchestrations, rather than saying the app is stopped.
  • Microsoft Entra: improving behavioural consistency (a sign-in is now refused with AADSTS90033 when the Directory can't be reached to check the application, rather than let through).
  • Storage: improving behavioural consistency of table entity keys (refusing keys that aren't quoted or can't be read, and fixing an issue where a key containing a comma or a quote was misread).

v2026.10

API Management and Durable Task Scheduler

This release contains two new Data Plane Emulators, many new features and bug fixes:

Data Plane Emulators

Features

  • ARM Templates and Bicep: support for the @retryOn decorator.
  • CLI: locally permissions generates a Role Definition with the Minimum Necessary Permissions needed to run your deployments.
  • Conditional Access: support for Microsoft Graph's What-If evaluation, showing which policies would apply to a sign-in and why the others don't.
  • Dashboard: support for deploying an ARM Template from within the Dashboard, including as-you-type validation and a What-If preview. You can also use Deploy to Locally links to open a template from any URL. Find out more.
  • Dashboard: support for creating a new Resource through a wizard, including a What-If preview.
  • Dashboard: support for querying resources via Resource Graph (KQL) queries.
  • New Theme: Tide - a navy and steel-blue theme.
  • Resource Providers: support for registering (and unregistering) Resource Providers on a per-Subscription basis. If the relevant plugin isn't installed, then registering the Resource Provider will download and install the plugin, if your plan includes it.
  • Web Apps: support for App Service sites which use .NET Aspire 13. Sidecar containers aren't supported in this release.

Enhancements

  • Activity Log: the Activity Log now has the same design and filters as the Observability page.
  • CLI: locally configure dns now works on Windows, from an elevated terminal.
  • Dashboard: a deployment's page now shows each resource as it's provisioned, and lets you cancel the deployment while it runs.
  • Directory: support for user Sponsors, including the Sponsors set when a guest is invited, and for disabling nesting on security groups.
  • Function Apps: Durable Functions now support orchestration versioning, extended sessions, restarting an orchestration and the Durable Task Scheduler.
  • Observability: requests, traces and evaluation events are now kept for 30 minutes by default, rather than 15.
  • Policy: better evaluation and enforcement of policies, including when assigning an initiative. Find out more.
  • Regions: the Regions section is now viewable on every plan. You can use the Azure Regions (or define your own Regions) using the Team plan.
  • Storage: support for listing blobs via Apache Arrow.

Bug Fixes

  • ARM Templates and Bicep: improving behavioural consistency and naming the resource that failed the deployment.
  • Cache for Redis: fixing issues with signing in using Microsoft Entra ID or the secondary access key, and where the non-SSL port stayed open after being disabled.
  • CI: fixing issues where locally ci incorrectly treated every run as the Starter plan, and exited with an error after a successful run.
  • CLI: fixing an issue where a deactivated installation was reported as an expired licence. Locally now says so, and to run locally setup.
  • Conditional Access: fixing an issue where policies that target a group or a directory role never applied when a user signed in.
  • Cosmos DB: improving behavioural consistency of users and permissions.
  • Dashboard: fixing an issue where the resources list showed any resource with an operation in progress as Deleting.
  • Database for PostgreSQL: fixing issues with Microsoft Entra ID authentication on flexible servers, including Entra-only servers such as those .NET Aspire creates.
  • Database for PostgreSQL: fixing an issue where turning password authentication on or off on an existing flexible server didn't take effect.
  • Directory: improving behavioural consistency of authentication tokens.
  • Directory: fixing an issue where an app that takes its tokens straight from the sign-in page (the implicit flow), such as App Service authentication without a client secret, couldn't sign in a browser that was already signed in to Locally.
  • DNS: improving behavioural consistency of Azure DNS and Private DNS zones, so a zone name used in two Resource Groups no longer overwrites the other.
  • Function Apps: fixing issues where the Python, Java and PowerShell language workers could fail to start.
  • Function Apps: fixing issues where a queue output binding failed when its queue didn't exist yet, and where a recreated Function App showed the old app's invocations.
  • Function Apps: fixing an issue where an HTTP function that threw an exception in a .NET app using ASP.NET Core integration left the caller waiting instead of returning a 500.
  • Management Locks: improving behavioural consistency when listing locks, which now include the locks on everything beneath the scope.
  • Microsoft Graph: improving behavioural consistency of errors and permissions, and support for updating and deleting applications and service principals via appId.
  • Policy: fixing an issue where assignments in DoNotEnforce mode were left out of compliance results.
  • Resource Groups: fixing issues where deleting a Resource Group could fail on nested or locked resources, or remove a resource that refused to be deleted.
  • Resource Providers: improving behavioural consistency, so requests to a provider the Subscription hasn't registered now fail.
  • Service Bus: fixing issues with transactions, auto-forwarding and dead-lettering, and improving behavioural consistency of message properties and counts. Entity names containing / are now supported.
  • Storage: improving behavioural consistency of versioned blobs, SAS tokens and recreated Containers.
  • Storage: fixing issues with Data Lake renames, listings, deleted paths, expiry and range reads.
  • Storage: fixing issues on macOS where names differing only in case or Unicode normalisation overwrote each other. These are now refused.
  • Themes: fixing an issue where progress bars were hard to see in every theme but Light and Dark.
  • Virtual Machines: fixing issues where the Custom Script extension failed without fileUris, and az vm extension set couldn't find its latest version.

Other

  • Support for ignoring RBAC permissions in the Control Plane API, so any authenticated principal is granted access before role assignments are configured.
    This is off by default but can be turned on in Settings -> Feature Flags within the Dashboard.
  • Support for provisioning resources that violate a deny-effect Azure Policy, recording the violation on the Governance page rather than blocking the request.
    This is off by default but can be turned on in Settings -> Feature Flags within the Dashboard.

v2026.09.03

This release contains:

Bug Fixes

  • Container Apps: ensuring that restarting a revision restarts its replicas, so they pick up rotated Key Vault secrets.
  • Container Apps: ensuring that a container app's replicas are replaced when their container stops.
  • Container Apps: fixing an issue where deleting a container app could occasionally leave its containers running.
  • Container Apps: fixing an issue where a container app's console logs appeared in every app's log stream.
  • Container Apps: improving behavioural consistency when an image can't be pulled (the app no longer reports as Running, and pull messages go to ContainerAppSystemLogs_CL).
  • Directory: support for retrieving, updating and deleting an app registration's federated identity credentials by name (previously only id was supported).
  • Event Grid: improving behavioural consistency of resource and system topic events, and validating a webhook subscription only once.
  • Function Apps: fixing an issue where restarting a Function App replaced resolved Key Vault references with the literal reference.
  • Function Apps: improving behavioural consistency of table input bindings, Service Bus trigger metadata and invocation logging.
  • Function Apps: fixing an issue where deleting a Function App left its language worker running.
  • Key Vault: ensuring that secret and key URIs include the vault's port.
  • Locally: fixing a connection leak that could exhaust ephemeral ports during long-running test suites.
  • locally run: az rest and curl now refuse requests for Azure URLs (such as https://management.azure.com/...), and give the Locally URL to use instead.
  • Managed HSM: ensuring that key URIs use the Managed HSM's Locally endpoint, rather than Azure's.
  • Managed Identity: improving behavioural consistency of federated identity credentials (issuer and subject must be unique, with at most 20 per identity).
  • Monitor: fixing a behavioural consistency issue in the common alert schema.
  • Storage: improving behavioural consistency of ETags in List Blobs, which fixes Event Hubs checkpoint stores after a restart.
  • Storage: support for data-plane role assignments scoped to a blob container, queue, file share or table.
  • Storage: ensuring that copying a blob or file checks that the caller can read the source.
  • Storage: fixing an issue where deleting and then recreating a storage account would leave the old content around.
  • Web Apps: ensuring that Key Vault config references report their status.
  • Web Apps: ensuring that Key Vault references in app settings are resolved for custom containers, after a restart or settings change, and when access is granted on the secret rather than the vault.
  • Web Apps: fixing an issue where restarting or deleting a custom container left its anonymous volumes behind.
  • Web Apps: support for WEBSITES_ENABLE_APP_SERVICE_STORAGE, giving custom containers a persistent /home.
  • Web Apps: support for acrUseManagedIdentityCreds when pulling custom container images. A failed pull no longer falls back to a cached image.
  • Web Apps: image pull output now goes to AppServicePlatformLogs rather than AppServiceConsoleLogs.
  • Web Apps: support for storage mounts in siteConfig.azureStorageAccounts when creating or updating a site.

v2026.09.02

This release contains:

Bug Fixes

  • Event Hubs: improving behavioural consistency (fixing compatibility with the Azure SDK for Python, and returning the right errors when a management request names a missing event hub or partition).
  • Event Hubs: fixing an issue where deleting and then recreating an event hub would leave the old content around.
  • Function Apps: ensuring that Function Apps linked to an Application Insights component have the connection string set.
  • Function Apps: diagnostic settings now send Function App and authentication logs.
  • Logging: replaying a request now sends it to the same host as the original, so data-plane requests such as Storage reach the right account.
  • Managed HSM: fixing an issue where Terraform couldn't create local role assignments.
  • Managed HSM: allowing the rotation of the wrapping keys for an activated HSM's security domain.
  • Service Bus: improving behavioural consistency (fixing compatibility with the Azure SDKs for Python and .NET, and only accepting supported api-version values on the management API).
  • Service Bus: fixing a bug where disabling local authentication wasn't fully propagated, allowing SAS keys to continue authenticating.
  • Service Bus: fixing an issue where deleting and then recreating a queue, topic or subscription would leave the old content around.
  • Virtual Machines: fixing an issue where the Custom Script extension required files to download before it could run a script or command.
  • Web Apps: ensuring that Web Apps linked to an Application Insights component have the connection string set.
  • Web Apps: diagnostic settings now send HTTP, platform and authentication logs, not just console output.

v2026.09.01

This release contains:

Improvements

  • App Configuration: Improving behavioural consistency of key and label filters, snapshots and feature flags.
  • App Service Authentication: Now enforced for Web Apps, Function Apps and Container Apps, including Microsoft Entra sign-in, access tokens sent from code and the legacy authentication settings.
  • Application Insights: Telemetry can now be sent using a Microsoft Entra token.
  • Cache for Redis: Surfacing the correct permissions when authenticating using a Microsoft Entra token.
  • Monitor: Alerts now fire and resolve on their own schedule and cover many more services. Diagnostic settings can send to Storage and Event Hubs, and KQL supports many more operators and functions.
  • Container Apps: Authentication and CORS settings are now enforced.
  • Container Registry: az acr build and az acr run now build and push images. Improving behavioural consistency of scope maps and locked images.
  • Cosmos DB: Support for vector, full-text and hybrid search, transactional batches and bulk operations from the .NET SDK, and point-in-time restore. Items are now deleted when their time-to-live passes.
  • Event Grid: Event subscriptions on a resource, resource group or subscription now receive events, and Key Vault, Container Registry, IoT Hub, App Service and Service Bus now raise theirs. The MQTT broker now supports MQTT v5 and more ways to authenticate.
  • Event Hubs: Retention, compaction and a hub's status are now honoured, and consumers can start from a point in time.
  • Functions: Support for route templates, binding expressions, custom handlers (such as Go or Rust), remote builds, PowerShell, Java and poison queues.
  • IoT Hub: Devices on MQTT now receive cloud-to-device messages. Improving behavioural consistency of message expiry and dead-lettering.
  • Key Vault: Roles can now be assigned on a single secret, key or certificate, and deleted items are purged on their scheduled date. Managed HSM supports backup and restore.
  • Locally CI: Team runbooks can now be applied in CI by setting LOCALLY_CI_APPLY_RUNBOOKS=true.
  • locally run curl: Now sends the right token for the API being called, including Microsoft Graph, Storage and Key Vault.
  • Microsoft Entra: Applications can now sign in with a certificate or federated credential, so GitHub Actions, workload identity and Terraform's OIDC support work. Tokens now match those issued by Microsoft Entra ID more closely.
  • Microsoft Graph: Support for directory extensions, and for token lifetime, token issuance, home realm discovery and activity timeout policies.
  • Role-based Access Control: Custom roles can now be created at resource group scope.
  • Service Bus: Improving behavioural consistency of sessions, rules, entity status and size limits.
  • Storage: Supporting pagination when listing blobs, queues, files and tables.
  • Virtual Machines: The Custom Script extension, Run Commands and cloud-init (customData) now run inside the container Locally launches for each VM, so they need Docker or Podman.
  • Web Apps and Function Apps: Configuration changes, connection strings and CORS now take effect in the running app, stopping an app stops it, and WebJobs are supported.

Bug Fixes

  • App Service Authentication: /.auth/me now returns the signed-in user's tokens when the token store is enabled.
  • App Service Authentication: improving behavioural consistency of redirects after sign-in and sign-out, which are now limited to the app itself and its allowed external redirect URLs.
  • ARM Templates and Bicep: deployment().name now returns the deployment's name, so Bicep modules deployed from different parent deployments no longer overwrite each other, and What-If previews the same names the deployment uses.
  • Assigning a role to a managed identity created in the same template no longer fails on the first run.
  • Azure Policy External Evaluation policies now resolve type-qualified aliases.
  • Closing Locally now removes all of its containers when using Podman.
  • Container Apps: az containerapp ingress no longer removes the app's existing ingress and secrets.
  • Directory Emulator: improving behavioural consistency when validating authorization codes and on-behalf-of requests.
  • Directory Emulator: support for v1.0 access tokens, and respecting the claims requested by the app registration.
  • Ensuring permissions are applied consistently in Container Registry, Cosmos DB, Event Grid, Event Hubs, IoT Hub, Service Bus and Storage.
  • Event Grid: improving behavioural consistency when publishing to a custom topic, domain or partner namespace, which now checks its credentials. MQTT clients now connect using the namespace's hostname.
  • Event Grid: updating a topic, domain or partner namespace now applies every change, not just tags.
  • Fixes a crash when provisioning many resources at once.
  • Key Vault: reading a missing secret or key now returns 404 rather than 500, which fixes azapi_resource. Purging a vault now removes all of its contents.
  • locally ci now releases its CI lease when it exits with an error.
  • locally ci: removed the unused LOCALLY_ANALYTICS_ENABLED and LOCALLY_CRASH_REPORTING_ENABLED environment variables.
  • locally deploy no longer leaves temporary files behind after deploying a Bicep file, and shows resource names and durations more clearly.
  • locally mcp install copilot-vscode now installs into VS Code's user profile, so Locally is available in every workspace.
  • locally setup now links to the same Terms and Conditions page as other places.
  • Microsoft Graph: improving behavioural consistency by checking the application's Graph permissions on each call. The Azure CLI, Azure PowerShell and VS Code are pre-consented.
  • MySQL and PostgreSQL Flexible Servers: changing the administrator password now changes it on the server, and MySQL server parameters are now applied.
  • Resource Groups: every API version Azure lists is now accepted.
  • Role-based Access Control: az role definition delete no longer reports an error after deleting a custom role.
  • Web Apps: a deployment whose build crashes on Apple Silicon now fails straight away and explains how to deploy without a build, rather than hanging.
  • Web Apps: custom containers are now reached on port 80 by default.
  • Web Apps: improving behavioural consistency of ZIP deploys, which now only run a build when SCM_DO_BUILD_DURING_DEPLOYMENT is true.

v2026.09

Initial Release

This is the initial release of Locally, which contains:

New Components

  • Locally Control Plane: provides a Resource Manager compatible API with support for provisioning Resources via Plugins. Find out more.
  • Locally Dashboard: a dashboard for Resource Manager-related functionality. Find out more.
  • MCP Server: gives AI assistants like Claude Code and Cursor a set of tools to explore and manage the resources in your Locally instance. Find out more.

Data Plane Emulators

Key Features

  • Automatic Configuration of common tooling, like the Azure CLI, HashiCorp Terraform, OpenTofu, PowerShell and Pulumi. Applications built using the Azure SDKs can also be connected to Locally, but require a few lines of changes at this time. Find out more.
  • Support for both ARM and Bicep Templates: these can be natively deployed to Locally.
  • Real Subscriptions and Credentials: Locally gives you multiple, real Subscriptions, with real credentials (Service Principals, Entra Users/Groups and Managed Identities) and real role-based access control (RBAC). The Default Identity has full permissions for ease of development (e.g. Global Administrator), but you can assign any Role to any Enterprise Application/Entra User/Group at any scope.

Features

  • Architecture Diagrams: View and export a live architecture diagram of your deployed infrastructure. Find out more.
  • Chaos Engineering: Support for testing how your application behaves when things go wrong. Find out more.
  • Containers: Support for launching containers in both Docker and Podman.
  • Cost Estimation: Shows a ballpark estimate of how much your application would cost to run in Azure. Find out more.
  • Directory Emulator: Work with Users, Groups, Applications, Service Principals and more. Test your applications using single-sign-on, SAML support and conditional access. Find out more.
  • Locally Directory: Shows you who in your team is most familiar with, and has most recently worked with, each Azure Service. Find out more.
  • Locally Runbooks: Define common infrastructure (Resource Groups, Resources, DB scripts and Entra users) for your team and have them available within Locally, optionally provisioning automatically at launch. Find out more.
  • Locally Teams: Build infrastructure together using common Runbooks, the Locally Directory and CI configuration at a Team level. Find out more.
  • Minimum Necessary Permissions: Run your application/deployments against Locally and see a Role Definition with the minimum permissions needed to run the deployment. Find out more.
  • Observability: Dig deep into your application by inspecting the HTTP(S) requests and responses being made, and by running KQL queries against the Application Insights and Log Analytics emulators.
  • Regions: Locally uses its own set of Regions to differentiate it from Azure (so you can be sure when you're targeting Locally or Azure). Support for using the Azure Regions is available as a preview feature. Find out more.
  • Themes: Locally ships with 9 themes: Dark, Forest, HardHacker, Light, Neon, Parchment, Retro, Sunset, Solarized.

Other

  • Support for launching containers via Docker and Podman. Both of these are auto-detected at launch.
  • Support for connecting to both Virtual Machines and Bastion instances over both Remote Desktop (for Windows VMs) and SSH.
    This allows you to validate whether the Virtual Machine in question has access to the route you're expecting it to.
  • Support for exploring the Control Plane API in a browser without authentication, which makes this more explorable during local development.
    This is enabled by default, but can be turned off in Settings -> Feature Flags within the Dashboard.
  • Support for disabling the Beta API in the Directory Emulator. Find out more.
    Beta API Versions are enabled by default, but can be turned off in Settings -> Feature Flags within the Dashboard.
  • Support for disabling Deprecated API Versions in the Control Plane API. Find out more.
    Deprecated API Versions are enabled by default, but can be turned off in Settings -> Feature Flags within the Dashboard.
  • Support for disabling Preview API Versions in the Control Plane API. Find out more.
    Preview API Versions are enabled by default, but can be turned off in Settings -> Feature Flags within the Dashboard.
  • Support for Purge Protection on resources that support it within the Resource Manager API.
    This is off by default but can be turned on in Settings -> Feature Flags within the Dashboard.

Preview Features

Preview Features are features that we're still working on, and may contain bugs or other issues.

  • Compliance: Validate your infrastructure's compliance with regulatory policies, including seeing a breakdown of which resources do/do not comply, and how to bring them into compliance. Find out more.
  • Custom Regions: support for using the regions from an Azure Environment (Azure Public, Azure China or Azure US Government). This feature flag can be turned on in Settings -> Feature Flags. Find out more.
  • Locally Policies: Define your team's policies centrally and allow your team to validate that their deployments comply with them, without blocking their day-to-day work. Find out more.
  • Policies: Deploy Azure Policies to your Subscriptions. Find out more.
  • Translation: Locally is available in 16 languages (with 14 translations in Beta, translated via AI), including Chinese (Simplified), Dutch, English (UK/US), French, German, Hindi, Italian, Japanese, Korean, Norwegian (Bokmål), Polish, Portuguese (Brazil), Russian, Spanish and Ukrainian.

Have your first local subscription running in under a minute.

Runs entirely on your machine, with the tools you already use.

Install Locally →

Or read more: