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. Add & Support Multicast in VNET

      We have a need for VNET to support Multicast for various applications (IaaS)

      2 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      declined  ·  1 comment  ·  Virtual Network  ·  Flag idea as inappropriate…  ·  Admin →
    2. Our team has tens of developers who have MSDN account. We'd like to share same VNet which connects to our on-premise network.

      Each developer has free-tier Azure usage within their MSDN account, but they can not start virtual machines in the on-premise-connected VNet using the free tier.

      To start virtual machines with their account and to access them from on-premise network, It seems that they have to make their own VNet and connect it to the on-premise-connected VNet. It is not convenient.

      I believe that If the owner of the on-premise-connected VNet could allow other accounts to create virtual machines within the VNet, lots of developers will be happy for that.

      29 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  ·  Virtual Network  ·  Flag idea as inappropriate…  ·  Admin →
    3. Allow Multiple network interfaces on all VM sizes

      While it is great that Azure now supports multiple network interfaces, this is restricted to standard sizes above large.

      Often the requirement for multiple nics is on a machine that is a crossing point between networks, using a standard tier large VM for this type of traffic is serious overkill!

      There is a need to have a small, ideally basic tier VM that can have two nics attached.

      I realise this may be in the pipeline, since multiple nics are so new to Azure, but it would be very helpful in creating cost effective solutions on Azure if this could…

      100 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      7 comments  ·  Virtual Network  ·  Flag idea as inappropriate…  ·  Admin →
    4. Allow Virtual Machines from different subscriptions to belong to the same Virtual Network

      We have multiple subscriptions for development and testing and it would be useful if we could have Virtual Machines from those different subscriptions attached to the same Virtual Network.

      1 vote
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      1 comment  ·  Virtual Network  ·  Flag idea as inappropriate…  ·  Admin →
      declined  ·  Narayan Annamalai responded

      We will soon have ways to inter connect different VNets on the same subscription, but subscription remains to be the trust boundary for a customer, hence Vnets will have to stay within subscription scope, at least in the near term.

    5. Specify Firewall Exceptions by Host Name Resolution

      The current mechanism of specifying firewall exceptions is problematic for those without static IP addresses. Allowing permitted IP addresses to be specified by host name resolution would allow customers to use a dynamic DNS service and eliminate the need to manually update firewall rules when a new address is assigned.

      79 votes
      Vote

      We're glad you're here

      Please sign in to leave feedback

      Signed in as (Sign out)
      You have left! (?) (thinking…)
      4 comments  ·  Virtual Network  ·  Flag idea as inappropriate…  ·  Admin →

      Thank you for the suggestion. Layer 7 functionality is out of scope for NSG at this time. Please take a look at WAF options, including Application Gateway, to see if they can meet your needs. We’re also looking at ways to expose endpoints within the vnet itself.

    2 Next →
    • Don't see your idea?

    Feedback and Knowledge Base