Microsoft 365 Certified: Teams Administrator Associate (MS-700) — Questions 151–211

Safe Attachments in Defender for Office 365 can scan files in SharePoint Online, OneDrive, and Teams. Configuring a policy for these workloads ensures files are scanned before download, meeting the security requirement without blocking uploads. This is the correct integrated solution.

The Teams App Usage report specifically lists the applications in use across the tenant. It provides the name of the app, the publisher, and the number of active users, allowing administrators to see exactly which third-party tools are most popular among their staff.

Adding multiple SBCs to the same voice route provides redundancy. If one SBC fails, Teams can attempt to route the call through another SBC listed in the route. This ensures high availability for outbound and inbound calls, as the voice route will try the next SBC in the list. This is a core method for achieving Direct Routing resiliency.

The Service health dashboard in the Microsoft 365 admin center provides real-time status of Microsoft services, including Teams. It shows active incidents, planned maintenance, and advisories. You can configure notifications to alert you of issues. This is the correct tool for monitoring service health and receiving alerts.

Jitter measures the variation in packet arrival times. High jitter on the user's side indicates network instability that can cause audio to cut out. Call Analytics displays jitter for both the user's endpoint and the participant's, so you can pinpoint whether the problem originated locally. This metric directly addresses the intermittent audio symptom described.

CQD provides a comprehensive view of quality for the entire organization by aggregating data from all calls and meetings. It allows administrators to filter by subnets, buildings, and endpoints over a 90-day period. This makes it the correct choice for identifying systemic patterns and historical trends across different network segments.

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.

The 'Assignments' section of a Conditional Access policy defines who the policy applies to. Without specifying users or groups, the policy cannot be enforced, as it needs to know which identities are subject to the security requirements and conditions you are establishing for Teams access.

Assigning the voice policy to the user is essential because the voice policy links the user to the PSTN usages and voice routes that define how outbound calls are routed. Without this assignment, the user cannot make PSTN calls. The voice policy also controls other calling features. This step is required to enable outbound calling through the configured SBC.

The Reports Reader role provides read-only access to usage reports across Microsoft 365 services, including Teams. It allows viewing reports without the ability to change any settings. This role is specifically designed for users who need to analyze data but not administer the service, making it the least privileged role for this scenario.

A voice routing policy (dial plan) defines normalization rules and PSTN usage records that map dialed numbers to the correct routes to the Session Border Controller (SBC). Without an assigned voice routing policy, Teams cannot determine how to route the call, causing immediate failure. Assigning the policy ensures the dialed number is normalized and matched to a PSTN usage, which is then associated with a route.

Channel moderation on General lets you grant moderator rights to the dispatchers so they can post announcements, while the member permission 'Allow members to start new posts' can be turned off to stop the 3,990 members from beginning conversations. Replies to existing threads remain possible because reply permission is a separate toggle, so the dispatchers keep working as required.

An app setup policy allows administrators to pin apps to the Teams sidebar and determine the installation behavior for users. By creating a custom policy for the Sales department, you can ensure the 'Tasks' app is consistently visible, which streamlines the user experience and ensures that critical business tools are always within reach for the target audience.

The Calling policy is the specific configuration set that governs whether a user can make or receive calls, including PSTN calls. By modifying this policy, administrators can grant or revoke dial-out permissions, making it the primary place to check when PSTN calling functionality is failing.

Changing the channel's membership type to Private makes the channel available only to the users explicitly added as channel members, even though they remain members of the parent team. Adding the dispatchers as channel members satisfies both visibility and posting restrictions because non-members cannot see or post in a private channel. This is the supported way to scope a channel to a subset of team members in Microsoft Teams.

Changing the AllowTranscription parameter to true enables the underlying capability for users governed by this policy to start transcriptions during meetings. This adjustment directly addresses the reported issue by unlocking the required menu option within the Teams client interface.

This is the core configuration step. Within the policy, you can independently set the permissions for Microsoft apps, third-party apps, and custom apps. Choosing to block all third-party apps ensures that only the apps developed by Microsoft will be visible and usable for those users.

The ability to create teams is tied to the ability to create Microsoft 365 groups. If group creation is restricted to certain users or disabled, users without permission will see this error when attempting to create a team. Checking the Microsoft 365 group creation settings in the Microsoft 365 admin center will reveal if the Sales team users are allowed to create groups.

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.

Channel moderation allows you to control who can post messages in a channel. By enabling moderation on the 'General' channel and assigning moderators, you ensure that only moderators can post, or that messages require approval before posting. This meets the requirement for review before posting.

A security group is necessary to identify the specific subset of users who will be granted the exception to the creation block. Microsoft 365 uses this group within a PowerShell script to map the 'EnableGroupCreation' attribute, allowing only these specific members to bypass the tenant-wide restriction.

For Calling Plans, the administrator must add and validate an emergency location (civil address) in the Teams admin center and assign it to the user. This address is transmitted to the PSAP during an emergency call. Without a validated location, the call may not route to the correct PSAP or may fail. This is the foundational step for emergency calling.

Adding a domain to the allow-list is a mandatory step for restricted external access configurations. Without this entry, Microsoft 365 blocks incoming and outgoing communication requests from that specific domain, effectively preventing any Teams chat interaction between users of the two organizations involved in the collaboration.

This is correct because adding a Power BI tab directly from Teams allows you to select a report from any workspace you have access to. It requires no additional configuration and is the simplest method. The tab will display the report and update automatically.

Within the Teams admin center, the 'Teams settings' section under 'Org-wide settings' (or 'Files' in the newer interface) contains the toggle switches for third-party storage providers. Enabling Dropbox and Google Drive here makes these services available for all users to add as tabs or storage locations.

Configuring and enforcing a Microsoft 365 Group naming policy requires that at least one user in the organization has an Azure AD Premium P1 or P2 license. This license level unlocks advanced governance features necessary for managing group lifecycles and naming standards across the entire Microsoft 365 tenant.

The Call Quality Dashboard (CQD) aggregates media quality data, including bandwidth usage, packet loss, jitter, and latency. It can show if there are network bandwidth issues affecting screen sharing and video. By analyzing CQD reports, you can identify if poor quality is due to insufficient bandwidth, making it the correct tool for this scenario.

The ability to delete sent messages is a configurable setting within the messaging policy. This is often restricted in highly regulated industries to ensure that all communication is preserved for eDiscovery purposes, demonstrating the importance of granular control over user communication habits within the environment.

This is the standard end-user method for creating a team. It is the most common way for users to self-provision teams, and it respects any tenant-level restrictions or naming policies that may be configured by the organization's administrators to maintain order within the environment.

A retention policy in the Microsoft 365 compliance center can be applied to Teams meeting recordings stored in SharePoint and OneDrive. Setting a 90-day retention period with deletion after that period ensures recordings are automatically removed. This is the centralized, minimal-effort solution that meets the requirement without manual intervention.

Meeting policies in Teams support a custom disclaimer setting that displays a disclaimer to participants before they join a meeting. By creating a new meeting policy with the required disclaimer text and assigning it to the legal team members, you ensure that only meetings organized by those users show the disclaimer. This meets the requirement without impacting other departments.

Messaging policies contain the settings for chat-based interactions, including the use of Giphy, memes, and stickers. By updating the messaging policy assigned to your users, you can toggle these settings off, effectively preventing the use of GIFs in any chat or channel conversation.

This report specifically tracks the platform used to access Teams, categorizing activity by desktop, web, or mobile. It is the correct report to determine which users are accessing the service via the browser versus the dedicated desktop application for support or compliance reasons.

Team templates provide a predefined structure of channels and apps that are automatically provisioned when a user creates a new team. This ensures that every team starts with the required configuration, minimizing administrative overhead and guaranteeing that essential collaboration tools are immediately available to the members.

Teams Only mode ensures all chat and meetings are handled by Microsoft Teams, satisfying the requirement. Even in this mode, users can still use the Skype for Business client to join meetings hosted by external users who have not yet migrated, providing the necessary interoperability while centralizing internal communications.

Resource accounts are specialized accounts for meeting rooms and shared devices. When combined with a Teams Room Basic or Pro license, they enable the device to join meetings, share content, and be discovered in the global address list as a bookable location for internal users.

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.

The sign-in logs in Microsoft Entra ID provide a comprehensive record of all login attempts. They specify the status of each attempt and detail which conditional access policies were triggered, allowing administrators to pinpoint exactly why a user's access to Teams was denied.

The Cloud storage options in Teams settings allow administrators to enable or disable specific third-party storage providers for the entire organization. By enabling only the approved providers, you restrict users to those services. This directly meets the requirement to permit only specific cloud storage providers. This is the correct location to configure this setting.

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.

Teams Rooms devices must be signed in with a resource account that has a Microsoft Teams Rooms license assigned. Without a valid license, the device cannot register with Teams and will not appear in the Teams Admin Center. This is a common misconfiguration. Checking the account and license is the first step to ensure the device can authenticate and be managed.

Custom messaging policies are the correct administrative tool for applying specific chat settings to a subset of users. By setting the Giphy content rating to 'Strict' within this custom policy and then assigning it to HR staff, you meet the requirement of localized control without impacting the rest of the organization's messaging capabilities.

The Teams device settings include a 'Make a test call' feature that allows users to record a message and play it back, verifying microphone and speaker functionality. This is a quick, user-driven test to confirm if the microphone is working. It directly addresses the need to check the microphone in real time.

The bitrate indicates how much data is being transmitted per second for the screen sharing stream. If the bitrate is low, the Teams client will dynamically reduce the resolution, resulting in the blurry images that the user observes during their presentation.

A high RTT indicates significant network latency. When this value exceeds thresholds, it suggests the local network is struggling to handle the traffic or the ISP route is heavily congested, which directly leads to audio delays and choppy video during a Teams session.

External access policies control whether users can communicate with people outside the organization who are using Teams. If external access is disabled for the finance users, they cannot start chats with external partners. Checking this policy first is logical because the issue is specific to external chats while internal chats work, pointing to a policy that governs external communication.

Retention policies in the Purview portal are designed to enforce data lifecycle management. By applying a policy to Teams chats, you can automatically purge messages after a 90-day window, ensuring that the organization adheres to its data governance and privacy policies consistently across the entire tenant.

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.

Call Analytics provides detailed per-user and per-meeting call quality data for the last 30 days. Since the meeting occurred 20 hours ago, it falls within the retention window, and you can filter by meeting or user to analyze metrics like packet loss, jitter, and latency. This is the appropriate tool for troubleshooting a specific meeting's audio quality.

Microsoft Teams Call Analytics retains granular, advanced telemetry (such as per-minute CPU and network stats) for exactly 7 days. After this period, you can still see that a call occurred, but you cannot access the deep technical details required for thorough quality analysis.

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.

Call Analytics session details provide a granular view of a specific call or meeting, including media stream information such as codecs used, network traversal (relay vs. direct), packet loss, jitter, and latency for each stream. This is exactly what is needed to investigate poor video quality for a particular meeting and understand the technical reasons behind it.

Permission policies allow you to 'Allow' or 'Block' specific apps for users. If the 'Shift' app (a Microsoft app) is not included in the allowed list of the permission policy assigned to the user, it will be hidden from their view in the app store, regardless of other settings.

Retention policies in Microsoft Purview can be applied to OneDrive and SharePoint sites to prevent the deletion of files for a specific period. By applying a 'Retain' policy to meeting recordings, you ensure that even if a user tries to delete the file, it remains discoverable for compliance and legal purposes.

Setting the domain access to 'Allow only specific external domains' changes the default behavior of the tenant from 'Open' to 'Restricted'. This ensures that the system will automatically block communication with any domain that is not explicitly added to the allowed list, providing a high level of security.

For non-channel meetings, the recording is saved to the OneDrive of the person who initiated the recording. Since a participant started the recording, the file will be in that participant's OneDrive under the Recordings folder. This is the correct first location to check to find the missing recording.

The Microsoft Graph API for Service Communications allows you to programmatically retrieve service health and incident data. You can use it to build a custom integration that sends notifications to a ticketing system via webhook. This API provides the necessary endpoints to subscribe to and fetch service communications, enabling proactive alerts.

Conditional access policies in Azure AD can enforce device compliance for specific cloud apps, including Teams. By targeting the Teams cloud app and the sales group, and requiring a compliant device, you ensure that only compliant Windows devices can access Teams. This directly satisfies the requirement.

Guest access must be enabled at the organization level before any user-level policy can permit it. Even with a policy allowing guest interactions, if the tenant-wide setting is disabled, the system will block all attempts to invite external guests to meetings to maintain security.

A Microsoft 365 retention policy applied to Teams recordings (stored in SharePoint or OneDrive) can automatically delete recordings after 90 days. This is the correct method because it ensures compliance across all recordings regardless of meeting policy settings. Retention policies are managed in the Microsoft 365 compliance center and take precedence for data lifecycle management.

Team creation is governed by the ability to create Microsoft 365 groups, which can be controlled at the tenant level. By allowing this user to create groups and not assigning a Teams admin role, the agent can create teams while remaining unable to modify organizational-wide Teams settings. This satisfies least privilege and directly addresses the requirement.