How can we improve Azure Networking?

Network Watcher Topology should get information for resources in different resource group than VNET

The preview of Network Watcher has a Topology feature which draws objects connected to a specific VNET, which is great. But, I noted that for a full topology, ALL resources need to be on the same Resource Group than the VNET chosen. That doesn't make sense, because is pretty common to have VMs and NICs on different RGs. Would be great if you choose a RG and a VNET as a starting point, and Topology feature gather all other resources interconnected independently of their RGs.

71 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
You have left! (?) (thinking…)
Alessandro shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

9 comments

Sign in
(thinking…)
Sign in with: Microsoft
Signed in as (Sign out)
Submitting...
  • JohnC commented  ·   ·  Flag as inappropriate

    Hello Microsoft, thank you for the update and great news that you plan to implement this. Now the question is, when? Can you estimate what quarter or half of what year this will land in preview? Your users are crying out for this!

  • JohnC commented  ·   ·  Flag as inappropriate

    Hello Microsoft, what is the status of this planned enhancement? You last responded 1 year ago and the community is unanimous that the topology diagram is essentially useless as it stands. We need this!

  • Anonymous commented  ·   ·  Flag as inappropriate

    This is a must have. Vnet is never in same RG as the resources being monitored.

  • Mike commented  ·   ·  Flag as inappropriate

    This is crazy. What enterprise customer has PCs and VNETs in the same RG?

  • Andy Ball commented  ·   ·  Flag as inappropriate

    voted - would say having dedicated RG for VNets / Network artifacts is a pretty de-facto standard in corporate environments

  • Douglas James Boyd commented  ·   ·  Flag as inappropriate

    we always place network related services in a dedicated Resource Group, as they generally have a different lifecycle and RBAC requirements

Feedback and Knowledge Base