NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet · #339 most downloaded on NuGet
Microsoft.Extensions.Configuration.AzureAppConfiguration is a configuration provider for the .NET Core framework that allows developers to use Microsoft Azure App Configuration service as a configuration source in their applications.
Last release 2 months ago
29 Jul 2026
Release timing varies
gaps range from 2 weeks to 5 months
Nearly every release is documented
notes for 30 of 30 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
49 releases · first in 2019
Add null check in examples by linglingye001 in #732
Full Changelog: 8.5.0...8.6.0
One column per quarter.
Bug fix: The registered failture status should be used when health check fails by Zhiyuan Liang (@zhiyuanliang-ms) in #714
Full Changelog: 8.5.0-preview...8.6.0-preview
ConnectAzureFrontDoor by using HEAD requests to check for changes. #717Add AlwaysHealthy health check when provider is disabled by Zhiyuan Liang (@zhiyuanliang-ms) in #700
Full Changelog: 8.4.0...8.5.0
Azure.Data.AppConfiguration to 1.8.0to take advantage of enhanced errors when Entra ID audience is misconfigured. #721failureStatus when the provider failed to load or refresh. #714Microsoft.Extensions.Configuration.AzureAppConfiguration 8.5.0-preview - November 14th, 2025
ConnectAzureFrontDoor to AzureAppConfigurationOptions, which can be used to load configuration settings from Azure App Configuration via an Azure Front Door endpoint. This enables client (browser) applications to take advantage of CDN benefits, such as scale, when fetching configuration. #706Microsoft.Extensions.Configuration.AzureAppConfiguration reference to 8.5.0-preview. See the release notes for more information on the changes.Microsoft.Extensions.Configuration.AzureAppConfiguration reference to 8.5.0-preview. See the release notes for more information on the changes.ConnectAzureFrontDoor to AzureAppConfigurationOptions, which can be used to load configuration settings from Azure App Configuration via an Azure Front Door endpoint. This enables client-side applications (like mobile/desktop apps) to securely load configuration from App Configuration service, while leveraging all the benefits of CDN. #706Microsoft.Extensions.Configuration.AzureAppConfiguration 8.4.0 - September 19th, 2025
Added an overload of AddAzureAppConfiguration that accepts the endpoint and token credential. #694
Added support for parsing json values with comments. #685
Added support for snapshot references. If a configuration setting's value is a snapshot reference, loading it automatically pulls all key-values and feature flags from the referenced snapshot into the configuration. This enables dynamically switching between snapshots at runtime. #689
Updated dependency package versions. #695
Azure.Data.AppConfiguration: 1.6.0 -> 1.6.1Azure.Messaging.EventGrid: 4.7.0 -> 5.0.0Azure.Security.KeyVault.Secrets: 4.6.0 -> 4.8.0Microsoft.Extensions.Diagnostics.HealthChecks: 6.0.36 -> 8.0.19Microsoft.Extensions.Azure: 1.7.6 -> 1.12.0Microsoft.Extensions.DependencyInjection.Abstractions: 6.0.0 -> 8.0.2Microsoft.Extensions.Logging: 6.0.0 -> 8.0.1Microsoft.Extensions.Configuration: 6.0.1 -> 8.0.0Microsoft.Extensions.Configuration.AzureAppConfiguration reference to 8.4.0. See the release notes for more information on the changes.Microsoft.Extensions.Configuration.AzureAppConfiguration reference to 8.4.0. See the release notes for more information on the changes.Added support for accepting JSON values with comments. #685
Added support for snapshot references. If a configuration setting's value is a snapshot reference, loading it automatically loads all key-values from the referenced snapshot. This enables dynamically switching between snapshots at runtime. #689
Added an overload of AddAzureAppConfiguration that accepts the endpoint and token credential. #694
Microsoft.Extensions.Configuration.AzureAppConfiguration 8.3.0 - July 24th, 2025
Added health check integration for Microsoft.Extensions.Diagnostic.HealthChecks. You can call AddAzureAppConfiguration on IHealthCheckBuilder to register a health check for the Azure App Configuration provider. #644
builder.Services
.AddHealthChecks()
.AddAzureAppConfiguration();Introduced a new environment variable AZURE_APP_CONFIGURATION_FM_SCHEMA_COMPATIBILITY_DISABLED to force processing and outputting feature flags using the Microsoft schema. #676
Microsoft.Extensions.Configuration.AzureAppConfiguration reference to 8.3.0. See the release notes for more information on the changes.Microsoft.Extensions.Configuration.AzureAppConfiguration reference to 8.3.0. See the release notes for more information on the changes.Microsoft.Extensions.Configuration.AzureAppConfiguration 8.2.0 - May 14th, 2025
Updated the existing Select APIs with the new parameter tagFilters to support filtering key-values and feature flags by tags.
public AzureAppConfigurationOptions Select(string keyFilter, string labelFilter = LabelFilter.Null, IEnumerable<string> tagFilters = null)public FeatureFlagOptions Select(string featureFlagFilter, string labelFilter = LabelFilter.Null, IEnumerable<string> tagFilters = null)Added an ActivitySource called Microsoft.Extensions.Configuration.AzureAppConfiguration to support instrumentation. A Load activity will start when configuration is initially built and the Refresh activity will start when a refresh is triggered. #645
This is the first stable release of the AzureAppConfigurationOptions.SetClientFactory API introduced in 8.2.0-preview. #380
public AzureAppConfigurationOptions SetClientFactory(IAzureClientFactory<ConfigurationClient> factory)FeatureFlagId property from feature flag telemetry. #655AllocationId from feature flag telemetry metadata, which was introduced in 8.1.0-preview. #600Microsoft.Extensions.Configuration.AzureAppConfiguration reference to 8.2.0. See the release notes for more information on the changes.Microsoft.Extensions.Configuration.AzureAppConfiguration reference to 8.2.0. See the release notes for more information on the changes.Microsoft.Extensions.Configuration.AzureAppConfiguration 8.2.0-preview - March 21st, 2025
Added the ability to set a client factory used for creating ConfigurationClient instances. #380
public AzureAppConfigurationOptions SetClientFactory(IAzureClientFactory<ConfigurationClient> factory)Microsoft.Extensions.Configuration.AzureAppConfiguration reference to 8.2.0-preview. See the release notes for more information on the changes.Microsoft.Extensions.Configuration.AzureAppConfiguration reference to 8.2.0-preview. See the release notes for more information on the changes.Microsoft.Extensions.Configuration.AzureAppConfiguration 8.1.2 - April 22nd, 2025
IServiceCollection.AddAzureAppConfiguration now correctly adds an instance of IConfigurationRefresherProvider to the service collection only the first time it is called instead of adding an instance on each invocation. #611Microsoft.Extensions.Configuration.AzureAppConfiguration reference to 8.1.2. See the release notes for more information on the changes.Microsoft.Extensions.Configuration.AzureAppConfiguration reference to 8.1.2. See the release notes for more information on the changes.Microsoft.Extensions.Configuration.AzureAppConfiguration 8.1.1 - February 26th, 2025
FeatureFlagOptions.Select were ignored if they were followed by a call to either AzureAppConfigurationOptions.Select or AzureAppConfigurationOptions.SelectSnapshot. #628Microsoft.Extensions.Configuration.AzureAppConfiguration reference to 8.1.1. See the release notes for more information on the changes.Microsoft.Extensions.Configuration.AzureAppConfiguration reference to 8.1.1. See the release notes for more information on the changes.Added the ability to monitor all selected key-values for refresh with the following new API. #536
Added the ability to monitor all selected key-values for refresh with the following new API. #536
public AzureAppConfigurationRefreshOptions RegisterAll()
When this API is called, changes to any selected key-values will cause a reload of the configuration.
Added the ability to check if the type of an IConfigurationSource is AzureAppConfigurationSource with the following new extension. #456
public static bool IsAzureAppConfigurationSource(this IConfigurationSource source)
Added support for injecting additional telemetry metadata to feature flags if telemetry is enabled
AllocationId represents the version of an allocation on a feature flag. The AllocationId changes when there are essential modifications to the allocation, such as adjustments to the percentile or variant configuration, but not for non-essential changes like feature flag descriptions.The APIs AzureAppConfigurationRefreshOptions.SetCacheExpiration and FeatureFlagOptions.CacheExpirationInterval have been deprecated and will be remove…
AzureAppConfigurationRefreshOptions.SetCacheExpiration and FeatureFlagOptions.CacheExpirationInterval have been deprecated and will be removed in a future release. They are replaced with AzureAppConfigurationRefreshOptions.SetRefreshInterval and FeatureFlagOptions.SetRefreshInterval, respectively. This change does not affect functionality but aims to eliminate confusion regarding cache expiration implied by the previous API names. #350Variant Feature Flags and Telemetry: This is the first stable release with support for the variants, allocation, and telemetry properties for feature flags added by version 4.0.0 of the Microsoft.FeatureManagement.* libraries. While variant feature flags can still be toggled on or off, they also allow for different configurations, ranging from simple primitives to complex JSON objects. Variant feature flags are particularly useful for feature rollouts, configuration rollouts, and feature experimentation (also known as A/B testing).
This is the first stable release of the load balancing mode introduced in 8.0.0-preview.3. Load balancing enables your application to distribute requests to App Configuration across all available replicas. This enhancement improves the scalability of applications that typically experience high request volumes to App Configuration, ensuring they remain within quota limits. Load balancing mode is off by default and can be activated by setting the new AzureAppConfigurationOptions.LoadBalancingEnabled property to true. #535
Added the ability to configure options used to connect to Key Vault resources that have no registered SecretClient with the following new API. #274
public AzureAppConfigurationKeyVaultOptions ConfigureClientOptions(Action<SecretClientOptions> configure)
This API can be called from within the AzureAppConfigurationOptions.ConfigureKeyVault method.
Added new fields to feature flag telemetry metadata, including FeatureFlagId, FeatureFlagReference, and ETag. #517
Upgraded the package reference for Azure.Security.KeyVault.Secrets to 4.6.0. #572
Added support for .NET 8 as a target framework. #530
This is the first stable release of the Replica Auto-Discovery enhancement that was introduced in 7.1.0-preview.
KeyVaultReferenceException instead of retrying for transient errors while connecting to Key Vault during startup, even if the startup timeout had not elapsed. #516Replica Auto-Discovery: For App Configuration stores with geo-replication enabled, the provider will now automatically discover any additional replica
Replica Auto-Discovery: For App Configuration stores with geo-replication enabled, the provider will now automatically discover any additional replicas and attempt to connect to them when it fails to connect to user-provided endpoints in code. This capability allows applications to leverage geo-replication for enhanced resiliency without code change and redeployment. Replica discovery is enabled by default and can be disabled by setting the new AzureAppConfigurationOptions.ReplicaDiscoveryEnabled property equal to false. #442.
Added support for the variants, allocation, and telemetry properties for feature flags introduced in version 4.0.0-preview of the Microsoft.FeatureManagement library. #476
key parameter to AzureAppConfigurationRefreshOptions.Register would throw a NullReferenceException. #503AzureAppConfigurationOptions.Select, FeatureFlagOptions.Select, and AzureAppConfigurationOptions.SelectSnapshot where additional calls with the same filters after the first call were ignored. The provider will now correctly use only the last call with duplicate filters to preserve the expected precedence. #490AddAzureAppConfiguration now throws ArgumentException for invalid inputs even if the optional parameter is equal to true. #318
AddAzureAppConfiguration now throws ArgumentException for invalid inputs even if the optional parameter is equal to true. #318This is the first stable release of the following API introduced in the 7.0.0-preview release. #387
public AzureAppConfigurationOptions SelectSnapshot(string name)
Added support for the requirement_type property for feature flags introduced in version 2.6.0-preview of the Microsoft.FeatureManagement library. #406
The initial configuration load now uses time-based retries instead of count-based retries in case of failures. The time-based retry often works more effectively in real-world scenarios, making applications more resilient to transient errors during startup. By default, the retry timeout is set to 100 seconds in AzureAppConfigurationOptions.StartupOptions.Timeout, but you can customize it using the following new API. #458
public AzureAppConfigurationOptions ConfigureStartupOptions(Action<StartupOptions> configure)
Added netstandard2.1 as a target framework. #482
Added improvements for request tracing.
Fixed a bug where TryRefreshAsync could throw an AggregateException after a network timeout while trying to get key-values from Azure App Configuratio
TryRefreshAsync could throw an AggregateException after a network timeout while trying to get key-values from Azure App Configuration. #440AZURE_APP_CONFIGURATION_PROVIDER_DISABLED that when equal to "true" will disable Azure App Configuration in your application. #429Fixed a bug where ASP.NET (.NET Framework) applications would fail to refresh the configuration. #410
Removed IConfigurationRefresher.SetDirty API in favor of IConfigurationRefresher.ProcessPushNotification API for push-model based configuration refres
IConfigurationRefresher.SetDirty API in favor of IConfigurationRefresher.ProcessPushNotification API for push-model based configuration refresh. Unlike the SetDirty method, the ProcessPushNotification method guarantees that all configuration changes up to the triggering event are loaded in the following configuration refresh. For more details on the ProcessPushNotification API, refer to this tutorial. #357IConfigurationRefresher.LoggerFactory API, but refresh logs are still available through standard ASP.NET Core logging if services.AddAzureAppConfiguration() is invoked in your ConfigureServices method. #367IConfigurationRefresher.ProcessPushNotification now validates that the push notification was triggered for one of the registered App Configuration stores. If no matching App Configuration store is registered, the push notification is ignored and the refresh operation will not be triggered. #319This is the first stable release of the following API introduced in 5.3.0-preview release. #178
public AzureAppConfigurationOptions Connect(IEnumerable<Uri> endpoints, TokenCredential credential)
Added the following new API for additional App Configuration geo-replication support. #385
public AzureAppConfigurationOptions Connect(IEnumerable<string> connectionStrings)
The new API allows you to provide an ordered list of connection strings of your App Configuration store and its replicas.
Added the following new API for performing custom transformations on App Configuration settings. #157
public AzureAppConfigurationOptions Map(Func<ConfigurationSetting, ValueTask<ConfigurationSetting>> mapper)
For .NET 7 or later, added support for refreshing configuration when AzureAppConfigurationProvider is nested under ChainedConfigurationProvider. #168
Added support for Azure SDK logging in addition to standard ASP.NET Core logging. Refresh logs are available under the "Microsoft-Extensions-Configuration-AzureAppConfiguration-Refresh" category. To enable Azure SDK logs, refer to these instructions. #367
Added the following new API for the App Configuration geo-replication support. #178
Added the following new API for the App Configuration geo-replication support. #178
public AzureAppConfigurationOptions Connect(IEnumerable<Uri> endpoints, TokenCredential credential)
The new API allows you to provide an ordered list of replica endpoints of your App Configuration store. The App Configuration provider will fail over to other replicas when a replica is not accessible (either the service is unavailable or there are networking issues). A sample application can be found here.
Added support for .NET 7 as a target framework. #366
AzureAppConfigurationOptions.Select would select key-values with all labels. #311AzureAppConfigurationOptions.Select would be incorrectly ignored if the key-values were already selected by a previous call. #349AddAzureAppConfiguration could throw an exception on invalid feature flags even with the optional parameter set to true. #348Azure.Security.KeyVault.Secrets to 4.3.0 and System.Text.Json to 4.7.2. #351Added support for Feature Management V2 schema introduced in Microsoft.FeatureManagement 3.0.0-preview library. #315
Added support for .NET 6 as a target framework. #290
Added support for Feature Management V2 schema introduced in Microsoft.FeatureManagement 3.0.0-preview library. #315
Added deprecation warning to the IConfigurationRefresher.SetDirty API. IConfigurationRefresher.ProcessPushNotification API should be used instead for…
IConfigurationRefresher.SetDirty API. IConfigurationRefresher.ProcessPushNotification API should be used instead for push-model based configuration refresh. Refer to this tutorial for more details about the ProcessPushNotification API. #301Removed all offline caching capabilities. #135
Removed all offline caching capabilities. #135
Added support for parsing and using sync-token from push notifications received from Event Grid. Using sync-token ensures that users get the latest key-values from App Configuration on any subsequent request. The following new APIs were added:
EventGridEventExtensions.TryCreatePushNotification(this EventGridEvent eventGridEvent, out PushNotification pushNotification)
IConfigurationRefresher.ProcessPushNotification(PushNotification pushNotification, TimeSpan? maxDelay = null)
To use sync-token in a push refresh enabled application, the existing SetDirty() call can be replaced by the following code. Depending on the event handler you're using, you may need to convert the received event to an EventGridEvent object. For example, if you are using Service Bus as the event handler, the code will look like this:
serviceBusClient.RegisterMessageHandler(
handler: (message, cancellationToken) =>
{
EventGridEvent eventGridEvent = EventGridEvent.Parse(BinaryData.FromBytes(message.Body));
if (eventGridEvent.TryCreatePushNotification(out PushNotification pushNotification))
{
_refresher.ProcessPushNotification(pushNotification, maxDelay);
}
return Task.CompletedTask;
},
exceptionReceivedHandler: (exceptionargs) =>
{
Console.WriteLine($"{exceptionargs.Exception}");
return Task.CompletedTask;
});
The next call to RefreshAsync() or TryRefreshAsync() will get the latest key-values from your App Config store. #278
Added support for CancellationToken during refresh operations. The following APIs were updated in IConfigurationRefresher interface: #281
Task RefreshAsync(CancellationToken cancellationToken = default);
Task<bool> TryRefreshAsync(CancellationToken cancellationToken = default);
Added support for logging errors during refresh operations. #273
Ensured that Key Vault secret refresh interval cannot be less than 1 second. #284
Upgraded Microsoft.Extensions packages from version 2.1.1 to 3.1.18. #272
Fixed a bug where the cache expiration time was not being updated after failed refresh operations. #283
Added deprecation warning to all Offline Cache APIs. The current implementation of offline cache will be removed in the next major release.
Added two new APIs which allow users to opt-in for periodically reloading secrets and certificates from Key Vault. #249
Added two new APIs which allow users to opt-in for periodically reloading secrets and certificates from Key Vault. #249
AzureAppConfigurationKeyVaultOptions SetSecretRefreshInterval(string secretReferenceKey, TimeSpan refreshInterval)
This method allows users to set a refresh interval per key of Key Vault references. The API can be called multiple times to register multiple keys of Key Vault references for refresh.
AzureAppConfigurationKeyVaultOptions SetSecretRefreshInterval(TimeSpan refreshInterval)
This method allows users to set a refresh interval for all Key Vault references which do not have individual refresh intervals.
This is the first stable release of the FeatureFlagOptions.Select API introduced in 4.3.0-preview release.
FeatureFlagOptions.TrimFeatureFlagPrefix API, which was introduced in 4.3.0-preview release, has been removed from this stable release.
Added two new APIs for filtering and trimming feature flag by a prefix. #234
Added two new APIs for filtering and trimming feature flag by a prefix. #234
FeatureFlagOptions Select(string featureFlagFilter, string labelFilter)
FeatureFlagOptions TrimFeatureFlagPrefix(string prefix)
Updated package license information.
Added support for .NET 5 as a target framework.
Added SetSecretResolver API to allow users to configure the behavior when a Key Vault reference cannot be resolved. #209
SetSecretResolver API to allow users to configure the behavior when a Key Vault reference cannot be resolved. #209Breaking Change : Updated ConfigureRefresh to throw when it is passed a callback that does not register any key-value for refresh using the Register m…
ConfigureRefresh to throw when it is passed a callback that does not register any key-value for refresh using the Register method. #162KeyVaultReferenceException to be thrown when the optional parameter is set to true in the method AddAzureAppConfiguration and a key vault reference could not be resolved. #136Breaking Change : Added enhanced support for applications that leverage Event Grid integration in App Configuration for configuration refresh. The fol…
Breaking Change : Added enhanced support for applications that leverage Event Grid integration in App Configuration for configuration refresh. The following new API is introduced in IConfigurationRefresher interface, which can be called when an application responds to push notifications from Event Grid. This signals the application to reassess whether configuration should be updated on the next call to RefreshAsync() or TryRefreshAsync(). #133
void SetDirty(TimeSpan? maxDelay = null)
Breaking Change : Added JSON content-type (e.g. MIME type application/json) support for key-values in App Configuration. This allows primitive types, arrays, and JSON objects to be loaded properly to IConfiguration. Existing applications that use key-values with a valid JSON content-type may need to be updated. #191
Breaking Change : Added the following property to IConfigurationRefresher to allow users to disambiguate instances of the interface when using multiple Azure App Configuration providers.
Uri AppConfigurationEndpoint { get; }
Added support for applications to obtain IConfigurationRefresher instances through dependency injection (DI). This allows better control of when to call RefreshAsync()/TryRefreshAsync() or whether to await the call. The following two APIs can be used to take advantage of this feature. #167
IServiceCollection.AddAzureAppConfiguration() first to add required services to the DI container.public static IServiceCollection AddAzureAppConfiguration(this IServiceCollection services)
IConfigurationRefresher instances via IConfigurationRefresherProvider interface obtained through DI.public interface IConfigurationRefresherProvider
{
IEnumerable<IConfigurationRefresher> Refreshers { get; }
}
Fixed an issue that may cause configuration refresh to be ignored when the key registered to refresh all configuration has changed. #178
Improved refresh for feature flags to reduce the number of calls made to App Configuration if no change is detected. #138
TryRefreshAsync to throw an Azure.Identity.AuthenticationFailedException when the TokenCredential used to fetch a key vault reference failed to authenticate. #149optional parameter is set to true in the method AddAzureAppConfiguration
RefreshAsync might ignore exceptions if configuration fails to load after a change is detected in a key with refreshAll: true.TryRefreshAsync would throw a NullReferenceException if the initial attempt to load the configuration in IConfiguration.Build failed.TryRefreshAsync or RefreshAsync to auto-recover from failures during initial configuration load when the optional parameter is set to true in the method AddAzureAppConfiguration. #145Added the following method to allow users to override ConfigurationClientOptions. This enables customization on the underlying App Configuration clien
Added the following method to allow users to override ConfigurationClientOptions. This enables customization on the underlying App Configuration client that includes modifying retry options and configuring proxy settings. #106
public AzureAppConfigurationOptions ConfigureClientOptions(Action<ConfigurationClientOptions> options)
Added IConfigurationRefresher.TryRefreshAsync method, which will not throw exceptions on transient errors during configuration refresh. #113
Renamed the IConfigurationRefresher.Refresh method to IConfigurationRefresher.RefreshAsync.
Reduced maximum number of retries when querying App Configuration to prevent blocking the application for long periods of time during startup or configuration refresh. #255
Updated Azure.Data.AppConfiguration reference to 1.0.0. See the release notes for more information on the changes.
Updated Azure.Data.AppConfiguration reference to 1.0.0. See the release notes for more information on the changes.
Replaced Newtonsoft.Json with System.Text.Json to improve performance and increase compatibility with ASP.NET Core 3.0 and SDKs from other Azure services. See this blog post for more information.
Updated Microsoft.Azure.KeyVault with its successor Azure.Security.KeyVault.Secrets to resolve key vault references.
Replaced the UseAzureKeyVault method used to configure Key Vault references with ConfigureKeyVault method.
TokenCredential can be provided to be used for authentication with referenced Key Vaults.SecretClient can be registered to override the provided TokenCredential, if any, for individual Key Vaults.TokenCredential or SecretClient must be configured using ConfigureKeyVault to successfully resolve a reference.IConfigurationBuilder configBuilder = new ConfigurationBuilder();
IConfiguration configuration = configBuilder.AddAzureAppConfiguration(options => {
options.Connect(endpoint, new DefaultAzureCredential());
}).Build();
IConfigurationBuilder configBuilder = new ConfigurationBuilder();
IConfiguration configuration = configBuilder.AddAzureAppConfiguration(options => {
options.Connect(endpoint, new DefaultAzureCredential());
options.ConfigureKeyVault(kv => {
kv.SetCredential(new DefaultAzureCredential())
});
}).Build();
IKeyVaultClient keyVaultClient = CreateKeyVaultClient();
IConfigurationBuilder configBuilder = new ConfigurationBuilder();
IConfiguration configuration = configBuilder.AddAzureAppConfiguration(options => {
options.Connect(endpoint, new ManagedIdentityCredential());
options.UseAzureKeyVault(keyVaultClient);
}).Build();
SecretClient secretClient = CreateSecretClient();
IConfigurationBuilder configBuilder = new ConfigurationBuilder();
IConfiguration configuration = configBuilder.AddAzureAppConfiguration(options => {
options.Connect(endpoint, new ManagedIdentityCredential());
options.ConfigureKeyVault(kv => {
kv.Register(secretClient);
});
}).Build();
Fixed a bug which caused some application frameworks which use a custom synchronization context, like ASP.NET, to hang when building the configuration provider.
Added support for Azure Key Vault references.
ConfigureRefresh for dynamic configuration.
refreshAll is true for a key that does not exist.Use might not always get loaded in the initial configuration load.Use might be loaded more than once if the client invoked Use more than once.ConnectWithManagedIdentity when the required access to an App Configuration store is not set up properly.Fixed a bug which caused some application frameworks which use a custom synchronization context, like ASP.NET, to hang when building the configuration
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →