Should I use one Azure App Configuration resource for all my environments or one by environment ?

Question

When I read the Azure App Configuration documentation, it seems it's possible to have only one Azure App Configuration for all my environments by using Labels.
I find it nice to have in one place the configuration for all my environments and be able to quiclky see the different versions, however I wonder if it's a good practice.

Indeed, usually my resources for different environments are separated into different resource group and even sometimes with different Azure Subscriptions and I have a version of each component of my project by environment. Even for deploying infrastructure as code, there is not usually one resource shared by all environments, or it would have to be created differently than the other resources in order not be created for each environment.

What is Microsoft recommendation about that ? How do you see things ? I guess if Labels have been created it's mainly for this purpose of having different versions of values depending on the environment.

Answer 1

@Alexandre - Thanks again for reaching out to us and being patient.

You could use different instances for different environments and you can use labels for enabling configurations for different environments.
You can take a look at the below doc for the same : Use Per Environment Configuration

But again, there is nothing wrong to use multiple instances if it would better fit for your project.

I hope this information helps. Please let us know if you have any further questions.