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. is it only IPv6 clients communicate via IPv6 LB to only IPv6 Virtual machines behind that LB and not IPv6 clients to IPv4 VM via IPv6LB

      IPV6

      8 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback
      Signed in as (Sign out)
      Close
      Close
      You have left! (?) (thinking…)
      3 comments  ·  IPv6  ·  Flag idea as inappropriate…  ·  Admin →
      under review  ·  AdminAzure Networking Team (Product Manager, Microsoft Azure) responded

      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.

    2. Please support configurable public IPv6 Idle Timeout for feature parity with public IPv4 Idle Timeout

      3 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback
      Signed in as (Sign out)
      Close
      Close
      You have left! (?) (thinking…)
      0 comments  ·  IPv6  ·  Flag idea as inappropriate…  ·  Admin →

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

      We're glad you're here

      Please sign in to leave feedback
      Signed in as (Sign out)
      Close
      Close
      You have left! (?) (thinking…)
      0 comments  ·  IPv6  ·  Flag idea as inappropriate…  ·  Admin →
    • Don't see your idea?

    Networking

    Categories

    Feedback and Knowledge Base

    (thinking…)
    Hosted by UserVoice