Thank you for all the votes and feedback. We have started work on this and the capability will be supported soon. If you would like to get in touch with us to discuss your scenarios, please fill this form: https://aka.ms/ApplicationGatewayCohort
We haven’t forgotten about this request! This is something we would like to bring in the future, but we cannot provide a timeline at this time.
Thank you for using UserVoice!
Still no news to share, just to add that we are investigating options on modifications for the App Service multi-tenant offering with enhanced capabilities.
We are still working on a few features which we hope to announce in a few months.
@Peter – We will not providing the WAF capabilities directly to Web Apps.
Further to @KWilson's post, you can set up an AGW/WAF in a separate RG to your Web Apps and route them all through the WAF. There is a limit of 20 (I think?) listeners so you can use the one AGW/WAF with multiple WebApps to reduce cost.
You can make it optional to provide a value for a param, by using a defaultValue and in some cases, just make the value “empty”. For example:
If you have scenarios where this isn’t working for you feel free to email…
A Default Value might be usable in some cases, however I've hit a point where I need to only set ConnectionString values for the WebApp if the Parameter is set. Leaving the Parameters blank breaks the deployment saying that the values can not be empty, however if the section is taken out of the template the deployment works and the values aren't attempted to be set in the portal.
this feature has been postponed as it wouldn’t be complete and might be revisited later if standards/supported features by CAs and browsers change (double wildcard certificates are not supported standard, resulting in no way to secure double wildcard domain)