Henry

My feedback

  1. 1,049 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    37 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Henry supported this idea  · 
  2. 75 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Azure Databricks  ·  Flag idea as inappropriate…  ·  Admin →
    Henry supported this idea  · 
  3. 1,106 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    39 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Henry supported this idea  · 
  4. 1,043 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    31 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Henry supported this idea  · 
  5. 136 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Henry supported this idea  · 
    Henry commented  · 

    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.

  6. 36 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →

    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:

    “defaultValue”: ""

    If you have scenarios where this isn’t working for you feel free to email…

    Henry supported this idea  · 
    Henry commented  · 

    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.

    +1

  7. 415 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    19 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Henry supported this idea  · 
    Henry commented  · 

    For us the intention would be to support www.*.<customdomain>. As a workaround we have been redirecting requests to www. to the naked domain so the certificate is valid.

Feedback and Knowledge Base