If you’re still doing configuration in web.config files for your Azure services, it’s time to try something new and leverage something that has been there for quite some time – Application Settings.
In your Azure Portal, you will notice a section called Application Settings. Within this section is everything you need to configure your application. If you have some custom configuration data in your web.config file, a simple way to rely less on the web.config (and make your end administrator’s job a little more easier) is to expose these configuration values via Application Settings.
The process to create a new Application Setting is straight-forward, create the setting, add the value. (In this case I created a key called Tool).
In your ASP.NET Web app, the process to consume the configuration value is even easier.
When run, the title of my page is now called “Hammer” as was defined in the Application Setting. If I change it, no need to redeploy my app, it updates accordingly (as it should).
It’s important to note that adding this key into your web.config file does not force an override in your Azure Application Settings – it is the opposite. When my Application Settings are not present, the following will be displayed.
However, if I were to add the “Tool” setting back into my Azure Portal, the previous value would be applied.