Azure Network Watcher Reviews

We use Azure Network Watcher when troubleshooting VPN connections to know whether the ports are enabled. By default, architecture will be available at the backend, so Azure Network Watcher will show you how these units and all other components connect.

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.

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 have one year of experience with Azure Network Watcher.

For now, I can't comment on how stable Azure Network Watcher is because I still need more exposure to it, stability-wise.

Azure Network Watcher has good scalability.

My rating for the technical support for Azure Network Watcher is seven out of ten because it needs improvement.

Neutral

Setting up Azure Network Watcher is straightforward because whenever you deploy Azure VNet, you also get the Azure Network Watcher by default.

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

I have a little experience with Azure Network Watcher but more experience with infrastructure-related solutions such as Azure Network Watcher. I also have experience with application gateways, load balancers, firewalls, open gateways, etc.

Right now, a limited amount of people use Azure Network Watcher within the company. The tool comes with VNet by default, but most people here don't know that the Azure Network Watcher is available, so it's a tool that needs to be leveraged more. It has a few limitations when compared to other tools. Users who are very new to Azure wouldn't be aware of the existence of Azure Network Watcher compared to people used to Azure.

My advice to others looking into using Azure Network Watcher is to go for it, as you'll have the tool by default when you're subscribed to Azure VNet.

I'm rating Azure Network Watcher as nine out of ten overall.

My company implements Azure Network Watcher and other Azure infrastructure for customers.

We use this solution for traffic monitoring. For example, when you want to see requests or inspect packets within your cloud network, to see how the traffic is flowing, or how the traffic and the packets are being transmitted from one host to another, and from one source or resource to another.

To connect a virtual machine or if you want to monitor the communication between a VM and certain endpoints, we have to specify the endpoints to fully qualify the domain name. It determines how the traffic is flowing.

At the end of the day, it should show you this map or graph resource about your current setup, on how traffic is flowing within your network or your environment.

This will help the company or the administrator, by helping them see how the traffic moves, to make sure that no entities are having any communication issues or different endpoints with task issues. It can help them also spot which endpoints should not be communicating to others. This is the value of the Network Watcher.

I like that it delivers. It does the job.

It provides good visibility.

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 have used it or known about it for between four and five years. I rarely use it, but I know it pretty well.

Azure itself is pretty stable, but It depends on the different resources on Azure. For example, if the resources on Azure are not stable, then it would become unstable as well.

It's not a server that scales in a way that, when the traffic comes or there is heavy traffic or loads, it scales. You just monitor the traffic within your environment. I don't see how scalability applies.

I have not had to contact technical support regarding Network Watcher.

It's not that is complex, however, for the sake of what it does, yes, I would say it's complex.

It could be a lot easier. It could be a much simpler experience, especially when you can set up a whole infrastructure with a couple of clicks. I don't see why you have to perform so many steps or very specific steps with Network Watcher.

I don't remember the pricing.

I would rate Azure Network Watcher a six out of ten.

Network Watcher allows you to see the logs to see what's going in and what's going out. You have got to set it up to see that, however, I haven't played much with it. That's why I was looking for something more granular, something that I'm more used to, like the FortiGate Firewall.

I've used it to get some logs and see what's going on to the network, however, that's about it.

The solution is stable.

Overall, the solution seems to be pretty good. 

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

I've used the solution for maybe a year or so. I haven't used it for that long just yet.

The solution is stable. There are no bugs or glitches and it doesn't crash or freeze. It's reliable. 

I also use Fortinet products.

I cannot recall what the initial setup was like. I cannot speak to how easy or difficult it was. 

I'm currently looking at FortiGate Firewall, which I have a better understanding of and is much more granular.

We're a Microsoft partner. 

I'd rate the solution at an eight out of ten.