Microsoft

MS-720 · Question #12

Case Study 2 - Litware, Inc 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…

Analysis Note The answer mapping data appears to be empty in this question (both source_items and correct_arrangement are []). This likely means the answer options weren't captured when the question was exported. I'll reconstruct the correct answer based on the technical…

Configure and manage Microsoft Teams Phone for voice users

Question

Case Study 2 - Litware, Inc 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

Analysis Note

The answer mapping data appears to be empty in this question (both source_items and correct_arrangement are []). This likely means the answer options weren't captured when the question was exported. I'll reconstruct the correct answer based on the technical scenario.

Context: What's Happening Here

Contoso is migrating from Skype for Business Server 2015 to Microsoft Teams using Direct Routing. jsmith is a Vancouver user, and Vancouver is the pilot site. Two key requirements apply specifically to Vancouver users:

Media path must be optimized during the pilot → requires Local Media Optimization (LMO)
Must be able to place emergency calls even without internet → requires the on-premises SBA to remain functional during transition

Correct Migration Sequence

For a user migration from on-premises Skype for Business Server to Teams with Direct Routing, the three steps in order are:

Step 1: Run `Move-CsUser` to move jsmith to Microsoft 365 / Teams

Move-CsUser -Identity "[email protected]" -Target "sipfed.online.lync.com" -MoveToTeams -Credential $cred

Why first: The user's identity and home server must be moved from on-premises AD/SfB to Azure AD / Teams before any cloud-side policies can take effect. You cannot assign Teams policies to a user still homed on-premises. The -MoveToTeams flag simultaneously sets the upgrade policy to TeamsOnly.

Common mistake: Trying to assign voice routing policies before moving the user. The cmdlets will either fail or silently have no effect because the user is still homed on-premises.

Step 2: Assign an Online Voice Routing Policy (`Grant-CsOnlineVoiceRoutingPolicy`)

Grant-CsOnlineVoiceRoutingPolicy -Identity "[email protected]" -PolicyName "Vancouver-VRP"

Why second: After the user is in the cloud, you need to tell Teams how to route outbound calls through Direct Routing (i.e., which SBC/PSTN gateway to use). Without this policy, the user has no dial-out capability via the Vancouver SBC. This policy maps to a PSTN usage that connects to the Vancouver SBC-which also enables Local Media Optimization for the pilot requirement.

Common mistake: Skipping this step and wondering why calls fail post-migration. E3 licenses don't automatically enable Direct Routing routing.

Step 3: Assign a phone number to the user (`Set-CsPhoneNumberAssignment` or `Set-CsUser`)

Set-CsPhoneNumberAssignment -Identity "[email protected]" -PhoneNumber "+1XXXXXXXXXX" -PhoneNumberType DirectRouting

Why third: The user must have a phone number assigned in the cloud after being moved, and this requires the user to already be TeamsOnly and have a voice routing policy active. The number must be typed as DirectRouting (not Calling Plan) since Contoso is using Direct Routing via the Vancouver SBC/PRI.

Common mistake: Using the old Set-CsUser -LineUri syntax without updating to the newer Set-CsPhoneNumberAssignment cmdlet, or assigning a Calling Plan number instead of Direct Routing.

Why This Order Is Non-Negotiable

Dependency	Reason
Move before policy	Cloud policies don't apply to on-prem homed users
Voice routing before number	Number assignment validates the routing policy is in place
TeamsOnly before calling	User must be in TeamsOnly mode to receive/make calls via Teams

Vancouver-Specific Considerations

LMO (Local Media Optimization): The voice routing policy must reference an SBC configured with GatewayLbrEnabledUserOverride and the correct network site. This is what "optimizes the media path" for the pilot.
Emergency calling (without internet): The on-premises SBA handles this even post-migration, as long as the SBC remains connected to the PRI. The migration of jsmith to Teams doesn't remove SBA functionality for emergency routing.

Topics

#Teams migration#Direct Routing#Teams Phone System#Hybrid voice

Community Discussion

No community discussion yet for this question.

Full MS-720 Practice