Drago Draganov

@SirElTomato Thanks for the request. We are very interested and indeed looking at this (and similar category scenarios) going forward. Though, there isn't yet a solid ETA I can provide...

Isolating production config store is always recommended, regardless of authorization. It allows for network level security (aka PrivateLink), low latency (with deployment closest to your services), dedicated quota, etc.

@arkiaconsulting, It's a great suggestion indeed! My understanding is that specific reference is only applicable for Azure App Services/Azure Functions. Nevertheless, we should work with these respective teams to help...

@Yiming-Jia, can you help @adriend-advz ?

@Jaelid, can you provide what Azure AppConfiguration client are you using (SDK, Configuration Providers, CLI, etc.)? There are KeyFilters and LabelFilters.

For selecting shared settings and namespaces, we indeed recommend the composition you use. [here](https://docs.microsoft.com/en-us/azure/azure-app-configuration/howto-best-practices#key-value-compositions) Perf wise, we should look into that Python SDK to see the reason. Do you mind...

I agree that filtering by tags is useful and we are looking into allowing that. I don't have specific ETA at the moment. My intention was to address the original...

Thanks for bringing that up! It helps us prioritize.

We had that feature on the service side during preview and decided to take it out due to perf complications. https://github.com/Azure/AppConfiguration/issues/342 If the result set isn't large, we could consider...

Thanks! @jiayi11 is this something we can consider on portal?