When demonstrating RBAC in the IAM section the app service had contributor-level access. Which is to widely scoped I guess. Is something like read-only available?
Yes. In the current version of the Azure App Configuration configuration provider there are new required roles. Either "Azure App Configuration Data Owner" (Read/Write) or "Azure App Configuration Data Reader" (Read Only)
Also, request-based refresh... That means if I were to host a net core app on-prem, with no public inbound connectivity, refreshes won't work, will they? Only the initial loading if the settings will work. Right?
If there are no requests to trigger refreshes, it is possible to trigger them manually. docs.microsoft.com/en-us/azure/azure-app-configuration/enable-dynamic-configuration-dotnet-core
You sold it to me, Jimmy. Amazing service. App Configuration is what I was looking for long time
When demonstrating RBAC in the IAM section the app service had contributor-level access. Which is to widely scoped I guess. Is something like read-only available?
Yes. In the current version of the Azure App Configuration configuration provider there are new required roles. Either "Azure App Configuration Data Owner" (Read/Write) or "Azure App Configuration Data Reader" (Read Only)
Also, request-based refresh... That means if I were to host a net core app on-prem, with no public inbound connectivity, refreshes won't work, will they? Only the initial loading if the settings will work. Right?
If there are no requests to trigger refreshes, it is possible to trigger them manually. docs.microsoft.com/en-us/azure/azure-app-configuration/enable-dynamic-configuration-dotnet-core