Microsoft MS-700 Managing Teams Exam Dumps and Practice Test Questions Set 8 Q 106-120
Visit here for our full Microsoft MS-700 exam dumps and practice test questions.
Question 106:
You are the Teams administrator for your organization. Users report that they cannot see the option to schedule live events in Microsoft Teams. You need to enable live events for all users in the organization. Which of the following should you configure?
A) Teams live events policy
B) Teams meeting policy only
C) Teams app permission policy
D) Teams messaging policy
Answer: A
Explanation:
Teams live events policy is the administrative control that governs whether users can create, schedule, and participate in live events within Microsoft Teams. Live events are large-scale broadcast meetings designed for scenarios where presenters deliver content to a large audience with limited interaction, such as town halls, company-wide announcements, training sessions, and webinars. When users cannot see the option to schedule live events, it typically indicates that the live events policy has not been properly configured or assigned to those users, making the live events policy the correct administrative setting to configure for enabling this functionality.
Live events in Microsoft Teams support two different production methods: Quick start for simple presentations using Teams encoding, and External app or device for advanced production scenarios using external encoding hardware or software. The live events policy controls multiple aspects of how users can create and participate in live events. Key policy settings include whether users can schedule live events at all, which production types are allowed (Teams-produced or external encoder), whether recording is enabled for live events, whether transcription is available, who can join live events (everyone, everyone in the organization, or specific people or groups), and whether attendees can use video on demand to watch the recording after the live event concludes.
The Teams admin center provides a centralized interface for managing live events policies at the organizational level. Administrators can use the global default policy that applies to all users organization-wide, create custom policies for different user groups with varying requirements, and assign specific policies to individual users or groups for granular control. For example, an organization might create a policy that allows executive leadership and corporate communications teams to schedule live events with external encoder production, while restricting other users to Teams-produced events or not allowing them to schedule live events at all. This flexibility enables organizations to balance functionality with governance requirements.
When configuring live events policy to enable functionality for all users, the administrator should navigate to the Teams admin center, access the Meetings section and select Live events policies, review the global (Org-wide default) policy or create a new policy, ensure that «Allow scheduling» is set to On to enable users to create live events, configure the «Who can join scheduled live events» setting to determine audience scope, enable recording if the organization wants to archive or distribute live event content after the broadcast, and consider enabling transcription for accessibility compliance. The policy changes may take up to 24 hours to fully propagate across the organization, though they often take effect more quickly. Organizations should also ensure that users have appropriate licenses, as live events require specific Microsoft 365 or Office 365 licenses including Microsoft Teams and Microsoft Stream.
A) is correct because the Teams live events policy specifically controls whether users can schedule and create live events, and configuring this policy is the correct administrative action to enable live events functionality for users in the organization.
B) is incorrect because Teams meeting policy controls standard Teams meetings settings like recording, transcription, and participant features, but does not govern live events functionality, which requires separate policy configuration through live events policies.
C) is incorrect because Teams app permission policy controls which third-party and custom apps users can install and use in Teams but does not affect the ability to schedule or participate in live events, which is a native Teams feature.
D) is incorrect because Teams messaging policy controls messaging features like chat, editing messages, deleting messages, and using memes or stickers, but has no relationship to live events scheduling or functionality.
Question 107:
You need to prevent users from using personal Microsoft Teams accounts while signed in with their organizational accounts on the same device. Which of the following policies should you configure?
A) Teams external access policy or tenant restrictions
B) Teams meeting policy
C) Teams calling policy
D) Teams app setup policy
Answer: A
Explanation:
Managing account usage and preventing users from simultaneously using personal Microsoft Teams accounts alongside their organizational accounts is a governance challenge that addresses security, data leakage, and compliance concerns. Teams external access policy combined with tenant restrictions provides the administrative controls necessary to prevent users from accessing personal Teams accounts while authenticated with their organizational credentials on the same device. This capability is crucial for organizations that need to ensure corporate data remains within controlled environments and prevent unauthorized data sharing through personal accounts.
The challenge arises because Microsoft Teams supports multiple account types including organizational accounts (Azure AD accounts provided by employers) and personal accounts (Microsoft accounts or MSAs used for personal Teams usage). Users can potentially sign into Teams with both types of accounts on the same device or even within the same application session, creating risks where corporate information might inadvertently or intentionally be shared through personal channels. For example, a user might copy sensitive business information from an organizational Teams chat and paste it into a conversation in their personal Teams account, bypassing data loss prevention controls and audit logging that apply to organizational accounts.
Teams external access policy, accessed through the Teams admin center, includes settings that control how users in your organization communicate with people outside the organization. While the primary purpose is managing federation with other organizations, these policies also impact personal account usage. The key setting is «Users can communicate with Skype users» which historically has been the gateway for personal account interaction. However, more comprehensive control comes from tenant restrictions, an Azure AD feature that works in conjunction with network-level controls to prevent users from accessing services using accounts from other tenants, including personal Microsoft accounts.
Implementing tenant restrictions requires configuration at multiple levels. First, organizations must configure Azure AD tenant restrictions through conditional access or network-level proxy servers that inject specific HTTP headers (Restrict-Access-To-Tenants and Restrict-Access-Context) into outbound requests. These headers inform Microsoft cloud services, including Teams, which tenants are allowed for authentication from that network. Second, administrators should review and configure Teams external access settings to limit communication scope. Third, organizations should consider implementing endpoint management policies through Intune or Group Policy that further restrict application behavior. Fourth, network-level controls such as proxy servers or firewalls can enforce tenant restrictions for users on corporate networks. The combination of these controls creates defense-in-depth protection against unauthorized account usage.
The business rationale for preventing personal account usage in organizational contexts includes preventing data exfiltration where users might transfer sensitive information to personal accounts or uncontrolled environments, maintaining audit and compliance requirements where all business communications must be logged and retained according to organizational policies, enforcing data loss prevention policies that only apply to organizational accounts and data, preventing shadow IT scenarios where business processes occur outside IT visibility and control, and ensuring that intellectual property and business information remain within corporate governance boundaries. Organizations should clearly communicate these policies to users, explaining both the technical restrictions and the business reasoning, and provide guidance on appropriate separation between personal and professional technology use.
A) is correct because Teams external access policy combined with Azure AD tenant restrictions provides the administrative controls to prevent users from using personal Microsoft Teams accounts while signed in with organizational credentials, addressing security and data governance requirements.
B) is incorrect because Teams meeting policy controls meeting-specific settings like recording, transcription, and participant permissions but does not provide controls over account types or prevent personal account usage alongside organizational accounts.
C) is incorrect because Teams calling policy manages voice calling features including emergency calling, call forwarding, and voicemail settings but does not control account usage or prevent simultaneous use of personal and organizational accounts.
D) is incorrect because Teams app setup policy controls which apps are pinned in Teams and the app installation experience but does not prevent users from signing into personal Teams accounts or control account-level access.
Question 108:
You are configuring audio conferencing for Microsoft Teams. Users in your organization need to dial into meetings using phone numbers when they cannot join via the Teams client. Which of the following licenses is required for audio conferencing?
A) Microsoft 365 Business Standard with Audio Conferencing add-on or Microsoft 365 E5
B) Microsoft 365 Business Basic only
C) Exchange Online Plan 1 only
D) Azure Active Directory Premium only
Answer: A
Explanation:
Audio conferencing in Microsoft Teams enables users to join meetings by dialing in from traditional phone lines using PSTN (Public Switched Telephone Network) connectivity, which is essential for participants who are traveling, in locations with poor internet connectivity, or prefer the reliability of telephone audio. This functionality requires specific licensing beyond the base Teams capabilities because it involves telecommunications infrastructure, phone number provisioning, and per-minute usage charges for dial-in and dial-out calls. Understanding the licensing requirements for audio conferencing is critical for Teams administrators planning deployments and budgeting for communication solutions.
Microsoft provides audio conferencing capabilities through two primary licensing options. The first option is purchasing an Audio Conferencing add-on license, which can be added to various Microsoft 365 or Office 365 base licenses including Business Standard, Business Premium, E1, and E3. The Audio Conferencing add-on is a separate SKU that must be purchased and assigned to users who need to schedule meetings with dial-in capabilities. The second option is Microsoft 365 E5 or Office 365 E5 licenses, which include audio conferencing capabilities as part of the comprehensive E5 feature set without requiring a separate add-on purchase. Organizations with E5 licenses still need to configure audio conferencing settings, but they don’t incur additional licensing costs.
When a user has an Audio Conferencing license assigned, several capabilities become available. Meeting organizers with audio conferencing licenses can schedule meetings that include dial-in phone numbers, allowing participants to join by phone even if they don’t have internet access. The meeting invitation automatically includes local and toll-free dial-in numbers for various countries based on the organizer’s configuration and available dial-in regions. Meeting organizers can also dial out from within a meeting to add participants who are not yet connected, bringing external participants into the conversation via phone call. The service includes a pool of communication credits for usage beyond included minutes, automated meeting lobby controls for phone participants, and integration with operator connect or calling plans for more comprehensive telephony needs.
Configuration and deployment considerations for audio conferencing include assigning the appropriate licenses to users who need to organize meetings with dial-in capabilities through the Microsoft 365 admin center, configuring audio conferencing settings including default phone numbers, PIN settings, and meeting entry/exit notifications in the Teams admin center, setting up communication credits if the organization expects usage beyond included minutes or requires dial-out functionality, configuring dial-in numbers for specific regions to provide local access numbers for participants in different countries, educating users on how to schedule meetings with audio conferencing and how to manage phone participants, and monitoring usage through reporting to understand consumption patterns and costs. Organizations should also consider toll-free number provisioning for better user experience, though toll-free usage consumes communication credits at higher rates than standard dial-in numbers.
A) is correct because Microsoft 365 Business Standard requires the Audio Conferencing add-on license for dial-in functionality, while Microsoft 365 E5 includes audio conferencing capabilities natively, making either option suitable for enabling users to dial into Teams meetings using phone numbers.
B) is incorrect because Microsoft 365 Business Basic includes basic Teams functionality but does not include or support audio conferencing capabilities even with add-on licenses, as it is positioned as an entry-level collaboration license.
C) is incorrect because Exchange Online Plan 1 provides email and calendaring services but has no relationship to Teams audio conferencing functionality, which requires specific Teams and audio conferencing licensing.
D) is incorrect because Azure Active Directory Premium provides identity and access management capabilities but does not include or enable Teams audio conferencing, which requires separate Teams and audio conferencing licensing.
Question 109:
You need to create a team for a project that will exist for only three months. You want to ensure the team is automatically deleted after the project ends. Which of the following features should you configure?
A) Microsoft 365 group expiration policy
B) Teams retention policy
C) Teams meeting policy
D) Manual deletion only
Answer: A
Explanation:
Microsoft 365 group expiration policy provides automated lifecycle management for groups and teams by enabling administrators to set expiration periods after which groups are automatically deleted if not renewed. Since Microsoft Teams is built on Microsoft 365 Groups infrastructure, expiration policies that apply to groups also apply to the underlying groups that support teams. This feature is ideal for temporary projects, short-term collaborations, or any scenario where teams have a defined lifecycle and should be automatically cleaned up to prevent sprawl, reduce storage costs, and maintain organizational hygiene in the Teams environment.
Group expiration policies work by defining a lifespan for groups measured in days, such as 90 days, 180 days, or any custom value up to 365 days. When a group approaches its expiration date (typically 30 days before), the group owner receives automated email notifications prompting them to renew the group if it’s still needed. If the owner takes action to renew the group, the expiration date is extended by the full lifecycle duration from the date of renewal. If no renewal action is taken before the expiration date, the group and its associated team are automatically deleted. However, the deletion is initially soft, meaning the group can be restored within 30 days if the deletion was premature or made in error, providing a safety net against accidental data loss.
Configuration of group expiration policy is performed through Azure Active Directory (Azure AD) rather than the Teams admin center, reflecting the foundational role that Microsoft 365 Groups play in Teams architecture. Administrators access the Azure AD admin center, navigate to Groups and then Expiration settings, and can configure the policy scope to apply to all groups, specific groups, or no groups. The policy settings include the group lifetime in days, the email contact for groups without owners (important since some groups may have been created without explicit owners or the original owners may have left the organization), and whether to enable automatic renewal if the group has been actively used. Once configured, the policy applies to existing groups and newly created groups within its scope.
The business benefits of implementing group expiration policies are substantial for organizations with many temporary teams or project-based work. First, the feature reduces Teams sprawl by automatically removing obsolete teams that are no longer needed, preventing the accumulation of abandoned teams that clutter the interface and confuse users. Second, it optimizes storage costs by removing inactive content from SharePoint, Exchange, and other services associated with expired groups. Third, it improves security posture by ensuring that access to obsolete data is not inadvertently maintained through forgotten teams. Fourth, it reduces administrative burden by automating cleanup that would otherwise require manual tracking and deletion. Fifth, it enforces discipline around resource lifecycle management, encouraging teams to actively decide whether their collaboration spaces remain necessary. Organizations should carefully communicate expiration policies to users, ensuring they understand renewal procedures and the importance of responding to expiration notifications.
A) is correct because Microsoft 365 group expiration policy enables automated lifecycle management with configurable expiration periods and automatic deletion of unused teams after the specified duration, perfectly addressing the requirement for temporary teams that should be automatically removed after project completion.
B) is incorrect because Teams retention policy controls how long messages and files are retained for compliance purposes and when they can be deleted, but it does not automatically delete teams or groups themselves based on lifecycle or expiration criteria.
C) is incorrect because Teams meeting policy controls meeting features and settings like recording, transcription, and participant permissions but has no functionality related to team lifecycle management or automatic team deletion.
D) is incorrect because manual deletion requires ongoing administrative attention to identify and remove obsolete teams, is prone to human error and oversight, creates administrative burden, and fails to provide the automated lifecycle management that addresses the requirement.
Question 110:
You need to prevent users from uploading custom background images for Teams meetings while still allowing them to use the default Microsoft-provided backgrounds. Which of the following policies should you configure?
A) Teams meeting policy with custom background settings
B) Teams messaging policy
C) Teams app permission policy
D) Teams calling policy
Answer: A
Explanation:
Teams meeting policy provides comprehensive controls over meeting experiences and features, including the ability to manage background effects that users can apply during video meetings. Custom background images allow users to upload and use their own images as virtual backgrounds, which can present organizational concerns including inappropriate content, distractions, information disclosure through background elements, and inconsistent professional appearance. The Teams meeting policy includes specific settings for controlling custom background usage while still permitting users to access the Microsoft-provided default backgrounds, making it the appropriate policy for managing this aspect of the meeting experience.
Background effects in Microsoft Teams include several categories: no background (showing the actual physical environment), blur (obscuring the background while keeping the person in focus), Microsoft-provided backgrounds (curated images provided by Microsoft), and custom backgrounds (images uploaded by users from their own devices). The meeting policy settings allow administrators to control these categories independently, providing flexibility to meet organizational needs. For example, an organization might want to maintain professional appearance standards by preventing custom backgrounds while still allowing blur effects for privacy and the Microsoft-provided backgrounds that have been vetted as appropriate.
The specific policy setting for managing custom backgrounds is found within the Teams meeting policy under the «Meeting engagement» section. Administrators can configure the «Let users choose their video background» setting with options including «All background types» (allowing blur, default images, and custom images), «Blur and default images only» (preventing custom uploads but allowing Microsoft-provided options and blur), and «Blur only» (most restrictive, allowing only background blur). For the scenario described where users should not upload custom images but can use default backgrounds, the «Blur and default images only» option is the appropriate configuration.
Implementation considerations include understanding that meeting policies can be applied globally through the org-wide default policy or targeted to specific users or groups through custom policies, recognizing that policy changes may take up to 24 hours to propagate though they often apply more quickly, communicating the policy rationale to users to ensure they understand why custom backgrounds are restricted, and considering the business justification which might include maintaining professional brand standards, preventing inappropriate or distracting content, protecting confidential information that might appear in custom background images, ensuring consistent visual presentation for external meetings, or addressing bandwidth concerns since custom backgrounds may require additional processing. Organizations should balance these governance needs against user preferences for personalization and self-expression in virtual environments.
A) is correct because Teams meeting policy includes specific settings for controlling background effects including the option to allow default Microsoft-provided backgrounds and blur while preventing users from uploading custom background images, directly addressing the requirement.
B) is incorrect because Teams messaging policy controls chat and messaging features like editing messages, deleting messages, chat permissions, and read receipts but does not govern meeting features like background effects or video settings.
C) is incorrect because Teams app permission policy controls which third-party and custom apps users can install and use in Teams but does not affect meeting features like background effects, which are native Teams functionality.
D) is incorrect because Teams calling policy manages voice calling features including emergency calling, call forwarding, caller ID, and voicemail but has no relationship to meeting video features like background effects.
Question 111:
You are managing a Microsoft Teams environment. The compliance team requires that all Teams conversations and files be retained for seven years for regulatory compliance. Which of the following features should you implement?
A) Microsoft 365 retention policies for Teams
B) Teams meeting policy
C) Azure Backup
D) OneDrive retention settings only
Answer: A
Explanation:
Microsoft 365 retention policies provide comprehensive data lifecycle management capabilities specifically designed to meet organizational compliance, legal, and regulatory requirements for retaining business records. When applied to Microsoft Teams, retention policies control how long teams channel messages, private chat messages, and associated files are preserved, ensuring that organizations can meet retention obligations such as the seven-year requirement commonly mandated by financial regulations, healthcare compliance standards, and legal hold scenarios. Retention policies are the purpose-built solution for compliance-driven data retention in the Microsoft 365 ecosystem, making them the correct choice for ensuring Teams data is preserved for the required duration.
Microsoft Teams generates multiple types of content that may be subject to retention requirements, including channel messages (conversations in team channels), private chat messages (one-on-one and group chats), files shared in channels (stored in SharePoint), files shared in chats (stored in OneDrive), meeting recordings (stored in OneDrive or SharePoint), and associated metadata. Retention policies can be configured to cover these different content types with appropriate retention periods. For comprehensive compliance coverage, organizations typically need to configure retention policies for Teams channel messages, Teams chats, SharePoint sites (for channel files), and OneDrive accounts (for chat files and meeting recordings), ensuring that all Teams-related content is appropriately retained.
The configuration of retention policies for Teams involves navigating to the Microsoft Purview compliance portal (formerly Microsoft 365 compliance center), creating or modifying retention policies, selecting the Teams-specific locations including «Teams channel messages» and «Teams chats,» defining the retention period (such as seven years), specifying the retention action (retain only, retain and then delete, or delete only), and optionally configuring adaptive scopes for more granular targeting based on attributes like department, location, or group membership. The retention period can be calculated from when content was created or last modified, providing flexibility for different compliance scenarios. Once configured, the policy applies automatically to content within its scope without requiring user intervention.
Important considerations for implementing Teams retention policies include understanding that retention policies create holds on content that prevent permanent deletion even if users attempt to delete messages or files, recognizing that retained content is preserved in secure locations (Preservation Hold library for SharePoint and Exchange) that are not visible to end users but accessible to compliance administrators through eDiscovery tools, planning for storage costs associated with long-term retention of potentially large volumes of Teams data, implementing appropriate eDiscovery procedures for compliance officers to search and export retained content when needed for legal or audit purposes, educating users that retention policies may prevent them from deleting content they consider obsolete, and regularly reviewing retention policies to ensure they remain aligned with regulatory requirements and organizational changes. Organizations subject to multiple regulatory frameworks may need to implement multiple retention policies with different settings for different user groups or content types.
A) is correct because Microsoft 365 retention policies specifically provide compliance-focused data preservation capabilities for Teams conversations and files, enabling organizations to meet regulatory requirements for retaining content for specified periods like seven years.
B) is incorrect because Teams meeting policy controls meeting features and user experiences during meetings but has no functionality related to content retention, compliance holds, or preservation of messages and files for regulatory purposes.
C) is incorrect because Azure Backup is designed for infrastructure and workload protection of Azure resources and is not applicable to Microsoft 365 services like Teams, which have their own compliance and retention capabilities through Microsoft Purview.
D) is incorrect because OneDrive retention settings alone would only cover files stored in OneDrive for Business and would not address Teams channel messages, private chat messages, or files stored in SharePoint team sites, providing incomplete compliance coverage.
Question 112:
You need to allow external users from specific domains to participate in Teams meetings but prevent them from initiating chats with internal users. Which of the following should you configure?
A) External access with domain-specific allow list
B) Guest access only
C) Teams meeting policy only
D) Disable all external communication
Answer: A
Explanation:
External access in Microsoft Teams provides federation capabilities that enable users in your organization to communicate with people outside your organization through Teams, allowing cross-organizational collaboration while maintaining security and control. External access (also called federation) is distinct from guest access in that external users remain within their own organization’s Teams tenant and use their own organizational credentials, rather than being added as guests to your tenant. When you need to allow external users from specific domains to participate in Teams meetings while preventing them from initiating chats with internal users, configuring external access with domain-specific allow lists and appropriate settings provides the precise control required.
External access operates through federation between Teams tenants or with Skype for Business organizations. When external access is enabled and configured, users from federated organizations can search for and communicate with users in your organization without requiring guest accounts or invitations. The external access configuration includes several key settings: whether external access is enabled at all, whether users from specific domains are allowed or blocked, whether external Teams accounts can communicate with your users, and what types of interactions are permitted (meetings, chat, calling). For the scenario described, administrators need to enable external access, create an allow list containing only the specific domains from which external users should be permitted, and configure the settings to allow meeting participation while restricting chat initiation.
The Teams admin center provides the interface for managing external access through the «Manage external access» section under Users > External access. Administrators can choose between three main configuration approaches: allow all external domains (least restrictive), allow only specific external domains (recommended for controlled federation), or block all external domains except specific ones. For organizations that want tight control over which external entities can communicate with their users, the allow list approach is most appropriate. Administrators add specific domain names (like partner.com or vendor.org) to the allow list, and only users from those domains will be able to interact with internal users according to the configured permissions.
The distinction between external access and guest access is critical for understanding which feature to use for different scenarios. External access is best for organization-to-organization federation where external users maintain their own identities and remain in their own tenants, external users need limited interactions like meetings or occasional chats, organizations want to avoid managing guest accounts, and there are established business relationships with specific partner organizations. Guest access is more appropriate when external users need deeper integration with teams and channels, access to specific team resources and files is required, external users don’t have their own Teams licenses or organizations, or long-term collaboration within a specific team is needed. In the described scenario where external users should participate in meetings but have restricted chat capabilities, external access with its more granular communication controls is the appropriate choice.
A) is correct because external access with domain-specific allow lists enables controlled federation with specific external organizations, allowing their users to participate in Teams meetings while providing granular controls over other communication types like chat initiation, perfectly matching the requirements.
B) is incorrect because guest access adds external users as guests to your tenant providing them with team membership and broader access, and does not provide the specific control over allowing meeting participation while preventing chat initiation that external access federation offers.
C) is incorrect because Teams meeting policy controls meeting features and experiences but does not manage whether external users from specific domains can communicate with your organization, which is controlled through external access configuration.
D) is incorrect because disabling all external communication would prevent external users from participating in Teams meetings entirely, which contradicts the requirement that external users should be able to participate in meetings even while chat initiation is restricted.
Question 113:
You are configuring Microsoft Teams Rooms devices for conference rooms in your organization. You need to ensure that Teams Rooms devices automatically accept meeting invitations and join scheduled meetings. Which of the following should you configure?
A) Room mailbox with automatic processing policies
B) User mailbox with manual acceptance
C) Shared mailbox without calendar permissions
D) Distribution list
Answer: A
Explanation:
Microsoft Teams Rooms devices require specialized account configuration to function properly as meeting room resources that can be scheduled, automatically accept appropriate meeting requests, and seamlessly join scheduled Teams meetings without manual intervention. A room mailbox with properly configured automatic processing policies provides the foundational identity and calendar automation required for Teams Rooms devices. Room mailboxes are a specific type of Exchange resource mailbox designed for conference rooms and meeting spaces, and they include built-in capabilities for calendar processing, meeting acceptance, and resource scheduling that are essential for Teams Rooms device functionality.
Room mailboxes differ from regular user mailboxes in several important ways. They are designed to be associated with physical meeting spaces rather than individual people, include automatic calendar processing that can accept or decline meeting requests based on availability and configured policies, support resource scheduling features like booking policies and resource delegates, integrate with Teams Rooms devices to provide automatic meeting join capabilities, and include properties specific to meeting rooms such as capacity, location, and available equipment. When a room mailbox is created for a Teams Rooms device, it becomes the identity that the device uses to sign into Teams and access its calendar for scheduled meetings.
The automatic processing policies for room mailboxes are configured through the Exchange Online PowerShell module using the Set-CalendarProcessing cmdlet with various parameters. Key settings include AutomateProcessing set to «AutoAccept» which enables automatic processing of meeting requests without human intervention, AddOrganizerToSubject set to $false to prevent the organizer’s name from being added to the meeting subject line, DeleteComments set to $true to remove meeting body text from processed requests, DeleteSubject set to $false to preserve the meeting subject, and RemovePrivateProperty set to $false to maintain meeting privacy settings. Additional parameters control whether conflicts are allowed, how far in advance bookings can be made, whether processing of external meeting requests is permitted, and other scheduling behaviors specific to organizational requirements.
For Microsoft Teams Rooms devices specifically, additional configuration beyond the basic room mailbox setup is necessary for complete functionality. The account must be licensed with a Microsoft Teams Rooms license (different from regular user licenses), assigned appropriate calling and audio conferencing capabilities if phone dial-in or dial-out is required, configured with modern authentication and appropriate conditional access policies that accommodate the device’s sign-in patterns, and potentially configured with password policies that support the longer password expiration periods typical for device accounts. The Teams Rooms device itself must be configured with the room mailbox credentials during its setup process, enabling it to sign into Teams, access the room mailbox calendar, and automatically join scheduled meetings at the appropriate times. Organizations should also consider physical security of the credentials, device management through Microsoft Endpoint Manager or Teams Rooms Pro management, and monitoring of device health through Teams admin center reporting.
A) is correct because room mailboxes with automatic processing policies provide the calendar automation, automatic meeting acceptance, and integration capabilities that Microsoft Teams Rooms devices require to function properly as conference room resources that automatically join scheduled meetings.
B) is incorrect because user mailboxes with manual acceptance would require human intervention to accept meeting invitations, which defeats the purpose of automatic processing for a conference room device and would result in the Teams Rooms device not having meetings on its calendar to join automatically.
C) is incorrect because shared mailboxes do not include calendar functionality or room scheduling capabilities, and they lack the automatic processing features necessary for Teams Rooms devices to automatically accept meetings and manage room bookings.
D) is incorrect because distribution lists are email forwarding mechanisms for sending messages to multiple recipients simultaneously and have no calendar, no room scheduling capabilities, and no functionality related to Teams Rooms devices or meeting management.
Question 114:
You need to prevent users in your organization from installing third-party apps from the Microsoft Teams app store. However, you still want them to be able to use Microsoft-provided apps. Which of the following policies should you configure?
A) Teams app permission policy
B) Teams meeting policy
C) Teams messaging policy
D) Teams calling policy
Answer: A
Explanation:
Teams app permission policy provides granular control over which applications users can install and use within Microsoft Teams, enabling administrators to balance the benefits of app extensibility with security, compliance, and governance requirements. The app ecosystem in Teams includes Microsoft apps (developed and published by Microsoft), third-party apps (developed by external vendors and published in the Teams app store), and custom apps (developed internally by organizations for their specific needs). When an organization needs to control which categories of apps users can access, the Teams app permission policy offers the precise configuration options required to allow some app types while blocking others.
The Teams app store contains thousands of applications that extend Teams functionality for various business scenarios including project management, CRM integration, customer support, productivity tools, collaboration enhancers, and industry-specific solutions. While this ecosystem provides tremendous value by enabling customization and integration, it also presents governance challenges. Organizations may want to restrict third-party app installation for several reasons: security concerns about apps accessing organizational data, compliance requirements limiting data sharing with external services, desire to control and standardize the tools used across the organization, need to evaluate and approve apps before deployment, concerns about app quality or support, or licensing and cost management for premium apps.
Teams app permission policy is configured through the Teams admin center under Teams apps > Permission policies. The global (Org-wide default) policy applies to all users unless they are assigned a custom policy. Within each permission policy, administrators can configure three main categories of apps: Microsoft apps (all apps published by Microsoft), Third-party apps (all apps published in the Teams app store by external vendors), and Custom apps (apps developed by or for your organization). For each category, administrators can choose «Allow all apps» (permitting any app in that category), «Allow specific apps and block all others» (creating an allow list), or «Block specific apps and allow all others» (creating a block list). For the scenario described where users should not install third-party apps but should still access Microsoft apps, the appropriate configuration is to allow all Microsoft apps while blocking all third-party apps.
Advanced app management capabilities include allowing or blocking individual apps by name regardless of category, creating custom policies for different user groups or departments with varying app permissions, using app setup policy (a separate but related policy) to control which apps are pinned in users’ Teams interface and whether users can add apps themselves, monitoring app usage through Teams admin center analytics to understand which apps are being used and by whom, managing app settings for specific apps to control their permissions and capabilities, and reviewing new app requests where users can request access to blocked apps allowing administrators to evaluate and potentially approve them. Organizations should establish an app governance framework that defines approval processes for new apps, conducts security and compliance reviews, documents approved and blocked apps, communicates app policies to users, and regularly reviews app usage and permissions to ensure policies remain appropriate.
A) is correct because Teams app permission policy specifically controls which categories and individual apps users can install and use in Teams, providing the capability to allow Microsoft apps while blocking third-party apps exactly as required.
B) is incorrect because Teams meeting policy controls meeting features and experiences like recording, transcription, and participant settings but does not govern app installation or usage permissions in Teams.
C) is incorrect because Teams messaging policy controls chat and messaging features like editing, deleting messages, priority notifications, and read receipts but does not manage app permissions or installation rights.
D) is incorrect because Teams calling policy manages voice calling features including emergency calling, call forwarding, and voicemail settings but has no relationship to app installation or app usage permissions in Teams.
Question 115:
You are implementing Microsoft Teams Phone System. Users need to make calls to external phone numbers. Which of the following must you configure to enable outbound PSTN calling?
A) Calling Plan, Operator Connect, or Direct Routing
B) Teams meeting policy only
C) Teams messaging policy only
D) No additional configuration required
Answer: A
Explanation:
Microsoft Teams Phone System provides cloud-based Private Branch Exchange (PBX) capabilities including call control, voicemail, call queues, and auto attendants. However, Teams Phone System alone only enables internal calling between Teams users within the organization; it does not include connectivity to the Public Switched Telephone Network (PSTN) required for making calls to external phone numbers, mobile phones, and traditional landlines. To enable outbound and inbound PSTN calling, organizations must implement one of three PSTN connectivity options: Microsoft Calling Plans, Operator Connect, or Direct Routing. Understanding these options and their implementation requirements is essential for Teams administrators deploying voice solutions.
Microsoft Calling Plans is the most straightforward PSTN connectivity option where Microsoft acts as the telecommunications carrier, providing phone numbers, PSTN connectivity, and handling the telecommunications infrastructure. Calling Plans are available in many (but not all) countries and include Domestic Calling Plans for calls within a country and International Calling Plans for worldwide calling. To implement Calling Plans, organizations purchase Calling Plan licenses, assign them to users along with Phone System licenses, acquire phone numbers through Microsoft, assign phone numbers to users, and configure emergency addresses for regulatory compliance. Microsoft handles all the underlying telephony infrastructure, making this option the simplest to deploy and manage but limiting availability to supported countries and potentially offering less flexibility than other options.
Operator Connect enables organizations to use existing or new telecom carriers that have partnered with Microsoft and integrated their networks with Teams. This option provides flexibility to choose preferred carriers, potentially maintain existing telecom relationships, and access broader geographic coverage including locations where Microsoft Calling Plans aren’t available. Implementation involves selecting an Operator Connect partner.
Microsoft list, working with that partner to establish service and acquire phone numbers, enabling the operator in the Teams admin center, and assigning phone numbers to users. The operator handles the PSTN connectivity while Microsoft provides the Teams Phone System features, creating a division of responsibility that can offer benefits like local carrier expertise, potential cost advantages, and regulatory compliance support.
Direct Routing provides the most flexible but technically complex option by enabling organizations to connect their own Session Border Controllers (SBCs) to Teams Phone System, allowing use of existing telecom contracts, on-premises voice infrastructure, or third-party PSTN providers. Direct Routing is essential for organizations with significant investments in existing telephony infrastructure, operating in locations without Calling Plans or preferred Operator Connect partners, requiring specific features or integrations not available through other options, or wanting complete control over telephony routing and costs. Implementation requires deploying or configuring SBCs (physical or virtual appliances that connect to Teams and translate protocols), establishing certified SBCs that Microsoft has validated for Teams interoperability, configuring voice routing in Teams admin center to define how calls are routed through SBCs, creating dial plans for number normalization, and configuring voice policies for user permissions and call routing. Organizations must also manage ongoing maintenance, troubleshooting, and ensure SBCs remain updated and properly configured.
A) is correct because enabling outbound PSTN calling from Teams Phone System requires implementing one of the three PSTN connectivity options—Calling Plans, Operator Connect, or Direct Routing—as Phone System alone only provides internal calling capabilities without external PSTN access.
B) is incorrect because Teams meeting policy controls meeting features and does not provide or configure PSTN connectivity, which requires separate telephony infrastructure through Calling Plans, Operator Connect, or Direct Routing.
C) is incorrect because Teams messaging policy controls chat and messaging features and has no relationship to voice calling capabilities or PSTN connectivity configuration required for external calling.
D) is incorrect because additional configuration is absolutely required to enable external calling; Teams Phone System alone does not include PSTN connectivity and organizations must explicitly implement one of the three PSTN connectivity options to enable external calls.
Question 116:
You need to create a team that only specific people in the organization can discover and join. Which of the following privacy settings should you configure when creating the team?
A) Private team
B) Public team
C) Org-wide team
D) Hidden team (not a valid option)
Answer: A
Explanation:
Microsoft Teams provides three primary team privacy settings that control who can discover and join teams, enabling organizations to balance collaboration openness with appropriate access control and information security. Understanding these privacy settings is essential for creating teams with appropriate visibility and access controls that align with the sensitivity of information, the nature of collaboration, and organizational governance requirements. When a team should only be discoverable and joinable by specific people rather than being broadly accessible across the organization, a private team configuration provides the required access control.
Private teams represent the most restrictive visibility option available in Teams and are the default privacy setting when creating new teams. In a private team, the team name and channels are not visible in the Teams directory or search results to users who are not members. Only team owners can add members to private teams, ensuring controlled access to team resources. Users cannot request to join private teams through the Teams interface; they must be explicitly added by a team owner. This privacy setting is appropriate for teams handling confidential information, department-specific or project-specific collaboration where access should be carefully controlled, executive leadership teams, compliance or legal teams dealing with sensitive matters, or any scenario where team content visibility needs to be limited to a specific, defined group of people.
Public teams provide broader discovery and access, appearing in the Teams directory where any user in the organization can search for and find them. Users can join public teams on their own initiative without requiring approval from team owners, though organization-level policies can restrict public team creation or joining based on user attributes. Public teams are appropriate for organizational initiatives with broad relevance, community of practice or interest groups that welcome wide participation, company-wide announcements or information sharing, and scenarios where maximum collaboration and open communication are desired. However, public teams are not suitable when information confidentiality, access control, or limited membership are requirements.
Org-wide teams are a special category that automatically include every person in the organization and automatically add new users as they join the organization. These teams are limited to organizations with fewer than 10,000 users due to scale considerations, and only global administrators can create them. Org-wide teams are public by nature since every user is automatically a member. They are appropriate for company-wide announcements, universal policies or procedures, and organization-wide initiatives where literally every employee should participate. The automatic membership maintenance makes org-wide teams useful for scenarios requiring guaranteed universal reach, but they are not suitable when selective membership or confidential information is involved.
Team privacy can be configured during team creation through the Teams client or Teams admin center. After creation, team owners can modify the privacy setting (converting between public and private) through team settings, though this should be done thoughtfully as changing privacy settings can affect user expectations and access patterns. Organizations should establish governance around team privacy including guidelines for when each privacy setting is appropriate, approval processes for public teams if control is desired, naming conventions that might indicate team privacy, and regular reviews of team settings to ensure privacy configurations remain appropriate as team purposes evolve. Clear communication to team creators about privacy implications helps ensure teams are configured appropriately from the beginning.
A) is correct because private teams restrict discovery and access to specific members added by team owners, preventing general organizational visibility and ensuring that only designated people can find and join the team, which aligns with the requirement for controlled access.
B) is incorrect because public teams are discoverable by all users in the organization and allow anyone to join without owner approval, which contradicts the requirement that only specific people should be able to discover and join the team.
C) is incorrect because org-wide teams automatically include every person in the organization and are public, which is the opposite of the requirement for selective membership where only specific people can discover and join.
D) is incorrect because «hidden team» is not a valid privacy configuration option in Microsoft Teams; the actual privacy settings available are private, public, and org-wide, with private providing the controlled access described in the requirement.
Question 117:
You are managing Teams for a large organization. The compliance team needs to search for specific messages sent in private chats and channel conversations as part of a legal investigation. Which of the following tools should you use?
A) Microsoft Purview eDiscovery
B) Teams meeting policy
C) Azure AD audit logs only
D) Teams usage reports
Answer: A
Explanation:
Microsoft Purview eDiscovery (formerly Microsoft 365 compliance eDiscovery) provides comprehensive legal and compliance tools for identifying, preserving, collecting, reviewing, and exporting electronic information stored across Microsoft 365 services including Microsoft Teams. When organizations face legal investigations, regulatory inquiries, or internal compliance requirements necessitating the search and retrieval of specific communications, eDiscovery offers the specialized capabilities required to conduct these searches across Teams private chats, channel conversations, files, and associated content while maintaining legal defensibility and chain-of-custody integrity.
Microsoft Purview offers two levels of eDiscovery functionality. Content Search provides basic search and export capabilities available to all Microsoft 365 organizations, enabling authorized compliance personnel to search across Exchange mailboxes (where Teams chat messages are stored), SharePoint sites (where Teams channel files reside), OneDrive accounts, and Teams channels. Content Search allows searching by keywords, date ranges, participants, and other criteria, then exporting the results for review. For more sophisticated legal scenarios, eDiscovery (Premium) provides advanced case management, custodian identification and holds, sophisticated collection and review workflows, analytics and machine learning-assisted document review, and export in legal industry-standard formats. Organizations choose between these options based on complexity of legal requirements, volume of data involved, and available licensing.
The architecture underlying Teams eDiscovery searches is important for understanding what content can be found and where it resides. Teams channel messages are stored in a hidden group mailbox associated with each team, making them searchable through Exchange-based eDiscovery queries. Teams private chats (one-on-one and group chats) are stored in the Exchange mailboxes of the individual participants, so searching for private chat messages requires including relevant user mailboxes in the search scope. Files shared in Teams channels are stored in the team’s SharePoint site document library, while files shared in private chats are stored in OneDrive for Business accounts. Meeting recordings, depending on configuration, are stored in either OneDrive or SharePoint. This distributed storage model means comprehensive eDiscovery searches must include multiple content locations.
Implementing eDiscovery searches requires appropriate permissions and careful execution. Compliance administrators, eDiscovery managers, and eDiscovery administrators have various levels of access to eDiscovery tools through role-based access control in Microsoft Purview. Creating an eDiscovery case provides a container for organizing related searches, holds, and exports associated with a particular legal matter. Content locations must be specified including which users, groups, sites, or teams to search. Search queries use Keyword Query Language (KQL) supporting Boolean operators, property restrictions, and various search conditions. Legal holds can be placed on identified content to prevent deletion during the investigation period. Search results can be previewed, refined, and eventually exported with detailed metadata for legal review. Organizations should establish clear procedures for eDiscovery requests, implement appropriate access controls to limit who can conduct searches, maintain audit trails of eDiscovery activities, and ensure compliance with data protection regulations when handling discovered content.
A) is correct because Microsoft Purview eDiscovery provides specialized legal and compliance search capabilities designed specifically for identifying and preserving Teams messages and content across private chats and channels as required for legal investigations and regulatory compliance.
B) is incorrect because Teams meeting policy controls meeting features and user experience settings but has no functionality for searching historical messages or content, which requires dedicated compliance and eDiscovery tools.
C) is incorrect because Azure AD audit logs track administrative activities, sign-ins, and directory changes but do not provide access to the content of Teams messages or enable keyword searches of conversations required for legal investigations.
D) is incorrect because Teams usage reports provide analytics on adoption, activity, and usage patterns but do not offer content search capabilities or the ability to locate specific messages, which requires eDiscovery tools designed for legal and compliance purposes.
Question 118:
You need to configure calling policies to prevent specific users from making international calls while allowing them to make domestic calls. Which of the following should you configure?
A) Teams calling policy with international calling restrictions
B) Teams meeting policy
C) Teams messaging policy
D) Teams app permission policy
Answer: A
Explanation:
Teams calling policy provides granular controls over voice calling features and permissions for users in your organization, enabling administrators to define who can make different types of calls, use specific calling features, and access various voice capabilities. When implementing Teams Phone System, organizations often need to apply different calling permissions to different user groups based on role requirements, cost control considerations, or security policies. Restricting international calling for specific users while maintaining domestic calling capabilities is a common governance requirement that is directly addressed through Teams calling policy configuration with appropriate international calling restrictions.
Teams calling policy includes numerous settings that control calling behavior. Key settings relevant to call restrictions include: making private calls (whether users can make calls at all), call forwarding and simultaneous ringing options, voicemail availability, inbound call blocking rules, calling party name (caller ID) settings, and critically for this scenario, whether users can make international calls. The international calling setting specifically controls whether users can place calls to phone numbers outside their home country, enabling organizations to restrict international calling to reduce telecommunications costs, prevent unauthorized international calls, or limit calling scope based on user roles and responsibilities.
Configuration of calling policies is performed through the Teams admin center under Voice > Calling policies. Organizations can use the global (Org-wide default) policy that applies to all users who aren’t assigned a custom policy, or create custom calling policies for different user groups with varying requirements. For the scenario described where specific users should not make international calls, administrators would create a custom calling policy with «Allow international calling» set to Off while ensuring «Allow private calling» remains On to permit domestic calls. This custom policy would then be assigned to the specific users who should have international calling restrictions, while other users could retain the default policy or be assigned policies with international calling enabled.
The implementation approach for call restriction requirements typically involves identifying user groups with different calling needs such as executives and sales teams who need international calling, general office workers who primarily need domestic calling, contractors or temporary staff with more limited calling requirements, or customer service representatives who need inbound call capabilities but restricted outbound calling. Organizations should document the business justification for different calling permissions, establish processes for requesting exceptions or policy changes, monitor calling patterns and costs to verify policies are effective, educate users about calling restrictions and alternatives like Teams-to-Teams calling for international communication, and implement appropriate dial plans and voice routing that support the policy restrictions. Additional cost controls might include communication credits monitoring, usage alerts for approaching thresholds, and regular review of calling activity through Teams admin center analytics.
A) is correct because Teams calling policy includes specific settings for international calling restrictions that can be disabled for specific users while maintaining their ability to make domestic calls, directly addressing the requirement for granular calling permission control.
B) is incorrect because Teams meeting policy controls meeting features like recording, transcription, and participant permissions but does not govern voice calling capabilities or restrict international versus domestic calling permissions.
C) is incorrect because Teams messaging policy controls chat and messaging features like editing, deleting messages, and using communication features like memes, but has no relationship to voice calling permissions or call restrictions.
D) is incorrect because Teams app permission policy controls which applications users can install and use in Teams but does not affect calling capabilities, which are controlled through separate voice-specific policies.
Question 119:
You are deploying Microsoft Teams for a healthcare organization that must comply with HIPAA regulations. You need to ensure that patient discussions in Teams are compliant. Which of the following should you implement?
A) Compliance features including retention policies, DLP, and eDiscovery
B) Teams meeting policy only
C) Public teams for patient discussions
D) No additional compliance configuration
Answer: A
Explanation:
Healthcare organizations handling protected health information (PHI) under HIPAA (Health Insurance Portability and Accountability Act) regulations must implement comprehensive compliance controls to protect patient privacy, maintain data security, ensure audit trails, and meet stringent regulatory requirements. Microsoft Teams can be used for healthcare communications including patient discussions when properly configured with appropriate compliance features. A comprehensive compliance implementation including retention policies to preserve communications for required periods, Data Loss Prevention (DLP) policies to prevent unauthorized PHI disclosure, eDiscovery capabilities for audit and investigation, encryption for data protection, and audit logging for accountability provides the multi-layered compliance framework necessary for HIPAA compliance.
HIPAA requires covered entities (healthcare providers, health plans, healthcare clearinghouses) and their business associates to implement administrative, physical, and technical safeguards to protect PHI. When using Teams for patient-related communications, several specific requirements must be addressed. The confidentiality requirement mandates that PHI is protected against unauthorized access, necessitating access controls, encryption, and DLP policies. The integrity requirement ensures PHI is not improperly altered or destroyed, requiring retention policies and version control. The availability requirement ensures PHI is accessible when needed for patient care, requiring high availability and disaster recovery capabilities. Additionally, HIPAA requires comprehensive audit trails showing who accessed PHI and what actions were taken, necessitating audit logging and monitoring capabilities.
Retention policies in Microsoft Purview enable organizations to preserve Teams conversations, messages, and files for required retention periods, which for HIPAA can range from six years to indefinitely depending on state laws and the type of records. Retention policies ensure that even if users delete messages containing PHI, the content is preserved in secure compliance locations accessible to authorized personnel for audit or legal purposes. This satisfies HIPAA’s documentation and record retention requirements.
Data Loss Prevention (DLP) policies detect when messages or files contain sensitive information like patient names, medical record numbers, diagnosis codes, or other PHI identifiers, and can automatically block sharing, encrypt content, or alert compliance personnel. DLP policies help prevent accidental or intentional unauthorized PHI disclosure, supporting HIPAA’s security rule requirements. Custom sensitive information types can be configured to detect organization-specific identifiers or formats used in the healthcare environment.
eDiscovery capabilities enable authorized compliance and legal personnel to search for and export specific communications when needed for audits, investigations, or legal proceedings, supporting HIPAA’s requirement for producing protected information in response to legitimate requests. Microsoft’s compliance with various industry certifications including HIPAA Business Associate Agreement (BAA) coverage provides the contractual and technical foundation for using Teams in healthcare settings, though organizations must still implement appropriate configurations and policies to achieve compliance.
Additional compliance and security considerations for healthcare Teams deployments include implementing appropriate access controls through Azure AD conditional access and MFA to ensure only authorized personnel access PHI, configuring private teams rather than public teams for patient discussions to limit information exposure, enabling Microsoft Purview sensitivity labels to classify and protect PHI-containing content, implementing information barriers to prevent communication between specific groups where required by regulations, providing staff training on HIPAA requirements and appropriate Teams usage, conducting regular compliance audits and risk assessments, and documenting all compliance configurations and procedures. Organizations should work with legal counsel and compliance experts to ensure their Teams implementation meets all applicable regulatory requirements.
A) is correct because HIPAA compliance for Teams requires comprehensive implementation of multiple compliance features including retention policies for record preservation, DLP for PHI protection, eDiscovery for audit capabilities, encryption, and audit logging—not just a single feature or policy.
B) is incorrect because Teams meeting policy controls meeting features and user experience but does not provide the compliance, data protection, retention, or audit capabilities required for HIPAA compliance in healthcare communications.
C) is incorrect because public teams allow broad organizational access and are completely inappropriate for patient discussions containing PHI, which require restricted access through private teams with carefully controlled membership.
D) is incorrect because HIPAA compliance absolutely requires additional compliance configuration beyond default Teams settings; organizations handling PHI must implement specific retention, DLP, security, and audit controls to meet regulatory requirements.
Question 120:
You need to configure Teams so that all meetings automatically include captions for accessibility compliance. Which of the following policies should you configure?
A) Teams meeting policy with live captions settings
B) Teams messaging policy
C) Teams calling policy
D) Teams app setup policy
Answer: A
Explanation:
Accessibility in Microsoft Teams is a critical consideration for ensuring inclusive collaboration environments that accommodate users with disabilities, comply with accessibility regulations such as the Americans with Disabilities Act (ADA) and Section 508, and support diverse user needs. Live captions provide real-time text transcription of spoken audio during meetings, enabling participants who are deaf or hard of hearing to follow conversations, supporting participants in noisy environments or situations where audio cannot be used, and assisting non-native language speakers in understanding discussions. The Teams meeting policy includes specific settings for controlling caption availability and behavior, making it the appropriate policy for implementing accessibility-focused caption requirements.
Teams live captions use speech recognition technology to generate real-time transcription of meeting audio, displaying the text in a caption window that participants can enable or disable according to their needs. The captions appear with minimal delay, typically just seconds behind the spoken words, and include speaker identification to help participants follow multi-person conversations. While captions are not perfect and may occasionally include transcription errors, they provide substantial accessibility value and are continuously improving as speech recognition technology advances. Microsoft Teams supports live captions in numerous languages, with availability varying by tenant configuration and regional settings.
The Teams meeting policy controls several caption-related settings that administrators can configure. The primary setting is «Live captions» which can be set to «Disabled» (captions not available), «Enabled but not default» (participants can turn captions on, but they are off by default), or potentially future settings that make captions enabled by default. As of current Teams capabilities, administrators can enable the caption feature but cannot force captions to be displayed by default for all participants; individual users control whether they view captions during meetings. However, meeting organizers can encourage caption usage, and organizational policies can establish expectations around accessibility. Organizations pursuing full accessibility compliance typically enable captions and provide user training on accessing and using this feature.
Additional accessibility considerations for Teams meeting implementations include enabling meeting transcripts which provide post-meeting searchable text versions of conversations complementing real-time captions, configuring meeting recording policies to ensure meetings can be reviewed by participants who need additional time to process information, implementing screen reader support through proper Teams client configuration and user training, ensuring all shared content meets accessibility standards with appropriate alt text, proper heading structure, and readable fonts, providing sign language interpretation capabilities for meetings requiring this accommodation, testing accessibility features regularly to ensure they function properly, training meeting organizers on accessibility best practices including describing visual content verbally, speaking clearly, and allowing time for caption delay, and establishing organizational processes for requesting and providing reasonable accommodations. Organizations should also consider third-party accessibility services that integrate with Teams for enhanced captioning, translation, or interpretation services when built-in capabilities are insufficient for specific requirements.
A) is correct because Teams meeting policy includes live captions settings that control whether captions are available in meetings, enabling administrators to ensure this accessibility feature is enabled organization-wide to support compliance requirements and inclusive collaboration.
B) is incorrect because Teams messaging policy controls chat and messaging features but has no settings related to meeting captions or accessibility features, which are configured through meeting-specific policies.
C) is incorrect because Teams calling policy manages voice calling features and permissions but does not control meeting accessibility features like captions, which are separate from calling capabilities.
D) is incorrect because Teams app setup policy controls which apps are pinned in the Teams interface and app installation behavior but does not manage meeting features like captions, which are configured through meeting policies.