Using environments with Azure App Configuration

The Azure container apps are deployed and running, using all the Azure services we have created so far. What’s missing with App Configuration are the different environments that are supported with the .NET configuration. Is the application running in the local development environment, in the Azure test environment, or on the production server? Running in the test environment, the production database should not be used.

.NET configuration supports different environments – depending on the environment, either appsettings.development.json or appsettings.production.json is loaded. Similar functionality is possible with Azure App Configuration using labels. We can specify development, production, and testing labels to differentiate environment configurations. This can be mapped to .NET environments.

Note

It’s a good practice to separate the production and the development environments across different Azure subscriptions...