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. File Server (NFS/SMB) as Azure CDN origin

      This is a request for File Server as Azure CDN origin. OSS solutions specially in the Education space like Moodle Learning Management system, utilize file servers (SMB & NFS) for storage of static contents. This capability will be significant boost to the performance of such Solutions when deployed on Azure infrastructure.

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

      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 →
    3. Support to override caching headers in Azure CDN or AFD which is the cache control was set as private..

      Currently Azure CDN or AFD do not support to override the caching header when it has header as Cache-Control: private, Cache-Control: no-cache, and Cache-Control: no-store.

      The ability to override misconfigured applications is a key CDN feature because many applications send incorrectly configured cache-control headers by default.

      Hope add this feature in next release.

      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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    4. SSL certificate from keyvault should not link to specific version

      This is about the option to select your own managed SSL certificate for a custom domain from a key vault.

      In Azure Front Door and an Azure App Service you can just select the certificate. If you replace the certificate in the key vault with a new version, the Front Door or App Service will automatically sync and use the latest version.

      However, in Azure CDN you can only select a specific version of the certificate. If you then replace the certificate in the key vault, the CDN endpoint will still point at the old version and you must switch…

      6 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 →
    5. 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 →
    6. Add referrer information to the Microsoft CDN Http Raw Logs

      I can see that with a standard Microsoft profile, you can enable http raw logs that can then be used to analyze usage patterns.

      The referrer doesn’t seem to be part of raw log properties (URL of the web page or resource that links to our cdn content). It would be useful to add this information if present and possibly even whole raw request.

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

      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 →
    8. CORS

      I'd like support for using wildcard domains for CORS on Azure CDN, such that I can work within the Standard Rules Engine for "Standard Microsoft" ski. Currently, I haven't found a way.

      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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    9. CDN-managed certificates should come with CAA record

      Consider following scenario: I use a Azure CDN with a custom hostname and CDN-issued certificate for the custom hostname.

      I'd configure a CNAME alias: my.website.com CNAME my-website-com.azureedge.net

      In this scenario, a record like my.website.com CAA ...digicert... is not allowed, see e.g. https://stackoverflow.com/a/34614769/705086

      Thus, I believe that Azure CDN, the bit that issues a CDN-managed cert should also publish a record like my-website-com.azureedge.net CAA ...digicert....

      This would also help getting the A+ rating on sites like sslcheck.com which favour CAA records.

      Github ref: https://github.com/MicrosoftDocs/azure-docs/issues/54715

      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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    10. CDN - Increase limit of 25 endpoints per profile, or fix your API error message

      Either increase the limit of 25 endpoints per profile, or fix your API error message which tells us to contact Microsoft to get the limit increased.

      {
      "error": {
      "code": "BadRequest",
      "message": "The number of endpoints created exceeds quota. Please contact support to increase quota."
      }
      }

      4 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. Support CDN Managed SSL Certificates for Apex/Root Domain

      Root/apex custom domains mapped to Azure CDN should be able to use CDN managed certificates just like other domains. When serving up content via CDN on multiple domains, it is cumbersome to have all but 1 that are CDN managed, and then have to go out and purchase another SSL certificate just for the root/apex domain.

      95 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 →
    12. Allow OR condition in Rules Engine match conditions for Azure CDN from Microsoft

      Allow OR condition in Rules Engine match conditions for Azure CDN from Microsoft. At the moment when you create multiple match conditions, they are combined using AND logic by default. It would be good to be able to choose between AND and OR.

      60 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 →
    13. Enlarge the number of Rules in Rules Engine for Azure CDN from Microsoft

      Enlarge the number of Rules in Rules Engine for Azure CDN from Microsoft. The current Rules engine allows 1 default and 4 custom rules. Making it to 10 or 20 will help significantly.

      58 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 →
    14. Azure CDN: Allow more Global Actions

      The Standard Microsoft CDN now has a Rules Engine similar to the Verizon Premium CDN, but there is a limit of 3 actions per rule. This is probably sufficient for most custom rules since you can create as many as you need, but since you can't create a custom rule without a condition (you must use the global rule for these), you are limited to 3 always-triggered actions. This is the most logical place for adding security headers, so it would help to remove the limit, or have a much higher limit of actions for the global rule.

      More here: …

      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  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    15. to enable configuring rules at HTTP Large Object Rules Engine inside Verizon CDN with arm template

      Today, you can configure Verizon CDN rules via UI at separate portal only,
      I'd like to have ability to have those rules (like rewrite or redirect), configured in arm template

      4 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 →
    16. Ability to test CDN Rules within the portal

      The provitioning of the CDN Rules take up to 10 min. It would be helpful to have the ability to test the match contidions and the action result within the portal bevore saving the rule. At the moment we are experiancing a frustrating trial and error experience.

      28 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. 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 →
    18. Add exclusion feature in CDN profile to be able to exclude certain user IPs for country filter rule

      Team, please consider to add this feature in future roadmap as we have customer use case that they need to whitelist certain user IPs as the users could be working outside of the country or travel abroad temporarily.

      3 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 →
    19. 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 →
    20. Verizon's CDN to prioritize compression scheme based on service response

      Verizon's CDN offering prioritize other compression schemes over Brotli. However, if a client can support Brotli (listed in Accept-Encoding request header) and the backend service treats Brotli as priority and actually uses it (Content-Encoding header in response is "br"), CDN should honor the will of the application and use Brotli as the mean to compress the responses. That in fact, can be applied as a general rule. The compression scheme supported and requested by the client and enforced by the service should take priority. Otherwise, the CDN would always have to decompress/recompress the resources. This is wasteful and inefficient.

      3 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 →
    ← Previous 1 3 4 5 6
    • Don't see your idea?

    Feedback and Knowledge Base