Build with an Azure free account. Get USD200 credit for 30 days and 12 months of free services.

Start free today

Getting started with Azure App Configuration

Play Getting started with Azure App Configuration
Sign in to queue


Azure App Configuration is a service that enables you to centralize your application configuration. Built on the simple concept of key-value pairs, this service provides manageability, availability, and ease-of-use. You can use Azure App Configuration to store and retrieve settings for applications, microservices, platforms, and CI/CD pipelines.

Jump to:






The Discussion

  • User profile image

    Thank you for the info

  • User profile image
    Can this tie with KeyVault? I have configuration that'll be useful to put here but I also have secrets stored in KeyVault. It would be nice if there was one abstraction that enable me to use both. Thanks!
  • User profile image
    Hello @nibras85, there is no common interface that is shared between Key Vault and App Configuration. While App Configuration provides grouping, extensive querying, and baked in metadata for evolving application settings, Key Vault is still the best place to store secrets. If you have a request or idea in mind about how you would like to see these services tied together feel free to leave a suggestion in the Azure App Configuration feedback page
  • User profile image

    Hi Jimmy, It is really good. But one question, when I have different environments how do I manage them.
    Ideally what would be my performance on application. Any more insights?

  • User profile image
    Thx for this overview, it's amazing. What about costs? How long is this service going to be in preview mode and are there any considerations regarding pricing policies and running costs? Tia.
  • User profile image
    Will the `ConnectWithManagedIdentity` also work if you are running the web-app just locally?

    Or will it only work when running in Azure?
  • User profile image
    excellent video, I liked that you showed how to use it from different perspective, inside azure, json, C# code etc.
  • User profile image

    If you have different environments, you could manage them by assigning different labels to the key-values. Then when you query settings for one of these given environments specify the label, and you will get all the settings for that specific label/environment. This also sets up the usage of utilities like import/export and compare settings.

    One thing to take note of is that sometimes environments have security boundaries, for example testing and production. If this is the case then the recommendation would be to use two separate app configuration instances. This way access control can be controlled for the two environments that have clearly distinct access requirements.
  • User profile image

    The service is currently free. It is possible that in the future may introduce a SKU system where there would be tiers to Azure App Configuration, but it is common within Azure to have a basic/free tier which is what I would expect if anything like that ever happened.

    I can't really comment on exact dates, but I would expect before end of year. Getting out of preview is really about ensuring that we have the very solid foundation of feature/functionality that everyone would expect while at the same time ensuring that our service has a high quality and reliability that is required of something as essential as application configuration.
  • User profile image

    ConnectWithManagedIdentity has a fallback mechanism intended for use in development. If it is not running on an Azure platform with an assigned managed identity, then it will try to check if the current logged on user has an Azure Identity. If so, then it will attempt to connect to Azure App Configuration using that identity. So in local development if you are logged in with an AAD user that has access to Azure App Configuration ConnectWithManagedIdentity will work.
  • User profile image

    Great stuff! I learned quite a bit from this video. Thanks!

  • User profile image
    Thanks, very useful there a way to use this with Azure Functions V1?

    We have a number of functions which are all .NET Framework and migrating to .NET Core is not going to be straightforward.
  • User profile image

    Everything should work fine on V1 Azure Functions.

    V1 Azure Functions run on .NET 4.7 according to their docs This framework version is able to use the Microsoft.Extensions.Configuration.AzureAppConfiguration package presented in this video since it is a NetStandard2.0 package. That means it can be used in .NET and .NET Core.
  • User profile image
  • User profile image
    Great demo! Do you have any guidance on if there's still a use case for staying with Application Settings and Connection Strings within an App Service versus externalizing everything to App Configuration?
  • User profile image

    This is one of the features in our next wave of updates. I would expect it within a month.
  • User profile image

    That's a great question. I'd like to give the full story with my answer.

    Migrating settings to Azure App Configuration will bring some immediate benefits. Settings will now have a history available, a built-in versioning mechanism, and utilities such as diffing and restoring configuration will be provided via the service. On top of this, the centralized configuration will be available to multiple App Services or any other micro services. Another added benefit of Azure App Configuration is the capability to dynamically update configuration during the run time of the application.

    All of these benefits make migrating settings to Azure App Configuration a great choice. However, I do want to mention an inherent benefit of using Application Settings and that is that they are available immediately to the application because they are injected into the process as environment variables. This makes app startup completely deterministic since the settings are always available as soon as the process is started. Azure App Configuration fills this gap by offering the capability to export settings from Azure App Configuration to an App Service. This can be done during deployment time to get the best of both worlds.

    So with all the benefits laid out, my recommendation is that migrating to Azure App Configuration is the best path in all scenarios. The App Service will immediately gain the benefits of Azure App Configuration I mentioned above and Azure App Configuration fills the gaps with App Services by providing an export mechanism if desired.

Add Your 2 Cents