Do you have problems with your Azure Web App not updating after you publish (from Visual Studio or other tool)? I had these problems with my Azure Linux ASP.NET Core Apps, but they can happen with any type of Azure Web App (or even Azure Functions). I will explain how I solved these problems and why they occured.
Two important settings in Azure Web Apps that you should really care about are WEBSITE_DYNAMIC_CACHE and WEBSITE_LOCAL_CACHE_OPTION. Being careless with them can lead to either website updating problems or unnecessary performance degradation. I will explain why, and how you should handle them.
Most people (including me) run into this common problem the first time they try to deploy a Linux Web App: Web deployment task failed. Could not connect to the remote computer ("linuxtest1.scm.azurewebsites.net"). This is easily solved. I will show you how.
Running your Azure Web Apps (App Services) from zip packages is an alternative to the standard deployment model. I will here describe how to setup the package deployment model ("Run From Package") and what the advantages/disadvantages are.