Microsoft MS-700 Managing Teams Exam Dumps and Practice Test Questions Set 6 Q 76-90
Visit here for our full Microsoft MS-700 exam dumps and practice test questions.
Question 76:
You are the Microsoft Teams administrator for your organization. Users report that they cannot find external users when searching in Teams to start a chat. You need to enable communication with external organizations. Which feature should you configure in the Teams admin center?
A) Guest access
B) External access
C) Anonymous join
D) Shared channels
Answer: B
Explanation:
Understanding the differences between various external collaboration features in Microsoft Teams is crucial for Teams administrators. Organizations need to communicate and collaborate with external partners, vendors, and customers, but different scenarios require different configuration approaches. Microsoft Teams provides multiple mechanisms for external collaboration, each with distinct characteristics, security implications, and use cases. Selecting the appropriate feature ensures users can collaborate effectively while maintaining security and compliance requirements.
External collaboration in Teams operates through several distinct features that are often confused. Each feature serves different purposes and provides different levels of access and control. Guest access allows adding external users as members of teams with full participation capabilities. External access enables communication between organizations through federated chat and calling. Shared channels allow collaboration without changing organizational boundaries. Understanding these distinctions prevents misconfiguration and ensures the right feature is enabled for specific business requirements.
A) is incorrect because guest access allows inviting external users as guests who become members of specific teams within your organization, but it doesn’t enable searching for and starting chats with any external user. Guest access requires explicitly inviting external users through email invitations, after which they appear in your directory and can participate in teams they’re added to. Guests cannot be discovered through search by your users—they must be invited first. Guest access is appropriate for long-term collaboration where external users need team membership, but it doesn’t address the scenario of users searching for and chatting with external contacts from other organizations.
B) is correct because external access (formerly called federation) enables users to search for, find, and communicate with users from other organizations through chat and calling without requiring guest invitations or team membership. When external access is enabled and configured to allow specific domains or all external domains, your users can search for external users by their email addresses, add them as contacts, and initiate chats or calls. The external users remain in their own organization’s tenant and aren’t added to your directory. External access provides peer-to-peer communication capabilities across organizational boundaries, which directly addresses the requirement for users to find and chat with external users.
C) is incorrect because anonymous join is a meeting feature that allows people without Teams accounts or organizational credentials to join Teams meetings through a meeting link without signing in. Anonymous join enables external participants to attend meetings but doesn’t provide chat or search capabilities outside of meetings. Anonymous participants can only interact within the specific meeting context and cannot be searched or contacted for ongoing conversations. This feature addresses meeting participation scenarios rather than general external communication through search and chat.
D) is incorrect because shared channels allow teams to invite external users to collaborate in specific channels while maintaining their home tenant identity, but shared channels don’t enable searching for arbitrary external users to start chats. Shared channels require creating a channel, configuring it as shared, and explicitly inviting external users or teams. External users don’t become searchable contacts for general chat purposes. Shared channels are designed for structured collaboration on specific topics while keeping external users separate from team membership, but they don’t provide the general search and chat capabilities described in the scenario.
When configuring external access, administrators can choose to allow all external domains, block specific domains, or allow only specific domains based on organizational security policies. External access configuration affects the entire organization, and administrators should work with security teams to establish appropriate policies. Additionally, both organizations must enable external access for communication to work—if the external organization blocks your domain, communication won’t be possible even if your organization allows theirs.
Question 77:
You need to configure a policy that prevents users from recording Teams meetings. The policy should apply only to users in the Sales department. What should you do first?
A) Modify the Global meeting policy
B) Create a new meeting policy and assign it to Sales users
C) Configure meeting settings in the Teams admin center
D) Modify the default messaging policy
Answer: B
Explanation:
Microsoft Teams uses policies to control user capabilities and experiences across various features including messaging, meetings, calling, and apps. Understanding how policy assignment works, the relationship between global policies and custom policies, and the precedence of policy assignments is essential for implementing granular control over Teams features for different user groups. Organizations often need different capabilities for different departments, roles, or user populations, requiring targeted policy configurations rather than organization-wide settings.
Teams policies follow a hierarchical model where global policies provide default settings for all users, but custom policies can be created and assigned to specific users or groups to override global settings. The global policy applies to all users who don’t have a custom policy assigned. When implementing requirements that apply to specific user subsets, administrators must create custom policies and assign them appropriately. Understanding this model prevents accidentally affecting all users when changes should be targeted, and ensures policies are applied to the correct user populations.
A) is incorrect because modifying the Global meeting policy would affect all users in the organization who don’t have a custom meeting policy assigned, not just Sales department users. The Global policy serves as the default for all users, and changes to it have organization-wide impact. If the goal is to prevent only Sales users from recording meetings while allowing other users to retain recording capabilities, modifying the Global policy would be too broad. The Global policy should contain the default settings for the general user population, with custom policies created for exceptions or specific groups.
B) is correct because creating a new meeting policy with the «Allow cloud recording» setting disabled and assigning it specifically to Sales department users implements the targeted control required. Custom policies override the Global policy for assigned users, enabling granular control. After creating the policy with appropriate settings, administrators can assign it to individual users, security groups, or use batch policy assignment for multiple users. This approach ensures only Sales users are affected by the recording restriction while other users continue following their existing policies. Custom policies are the correct mechanism for department-specific or role-specific controls.
C) is incorrect because meeting settings in the Teams admin center control organization-wide meeting behaviors and don’t provide user-specific or group-specific targeting capabilities. Meeting settings configure aspects like anonymous meeting join, meeting invitations, network requirements, and email integration that apply broadly across the organization. These settings aren’t the mechanism for controlling individual features like recording permissions for specific user groups. Meeting settings complement policies but operate at a different scope and don’t support the granular targeting required for department-specific controls.
D) is incorrect because messaging policies control chat and messaging capabilities like editing messages, deleting messages, chat retention, and read receipts, not meeting features like recording. Messaging policies and meeting policies are separate policy types controlling different aspects of Teams functionality. Meeting recording is configured through meeting policies specifically. Using the wrong policy type wouldn’t achieve the desired outcome. Teams administrators must understand which policy type controls which features to implement requirements correctly. Each policy type addresses specific functional areas within Teams.
After creating the custom meeting policy, administrators should assign it to Sales users using one of several methods: individual user assignment through PowerShell or Teams admin center, group policy assignment that automatically assigns the policy to members of a specified security group, or batch policy assignment for multiple users. Group policy assignment is often most efficient for department-specific policies as it automatically applies to new department members and removes itself when users leave the group.
Question 78:
Your organization uses Microsoft Teams for collaboration. You need to ensure that all Teams meetings are automatically deleted 60 days after they are created. Which feature should you configure?
A) Retention policy
B) Meeting policy
C) Expiration policy
D) Data loss prevention policy
Answer: C
Explanation:
Managing the lifecycle of Teams content including teams, channels, and associated data is crucial for maintaining organizational hygiene, controlling storage costs, and meeting compliance requirements. Microsoft Teams generates substantial content over time, and without proper lifecycle management, organizations accumulate outdated teams and content that consume resources and create information governance challenges. Understanding the different governance features available for Teams content management, their specific purposes, and how they differ from retention and compliance features ensures appropriate implementation of lifecycle policies.
Teams lifecycle management involves several features addressing different aspects of content and resource management. Retention policies control how long content is kept and when it’s deleted for compliance purposes. Expiration policies automatically remove teams and their associated resources after specified periods. Meeting policies control meeting features and capabilities. Data loss prevention prevents sensitive information from leaving the organization. Each feature serves distinct purposes, and selecting the appropriate feature requires understanding the specific requirement being addressed—in this case, automatic team deletion based on age.
A) is incorrect because retention policies control how long content like messages, files, and meeting recordings are retained for compliance purposes, but they don’t automatically delete entire teams or meetings as entities. Retention policies can delete messages after specified periods, but the team or meeting itself remains. Retention policies address compliance requirements for content preservation and deletion, operating on the data within teams rather than the teams themselves. A retention policy could delete meeting chat messages or recordings after 60 days, but wouldn’t delete the meeting entity or affect team structure.
B) is incorrect because meeting policies control user capabilities and features during meetings such as recording permissions, transcription, sharing options, and participant controls, but don’t manage meeting lifecycle or automatic deletion. Meeting policies are assigned to users and determine what features they can use in meetings. These policies don’t include settings for automatically deleting meetings based on age. Meeting policies control meeting functionality and user permissions, not content lifecycle. They operate during meeting creation and execution rather than post-meeting content management.
C) is correct because expiration policy (Microsoft 365 group expiration policy) automatically deletes inactive teams and their associated Microsoft 365 groups after a specified period, which can be configured to 60 days as required. When a team reaches its expiration period without activity, owners receive renewal notifications. If not renewed, the team is soft-deleted and can be restored within 30 days, after which it’s permanently deleted. Expiration policies help organizations maintain clean environments by removing unused teams automatically. This feature directly addresses automatic deletion of teams based on age, making it the appropriate choice for the scenario.
D) is incorrect because Data Loss Prevention (DLP) policies identify, monitor, and protect sensitive information from unauthorized sharing or disclosure, but don’t manage content lifecycle or automatic deletion. DLP policies scan content for sensitive data like credit card numbers, social security numbers, or custom sensitive information types, then apply protective actions like blocking sharing or requiring justification. DLP operates on content protection and compliance rather than lifecycle management. DLP prevents data loss incidents but has no functionality for automatic team or content deletion based on age.
When implementing expiration policies, administrators configure the expiration period (30, 60, 90, 180, or 365 days), specify whether it applies to all groups or selected groups, and determine notification intervals for team owners before expiration. Expiration policies can be configured to require renewal for inactive teams or automatically delete them. Organizations should communicate expiration policies to users, establish processes for reviewing and renewing active teams, and implement naming conventions and descriptions that help users identify team purposes when deciding whether to renew.
Question 79:
You are configuring phone system capabilities for your organization. Users need to make and receive calls using their Teams client. Which of the following must be assigned to users to enable this functionality?
A) Teams license only
B) Phone System license and Calling Plan
C) Audio Conferencing license
D) Teams Rooms license
Answer: B
Explanation:
Microsoft Teams Phone System represents Microsoft’s cloud-based telephony solution, replacing traditional PBX systems with cloud-based calling infrastructure. Understanding the licensing requirements for Teams calling capabilities is essential for Teams administrators because multiple licenses work together to provide complete telephony functionality. Simply having a Teams license doesn’t automatically enable external calling—specific additional licenses are required depending on the calling scenario and architecture. Properly licensing users ensures they have the capabilities needed while avoiding unnecessary costs for unused features.
Teams calling architecture operates through several components requiring specific licenses. The base Teams license included with Microsoft 365 subscriptions provides internal Teams-to-Teams calling within the organization. However, making and receiving calls to and from external phone numbers requires the Phone System add-on license, which provides PBX functionality like call queues, auto attendants, call forwarding, voicemail, and caller ID. Additionally, connectivity to the Public Switched Telephone Network (PSTN) requires either a Calling Plan (Microsoft’s PSTN connectivity), Direct Routing (using customer’s PSTN carriers), or Operator Connect (using certified carriers).
A) is incorrect because a Teams license alone enables only basic Teams collaboration features including chat, channels, Teams meetings, and internal Teams-to-Teams voice calling within the organization. Without the Phone System license, users cannot access PBX features, phone number assignment, or PSTN calling capabilities. The base Teams license doesn’t include telephony features needed to make and receive external phone calls. Organizations seeking only internal communication don’t need additional licenses, but any external calling scenario requires Phone System and PSTN connectivity licensing.
B) is correct because enabling users to make and receive external calls requires both the Phone System license (providing PBX functionality and call control features) and PSTN connectivity through a Calling Plan, Direct Routing, or Operator Connect. The Phone System license is an add-on to Microsoft 365 that provides telephony capabilities. Calling Plans provide Microsoft-managed PSTN connectivity with phone number assignment. Together, these licenses enable complete calling functionality allowing users to make and receive calls to and from external phone numbers using their Teams client. This combination provides the minimum required licensing for external calling scenarios.
C) is incorrect because Audio Conferencing licenses enable dial-in capabilities for Teams meetings, allowing meeting participants to join using traditional phone numbers when they cannot use the Teams application. Audio Conferencing provides bridge phone numbers and generates dial-in coordinates for meetings. However, Audio Conferencing doesn’t enable one-to-one calling capabilities or personal phone number assignment for users. Audio Conferencing and Phone System serve different purposes—Audio Conferencing is for meeting participation via phone, while Phone System enables personal calling capabilities. They’re complementary features but not substitutes for each other.
D) is incorrect because Teams Rooms licenses are designed for meeting room devices and shared collaboration spaces, not individual user calling capabilities. Teams Rooms licenses enable features for physical meeting rooms including calendar integration, join meetings functionality, and room device management. These licenses serve conference room equipment and shared devices rather than personal user calling. Individual users making and receiving calls need Phone System and Calling Plan licenses assigned to their user accounts, not Teams Rooms licenses which serve different use cases entirely.
When implementing Phone System, administrators must also configure voice routing policies (for Direct Routing scenarios), emergency location information, dial plans for normalization of dialed numbers, and caller ID policies. Users should be assigned appropriate phone numbers from Calling Plans or configured extensions for Direct Routing. Additional configuration includes setting up call queues and auto attendants for organizational call handling, configuring voicemail policies, and establishing calling policies that control which features users can access.
Question 80:
You need to prevent users from installing third-party apps in Microsoft Teams while still allowing them to use Microsoft-provided apps. Which type of policy should you configure?
A) App permission policy
B) App setup policy
C) Meeting policy
D) Messaging policy
Answer: A
Explanation:
Microsoft Teams extensibility through apps, bots, tabs, and connectors significantly enhances collaboration capabilities, but organizations need control over which apps users can access and install. Teams integrates with thousands of third-party applications from the Teams app store, custom line-of-business applications developed specifically for the organization, and Microsoft-provided apps. Understanding the different policy types controlling app behavior, their specific purposes, and how they work together ensures administrators can implement appropriate governance without blocking legitimate productivity enhancements or allowing security risks from unvetted applications.
Teams app governance operates through multiple policy types working in concert. App permission policies control which apps are available to users based on app publisher (Microsoft, third-party, custom). App setup policies control which apps are pinned in users’ Teams clients and installation behavior. Both policies work together to provide comprehensive app governance, but they address different aspects of app management. Organizations typically need to balance user productivity through app access with security and compliance requirements that may restrict certain app categories or specific applications.
A) is correct because app permission policies control which apps users can access and install based on app origin: Microsoft apps (published by Microsoft), third-party apps (published by external developers in the Teams store), and custom apps (developed specifically for your organization). App permission policies can globally allow or block each app category, or administrators can create detailed policies that allow specific apps while blocking others. To prevent third-party app installation while allowing Microsoft apps, administrators would create an app permission policy that blocks third-party apps and allows Microsoft apps, then assign this policy to appropriate users. This provides granular control over app access based on publisher.
B) is incorrect because app setup policies control which apps are installed and pinned in users’ Teams interface by default, and whether users can pin their own apps, but don’t control which apps users have permission to access or install. App setup policies provide user experience customization and can pre-install important organizational apps, but they don’t restrict access to app categories. A user could still access and install third-party apps even if they’re not included in the app setup policy, as long as app permission policies allow those apps. App setup policies manage the user interface and default installations, not permissions and access control.
C) is incorrect because meeting policies control meeting features and capabilities such as recording, transcription, screen sharing, breakout rooms, meeting reactions, and other meeting-specific functionality. Meeting policies don’t govern app installation or access permissions. They operate on meeting behavior and participant capabilities rather than the broader Teams environment and app ecosystem. Meeting policies and app policies are separate policy types addressing completely different functional areas within Teams. Attempting to control app access through meeting policies would be ineffective as they don’t include relevant settings.
D) is incorrect because messaging policies control chat and messaging features like message editing, deleting, read receipts, priority notifications, and message translation. Messaging policies govern communication capabilities within Teams conversations but don’t control app permissions or installation. Like meeting policies, messaging policies are a separate policy type addressing specific functional areas. Apps may integrate with messaging through bots or message extensions, but messaging policies don’t control app access. Each policy type in Teams has specific purposes and controlling app access requires the appropriate policy type.
When configuring app permission policies, administrators should review available apps in the Teams admin center’s Manage apps section, deciding which apps are approved for organizational use based on security reviews, data handling practices, and business value. Organizations often block third-party apps by default, then selectively allow specific vetted applications. Custom app policies might be created for different departments or user groups with varying app needs. After configuring permissions, administrators should communicate available approved apps to users and establish processes for requesting new app approvals.
Question 81:
Users report that external guests invited to teams cannot access files shared in channels. You verify that guest access is enabled. What is the MOST likely cause of this issue?
A) SharePoint external sharing is disabled
B) External access is not configured
C) Meeting policies are restrictive
D) The guests don’t have Teams licenses
Answer: A
Explanation:
Microsoft Teams’ architecture is deeply integrated with other Microsoft 365 services, particularly SharePoint and OneDrive for file storage. Understanding these dependencies is crucial for troubleshooting Teams issues because problems that appear to be Teams-specific often originate from configuration in underlying services. Guest access in Teams involves multiple service layers including Azure Active Directory for identity, SharePoint for file storage, and Exchange for calendar and email. When guest access issues occur, administrators must understand this multi-service architecture to identify the root cause effectively.
Files shared in Teams channels are actually stored in SharePoint document libraries associated with the team’s underlying Microsoft 365 group. Every team created in Teams has a corresponding SharePoint site where channel files reside. When guests access channel files, they’re actually accessing SharePoint content through the Teams interface. This dependency means SharePoint’s external sharing settings directly impact guest access to Teams files. If SharePoint sharing is restricted, guests cannot access files even when Teams guest access is enabled. This architectural relationship requires coordination between Teams and SharePoint configurations.
A) is correct because SharePoint external sharing settings control whether guests can access files in Teams channels. Teams relies on SharePoint for file storage, and SharePoint’s external sharing must be enabled for guests to access channel files. Even with Teams guest access fully enabled, if SharePoint external sharing is disabled at the tenant level or site level, guests will be unable to access files. Administrators must ensure SharePoint external sharing is enabled and configured to allow at least «Existing guests» or more permissive settings. This is a common configuration oversight where Teams settings are configured correctly but underlying SharePoint settings block guest file access.
B) is incorrect because external access (federation) and guest access are different features serving different purposes. External access enables communication with users from other organizations through chat and calling, but it doesn’t involve adding external users to teams or providing access to team resources like files. The scenario describes guests invited to teams who cannot access files—this is guest access functionality, not external access. External access configuration wouldn’t affect guest users’ ability to access channel files within teams they’ve been invited to. The issue described is clearly related to guest access and file sharing, not external access.
C) is incorrect because meeting policies control meeting features and capabilities, not file access permissions. Meeting policies govern settings like recording, transcription, screen sharing, and other meeting-specific functionality. They have no impact on guest users’ ability to access files shared in Teams channels. File access is controlled by SharePoint permissions and sharing settings, not meeting policies. While meeting policies might affect guests’ ability to share content during meetings, they wouldn’t prevent access to channel files. The problem described is fundamentally about file access permissions, not meeting capabilities.
D) is incorrect because guest users don’t need Teams licenses to access teams they’ve been invited to as guests. Guest access is covered by the host organization’s licenses, and guests can participate in teams, access files, join meetings, and use Teams features without purchasing their own licenses. Guests use their existing Microsoft 365 or Azure AD accounts from their home organization or Microsoft accounts if they don’t have organizational accounts. Licensing isn’t a factor in guest file access problems. The issue is related to sharing configuration rather than licensing requirements.
To resolve this issue, administrators should navigate to the SharePoint admin center, review external sharing settings at both the tenant level and the specific site level for affected teams, and ensure sharing is enabled appropriately. SharePoint offers several external sharing options: «Anyone» (most permissive), «New and existing guests,» «Existing guests only,» and «Only people in your organization» (most restrictive). For Teams guest access to work fully, at minimum «Existing guests» must be enabled. Additionally, administrators should verify that Azure AD external collaboration settings allow guest invitations and that no conditional access policies are blocking guest access.
Question 82:
You need to configure Teams to automatically transcribe all meetings for compliance purposes. Which setting should you configure?
A) Enable transcription in the Global meeting policy
B) Enable recording in meeting settings
C) Configure compliance recording policies
D) Enable live captions in meeting policy
Answer: C
Explanation:
Compliance and regulatory requirements often mandate recording or transcribing communications for industries like finance, healthcare, or legal services. Microsoft Teams provides multiple features related to recording and transcription, but they serve different purposes and operate through different mechanisms. Understanding the distinction between user-initiated recording, automatic transcription features, and compliance-driven recording ensures administrators implement appropriate solutions that meet legal and regulatory obligations without relying on manual user actions or optional features that might be disabled.
Teams offers several recording and transcription capabilities operating at different levels. User-controlled meeting recording allows meeting organizers or authorized participants to manually start recording meetings, with optional transcription. Live captions provide real-time speech-to-text during meetings for accessibility. Compliance recording is a specialized feature that automatically captures all audio, video, and screen sharing from calls and meetings for specific users who require policy-based recording for regulatory compliance. These are distinct features with different configuration mechanisms and purposes.
A) is incorrect because enabling transcription in meeting policies makes transcription available as an optional feature that users can enable during meetings, but it doesn’t automatically transcribe all meetings. Meeting policy transcription settings control whether users have the ability to enable transcription when recording meetings, but this depends on users choosing to record and enable transcription. For compliance purposes requiring all meetings to be transcribed automatically without relying on user actions, meeting policy settings are insufficient. Meeting policies provide user capabilities rather than automatic compliance-driven features.
B) is incorrect because enabling recording in meeting settings or policies allows users to record meetings manually, but it doesn’t ensure all meetings are automatically recorded or transcribed. User-controlled recording requires someone in the meeting to start recording, and participants can join meetings without recording being active. For compliance requirements demanding capture of all communications, relying on optional user-initiated recording is inadequate. Meeting recording settings provide capabilities to users but don’t enforce automatic capture for compliance. Organizations needing guaranteed recording must use policy-based compliance recording rather than user-controlled recording features.
C) is correct because compliance recording policies automatically record all calls and meetings for users who require policy-based recording for regulatory compliance. Compliance recording is configured through Teams admin center or PowerShell by designating compliance recording applications from certified partners that integrate with Teams. When users subject to compliance recording policies participate in calls or meetings, the sessions are automatically recorded by the compliance recording system without requiring user action. This ensures complete capture of communications as required by regulations like MiFID II, Dodd-Frank, or other industry-specific requirements. Compliance recording is the appropriate solution for automatic, policy-driven recording and transcription.
D) is incorrect because live captions provide real-time speech-to-text display during meetings for accessibility purposes, allowing participants to read spoken content as it occurs, but live captions don’t create stored transcripts for compliance purposes. Live captions are temporary, displayed during meetings, and aren’t saved for later review or compliance documentation. While valuable for accessibility, live captions don’t meet compliance requirements for maintaining permanent records of meeting communications. Compliance requires stored recordings and transcripts that can be reviewed and retained according to record-keeping regulations, which live captions don’t provide.
Implementing compliance recording requires working with certified compliance recording partners whose applications integrate with Teams through the compliance recording APIs. Organizations must configure compliance recording policies identifying which users require automatic recording, deploy and configure the partner’s recording solution, ensure adequate storage for recordings, and establish retention policies meeting regulatory requirements. Compliance recording typically applies to specific roles like traders, advisors, or executives in regulated industries rather than all users. Organizations should document their compliance recording policies and inform affected users about automatic recording as required by regulations.
Question 83:
Your organization has multiple office locations across different countries. You need to ensure that Teams assigns appropriate emergency addresses based on where users physically connect to the network. Which feature should you implement?
A) Dynamic emergency calling
B) Location-based routing
C) Network roaming policy
D) Emergency call routing policy
Answer: A
Explanation:
Emergency calling in Voice over IP (VoIP) systems like Microsoft Teams Phone System presents unique challenges compared to traditional telephony because IP connections don’t inherently indicate physical location. When users make emergency calls (like 911 in the United States or 112 in Europe), emergency services need accurate physical location information to dispatch help appropriately. Microsoft Teams Phone System requires configuration to provide location information, and organizations with mobile users or multiple locations need solutions that automatically update emergency location information based on where users are physically located when making calls.
Teams Phone System supports multiple approaches to emergency calling and location management. Static emergency locations can be assigned to users, but these don’t update when users move between locations. For organizations where users work from multiple office locations or travel frequently, static location assignment creates safety risks if emergency calls report incorrect locations. Dynamic emergency calling solves this by automatically detecting users’ network locations and associating them with appropriate emergency addresses. Understanding the difference between static and dynamic emergency calling capabilities ensures appropriate implementation for organizational needs and user mobility patterns.
A) is correct because dynamic emergency calling automatically updates users’ emergency locations based on their network connection using trusted IP addresses or subnet information configured in the Teams admin center. Administrators define network topology by configuring network sites, subnets, and trusted IP addresses, associating each with specific civic addresses. When users connect to the network from different offices, Teams automatically detects their location based on IP address and updates their emergency location accordingly. This ensures emergency calls include accurate current location information regardless of where users connect. Dynamic emergency calling is essential for organizations with multiple locations and mobile users.
B) is incorrect because location-based routing (LBR) is a feature for Direct Routing scenarios that prevents toll bypass by ensuring calls are routed according to geographic restrictions and toll regulations, not for emergency address assignment. LBR enforces policies ensuring inbound and outbound calls route through gateways in specific locations based on regulatory requirements. While location-based routing involves network location awareness, its purpose is toll compliance rather than emergency calling accuracy. LBR and dynamic emergency calling are separate features—LBR focuses on call routing compliance while dynamic emergency calling focuses on safety and emergency response accuracy.
C) is incorrect because network roaming policy controls voice and video quality by managing settings like media optimization when users connect from different networks, but it doesn’t manage emergency address assignment. Network roaming policies help optimize Teams performance for users connecting from home, corporate networks, or public Wi-Fi by configuring how Teams handles media traffic in different network conditions. While network location affects roaming policies, these policies don’t provide emergency calling location management. Network roaming policies address performance optimization rather than emergency services location accuracy.
D) is incorrect because emergency call routing policy controls how emergency calls are routed and whether they’re sent to security desk operations first or directly to emergency services, but it doesn’t automatically update user locations based on network connectivity. Emergency call routing policies define notification recipients, whether to enable enhanced emergency services, and routing behavior for emergency calls. While important for emergency calling configuration, routing policies assume location information is already established and focus on call handling procedures rather than automatic location detection and assignment based on network connection.
Implementing dynamic emergency calling requires several configuration steps: defining network regions, sites, and subnets in the Teams admin center with associated civic addresses; ensuring network infrastructure provides accurate IP information; configuring emergency addresses with precise location details including floor and room information where applicable; testing emergency calling from different locations; and establishing processes for maintaining network topology as office configurations change. Organizations should also consider emergency calling policies, notification settings for security teams, and user education about emergency calling capabilities and limitations.
Question 84:
You are implementing a Teams environment for a company with a hybrid deployment of Exchange. Users with mailboxes on Exchange Server on-premises report that they cannot schedule Teams meetings from Outlook. What is the MOST likely solution?
A) Enable OAuth authentication between Exchange and Azure AD
B) Migrate all mailboxes to Exchange Online
C) Disable hybrid configuration
D) Assign Exchange Online licenses to users
Answer: A
Explanation:
Microsoft Teams integrates deeply with Exchange for calendar functionality, meeting scheduling, and other collaboration features. In hybrid environments where some mailboxes remain on-premises while the organization uses Microsoft 365, proper authentication configuration between on-premises Exchange and Azure Active Directory is critical for Teams functionality. Understanding the authentication requirements for Teams in hybrid scenarios ensures administrators can troubleshoot scheduling issues and maintain full feature functionality across both on-premises and cloud resources without forcing premature migrations.
Teams meeting scheduling integration with Outlook requires calendar access through Exchange Web Services or REST APIs. In hybrid Exchange environments, Teams must authenticate to on-premises Exchange servers to access calendar information for users whose mailboxes haven’t migrated to Exchange Online. OAuth (Open Authorization) authentication provides secure, modern authentication between services without exposing credentials. When OAuth isn’t properly configured between Exchange on-premises and Azure AD, Teams cannot access on-premises mailboxes to schedule meetings, resulting in users being unable to create Teams meetings from Outlook despite having proper Teams licenses.
A) is correct because enabling OAuth authentication between Exchange Server on-premises and Azure Active Directory establishes the authentication trust necessary for Teams to access on-premises Exchange mailboxes for meeting scheduling. OAuth configuration involves running specific scripts on Exchange servers, registering Exchange as a trusted application in Azure AD, and configuring authentication policies. Once OAuth is properly configured, Teams can authenticate to on-premises Exchange on behalf of users and integrate meeting scheduling into Outlook. This is the standard solution for Teams meeting scheduling in hybrid Exchange environments and doesn’t require migrating mailboxes to resolve the issue.
B) is incorrect because while migrating mailboxes to Exchange Online would resolve the issue by moving mailboxes to the native Teams environment, it’s not the most appropriate solution for organizations maintaining hybrid environments intentionally. Many organizations keep mailboxes on-premises for specific business, compliance, or technical reasons and aren’t ready for complete migration. Forcing migration to solve an authentication configuration problem is excessive and disruptive. The issue can be resolved through proper OAuth configuration while maintaining the hybrid deployment. Migration is a strategic decision rather than a tactical troubleshooting step.
C) is incorrect because disabling hybrid configuration would break integration between on-premises Exchange and Microsoft 365, causing additional problems rather than solving the meeting scheduling issue. Hybrid configuration enables coexistence, directory synchronization, free/busy sharing, and other integrated features between on-premises and cloud environments. Removing hybrid configuration would eliminate these benefits and potentially impact mail routing, calendar sharing, and other essential functionality. Hybrid configuration is not the cause of the problem—improper authentication configuration is. Disabling hybrid would be destructive and counterproductive.
D) is incorrect because users with Exchange on-premises mailboxes don’t require Exchange Online licenses to use Teams, and adding Exchange Online licenses doesn’t automatically solve authentication configuration issues. Teams functionality is licensed through Microsoft 365 or Office 365 subscriptions that include Teams. While some scenarios benefit from Exchange Online Plan 1 or Plan 2 licenses for certain advanced features, basic Teams meeting scheduling doesn’t require Exchange Online licenses when mailboxes are on-premises—it requires proper authentication configuration. Assigning additional licenses doesn’t establish OAuth authentication or resolve the underlying authentication problem.
Configuring OAuth authentication requires running the Configure-EnterprisePartnerApplication.ps1 script on Exchange servers, ensuring the Exchange on-premises organization is registered as a partner application in Azure AD, configuring the appropriate permissions, and potentially updating Exchange Server to supported versions that include OAuth support. Administrators should verify that Exchange 2016 CU8 or later, or Exchange 2019, is deployed as earlier versions have limited OAuth support. After configuration, administrators should test by creating Teams meetings from Outlook for users with on-premises mailboxes, verifying that meeting details appear correctly and join links function properly.
Question 85:
You need to prevent specific users from initiating private chats in Teams while still allowing them to participate in team conversations and channel discussions. Which type of policy should you configure?
A) Messaging policy
B) Meeting policy
C) App setup policy
D) Teams policy
Answer: A
Explanation:
Microsoft Teams provides multiple communication modes including team channels for group conversations, private chats for one-to-one or small group discussions, and meetings for scheduled or ad-hoc collaboration. Organizations sometimes need granular control over which communication modes users can initiate based on regulatory requirements, organizational policies, or specific user roles. Understanding which policy types control which communication capabilities ensures administrators can implement appropriate restrictions without unnecessarily limiting collaboration or affecting unrelated features. Policy types are specialized for different functional areas within Teams.
Communication control policies operate at different levels and affect different interaction types. Messaging policies specifically control chat and messaging behaviors including the ability to send private chats, edit or delete messages, use priority notifications, and other chat-related features. Teams policies control team-specific capabilities like team creation and discovery. Meeting policies govern meeting functionality. Understanding these distinctions prevents attempting to configure restrictions through inappropriate policy types that don’t contain relevant settings. For controlling private chat initiation, messaging policies are the appropriate mechanism.
A) is correct because messaging policies include the «Chat» setting that controls whether users can initiate private one-to-one and group chats. When this setting is disabled in a user’s messaging policy, they cannot start new private chats but can still participate in team channel conversations and respond to existing chats others initiated with them. This provides the granular control described in the scenario—preventing private chat initiation while maintaining team collaboration capabilities. Messaging policies are assigned per user or group, allowing targeted application to specific users who require chat restrictions while other users retain full chat capabilities.
B) is incorrect because meeting policies control meeting-related features and capabilities such as allowing Meet Now, meeting recording, transcription, screen sharing, breakout rooms, and other meeting-specific functionality. Meeting policies don’t include settings for controlling private chat initiation or participation. While meetings and chats are both communication modes in Teams, they’re controlled by separate policy types. Attempting to restrict private chats through meeting policies would be ineffective as meeting policies don’t contain relevant settings. Meeting policies and messaging policies address different functional domains within Teams.
C) is incorrect because app setup policies control which apps are pinned in users’ Teams clients, whether apps are installed by default, and whether users can pin their own apps. App setup policies customize the user interface and app experience but don’t control communication capabilities like private chat initiation. App setup policies might affect which apps users see pinned in their Teams interface, but they don’t restrict core Teams communication features. Communication control is handled through messaging and meeting policies, not app-related policies which focus on the app ecosystem rather than native Teams communication features.
D) is incorrect because Teams policies control team-specific capabilities including the ability to create private teams, discover teams through search, and create channels, but don’t control private chat functionality. Teams policies govern team creation and management features rather than messaging or communication behaviors. Private chats exist outside the context of teams as person-to-person or group conversations, and their control falls under messaging policies rather than Teams policies. Each policy type has specific functional domains, and understanding these boundaries ensures correct policy selection for implementing requirements.
When implementing messaging policies that restrict private chat, administrators should consider the impact on user workflows and communication patterns. Some roles may legitimately require private chat capabilities for sensitive discussions or cross-organizational collaboration. Organizations might create multiple messaging policies: a standard policy allowing all messaging features for general users, and restricted policies for specific user groups with chat limitations. Communication about policy changes and the reasons behind restrictions helps users understand limitations and identify appropriate alternative communication methods for their needs. Messaging policies can be assigned through the Teams admin center or PowerShell.
Question 86:
Your organization wants to prevent users from sharing sensitive information in Teams messages. You need to implement a solution that automatically detects and blocks messages containing credit card numbers. Which feature should you configure?
A) Information barriers
B) Retention policies
C) Data loss prevention (DLP) policies
D) Sensitivity labels
Answer: C
Explanation:
Protecting sensitive information from accidental or intentional disclosure is a critical security and compliance requirement. Microsoft Teams handles vast amounts of organizational communications daily, and without proper controls, sensitive data like financial information, personally identifiable information, or intellectual property could be inadvertently shared. Microsoft 365 provides multiple information protection features, each designed for specific protection scenarios. Understanding the purpose and capabilities of each feature ensures administrators implement appropriate controls that effectively prevent data loss while minimizing disruption to legitimate communications.
Information protection in Microsoft 365 operates through several complementary technologies. Data Loss Prevention (DLP) identifies sensitive information in content and enforces protective actions. Sensitivity labels classify and protect content based on organizational taxonomy. Information barriers prevent specific groups from communicating. Retention policies manage content lifecycle. Each technology addresses different protection requirements, and selecting the appropriate feature depends on the specific threat being mitigated—in this case, preventing sensitive data patterns like credit card numbers from being shared through Teams messages.
A) is incorrect because information barriers prevent specific users or groups from communicating with each other based on organizational policies, but they don’t detect or block sensitive information within allowed communications. Information barriers are used in scenarios where regulatory or organizational requirements mandate communication restrictions between departments, such as preventing investment bankers from communicating with analysts to avoid conflicts of interest. Information barriers control who can communicate with whom, not what content can be shared. They segment organizations into communication boundaries but don’t analyze message content for sensitive data patterns like credit card numbers.
B) is incorrect because retention policies control how long content is kept and when it’s deleted to meet compliance requirements for record retention or data minimization, but they don’t prevent sharing of sensitive information. Retention policies operate on content lifecycle management, specifying retention periods for messages, files, and other content. They can preserve content for legal or compliance reasons or delete it after specified periods. Retention policies don’t analyze content for sensitive information or block messages in real-time. They address data retention and disposal requirements rather than preventing data disclosure or loss during communication.
C) is correct because Data Loss Prevention (DLP) policies automatically detect sensitive information like credit card numbers, social security numbers, or custom sensitive information types within Teams messages and enforce protective actions such as blocking the message, providing user notifications and policy tips, or requiring user justification. DLP policies can be configured with pre-built sensitive information types for common data patterns like credit cards, or custom patterns specific to organizational needs. When users attempt to send messages containing detected sensitive information, DLP policies can prevent sending, warn users, or notify administrators. This directly addresses the requirement to detect and block credit card numbers in Teams communications.
D) is incorrect because sensitivity labels provide classification and protection for content based on organizational taxonomy (like Public, Internal, Confidential, Highly Confidential), but they’re applied manually by users or automatically through auto-labeling policies based on content inspection. Sensitivity labels can enforce protections like encryption, access restrictions, or visual markings, but in Teams, they primarily apply to files and meetings rather than real-time message analysis and blocking. Sensitivity labels are classification mechanisms that help users make appropriate handling decisions and enforce organizational protections, but they don’t automatically detect specific sensitive data patterns like credit card numbers in messages before sending.
Implementing DLP policies for Teams requires enabling DLP in the Microsoft Purview compliance portal (formerly Security & Compliance Center), creating or using pre-configured DLP policies that include Teams locations, selecting appropriate sensitive information types to detect, configuring policy actions for when sensitive information is detected, and determining whether to enforce blocking immediately or run in test mode initially. Organizations should communicate DLP policies to users so they understand restrictions and can handle sensitive data appropriately. Policy tips in Teams can educate users in real-time when they attempt to share sensitive information, promoting security awareness while enforcing policies.
Question 87:
You manage Teams for an organization with multiple departments. The marketing department needs the ability to create teams, but other departments should not have this capability. How should you configure this requirement?
A) Modify the Global teams policy
B) Create a custom teams policy and assign it to marketing users
C) Configure Microsoft 365 Group creation policies
D) Use Azure AD administrative roles
Answer: C
Explanation:
Microsoft Teams’ architecture is built on Microsoft 365 Groups (formerly Office 365 Groups), meaning every team created in Teams is actually a Microsoft 365 Group with associated resources including a SharePoint site, Exchange mailbox, Planner, and OneNote. Understanding this architectural foundation is crucial because many Teams management capabilities, particularly team creation permissions, are controlled through Microsoft 365 Group settings rather than Teams-specific policies. When administrators want to restrict who can create teams, they must understand that this control exists at the Microsoft 365 Group level, and Teams inherits those permissions.
Team creation permissions in Microsoft 365 follow a hierarchical model. By default, all users can create Microsoft 365 Groups (and therefore Teams), but organizations often want to restrict this capability to prevent uncontrolled proliferation of teams and maintain governance. While Teams policies control various team-related features and behaviors, the fundamental permission to create teams is governed by Microsoft 365 Group creation policies configured through Azure AD or PowerShell. Understanding this distinction between feature policies (Teams policies) and creation permissions (Group policies) is essential for implementing team creation restrictions correctly.
A) is incorrect because the Global teams policy controls team-specific features and capabilities like team discovery options but doesn’t control who has permission to create teams. Teams policies govern feature availability such as whether users can discover private teams or whether certain Teams features are enabled, but they don’t include settings for restricting team creation permissions. The Global teams policy applies to all users who don’t have custom teams policies, but modifying it wouldn’t restrict team creation to specific users or departments. Creation permissions operate at a different level than feature policies.
B) is incorrect because custom teams policies control team-related features and discovery settings but don’t include team creation permissions. Teams policies can be created and assigned to specific users to control their team experiences regarding discoverability and features, but the underlying permission to create teams is controlled through Microsoft 365 Group settings, not Teams policies. While custom Teams policies are valuable for managing team features, they don’t address the fundamental question of creation permissions. Attempting to restrict team creation through Teams policies alone would be ineffective.
C) is correct because Microsoft 365 Group creation policies control who has permission to create Microsoft 365 Groups, which directly controls who can create Teams since teams are built on Groups. Administrators can configure Group creation restrictions using Azure AD or PowerShell to limit group creation to members of specific security groups. To implement the requirement, administrators would disable default group creation permissions, create a security group containing marketing department users, and configure Azure AD settings to allow only that security group to create groups. This effectively restricts team creation to marketing users while preventing other departments from creating teams.
D) is incorrect because Azure AD administrative roles like Global Administrator, Teams Administrator, or Groups Administrator provide broad administrative privileges for managing Teams and Groups across the organization but don’t provide a mechanism for giving regular users team creation permissions while restricting others. Administrative roles are designed for IT administrators who manage the service, not for delegating creation capabilities to specific user populations. Assigning administrative roles to marketing users would give them excessive permissions including the ability to manage other users’ teams and administrative settings. Administrative roles are inappropriate for implementing user-level creation restrictions.
Implementing Microsoft 365 Group creation restrictions requires using Azure AD PowerShell to configure group settings templates, creating a security group containing users who should have creation permissions, and applying the template to enforce restrictions. Organizations should establish clear team creation governance including naming conventions, approval processes where appropriate, team lifecycle management, and guidance on when to create new teams versus using existing ones. Communication about team creation policies and the governance rationale helps users understand restrictions and identify appropriate processes for requesting teams when needed. Some organizations implement self-service portals or approval workflows for team creation requests.
Question 88:
Users report that they cannot see presence status (Available, Busy, Away) for other users in the organization. What is the MOST likely cause of this issue?
A) Privacy mode is enabled in Teams admin center
B) Exchange Web Services connectivity issues
C) Presence policy is misconfigured
D) Firewall is blocking Teams traffic
Answer: A
Explanation:
Presence information in Microsoft Teams provides real-time status visibility showing whether users are available, busy, in a meeting, away, offline, or using custom status messages. Presence awareness is fundamental to Teams collaboration, helping users decide whether to interrupt colleagues with messages or calls, understanding team availability, and improving communication efficiency. Several factors affect presence functionality including service connectivity, privacy settings, and Exchange integration. Understanding the architecture of presence in Teams and configuration options that affect presence visibility ensures administrators can troubleshoot presence issues effectively.
Teams presence integrates multiple data sources including calendar information from Exchange (showing busy when in meetings), active call or meeting status, user activity signals from Teams and Office applications, and manual status settings users configure. The presence service aggregates these signals to display accurate status. However, privacy considerations sometimes conflict with presence visibility—some organizations or users want to limit who can see their status. Teams provides privacy controls that affect presence visibility, and understanding these settings is crucial for troubleshooting widespread presence issues where no users can see others’ status.
A) is correct because privacy mode in the Teams admin center is a tenant-wide setting that, when enabled, hides presence information from users who don’t have each other in their contacts or aren’t part of common teams or conversations. Privacy mode was introduced to address privacy concerns in large organizations where users might not want their presence visible to everyone in the directory. When privacy mode is enabled and users haven’t established communication relationships, presence status shows as «Presence Unknown» or unavailable. If users are reporting organization-wide inability to see presence, privacy mode being inadvertently enabled would cause this symptom. Privacy mode represents a common administrative misconfiguration affecting presence visibility.
B) is incorrect because while Exchange Web Services (EWS) provides calendar information that influences presence status (showing busy during scheduled meetings), EWS connectivity issues wouldn’t cause complete inability to see presence status for all users. Presence functionality in Teams operates primarily through the Teams service, and even without Exchange connectivity, basic presence indicators based on Teams activity would still function. Users might not show as busy during calendar meetings if Exchange connectivity fails, but their presence status based on Teams activity would remain visible. Complete presence invisibility organization-wide suggests a configuration issue rather than Exchange connectivity problems.
C) is incorrect because there is no specific «presence policy» in Microsoft Teams that controls basic presence visibility. Presence functionality is controlled through privacy mode settings and user-level privacy settings rather than assigned policies like messaging or meeting policies. While various policies control other Teams features, presence visibility isn’t governed by a configurable policy type that would be assigned to users. The concept of a misconfigured presence policy suggests confusion about which settings control presence. Privacy mode and user privacy settings are the relevant configurations for presence visibility, not policy assignments.
D) is incorrect because if firewall configurations were blocking Teams traffic sufficiently to prevent presence functionality, users would experience broader Teams connectivity issues beyond just presence visibility. Teams uses HTTPS connections to Microsoft cloud services, and firewall blocking would likely prevent core Teams functionality including messaging, calling, and potentially authentication. Users would report inability to use Teams at all rather than specifically missing presence information. Presence is a lightweight feature within Teams’ overall connectivity, and if connections work for other Teams features, presence should function. Firewall issues would manifest more broadly than isolated presence problems.
To resolve presence visibility issues related to privacy mode, administrators should navigate to the Teams admin center, review privacy settings under Org-wide settings > Teams settings, and ensure privacy mode is configured according to organizational requirements. If privacy mode is intended for the organization, administrators should communicate to users that they may need to establish communication relationships (exchanging messages, participating in shared teams) before presence becomes visible. Organizations should balance privacy considerations with collaboration needs when deciding whether to enable privacy mode, considering that presence awareness significantly enhances Teams collaboration effectiveness and user experience.
Question 89:
You need to configure Teams to provide sign language interpretation during meetings for accessibility. Which feature should you enable in the meeting policy?
A) Live captions
B) Language interpretation
C) Transcription
D) Meeting reactions
Answer: B
Explanation:
Microsoft Teams continuously enhances accessibility and inclusion features to ensure all participants can fully engage in meetings regardless of language barriers or disabilities. Understanding the different accessibility and language features in Teams, their specific purposes, and how they differ from each other ensures administrators can enable appropriate capabilities for diverse organizational needs. Sign language interpretation, real-time captions, and transcription each serve different accessibility purposes, and selecting the right feature for specific requirements ensures meetings are inclusive and compliant with accessibility regulations.
Teams provides multiple features that might superficially seem to address similar needs but actually serve distinct purposes. Live captions provide real-time speech-to-text for the primary meeting language, helping participants who are deaf or hard of hearing or who prefer reading spoken content. Transcription creates searchable records of meeting speech. Language interpretation enables real-time human interpretation between languages or sign language interpretation, where interpreters can provide audio or video interpretation that participants select as their audio channel. Understanding these distinct capabilities and use cases prevents configuring inappropriate features for specific accessibility requirements.
A) is incorrect because live captions provide automated speech-to-text transcription of the primary meeting language displayed on participants’ screens in real-time, but they don’t provide sign language interpretation. Live captions use automated speech recognition to convert spoken words to text, helping participants who are deaf or hard of hearing follow along by reading captions. However, many members of the deaf community prefer sign language communication over text captions as sign languages are natural languages with distinct grammar and expression. Live captions and sign language interpretation serve different accessibility needs—captions provide text representation while interpretation provides visual language communication through interpreters.
B) is correct because the language interpretation feature in Teams enables meeting organizers to designate interpreters who can provide real-time interpretation, including sign language interpretation. When language interpretation is enabled in meeting policies and configured for a meeting, organizers can assign interpreters who provide interpretation between languages or provide sign language interpretation through video. Participants can select their preferred interpretation channel to hear (or see for sign language) the interpretation instead of the original audio. This feature specifically addresses sign language interpretation requirements by enabling designated interpreters to provide video-based sign language while participants who need interpretation can view the interpreter’s video feed in a prominent position.
C) is incorrect because transcription creates text records of meeting speech that can be reviewed during and after meetings, but like live captions, it doesn’t provide sign language interpretation. Transcription captures spoken content in text form for record-keeping, review, or accessibility purposes. While valuable for creating meeting records and helping participants review what was discussed, transcription is text-based and doesn’t provide the visual language communication that sign language interpretation offers. Transcription and interpretation address different needs—transcription creates textual records while interpretation facilitates real-time communication across language barriers including sign languages.
D) is incorrect because meeting reactions allow participants to express emotions or feedback during meetings using icons like thumbs up, applause, or hearts, but they have no relationship to sign language interpretation or accessibility features. Meeting reactions are engagement tools that provide non-verbal feedback mechanisms without interrupting speakers. While reactions can enhance meetings by allowing silent acknowledgment and feedback, they don’t address accessibility requirements for participants who need sign language interpretation. Reactions are participation features rather than accessibility accommodations.
Implementing sign language interpretation requires several configuration steps: enabling language interpretation in meeting policies assigned to users who will organize meetings requiring interpretation, educating meeting organizers on how to configure interpretation when scheduling meetings, designating interpreters who will provide sign language interpretation, and ensuring interpreters have appropriate video and bandwidth capabilities for clear sign language visibility. Organizations should establish processes for requesting interpretation services, maintaining rosters of available interpreters, testing interpretation setups before important meetings, and training both meeting organizers and participants on using interpretation features effectively.
Question 90:
Your organization uses Teams Phone System with Direct Routing. You need to ensure that when users make outbound calls, the caller ID displays the company’s main phone number instead of individual user numbers. Which configuration should you implement?
A) Caller ID policy
B) Call park policy
C) Call queue configuration
D) Dial plan normalization
Answer: A
Explanation:
Caller ID management in Teams Phone System provides important control over how your organization presents itself to external call recipients and manages identity for different calling scenarios. Organizations often want outbound caller ID to display corporate main numbers rather than individual user extensions or direct numbers for privacy, branding, or call management purposes. Understanding Teams Phone System caller ID configuration options, including how to set organization-wide defaults and user-specific overrides, ensures administrators can implement appropriate caller ID presentation that meets business requirements while complying with regulations prohibiting caller ID spoofing.
Caller ID in Teams Phone System can be configured at multiple levels with different precedence. Users have default caller IDs based on their assigned phone numbers. However, administrators can override these through policies to substitute different numbers, display resource account numbers, or anonymize caller ID. Caller ID policies specify what number appears for outbound calls, whether users can override their caller ID, and whether incoming caller ID is blocked or modified. Understanding the distinction between caller ID policies and other calling features prevents confusion about which configuration mechanism controls outbound caller ID presentation.
A) is correct because caller ID policies in Teams Phone System control what phone number is displayed for outbound calls and whether users can override their caller ID settings. Administrators can create caller ID policies that substitute users’ default phone numbers with alternative numbers like the company main number, using the CallingIDSubstitute parameter set to «Resource» or «LineUri» with specified replacement numbers. When this policy is assigned to users, their outbound calls display the configured substitute number instead of their individual phone numbers. This directly addresses the requirement to display the company main number for outbound calls, providing centralized control over caller ID presentation.
B) is incorrect because call park policies control the call park feature that allows users to place calls on hold and retrieve them from another device using call park pickup codes. Call park enables scenarios where users need to transfer calls between devices without formally transferring to another user. Call park policies configure settings like call park timeout duration and pickup ranges but have no relationship to caller ID presentation. Call park is a call handling feature rather than a caller ID management mechanism. These are separate functional areas within Teams Phone System.
C) is incorrect because call queue configuration manages how incoming calls are handled by automated call distribution systems, including settings for queue greeting, music on hold, call routing methods, and agent alert behaviors. Call queues can have caller ID settings that determine what caller ID agents see when receiving calls from the queue, but they don’t control outbound caller ID for individual users making calls. Call queues are inbound call management features rather than outbound caller ID control mechanisms. The requirement describes outbound calling scenarios, not call queue operations.
D) is incorrect because dial plan normalization rules convert dialed numbers into E.164 format for call routing purposes but don’t control what caller ID is displayed to call recipients. Dial plans help users dial using familiar formats like extensions or local numbers while the system normalizes them to proper international format for routing. Dial plans operate on dialed numbers (destination) rather than caller ID (source). While important for call routing, dial plans don’t address caller ID presentation requirements. Caller ID display and dial plan normalization are separate functions in Teams Phone System.
Implementing caller ID policies requires creating policies through Teams admin center or PowerShell, configuring the CallingIDSubstitute parameter to specify whether to use a resource account number, specified line URI, or other options, and assigning the policy to users who should display the company main number. Organizations must ensure the substitute number is validated and owned by the organization—Teams doesn’t allow arbitrary caller ID spoofing. Some regions have regulations requiring caller ID accuracy and prohibiting misleading caller ID, so organizations should implement legitimate business-purpose caller ID substitution rather than deceptive practices. Users can be educated about why their outbound calls display corporate numbers and given guidance on when to use direct numbers if policies allow user overrides.