Azure Network Watcher vs NetCrunch comparison

"The most valuable features I have found are typology, visualization, and capture."

"The solution is good for monitoring device behavior."

"The most valuable feature of Azure Network Watcher is using the gateways with the connections. The monitoring is useful for the logs and application insights into the data. The traffic filtering issues when it comes to deploying those applications are helpful."

"I like the visibility."

"What I like most about Azure Network Watcher is that it's focused more on the architecture. I also like that it has a packet capture feature that tells you how the packet travels and whether it's exiting Azure, etc."

"The most valuable feature of Azure Network Watcher is the cloud-native application firewall. It is helpful for securing databases."

"The stability is very good. I rate it a ten out of ten."

"It provides good visibility."

"Reporting on NetCrunch is pretty good. It's very similar to SolarWinds. It's just a different interface. The majority of everything there was beneficial."

"User experience could be improved."

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

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

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

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

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

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

"Lacks sufficient security features."

"I didn't care for the role-based, permission-based options, which were not the best."

"The pricing is good. It's not too expensive."

"Azure Network Watcher is a little bit expensive."

"Price-wise, I have no information on how much Azure Network Watcher costs."

"The price of the solution is reasonable."