Azure Network Watcher Reviews

Our use case includes logs, mainly. 

I like the visibility. 

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

I have been using this solution for two years. 

It is stable. It is good. 

It is scalable enough for our company. 

The customer service and support are quite good.

Neutral

I used AWS, Azure, and SAP.

The initial setup is quite challenging until you get to know what you need to do.

It took us a month to deploy it.

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

It's important to have visibility. Overall, I would rate the solution a seven out of ten.

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.

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.