Non-overlapping address spaces
In the following image, three virtual networks have been created in Azure.
Upon the successful import of the data into Address Manager, a new configuration is created in Address Manager with the name of the Resource Group defined in Azure.
The virtual networks are imported to IPv4 blocks under the IP Space tab in the Address Manager user interface. The name of the block corresponds to the virtual network name in Azure and indicates whether the virtual network is public or private.
The virtual networks are also imported to IPv6 blocks under the IP Space tab in the Address Manager user interface. The name of the block corresponds to the virtual network name in Azure and indicates whether the virtual network is public or private.
Overlapping address spaces
In the following image, two private virtual networks have been created in Azure.
In this example, vnet-2 and vnet-3 have address spaces. The 10.0.0.0/16 address space is overlapping in the two networks.
When the virtual network information is imported in Address Manager, two configurations are created for the overlapping address spaces.
The virtual networks are imported to IPv4 blocks under the IP Space tab in the Address Manager user interface. The name of the block corresponds to the virtual network name in Azure and indicates whether the virtual network is public or private within each configuration.