App Configuration Emulator

Preview

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

App Configuration Emulator

Available on Starter Standard Team Compare plans →

Azure App Configuration is a managed service for storing your application's settings and feature flags in one place - so you can change them without redeploying, and keep them consistent across environments.

Locally supports both provisioning App Configuration stores and configuring the values within them (such as key-values and feature flags, and taking snapshots of them) - so you can fully test your application against it.

When you provision an App Configuration store in Locally, a data plane instance is created at https://<name>.azconfig.locally:5664, which you can connect to using the App Configuration SDKs, the Azure CLI and the configuration providers for .NET (and other languages).

For a step-by-step walkthrough, see Provisioning an App Configuration Store.

Plugin required

Locally v2026.10+ automatically installs this Resource Provider plugin when its Resource Provider is registered, but you can also install it via:

$ locally plugin install --name Microsoft.AppConfiguration

Finding the Emulator

Once an App Configuration store has been created, you can find its Data Plane Endpoint on its resource page within the Locally Dashboard:

Screenshot of an App Configuration resource in the Locally Dashboard, with the Endpoints for this Service dropdown open on the Data Plane Endpoint

Opening the Data Plane Endpoint in your browser takes you to the emulator's own UI.

The App Configuration Emulator

Within the App Configuration Emulator you can view and manage key-values and feature flags, and find the connection strings to interact with the store:

Screenshot of the App Configuration Emulator, showing a store's feature flags and key-values

Key-values and feature flags created in the App Configuration Emulator, the Azure CLI or the Azure SDKs will appear both in the App Configuration Emulator and on the store's resource page in the Locally Dashboard:

Screenshot of an App Configuration store's key-values, feature flags and labels in the Locally Dashboard

What's Supported

The App Configuration emulator supports:

Customer Managed Keys Feature Flags Key Values Labels Locks Replicas Revisions Snapshots

As of Locally v2026.11.03, the following API versions are supported for the App Configuration data plane:

2026-05-01-preview 2026-04-01 2024-09-01 2023-11-01 2023-10-01 1.0

Authentication is supported using either a Microsoft Entra token (with the App Configuration Data Reader or App Configuration Data Owner role) or an access key (if local authentication is enabled).

Replicas get their own endpoint, https://<name>-<replica>.azconfig.locally:5664 - and every endpoint accepts reads and writes, with a change made through one visible through the others straight away. The configuration providers find a store's replicas on their own, through the same DNS records Azure publishes, and fail over to them.

Note

Before v2026.11, stores were served on <name>.config.locally. That domain still works, so any existing connection strings keep working, but it will be removed in v2026.12 - and replica discovery only works on azconfig.locally.

App Configuration also works with Locally's other emulators, as you'd expect - for example:

  • A key-value can hold a Key Vault reference to a secret in the Key Vault Emulator, which the configuration providers resolve for you.
  • App settings in the Web App Emulator and Function App Emulator can use @Microsoft.AppConfiguration(...) references, resolved using the app's managed identity - including a key-value that's itself a Key Vault reference.
  • Changes to key-values and snapshots are sent to the Event Grid Emulator, so a subscription on the store receives KeyValueModified, KeyValueDeleted, SnapshotCreated and SnapshotModified events.

Examples

The locallybuild/examples repository has examples that provision an App Configuration store in Locally using:

This end-to-end example reads and writes its settings in App Configuration, and has everything you need to run it against Locally:

Differences from Azure

As of Locally v2026.11.03, the App Configuration emulator has the following differences from Azure:

  • Replicas are always in sync. There's no delay between regions, so a Sync-Token never has anything to wait for - unless you use Chaos Engineering (on the Team plan) to serve stale reads from a replica, or fail a store over to one.
  • Private Link isn't supported on the data plane.
  • Older preview API versions, such as 2022-11-01-preview and 2023-05-01-preview, aren't accepted.

Should you encounter any issues, please take a look at the troubleshooting section, reach out in our Discord or open an issue and we'll take a look.

Preview

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

A local cloud for you and your AI agents.

Your Azure infrastructure, running on your machine. Deploy in seconds, break things freely, and ship to Azure when you're ready.