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.134 votes
We are working on improving the capabilities of the Network Watcher Topology. This includes visualising resources across Resources Groups as well as across subscriptions, filters, handling large resource counts well and more.
Customers can expect public preview access by July 2021 latest.
For private preview access, sign up here: https://aka.ms/ARTaccess
You should consider adding a Azure Networking Traffic Simulator somewhere in Azure to provide better tooling for troubleshooting and configuring NSG firewall rules.8 votes
Provide a dashboard to help understand the Azure network topology and to visualise the NSG rules29 votes
Thank you for your suggestion. We have included this in our planning.
Can network traffic (volume, speed, etc.) be visible in blades either at network interface or network security group?
Can network traffic (volume, speed, etc.) be a tile visible in blades either at network interface or network security group or VM?7 votes
This feedback/suggestion is under review as an addition to Network Watcher.
- Don't see your idea?