Henry

My feedback

  1. 1,146 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    45 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,385 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    43 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Henry supported this idea  · 
  4. 1,261 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    36 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Henry supported this idea  · 
  5. 40 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 →
    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

  6. 441 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    20 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