Azure Network Watcher resources not visible while created from Azure Portal

Michal Furmankiewicz 21 Reputation points
2020-11-01T09:23:35.077+00:00

When you create NetworkWatcher from Portal you see nothing in the NetworkWatcher RG, but when You use Terraform everything is clear and visible in one group with FlowLogs, Network Watcher objects and whole configuration. Whole easier.

Azure Network Watcher
Azure Network Watcher
An Azure service that is used to monitor, diagnose, and gain insights into network performance and health.
169 questions
{count} votes

Accepted answer
  1. GitaraniSharma-MSFT 49,591 Reputation points Microsoft Employee
    2020-11-02T05:10:54.08+00:00

    Hello @Michal Furmankiewicz ,

    Welcome to Microsoft Q&A Platform. Thanks for posting your query.

    Azure Network Watcher resources should be visible in the NetworkWatcherRG even when they are enabled via Azure portal. I can see the same in my subscription:
    36761-networkwatcherrg.jpg

    When you create or update a virtual network in your subscription, Network Watcher will be enabled automatically in your Virtual Network's region.
    When you enable Network Watcher using the portal, the name of the Network Watcher instance is automatically set to NetworkWatcher_region_name where region_name corresponds to the Azure region where the instance is enabled. For example, a Network Watcher enabled in the West Central US region is named NetworkWatcher_westcentralus.
    The Network Watcher instance is automatically created in a resource group named NetworkWatcherRG. The resource group is created if it does not already exist.

    If you wish to customize the name of a Network Watcher instance and the resource group it's placed into, you can use PowerShell, the Azure CLI, the REST API, or ARMClient methods. In each option, the resource group must exist before you create a Network Watcher in it.

    Please refer : https://video2.skills-academy.com/en-us/azure/network-watcher/network-watcher-create

    Could you please check the subscription in which the NetworkWatcherRG is deployed in and if you are looking at the right one by checking the subscription ID in the Overview tab of NetworkWatcherRG? If multiple subscriptions are selected in the your Azure portal directory, you will be able to see all the NetworkWatcherRG deployed in all the selected subscriptions.

    If you are checking Network Watcher resource itself, make sure that in the overview tab, the correct subscription from the dropdown is selected.

    You could also try to disable the resources, delete the resource group and recreate & re-enable the Network Watcher via Azure portal to confirm if there is an issue in your case.

    Hope this helps!

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

    ----------------------------------------------------------------------------------------------------------------

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Rana Banerjee 1 Reputation point
    2020-11-01T10:40:08.037+00:00

    I think, once you delete / disable Network Watcher, you will need to contact support to enable it.


  2. Varadh Raj 1 Reputation point
    2021-03-06T06:02:10.857+00:00

    I had similar issue. I went to the overview table and enabled the network watcher for my region which is eastus. You can enable it by clicking the 3 dot elipsis. After doing this I see that the resource group and vnet is populated in the topology blade.74988-network-watcher.png

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.