Visit here for our full Microsoft MS-700 exam dumps and practice test questions.
Q161
Your company has a Microsoft 365 subscription that uses Microsoft Teams. You need to ensure that users can schedule meetings that allow external participants to join via a web browser without requiring authentication. What should you configure?
A) Teams meeting policies
B) External access settings
C) Guest access settings
D) Meeting settings for anonymous users
Answer: D
Explanation:
This question addresses the scenario where an organization needs to enable external participants to join Microsoft Teams meetings through a web browser without requiring them to authenticate or sign in. This is a common requirement in business environments where companies frequently collaborate with external partners, clients, or vendors who may not have Microsoft 365 accounts or Teams installed on their devices. The correct answer involves configuring settings that specifically control anonymous user participation in meetings. Meeting settings for anonymous users control whether people who are not signed in to Teams can join meetings in your organization. When you enable this setting, anonymous users receive a meeting link and can join the meeting by entering their name without any authentication requirements. They join through the Teams web client and have limited functionality compared to authenticated users, but they can participate in audio, video, chat, and screen sharing based on the meeting organizer’s permissions. This setting is managed in the Teams admin center under Meetings and then Meeting settings. Teams meeting policies are incorrect because while they control various aspects of meeting behavior and functionality, they primarily govern what features are available to your organization’s users during meetings rather than access controls for unauthenticated external participants. External access settings are incorrect because they control federation with other organizations that use Microsoft Teams or Skype for Business. External access requires that the external users have their own Microsoft 365 accounts and are signed in to Teams, which is different from anonymous access. Guest access settings are incorrect because guest access is designed for adding people from outside your organization to teams and channels for ongoing collaboration. Guest access requires inviting users as guests to your Azure AD tenant, and they must authenticate using their email address. This is not the same as allowing anonymous, unauthenticated access to meetings through a web browser.
Q162
You are a Microsoft Teams administrator for your organization. Users report that they cannot see the option to record meetings. You need to enable meeting recording for all users in the organization. What should you do?
A) Configure the meeting policies in the Teams admin center
B) Enable guest access in the Teams admin center
C) Modify the external access settings
D) Configure the messaging policies in the Teams admin center
Answer: A
Explanation:
This question focuses on enabling meeting recording functionality for users within a Microsoft Teams environment. Meeting recording is a valuable feature that allows participants to capture audio, video, and screen sharing activity during Teams meetings for later review, training purposes, compliance requirements, or for sharing with attendees who could not join the live session. The ability to record meetings is controlled through Teams meeting policies, which are configured in the Teams admin center and can be applied globally or to specific users and groups. Meeting policies in Teams provide administrators with granular control over various meeting features and capabilities. To enable meeting recording, you need to access the Teams admin center, navigate to Meetings and then Meeting policies, and configure the appropriate policy. Within the meeting policy settings, there is a specific option called “Cloud recording” that controls whether users can record meetings. When this setting is turned on, meeting organizers and authorized participants can start recording meetings to the cloud, and the recordings are stored in Microsoft Stream or OneDrive and SharePoint depending on your organization’s configuration. You can create custom meeting policies for different user groups if you need varying levels of control, or you can modify the global policy to apply recording permissions organization-wide. It is important to note that only authenticated users with appropriate permissions can record meetings, and the recording feature respects other policy settings such as who can bypass the lobby. Guest access settings are incorrect because they control whether people from outside your organization can be invited as guests to join teams and channels. Guest access determines the permissions and capabilities that guests have within your Teams environment, such as whether they can create channels, use chat, or access files. However, guest access does not control meeting recording capabilities for your organization’s users. Even if guest access is enabled, this does not affect whether internal users can record meetings. External access settings are incorrect because they manage federation with other Microsoft 365 organizations and allow users from different domains to communicate with each other through Teams. External access enables finding, calling, and chatting with users from external organizations, but it does not govern meeting recording functionality for your own users. Messaging policies are incorrect because they control chat and messaging features in Teams, such as whether users can delete sent messages, use chat, edit messages, use Giphys, memes, and stickers in conversations. Messaging policies do not affect meeting-related features like recording capabilities.
Q163
Your organization uses Microsoft Teams for collaboration. You need to prevent users from using third-party cloud storage services like Dropbox and Google Drive within Teams. What should you configure?
A) App permission policies
B) App setup policies
C) Messaging policies
D) Meeting policies
Answer: A
Explanation:
This question addresses the need to control which third-party applications and services users can access within Microsoft Teams. Organizations often have compliance, security, or data governance requirements that necessitate restricting the use of external cloud storage services to prevent data leakage or ensure that all corporate data remains within approved and managed systems. Microsoft Teams provides robust app management capabilities that allow administrators to control which apps users can install and use within the Teams environment. App permission policies are the correct configuration for controlling access to third-party applications in Teams. These policies allow administrators to specify which apps are allowed or blocked for users in the organization. You can create app permission policies that block specific apps, allow only specific apps, or block all apps except those explicitly allowed. To prevent users from accessing third-party cloud storage services like Dropbox or Google Drive, you would configure an app permission policy in the Teams admin center by navigating to Teams apps and then Permission policies. Within the policy, you can block specific apps by searching for them and adding them to the blocked apps list, or you can set a more restrictive policy that blocks all third-party apps by default and only allows Microsoft apps or specific approved applications. App permission policies can be assigned globally to all users or to specific users and groups depending on your organizational requirements. This gives administrators flexible control over the Teams app ecosystem while balancing security needs with user productivity. App setup policies are incorrect because they control which apps are pinned to the app bar in Teams and the order in which they appear. Setup policies also determine which apps are installed by default for users when they first start using Teams. While app setup policies influence the user experience and make certain apps more prominent or automatically available, they do not prevent users from accessing or installing apps. Even if an app is not pinned or pre-installed through a setup policy, users can still search for and install it unless it is blocked by an app permission policy. Messaging policies are incorrect because they govern chat and messaging features within Teams, such as whether users can delete messages, edit sent messages, use chat functionality, send urgent messages, or use features like Giphys, stickers, and memes in conversations. Messaging policies do not control access to third-party applications or cloud storage services. Meeting policies are incorrect because they control features and capabilities available during Teams meetings, such as whether users can record meetings, use video, share screens, use background effects, enable meeting chat, or allow anonymous users to join meetings. Meeting policies do not manage app permissions or access to external storage services.
Q164
You are administering Microsoft Teams for your company. A user reports that when they try to start a meeting, the Meet Now button is not available. You need to ensure the user can start instant meetings. What should you verify?
A) The user has been assigned a Teams meeting policy that allows Meet Now
B) The user has guest access enabled
C) The user has external access configured
D) The user has been assigned a messaging policy
Answer: A
Explanation:
This question deals with troubleshooting issues related to instant meeting functionality in Microsoft Teams, specifically the Meet Now feature. Meet Now allows users to start an impromptu meeting immediately without scheduling it in advance, which is useful for quick collaboration sessions, urgent discussions, or spontaneous team meetings. When the Meet Now button is not available to a user, it typically indicates a policy configuration issue that is restricting this functionality. The Meet Now feature is controlled through Teams meeting policies, which are configured in the Teams admin center and determine what meeting features and capabilities are available to users. Meeting policies contain a specific setting called “Meet now in channels” and general meeting settings that control whether users can initiate instant meetings. To resolve this issue, you need to verify that the user has been assigned a meeting policy that enables the Meet Now functionality. In the Teams admin center, navigate to Meetings and then Meeting policies to review the policies in your organization. Check which policy is assigned to the affected user and ensure that the appropriate settings are enabled. If the user is assigned to a restrictive policy that disables instant meetings, you can either modify that policy to enable Meet Now or assign the user to a different policy that has this feature enabled. Meeting policies can be assigned globally or to specific users and groups, allowing administrators to provide different levels of meeting capabilities based on organizational roles or security requirements. It is also worth checking that the user’s Teams client is up to date and that they have the necessary licenses to use Teams meeting features. Guest access being enabled is incorrect because guest access controls whether people from outside your organization can be invited to join teams and channels as guests. Guest access determines what permissions and capabilities external guests have within your Teams environment, such as creating channels, participating in chats, or accessing files. However, guest access configuration does not affect whether your internal users can use the Meet Now feature to start instant meetings. Guest access and Meet Now functionality are separate capabilities. External access configuration is incorrect because external access manages federation settings that allow users from other Microsoft 365 organizations to communicate with your users through Teams. External access enables cross-organization communication such as chat, calling, and meetings with users from federated domains, but it does not control whether internal users can start instant meetings using Meet Now. External access is about inter-organizational communication rather than meeting initiation features. Messaging policy assignment is incorrect because messaging policies control chat and messaging features in Teams, such as whether users can delete sent messages, edit messages, use chat functionality, read receipts, priority notifications, or use features like Giphys, stickers, and memes in conversations. Messaging policies do not govern meeting-related functionality like the ability to start instant meetings with Meet Now.
Q165
Your organization has implemented Microsoft Teams and wants to ensure that all meetings include a lobby where participants wait until admitted. You need to configure this setting for all users. Where should you configure this setting?
A) Teams meeting policies
B) Teams calling policies
C) Teams app setup policies
D) Teams messaging policies
Answer: A
Explanation:
This question addresses the configuration of lobby settings for Microsoft Teams meetings, which is an important security and meeting management feature. The lobby functionality allows meeting organizers to control who can directly join meetings and who must wait in a virtual lobby until they are admitted by the organizer or another authorized participant. This feature is particularly useful for preventing unwanted participants from joining meetings, ensuring that external attendees are properly vetted before being admitted, and maintaining professional meeting environments where the organizer wants to control the flow of participants. The lobby settings are controlled through Teams meeting policies, which provide comprehensive control over various meeting features and behaviors. Meeting policies in the Teams admin center include a setting called “Automatically admit people” which determines who can bypass the lobby and enter the meeting directly. The options for this setting typically include Everyone, People in my organization, People in my organization and guests, People in my organization trusted organizations and guests, or Only me and the people I invite. To ensure that all meetings include a lobby where participants wait until admitted, you would configure the meeting policy to restrict automatic admission, such as setting it to “Only me and the people I invite” or configuring it so that external participants always go through the lobby. You can access this setting in the Teams admin center by navigating to Meetings and then Meeting policies, where you can modify the global policy or create custom policies for different user groups. The lobby setting works in conjunction with other meeting security features such as meeting options that allow organizers to control specific meeting behaviors on a per-meeting basis. It is important to balance security needs with user experience, as overly restrictive lobby settings might create friction for legitimate participants while enhancing meeting security. Teams calling policies are incorrect because they govern voice calling features in Teams, such as whether users can make private calls, use call forwarding, simultaneously ring other numbers, delegate calling permissions to others, configure voicemail settings, or use call park functionality. Calling policies are focused on one-to-one or group calling features rather than meeting-specific functionality like lobby controls. While both calling and meetings involve real-time communication, they are managed through separate policy types with different configuration options. Teams app setup policies are incorrect because they control which apps are pinned to the app bar in Teams, the order in which apps appear, and which apps are pre-installed for users when they start using Teams. App setup policies influence the user interface and app availability but do not affect meeting security features like lobby settings. Even with specific apps pinned or installed, the meeting lobby behavior is controlled independently through meeting policies. Teams messaging policies are incorrect because they manage chat and messaging features within Teams, such as whether users can delete sent messages, edit messages, use chat functionality, send urgent messages with priority notifications, or use Giphys, stickers, memes, and other rich content in conversations. Messaging policies do not control meeting-related security features like lobby admission settings.
Q166
You manage Microsoft Teams for a global organization. Users in different regions report experiencing poor audio and video quality during Teams meetings. You need to identify the root cause of the quality issues. What tool should you use?
A) Call Quality Dashboard
B) Teams admin center meeting reports
C) Microsoft 365 security center
D) Azure Active Directory logs
Answer: A
Explanation:
This question focuses on troubleshooting and monitoring audio and video quality issues in Microsoft Teams meetings, which is a critical responsibility for Teams administrators. Poor call quality can significantly impact user productivity, collaboration effectiveness, and overall user satisfaction with the Teams platform. When users across different regions experience quality problems, it suggests potential network infrastructure issues, bandwidth limitations, routing problems, or configuration issues that need systematic investigation. The Call Quality Dashboard (CQD) is the primary tool for analyzing and troubleshooting call and meeting quality issues in Microsoft Teams. CQD provides detailed telemetry data about calls and meetings in your organization, including metrics such as packet loss, jitter, latency, round-trip time, audio and video quality measurements, and network connectivity information. The dashboard presents this data through various reports and visualizations that help administrators identify patterns, trends, and specific problem areas. You can access CQD through the Teams admin center or directly at the CQD portal, where you can view summary reports showing overall call quality across your organization and drill down into specific time periods, locations, networks, or user segments. CQD allows you to filter data by region, subnet, building, or user to isolate problems affecting specific geographic areas or network segments. For a global organization experiencing regional quality issues, CQD can help identify whether problems are related to specific internet service providers, network paths, VPN connections, WiFi networks, or endpoint devices. The tool also provides recommendations for improving call quality based on the telemetry data collected. It is important to note that CQD requires proper network configuration and building data to be uploaded for optimal analysis, including mapping subnets to physical locations and network details. Teams admin center meeting reports are incorrect because while they provide useful information about meeting usage, participation, and duration, they do not offer the detailed quality metrics and network performance data needed to diagnose audio and video quality issues. Meeting reports show statistics such as how many meetings were held, participant counts, meeting durations, and general usage patterns, but they lack the granular telemetry data about packet loss, jitter, latency, and other technical metrics that are essential for troubleshooting quality problems. These reports are more suited for understanding meeting adoption and usage patterns rather than technical quality analysis. Microsoft 365 security center is incorrect because it focuses on security threats, compliance, and data protection across Microsoft 365 services. The security center provides insights into potential security risks, data loss prevention policies, threat detection, and security recommendations, but it does not monitor or analyze real-time communication quality metrics for Teams calls and meetings. While security is important for Teams deployments, it is a separate concern from call quality monitoring and troubleshooting. Azure Active Directory logs are incorrect because they contain information about user authentication, sign-in activities, directory changes, and access patterns within Azure AD. These logs are valuable for security auditing, troubleshooting authentication issues, and monitoring user access patterns, but they do not provide telemetry data about call and meeting quality in Teams.
Q167
Your company uses Microsoft Teams and wants to implement a solution that automatically transcribes meetings and provides searchable meeting notes. What feature should you enable?
A) Live captions and transcription
B) Meeting recording
C) Cloud recording with automatic transcription
D) Meeting policies for note-taking
Answer: C
Explanation:
This question addresses the need for automated meeting transcription and searchable meeting content in Microsoft Teams, which enhances accessibility, compliance, and productivity by providing written records of spoken content during meetings. Many organizations require meeting transcripts for documentation purposes, accessibility compliance, content review, training materials, or for participants who need to reference what was discussed after the meeting. Microsoft Teams offers several features related to capturing meeting content, but the specific requirement for automatic transcription with searchable notes points to cloud recording with automatic transcription enabled. Cloud recording with automatic transcription is the feature that records the entire meeting to the cloud and automatically generates a transcript of the spoken content. When you enable cloud recording in Teams, the meeting audio, video, and screen sharing are captured and stored in Microsoft Stream or OneDrive and SharePoint depending on your organization’s configuration. Along with the recording, Teams automatically generates a transcript that timestamps each speaker’s contributions and makes the content searchable. Users can access the recording and transcript after the meeting, search for specific keywords or phrases within the transcript, and jump to relevant sections of the recording. The transcript also supports accessibility by providing captions that can be displayed during playback. To enable this feature, administrators need to configure meeting policies in the Teams admin center to allow cloud recording, and the transcription feature must be enabled in the organization’s settings. Users can then start recording during meetings, and the transcription is automatically generated in the background without requiring additional action. The searchability of transcripts makes it easy to find specific discussions or decisions within long meetings, and the automated nature eliminates the need for manual note-taking or transcription services. Live captions and transcription are incorrect as the sole answer because while this feature provides real-time captions during meetings that make spoken content visible as text on screen, it does not automatically save or store the transcription for later access. Live captions are primarily an accessibility feature that helps participants follow along during the meeting by displaying what is being said in real-time, but once the meeting ends, the live captions are not retained unless combined with recording. Live captions alone do not create a searchable archive of meeting notes that can be referenced after the meeting concludes. Meeting recording by itself is incorrect because while recording captures the audio, video, and screen sharing content of a meeting, it does not automatically include transcription unless specifically configured. Basic meeting recording provides a video file that users can replay, but without transcription enabled, the content is not searchable by keywords or phrases, and viewers must watch the entire recording to find specific information. Recording without transcription is less useful for quickly referencing specific discussions or creating searchable meeting documentation. Meeting policies for note-taking are incorrect because there is no specific Teams feature or policy setting dedicated to note-taking in the way described. While users can take notes during meetings using integrated apps like OneNote or the meeting notes feature, this is a manual process that requires active participation and does not provide automatic transcription of spoken content.
Q168
You are the Teams administrator for your organization. You need to prevent users from creating private channels within teams. What should you configure?
A) Teams policies
B) Channel policies
C) Messaging policies
D) App permission policies
Answer: A
Explanation:
This question deals with controlling channel creation capabilities within Microsoft Teams, specifically the ability of users to create private channels. Private channels are a feature in Teams that allows team members to create focused spaces for sensitive discussions or collaboration with a subset of team members, separate from the standard channels that are visible to all team members. While private channels can be useful for managing confidential projects or sensitive information, some organizations prefer to restrict their use due to governance concerns, compliance requirements, information management policies, or to maintain transparency within teams. Understanding how to control private channel creation is essential for Teams administrators who need to balance collaboration flexibility with organizational policies. Teams policies are the correct configuration for controlling whether users can create private channels. In the Teams admin center, you can configure Teams policies by navigating to Teams and then Teams policies, where you will find settings that govern various team and channel behaviors. Within Teams policies, there is a specific setting called “Create private channels” that can be turned on or off. When this setting is disabled, users will not see the option to create private channels when they attempt to add a new channel to a team, even if they have owner or member permissions that would normally allow channel creation. Teams policies can be configured globally to apply to all users in the organization, or you can create custom Teams policies and assign them to specific users or groups based on your organizational requirements. This allows for flexible governance where certain user groups might be allowed to create private channels while others are restricted. It is important to note that disabling private channel creation does not affect existing private channels, which will continue to function normally. The policy only prevents the creation of new private channels going forward. Channel policies do not exist as a separate policy type in Microsoft Teams administration. While channels are a core component of Teams, their creation and management are controlled through Teams policies rather than a standalone channel policy configuration. This is because channel behavior and permissions are intrinsically tied to team-level settings and governance. The Teams admin center does not provide a separate channel policies section, making this option incorrect for achieving the desired restriction on private channel creation. Messaging policies are incorrect because they control chat and messaging features within Teams, such as whether users can delete sent messages, edit messages, use chat functionality, send urgent messages with priority notifications, read receipts, or use features like Giphys, stickers, memes, and URL previews in conversations. Messaging policies govern the communication and content sharing capabilities in chat and channel conversations but do not control structural elements like channel creation or the types of channels that can be created. App permission policies are incorrect because they manage which applications users can install and use within Teams. App permission policies allow administrators to block specific apps, allow only approved apps, or control access to third-party integrations and custom apps. While app permissions are important for governance and security, they do not affect the fundamental Teams structure features like channel creation capabilities.
Q169
Your organization uses Microsoft Teams and needs to ensure that all team names follow a specific naming convention with a prefix based on department. What should you implement?
A) Microsoft 365 Groups naming policy
B) Teams policies
C) Azure AD group naming policy
D) Messaging policies
Answer: A
Explanation:
This question addresses the need for enforcing naming conventions across Microsoft Teams within an organization, which is an important governance and organizational requirement. Consistent naming conventions help users easily identify teams, understand their purpose, determine which department or project they belong to, and maintain a organized and professional appearance across the collaboration platform. Without naming policies, team names can become inconsistent, confusing, or fail to convey important organizational context, making it difficult for users to find relevant teams and for administrators to manage the Teams environment effectively. Implementing naming standards is particularly important in large organizations with hundreds or thousands of teams where clear identification and categorization are essential. The Microsoft 365 Groups naming policy is the correct solution for enforcing naming conventions on Teams. Since every Microsoft Team is backed by a Microsoft 365 Group, the naming policy applied to Microsoft 365 Groups automatically affects Teams as well. You can configure a naming policy in the Azure Active Directory admin center or Microsoft 365 admin center under Groups settings. The naming policy allows you to define prefixes and suffixes that are automatically added to group and team names when they are created. You can specify fixed text as prefixes or suffixes, such as department names, or use attributes like department, country, or other Azure AD user attributes to dynamically generate prefixes based on the creator’s properties. For example, you could configure a policy that automatically adds the department name as a prefix, so when a user from the Sales department creates a team called “Customer Projects,” it would automatically become “Sales-Customer Projects.” The naming policy also allows you to block specific words or phrases from being used in team names, which helps maintain professional standards and prevent inappropriate naming. Once implemented, the naming policy is enforced during team creation, and users will see a preview of the final team name including the required prefixes and suffixes before the team is created. Teams policies are incorrect because they control features and capabilities related to team and channel management, such as whether users can create private channels, create teams, discover private teams, or manage various team settings. While Teams policies govern functional aspects of how teams operate, they do not provide capabilities for enforcing naming conventions or automatically applying prefixes and suffixes to team names. Teams policies focus on permissions and feature availability rather than naming standards. Azure AD group naming policy is essentially the same as Microsoft 365 Groups naming policy because the naming policy for groups in Azure AD applies to Microsoft 365 Groups, which in turn affects Teams. However, the more precise and commonly used terminology in the context of Teams administration is “Microsoft 365 Groups naming policy,” as this directly references the relationship between Microsoft 365 Groups and Teams. Both answers refer to the same underlying configuration, but option A uses the more specific terminology relevant to Teams administration. Messaging policies are incorrect because they govern chat and messaging features within Teams, such as whether users can delete sent messages, edit messages, use chat functionality, or use features like Giphys, stickers, and memes in conversations. Messaging policies are focused on communication capabilities and content within Teams rather than on organizational structure or naming conventions for teams themselves.
Q170
You administer Microsoft Teams for your company. Users need to be able to schedule Teams meetings that automatically include a dial-in phone number for audio conferencing. What must be configured?
A) Audio Conferencing licenses and service
B) Phone System licenses
C) Calling policies
D) Direct Routing
Answer: A
Explanation:
This question focuses on enabling audio conferencing capabilities in Microsoft Teams meetings, which allows participants to join meetings via traditional phone calls using dial-in numbers. Audio conferencing is a critical feature for inclusive meetings because it accommodates participants who may not have reliable internet access, are traveling, working from locations with poor connectivity, or simply prefer to join meetings by phone. When audio conferencing is properly configured, Teams meeting invitations automatically include dial-in phone numbers and conference IDs that participants can use to join the meeting audio portion through any phone, while video and content sharing remain available through the Teams application or web client. Audio Conferencing licenses and service are the correct requirements for adding dial-in capabilities to Teams meetings. Audio Conferencing is a separate add-on license in Microsoft 365 that must be assigned to users who organize meetings that require dial-in numbers. Once users have Audio Conferencing licenses assigned, the service must be configured in the Teams admin center, which includes setting up conferencing bridges with dial-in phone numbers for various regions and countries. When a user with an Audio Conferencing license schedules a Teams meeting, the meeting invitation automatically includes the dial-in phone numbers, conference ID, and instructions for joining by phone. The Audio Conferencing service provides toll and toll-free numbers depending on your configuration and licenses, and it maintains conferencing bridges that handle the phone connections and integrate them with Teams meetings. Administrators can manage audio conferencing settings in the Teams admin center under Meetings and then Conference bridges, where you can view available phone numbers, set default numbers for different regions, configure bridge settings, and manage dial-in number assignments. It is important to ensure that users have the appropriate licenses assigned and that the audio conferencing service is properly configured for your organization’s geographic locations to provide the best experience for participants joining by phone. Phone System licenses are incorrect because while they are required for making and receiving regular phone calls through Teams using calling plans or Direct Routing, they are not specifically required for adding dial-in numbers to Teams meetings. Phone System provides features like voicemail, call forwarding, auto attendants, and call queues, which are focused on individual calling capabilities rather than meeting audio conferencing. Audio Conferencing and Phone System are separate services with different purposes, though they can be used together in a comprehensive Teams voice solution. Calling policies are incorrect because they govern individual calling features and behaviors in Teams, such as whether users can make private calls, use call forwarding, delegate calling permissions, or configure voicemail. Calling policies control one-to-one and group calling capabilities but do not enable or configure audio conferencing for meetings. Even with appropriate calling policies configured, meetings will not include dial-in numbers unless Audio Conferencing licenses and services are properly set up. Direct Routing is incorrect because it is a telephony configuration method that connects Microsoft Phone System to third-party Session Border Controllers and PSTN carriers, allowing organizations to use their existing telephony infrastructure with Teams. While Direct Routing can be used as part of a comprehensive voice solution that includes audio conferencing, it is not the primary requirement for enabling dial-in numbers in meetings.
Q171
Your company has implemented Microsoft Teams and wants to prevent users from sharing files from unapproved third-party cloud storage services during meetings. What type of policy should you configure?
A) App permission policy
B) Meeting policy
C) Sharing policy
D) Data loss prevention policy
Answer: A
Explanation:
This question addresses the security and compliance requirement of controlling which file sharing and cloud storage services users can access during Microsoft Teams meetings. Organizations often need to restrict the use of unapproved cloud storage services to prevent data leakage, ensure compliance with data governance policies, maintain control over corporate information, and meet regulatory requirements. When users can freely share files from various third-party storage services during meetings, it creates risks of sensitive information being stored in unsanctioned locations, potential data breaches, and difficulties in maintaining data lifecycle management and retention policies. Controlling access to third-party applications is therefore an essential aspect of Teams administration and security. App permission policies are the correct configuration for preventing users from accessing unapproved third-party cloud storage services during meetings or any other Teams activities. These policies allow administrators to control which applications can be installed and used within the Teams environment. In the Teams admin center, you can configure app permission policies by navigating to Teams apps and then Permission policies, where you can create policies that block specific apps or categories of apps, allow only approved apps, or implement a default-deny approach where all apps are blocked except those explicitly allowed. To prevent file sharing from unapproved services like Dropbox, Google Drive, or Box during meetings, you would create an app permission policy that blocks these specific applications. You can search for apps by name and add them to the blocked apps list, or you can block entire categories of apps. App permission policies can be assigned globally to all users or to specific users and groups, providing flexible control based on organizational roles and security requirements. When an app is blocked through a permission policy, users cannot install it, and if it was previously installed, they cannot access it. This prevents users from sharing files from these services during meetings or in any other Teams context. Meeting policies are incorrect because while they control various meeting features and capabilities such as recording, screen sharing, video usage, lobby settings, and participant permissions, they do not specifically control which applications or cloud storage services users can access during meetings. Meeting policies focus on the meeting experience and available features rather than application-level access control. Even with restrictive meeting policies, users could still access third-party storage apps if they are not blocked at the application permission level. Sharing policies do not exist as a specific policy type in Microsoft Teams administration. While there are various settings related to file sharing and collaboration throughout Teams and SharePoint configurations, there is no dedicated “sharing policy” in the Teams admin center that controls third-party application access. File sharing capabilities are managed through a combination of app permissions, SharePoint settings, and other governance controls. Data loss prevention policies are incorrect for this specific scenario because while DLP policies are powerful tools for preventing sensitive information from being shared inappropriately, they work by scanning content and blocking or warning about policy violations based on content classification, sensitive information types, or labels. DLP policies do not prevent users from accessing specific applications or third-party services. Instead, they monitor and control what content can be shared regardless of the application being used.
Q172
You are a Teams administrator for a company with strict compliance requirements. You need to ensure that all Teams conversations and files are retained for seven years even if users delete them. What should you configure?
A) Retention policies in the Microsoft Purview compliance portal
B) Teams messaging policies
C) Data loss prevention policies
D) Legal hold on all users
Answer: A
Explanation:
This question addresses compliance and data retention requirements in Microsoft Teams, which are critical concerns for organizations in regulated industries such as finance, healthcare, legal, and government sectors. Many organizations are required by law or industry regulations to retain electronic communications and associated files for specific periods, often ranging from several years to indefinitely. These retention requirements serve various purposes including regulatory compliance, legal discovery, audit trails, and historical record keeping. Microsoft Teams generates significant amounts of data including chat messages, channel conversations, meeting recordings, shared files, and other collaboration artifacts, all of which may be subject to retention policies. The challenge is ensuring that this data is preserved for the required duration regardless of user actions such as deleting messages or leaving the organization. Retention policies in the Microsoft Purview compliance portal (formerly Office 365 Security & Compliance Center) are the correct solution for ensuring that Teams content is retained for a specified period. Retention policies allow administrators to define how long content should be kept and what happens at the end of the retention period. You can create retention policies that apply to Teams channel messages, Teams chats, and Teams meeting recordings, specifying retention periods such as seven years as required in this scenario. Retention policies work by preserving copies of content even when users delete it, making the content available for compliance, legal, and audit purposes through eDiscovery and content search tools. To configure retention policies, access the Microsoft Purview compliance portal, navigate to Data lifecycle management or Records management, and create a new retention policy. You can specify the locations to which the policy applies, such as Teams channel messages and Teams chats, define the retention period, and configure whether content should be deleted automatically after the retention period expires or retained indefinitely. Retention policies override user deletions, meaning that even if a user deletes a message or file, the content remains in a preserved state for the specified retention period and can be retrieved through compliance tools. This ensures that your organization meets regulatory requirements and can respond to legal discovery requests. Teams messaging policies are incorrect because they control chat and messaging features within Teams such as whether users can delete sent messages, edit messages, use chat functionality, or use features like Giphys and stickers. While messaging policies can prevent users from deleting messages in real-time, they do not provide the long-term retention and compliance capabilities needed to preserve content for seven years. Messaging policies focus on user experience and messaging capabilities rather than data retention and compliance. Data loss prevention policies are incorrect because they are designed to prevent sensitive information from being shared inappropriately by scanning content for sensitive data types, applying protective actions, and alerting administrators or users when policy violations occur. DLP policies focus on preventing data leakage and unauthorized sharing rather than on retaining data for compliance purposes. While DLP is important for security, it does not address the requirement to preserve content for extended periods. Legal hold on all users is incorrect as the primary solution because while legal holds (also known as litigation holds or in-place holds) can preserve content indefinitely and prevent deletion, they are typically used for specific legal or investigative purposes rather than as an organization-wide retention solution. Legal holds are more targeted and are intended for situations where specific users or content need to be preserved due to litigation or investigations.
Q173
Your organization uses Microsoft Teams and has enabled guest access. You need to ensure that guests cannot download or print files shared in teams. What should you configure?
A) Azure AD conditional access policies and SharePoint settings
B) Guest access settings in Teams admin center
C) Teams sharing policies
D) App permission policies
Answer: A
Explanation:
This question addresses the security requirement of controlling what actions guest users can performon files shared within Microsoft Teams, specifically preventing downloading and printing of documents. Guest access in Microsoft Teams allows organizations to collaborate with external partners, vendors, clients, and other stakeholders by inviting them to participate in teams and channels. While guest access enables valuable external collaboration, it also introduces security risks, particularly around sensitive document access and potential data leakage. Organizations often need to allow guests to view and collaborate on files while restricting their ability to download, print, or take files outside the controlled Teams environment. This balance between collaboration and security requires careful configuration of multiple Microsoft 365 services that work together to enforce file access restrictions. Azure AD conditional access policies combined with SharePoint settings are the correct solution for preventing guests from downloading or printing files. Since files shared in Teams are actually stored in SharePoint or OneDrive, the file access controls must be configured at the SharePoint level. In the SharePoint admin center, you can configure settings that control whether users can download files, and you can apply these restrictions specifically to guest users or external users. Additionally, Azure AD conditional access policies provide granular control over access conditions and can enforce restrictions based on user type, device compliance, location, and other factors. You can create a conditional access policy that targets guest users and applies session controls that limit their actions, such as using app-enforced restrictions that work with SharePoint to prevent downloading. To implement this, navigate to the Azure AD admin center, create or modify a conditional access policy, specify guest users as the target, and configure session controls to use app-enforced restrictions for SharePoint Online. Then in SharePoint admin center, configure the appropriate access control settings to limit downloading for external users. These settings work together to ensure that when guests access files in Teams, they can view and edit them in the browser but cannot download them to their devices or print them. This approach provides robust security while maintaining collaboration capabilities. Guest access settings in Teams admin center are incorrect because while they control various capabilities that guests have within Teams, such as whether they can create channels, delete messages, edit messages, or use certain features, they do not provide granular control over file operations like downloading and printing. The Teams admin center guest settings focus on messaging, calling, and meeting capabilities rather than document-level security controls. File access restrictions require deeper integration with SharePoint and Azure AD policies that govern document access behavior. Teams sharing policies do not exist as a specific policy type in Microsoft Teams administration. While there are various sharing-related configurations throughout Microsoft 365, there is no dedicated Teams sharing policy in the Teams admin center that controls file download and print capabilities. File sharing and access controls are managed through SharePoint, OneDrive, and Azure AD rather than through Teams-specific policies. App permission policies are incorrect because they control which applications users can install and use within Teams, such as blocking or allowing specific third-party apps, custom apps, or Microsoft apps. App permission policies do not govern file access behaviors like downloading or printing documents. While app permissions are important for controlling the Teams app ecosystem, they operate at the application level rather than at the document access level required for this scenario.
Q174
You manage Microsoft Teams for your organization. Users report that they cannot find a specific team when searching, even though they are members of that team. What is the most likely cause?
A) The team is set to private and hidden from search results
B) The team has been archived
C) The users lack appropriate Teams policies
D) The team naming policy is blocking visibility
Answer: B
Explanation:
This question addresses a common troubleshooting scenario in Microsoft Teams where users who are members of a team cannot locate it through search functionality. Teams provides robust search capabilities that allow users to find teams, channels, messages, files, and people across their organization, but certain team states and configurations can affect visibility and accessibility. When team members report that they cannot find a team they belong to, it indicates a change in the team’s status or configuration that has removed it from normal search results and the active teams list. Understanding the different states a team can be in and how these states affect user experience is essential for Teams administrators who need to quickly diagnose and resolve access issues. An archived team is the most likely cause of this issue. When a team is archived in Microsoft Teams, it is placed in a read-only state where members can still view the team’s content including messages, files, and channel history, but they cannot add new messages, edit existing content, add new members, or perform other active collaboration activities. Critically, archived teams do not appear in the regular teams list in the Teams client, and they are not included in standard search results. Users who are members of archived teams can still access them by specifically looking for archived teams through the “Manage teams” interface and selecting “Hidden teams” or by using the option to show archived teams, but they will not see these teams in their normal day-to-day Teams view. Archiving is typically used for teams that are no longer actively needed but whose content must be preserved for reference or compliance purposes, such as completed projects, ended initiatives, or historical records. If users report that they suddenly cannot find a team they were previously using, checking whether the team has been archived should be one of the first troubleshooting steps. Team owners and administrators can archive teams either intentionally as part of team lifecycle management or accidentally if they are not familiar with the feature. To resolve this issue, an administrator can unarchive the team through the Teams admin center by navigating to Teams, selecting Manage teams, finding the archived team, and selecting the option to restore or unarchive it. Once unarchived, the team returns to active status and appears normally in search results and the teams list for all members. The option stating the team is private and hidden from search results is incorrect because while teams can be private, meaning that users cannot discover them without an invitation, private teams are still fully visible and searchable to their members. Once a user is a member of a private team, they can see it in their teams list and find it through search just like any other team they belong to. The privacy setting affects discoverability for non-members but does not hide the team from existing members. Users lacking appropriate Teams policies is incorrect because Teams policies control features and capabilities available to users, such as whether they can create teams, create private channels, or use certain meeting features. Policies do not affect the visibility of teams that users are already members of. If a user is a member of a team, policy configurations would not prevent them from seeing or finding that team in their Teams client. Team naming policy blocking visibility is incorrect because naming policies enforce naming conventions such as required prefixes or suffixes and can block certain words from being used in team names. However, naming policies do not affect the visibility or searchability of existing teams to their members. Once a team is created and a user is a member, they can find and access it regardless of naming policy configurations.
Q175
Your company uses Microsoft Teams and needs to prevent users from scheduling meetings longer than two hours. What should you configure?
A) This cannot be configured through Teams policies
B) Meeting policies in Teams admin center
C) Calendar policies in Exchange admin center
D) Azure AD conditional access policies
Answer: A
Explanation:
This question addresses a commonly requested but unsupported restriction in Microsoft Teams meeting management. Organizations sometimes want to limit meeting durations for various reasons such as encouraging more focused and efficient meetings, reducing calendar congestion, managing meeting room resources, or implementing organizational policies around meeting culture and time management. While Microsoft Teams provides extensive policy controls over meeting features and behaviors, there are certain limitations that administrators should understand when attempting to implement organizational meeting governance requirements. The ability to limit meeting duration through configuration is one such limitation. It cannot be configured through Teams policies because Microsoft Teams does not currently provide a native policy setting that restricts the maximum duration of scheduled meetings. Teams meeting policies offer extensive controls over features like recording, screen sharing, video usage, lobby settings, participant permissions, and many other meeting capabilities, but they do not include options to set minimum or maximum meeting durations. Users are free to schedule meetings of any length they choose, from brief fifteen-minute check-ins to all-day sessions or multi-day events. This is by design, as Microsoft aims to provide flexibility for diverse organizational needs where meeting duration requirements vary significantly. While some organizations might want to limit meetings to two hours, others might regularly need longer sessions for training, workshops, or strategic planning. The absence of duration limits in Teams reflects this diversity of use cases. Organizations that need to enforce meeting duration policies must typically implement them through organizational culture, manager oversight, training, or external tools rather than through technical restrictions in Teams. Some organizations use third-party governance tools or custom solutions that integrate with the Microsoft Graph API to monitor meeting durations and provide reporting or notifications when meetings exceed desired lengths, but these are workarounds rather than native Teams functionality. It is worth noting that while you cannot prevent users from scheduling long meetings, you can influence meeting behavior through other means such as training on effective meeting practices, implementing meeting-free days or times, or using organizational change management to establish meeting culture norms. Meeting policies in the Teams admin center are incorrect because while they provide extensive control over meeting features and capabilities, they do not include settings for limiting meeting duration. You can control who can bypass the lobby, whether meetings can be recorded, whether video can be used, and dozens of other features, but maximum meeting duration is not among the configurable options. Administrators should be aware of this limitation when planning Teams governance strategies. Calendar policies in Exchange admin center are incorrect because they primarily control calendar sharing permissions, working hours, resource booking, and calendar processing rules rather than meeting-specific behaviors in Teams. While Exchange calendar policies affect how calendars function in Outlook and how calendar information is shared, they do not provide controls over Teams meeting durations or prevent users from scheduling long meetings. Azure AD conditional access policies are incorrect because they control access to cloud applications based on conditions like user identity, device compliance, location, and risk level. Conditional access policies enforce security requirements such as requiring multi-factor authentication or restricting access from certain locations, but they do not govern meeting scheduling behaviors or duration limits within applications like Teams.
Q176
You are the Teams administrator for a multinational organization. You need to configure Teams so that users in the European office can only communicate with users in the North American office and not with other external organizations. What should you configure?
A) External access with allowed domains list
B) Guest access settings
C) Teams policies
D) Conditional access policies
Answer: A
Explanation:
This question addresses the configuration of inter-organizational communication in Microsoft Teams, specifically controlling which external domains users can communicate with through federation. External collaboration requirements vary significantly across organizations, with some needing completely open external communication, others requiring complete isolation, and many needing selective federation where communication is allowed only with trusted partner organizations. In this scenario, a multinational organization with separate Microsoft 365 tenants for different regions needs to enable communication between specific offices while preventing communication with other external organizations. This represents a common enterprise scenario where different business units or regional offices operate separate tenants but need controlled collaboration capabilities. External access with an allowed domains list is the correct solution for enabling selective federation between specific organizations. External access, also known as federation, allows users from different Microsoft 365 organizations to find, call, chat with, and set up meetings with each other while each organization maintains its own separate tenant. By default, external access in Teams is configured to allow communication with all external domains, but administrators can restrict this by configuring an allowed domains list that specifies exactly which external organizations users can communicate with. To implement this, navigate to the Teams admin center, go to Users and then External access, and configure the settings to allow only specific domains. You would add the domain of the North American office to the allowed list for the European office and vice versa, while ensuring that the external access mode is set to allow only specific domains rather than all external domains. This configuration creates a controlled federation where users in the European office can search for, call, chat with, and meet with users in the North American office as if they were in the same organization, but they cannot communicate with users from other external organizations. It is important to note that external access is a reciprocal relationship, meaning that both organizations must configure their external access settings to allow communication with each other. Additionally, external access requires that users have accounts in their respective organizations and are signed in to Teams, which differentiates it from guest access. Guest access settings are incorrect because guest access is designed for inviting external users to join your organization’s teams and channels as guests, giving them access to internal resources and ongoing collaboration. Guest access requires inviting external users who then become guests in your Azure AD tenant, which is different from the federation model where users remain in their own organizations but can communicate across tenants. Guest access would not be appropriate for this scenario because it would require inviting all users from the North American office as guests in the European tenant and vice versa, which creates management overhead and is not designed for organization-to-organization communication between separate tenants of the same company. Teams policies are incorrect because they control features and capabilities available to users within your organization, such as whether users can create teams, create private channels, or use various meeting features. Teams policies do not govern external communication or federation with other organizations. While Teams policies are essential for managing internal Teams behavior, they do not provide the cross-tenant communication controls needed for this scenario. Conditional access policies are incorrect because they control access to cloud applications based on conditions and enforce security requirements, but they do not specifically manage which external organizations users can communicate with through Teams federation. Conditional access might be used in conjunction with external access to enforce additional security requirements for external communications, but it is not the primary mechanism for enabling selective federation between specific organizations.
Q177
Your organization uses Microsoft Teams and wants to implement a solution that routes incoming calls to a group of support agents and provides automated menu options for callers. What feature should you configure?
A) Call queue and auto attendant
B) Call forwarding and delegation
C) Calling policies
D) Direct Routing
Answer: A
Explanation:
This question addresses the implementation of enterprise voice features in Microsoft Teams that enable sophisticated call routing and automated call handling, which are essential for customer service operations, support centers, sales teams, and any organization that receives significant incoming call volume. Traditional phone systems have long provided features like automated attendants that greet callers with menu options and call queues that distribute calls among available agents, and Microsoft Teams brings these capabilities into the modern cloud-based collaboration platform. Organizations migrating from legacy phone systems to Teams need to understand how to replicate and enhance these call handling capabilities using Teams voice features. Call queues and auto attendants are the correct features for implementing this solution. An auto attendant in Teams provides automated menu options for incoming callers, greeting them with a customized message and allowing them to navigate through a menu system by pressing digits on their phone keypad or using voice commands. For example, an auto attendant might say “Press 1 for Sales, Press 2 for Support, Press 3 for Billing” and then route the call accordingly based on the caller’s selection. Auto attendants can have multiple menu layers, business hours configurations, holiday schedules, and different call flows for different times. A call queue works in conjunction with the auto attendant by receiving calls and distributing them to a group of agents using various routing methods such as attendant routing, serial routing, round robin, or longest idle. Call queues can play music on hold, provide estimated wait times, allow callers to opt for callbacks, and configure overflow handling when all agents are busy. To implement this solution, you need Phone System licenses for your organization and appropriate calling capabilities through Calling Plans or Direct Routing. Then in the Teams admin center, navigate to Voice and configure both auto attendants and call queues. You would first create user accounts or resource accounts to serve as the identity for the auto attendant and call queue, assign phone numbers to them, create the auto attendant with appropriate menu options and greetings, create the call queue with the support agents as members, and configure the auto attendant to route calls to the call queue based on menu selections. This combination provides a professional call handling experience that efficiently routes callers to the right destination. Call forwarding and delegation are incorrect because these features allow individual users to forward their calls to other numbers or delegate call handling to assistants or colleagues. While call forwarding and delegation are useful for personal call management, they do not provide the automated menu systems, call distribution logic, or group call handling capabilities needed for a support center scenario. These features are designed for individual user productivity rather than organizational call routing. Calling policies are incorrect because they control what calling features are available to users, such as whether they can make private calls, use call forwarding, configure voicemail, or delegate calling permissions. Calling policies govern feature availability and behavior but do not implement call routing solutions or automated attendants. Even with appropriate calling policies enabled, you would still need to configure auto attendants and call queues to achieve the desired call handling functionality. Direct Routing is incorrect because it is a method of connecting Microsoft Phone System to third-party telephony infrastructure and PSTN carriers through Session Border Controllers. Direct Routing enables organizations to use their existing telephony investments with Teams and provides PSTN connectivity for making and receiving external calls. While Direct Routing might be part of the overall voice solution that enables external calling capabilities, it is not the feature that provides automated menus and call distribution. Organizations using Direct Routing would still need to configure auto attendants and call queues to implement the call handling logic described in the question.
Q178
You manage Microsoft Teams for your organization. You need to ensure that when users share their screen during meetings, only the application window is shared and not their entire desktop. What should you configure?
A) This is a user choice during screen sharing and cannot be enforced by policy
B) Meeting policies to restrict screen sharing modes
C) Application permission policies
D) Messaging policies
Answer: A
Explanation:
This question addresses screen sharing behavior in Microsoft Teams meetings, specifically whether administrators can enforce restrictions on what type of content users share when presenting. Screen sharing is a fundamental collaboration feature in Teams that allows meeting participants to show their work, present applications, demonstrate software, review documents, and collaborate visually. Teams offers multiple screen sharing modes including sharing the entire desktop, sharing specific application windows, and sharing PowerPoint presentations in presenter mode. From a security and privacy perspective, organizations sometimes want to prevent users from accidentally sharing their entire desktop which might expose sensitive information visible in other windows, notifications, personal content, or confidential materials unrelated to the meeting purpose. However, Teams policies have limitations in enforcing certain user behaviors. This is a user choice during screen sharing and cannot be enforced by policy because Microsoft Teams does not provide a policy setting that restricts users to only window sharing and prevents desktop sharing. When a user initiates screen sharing in a Teams meeting, they are presented with options to share their desktop, share a specific window, share a PowerPoint file, or share a whiteboard. The user makes this selection based on their needs for that particular sharing session. While administrators might want to enforce window-only sharing to reduce the risk of inadvertent information disclosure, Teams meeting policies do not include a configuration option to restrict the available sharing modes. This design decision reflects the reality that different sharing scenarios have legitimate needs for different modes. Sometimes users need to share their entire desktop to demonstrate workflows that span multiple applications, show taskbar or system tray information, or provide comprehensive views of their environment. Other times, window sharing is more appropriate and professional. Because these needs vary contextually, Teams leaves the choice to users rather than allowing administrators to enforce restrictions. Organizations concerned about sensitive information exposure during screen sharing should address this through user training, best practices guidance, security awareness programs, and organizational policies rather than through technical controls. Users should be educated about when to use desktop sharing versus window sharing, how to close sensitive applications before sharing, and how to verify what they are sharing before presenting. Some organizations also implement data loss prevention strategies and information protection policies that help safeguard sensitive content regardless of how it is shared. Meeting policies to restrict screen sharing modes might seem like the correct answer, but it is incorrect because while meeting policies do control whether screen sharing is allowed at all and who can share content during meetings, they do not provide granular controls over which sharing modes are available. You can configure meeting policies to completely disable screen sharing for certain users or control whether only presenters or all participants can share, but you cannot restrict users to specific sharing modes like window-only sharing. Application permission policies are incorrect because they control which applications users can install and use within Teams, such as third-party apps, custom apps, or specific Microsoft applications. App permission policies do not govern screen sharing behavior or the modes available during content sharing in meetings. These policies operate at the application level for the Teams app ecosystem rather than controlling meeting functionality like sharing modes. Messaging policies are incorrect because they govern chat and messaging features within Teams, such as whether users can delete sent messages, edit messages, use chat functionality, or use features like Giphys, stickers, and memes in conversations. Messaging policies are focused on text-based communication capabilities and do not affect meeting features like screen sharing.
Q179
Your company has Microsoft Teams deployed and needs to ensure that all meetings are automatically recorded and the recordings are stored in a centralized location accessible only to compliance officers. What should you configure?
A) Compliance recording policies
B) Meeting policies with automatic recording enabled
C) Retention policies for Teams recordings
D) Legal hold on all users
Answer: A
Explanation:
This question addresses a specialized compliance requirement where organizations need to capture all Teams meetings for regulatory purposes, security monitoring, dispute resolution, or quality assurance, and ensure that these recordings are stored securely with access limited to authorized compliance personnel. This scenario is common in highly regulated industries such as financial services, healthcare, legal services, and government agencies where communications must be recorded and retained to meet regulatory obligations. Standard Teams meeting recording, where users manually start and stop recordings that are then stored in SharePoint or OneDrive with access for meeting participants, does not meet these compliance requirements because it relies on user action, stores recordings in user-accessible locations, and does not provide the centralized control and restricted access needed for compliance purposes. Compliance recording policies are the correct solution for this requirement. Compliance recording is a specialized feature in Microsoft Teams that automatically captures all calls and meetings for specified users without user intervention or awareness, and stores these recordings in a separate compliance recording system rather than in standard SharePoint or OneDrive locations. Compliance recording requires integration with third-party compliance recording partners who are certified by Microsoft to provide this functionality. These partner solutions connect to Teams through certified APIs, automatically record all Teams communications for policy-assigned users, store recordings in specialized secure storage systems with appropriate retention and access controls, and provide compliance officers with tools to search, retrieve, and analyze recordings. To implement compliance recording, you must first select and deploy a Microsoft-certified compliance recording partner solution. Then in the Teams admin center, you configure compliance recording policies by navigating to Voice and then Compliance recording policies, where you can create policies that specify which users should have their communications recorded and which recording application to use. These policies are assigned to users who need to be recorded, typically users in regulated roles such as traders, advisors, or other positions with compliance recording requirements. Once assigned, all Teams calls and meetings involving these users are automatically recorded by the compliance recording solution without requiring manual action and without obvious indication to the users that recording is occurring. The recordings are stored in the partner’s compliance platform with appropriate security controls, retention policies, and access restrictions that limit retrieval to authorized compliance officers. Meeting policies with automatic recording enabled are incorrect because while Teams meeting policies do include settings related to recording such as who can record meetings and whether recording is allowed, they do not provide automatic recording functionality that captures all meetings without user action. Meeting policies can enable recording capabilities for users, but they still require someone in the meeting to manually start the recording. Additionally, standard Teams recordings are stored in SharePoint or OneDrive with access available to meeting participants, which does not meet the requirement for centralized storage accessible only to compliance officers. Retention policies for Teams recordings are incorrect because while retention policies are essential for ensuring that recorded content is preserved for required periods and can prevent deletion of recordings, they do not provide automatic recording functionality. Retention policies work on content that has already been created, but they do not cause meetings to be recorded automatically. Organizations would still need users to manually record meetings, and the recordings would be stored in standard locations. Retention policies are complementary to compliance recording but do not fulfill the automatic recording and centralized storage requirements. Legal hold on all users is incorrect because legal holds preserve content and prevent deletion for specific users involved in litigation or investigations, but they do not cause meetings to be recorded automatically. Legal holds maintain existing content including chat messages, channel conversations, and meeting recordings that users create, but they do not trigger automatic recording of all meetings. Like retention policies, legal holds are a preservation mechanism rather than a recording mechanism.
Q180
You are the Microsoft Teams administrator for your organization. Users report that they cannot see presence status (Available, Busy, Away) for some external users they regularly communicate with. What is the most likely cause?
A) The external organization has not configured external access to allow your domain
B) Your organization has guest access disabled
C) The users need Teams calling policies enabled
D) Presence information requires Microsoft 365 E5 licenses
Answer: A
Explanation:
This question addresses troubleshooting presence and availability information visibility across different Microsoft 365 organizations in Teams. Presence status is a fundamental feature of unified communications that indicates whether users are available, busy, in a meeting, away, offline, or in other states that help people know the best time to initiate communication. In enterprise environments where organizations regularly collaborate with external partners, clients, or other business units operating in separate Microsoft 365 tenants, presence information becomes particularly valuable for efficient communication and collaboration. When users can see external presence, they can avoid interrupting colleagues who are busy, choose optimal times for communication, and generally improve collaboration effectiveness. However, presence visibility across organizations requires proper configuration of federation settings on both sides of the relationship. The external organization has not configured external access to allow your domain is the most likely cause of this issue. External access, also known as federation, in Microsoft Teams allows users from different Microsoft 365 organizations to communicate with each other, and proper configuration is required on both organizations for the relationship to work fully. Presence information sharing is one of the capabilities enabled through external access configuration. For users in your organization to see presence status for users in an external organization, both organizations must have external access configured to allow communication with each other’s domains. If your organization allows external access from all domains but the external organization has restricted external access to only specific allowed domains and has not included your domain in that list, users in your organization will not be able to see presence information for users in the external organization. Similarly, if the external organization blocks external access entirely or has blocked your specific domain, presence sharing will not function. External access configuration is reciprocal, meaning that both organizations must allow the federation relationship for full functionality including presence, chat, calling, and meeting capabilities across organizations. To troubleshoot this issue, you should verify your organization’s external access settings in the Teams admin center under Users and then External access, confirm that your organization is configured to allow external communications, and then coordinate with the external organization’s Teams administrator to ensure they have also configured external access appropriately. The external organization needs to either allow all external domains or specifically add your domain to their allowed domains list. Once both sides are configured correctly, presence information should become visible, though there may be a brief delay as the changes propagate through the system. Guest access being disabled in your organization is incorrect because guest access and external access are two different features with different purposes. Guest access allows external users to be invited into your organization’s teams and channels as guests, giving them access to internal resources and collaboration spaces. External access allows users from different organizations to communicate with each other while remaining in their respective organizations. Presence visibility for external users with whom you communicate through federation relies on external access configuration, not guest access settings. Even if guest access is disabled, external access can still function and provide presence information for federated users. Users needing Teams calling policies enabled is incorrect because calling policies control what calling features are available to users, such as whether they can make private calls, use call forwarding, delegate calling, or configure voicemail. Calling policies do not affect presence information visibility. Presence is a core feature of Teams that works independently of calling capabilities and does not require specific calling policies to be enabled for users to see availability status of themselves or others. Presence information requiring Microsoft 365 E5 licenses is incorrect because presence functionality is available across all Microsoft 365 and Office 365 plans that include Teams, including E1, E3, E5, Business Basic, Business Standard, and Business Premium plans. Presence is a fundamental feature of the Teams platform and does not require premium licensing. While E5 licenses provide additional advanced features such as advanced compliance tools, audio conferencing, and phone system capabilities, basic presence information is available to all Teams users regardless of license level.
