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. Custom domain HTTPS support for Azure CDN from Akamai

      This is supported for Azure CDN from Verizon profiles (https://azure.microsoft.com/en-us/blog/announcing-custom-domain-https-support-with-azure-cdn). Also add this support for Azure CDN from Akamai.

      590 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      under review  ·  12 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    2. Redirect to HTTPS

      Allow HTTPS only configuration to responds with 'redirect to HTTPS' when HTTP request is received. This will be very useful for the new static website storage accounts. Especially, when the wider premium 3rd party CDN is not needed.

      450 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      25 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    3. CDN Allow Root Domain for Custom Domains

      It would be great to be able to set an A record to a root domain for CDNs like you can with web apps.

      For example you can set a CNAME to www.example.com but you cannot set an A record to example.com.

      167 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      8 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    4. Make raw logs available for CDN traffic

      If raw logs were made available and posted to blob storage, developers could use them for sub-billing our customers for their usage of the CDN.

      155 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      planned  ·  10 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    5. Fallback to custom URL when content not found

      Would be good if MS could provide fallback to custom URLs when content is not found on CDN

      131 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      under review  ·  2 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    6. 129 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      planned  ·  13 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    7. Make full purge and wildcard purge for AKAMAI CDN

      There is no way I can purge AKAMAI CDN endpoint fully or with wildcard which is best fit for our project.

      116 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      6 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    8. Allow changing of pricing tier

      Allow changing pricing their from Verizon Standard to Verizon Premium and vice versa

      105 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      planned  ·  2 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    9. Prevent Azure CDN Bandwidth abuse

      Hello,
      I have already made a couple of posts in regards to this issue on StackOverflow: http://stackoverflow.com/questions/35488753/how-to-prevent-azure-cdn-bandwidth-abuse-by-malicious-bandwidth-vampire-requests and on MSDN CDN forum: https://social.msdn.microsoft.com/Forums/azure/en-US/9e37ca24-b38d-4193-847b-f679eab76aa5/azure-cdn-bandwidth-abuse-by-malicious-bandwidth-vampire-requests?forum=azurecdn but so far, unfortunately, no good solutions to the problem were offered. So I thought it would be a good idea to post this idea here as well, and get a little more into detail on how to solve the issue since this little fix can easily be integrated into the upcoming WAF offering with the Premium SKU.

      Problem:
      To summarize, the problem can simply be stated as follows: Any large multimedia content file such as an…

      103 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      under review  ·  2 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    10. CDN image auto image crop and resizer functionality for images

      It would be really good, if the CDN could handle query strings and for the file format of images, handle resizing and cropping parameters automatically to resize our content needs... This done by the Azure CDN by its own.

      101 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      under review  ·  8 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    11. CDN: Support Vary: Origin header.

      The CDN ignores the Vary: Origin header, and thus the associated Access-Control-Allow-Origin is not emitted either. Even though the underlying blob store does return the correct Vary header, the CDN ignores this (basically breaking HTTP logic) and returns the same response to all users regardless of the origin (X-Cache: HIT) is then returned instead.

      This is basically a flaw, a bug, and an oversight- but I'm not going to pay for Azure support to tell you this.

      Without this functioning properly, the CDN cannot be used to host website resources (such as fonts) since these must all have Access-Control-Allow-Origin headers…

      94 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      9 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
      planned  ·  Anton Kucer [MSFT] responded

      Azure CDN by default ignores Vary header except when it is used with Vary: accept-encoding. This is done as the Vary header can easily cause serious cache bloat issues. Long term we are targeting feature to allow users to easily adjust this default behavior.

    12. wildcard ssl / domain / url support for Azure CDN

      Allow a wildcard domain like *.mydomain.com and wildcard SSL for such a domain as well. This will allow support for dynamic domain creating like multi tenant systems which might use that

      93 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      under review  ·  5 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    13. 70 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      under review  ·  1 comment  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    14. Ability to provide custom error response for HTTP errors e.g. 404's

      Ability when 404 is returned by ones origin to have the CDN respond with a preconfigured URL i.e. custom response page.

      67 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      under review  ·  3 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    15. Support WebApp deployment slots for Endpoints

      In the Azure Portal, when configuring an Endpoint for a CDN resource, you can select WebApp. It gives you a nice list of WebApps you have access too. The problem is, if those WebApps are using Deployment Slots for staging (Dev, Test, Prod); you can't add an Endpoint for anything other than the production slot.

      We would like to have a mirrored setup where our WebApp Dev slot is accessible through the CDN.

      The work around is to add a custom origin, which works--but seems like the WebApp feature could be more robust.

      Thanks!

      62 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      under review  ·  2 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    16. Custom rules for WAF

      Allow user created rules for WAF.

      61 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      under review  ·  5 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    17. HTTP/2 Server Push Support

      Would be nice to support Server Push, we want to use them for serving 3D Models.

      59 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    18. Provide API to access CDN Supplemental Management Portal

      API is needed to add new rules (e.g. Country Filtering, Token Auth, etc.) for newly added content.

      Use case: User adds new video content in CMS where he is able to block this video in some regions.

      51 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      6 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
      started  ·  Anton Kucer [MSFT] responded

      Work has started on both moving capabilities that are only available in the CDN Supplemental Portal (e.g. rules engine) into the Azure Portal and also providing API’s to support all of these features. This work will be done in multiple phases over the next several months.

    19. Front Door - Allow choice of TLS version

      Currently Front Door supports HTTPS and custom HTTPS, but I can't choose which version of TLS used - I'd like to remove TLS 1.0 from the list of supported versions so that I'm not using known insecure versions.

      44 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
    20. Test Azure CDN Rule Engine before sending for approval

      At this moment, you cann't test Azure CDN Rule Engine before sending for approval, approval of new Rules takes up to 4 hours. Which make things very difficult.

      43 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      4 comments  ·  Content Delivery Network  ·  Flag idea as inappropriate…  ·  Admin →
      planned  ·  Anton Kucer [MSFT] responded

      Rule approval is currently automatic with no delay. We will follow up on having the 4 hour approval message you see in the CDN supplemental portal updated to remove this confusion. While approval is automatic it can currently take 90 minutes for updates to propagate to all CDN POPs. Work is under way to significantly reduce this to a much lower value in the next few months.

    ← Previous 1 3 4 5
    • Don't see your idea?

    Feedback and Knowledge Base