Microsoft 365 Certified: Teams Administrator Associate (MS-700) — Questions 1–75

Sensitivity labels allow you to define rules for how data should be handled. By applying these to teams or files, you can enforce policies that restrict external sharing, ensuring that sensitive content remains protected even if a user tries to share it externally with a guest user.

Private channels require users to be members of the parent team before they can be added to the private channel. Adding Alex to the team first establishes the necessary membership, and then you can add him to the private channel. This is the correct and required sequence.

This setting controls which participants can bypass the lobby. Setting it to 'Organizers only' ensures that only meeting organizers can bypass the lobby, while attendees must wait in the lobby. This directly meets the requirement to allow only organizers to bypass the lobby. It is configured in the Teams meeting policy under 'Participants & guests'.

Call Analytics provides detailed real-time telemetry for individual Teams meetings, including screen sharing quality metrics such as frame rate, latency, and packet loss. By reviewing the session details for the affected users, you can identify whether the issue is due to network conditions, device performance, or other factors, enabling targeted remediation.

The App Setup policy is specifically designed to manage the look and feel of the Teams client, including the ability to pin specific apps to the sidebar. By creating a custom setup policy, you can dictate exactly which apps appear for the users assigned to that policy.

The network connectivity test tool assesses network readiness and connectivity from a specific location to Microsoft 365. It can identify latency, packet loss, and other network issues that affect call quality. Running it from an affected user's location helps determine if the problem is network-related, complementing Call Analytics data.

This workload focuses on the core collaboration features of Teams. Teams Advisor provides a step-by-step guide for setting up the basic infrastructure, including team structures, channel management, and the initial integration of applications, which are essential for getting the organization started with modern teamwork and communication.

For dynamic emergency calling, Teams uses the network topology to determine the client's location based on the subnet or wireless access point. You must configure trusted IP addresses and associate them with emergency locations. This allows Teams to automatically transmit the correct emergency location when a user dials an emergency number. Without this, the emergency location may not be transmitted correctly, even if policies are assigned.

Meeting expiration is a setting that can be configured by the organizer when scheduling a Teams meeting in Outlook. The expiration time is included in the meeting details, often in the body or as a separate field. Checking the Outlook calendar item for the meeting will reveal if an expiration time was set, which explains why the user cannot join after that time.

The Teams calling policy includes settings such as AllowPrivateCalling, which controls whether users can make private calls. If this setting is disabled, the Calls app may be hidden. Ensuring the user is assigned a calling policy with AllowPrivateCalling enabled is the correct first step to make the Calls app visible.

Selecting 'Only organizers and co-organizers' forces all external participants, including trusted federated users, to wait in the lobby until explicitly admitted. This prevents unauthorized individuals from entering sensitive meetings prematurely, fulfilling strict security guidelines required by the finance department for confidential discussions.

The Call Quality Dashboard requires a building mapping file to associate network subnets with physical site names. Without this file, CQD only shows raw IP addresses, making it impossible for administrators to determine which physical locations are experiencing quality issues based on the aggregated telemetry data provided in the reports.

Retention policies at the tenant level are the authoritative method for controlling how long data persists. By setting a seven-year retention period and applying it to Teams chats, the system preserves all conversation data, even if users attempt to delete messages from their own client interface.

External access is a two-way setting. Even if your organization allows the external domain, the external organization must also allow your domain for communication to work. If the external user's organization has not allowed your domain, they cannot receive or start chats. This is a common oversight.

For Teams to provide a dynamic location, the administrator must upload the organization's network topology, including subnets, switches, and wireless access points. These network elements are then linked to specific civic addresses and locations, allowing the system to pinpoint where a user is located when they place an emergency call.

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.

Network Planner is specifically designed to help administrators estimate the bandwidth requirements for their organization's sites. By inputting the number of users and their expected personas, it calculates the network impact of Teams traffic, including video, audio, and screen sharing, providing a clear readiness report.

Communication Compliance is the correct tool for this requirement. By enabling the 'Report message' feature in Teams messaging policies and setting up a policy in Purview, flagged messages are routed to a dedicated dashboard where compliance officers can investigate and take action.

Channel moderation settings determine who can post messages in a channel. If moderation is enabled and the user is not a moderator, they cannot post. The error message indicates a permission issue, which aligns with moderation restrictions. Checking the channel moderation settings will reveal if the user is restricted from posting.

For dial-in details to appear, the user's Audio Conferencing license must be paired with an audio conferencing bridge that has at least one default toll or toll-free number configured for the organization. If no bridge number is set as default, the invitation omits dial-in information even though the license is present. Assigning the bridge number resolves the missing dial-in details.

The Group Expiration policy is the correct tool for this scenario as it automatically sends renewal notifications to owners of inactive teams. It integrates with Azure AD to monitor activity and provides a mechanism for owners to extend the life of their teams or allow them to be automatically deleted.

In Teams, team owners can control whether members are allowed to create channels. By default, members can create channels. In the team's settings, under 'Member permissions', you can uncheck 'Allow members to create and update channels'. This restricts members to only use existing channels, such as the General channel, and prevents them from creating new ones.

Sensitivity labels in Microsoft Purview, when published to users and configured with the 'Require users to apply a label to their groups or sites' setting, enforce label selection during team creation. The label automatically applies to the Microsoft 365 group and connected SharePoint site. This directly satisfies the requirement to enforce a label and apply it to associated resources.

Compliance recording in Teams requires a certified recording partner solution and a compliance recording policy assigned to users. The policy tells Teams to route calls to the recording service, which then records and stores the calls. This is the correct method to automatically record PSTN calls for compliance.

The Dashboard in the Teams Admin Center provides a unified view of the organization's Teams health. It includes tiles for user activity and call quality, allowing administrators to quickly identify status changes without needing to navigate through specific sub-reports or external monitoring tools.

The Org-wide Guest Access setting is the master switch for external collaboration. If this is disabled, no guests can be added to any team. You must verify this setting first, as it acts as a global blocker that overrides all other team-level or user-level configuration settings.

When HostedVoiceMail is disabled, the Teams voice infrastructure lacks a valid destination for unanswered calls after the ring timer expires. Consequently, the call fails to deposit a voicemail message and terminates abruptly, disrupting standard telephony workflows.

App Setup policies give administrators the power to pin apps to the navigation bar and install them on behalf of users. By creating a custom setup policy and assigning it to the department members, the administrator can ensure the project management app is prominently displayed for everyone in that group.

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.

After enabling moderation, you must designate which members are moderators. Moderators are the only ones who can post new messages when moderation is on. Adding the specific members as moderators allows them to post while other members can only read. This is the second required action.

Advisor for Teams analyzes your Microsoft 365 environment and creates a tailored deployment plan. It provides specific recommendations for workloads like Chat, Teams, and Meetings, and sets up a dedicated team for the deployment project to help administrators stay organized throughout the rollout process.

QoS is the recommended solution for managing bandwidth constraints. By tagging Teams media traffic, the network can prioritize audio and video packets, ensuring that even when the network is busy, communication quality remains high and users do not experience dropouts or lag.

For a user to dial out from a Teams meeting to a PSTN number, they must have a Teams meeting policy that enables PSTN dial-out and be assigned a phone number that supports outbound calls. Since other users in the department can dial out, the likely cause is that this user is assigned a different meeting policy that disallows dial-out. Assigning the correct policy and verifying the phone number resolves the issue.

The Teams Administrator role provides the necessary permissions to manage the Teams service, including policies, team settings, and user configurations, without granting access to other M365 services like Exchange or SharePoint. This is the correct role to assign for effective, limited-scope administrative management.

The most common cause of no audio with a USB headset is that Teams is not using the correct audio device. Teams allows users to select their preferred microphone and speaker. If the headset is not selected, audio will not be routed to it. Checking and selecting the correct device in Teams settings is the first troubleshooting step.

Channel moderation settings allow team owners to restrict who can post messages in a channel. If moderation is enabled and members are not allowed to post, they will be unable to send messages in that channel, but direct messages remain unaffected. This matches the scenario where only channel messages are blocked for members of a specific team.

The Active issues tab in Service health displays current incidents and advisories that may impact Teams meeting join capabilities. If an advisory is present, it provides details on scope and workarounds. This is the first place to verify if the problem is service-related, aligning with the scenario's need to distinguish between network and service issues.

CQD allows for the ingestion of building data, which maps subnets to physical locations. This enables administrators to compare performance between different offices. It provides the necessary scale to see if a specific site is underperforming compared to the rest of the global organization over time.

Teams use Microsoft 365 Groups for their membership. By changing the membership type of the group from 'Assigned' to 'Dynamic User' and defining a rule (e.g., user.department -eq 'Sales'), the membership becomes automated. This requires an Azure AD Premium P1 license for each unique user that is a member of one or more dynamic groups.

High packet loss at the client level is almost always caused by congestion on the local network or Wi-Fi interference. When the local network is saturated or the wireless connection is unstable, packets are dropped before they can be successfully transmitted to the internet.

Audio Conferencing allows participants to join Teams meetings via a dial-in number. To enable this, each user who schedules meetings must have an Audio Conferencing license, and the meeting policy must allow audio conferencing. This is the correct configuration to provide dial-in numbers for meetings.

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.

These UDP ports are strictly required by the Teams client to facilitate media streams for audio, video, and screen sharing. Blocking these ports forces the application to use less efficient fallback mechanisms, which directly results in poor call quality and performance issues for users.

With Operator Connect, the carrier manages the SBC infrastructure and the connection to Microsoft's network. This removes the burden of hardware maintenance, software updates, and complex certificate management from the organization's IT staff, making it much easier to deploy and maintain than a traditional Direct Routing setup.

Teams meeting recordings are stored in SharePoint and OneDrive. If the user's OneDrive is out of storage or if they lack permissions to the SharePoint site where the recording should be saved, the recording will fail. Checking storage quota and permissions is the logical next step after verifying licenses and policies, as these are common blockers for recording storage.

Real-time analytics allow an administrator to look up an active user and see live telemetry for their current meeting. This includes detailed statistics on network performance and device health, which are updated every few seconds to help pinpoint the exact cause of a participant's audio or video degradation.

When you create a private channel, Teams automatically provisions a new SharePoint site collection dedicated to that private channel, separate from the parent team's site. This is by design to ensure privacy and isolated file storage for private channel members.

Teams Rooms require a specific license to function correctly. The Pro or Basic licenses provide the necessary entitlements for the MTR software to sign in, join meetings, and access advanced management features. Standard user licenses are not supported for dedicated room systems and may lead to functional issues.

Device Configuration Profiles are specifically designed for managing the settings of Teams-certified IP phones and other Android-based Teams devices. They allow you to centrally manage brightness, language, network settings, and UI customizations like background images, ensuring that all devices adhere to corporate standards and branding.

The Network section in Call Analytics provides metrics such as packet loss, jitter, and latency, along with connectivity details. These metrics help determine whether the poor audio and dropped calls were due to network issues on the user's side or within the Microsoft Teams service. This is the first place to check for network-related call quality problems.

Team creation is tied to Microsoft 365 group creation. By restricting group creation to a specific security group, you control who can create teams. Adding marketing users to that group allows them to create teams while others cannot. This is the correct method.

LBR uses the network site configuration, which maps IP subnets to physical locations. When a user makes a call, Teams checks their current IP against the defined network sites. If the site is configured for LBR, the service enforces the routing rules associated with that specific geographical location.

To add a tab, the user must be a member of the team (or have appropriate permissions) and the app used for the tab must be allowed by the app permission policy assigned to the user. If the app is blocked or the user is not a member, they cannot add tabs. This option correctly identifies the two key prerequisites for adding tabs in Teams.

Before individual teams can accept guests, guest access must be enabled at the organization level. This is the global master switch that controls whether any guest functionality is permitted within your tenant, ensuring that all teams operate within the boundaries defined by your organizational security and compliance governance policies.

Mapping subnets to physical locations allows CQD to aggregate call data by building, city, or region. This enables administrators to identify if a specific office has a local network issue, such as a faulty router or insufficient bandwidth, by comparing it against other locations.

Calling Plans in Microsoft Teams determine the scope of outbound calling. A Domestic Calling Plan allows only domestic calls, while an International Calling Plan includes both domestic and international. To enable international calling, you must assign a Calling Plan that includes international minutes. This is the direct and correct solution.

Teams channel policies allow administrators to define specific permissions for users, such as whether they can create private or shared channels. By creating a custom policy with private channel creation disabled, you create the administrative framework necessary to restrict these specific actions for any user to whom the policy is assigned.

Teams File Preview allows users to view and co-author documents directly within the Teams interface. This feature is integrated directly into the Files tab, providing a streamlined experience that removes the need to leave the app to perform basic editing tasks, which helps to maintain the user's workflow.

The Teams Administrator role is specifically designed to grant access to the Teams admin center and PowerShell cmdlets for managing teams, channels, and all policy types. This role perfectly matches the required tasks without over-provisioning permissions, keeping the management environment secure and compliant.

The Help menu in the Teams desktop client provides a 'Collect logs' option that gathers detailed diagnostic logs, including media and signaling data. This is the correct procedure to capture logs for troubleshooting call drops and other issues. The logs are saved as a compressed file that can be shared with support.

The auto attendant has a built-in 'Dial by extension' feature that allows callers to enter an extension. By enabling this option and specifying a custom extension range, the auto attendant will search the directory for users with extensions in that range. This directly satisfies the requirement without additional resources.

Microsoft Entra ID (formerly Azure AD) governs the foundational ability to invite guests. If the 'External collaboration settings' are configured to 'Deny invitations to the specified domains' or if guest invites are disabled entirely, the user will not be able to access resources regardless of Teams settings.

Since 'AllowAllApps' is set to false, the user can only access apps explicitly defined in the 'AllowedApps' collection. If the desired app is not in this list, it will not appear in the store for the user, regardless of its global status or availability to other users.

Call Quality Dashboard (CQD) aggregates call and meeting data to provide trend analysis and identify patterns in call quality across the organization. It helps you proactively monitor quality metrics and is essential for analyzing historical trends, as required. CQD does not provide service health alerts but is crucial for quality monitoring.

Teams update policies allow administrators to manage how users receive updates to the Teams client. By setting the 'Allow public preview' option to 'Enabled' or 'Follow Office Preview' within this policy, administrators can grant specific users access to new features before they are generally available to the public.

Call Analytics provides detailed per-user call history and diagnostic data, including why a call failed. For outbound PSTN calls, it can show if the call was blocked by a voice routing policy, if the number was misdialed, or if there was a carrier issue. This directly addresses the scenario of outbound call failures while inbound calls succeed.

If the Allow PSTN dial-in setting is disabled in the meeting policy, meeting invitations will not include dial-in numbers even if the user is licensed for Audio Conferencing. This directly explains the missing dial-in information. Enabling this setting would resolve the issue, making it the most likely cause.

A Survivable Branch Appliance (SBA) is designed to provide local PSTN connectivity when the connection to Microsoft 365 is lost. To enable this, the SBA must have a local PSTN gateway (or SIP trunk) and the branch users must be homed on the SBA for failover. During a WAN outage, the SBA registers the users locally and routes their calls through the local gateway, ensuring continued PSTN access. This configuration is essential for branch survivability.

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.

The Teams user activity report shows detailed activity for each user, including last activity date, messages sent, calls, and meetings. It can be filtered to a specific time range, such as the past 30 days. This report directly answers which users have been active.

Round-trip time (RTT) measures the time it takes for a signal to go from the source to the destination and back. It is the primary metric for network latency. High RTT indicates delays in audio transmission, which matches the user's experience of choppy audio and delays. In Call Analytics, RTT is displayed for each participant and can help identify network latency issues.

The Teams web client requires a supported browser version. Chrome 92 is outdated; updating to the latest version ensures compatibility. Microsoft regularly updates the list of supported browsers for Teams, and using an older version can trigger the 'browser not supported' error. Updating Chrome is the direct fix.

TCP is not designed for real-time media because its retransmission mechanisms introduce significant latency and jitter. Forcing TCP-only mode bypasses the high-performance UDP delivery optimized for Teams, resulting in noticeable degradation of both audio and video quality during meetings and calls.

This is the correct approach because conditional access policies in Microsoft Entra ID can target the Microsoft Teams cloud app specifically. By requiring the device to be marked as compliant, only devices that meet Intune compliance policies will be granted access. This enforces the security team's requirement without affecting other applications. The policy must be scoped to the Teams cloud app to avoid unintended impact on other services.

A Microsoft Teams Rooms Pro license provides the necessary features for one-touch join, including the ability to join meetings from the device calendar. Configuring the device with the resource account credentials allows it to authenticate and access the calendar. This is the correct and required setup for Teams Rooms on Windows.