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. Correctly handle CORS with Range header

      When browser sends a Range request to CDN, CDN downloads the entire file from origin, then serve the appropriate range to the browser. However, when serving the content range, it does not send the CORS header that is present in the origin, thus breaking cross origin requests.

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

      Which SKU of Azure CDN are you using – Azure CDN from Verizon or Azure CDN from Akamai. See the following documentation for working with CORS and Azure CDNhttps://docs.microsoft.com/en-us/azure/cdn/cdn-cors. If CORS isn’t working after following this documentation please provide us a repro or open up a support ticket so that we can investigate further.

    2. provisioning a certificate should not take hours

      there isn't much to it. when a domain change or when moving an app to azure we're forced to set up the cname first and then the endpoint https next, so that users are immediately redirected to the endpoint but the endpoint won't serve it's proper certificate until 6+ hours later.

      6 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 →
    3. minify as well as compress files

      Azure CDN will compress files by type, why not also minify by type - so that it automatically minifies JS, CSS, HTML files that it caches, or passes through uncached.

      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 →
    4. 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 →
    5. 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 →
    6. 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 →
    7. Provide a way to Supress ETags when Using Akamai CDN and Blob Storage

      When using the Akamai CDN to serve content from Blob storage (strong) ETags are sent back with the response. These seem to confuse clients and make response time slower than they could be.

      e.g. https://jsfiddle.net/29zozLjk/show/ in Chrome this resource returns a 304, whereas it should always load from cache

      It would be nice if there was a way to prevent these ETags being applied - either at Content Storage or the CDN.

      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 →
    8. 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 →
    9. Add Azure Service Fabric Reverse Proxy Port to AKAMAI CDN Allowed Origin Ports

      The Azure Service Fabric Reverse Proxy allows services running in the cluster to be reached from outside the cluster via HTTP(s). The default port for the reverse proxy is 19081.

      Azure CDN (with AKAMAI) allowed origin port list currently does not include that port.

      AKAMAI CDN should include the default reverse proxy port for Azure Service Fabric in the allowed origin port list so that integration can happen right out of the box.

      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 →
      planned  ·  Anton Kucer [MSFT] responded

      Thank you for the feedback. We have confirmed the ability to add this port. We are targeting January 2018 to have this update in place as the Akamai network is currently locked down for this type of update until after the holiday season.

    10. CDN full code deployment

      Currently it doesn't seem possible to deploy a CDN through the CLI tool for the purpose of serving static web content from blob storage.

      Missing functionality includes:
      - Creating a CDN endpoint for a Premium_Verizon CDN
      - Creating Rules e.g. (HTTP -> HTTPS redirect)

      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 →

      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

    11. Can you reduce the configuration time for Azure CDN(Verizon & Akamai) to turn on https?

      Can Azure'Verizon and Akamai CDN turn on https less time, after all, not every customer is willing to let his environment without access to https for 6-8 hours
      Plus Azure Microsoft CDN capabilities are expected to be finished, after all, better than Azure Verizon and Akamai in terms of performance

      4 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 →
    12. Make deployments and config updates much faster

      The whole configuration and update of CDN endpoints is terribly slow and is causing enough confusion that we considered moving our CDN to Amazon, which works as expected. This on Verizon standard but might apply to others as well.

      1) Initial deployment took an hour before files (served from storage directly) were available on the CDN. The 404 messages are very confusing since the endpoint says it is available almost immediately and the url works straight away.
      2) Even after the first asset I was testing appeared on the CDN, others in the same storage folder took several minutes before…

      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 →
    13. SERVERS REQUIRED FOR USERS OF PAKISTAN

      Please establish servers in Pakistan and Dubai as there are no nearby servers for Pakistan. The minimum latency that we get here in Pakistan is around 250ms which is too high for developing projects and playing online games from your servers.

      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 →
    14. In the rule engine of Verizon Premium CDN, %{arg_<parameter>} support url decode

      Usually the value of %{arg_<parameter>} is url-encoded, and url-decode is required for subsequent references sometime. It can provide a function or delimiter to do this, like case conversion.

      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 →
    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. 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 →
    17. Alerts triggered from a URL RegEx

      It would be great if we could register alerts to trigger from a URL hit or number of hits / second.

      3 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 →
    18. CDN akamai cache hit rate

      Hello CDN PG,

      Please work with Akamai to make cache hit logs available via the Azure portal/CDN Core Analytics.

      We would like to have visibility of our cache hit rates for this service.

      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 →
    19. Add support for TeleSec / T-Systems CA SSL certificates on Azure CDN

      TeleSec / T-Systems is the biggest CA available in Germany. If a company, like our own, does not like to use foreign CAs for security reasons or for conformance with GDPR, it would be most helpful to support this one. (Plus, they once ran Azure in your name in Germany - perhaps that's why you forgot to add them?)

      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  ·  1 comment  ·  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 →
    • Don't see your idea?

    Feedback and Knowledge Base