nerdexam
Microsoft

MS-721 · Question #165

Case Study 3 - Contoso, Ltd Overview Company Information Contoso, Ltd. is an international manufacturing company that has 2,000 employees. Contoso currently uses a third-party meeting service. The com

The correct answer is Unassign +1416555555.; Change the usage type of +1416555555.; Assign +1416555555 to a new resource account for the reception area.. Reconfiguring an existing Teams Phone number for a new resource account requires unassigning it from its current use, potentially changing its usage type, and then assigning it to the new resource account for proper functionality.

Configure and manage Microsoft Teams Phone

Question

Case Study 3 - Contoso, Ltd Overview Company Information Contoso, Ltd. is an international manufacturing company that has 2,000 employees. Contoso currently uses a third-party meeting service. The company plans to migrate the meeting service to Microsoft Teams and replace all legacy video teleconferencing (VTC) devices. Physical Locations Contoso has offices in Toronto, New York, Rome, and London. The company has a global sales team that works remotely. Existing Environment Active Directory Environment The on-premises network contains an Active Directory Domain Services (AD DS) forest named contoso.com. Microsoft 365 and Teams Environment Contoso has a Microsoft 365 subscription. All users are licensed for Microsoft 365 E5 and Teams Premium. All users are enabled for Teams Phone by using Operator Connect. The contoso.com domain syncs to Microsoft 365 by using Azure AD Connect cloud sync. All users use the Microsoft Authenticator app for multi-factor authentication (MFA) to cloud services. A Microsoft Surface Hub device is deployed to the boardroom in each office. The reception area at the Toronto office is configured to use a phone number of +14165555555 in Teams. Problem Statements Contoso identifies the following issues: - A user in the London office cannot locate the recorded files from a recurring Teams meeting. - Executives in the New York office report having to use Microsoft Authenticator to access their Microsoft OneDrive files from the Surface Hub. - A user in the Toronto office reports receiving incoming calls while attending Teams meetings instead of having calls sent automatically to voicemail. Requirements Planned Changes Contoso plans to implement the following changes: - Deploy a new Teams-certified endpoint to all the boardrooms and huddle spaces in all the offices. - Start a pilot project to deploy an Intelligent Speaker to the boardroom in the Rome office and evaluate transcription and voice attribution capabilities. - Deploy a Teams shared device to the lunchroom in the Toronto office. Calls placed to +14165555555 must ring in both the reception area and the lunchroom. Technical Requirements Contoso identifies the following technical requirements: - The endpoint deployed to each boardroom must include a console on the table. The endpoint must automatically invite the existing Surface Hub when joining a Teams meeting. - The sales team must be able to temporarily sign in to the endpoints deployed to the huddle spaces to respond to Teams messages and attend video calls. - The endpoints deployed to the huddle spaces must allow only outbound emergency calls when a user is NOT signed in. - During Teams meetings, the sales team must have a watermark displayed on shared content. Drag and Drop Question You need to implement the planned changes for the +14165555555 reception area number. You create a new call queue. Which three actions should you perform in sequence next? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. Answer:

Exhibit

MS-721 question #165 exhibit

Answer Area

Drag items

Port +1416555555Release +1416555555Assign +1416555555 to the lunchroom device.Change the usage type of +1416555555.Unassign +1416555555.Assign +1416555555 to a new resource account for the reception area.

Correct arrangement

  • Unassign +1416555555.
  • Change the usage type of +1416555555.
  • Assign +1416555555 to a new resource account for the reception area.

Explanation

Reconfiguring an existing Teams Phone number for a new resource account requires unassigning it from its current use, potentially changing its usage type, and then assigning it to the new resource account for proper functionality.

Approach. The problem statement (implied by the solution) requires correctly setting up the phone number +14165555555 for the reception area using a new resource account, even though it's already 'configured to use' this number. This suggests a re-provisioning or a proper setup using modern Teams Phone capabilities. The correct interaction involves dragging the following three actions into the 'Answer Area' in the specified order:

  1. Unassign +14165555555: If the phone number is currently assigned to a user, a common area phone, or an older resource account, it must first be unassigned to free it up for its new configuration. This makes the number available in the tenant's number pool for reassignment.
  2. Change the usage type of +14165555555: Resource accounts (which are used for common area phones, auto attendants, or call queues) require a specific usage type, typically 'Service' numbers, distinct from direct-dial user numbers. If the number was previously assigned to a user or had a different usage type, this step is crucial to ensure it can be correctly assigned to a resource account.
  3. Assign +14165555555 to a new resource account for the reception area: This is the final step, where the now-available and correctly typed phone number is linked to the new resource account created for the reception area. This ensures the reception area has a dedicated and properly configured phone line in Teams.

Common mistakes.

  • common_mistake. Common mistakes include selecting irrelevant actions or performing the steps in the wrong order:
  • Selecting 'Port +14165555555' or 'Release +14165555555': Porting involves moving a number between different telecom carriers, which is not applicable here as the number is already in Teams via Operator Connect. Releasing a number makes it permanently available in the tenant's number pool, potentially for others to claim, but the goal is to re-use it immediately for a specific purpose within the same tenant.
  • Selecting 'Assign +14165555555 to the lunchroom device': This action is for a different location and device, not the reception area, and thus does not address the problem.
  • Incorrect Order of Operations: Attempting to 'Assign' the number before 'Unassigning' it from its current holder will fail because the number is already in use. Similarly, if the 'Change usage type' is required and not performed before the 'Assign' step, the assignment might fail or not function as intended for a resource account. The logical flow is to free the number, prepare it, and then assign it.

Concept tested. Microsoft Teams Phone System administration, including managing phone numbers (unassigning, changing usage types, and assigning), understanding the purpose of resource accounts for common area phones and shared devices, and the sequential steps involved in re-provisioning phone numbers within a Microsoft Teams tenant.

Topics

#Teams Phone#Call Queues#Shared Devices#Call Routing

Community Discussion

No community discussion yet for this question.

Full MS-721 Practice