Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Networking

The Networking forum covers all aspects of Networking in Azure, including endpoints, load-balancing, network security, DNS, Traffic Manager, virtual networks, and external connectivity.

Virtual Network:

  • Service overview

  • Technical documentation

  • Pricing details

  • Traffic Manager:

  • Service overview

  • Technical documentation

  • Pricing details

  • Network Watcher:

  • Service overview

  • Technical documentation

  • Pricing details

  • If you have any feedback on any aspect of Azure relating to Networking, we’d love to hear it.

    • Hot ideas
    • Top ideas
    • New ideas
    • My feedback
    1. Support for W3C Trace Context (distributed tracing)

      Please add support for W3C Trace Context (https://www.w3.org/TR/trace-context/).

      Azure Application Gateway should generate (and log) the required headers for the trace context so that end-to-end tracing would be possible. Preferrably with integration to Application Insights which already supports this.

      75 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    2. Application Gateway Redirection 308 Permanent Redirect Not Implemented

      According to Documentation available under https://docs.microsoft.com/en-us/azure/application-gateway/redirect-overview, currently Application Gateway does not support 308 Permanent Redirect Methods defined in RFC7538 when doing redirects.
      This can lead to problems with some browsers when doing request, most problems arise when a POST Request is sent to the HTTP Endpoint and it redirects to the HTTPS Endpoint but the Method changes to a GET.

      5 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    3. Better visibility for Instance count, CPU and Memory utilization on Application Gateway

      There should be a better and clean way to see Instance count, CPU and Memory utilization on Application Gateway, rather than going thru doing calculations on Throughput/Connection/SSL provided in this document:
      https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-metrics

      It would help immensely if these 3 metrics are available for what they are and present the data for immediate glance and not do calculations. We dont have to open a case to see this data, every time it is needed.

      18 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    4. Move Application Gateway to Another Resource Group

      Please remove Application Gateway limitation move to another RG. It can be applied use case like give another team or person at another RG at one subscription without recreate the Application Gateway. Thank You.

      6 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    5. I want to set HTTP keep-alive ON / OFF in the Application Gateway settings

      When the Application Gateway is in the process of forwarding an HTTP request to the backend, Connection Header Value in forwarding HTTP request is "keep-alive".
      Therefore, to disable HTTP keep-alive in the process of forwarding an HTTP request to the backend, it must be set in the backend settings.

      But Some customers using Application Gateway may also have a requirement that the backend settings can't be set.
      Even for such customers, it would be more convenient to be able to disable keep-alive in Application Gateway settings.

      9 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    6. Allow both AppGw and Standard Public IP Address to move from one subscription to another.

      Allow both AppGw and Standard Public IP Address to move from one subscription to another.
      We, regardless of using AppGw v1 or v2, would be allowed to move an existing AppGw entirely by doing this.

      56 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    7. Refine HTTP to HTTPS Redirect configuration

      Refine HTTP to HTTPS Redirect configuration.

      Process for configuring HTTP to HTTP redirection in Azure Application Gateway is cumbersome and needlessly complex.

      Something as simple as a tickbox on an HTTPS Listener/Rule to catch and redirect all HTTP traffic would be sufficient for 98% of web and application hosting scenarios.

      17 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    8. Azure Application Gateway DNS refresh time for backend with FQDN

      After adding a backend using a FQDN to Application Gateway Backend Pool the domain name is cached forever (or until the gateway is updated).

      If the IP addresses for this backend changes and the cached once stop working the health probe for all the hosts will start to fail and the backend will soon become entirely offline (although it actually is working fine using the new IP addresses).

      Having a setting for how often to update a backend (or all backends) cached domain would make the gateway backends be much more stable compared to today. This could be compared to…

      20 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    9. ProhibitedTargets support on AGIC add-on

      Hello Team,

      Our customer has need to deploy shared App Gw via AGIC add-on instead of HELM.
      However, in the doc below, ProhibitedTargets was not supported by AGIC add-on.
      https://docs.microsoft.com/en-us/azure/application-gateway/ingress-controller-overview#difference-between-helm-deployment-and-aks-add-on

      Can you please consider add this feature on AGIC Add-on? Thanks!

      7 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    10. Application Gateway Health Check DNS Retry

      We were told by support that if the Application Gateway Health Check DNS request fails (the DNS entry is not found) the Application gateway will not try a lookup again until there is a config change. We have a race condition when standing up new apps that sometimes the health check happens before the DNS Entry can be resolved which causes the site to stay in an 'unknown' state forever until the next config change.
      We would love to see some kind of retry logic around DNS lookups as DNS requests fail sometimes. It seems like a bad idea to…

      3 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    11. Add REST APIs and SDK to manage Application Gateway child resources

      (following github issue https://github.com/Azure/azure-rest-api-specs/issues/8252)

      Hi,

      Currently, REST API and SDK (go, javascript, ...) does not provide way to manage Application Gateway child resources (backend address pools, frontend ip configurations, load balancing rules, ...).

      However, it's possible with the AZ CLi.

      Could the REST APIs and SDK be updated to allow it?

      Regards,

      122 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    12. Add X-Forwarded-For information in Application Gateway Access log

      If we have other Layer 7 Load Balancer like Cloudflare load balancer uses in front of AppGw, we are not able to obtain real client IP. Imagine Cloudflare load balancer inserts X-Forwarded-For info before forwarding request to AppGw, can we add X-Forwarded-For information in Application Gateway Access log?

      147 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      5 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    13. Application Gateway (V2) - there should be an option for enabling/disabling buffering

      Currently, Application Gateway v2 has enabled buffering so there is no way to send chunked data also header Transport-Encoding is always removed from the requests. That doesn't happen with V1 and definitely should be allowed to control it.

      12 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    14. WAF disable OWASP rule for specific request elements

      Hello Team,

      We have needs to disable OWASP rule for specific request element and keep OWASP rule monitor other request elements.

      Thanks!

      3 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    15. TLS 1.3 and HSTS Support for Azure Application Gateway

      This is about a feature request for an Azure Application Gateway to support TLS 1.3 and HSTS.
      At least HSTS is just a secure header which should be trivial to implement.
      I`m looking forward to a feedback.

      632 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      18 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →

      Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature

    16. Multiple site hosting with AAD easyauth enabled

      We need to have an easy-to-configure flow for hosting multiple sites/apps with AAD easyauth enabled under the same custom domain. e.g.
      https://contoso.com/myApp1 --> https://myApp1.azurewebsites.net, and https://contoso.com/myApp2 --> https://myApp2.azurewebsites.net
      The goal is to have both apps working and their authentication flows and redirects not break.

      3 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    17. Correct processing of Scale Set certificates

      If Scale Set is set as backend, and certificates are issued to each of Scale Set VMs individually, then there will be an error in Application Gateway: "The Common Name (CN) of the backend certificate does not match the host header of the probe." because App Gateway will not use valid FQDN as hostname when querying those VMs.

      1 vote
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    18. Application Gateway X-Forwarded-For IP:port is malformed

      Possibly this can be resolved by settings only; if so needs better documentation.

      X-Forwarded-For is only supposed to have IP address only (no ports). Our parser choked. In looking to improve the parser we very quickly discovered that as specified it causes a parse ambiguity in IPv6. That is, appending :port to an existing IPv6 address spelled with :: results in another valid IPv6 address. It would have worked if it was [IPv6]:port which is even more broken as compared to what the defacto standard is but is at least unambiguous.

      Needs doc improvement and possibly code improvement. Or maybe…

      3 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    19. We can not see any error when we delete permission for AppGW from KeyVault.

      When I deleted a permission from KeyVault to get Secret, We could not see any errors. It's very confusion. I can not identify the reason why AppGW is failed status. I hope we can see error about KeyVault side configuration.

      1 vote
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    20. Application Gateway needs load balancing methods

      Currently it seems Application Gateway only allows a round robin of all servers in the pool - there's no way to change this.
      Having a weighting of how many to each server, or picking the first of a list?

      For an example scenario - Imagine two servers A and B and in general you want server A to handle all urls /projectA/... and server B /projectB/... for efficiency reasons. However both servers are able to serve up both sites if needed. You could have 2 pools, one with server A first and one with server B first on a "first-server"…

      1 vote
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    ← Previous 1 3 4 5 12 13
    • Don't see your idea?

    Feedback and Knowledge Base