An Azure virtual network (VNet) is a representation of your own network in the cloud. It is a logical isolation of the Azure cloud dedicated to your subscription. You fully control the IP address blocks, DNS settings, security policies, and route tables within this network. You need to also further segment your VNet into subnets and deploy Azure IaaS VMs to use Teradata products. Additionally, you can connect the VNet to your on-premises network or another Vnet you own on Azure cloud.
When you deploy Teradata products using a solution template, private IPs are assigned within the same VNet or VNet peering. After deploying a solution template, you have the option to create public IPs if you are connecting to the public cloud through the Internet.
When you deploy Teradata products separately, you can create a new public IP address or select an existing public IP address.
VNets are associated to a resource group which provides network boundaries for resources. A VNet is required when deploying a VM. VNets cannot span over multiple regions.