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 HTTP variables for Standard rules engine (Standard Microsoft CDN)

      Currently there's no way to retrieve HTTP request/response cookies that we can then use to dynamically alter a request or a response. This is only available for Verizon Premium rules engine. It would be useful to have the same capability through Standard rules engine.

      19 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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    2. Provide the ability to prevent hotlinking in Azure CDN Standard

      The ability to deny content or serve alternate content when hotlinking is detected, via whitelist / blacklisting referrers.

      This would help us protect our CDN from third-party usage and is something AWS provides already.

      18 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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
      planned  ·  Anton Kucer [MSFT] responded

      I’ve update the title to indicate that this is a request for Azure CDN Standard. This capability is available to today with Azure CDN from Verizon Premium via the rules engine. Via the rules engine you can match on a specific referer and deny a request or redirect / rewrite the request to a different location.

    3. Verizon: allow SNI on origin server

      Verizon endpoints seem not to support origin servers if they are require SNI for their HTTPS bindings. This is a very unconvenient requirement if the origin server is hosting multiple websites.

      https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b745d9a3-54e4-4b5f-be61-1028e3d9f678/azure-cdn-endpoint-giving-502-bad-gateway-with-https?forum=azurecdn
      https://stackoverflow.com/questions/51374976/automatic-sni-resolution-between-cdn-and-origins-is-not-currently-supported-for

      Could this requirement be abandoned? I.e., could origin servers with the SNI requirement be supported?

      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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    4. 17 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      under review  ·  0 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    5. Add more endpoints outside of EU

      https://azure.microsoft.com/en-us/documentation/articles/cdn-pop-locations/
      Open CDN map- and you will find that for MOST geographical regions- CDN is irrelevant. For exUSSR region closest CDN is in Poland but latency just on a few millisecond less than directly from WE region. For MEA region- the same...

      16 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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
      started  ·  Anton Kucer [MSFT] responded

      Work is ongoing to provide POPs in additional Geographical regions. In November POP’s were added in India and South America. Additional POP’s in South America and in Oman will be added in the next few months. We also announced last year a partnership with Akamai which will allow us later this year to provide access to the entire Akamai network. Akamai has POP’s in over 110 countries. The following link from Akamai will help us see the level of coverage that they have today: http://wwwnui.akamai.com/gnet/globe/index.html

    6. Front Door - Allow caching of font/woff and font/woff2

      According to the list detailed on Azure Front Door - Caching (https://docs.microsoft.com/en-us/azure/frontdoor/front-door-caching#file-compression) WOFF and WOFF2 fonts are excluded from the list.

      The general consensus is that these fonts should be served with:
      font/woff
      font/woff2

      And previously as:
      application/font-woff
      application/font-woff2

      It would be great if these could be included in the allowed list along with the other font definitions.

      https://www.iana.org/assignments/media-types/font/woff
      https://www.iana.org/assignments/media-types/font/woff2

      15 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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    7. Use Let's Encrypt TLS certificates for managed HTTPS on CDN custom domain

      Current implementation of managed TLS certificates for custom domain on Azure CDN uses DigiCert and has a lot of issues (validation is slow and needs manual operations from Microsoft and DigiCert support).

      It would be better to use Let's Encrypt TLS certificates for managed HTTPS on CDN custom domain

      15 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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    8. Make another POP location in Moscow, Russia

      Make another POP location in Moscow, Russia

      15 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      planned  ·  2 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    9. cmdlet / API for updating 'Custom caching rules'

      It looks like the only way to update caching rules is via the WebUI, it would be nice if there was a programmatic way of updating custom caching rules, you know devops and all that. cmdlets / api / **** even ARM options

      14 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      planned  ·  1 comment  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    10. Allow configurable origin read-timeout length for CDN

      Currently Microsoft CDN have a 30 seconds timeout for first response from origin server requests. It would be great to have the timeout period configurable to allow for a longer period of time.

      99,9% of time, this default timeout is more than enough.
      But if some content needs a little more time, you will receive an error "HTTP 503 - our services aren't available right now".

      "The origin read-timeout length increases from two seconds for general web delivery to two minutes for the large file optimization type. This increase accounts for the larger file sizes to avoid a premature timeout…

      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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    11. standardize azure cdn offerings

      Currently I know that Azure provides CDNs from different vendors on the standard layer. There are three types of CDNs, as follows:

      S1 standard Verizon
      S2 standard Akamai
      S3 Standard Microsoft (Preview)

      Each offers different functions
      Https://docs.microsoft.com/en-us/azure/cdn/cdn-features

      But at the moment, our test has the best effect in the target area of ​​our products with Akamai's CDN effect, but
      Akamai does not support custom domain HTTPS features
      Microsoft does not support cache rules
      Verizon has all the above features, but the CDN effect is the least desirable in the target area of ​​our products.

      I am interested to know if…

      11 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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
      started  ·  Anton Kucer [MSFT] responded

      We are targeting to have parity across all standard SKU’s. Cache rules for Microsoft and HTTPS Custom Domain support are all targeted to be available later this year.

    12. 11 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      2 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →

      Azure CDN is currently revaluating their plans for Azure Government

      For customers that have both public Azure and Azure Government, given that CDNs don’t host restricted data, you can use Azure CDN from public Azure in the interim.

    13. Dashboard with CDN Information

      1. The current CDN portal provides the required information, but it would be good to have something in the form of an Dashboard, which can provide an complete view of the performance and utilization.

      2. Region/Country wise cache status and the hit and miss ration is good to have to understand the traffic and to be aware of the performance from the different regions.

      11 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      under review  ·  1 comment  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    14. Support compression directly from IIS Origin

      Azure CDN adds the Via header when it communicates with origin servers as this is required by HTTP/1.1 - (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html). IIS by default does not apply HTTP compression to requests that have the "Via" header. This prevents gzip compression from working by default with Azure CDN as IIS by default will not compress content when it receives a request with a Via header. This default setting for IIS can be changed by setting the noCompressionForProxies to false.

      This is not intuitive and should "just work". The whole point of having combined services in Azure is that we shouldn't…

      11 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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
      planned  ·  Anton Kucer [MSFT] responded

      I significantly updated the title and contents of this request to accurately reflect why compression from an IIS origin does not work with Azure CDN. The CDN does support HTTP/1.1 when communicating with origin servers. We are planning on adding support in the future that will allow one to prevent the Via header from being sent to IIS.

      In the next month we are also targeting to enable one to have the CDN compress files directly – see http://feedback.azure.com/forums/169397-cdn/suggestions/1074433-automatic-http-compression-on-azure-blob-cdn-gzip.

    15. Request filtering like AWS WAF

      Add request filtering ability like in AWS WAF

      11 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      planned  ·  0 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    16. CDN for root-DNS entry

      Actually it is by design not possible, to add a cname entry for the root-Level DNS entry. But a cname is needed to provide a CDN. I dont want to publish all my Websites with WWW, just to use a CDN.
      Some Providers already have the Workaround and provide a ANAME.

      Please provide also a Workaround, to provide a CDN for the root-Domain.

      Thanks, Martin

      10 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  ·  Content Delivery Network  ·  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

    17. CDN Origin Host Header misguided instructions and required field

      If you front a blob store with a Azure CDN then by default it does not work, you are required to enter a Origin host header before it works. This then should be a required field. Also the tool tip hint in the portal for the origin is very confusing "Azure CDN origins, such as Web Apps, Blob Storage, and Cloud Services, require this host header value to match the origin hostname by default." Using 'required' and 'default' is bad wording in this situation. There are many people falling into this trap from a quick search on the internet.

      10 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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    18. CDN

      Please Azure CDN(Standard Microsoft SKU) support "X-Forwarded-For".
      My customer need to know original client src IP address in origin servers.

      10 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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    19. Is there any plan to implement how to operate Azure CDN by JAVA SDK?

      We are now using JAVA SDK to access Azure service but it seems no api to operate CDN service. We need to use the "query string" function of azure cdn with java, i would like how to define the file name pattern of resource like css or javascript.
      So, we would like to know is there any schedule of this request will be planned? Thanks.

      10 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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
      planned  ·  Anton Kucer [MSFT] responded

      Yes support for Java SDK is planned. Initial API support for Azure CDN is targeted to be available in December. Java SDK support will follow after this is released.

    20. Azure CDN should have the possibility to rewrite response code from origin

      Azure CDN should have the possibility to rewrite response code in case of error (404,500 response) from origin like AWS CloudFront has:

      "You can choose the HTTP status code CloudFront returns along with a custom error page for a given HTTP status code. For example, if your origin returns a 500 status code to CloudFront, you might want CloudFront to return a custom error page and a 200 status code (OK) to the viewer."

      10 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      triaged  ·  0 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    • Don't see your idea?

    Feedback and Knowledge Base