Azure Network Watcher could improve by having other built-in applications. For example, an application to log activities for in and outbound traffic.

In a future release, the solution should have better firewall settings.

The solution could use some additional components of the network culture, not only VMs. I'd like to see some additional security features because what they currently have concentrates only on the network. As we have SOC, we should also have NOC.

Azure Network Watcher needs to have better documentation and it needs to capture information accurately. 

The solution could improve by limiting the need to clarify the logs. When the clarification is minimized, it is better for everyone involved.

In a future release, it would be helpful to have a monitoring tool that can have
a pictorial representation of all the logs. This way people can understand exactly what the issues are visually.

I would like to see in the future if we can troubleshoot as a firewall because it is equipment as a network player and some diagnostics. It would be even helpful if we can improve Azure Network Watcher to have some scope to identify missing rules.

The initial setup and initial learning curve could be improved to be easier.

I don't find it that appealing.

It's not the most friendly or straightforward to set up. For me, it's not that appealing that I want to go ahead and set it up each time.

I don't see the value versus the way you have to set it up at first.

The initial setup and deployment could be improved to be simplified.

From my perspective, this is something that should be out of the box, available, and given. I don't see why there is a need to set it up. 

The experience should be there, the servers or the insights, they should be readily available out of the box, once you start setting up your environment on Azure.

The setup is a huge part of what needs to be better, as well as the view, or the graph could be improved. Microsoft has the capability to enrich it and to make it look more granular.

I would like to see a graph with simple diagrams and richer information.

I still use Wireshark and Azure Network Watcher to get the required data. My team captures the traffic from Azure Network Watcher, downloads it, then imports that traffic into Wireshark to get more details on the number of hits and replies, for example. If you can do that on Azure Network Watcher and have Wireshark built-in, that would make Azure Network Watcher better.

If Azure Network Watcher has that functionality where you won't need a third-party tool to get what you need, that would be helpful.

I'm also expecting more from Azure Network Watcher. It's more complex than knowing how the IP flows from its source to the destination. The tool also needs more open-source features, such as having some built-in Wireshark that improves monitoring for customers. Sometimes, you encounter a VPN tunnel, network, or routing issue, but finding out more about the blockage is challenging. Is it one hundred percent an Azure issue? Is it a peer issue? You don't get complete information from Azure Network Watcher, so you must use other tools and depend on your strategies to resolve a specific issue.

If more features could be added in the next release of Azure Network Watcher, specifically ones you can find on open-source tools, then that would be a plus point for the tool.

Azure is good, however, the Fortinet GUI is more intuitive and I like it more than anything else.