Case Study 2 - Contoso Overview General Overview The network contains an Active Directory forest named contoso.com that syncs to Microsoft 365 by using Azure AD Connect. Domain controllers run Windows

To enable a user for Microsoft 365 Phone System with a specific voice routing policy from an on-premises Skype for Business deployment, the correct sequence involves assigning the Phone System license, migrating the user online, enabling enterprise voice, and then assigning the v

Implement and configure Teams Phone

Question

Case Study 2 - Contoso Overview General Overview The network contains an Active Directory forest named contoso.com that syncs to Microsoft 365 by using Azure AD Connect. Domain controllers run Windows Server 2019. Physical Locations Contoso has offices in Toronto, New York, and London. Contoso has a manufacturing facility in Vancouver. Contoso has a global sales team that works remotely without a physical corporate office. Existing Environment Active Directory Environment The network contains an Active Directory forest named contoso.com that syncs to Microsoft 365 by using Azure AD Connect. Domain controllers run Windows Server 2019. Microsoft Office 365 Contoso has a Microsoft 365 subscription. All users are assigned Microsoft 365 E3 licenses. Contoso uses Microsoft Exchange Online for email. Network Infrastructure All the offices connect to each other by using a private WAN. The Toronto office has a 1-Gbps internet circuit and the London office has a 100-Mbps internet circuit. Internet access for all the offices is provided through the Toronto and London offices. The remote sales team users connect to the networks by using VPN connections. The remote users use various connection types, including wireless and mobile. Skype for Business Server traffic for the remote users is routed through the VPN connections. Telephony Contoso uses a centralized Skype for Business Server 2015 deployment configured for disaster recovery between the Toronto and London datacenters. Each frontend pool connects to the PSTN through a pair of managed Session Border Controllers (SBCs) that provide Enterprise Voice and dial-in conferencing. Contoso has a Skype for Business Server Survivable Branch Appliance (SBA) and a local SBC that connects to a Primary Rate Interface (PRI) in the Vancouver manufacturing facility. Contoso has hybrid connectivity deployed between Skype for Business Server and Office 365. All SBCs are Microsoft Teams-certified. The returns department has an auto attendant that uses an ID or [email protected]. Requirements Planned Changes Contoso plans to migrate all existing services from Skype for Business Server to Teams. Direct Routing will be deployed for the existing SBCs. Existing meeting rooms have Skype for Business Server video endpoints that are Skype for Business Server-certified. The endpoints are not Teams-certified. You plan to use the video endpoints in Teams until the equipment is replaced with Microsoft Teams Rooms. A limited pilot of the Teams migration and the Direct Routing deployment will occur in the Vancouver facility before deployment to the entire company. Technical Requirements Contoso identifies the following technical requirements: During the limited pilot, the media path must be optimized. Media flow for the remote sales team users must be optimized. All sales team users require inbound toll-free audio conferencing. Users in the Vancouver facility must be able to place emergency calls regardless of internet availability. When users in the returns department dial out, the outbound calls must display Contoso and the department's phone number. The video endpoints for the existing meeting rooms must be able to be used for both voice and video conferencing in Teams meetings. Drag and Drop Question You need to migrate a Vancouver facility user named jsmith from Skype for Business Server to Teams. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. Answer:

Exhibit

Answer Area

Explanation

Approach. The goal is to enable user 'jsmith' for Microsoft 365 Phone System and assign the 'Vancouver' voice routing policy, considering the user is currently on an on-premises Skype for Business Server 2015 deployment. The correct interaction involves dragging the following four actions into the 'Answer Area' and ordering them as follows:

Assign the Microsoft 365 Phone System license to jsmith.
- Reasoning: A Phone System license is a fundamental prerequisite for a user to utilize Microsoft Teams Phone System features, including making and receiving calls and applying voice routing policies. Without this license, subsequent configuration steps related to Phone System will not function.
Run the following command. Move-CsUser -Identity [email protected] -Target sipfed.online.lync.com
- Reasoning: The scenario states 'Contoso uses a centralized Skype for Business Server 2015 deployment,' meaning jsmith is homed on-premises. To leverage Microsoft 365 Phone System (Teams Phone System), the user must be migrated from the on-premises Skype for Business environment to the online environment. The Move-CsUser cmdlet is used for this hybrid migration, moving the user to Skype for Business Online (which for voice capabilities, effectively means provisioning them for Teams).
Run the following command. Set-CsOnlineUser -EnableEnterpriseVoice $true -identity [email protected]
- Reasoning: After the user has been moved to the online environment, their Enterprise Voice capabilities need to be explicitly enabled within Microsoft 365. This cmdlet provisions the user for voice services in the cloud, allowing them to make and receive calls.
Run the following command. Grant-CsOnlineVoiceRoutingPolicy -identity [email protected] -PolicyName Vancouver
- Reasoning: Once Enterprise Voice is enabled, the specific 'Vancouver' online voice routing policy needs to be assigned to the user. This policy dictates how inbound and outbound calls for jsmith are routed, which is essential for Direct Routing or specific calling plan configurations.

Common mistakes.

common_mistake. A common mistake is selecting the 'Assign the Microsoft 365 Audio Conferencing license to jsmith.' action. This license is for scheduling and participating in audio conferences, not for direct Phone System calling capabilities, and is therefore not relevant to enabling a user for Phone System with a voice routing policy. Another mistake would be to apply the commands in an incorrect order. For example, trying to run Set-CsOnlineUser or Grant-CsOnlineVoiceRoutingPolicy before Move-CsUser would target an on-premises user with online-specific commands, leading to failure or incorrect configuration. Similarly, not assigning the Phone System license first would prevent the necessary features from being provisioned.

Concept tested. Microsoft Teams Phone System user provisioning in a hybrid Skype for Business environment, including licensing, user migration from on-premises to online, enabling enterprise voice, and applying online voice routing policies (often for Direct Routing).

Topics

#Teams Migration#Skype for Business Hybrid#Direct Routing#User Provisioning

Community Discussion

No community discussion yet for this question.

Full MS-721 Practice