You are deploying Microsoft Skype for Business 3PIP phones to remote sites for use with Microsoft Teams. You need to sign each 3PIP phone in to Teams. What are two possible ways to achieve the goal?…

Question

Options

• AFrom the Microsoft Teams admin center, remotely provision a new device.
• BFrom the device, instruct a local user to sign in from a computer that connects to the device by
• CFrom the device, instruct a local user to sign in by using the device itself.
• DFrom the device, instruct a local user to use the direct inward dial (DID) number and PIN of the
• EFrom the device, instruct a local user to sign in from the web.

• A
  15% (3)
• B
  5% (1)
• C
  70% (14)
• D
  10% (2)

Explanation

Signing into Teams on 3PIP phones supports two user-initiated flows: directly entering credentials on the device itself (C), and using web-based sign-in (E), where a code is displayed on the phone and the user completes authentication at a URL (like aka.ms/teamsdevicelogin) from any browser. Both are supported authentication paths for 3PIP devices in the Teams environment.

Why the distractors are wrong:

• A - Remote provisioning from the Teams admin center applies to native Teams-certified IP phones, not 3PIP devices, which have limited admin center management support.
• B - There is no supported sign-in flow where a user connects to the phone from a separate computer; this describes no real Teams authentication method.
• D - The DID + PIN method is used for common area phones or Skype for Business endpoints, not for signing individual user accounts into Teams on 3PIP hardware.

Memory tip: Think "C = on the Console, E = External web" - the two ways a local user can authenticate are directly on the phone's console or via an external web page, with no admin or DID shortcut available for 3PIP devices.

No community discussion yet for this question.