We are planning to use below
Secrets - Azure Key-Vault
Master Key rotation for Always Encrypted columns
Certificate Store (can easily write a provider in .NET)
Sensitive items like connection
strings (hiding other resource info), passwords etc.
Configurations - Azure App Configurations (still in preview)
Watch is a wonderful method ...
I have the same opinion as you, I see no point in using the Key Vault in such scenarios.
Instead I utilize Azure App Configuration https://docs.microsoft.com/en-us/azure/azure-app-configuration/overview , where I simply store all application settings.
And the only string I store together within the actual app service/ func/ web job, would be the connection ...
I have fixed this partially by updating the routes.txt file in the installation folder for the client app by adding an entry for the subnet used by the gateway to assign IP address to new logins.
While this now routes to the correct PC when RDPing, unfortunately a new IP is assigned to the PC every time it connects to the VPN, making it difficult to know ...
The service hook will fire as part of the notifications process. You can suppress all notifications by setting the URI parameter suppressNotifications to true.
An example request URI might be:
See the work item update API documentation for more ...