Web app deployed with alwaysOn seems to be impossible to downscale through ARM

This is not so much a complaint about a template, maybe more of a suggestion to add a sample.

I wanted to have a template where you could configure the App Service Plan tiers. This seemed to be very easy and lot's of samples exists in this repo. However, if you have the "alwaysOn" property set to "true" in one of the web apps and want to scale to a tier that doesn't allow this function (shared and free), there is no way to have ARM scale down. The moment you specify "free" and alwaysOn to "false", my deployment fails. Problem relies in the sequence of deployment, the app service plan goes before the web app itself. The "free" tier is an App Service Plan configuration and it tries to update that value, however, it can't. There is a webapp using "alwaysOn" which is not allowed on the free tier. Hence, I should update the webapp first with "alwaysOn: false", but that's a weird thing to do. The service plan should be deployed BEFORE the webapp. This seems a like a deadlock situation, am I right?

Begin with the ARM deployment sequence for the App Service Plan and web app, focusing on the alwaysOn constraint when changing to the free or shared tiers. Reproduce the downscale failure and identify the relevant quickstart sample entry points; done means a documented sample or deployment path that handles this transition successfully.

Written by the indexing model from the issue text.