Troubleshooting practice questions

A user reports poor audio quality during Teams calls. You need to identify the specific network metrics causing the issue for a specific session. Which tool should you use?

Trap 1: Microsoft 365 Admin Center Usage Reports

Usage reports provide high-level metrics on active users and feature adoption trends across the organization. These reports are designed for license optimization and administrative oversight rather than troubleshooting real-time media path issues or individual call quality metrics like jitter or packet loss.

Trap 2: Microsoft Purview Audit Logs

Audit logs track administrative actions and user events, such as file deletions or policy changes, within the Microsoft 365 environment. They do not contain media-stream telemetry, network latency data, or audio quality metrics required to diagnose specific call quality degradations or packet loss scenarios.

Trap 3: Call Quality Dashboard (CQD)

CQD is intended for managing call quality at an organizational or subnet level using aggregate data. While useful for identifying trends across large groups, it lacks the individual session detail required to isolate a single user's specific audio performance issue during a single call.

A
Microsoft 365 Admin Center Usage Reports
Why it fails: Usage reports provide high-level metrics on active users and feature adoption trends across the organization. These reports are designed for license optimization and administrative oversight rather than troubleshooting real-time media path issues or individual call quality metrics like jitter or packet loss.
B
Teams Call Analytics
Call Analytics provides detailed per-user and per-session telemetry, including network performance, device information, and client versions. This tool is specifically designed to troubleshoot individual call issues by exposing technical metadata that helps pinpoint whether the failure occurred on the local network or the internet backbone.
C
Microsoft Purview Audit Logs
Why it fails: Audit logs track administrative actions and user events, such as file deletions or policy changes, within the Microsoft 365 environment. They do not contain media-stream telemetry, network latency data, or audio quality metrics required to diagnose specific call quality degradations or packet loss scenarios.
D
Call Quality Dashboard (CQD)
Why it fails: CQD is intended for managing call quality at an organizational or subnet level using aggregate data. While useful for identifying trends across large groups, it lacks the individual session detail required to isolate a single user's specific audio performance issue during a single call.

Question 2mediummultiple choice

A user is experiencing issues with app performance in Teams. You want to view the current app permission policy assigned to this specific user. Which tool is most appropriate?

Trap 1: Microsoft 365 Security Center

The Security Center focuses on threat protection, information protection, and compliance monitoring. It is not the correct interface for viewing Teams-specific policies assigned to individual users, as it does not provide the granular user-to-policy mapping found within the dedicated Teams administration tools.

Trap 2: Microsoft Entra ID admin center

While Microsoft Entra ID manages user objects and group memberships, it does not display the specific Teams-level policies assigned to a user. These policies are managed within the Teams admin center or via PowerShell, making Microsoft Entra ID an ineffective tool for inspecting Teams policy assignments.

Trap 3: Microsoft Purview eDiscovery

Purview eDiscovery is used for legal holds and searching content within mailboxes and teams. It is not designed to manage or display configuration policies assigned to users. Using this tool to troubleshoot policy assignments would be incorrect and provide no relevant configuration data for the user.

A
Microsoft 365 Security Center
Why it fails: The Security Center focuses on threat protection, information protection, and compliance monitoring. It is not the correct interface for viewing Teams-specific policies assigned to individual users, as it does not provide the granular user-to-policy mapping found within the dedicated Teams administration tools.
B
Teams admin center
The Teams admin center allows administrators to navigate to the 'Users' tab, select a specific user, and view their assigned policies, including app permission policies. This direct approach is the standard procedure for auditing and troubleshooting policy-related issues for individual users within a Microsoft 365 tenant.
C
Microsoft Entra ID admin center
Why it fails: While Microsoft Entra ID manages user objects and group memberships, it does not display the specific Teams-level policies assigned to a user. These policies are managed within the Teams admin center or via PowerShell, making Microsoft Entra ID an ineffective tool for inspecting Teams policy assignments.
D
Microsoft Purview eDiscovery
Why it fails: Purview eDiscovery is used for legal holds and searching content within mailboxes and teams. It is not designed to manage or display configuration policies assigned to users. Using this tool to troubleshoot policy assignments would be incorrect and provide no relevant configuration data for the user.

Question 3mediummulti select

You need to monitor the overall health of the Microsoft Teams service and receive notifications about known incidents. Which TWO tools should you use? (Each correct answer presents a complete solution).

Trap 1: Teams Client Diagnostic Logs

Diagnostic logs are specific to an individual user's client behavior and local environment. They are used for deep-dive technical troubleshooting of specific software errors or crashes, but they do not provide information about the global status of the Microsoft Teams cloud service health.

Trap 2: Teams Advisor

Teams Advisor is a tool used during the initial rollout to help plan the deployment of Teams workloads like Chat, Groups, and Meetings. It creates a project plan and tracks progress, but it is not a monitoring tool for ongoing service health or incidents.

Trap 3: Teams App Store

The Teams App Store is where users and admins manage third-party and custom applications. It has no functionality related to monitoring the operational health of the Teams core service or notifying administrators about service degradations or regional outages currently affecting the tenant.

A
Teams Client Diagnostic Logs
Why it fails: Diagnostic logs are specific to an individual user's client behavior and local environment. They are used for deep-dive technical troubleshooting of specific software errors or crashes, but they do not provide information about the global status of the Microsoft Teams cloud service health.
B
Teams Advisor
Why it fails: Teams Advisor is a tool used during the initial rollout to help plan the deployment of Teams workloads like Chat, Groups, and Meetings. It creates a project plan and tracks progress, but it is not a monitoring tool for ongoing service health or incidents.
C
Service health in the Microsoft 365 Admin Center
The Service Health page is the official source for status updates on all Microsoft 365 services. It lists active incidents, advisories, and resolved issues, providing detailed information on the scope of the impact and the current progress of the engineering teams toward a fix.
D
Teams App Store
Why it fails: The Teams App Store is where users and admins manage third-party and custom applications. It has no functionality related to monitoring the operational health of the Teams core service or notifying administrators about service degradations or regional outages currently affecting the tenant.
E
Microsoft 365 Admin mobile app
The Microsoft 365 Admin mobile app allows administrators to monitor service health on the go. It can be configured to send push notifications for new incidents and status changes, making it an essential tool for staying informed about service disruptions outside of office hours.

Question 4mediummultiple choice

You are managing a fleet of Microsoft Teams Rooms (MTR) on Windows. You want to use the 'Remote Login' and 'Advanced Proactive Management' features. Which license must be assigned to these devices?

Trap 1: Microsoft Teams Shared Devices license

The Shared Devices license is specifically intended for common area phones, panels, and display devices rather than full-scale Teams Room systems. It does not include the advanced meeting management or the proactive monitoring features required for high-end meeting room hardware and enterprise-level management workflows.

Trap 2: Microsoft Teams Rooms Basic license

The Basic license provides essential meeting capabilities for up to 25 devices but lacks the advanced management features like remote login and proactive health monitoring. It is generally used by smaller organizations that do not need the deep administrative insights or remote troubleshooting tools provided by the Pro tier.

Trap 3: Microsoft 365 E5 license

While an E5 license includes Teams, it is a user-based license and is not the correct or supported way to license a Teams Room device. Room systems require specific device licenses (Basic or Pro) to ensure they have the correct permissions for resource mailbox integration and specialized room features.

A
Microsoft Teams Shared Devices license
Why it fails: The Shared Devices license is specifically intended for common area phones, panels, and display devices rather than full-scale Teams Room systems. It does not include the advanced meeting management or the proactive monitoring features required for high-end meeting room hardware and enterprise-level management workflows.
B
Microsoft Teams Rooms Basic license
Why it fails: The Basic license provides essential meeting capabilities for up to 25 devices but lacks the advanced management features like remote login and proactive health monitoring. It is generally used by smaller organizations that do not need the deep administrative insights or remote troubleshooting tools provided by the Pro tier.
C
Microsoft Teams Rooms Pro license
The Teams Rooms Pro license is the required tier for accessing advanced management features. It includes the Pro management portal, which offers proactive alerts, remote remediation, and detailed analytics that help administrators maintain high availability for their meeting room environments and resolve issues before they impact users.
D
Microsoft 365 E5 license
Why it fails: While an E5 license includes Teams, it is a user-based license and is not the correct or supported way to license a Teams Room device. Room systems require specific device licenses (Basic or Pro) to ensure they have the correct permissions for resource mailbox integration and specialized room features.

Review the full routing breakdown →

Question 5hardmultiple choice

You are a Teams administrator for a multinational company. The company uses Direct Routing for PSTN connectivity. A user reports that when they receive an incoming PSTN call, the call rings on their Teams client but when they answer, the call drops immediately. You have verified that the user's voice configuration is correct and that the Session Border Controller (SBC) is reachable. You need to troubleshoot the issue. Which tool should you use to capture and analyze the SIP traffic for this call?

Trap 1: Teams client debug logs

Teams client debug logs capture client-side activity, including media and signaling, but they do not provide the full SIP trace from the SBC perspective. While they can be useful, they are less comprehensive for Direct Routing issues. The SBC logs are more authoritative for SIP-level troubleshooting.

Trap 2: Microsoft 365 network connectivity test tool

The Microsoft 365 network connectivity test tool assesses network readiness and connectivity to Microsoft 365 services. It does not capture SIP traffic or provide call-specific signaling details. It is useful for general network diagnostics but not for troubleshooting individual call drops.

Trap 3: Microsoft Teams admin center Call Analytics

Call Analytics provides detailed information about calls, including quality and signaling, but it does not capture raw SIP traffic. It shows media and signaling metrics but is not a packet capture tool. For deep SIP troubleshooting, you need to capture the actual SIP messages exchanged between Teams and the SBC.

A
Teams client debug logs
Why it fails: Teams client debug logs capture client-side activity, including media and signaling, but they do not provide the full SIP trace from the SBC perspective. While they can be useful, they are less comprehensive for Direct Routing issues. The SBC logs are more authoritative for SIP-level troubleshooting.
B
Session Border Controller (SBC) logs and SIP tracing
SBC logs and SIP tracing capture the SIP signaling between the SBC and Teams. Since the call rings but drops upon answer, the issue likely lies in SIP signaling (e.g., media negotiation, codec mismatch, or SDP issues). Analyzing SBC logs and SIP traces will reveal the exact SIP messages and error codes causing the drop.
C
Microsoft 365 network connectivity test tool
Why it fails: The Microsoft 365 network connectivity test tool assesses network readiness and connectivity to Microsoft 365 services. It does not capture SIP traffic or provide call-specific signaling details. It is useful for general network diagnostics but not for troubleshooting individual call drops.
D
Microsoft Teams admin center Call Analytics
Why it fails: Call Analytics provides detailed information about calls, including quality and signaling, but it does not capture raw SIP traffic. It shows media and signaling metrics but is not a packet capture tool. For deep SIP troubleshooting, you need to capture the actual SIP messages exchanged between Teams and the SBC.

Question 6mediummultiple choice

A user reports that during a Microsoft Teams meeting, they can hear other participants but no one can hear them. The user is using a USB headset. You need to determine the most likely cause using available Teams diagnostic tools. Which tool should you use first?

Trap 1: The Teams admin center's Meeting policies report

Meeting policies control what features users can access, such as whether they can use audio in meetings. However, a policy that blocks audio would affect all meetings and likely be noticed earlier. It would not cause a sudden one-way audio issue for a single user, and checking policies would not quickly resolve the immediate problem of a non-functioning microphone.

Trap 2: Network Planner in the Microsoft Teams admin center

Network Planner is used for capacity planning and assessing network readiness for Teams, not for troubleshooting individual user device issues. It would not help diagnose a microphone problem or a muted state. It focuses on bandwidth and network topology, which are not relevant to a single user's audio input failure in a live meeting.

Trap 3: Call Analytics in the Microsoft Teams admin center

Call Analytics provides detailed media quality and connection metrics for individual users, but it is not designed to perform real-time device diagnostics. It can show audio quality issues, but it cannot directly test whether the microphone is muted or malfunctioning, which is the first thing to check for a one-way audio problem. It would not quickly isolate a local device issue.

A
The Teams admin center's Meeting policies report
Why it fails: Meeting policies control what features users can access, such as whether they can use audio in meetings. However, a policy that blocks audio would affect all meetings and likely be noticed earlier. It would not cause a sudden one-way audio issue for a single user, and checking policies would not quickly resolve the immediate problem of a non-functioning microphone.
B
Teams device settings and the Make a test call feature
The Make a test call feature in Teams device settings records a short message and plays it back, allowing the user to verify if their microphone is working and if they are muted. This is the fastest way to isolate a local audio input problem. It directly tests the microphone and speaker, which is the most likely cause of one-way audio when using a USB headset.
C
Network Planner in the Microsoft Teams admin center
Why it fails: Network Planner is used for capacity planning and assessing network readiness for Teams, not for troubleshooting individual user device issues. It would not help diagnose a microphone problem or a muted state. It focuses on bandwidth and network topology, which are not relevant to a single user's audio input failure in a live meeting.
D
Call Analytics in the Microsoft Teams admin center
Why it fails: Call Analytics provides detailed media quality and connection metrics for individual users, but it is not designed to perform real-time device diagnostics. It can show audio quality issues, but it cannot directly test whether the microphone is muted or malfunctioning, which is the first thing to check for a one-way audio problem. It would not quickly isolate a local device issue.

Question 7mediummultiple choice

You are troubleshooting a Teams meeting issue where attendees from a specific remote office experience choppy video and audio. You suspect network problems. Which tool should you use to analyze the network connectivity for that office?

Trap 1: Teams usage reports

Teams usage reports provide aggregate data on how users are using Teams, such as number of meetings and messages. They do not include network performance metrics or connectivity details. Therefore, they cannot help diagnose choppy video and audio caused by network problems in a specific office.

Trap 2: Teams Network Planner

Network Planner is a design tool that helps estimate bandwidth requirements for Teams across your network. It does not provide real-time diagnostics or troubleshooting for an existing network issue. It is used before deployment or when planning changes, not for analyzing current connectivity problems in a specific office.

Trap 3: Call Analytics

Call Analytics is used to troubleshoot individual call quality issues by providing per-user call details. While it can show network metrics for a specific call, it does not provide a comprehensive analysis of the network connectivity for an entire office. It is more reactive and user-specific, not suited for assessing overall network health of a location.

A
Teams usage reports
Why it fails: Teams usage reports provide aggregate data on how users are using Teams, such as number of meetings and messages. They do not include network performance metrics or connectivity details. Therefore, they cannot help diagnose choppy video and audio caused by network problems in a specific office.
B
Microsoft 365 network connectivity test tool
The Microsoft 365 network connectivity test tool (available at connectivity.office.com) allows you to run tests from a specific location to assess network readiness for Teams. It measures latency, packet loss, and connectivity to Microsoft 365 endpoints. This tool can help identify if the remote office has network issues affecting Teams media quality, making it the right choice for this scenario.
C
Teams Network Planner
Why it fails: Network Planner is a design tool that helps estimate bandwidth requirements for Teams across your network. It does not provide real-time diagnostics or troubleshooting for an existing network issue. It is used before deployment or when planning changes, not for analyzing current connectivity problems in a specific office.
D
Call Analytics
Why it fails: Call Analytics is used to troubleshoot individual call quality issues by providing per-user call details. While it can show network metrics for a specific call, it does not provide a comprehensive analysis of the network connectivity for an entire office. It is more reactive and user-specific, not suited for assessing overall network health of a location.

Question 8mediummultiple choice

A user reports that they cannot see the 'Meet Now' option in their Microsoft Teams client. You need to determine the cause. Which policy setting should you check?

Trap 1: The app permission policy assigned to the user, specifically the…

App permission policies control which third-party or custom apps users can access within Teams. They do not affect core meeting features like 'Meet Now'. Disabling external apps would not remove the 'Meet Now' option. This setting is unrelated to the reported issue, so checking it would be a misdirection.

Trap 2: The messaging policy assigned to the user, specifically the 'Allow…

The messaging policy controls chat and channel features, not meeting creation. Disabling chat would not remove the 'Meet Now' option. While chat and meetings are related, they are governed by separate policies. Checking messaging policy would not resolve the missing 'Meet Now' button, as it does not control meeting initiation.

Trap 3: The live events policy assigned to the user, specifically the…

Live events policies govern the ability to schedule and participate in large-scale broadcast events, not ad-hoc meetings. The 'Allow scheduling' setting in live events policy affects live events only. It has no impact on the 'Meet Now' feature, which is part of regular meetings. Therefore, this check would not identify the cause.

A
The app permission policy assigned to the user, specifically the 'Allow external apps' setting.
Why it fails: App permission policies control which third-party or custom apps users can access within Teams. They do not affect core meeting features like 'Meet Now'. Disabling external apps would not remove the 'Meet Now' option. This setting is unrelated to the reported issue, so checking it would be a misdirection.
B
The meeting policy assigned to the user, specifically the 'Allow Meet Now' setting.
The 'Allow Meet Now' setting in the Teams meeting policy controls whether users can start ad-hoc meetings. If this setting is disabled, the 'Meet Now' option will not appear. This is the most direct policy to check when a user reports missing 'Meet Now' functionality, as it specifically governs that feature.
C
The messaging policy assigned to the user, specifically the 'Allow chat' setting.
Why it fails: The messaging policy controls chat and channel features, not meeting creation. Disabling chat would not remove the 'Meet Now' option. While chat and meetings are related, they are governed by separate policies. Checking messaging policy would not resolve the missing 'Meet Now' button, as it does not control meeting initiation.
D
The live events policy assigned to the user, specifically the 'Allow scheduling' setting.
Why it fails: Live events policies govern the ability to schedule and participate in large-scale broadcast events, not ad-hoc meetings. The 'Allow scheduling' setting in live events policy affects live events only. It has no impact on the 'Meet Now' feature, which is part of regular meetings. Therefore, this check would not identify the cause.

Question 9mediummultiple choice

Your company is in the process of rolling out Microsoft Teams to 5,000 users. You need a centralized tool that provides a checklist of deployment tasks and monitors the progress of the rollout, including user readiness and environmental readiness. Which tool should you use?

Trap 1: Microsoft Support and Recovery Assistant (SaRA)

The Microsoft Support and Recovery Assistant is a diagnostic tool used to fix specific sign-in or installation issues on an individual user's machine. It is not a project management or deployment monitoring tool and cannot provide a centralized overview of an entire organization's rollout progress or environmental readiness.

Trap 2: Teams Device Health

Teams Device Health focuses on monitoring the status and performance of Teams-certified hardware, such as Teams Rooms or IP phones. While it is useful for ongoing maintenance, it does not provide the deployment checklists, project planning, or user readiness tracking features that are found within the Teams Advisor tool.

Trap 3: Microsoft 365 Adoption Score

Adoption Score provides insights into how people are using Microsoft 365 services and the quality of their experience, but it is not a deployment planning tool. It focuses on post-deployment usage patterns rather than the specific checklist of technical tasks required to set up the environment during a rollout.

A
Teams Advisor
Teams Advisor provides a structured approach to rolling out Teams by creating a personalized project plan for your organization. It helps monitor readiness tasks and provides a central location for the deployment team to collaborate, ensuring that all technical and user-adoption prerequisites are met before moving to the next phase.
B
Microsoft Support and Recovery Assistant (SaRA)
Why it fails: The Microsoft Support and Recovery Assistant is a diagnostic tool used to fix specific sign-in or installation issues on an individual user's machine. It is not a project management or deployment monitoring tool and cannot provide a centralized overview of an entire organization's rollout progress or environmental readiness.
C
Teams Device Health
Why it fails: Teams Device Health focuses on monitoring the status and performance of Teams-certified hardware, such as Teams Rooms or IP phones. While it is useful for ongoing maintenance, it does not provide the deployment checklists, project planning, or user readiness tracking features that are found within the Teams Advisor tool.
D
Microsoft 365 Adoption Score
Why it fails: Adoption Score provides insights into how people are using Microsoft 365 services and the quality of their experience, but it is not a deployment planning tool. It focuses on post-deployment usage patterns rather than the specific checklist of technical tasks required to set up the environment during a rollout.

Review the full routing breakdown →

Question 10hardmultiple choice

You are deploying Microsoft Teams Direct Routing for your organization. You have configured a Session Border Controller (SBC) and a voice route. Users report that outbound calls to a specific number range fail, but calls to other numbers work. You need to troubleshoot the issue. Which tool should you use to view the detailed call flow and identify where the call is failing?

Trap 1: Network Planner

Network Planner helps estimate bandwidth requirements for Teams voice and meetings based on network topology. It does not provide call-level troubleshooting or signaling details. It is used during planning, not for diagnosing live call failures. Thus it cannot help identify why calls to a specific number range are failing.

Trap 2: Teams PowerShell module

Teams PowerShell can be used to retrieve configuration and call records, but it does not provide the real-time detailed call flow and signaling analysis that call analytics offers. While you can use it to check voice routes and policies, it lacks the granular per-call diagnostic capabilities needed here. Therefore it is not the best tool for this troubleshooting.

Trap 3: Call Quality Dashboard (CQD)

CQD provides aggregate telemetry on call quality, such as packet loss and jitter, but it does not show detailed call flow or signaling for individual calls. It is used for monitoring trends and identifying quality issues, not for troubleshooting call routing failures. Therefore it is not the appropriate tool for this scenario.

A
Microsoft Teams admin center call analytics
Call analytics in the Teams admin center provides per-user call history with detailed session information, including signaling and media path. It shows why a call failed, such as a mismatch in number patterns or SBC errors. This is the correct tool to diagnose why specific outbound calls fail while others succeed.
B
Network Planner
Why it fails: Network Planner helps estimate bandwidth requirements for Teams voice and meetings based on network topology. It does not provide call-level troubleshooting or signaling details. It is used during planning, not for diagnosing live call failures. Thus it cannot help identify why calls to a specific number range are failing.
C
Teams PowerShell module
Why it fails: Teams PowerShell can be used to retrieve configuration and call records, but it does not provide the real-time detailed call flow and signaling analysis that call analytics offers. While you can use it to check voice routes and policies, it lacks the granular per-call diagnostic capabilities needed here. Therefore it is not the best tool for this troubleshooting.
D
Call Quality Dashboard (CQD)
Why it fails: CQD provides aggregate telemetry on call quality, such as packet loss and jitter, but it does not show detailed call flow or signaling for individual calls. It is used for monitoring trends and identifying quality issues, not for troubleshooting call routing failures. Therefore it is not the appropriate tool for this scenario.

Question 11mediummultiple choice

You are the Teams administrator for a company that uses Microsoft Teams. Users in the marketing department report that when they join meetings, they sometimes cannot hear other participants and the audio is choppy. You need to determine whether the issue is related to the network or the client devices. Which tool should you use to get detailed media quality metrics for these users?

Trap 1: Teams admin center > Users > Manage users

The Teams admin center user management section provides basic account information and policies, but it does not include detailed media quality metrics such as jitter, packet loss, or latency. This tool is used for user configuration, not for troubleshooting call quality issues. Therefore, it would not help diagnose the choppy audio problem.

Trap 2: Teams client diagnostic logs

Teams client diagnostic logs contain detailed client-side information and can be useful for debugging client issues, but they do not provide a centralized view of network quality metrics across multiple users. They are more time-consuming to analyze and are not the primary tool for assessing media quality at scale.

Trap 3: Microsoft 365 usage reports in the Microsoft 365 admin center

Microsoft 365 usage reports show adoption and usage trends, such as the number of active users and meetings organized. They do not provide granular media quality metrics like packet loss or jitter. This tool is not suitable for diagnosing specific audio quality issues in meetings.

A
Teams admin center > Users > Manage users
Why it fails: The Teams admin center user management section provides basic account information and policies, but it does not include detailed media quality metrics such as jitter, packet loss, or latency. This tool is used for user configuration, not for troubleshooting call quality issues. Therefore, it would not help diagnose the choppy audio problem.
B
Teams client diagnostic logs
Why it fails: Teams client diagnostic logs contain detailed client-side information and can be useful for debugging client issues, but they do not provide a centralized view of network quality metrics across multiple users. They are more time-consuming to analyze and are not the primary tool for assessing media quality at scale.
C
Microsoft 365 usage reports in the Microsoft 365 admin center
Why it fails: Microsoft 365 usage reports show adoption and usage trends, such as the number of active users and meetings organized. They do not provide granular media quality metrics like packet loss or jitter. This tool is not suitable for diagnosing specific audio quality issues in meetings.
D
Call Analytics in the Teams admin center
Call Analytics provides detailed per-user and per-session media quality data, including packet loss, jitter, latency, and device information. This allows you to determine if the choppy audio is due to network conditions or client issues. It is the correct tool for troubleshooting individual call quality problems.

Question 12hardmultiple choice

You are a Teams administrator at Fabrikam. Users report that during Teams meetings, their video frequently freezes while audio continues. You suspect a network issue. You need to determine whether the problem is caused by insufficient bandwidth or high jitter. Which tool should you use to analyze the real-time media quality metrics for affected users?

Trap 1: Microsoft 365 network connectivity test in the Microsoft 365 admin…

The Microsoft 365 network connectivity test assesses network readiness from a specific location, but it does not provide per-user real-time media quality metrics during actual meetings. It tests connectivity to Microsoft 365 endpoints, not the live call quality experienced by users. It would not show jitter or bandwidth for ongoing calls.

Trap 2: Teams usage reports in the Microsoft 365 admin center

Teams usage reports show aggregated activity data such as number of messages sent, calls made, and meetings attended. They do not include quality metrics like jitter or bandwidth. These reports are useful for adoption tracking, not for troubleshooting real-time media quality issues during meetings.

Trap 3: Network planner in the Teams admin center

Network planner helps estimate bandwidth requirements for Teams based on user personas and network topology before deployment. It does not provide live or historical quality metrics for actual calls. It is a planning tool, not a troubleshooting tool for ongoing media quality problems.

A
Call Analytics in the Teams admin center
Call Analytics provides detailed real-time and historical telemetry for Teams calls and meetings, including jitter, packet loss, and bandwidth usage. Administrators can view per-user metrics and identify whether video freezing is due to insufficient bandwidth or high jitter. This is the correct tool for diagnosing media quality issues for specific users.
B
Microsoft 365 network connectivity test in the Microsoft 365 admin center
Why it fails: The Microsoft 365 network connectivity test assesses network readiness from a specific location, but it does not provide per-user real-time media quality metrics during actual meetings. It tests connectivity to Microsoft 365 endpoints, not the live call quality experienced by users. It would not show jitter or bandwidth for ongoing calls.
C
Teams usage reports in the Microsoft 365 admin center
Why it fails: Teams usage reports show aggregated activity data such as number of messages sent, calls made, and meetings attended. They do not include quality metrics like jitter or bandwidth. These reports are useful for adoption tracking, not for troubleshooting real-time media quality issues during meetings.
D
Network planner in the Teams admin center
Why it fails: Network planner helps estimate bandwidth requirements for Teams based on user personas and network topology before deployment. It does not provide live or historical quality metrics for actual calls. It is a planning tool, not a troubleshooting tool for ongoing media quality problems.

Question 13mediummultiple choice

You are the Teams administrator for a company that uses Microsoft Teams. Several users in the marketing department report that their calls to external partners often drop after about 10 minutes, but internal calls are fine. You need to determine whether the issue is related to network connectivity or a Teams service problem. Which tool should you use first?

Trap 1: Azure Network Watcher

Azure Network Watcher monitors and diagnoses Azure network resources, such as virtual machines and virtual networks. It does not capture Teams call telemetry or analyze media quality for external calls, so it cannot directly troubleshoot the reported issue.

Trap 2: Microsoft 365 network connectivity test tool in the Microsoft 365…

The Microsoft 365 network connectivity test tool validates general network readiness for Microsoft 365, but it does not provide per-call diagnostics or isolate issues specific to external calls. It is useful for initial network assessments but lacks the detailed call-quality metrics needed to troubleshoot dropped calls with external partners.

Trap 3: Teams usage reports in the Microsoft 365 admin center

Teams usage reports show aggregate activity such as number of calls and meetings, but they do not provide call-level diagnostics or quality metrics. They cannot help determine why specific external calls drop after 10 minutes because they lack session-level detail.

A
Call Analytics in the Microsoft Teams admin center
Call Analytics provides detailed per-user and per-call telemetry for Teams calls, including session details, media quality, and network metrics. It can show whether the dropped external calls experienced packet loss, jitter, or connectivity failures, helping distinguish between network and service issues.
B
Azure Network Watcher
Why it fails: Azure Network Watcher monitors and diagnoses Azure network resources, such as virtual machines and virtual networks. It does not capture Teams call telemetry or analyze media quality for external calls, so it cannot directly troubleshoot the reported issue.
C
Microsoft 365 network connectivity test tool in the Microsoft 365 admin center
Why it fails: The Microsoft 365 network connectivity test tool validates general network readiness for Microsoft 365, but it does not provide per-call diagnostics or isolate issues specific to external calls. It is useful for initial network assessments but lacks the detailed call-quality metrics needed to troubleshoot dropped calls with external partners.
D
Teams usage reports in the Microsoft 365 admin center
Why it fails: Teams usage reports show aggregate activity such as number of calls and meetings, but they do not provide call-level diagnostics or quality metrics. They cannot help determine why specific external calls drop after 10 minutes because they lack session-level detail.