Azure, Networking ExpressRoute
Azure ExpressRoute Overview
ExpressRoute enables you to extend the campus network into the Microsoft cloud over a private connection facilitated by a connectivity provider. This connection works like a split tunnel VPN. Traffic bound for campus does not go over the public Internet.
When using ExpressRoute, a virtual network is allocated by the TechServices Networking group on the campus private IP space and peered to your Azure subscription (default of 251 IPs in vnet with a 32 node subnet). You will then be able to use the new virtual network when configuring new servers. Azure can dynamically assign IPs from the subnet or you can manually assign dedicated IPs. Traffic destined for campus IP space will traverse the ExpressRoute. Traffic destined for the Internet will go directly out.
By default, the virtual network will use Azure DNS which should be fine for most use cases. If you need to resolve Active Directory computer names you may configure the IP addresses of the Azure based UOFI domain controllers (10.232.1.8 and 10.232.1.9) as your DNS IPs for the entire virtual network or virtual machine.
The ExpressRoute connection is located in Chicago, so the Azure Virtual Network (VNET) will be created in the North Central US (Chicago) region to ensure the best performance. Be sure to create any resources that need to use this network in that region.
The University covers the monthly costs for ExpressRoute and your subscription will only be charged for the data traversing the VNet at about $.01 per gigabyte.
To request an ExpressRoute network, send an email to email@example.com with the following information:
- Azure Subscription Name
- Description of purpose: something like "unit name Azure VNet"
- Desired network name, should be listed in the form of: azure-[shortname]-vnet
- Primary contact NETIDs
- Backup contact NETIDs
- Administrative contact NETIDs