Using Network Planner - example scenario

The Network Planner tool is available in the Teams admin center. It helps you determine network requirements for your organization. This example scenario shows how you can use the tool to create sites, personas, and running reports for a company called Contoso.

Before you begin

We assume you already know your way around the Teams admin center, and you are familiar with what you need to do to prepare your network for Teams. If this is the first article you've seen on Network Planner, we recommend that you go through the following articles first.

Overview of Contoso network

Contoso has three locations:

  • Seattle Headquarters: This is the main location for Contoso. It has 1000 employees and 25 of them are calling only. The site is connected to the internet, and there is a local telephone connection (PSTN). Contoso has Direct Routing set up to be able to use the local telephone connection with Teams.
  • Kirkland Office: This branch office has 400 employees and 10 are calling only. The site uses its connection to the headquarters for both internet and phone (PSTN) traffic. This office is connected to the Seattle headquarters using a WAN connection.
  • Denver Office: This office has 250 employees and 50 are calling only. The site has its own local internet connection, but has no direct telephone connection (PSTN).

Let's get started!

Now, you need to add the three sites to your network plan. The table below summarizes the characteristics of Contoso's network locations.

Location Total number of employees Calling only employees Internet connection PSTN connection WAN link capacity Internet link capacity
Seattle HQ 1000 25 Local Internet Local PSTN using Direct Routing 200 Mbps 500 Mbps
Kirkland Office 400 10 Remote Internet through HQ Remote PSTN through HQ 200 Mbps N/A
Denver Office 250 50 Local Internet No PSTN connection N/A 150 Mbps
  1. Click your network plan in Network Planner.
  2. Select the Network sites tab and click Add a network site.

Adding a network site

  1. Using the table above, fill in the details for the Seattle HQ site. Turn on both the ExpressRoute and Connected to WAN toggles.

New site details

  1. Since the Seattle HQ site has local internet and local PSTN connections, you need to correctly specify these characteristics.

New site egress settings

  1. Click Save to complete adding the Seattle HQ site.
  2. Create the Denver site using the same process. WAN should not be enabled.
  3. Since the Kirkland site leverages the connection to Seattle HQ for both internet and PSTN connectivity, it is considered a remote site. When creating the Kirkland site, you need to specify that it is connected to WAN and select Remote for both Internet egress and PSTN egress.

Remote site egress settings