For example, a network security group that exists in a resource group other than MyResourceGroup, isn't shown, even if the network security group is associated to a subnet in the MyVnet virtual network. Within the same resource group and region as the myVnet virtual network.Topology information is only shown for resources that are: One subnet has a network security group associated to it. The other two subnets have a route table associated to them. The VM has one network interface attached to it and a public IP address associated to it. In the following picture, a topology is shown for a virtual network named MyVnet, in the resource group named MyResourceGroup:Īs you can see in the previous picture, the virtual network contains three subnets.
Select a subscription, the resource group of a virtual network you want to view the topology for, and then select the virtual network. The network watchers are created in a resource group named NetworkWatcherRG. If you don't have a network watcher enabled in the region that the virtual network you want to generate a topology for is in, network watchers are automatically created for you in all regions. Generating a topology requires a network watcher in the same region that the virtual network that you want to generate the topology for exists in. When Network Watcher appears in the results, select it. In the All services filter box, enter Network Watcher. On the top, left corner of the portal, select All services. Log into the Azure portal with an account that has the necessary permissions.
#NETWORK TOPOLOGY MAPPER HOW TO#
To learn how to migrate to the Az PowerShell module, see Migrate Azure PowerShell from AzureRM to Az.
To get started with the Az PowerShell module, see Install Azure PowerShell. This article uses the Azure Az PowerShell module, which is the recommended PowerShell module for interacting with Azure.
0 kommentar(er)
