Network watcher not working on FTD VM

Nvm mind. We thought it was because we had the windows agent instead of the Linux agent. But, we get the same error it is not installed when using the Linux agent.

Hi @Jess,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

1. As we can see above you have mentioned that you already uninstalled and re-installed the extension and it is not worked. Could you check version of the extension which is latest or not. If not, please upgrade it to latest by following the document: https://video2.skills-academy.com/en-us/azure/network-watcher/network-watcher-agent-update?tabs=windows#latest-version
2. Also check the agent status & if the version is lower than latest version, upgrade the agent. Refer the document: https://video2.skills-academy.com/en-us/troubleshoot/azure/virtual-machines/windows/windows-azure-guest-agent#step-2-check-whether-guest-agent-is-ready
3. For future if you want, you can enable auto-upgrade for extension by following the document: https://video2.skills-academy.com/en-us/azure/virtual-machines/automatic-extension-upgrade?tabs=RestAPI1%2CRestAPI2#enable-automatic-extension-upgrade

Kindly let us know if the above helps or you need further assistance on this issue.

Thanks,

Sai Prasanna.

It seems like there is a conflict between the Azure Network Watcher and the Cisco FTD firewall VM in your setup. Here are a few steps you can try to resolve the issue:

1. Check Extension Installation Logs • After reinstalling the Network Watcher extension, check the logs to ensure it installed correctly. • You can access the VM’s logs via Azure’s portal:
   1. Go to the VM resource.
   2. In the “Support + Troubleshooting” section, click on “Boot diagnostics” and “Serial log”.
   3. Look for any specific errors related to the extension installation.
2. Verify the Installed Extensions • Confirm the extension is installed correctly by listing the extensions via Azure CLI or PowerShell: • Azure CLI:

az vm extension list --resource-group <Resource-Group-Name> --vm-name <VM-Name>

•	PowerShell:

Get-AzVMExtension -ResourceGroupName <Resource-Group-Name> -VMName <VM-Name>

•	Ensure that NetworkWatcherAgent (not just AzureNetworkWatcherExtension) appears in the list.

3. Manually Install the Network Watcher Agent • If the NetworkWatcherAgent isn’t appearing correctly, you can try installing it manually via the Azure CLI:

az vm extension set \

--resource-group <Resource-Group-Name> \

--vm-name <VM-Name> \

--name NetworkWatcherAgentLinux \

--publisher Microsoft.Azure.NetworkWatcher

•	If your Cisco FTD VM is running Windows, replace NetworkWatcherAgentLinux with NetworkWatcherAgentWindows.

4. Check for Conflicts with Cisco FTD • Some services or firewall settings in Cisco FTD might block communication required by the Network Watcher agent. Check the following: • Ensure that outbound traffic to Azure monitoring services is not being blocked by firewall rules. • Ensure that the required network security group (NSG) rules are not preventing the Azure agent from communicating.
5. Network Watcher Region • Ensure the VM is in a region where Network Watcher is enabled. If it isn’t enabled in that region, the connection monitor tool will not work. • You can enable Network Watcher for a region with the following Azure CLI command:

az network watcher configure --locations <region> --enabled true

6. Restart VM • After reinstalling the extension, it may help to restart the VM to ensure everything is properly refreshed.

If my answer is helpful to you, you can adopt it, thank you！

Hi @Jess,

Hope you are having a good day.

Following up to see if the above suggestion was helpful. And, if you have any further query do let us know.

We are happy to assist you.

Thanks.

Hi @Jess,

Hope you are having a good day.

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, please respond with more details and we will try to help.

Thanks.