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: 
Meetings 
Webinars Town halls
As an admin, it’s important to ensure that your users have a reliable collaboration experience for their Teams meetings. The best practice configurations dashboard for Microsoft Teams meetings helps you manage and monitor your environment for seamless collaboration. This dashboard provides you with best practice configurations, the effect of your current settings, and actions you can take to follow Microsoft’s recommendations. The dashboard highlights locations that don’t follow Microsoft's recommended best practices. When you follow recommended actions, the trend of locations not adhering to best practices is tracked to help monitor progress. All monitored areas are evaluated over a period of seven days.
Access the best practice configurations dashboard
To access the best practice configuration dashboard, follow these steps:
Go to the Teams admin center.
Expand Meetings from the navigation pane.
Under Meetings, select Best practice configurations.
The Summary widget displays the number of best practices that need action and the number without issues.
The Best practice configurations table provides statuses and insights for the following best practices:
- Enable the correct ports and protocols
- Update outdated Teams clients
- Implement split tunneling for VPNs
To view a detailed dashboard with recommendation, select a best practice from a row in this table. A list of IP addresses is shown for each city, displaying the extent to which each location follows best practices. You can use the name of the city, country/region, or the IP address to search and filter for locations. You can also export the dashboard's table in a CSV file that you can share.
Interpret the dashboards
The following sections provide details on the information in each best practice configuration's dashboard. Each dashboard is grouped by countries/regions, cities, and public IP addresses to identify systemic issues affecting your organization. These broader categories allow efficient detection and resolution of widespread problems impacting multiple users within a specific region or network segment, quickly identifying patterns and trends that indicate underlying issues, instead of trying to pinpoint every individual affected user.
Update outdated Teams clients
For the best meeting experience, your users should always use the latest version of Teams. The media streams in this dashboard show when Windows and Mac users are on a client build that's more than three months old, which can negatively affect meeting quality. The outdated Teams clients dashboard monitors desktop clients (Windows and Mac) across the organization and highlights the locations most impacted by outdated Teams clients. To learn more about Teams updates, see Why it's important to keep Teams updated.
To view outdated Teams clients, select Update outdated client versions in the Best practice configurations table.
| Callout | Description |
|---|---|
| 1 | Client versions trend - Trend of cities with supported and outdated Teams clients. |
| 2 | Recommended action - Actions you should take to meet the recommended best practice configurations. |
| 3 | Regions with out-of-date clients - Visual map that includes a date for when this dashboard was generated and a count of cities with outdated clients. You can also search by country/city/region. |
| 4 | The table provides the following data:
|
| 5 | You can use these buttons to:
|
Enable the correct ports and protocols
The media streams in the Enable the correct ports and protocols dashboard reflect Teams media communications conducted over Transmission Control Protocol (TCP) instead of User Datagram Protocol (UDP). This dashboard highlights locations that have a high proportion of streams using TCP.
You should open UDP ports on both the network and client firewalls to Microsoft Teams services to avoid any impact on meeting and call quality. UDP is the preferred network protocol for media streams and high rates of TCP usage can negatively affect the Teams user experience. To learn more about UDP ports and client firewalls, see Microsoft 365 URLs and IP address ranges.
To view ports and protocols, select Enable the correct ports and protocols in the Best practice configurations table.
| Callout | Description |
|---|---|
| 1 | Network traffic trend - Trend of cities with TCP and UDP traffic. |
| 2 | Recommended action - Actions you should take to meet the recommended best practice configurations. |
| 3 | Regions with TCP traffic - Visual map that includes a date for when this dashboard was generated and a count of cities with TCP and UDP traffic. You can also search by country/city/region. |
| 4 | The table provides the following data:
|
| 5 | You can use these buttons to:
|
Address DNS resolution failures
This dashboard monitors and highlights the locations most affected by Domain Name System (DNS) resolution failures, offering clear visibility into impacted cities and subnets. These insights help you prioritize out where to focus first, so you can fix issues faster and maintain media quality and service performance. To ensure reliable connectivity, you should ensure that DNS resolution occurs close to the network egress point. This setup enhances fault tolerance, reduces reliance on external DNS servers, and improves the overall stability and efficiency of Teams. To learn more about egress network connections, see Microsoft 365 network connectivity principles.
To view DNS resolution failures, select Address DNS resolution failures in the Best practice configurations table.
The following details are available:
- Cities and regions impacted
- Public IPs (reflexive) that have high proportion of streams having DNS resolution failures
- Number and percentage of streams originating from the DNS resolution failure
Bypass local proxy
This dashboard monitors locations where a high number of streams are routed through a proxy. To improve performance, it's best to keep the connection between the user's device and Microsoft Teams services as short and direct as possible. When too much traffic flows through a proxy server, the server can get overwhelmed—leading to delays, poor media quality, and a frustrating experience. To learn more about local proxies, see Proxy servers for Teams and Skype for Business Online.
To view local proxies, select Bypass local proxy in the Best practice configurations table.
The following details are available:
- Cities and regions impacted
- Public IPs (reflexive) that have a high proportion of streams routed over proxy.
- Percentage and volume of streams routed over proxy.
Bypass cloud proxy
This dashboard highlights locations where a large number of streams are routed through cloud-based proxies. These proxies can introduce latency and packet loss, which might affect call quality. To improve performance, we recommend bypassing cloud proxy configurations for Teams traffic, including TLS/SSL inspection. Teams media traffic is already encrypted, so you don't need proxies for security. To learn more about cloud proxies, see Microsoft 365 network connectivity principles.
To view cloud based proxies, select Bypass cloud proxy in the Best practice configurations table.
The following details are available:
- Cities and regions impacted
- Public IPs (reflexive) that have a high proportion of streams routed over proxy
- Percentage and volume of streams routed over proxy.