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.

    How can we improve Azure Networking?

    You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

    There are two ways to get more votes:

    • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
    • You can remove your votes from an open idea you support.
    • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
    (thinking…)

    Enter your idea and we'll search to see if someone has already suggested it.

    If a similar idea already exists, you can support and comment on it.

    If it doesn't exist, you can post your idea so others can support it.

    Enter your idea and we'll search to see if someone has already suggested it.

    • Hot ideas
    • Top ideas
    • New ideas
    • My feedback
    1. Support IPv6 Throughout the Azure Platform

      IPv6 has been a standard for years and ISPs are starting to roll out native IPv6 stacks to consumers. The time is now to support IPv6.

      1,553 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      65 comments  ·  IPv6  ·  Flag idea as inappropriate…  ·  Admin →

      IPv6 in Azure VNET is currently previewing globally- in ALL Azure Public cloud regions.

      Announcement (Service Update): https://azure.microsoft.com/en-us/updates/public-preview-microsoft-adds-full-ipv6-support-for-azure-vnets/

      Links to Documentation & Samples
      Full documentation including sample scripts is available here: https://aka.ms/IPv6ForAzureVNETdoc

      A sample JSON template is posted in the quickstart repository: https://azure.microsoft.com/en-us/resources/templates/ipv6-in-vnet/

    2. Make all services available with IPv6 addresses.

      IPv4 addresses are running out and Azure has had a lot of problems with this, resolved by buying IPv4 address pools at a significant cost.
      Some users and cloud deployments only require connectivity with on premises networks (either IPv4 or IPv6, not both).
      Make IPv6 available for all services and allow the option of choosing what type of addresses are required (IPv4+IPv6 or IPv6 only).
      Also, consider:
      ● Giving each cloud service a /60 (or bigger) instead of a /64;
      ● Making IPv6 addresses static, since pool depletion is no longer an issue.

      49 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  IPv6  ·  Flag idea as inappropriate…  ·  Admin →
    3. Allow IPv6 VIPs - Charge for *blocks of* IPv6 addreses

      It would be nice if we could purchase elastic IPv6 blocks of IPs, then when setting up an endpoint for a VM we could select the specific IP from the block for the endpoint.

      47 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  IPv6  ·  Flag idea as inappropriate…  ·  Admin →
    4. IPv6 should be default

      It's 2019. Globally routable IPv6 should be on by default, not some sort of advanced command-line only kludge requiring twiddling with load balancers and NAT the way it is now on Azure. See linode for simple and effective.

      7 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  IPv6  ·  Flag idea as inappropriate…  ·  Admin →
    5. Support for multiple nics with ipv6

      Currently there is no support for ipv6 when the machine has multiple NICs. This blocks the need to have an ipv6 loadbalancer.

      7 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  IPv6  ·  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

    6. IPv6 support must be consistent and easy

      IPv6 was designed for the minimum configuration and maximum flexibility. No NAT, flexible load balancing.

      It's 2019 here but IPv6 support in Azure leaves much to be desired.

      Specifically, do you want us to "request an IPv6 address" and "assign to the load balancer"? Really?

      The main principle of IPv6 is to issue the minimum of /64 block.

      The block must be assigned to the LB (router) and the prefix along with RDNSS must be announced using multicast.

      VMs must have global IPv6 connectivity.
      LB must have a unicast address.

      Azure is intended for the service and application development, not…

      4 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  IPv6  ·  Flag idea as inappropriate…  ·  Admin →
    7. Support ipv6 for microsoft peering and receive IPv4 subnets over it

      Allow users to create microsoft peering using IPv6 and receive/advertise IPv4 subnets over it. This will save some IPv4 subnets for us.

      3 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      unplanned  ·  1 comment  ·  IPv6  ·  Flag idea as inappropriate…  ·  Admin →
    8. 3 votes
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  IPv6  ·  Flag idea as inappropriate…  ·  Admin →
    9. add support of '--idle-timeout' for "az network lb rule update -g lwm2m6 --lb-name lblwm2m6 --idle-timeout 30 -n IPv6Tcp80_8080"

      Want to configure '--idle-timeout':

      az network lb rule update -g lwm2m6 --lb-name lblwm2m6 --idle-timeout 30 -n IPv6Tcp80_8080

      1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      0 comments  ·  IPv6  ·  Flag idea as inappropriate…  ·  Admin →
    10. 1 vote
      Vote
      Sign in
      (thinking…)
      Sign in with: Microsoft
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      3 comments  ·  IPv6  ·  Flag idea as inappropriate…  ·  Admin →

      The suggestion seems to be a question about IPv6 clients accessing an IPv4-only VM. In Azure, IPv6 traffic from the internet is plumbed directly to native IPv6 endpoints on VMs. There are many advantages to this approach but one disadvantage is the VMs must have IPv6 endpoints and the applications must be IPv6-aware. In the example below, I would guess the web server has not been configured to monitor both the IPv4 and IPv6 endpoints on the VM but that is really a support question.
      It is possible to translate between IPv4 and IPv6 (NAT64) which is not currently supported in Azure so we’ll take this suggestion as a vote for NAT64 support.

    • Don't see your idea?

    Feedback and Knowledge Base