How to override Azure App Configuration with apsettings.json file for certain properties using .NET 7?

I have 4 .NET 7 microservices deployed in Azure Kubernetes Service. For local development environment, each microservice has appsettings.json and appsettings.Development.json file. Among these 4 microservices there are few properties in the appsettings.json file which are common and few are unique. In order to manage all the application related properties centrally I thought of leveraging Azure App Configuration It allows to centralize application configuration to a single place and have different applications use it.

I am able to connect to the Azure App Configuration via the connectionstring which is managed in Azure Key Vault.

For example, I have the below setting which has different value for different microservice

{
 
  "AppOptions": {
    "Name": "Microservice1.API"
  },
  "SwaggerOptions": {
    "Title": "Microservice1 Service",
    "Description": "Open API Documentation of Microservice1 Service API.",
    "Name": "xxxxxxx",
    "Email": ""
  }
}

The above values are different in case of Microservice 2 and the same applies for other two microservices.

Can anyone suggest me what is the way to override the Azure App Configuration properties and consider the values in the appsettings.json file?

Please share with me in case there is any other better way to deal with this issue

Can anyone please help me to fix this issue

I think the best practice is using labeling for app configuration. so that you can define a label per microservices.

For example in app configuration:

And in the code you can retrieve them like this:

builder.Configuration.AddAzureAppConfiguration(options =>
{
    options. Connect(connectionString)
           .Select(KeyFilter.Any, "Microservice1");

});

The above code is for Microservice1 and should be the same for other microservices with their label names.

In App Configuration, I recommend you prefix the key name with the microservice name. For example,

Then in each of your microservice, you load keys that start with that microservice and trim that prefix. This way, you app code doesn't have to deal with the prefix. For example,

builder.Configuration.AddAzureAppConfiguration(options =>
{
    options.Connect(connectionString)
           .Select("Microservice1:*", LabelFilter.Null)
           .TrimKeyPrefix("Microservice1:");

});

For local development, you can call AddJsonFile("appsettings.json") after calling the AddAzureAppConfiguration(...). Then what's in the appsettings.json will override what's loaded from App Configuration. Alternatively, you can skip calling AddAzureAppConfiguration(...) altogether if you detect you are in the dev environment, for example, based on an environment variable.