Anonymous

My feedback

  1. 110 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Web Apps » App Service Environment  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    We bought dedicated Application Gateways for each slot to get around all of the problems of going through a central Application Gateway/Web Application Firewall for all deployment environments. Well now we find out that IP Restrictions are not sticky to the deployment slots. Isn't this a fine mess? Please escalate this request as even throwing money at all the extra Gateways does not help us unless we open a gaping hole in security.

  2. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
    Anonymous commented  · 

    Application Gateway backend pools are not natively aware of an App Service's deployment slots. I have to get around this by, instead of targeting a backend pool to type "App Service", I need to target type "IP or FQDN" and then put in the "client-staging.azurewebsites.com" or "client-development.azurewebsites.com" values (if using the original example).
    At the very least, make the backend pool App Service target aware of the deployment slots to select in the drop down list.
    However, the original poster's (OP) request would be a complete solution: Have the Application Gateways be aware of app service deployment slot swaps so we don't need to manually fuss with App Gateways for slot swaps. App Gateways should be swap-aware.

  3. 1,068 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    41 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    Glad to hear that this is being actively developed. It can't come soon enough.

    Anonymous supported this idea  · 
  4. 755 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    29 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    This is a major blocker to implementing on Azure. We have 100's or 1000's of mini-sites with custom sub-domains to distinguish them. Application Gateway is not scalable - dead in the water.

  5. 134 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    This is very important. Since we need to use the App Service Certificate at the Application Gateway, we are forced to turn off auto-renew on the certificate and do it manually. This is a noticeable loss of value to the ASC offering. Allowing the Application Gateway to get the certificate from Azure Key Vault would maintain full functionality.

    Anonymous supported this idea  · 
  6. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous commented  · 

    Yes, please make dynamic DNS native for the Azure DNS service

    Anonymous supported this idea  · 

Feedback and Knowledge Base