Explanation:
To connect analog devices to Teams, you must use a Teams-certified Session Border Controller (SBC). The SBC acts as the bridge between the public switched telephone network (PSTN) and Teams. Direct Routing is the service that connects your SBC to Microsoft Teams, and the ATAs (which physically connect the intercoms) must be registered with that SBC to be recognized and managed as part of the telephony system.

Correct Option:

C. Register the ATAs with a Teams-certified SBC.
Analog Telephone Adapters (ATAs) convert analog signals to digital SIP. For Teams to route calls to/from these devices, the ATAs must be configured as endpoints under the management of a Teams-certified SBC, which then presents them to Teams.

E. Enable Direct Routing to a Teams-certified SBC.
Direct Routing is the mandatory Microsoft service that allows you to connect your own SBC to Teams Phone. Without configuring a Direct Routing trunk between the SBC and Microsoft, the analog calls from the ATAs cannot enter the Teams network.

Incorrect Option:

A. Create a trusted application endpoint for Teams.
Trusted application endpoints are for interactive applications (e.g., contact center bots, automated attendants) that make or receive calls programmatically via the Microsoft Graph API. An analog intercom is a simple physical device, not a software application requiring this elevated API permission.

B. Create a resource account for each intercom.
Resource accounts are primarily used to assign phone numbers and licenses to cloud-based resources like Auto Attendants or Call Queues. An analog device is a physical endpoint managed via the SBC; its identity and routing are handled at the SBC level, not by a resource account in Teams.

D. Create a configuration profile for IP phones.
Configuration profiles apply to Teams-certified IP phones (e.g., Yealink, Poly). Analog devices connected via ATAs are not native IP phones and cannot receive or apply Teams device settings from these profiles.

Reference:
Microsoft documentation on "Configure an Analog Device" explicitly states the requirement for a Teams-certified SBC and Direct Routing, and details the step to create a user for the analog device on the SBC. (Microsoft Learn, "Configure an Analog Device").

Explanation:
For retail sites needing a carrier-managed PSTN solution that likely integrates with an existing provider, Operator Connect is the strategic recommendation. It allows the organization to procure PSTN services directly from a Microsoft-certified telecom operator within the Teams admin center, simplifying management while maintaining a direct relationship and potentially favorable rates with their chosen operator.

Correct Option:

C. Operator Connect.
This is a fully managed service where a certified operator provides the PSTN connectivity, SIP trunks, and numbers directly into Teams. It's centrally managed via the Teams admin center, offloads SBC maintenance from the customer, and is ideal for organizations seeking a streamlined, operator-managed solution without using Microsoft's own Calling Plans.

Incorrect Option:

A. Teams Calling Plans.
These are Microsoft's own PSTN minute and number bundles. While simple, they may not be cost-effective for high-volume sites, limit carrier choice, and might not be available in all regions. They don't leverage an existing carrier relationship.

B. Direct Routing without media bypass.
Direct Routing connects a customer-managed SBC to Teams. "Without media bypass" means all call audio (media) is routed through Microsoft's network, which increases latency and bandwidth usage. This is often less optimal for performance compared to enabling bypass where possible.

D. Direct Routing with media bypass.
This is the most performant Direct Routing configuration, allowing media to flow directly between the SBC and the user. However, it requires the customer to purchase, configure, and manage their own SBC and SIP trunks, which adds complexity and may not align with a desire for a fully managed solution.

Reference:
Microsoft's documentation on "Plan Operator Connect" describes it as a program for organizations to order PSTN services from a participating provider directly within Microsoft Teams, offering a managed alternative to Calling Plans and customer-managed Direct Routing.

Explanation:
In a traditional call queue with Conference mode disabled, the system performs a "call forwarding" action to the agent. If the agent's call forwarding settings (like "Forward my calls to voicemail" or "Always forward") are active, the call queue call can be intercepted and sent to voicemail instead of ringing the agent. Disabling Conference mode changes the call delivery method to a direct, simultaneous ring which bypasses the agent's personal forwarding rules.

Correct Option:

C. Conference mode.
When disabled, the Call Queue uses a "simultaneous ring" method to call agents. This method bypasses most of the agent's personal call forwarding settings, ensuring the queue call rings their device directly. This is the correct setting to guarantee agents receive the calls.

Incorrect Option:

A. Music on hold.
This setting controls the audio callers hear while waiting in the queue. Disabling it would result in silence, which is a poor user experience, but it does not affect the ability of agents to receive the call.

B. Attendant routing.
This is not a standard setting for a basic Call Queue. "Attendant routing" typically refers to a feature in Auto Attendants or specific routing methods, not a toggle that blocks agents from receiving calls.

D. Round robin.
This is an agent routing method (others include Serial, Attendant, Longest idle). It determines the order in which agents are called (e.g., distributing calls evenly). Changing the routing method affects call distribution but does not prevent agents from receiving calls altogether.

Reference:
Microsoft's documentation on "Call Queue settings" explicitly states: "If Conference mode is turned off, Call Queue calls will ring agents even if their call forwarding settings are set to Forward my calls to voicemail or Always forward." This is the critical technical reason for disabling it to ensure delivery. (Microsoft Learn, "Create a Call Queue - Settings").

Explanation:
To enable users for calling in a new location, you must first acquire phone numbers for them, then assign those numbers to the users, and finally configure the routing policies that govern how they can use those numbers to make calls. This process is managed centrally within the Microsoft Teams admin center for a streamlined deployment.

Correct Option:

A. From the Microsoft Teams admin center, assign a voice routing policy to the users.
A voice routing policy determines which PSTN routes (e.g., local, international) are available to the user. It is a required configuration for users to make outbound calls via Direct Routing or Operator Connect.

C. From the Microsoft Teams admin center, assign the phone numbers to the users.
After acquiring numbers, they must be explicitly assigned to individual users to become their official business line. This is done in the Teams admin center under Voice > Phone numbers.

E. From the Microsoft Teams admin center, order five user numbers.
For a new site, you must first procure the required phone numbers. The Teams admin center provides a self-service portal ("Get new numbers") to order numbers directly for supported PSTN solutions (Calling Plans, Operator Connect) in the required geographic area (United Kingdom).

Incorrect Option:

B. From the Microsoft 365 admin center, modify the office phone numbers of the users.
While you can edit a user's "Phone" attribute in the M365 admin center, this field is for informational (Active Directory) purposes only. It does not functionally provision a calling-enabled phone number in Teams Phone.

D. From the Microsoft Teams admin center, modify the dial-out settings of the users.
"Dial-out settings" is not a standard user-level setting in Teams admin center. Call routing is controlled by voice routing policies (correct option A), not a separate "dial-out" configuration.

F. From the Microsoft 365 admin center, create a support ticket to request five phone numbers.
Phone numbers for Teams are not requested via general support tickets. They are procured through the dedicated Voice > Phone numbers section in the Teams admin center, either via self-service ordering or through your Operator Connect provider.

G. From the Microsoft Teams admin center, assign a calling policy to the users.
A calling policy controls if a user can make private calls, use call forwarding, etc. While often necessary, the question's core requirements focus on acquiring and assigning the phone number itself and configuring routing. A calling policy does not enable PSTN connectivity without a number and a routing policy.

Reference:
The Microsoft Learn documentation on "Manage telephone numbers for your organization" outlines the process: 1) Get (order) numbers, 2) Assign numbers to users/resource accounts, and 3) Configure policies like voice routing policies for call authorization.

Explanation:
To provide a toll-free dial-in number for Teams meetings, you must set up a dedicated conference bridge with toll-free numbers. Because toll-free calls incur costs for the organizer's organization, Communications Credits are mandatory to pay for those inbound minutes. Finally, the toll-free number must be assigned to the conference bridge resource to make it available for use.

Correct Option:

A. Purchase Communications Credits.
Toll-free dial-in is a premium, billable service. Communications Credits are a mandatory pay-as-you-go monetary pool required to fund the costs of inbound toll-free calls to your conference bridges. Without it, the service cannot be enabled.

D. Get a Dedicated conference bridge (Toll Free) number.
You must specifically acquire a toll-free number of the type "Conference Bridge" (e.g., a TF-DEDICATED number). Standard user/subscriber toll-free numbers or geographic conference bridge numbers cannot be used for this purpose. This is done in the Teams admin center.

G. Assign a phone number to the bridge.
After acquiring the dedicated toll-free conference bridge number, you must explicitly assign it to your organization's conference bridge settings (found under Meetings > Conference Bridges). This action makes it available for organizers to select.

Incorrect Option:

B. Assign a phone number to a resource account.
Resource accounts are used for Cloud Auto Attendants and Call Queues, not for the shared conference bridge used by all Teams meetings. The conference bridge is a tenant-wide resource.

C. Get an auto attendant toll-free number.
Auto Attendant numbers are for interactive voice response (IVR) systems, not for dialing into meetings. The number type must be Conference Bridge.

E. Purchase a Microsoft 365 Domestic and International Calling Plan license.
Calling Plans are for user outbound PSTN calling. Audio Conferencing is the license required for dial-in capabilities. While often bundled, the Calling Plan itself is not a prerequisite for the toll-free bridge.

F. From the meeting policy, set Allow dial-in users to bypass the lobby to On.
This is a behavioral setting that controls whether dial-in users join the meeting directly or wait in the lobby. It is not a prerequisite for enabling or assigning the toll-free bridge number itself.

Reference:
Microsoft's documentation on "Set up Audio Conferencing for Microsoft Teams - Step 4: Get service phone numbers" specifies the need to get toll-free dedicated conference bridge numbers. The "Communications Credits" documentation states they are required for toll-free dial-in. The assignment step is covered in the Teams admin center interface for Conference Bridges.

Explanation:
A successful pilot validation requires confirming that the underlying network meets Microsoft's requirements for real-time media. The Microsoft 365 network connectivity test tool provides the most direct technical validation by measuring key metrics like latency, packet loss, and jitter from a user's location to the Microsoft network edge, which directly impacts call quality and meeting performance.

Correct Option:

A. Microsoft 365 network connectivity test tool.
This browser-based tool runs a series of tests from a user's endpoint to diagnose network performance, connectivity issues, and potential configuration problems that would degrade the Teams experience. It is the definitive tool for validating if the network infrastructure meets the technical prerequisites for a high-quality Teams deployment.

Incorrect Option:

B. Self-help diagnostics for Teams.
These are valuable for diagnosing specific, post-deployment issues for individual users (e.g., "Can't join a meeting"). They are reactive troubleshooting tools, not the comprehensive, proactive validation tool needed to certify the network for a pilot launch.

C. The Test-CsTeamsShiftsConnectionValidate cmdlet.
This PowerShell cmdlet is used exclusively to validate the connection between Teams and the Shifts app (for workforce management), often involving a third-party connector like UKG Dimensions. It is not a general-purpose pilot validation tool unless Shifts integration is the primary technical requirement.

D. The Teams device usage report in the Microsoft Teams admin center.
This report provides aggregate adoption and usage data (e.g., how many IP phones are active). It is an excellent tool for measuring rollout adoption after the pilot, but it does not perform a technical validation of network performance or feature functionality.

Reference:
Microsoft's documentation on "Assess your network connectivity with the Microsoft 365 network connectivity test tool" positions this tool as the primary method for evaluating network readiness and identifying potential issues before and during rollout, making it essential for pilot validation.

Explanation:
Deploying a Teams SBA involves creating its identity in Azure AD, provisioning it within Teams, and ensuring efficient media flow. The SBA acts as a local registrar and media gateway during an outage, so configuring media bypass on the primary SBC is essential to allow direct media flow between the SBA and endpoints when the SBC is unreachable.

Correct Option:

A. Register an application in Azure Active Directory (Azure AD).
The SBA requires an Azure AD application registration (service principal) for authentication and authorization to communicate with Microsoft Teams and obtain its configuration. This is a foundational identity and security prerequisite.

B. Run the New-CsTeamsSurvivableBranchAppliance Cmdlet.
This PowerShell command is the primary step to provision and define the SBA in the Teams backend. It creates the SBA object, associates it with a site, and links it to the assigned PSTN gateway (the SBC).

D. Configure the SBC for media bypass.
Media bypass must be enabled on the primary SBC (the online voice gateway) that serves the SBA's site. This configuration is critical for the SBA's function, as it allows media to flow directly between the SBA and Teams endpoints during normal operation, optimizing performance and enabling survivability scenarios.

Incorrect Option:

C. Enroll the SBA server in Microsoft Intune.
SBAs are physical or virtual appliances that run a dedicated, Teams-certified software image. They are not general-purpose servers managed by Intune. Their configuration and management are performed entirely through specific Teams PowerShell cmdlets (like the one in option B) and the appliance's local web interface.

E. Configure the SBC for call forking.
Call forking is used for scenarios like simultaneous ring to a mobile number or call delegation. It is not a requirement or standard configuration for SBA functionality. The SBA operates in a failover mode, not a forking mode.

F. Enable ForwardPAI on the online voice gateway.
Forwarding P-Asserted-Identity (PAI) is related to how caller ID information is passed in SIP headers. While sometimes used for compliance or interoperability, it is not a core prerequisite for deploying an SBA. The SBA's core requirement is connectivity and media path configuration, not specific header manipulation.

Reference:
Microsoft's documentation on "Configure a Survivable Branch Appliance" explicitly lists the steps: 1) Register an Azure AD app, 2) Run New-CsTeamsSurvivableBranchAppliance, and 3) Ensure the associated SBC is configured for media bypass. This aligns perfectly with options A, B, and D.

Explanation:
The question implies that prior technical requirements (likely related to policies or licensing) were implemented for the sales team. Meeting reactions (like "like," "love," "applause") are a core, baseline feature of Teams meetings. They require no special license, admin policy change, or storage configuration and work directly within the meeting client for all participants.

Correct Option:

A. Meeting reactions.
This is a fundamental in-meeting interaction feature enabled by default. After implementing general meeting policies or assigning Teams licenses (the implied requirement), users gain access to the standard meeting client, which includes reactions. No additional configuration for storage, compliance, or external sharing is needed.

Incorrect Option:

B. PowerPoint Live.
This feature allows presenters to share PowerPoint presentations in a special interactive mode. While part of Teams, it may have dependencies on specific Office licensing (Microsoft 365 Apps) and could be controlled by administrator policies (e.g., "Allow PowerPoint sharing") that might not have been part of the stated requirements.

C. Meeting recording.
Meeting recording is a highly policy-controlled feature. An administrator must enable it via Teams meeting policies (the "Allow cloud recording" setting). Furthermore, it requires configured storage (OneDrive for user meetings, SharePoint for channel meetings) and often depends on user licenses that include recording capabilities. Its availability is not automatic.

D. Whiteboard.
The Microsoft Whiteboard integration requires specific sharing policies to be enabled ("Whiteboard" must be allowed in the Teams admin center). It also depends on the Whiteboard service being provisioned and may have compliance or data residency considerations. Like recording, it is not a default-on feature.

Reference:
Microsoft's documentation on "Meeting policies in Teams - Audio & video" and "Sharing and content policies" shows that features like recording, live presentations, and Whiteboard can be individually allowed or blocked by an administrator. Meeting reactions, however, are a fundamental part of the meeting experience controlled by the "Meeting reactions" setting in meeting policies, which is typically enabled by default. The simplest and most universally available feature post-basic licensing is reactions.

Explanation:
A "lunchroom device" is a shared phone meant for transient use by multiple employees. Hot desking is the dedicated Teams feature designed for this exact scenario. It allows users to securely sign in to a shared device with their own credentials, accessing their personal call history, voicemail, and contacts, and then sign out when done, resetting the device for the next user.

Correct Option:

A. Hot desking.
This is the correct feature to implement. Hot desking transforms a shared Teams phone (like one in a lunchroom or lobby) into a personalized endpoint. Users sign in via a PIN, QR code, or proximity badge, making it their own for the duration of use. This provides personalized calling while maintaining security and shared access.

Incorrect Option:

B. Call hold.
This is a basic telephony function (placing a call on hold), not a configuration or management feature for a device. It does not address the need to manage a shared device for multiple users.

C. A calling policy.
Calling policies in Teams control user capabilities, such as whether they can make private calls, use call forwarding, or send calls to voicemail. While you would assign a policy to users who use the lunchroom phone, the policy itself does not implement the shared device functionality. The core solution to enable multiple users to use one device personally is Hot desking.

Reference:
Microsoft's documentation on "Set up hot desking" explicitly describes it as the solution for providing users with access to a shared workspace and phone. It details the process of configuring a Teams device for hot desking, which includes enabling the feature on the account and the device itself.

Explanation:
The solution states to redirect calls directly to a shared voicemail box. This would bypass the agents entirely, preventing them from answering live calls. It also does not provide a call queue history for agents to view, as no queue or agent interaction is being logged. While transcribed voicemails might land in a shared mailbox, the goal requires agents to handle calls first, with voicemail as a fallback, and have access to a history of their queue interactions.

Correct Option:

B. No.
This solution does not meet the goal.

Fails on Call Routing: Redirecting calls directly to voicemail means support agents never receive the calls, violating the primary requirement to route calls to them.

Fails on Call Queue History: A shared voicemail box does not provide agents with a viewable call queue history (e.g., missed, answered calls). That history is tracked within the Call Queue analytics and agent experience, not in a mailbox.

Minimizes Effort Incorrectly: While simple, it solves the wrong problem by eliminating the queue functionality entirely.

Incorrect Option:

A. Yes.
This would be incorrect. The proposed solution is a workaround that avoids using the Call Queue feature as intended. It does not fulfill the core requirements of routing calls to agents or providing them with a queue performance history. The correct approach would be to create a proper Call Queue with configured agents, set a Timeout routing action to send overflow calls to a shared voicemail (like a Cloud Voicemail-enabled resource account), and use Teams' built-in reports for queue history.

Reference:
The design of Teams Call Queues separates the routing of live calls to agents (via distribution lists or groups) from the configuration of fallback options like voicemail. The "Agent Experience" provides call history. Redirecting directly to voicemail circumvents the entire queue system and agent assignment.

Explanation:
The user can make internal calls (which are routed over Microsoft's internal network) but cannot make external PSTN calls. This specific symptom points directly to an issue with the PSTN calling configuration. External calls require a correctly configured and assigned voice routing policy that authorizes the call and selects the appropriate SBC/PSTN route based on the dialed number.

Correct Option:

B. The user has the incorrect voice routing policy applied.
A voice routing policy contains the PSTN usage records that authorize a user to make certain types of calls (e.g., Local, Long Distance, International) and links to the voice routes that determine which SBC (out of the 10) is used to complete the call. An incorrect or missing policy would prevent external dialing while internal calls remain unaffected.

Incorrect Option:

A. The user has the incorrect Teams app setup policy applied.
App setup policies control the pinned apps and default settings in the Teams client. They do not govern telephony routing or PSTN call authorization. This would not cause the specific failure of external dialing only.

C. The user is missing a validated emergency address.
Emergency address registration is a compliance and safety requirement for making emergency calls. The lack of one may block all PSTN calls, but often it only blocks emergency calling or generates a warning, while still allowing standard business calls. It is not the most likely cause for a complete failure of all external calls.

D. Enterprise Voice is disabled for the user.
"Enterprise Voice" is the Skype for Business / on-premises term for enabling a user for VoIP. In a Microsoft Teams Phone deployment, the equivalent is being licensed and enabled for Teams Phone. If this were disabled, the user would have no calling capabilities at all, including internal calls via the dial pad, which contradicts the scenario.

Reference:
Microsoft's documentation on "Manage voice routing policies" explains that these policies determine the call permissions and available routes for users. A user without an assigned policy, or with a policy lacking the correct PSTN usages, will be unable to place external PSTN calls.

Explanation:
To use Direct Routing (connecting your own SBC for PSTN calling), users must have a license that includes the Microsoft Teams service. This is a core component of both Microsoft 365 E3/E5 and Office 365 E3/E5 plans. Any of these licenses provide the Teams foundation; the separate Phone System add-on or included capability is then what authorizes enterprise calling features.

Correct Option:

D. Office 365 E3 or Microsoft 365 E3.
Both Office 365 E3 and Microsoft 365 E3 include the Microsoft Teams service. For Direct Routing, you also need the Phone System capability, which is included in the E5 plans but must be purchased as an add-on to the E3 plans. The question asks for licenses you can assign to achieve the goal, and both E3 licenses are valid base licenses to which the required Phone System add-on can be attached.

Incorrect Option:

A. Microsoft 365 E3 or Microsoft 365 E5.
This omits Office 365 E3/E5, which are also valid base licenses for Teams and Direct Routing. It is therefore not the complete list of correct options presented.

B. Office 365 E3 or Office 365 E5.
This omits Microsoft 365 E3/E5, which are equally valid. Therefore, it is an incomplete list of the correct possibilities from the given choices.

C. Microsoft 365 E5 or Office 365 E5.
While correct in that these licenses do achieve the goal (as both include Teams and Phone System), the question's phrasing does not restrict it to only licenses with built-in Phone System. The E3 plans, with the Phone System add-on, also achieve the goal, making this list incomplete.

Reference:
Microsoft's licensing documentation for "Teams Phone with Direct Routing" states the prerequisite is a license that includes Microsoft Teams (such as Office 365/Microsoft 365 E1, E3, or E5) and the Phone System add-on (included in E5, available as add-on for E1/E3). Therefore, both Office 365 E3 and Microsoft 365 E3 are valid base licenses to which Phone System can be added to meet the requirement.