MS-721 Practice Questions

A direct hybrid migration from Lync Server 2013 to Microsoft Teams is not supported. To enable a managed, low-impact migration with coexistence capabilities, the on-premises environment must first be upgraded to a supported version of Skype for Business Server (2015 or 2019). Microsoft provides a direct, in-place upgrade path from Lync Server 2013 to Skype for Business Server 2015. This process is designed to minimize service disruption by upgrading the existing servers. Once the environment is running Skype for Business Server 2015, you can configure the required hybrid connectivity with Microsoft 365 and begin moving users, including those with Enterprise Voice, to Teams in a controlled manner.

A. Migrating directly from Lync Server 2013 to Teams is not a supported hybrid path. This would require a disruptive cut-over migration, failing the "minimize impact" requirement.

B. This option is inefficient and incomplete. It only addresses Enterprise Voice users and involves a more complex side-by-side migration to a new server version, which is not the most direct upgrade path.

C. This is incorrect for the same reason as option A; a direct hybrid migration from Lync Server 2013 is not supported. It also fails to address the Enterprise Voice users.

1. Microsoft Documentation

"Plan hybrid connectivity between Skype for Business Server and Microsoft 365 or Office 365": This document specifies the prerequisites for a hybrid deployment. Under the "Prerequisites" section

it states

"To configure a hybrid deployment

you need to have one of the following supported topologies: A Skype for Business Server 2019 deployment... A Skype for Business Server 2015 deployment..." Lync Server 2013 is not listed as a supported topology for direct hybrid configuration with Microsoft 365/Teams.

2. Microsoft Documentation

"Upgrade to Skype for Business Server 2015": This official guide details the upgrade process. In the "Supported upgrade paths to Skype for Business Server 2015" section

it confirms

"Skype for Business Server 2015 supports in-place upgrade from Lync Server 2013." This validates the first step in the correct answer.

3. Microsoft Documentation

"Move users between on-premises and cloud": This document outlines the process for migrating users in a hybrid environment. The entire process is predicated on having a supported hybrid configuration in place

which

as established

requires Skype for Business Server on-premises

not Lync Server 2013. The document states

"Moving a user from on-premises to TeamsOnly requires Skype for Business hybrid to be configured."

In Microsoft Teams, phone numbers have specific "Usage" types: User (Subscriber) or Voice app (Service). Because the number is currently assigned to a user, you must first unassign it to make it available in your inventory. However, a number with a "User" usage type cannot be linked to a Resource Account. You must change the usage type to Voice app to make it compatible with an Auto Attendant or Call Queue. Once the usage type is updated, the final step is to assign the phone number to the specific Resource Account (IT Service Desk) associated with your Auto Attendant. Releasing the number would return it to the Microsoft pool, losing access to it.

Microsoft Learn: Manage phone numbers for your organization. Section: "Change the usage of a phone number." This document specifies that you must change the usage type of a number before it can be assigned to a different type of service or user.

Microsoft Learn: Set up an auto attendant. Section: "Prerequisites." This identifies the requirement for a Resource Account and a service-type (Voice app) phone number.

Microsoft Learn: Assign or change a phone number for a user. Section: "Unassign a phone number." Provides the procedure for disconnecting a number from a user identity.

Microsoft Learn: Manage resource accounts in Microsoft Teams. Section: "Assign a phone number to a resource account." Outlines the final step of linking a Voice app number to the account.

Statement 1 (No): Coordinated Meetings require reciprocal trust. While Room1 trusts Hub, and Hub trusts Room1, Room2 is not listed in any <TrustedAccounts> tags, nor does it trust any other account. Therefore, all three cannot participate in a single coordinated one-touch join.

Statement 2 (Yes): Room1 has Audio default="true" and enabled="true". Both Room2 and Hub have Audio default="false". In a coordinated setup, only one device should handle audio to prevent echo; here, Room1 is the designated leader for audio.

Statement 3 (Yes): All three devices have Video enabled="true" (Room1 and Hub) or are capable of configuration. In Coordinated Meetings, video can be toggled on multiple devices simultaneously if they are part of the trusted ecosystem.

Microsoft Learn: Configure Coordinated Meetings with Microsoft Teams Rooms on Windows and Surface Hub. Section: "Step 1: Create your Coordinated Meeting configuration file."

Microsoft Technical Documentation: XML configuration file (skypesettings.xml). Parameters for , , and

Microsoft Support: Set up Coordinated Meetings with Teams Rooms. Details on reciprocal trust requirements for accounts to appear on the console for one-touch join.

To ensure a specific employee's meeting invitations include a local dial-in number for Lisbon, two distinct actions are necessary. First, the employee's "Usage location" must be set to Portugal in the Microsoft 365 admin center. This is a fundamental prerequisite for assigning a phone number from that country to the user. Second, you must navigate to the employee's user profile within the Microsoft Teams admin center and edit their specific "Audio conferencing" settings. This allows you to assign the Lisbon service number to their profile, which will then be included in all meeting invitations they create, overriding the organization's default number.

B. Modifying the default conferencing bridge would incorrectly change the dial-in number for all users in the organization, not just the specified employee.

C. The Microsoft 365 E3 license now includes the Audio Conferencing feature. Therefore, assigning a separate add-on license is not necessary.

1. Microsoft Learn. (2024). Manage the Audio Conferencing settings for a user in Microsoft Teams.

Reference: Under the section "Set toll and toll-free numbers for a single user

" the documentation states: "In the left navigation

select Users > Manage users... Select the user from the list of available users... Next to Audio conferencing

select Edit... Use the Toll number and Toll-free number boxes to enter the numbers for the user." This directly supports option A.

2. Microsoft Learn. (2023). Assign licenses to users.

Reference: In the section "Assign licenses in the Active users page

" the documentation notes the importance of the Usage location property. It states

"If a user doesn't have a usage location specified

they're assigned the location of the organization. For some services

you can't assign a license to a user unless the user has a usage location." This establishes setting the usage location (Option D) as a prerequisite for assigning location-specific services like a Portuguese phone number.

3. Microsoft Learn. (2024). Audio Conferencing in Microsoft 365.

Reference: The article explicitly states: "Audio Conferencing has been added to the following Microsoft 365 and Office 365 subscriptions: Microsoft 365 Business Basic

Business Standard

Business Premium

E3

F1

F3...". This confirms that an add-on license (Option C) is not required for a user with an M365 E3 license.

The proposed solution uses New-CsTeamsMeetingPolicy to create a policy that disables video. However, Teams meeting policies are assigned to users or groups, not to network locations. This means the policy would restrict video for the assigned users regardless of where they are connecting from, whether at the specific corporate site or elsewhere. The solution fails to meet the core requirement of applying the restriction only when users are at the specified site. Location-based controls in Teams are managed through network configuration settings for features like Location-Based Routing or emergency calling, not through meeting policies.

A. Yes: This is incorrect because a Teams meeting policy is user-centric and applies globally to the assigned user, not dynamically based on their network site.

1. Microsoft Learn. (2024). Set-CsTeamsMeetingPolicy. "This cmdlet sets a Teams meeting policy for a user or the entire tenant." The scope is defined per-user

not per-location. Retrieved from https://learn.microsoft.com/en-us/powershell/module/skype/set-csteamsmeetingpolicy

2. Microsoft Learn. (2024). Manage meeting policies for audio and video. "You assign a policy directly to users

either individually or at scale through a batch assignment

or to a group that the users are members of." This confirms policies are not assigned to network sites. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/meeting-policies-audio-and-video

3. Microsoft Learn. (2024). Network settings for cloud voice features in Microsoft Teams. This document explains how network sites

subnets

and trusted IP addresses are configured for location-specific features like Location-Based Routing and dynamic emergency calling

which are distinct from meeting policies. Retrieved from https://learn.microsoft.com/en-us/microsoftteams/cloud-voice-network-settings

To apply a custom theme to a Microsoft Teams Rooms on Windows device, you must create and deploy a specific XML configuration file named SkypeSettings.xml. This file is placed in the C:\Users\Skype\AppData\Local\Packages\Microsoft.SkypeRoomSystem8wekyb3d8bbwe\LocalState directory on the device. Within this file, the element is used to specify the custom theme name, the path to the custom background image, and custom color components, which overrides the default themes provided with the system.

A. A configuration profile (e.g., in Intune) is a mechanism to deploy settings or files to a device, but it is not the configuration file itself. The question asks what to configure, which is the XML file.

C. A team template is used to create new teams with a predefined structure of channels and apps within the Microsoft Teams service. It does not affect the physical hardware or user interface of a Teams Rooms device.

D. A LayoutModification.xml file is used to customize the Windows Start screen layout for standard Windows 10/11 desktops, not the specific user interface or background of the Microsoft Teams Rooms application.

1. Microsoft Learn. "Manage a Microsoft Teams Rooms console settings remotely with an XML configuration file." This document explicitly states

"You can use the XML configuration file to... Apply a custom theme." It provides the exact XML structure under the "Apply a custom theme" section

demonstrating the use of and tags within the SkypeSettings.xml file.

2. Microsoft Learn. "Microsoft Teams Rooms themes." This page details the process of creating a custom theme

specifying that "Custom theme settings are applied using an XML file." It confirms that the SkypeSettings.xml file is the central component for this customization.

A Town hall is the recommended Microsoft Teams template for large-scale, one-to-many communications, replacing the legacy Live Events functionality. While a standard Town hall (included in Microsoft 365 E5) supports up to 10,000 attendees, it does not include Microsoft eCDN (Enterprise Content Delivery Network) by default. To satisfy the requirement for Microsoft eCDN support and real-time monitoring of the attendee experience, the meeting organizer must be assigned a Teams Premium license. Teams Premium includes the Microsoft eCDN entitlement, allowing for optimized bandwidth usage during large-scale internal broadcasts without requiring additional third-party infrastructure.

Microsoft Learn (Official Documentation):

Plan for Teams town halls: "Town hall organizers with a Teams Premium license have Microsoft eCDN enabled by default... For town hall organizers with all other Teams subscriptions, you can enable them to use the Microsoft eCDN solution or [certified partners]." (Last updated Sept 2025).

Microsoft Teams Premium - Overview for admins: Under the "Microsoft eCDN" section, it specifies that this feature is supported for town halls and view-only meetings, and organizers with a Teams Premium license use it by default.

Enterprise content delivery networks for streaming Microsoft Teams events: Confirms that if an organizer has a Teams Premium license, Microsoft eCDN is the default for town halls.

Microsoft Teams Feature Comparison:

Meetings, webinars, and town halls feature comparison: Lists "Town hall" as the primary replacement for Live Events with a capacity of 10,000 (Base) or 20,000+ (Premium) attendees.

Direct Guest Join (also known as third-party join) allows Teams Rooms users to join meetings hosted on other platforms like Zoom or Cisco Webex with a single touch, utilizing a web-based experience within the Teams Rooms interface.

Proximity join (utilizing Bluetooth beacons) allows a user’s personal Teams client (mobile or desktop) to detect a nearby Teams Room. Once detected, the user can "cast" or wirelessly share their screen/content to the room display and seamlessly add the room to their meeting.

Companion mode is used when a user is already in a meeting and joins from a second device to share content or use chat, while Together mode is a video layout feature, not a connectivity or casting tool.

Microsoft Learn (Official Documentation): "Enable Teams Rooms devices to join third-party meetings" (Topic: Direct Guest Join configuration).

Microsoft Learn (Official Documentation): "Wireless screen sharing with Proximity Join in Microsoft Teams Rooms."

Microsoft Tech Community (Official Blog): "Direct Guest Join for Microsoft Teams Rooms on Android and Windows," Section: One-touch join experience.

Microsoft Support: "Use Companion Mode to join a meeting on a second device" (Distinguishes companion mode from initial proximity casting).

New York Office: The requirement states that if an SBC fails, PSTN services must remain available through a local PSTN egress. To achieve local failover within the same site without relying on another geographical location, you must deploy a local redundant SBC pair (typically configured as a High Availability cluster). This ensures that the failure of a single physical unit does not disrupt the local egress.

Calgary Office: The requirement is to prioritize local egress but ensure availability during an outage while minimizing the number of SBCs. By selecting PSTN over WAN, Calgary can use the redundant SBC infrastructure in New York as a backup path. This satisfies the survivability requirement without needing to deploy a redundant pair at the branch site, thus minimizing hardware.

Official Vendor Documentation: Microsoft Learn. Plan Direct Routing - High Availability. "To provide high availability for Direct Routing, you can combine SBCs into clusters (redundant pairs) to handle local failures." [Section: SBC High Availability]

Official Vendor Documentation: Microsoft Learn. Configure Direct Routing - Path Selection and Failover. "You can configure voice routes to prioritize a local SBC and then fail over to an SBC in another site over the WAN if the local device is unreachable." [Section: Voice Routing Policies]

Official Vendor Documentation: Microsoft Learn. Microsoft Teams PSTN Connectivity Components. "Deploying local redundancy (HA) at primary sites while utilizing centralized SBC resources for smaller branch sites via WAN is a recommended architecture for cost-optimization." [Section: Design Considerations]

To enable four-digit internal dialing that translates to a full E.164 number (+14235551xxx) with minimal administrative effort, a Normalization Rule is used.

1. Pattern: The regular expression ^(\d{4})$ is the most efficient. The ^ and $ anchors ensure the rule matches exactly four digits. The parentheses (\d{4}) create a capture group containing those four digits.
2. Translation: The translation uses the captured group to construct the full number. In .NET regex (used by Teams), $1 represents the first captured group. Therefore, +1423555$1 appends the four dialed digits to the company's base prefix, resulting in the required E.164 format (e.g., dialing 1001 becomes +14235551001).

Microsoft Documentation: Create and manage dial plans, "Normalization rules" section. (Specifics on how Teams uses .NET Regex for digit manipulation). Microsoft Learn: Dial Plans

Microsoft Documentation: Direct Routing - Local Media Optimization, "Normalization Rules" subsection. (Reference for E.164 translation patterns). Microsoft Learn: Direct Routing

Microsoft Technical Reference: Regular Expression Language - Quick Reference, "Substitutions" section. (Detailing the use of $number for captured groups). Microsoft Learn: Regex Substitutions