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. 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

    2. Integrate customizing cipher suites in Azure CDN.

      Allowing custom cipher suite configuration is an important feature and allows for better security control. If there are any new vulnerability on any of the cipher, we can quickly arrest the issue by disabling the specific cipher. This can greatly minimize the impact on the system’s operations.

      For information, this request is arising from the security findings after VAPT was conducted for this system. As more government agencies onboard GCC and use the Verizon CDN service, this will likely be a repeated finding which will come up during security testing. The interim solution for custom domains for all impacted systems…

      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 →
    3. lamda@edge like functionality in Azure

      AWS has a service called lamda@edge. But Azure don't have anything that can be compared with it. Due to this lack of capability, we are not able to migrate to Azure. Going without this requires a huge amount of changes to the system which is not feasible at all.
      Are you guys planning something similar?

      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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    4. I want to support SSL for your custom CDN domain.

      I want to support SSL for your custom CDN domain.

      9 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      3 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    5. CDN should support ETAGS just like they support last modification date

      When performing a request with 'If-Modified-Since' header, CDN correctly respond 304 if data is not modified. But they ignore equivalent ETAGS directive: IF-None-Match and always return OK 200. They should consider it. Just as described in RFC 7234.

      9 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

      This is a limitation just with Azure CDN from Akamai. With Azure CDN from Verizon ETag support is enabled by default. Supporting ETags is an optional and not a mandatory header per HTTP RFC. We are working long term to mitigate / remove differences in caching behavior between Verizon and Akamai.

    6. Allow applying the same custom domain name on multiple CDN endpoints

      Only being able to use a custom domain on a single endpoint blocks a couple of scenarions:

      1) Using CDN with multiple origins, e.g. an origin server in USA and one in Europe

      2) Failover between CDN profiles

      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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    7. Custom domain confirmation status is confusing

      When a user configure custom domain configuration to Azure CDN endpoint, it sometimes happens that confirmation email from DigiCert doesnt receive quickly.

      In that case, Azure portal says that "pending" on sending out the confirmation. according to CDN document, it says that confirmation email delivery could take up to 1 hour.
      If it is pending, it would be nicer if the portal could say that how many hours it required to deliver or process queued emails.

      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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    8. Provide Feedback as to if CDN can reach origin url.

      Right now you need to wait 90 minutes or so (potentially) if you are getting 404 errors on content. It would be nice to have some kind of visual feedback on the endpoint configuration page if the origin url was reachable from Azure.

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

      With Azure CDN from Verizon it takes up to 90 minutes for configuration for a new CDN endpoint to propagate to all worldwide CDN POPs. For a new endpoint you will get back 404 errors until the configuration has propagated to the CDN POP that you are making requests to. We are working with Verizon to reduce this propagation time and also working with them so that we can deterministically provide feedback via API and UI when this propagation has completed.
      With Azure CDN from Akamai CDN endpoints are typically created in under a minute and the status of via API and UI accurately reflects when endpoint configuration has completed.

    9. API for Real-Time Stats of CDN

      Provide API to get live CDN metrics (number of requests, different cache statuses, different HTTP response codes, response time, origin time etc) from CDN. The same metrics is available now only via HTML dashboard in CDN manager as "Real-Time Stats", but enterprise setups need the data to our dashboard systems, not as yet another separate website.

      8 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 →
    10. Fix brotli support in Azure CDN / Microsoft Profile

      MS Profile has brotli support -- except that it doesn't serve brotli-compressed files if the request also allows gzip. The whole point of doing brotli is to PREFER brotli, and FALL BACK to gzip. They shot themselves in the foot with this feature, making it totally useless to server Javascript and CSS to browsers.

      8 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. Purging via CNAME

      Currently purging is just supported by specifying the CDN endpoint. For case where a rewrite rules is used to direct customers to different content based on the CNAME (e.g. by selecting content to return based on host name) it is valuable to have the ability to purge content based on CNAME. Without this capability one needs to create individual CDN endpoints to use for each CNAME that has different content returned based on the CNAME.

      8 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 →
    12. Allow a CDN to be a linked resource

      We want the ability to see CDNs which are related to a particular property as well prevent accidental deletion if linked.

      8 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 →
    13. Provide access control feature

      I'm looking to use Azure CDN to replace a password-protected FTP area. The lack of access control is preventing me using the CDN.

      7 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. Powershell/CLI/ARM Template support to edit Azure CDN "Caching behavior"

      ARM Template support to edit Azure CDN "Caching behavior"

      Currently only "Query String Caching Behavior" is supported in ARM Templates.

      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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    15. 7 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. Allow us to restore a deleted CDN profile

      Allow us to restore a deleted CDN profile

      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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    17. Minimal rules to Azure CDN to support static websites based on Blob Storage

      The Azure Blob Storage is lacking a few features to actually support a static website. Namely, there is no way to have a "default blob" fallback to emulate the behavior of a default file in every "folder". Right now, the Verizon Premium CDN (abyssally bad UX) is the only option if one ever hope to host a static website backed by the Blob Storage on Azure. It would be much nicer if the Azure CDN could provide minimal features. No need for a full URL rewrite engine, a few minimal options tailored for the Blob Storage should be enough.

      7 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. Support HSTS and HPKP

      Allow HSTS and HPKP to be enabled on Azure CDN

      Currently these values can only be passed through from the origin, which is fine for HSTS but can cause issues for HPKP (as the CDN cert may change, and probably doesn't match the origin cert)

      7 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 →

      How do you want HSTS to be enabled on the CDN? HSTS can be enabled on Azure CDN from Verizon Premium by using the rules engine to add the “Strict-Transports-Security” response header. Support for HPKP would likely require customers to provide their own HTTPS certificates. Once support for providing your own certificates is available the rules engine could be used to enabled HPKP support.

    19. Automate CDN Purge

      As a user of Azure DevOps for our CI/CD pipeline, some Azure CDN tools would be useful, for triggering a purge of resources for instance

      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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    20. Rule engine support for standard verizon

      Standard verizon don't support rule engine.

      For example, i want deliver font, standard verizon can not be set a cors because this is not support rule engine.

      Please support only frequently used settings at least.

      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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    • Don't see your idea?

    Feedback and Knowledge Base