Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to: Microsoft Teams
The Teams Locations and Networks usage report in the Microsoft Teams admin center gives you insight into client requests for location information from the Network Configuration Service (NCS). This information can be useful in understanding whether network topology as delivered by Teams clients is matching with the locations configured in the service.
Both IPv4 and IPv6 clients are supported.
The Network Site tab shows the requests coming from clients for matching subnet information to network sites that deliver emergency calling policies and network sites.
The Network Identifier tab shows the requests coming from clients for matching Wifi Access Point, Subnet, Switch or Port information with emergency addresses.
The Trusted IP address tab shows the requests coming from clients for matching their external IP address with a trusted IP address record to determine whether the end-user was on the company premises or working remotely.
View the Locations and Networks report
In the left navigation of the Microsoft Teams admin center, click Analytics & reports > Usage reports. On the View reports tab, under Report, select Networks and Locations.
Under Date range, select a predefined range of 7 or 28 days and then select Run report.
Interpret the report
Network Site
The table gives you a breakdown of the Match and Not Match event groupings for Network Site acquisition. Here’s the information included in the report.
| Column Name | Description |
|---|---|
| Reason | Whether the grouping represents a match or not match. |
| Count | The quantity of events for this grouping. |
| IP Version | Whether the Subnet ID is IPv4 or IPv6. |
| Subnet ID | Subnet ID of the matching records. |
| Mask Bits | Quantity of subnet mask bits. |
| Network Site ID | The Network Site ID record containing the matched subnet. |
| Teams ECRP | The Teams Emergency Call Routing Policy associated with the Network Site. |
| Teams ECP | The Teams Emergency Calling Policy associated with the Network Site. |
Network Identifier
The table gives you a breakdown of the Match and Not Match event groupings for Location acquisition. Here’s the information included in the report.
| Column Name | Description |
|---|---|
| Reason | Whether the grouping represents a match or not match. |
| Count | The quantity of events for this grouping. |
| IP | IP address of records for this grouping. |
| IP version | Whether the IP address is IPv4 or IPv6. |
| Chassis ID | Ethernet switch chassis ID for LLDP matching. |
| BSSID | Wireless access point’s BSSID. |
| Port ID | Ethernet switch port ID for LLDP matching. |
| Matched Network Type | Refers to the network type that was used for matching.
|
| Matching Identity | Matched network device detail. |
| Location ID | Specific location acquired from matched network device. |
Trusted IP address
The table gives you a breakdown of the public IP addresses used by clients to access Microsoft Teams services and matching with a trusted IP address. Here’s the information included in the report.
| Column Name | Description |
|---|---|
| Reason | Whether the grouping represents a match or not match. |
| Count | The quantity of events for this grouping. |
| IP Version | Whether the public IP is IPv4 or IPv6. |
| Public IP | Public IP address of records for this grouping. |
| Trusted IP Address | For matching records, the trusted IP address. |
| Mask Bits | Quantity of mask bits for the trusted IP address. |
Related Articles
Network settings for cloud voice features