Manage your network topology for cloud voice features in Microsoft Teams
If your organization is deploying Location-Based Routing for Direct Routing or dynamic emergency calling, you must configure network settings for use with these cloud voice features in Microsoft Teams.
Network settings are used to determine the location of a Teams client. The settings include network regions, network sites, subnets, and trusted IP addresses. Depending on the cloud voice feature and capability that you're deploying, you configure some or all of these settings. To learn more about these terms, see Network settings for cloud voice features.
You configure network settings on the Network topology page of the Microsoft Teams admin center or by using Windows PowerShell.
Note that it can take some time (up to four hours) for some changes to network settings (such as a new address, network identifier, and so on) to propagate and be available to Teams clients.
Note
Network configuration data may be used across Microsoft 365 services to provide additional services your organization has subscribed to.
Configure network settings in the Microsoft Teams admin center
You define network regions, network sites, and subnets on the Network sites tab of the Network topology page.
You can create or modify a network site, associate a site with a network region, associate a subnet to the site, turn on Location-Based Routing, and assign emergency policies to the site. You can also add network regions that can be used globally for all sites.
Add and configure a network site
In the left navigation of the Microsoft Teams admin center, go to Locations > Network topology, and then select the Network sites tab.
Select Add, and then enter a name and description for the site.
To associate the site with a network region, select Add network region, select an existing region or select Add to add a region, and then select Link.
To enable Location-Based Routing for the site, turn on Location based routing.
To assign emergency services policies to the site, do one or both of the following:
If your organization uses Calling Plans, Operator Connect, or Direct Routing, under Emergency calling policy, select the policy that you want.
If your organization deployed Direct Routing, under Emergency call routing policy, select the policy that you want.
(Optional) If you want to change the behavior for clients in this site, you can use the network roaming policy. Under Network roaming policy, select the policy that you want. For more information, see Manage audio and video settings for clients.
To associate a subnet to the site, under Subnets, select Add subnets. Specify the IP version, IP address, network range, add a description, and then select Apply. Each subnet must be associated with a specific site.
Select Save.
Modify a network site
In the left navigation of the Microsoft Teams admin center, go to Locations > Network topology, and then select the Network sites tab.
Select the site by clicking to the left of the site name, and then select Edit.
Make the changes that you want, and then select Save.
Manage external trusted IP addresses
You manage external trusted IP addresses on the Trusted IPs tab on the Network topology page of the Microsoft Teams admin center. You can add an unlimited number of external trusted IP addresses.
Add a trusted IP address
In the left navigation of the Microsoft Teams admin center, go to Locations > Network topology, and then select the Trusted IPs tab.
Select Add.
In the Add trusted IP address pane, specify the IP version, IP address, network range, add a description, and then select Apply.
Edit a trusted IP address
In the left navigation of the Microsoft Teams admin center, go to Locations > Network topology, and then select the Trusted IPs tab.
Select the IP address by clicking to the left of it, and then select Edit.
In the Edit trusted IP address pane, make the changes that you want, and then select Apply.
Configure network settings using PowerShell
To complete the steps in this section, you need some familiarity with PowerShell cmdlets. To learn more, see Teams PowerShell Overview.
Define network regions
To define network regions, use the New-CsTenantNetworkRegion cmdlet. Note that the RegionID parameter is a logical name that represents the geography of the region and has no dependencies or restrictions; the CentralSite <site ID> parameter is optional.
New-CsTenantNetworkRegion -NetworkRegionID <region ID>
This example creates a network region named India:
New-CsTenantNetworkRegion -NetworkRegionID "India"
For more information, see Set-CsTenantNetworkRegion.
Define network sites
To define network sites, use the New-CsTenantNetworkSite cmdlet. Each network site must be associated with a network region.
New-CsTenantNetworkSite -NetworkSiteID <site ID> -NetworkRegionID <region ID>
The following example creates two new network sites, Delhi and Hyderabad, in the India region:
New-CsTenantNetworkSite -NetworkSiteID "Delhi" -NetworkRegionID "India"
New-CsTenantNetworkSite -NetworkSiteID "Hyderabad" -NetworkRegionID "India"
The following table shows the network sites defined in this example:
| Site 1 | Site 2 | |
|---|---|---|
| Site ID | Site 1 (Delhi) | Site 2 (Hyderabad) |
| Region ID | Region 1 (India) | Region 1 (India) |
For more information, see Set-CsTenantNetworkRegion.
Define network subnets
To define network subnets and associate them to network sites, use the New-CsTenantNetworkSubnet cmdlet. You can associate each network subnet with one site only.
New-CsTenantNetworkSubnet -SubnetID <Subnet IP address> -MaskBits <Subnet bitmask> -NetworkSiteID <site ID>
The following example creates an association between subnet 192.168.0.0 and the Delhi network site, and between subnet 2001:4898:e8:25:844e:926f:85ad:dd8e and the Hyderabad network site:
New-CsTenantNetworkSubnet -SubnetID "192.168.0.0" -MaskBits "24" -NetworkSiteID "Delhi"
New-CsTenantNetworkSubnet -SubnetID "2001:4898:e8:25:844e:926f:85ad:dd8e" -MaskBits "120" -NetworkSiteID "Hyderabad"
The following table shows the subnets defined in this example:
| Site 1 | Site 2 | |
|---|---|---|
| Subnet ID | 192.168.0.0 | 2001:4898:e8:25:844e:926f:85ad:dd8e |
| Mask | 24 | 120 |
| Site ID | Site (Delhi) | Site 2 (Hyderabad) |
For multiple subnets, you can import a CSV file by using a script such as the following:
Import-CSV C:\subnet.csv | foreach {New-CsTenantNetworkSubnet –SubnetID $_.Identity -MaskBits $_.Mask -NetworkSiteID $_.SiteID}
In this example, the CSV file looks like the following:
Identity, Mask, SiteID
172.11.12.0, 24, Redmond
172.11.13.0, 24, Chicago
172.11.14.0, 25, Vancouver
172.11.15.0, 28, Paris
For more information, see Set-CsTenantNetworkSubnet.
Define external subnets (external trusted IP addresses)
To define external subnets and assign them to the tenant, use the New-CsTenantTrustedIPAddress cmdlet. You can define an unlimited number of external subnets for a tenant.
New-CsTenantTrustedIPAddress -IPAddress <External IP address> -MaskBits <Subnet bitmask> -Description <description>
For example:
New-CsTenantTrustedIPAddress -IPAddress 198.51.100.0 -MaskBits 30 -Description "Contoso address"
For more information, see Set-CsTenantTrustedIPAddress.
Enable network roaming policies
Once you configure your network roaming policies, you need to enable Network configuration lookup* within each of your Meeting Policies in the Teams admin center under Meetings > Meeting Policies.
You can either edit the global policy or create a new policy and assign the policy to specific users.