Blog Post

Microsoft Teams Blog
4 MIN READ

How to Deploy Teams Phone Devices

Francisco_Ortiz's avatar
Nov 29, 2023

Teams phone devices are a great way to stay connected and productive with your colleagues and customers. These devices are designed to provide a seamless calling and meeting experience. With just three easy steps, you can deploy a Teams Phone device certified by Microsoft, in your spaces and enjoy advanced calling features.

 

Step 1: Consider the space Teams phone device will be used in

  • Personal Space: Used on an employee’s desk to make and receive calls.
  • Shared Space: Used in a shared space, such as a lobby, a building floor, or anywhere your employees and visitors need quick access to make call.

The space you choose will determine the type of license you will need.

 

Step 2: Pick the licenses and workloads you will need for the space

 

Calls

People

Voicemail

Walkie Talkie

Calendar

 

Teams Phone license

Yes

Yes

Yes

Yes

Yes

Teams Shared Device license

Yes

Yes

Yes

Yes

No

Teams Rooms Pro license

Yes

Yes

No

No

Yes

 

Licenses:

  • Teams Phone license: If the phone device is used at a user’s desk, you can use the same Teams Phone License used on Teams desktop or Teams mobile app allowing you to make and receive calls and join meetings on the phone device. Teams subscriptions with Teams Phone license enables calling between Teams on mobile, desktop and phone device. With Microsoft Calling plans add-on license you can make and receive calls to and from a phone number over PSTN network.
  • Teams Shared Device license: If you are using the phone device in a shared space, such as a lobby or a building floor, you will need a Shared Device license that will allow users to use the device for calling purposes. Shared Device license comes included with a Teams Phone license enabling use of advanced calling features such as call queue, auto attendant, etc.
  • Teams Rooms Pro license: If you are using the audio-conferencing device in a small meeting room, you will need a Teams Rooms Pro license that will allow you to join audio meetings with one touch.

 

Workloads:

  • Calls: Manage calls, search the directory, and use speed dial for quick calling. Users can also use advanced calling features such as call queue and auto attendant.
  • People: Add and manage contacts and contact groups.
  • Voicemail: View voicemail history and associated actions.
  • Walkie Talkie: Users part of a Teams channel can broadcast messages to other users' part of the same channel.
  • Calendar: Schedule and join meetings.

 

Step 3: Setup desired phone device experience for your users

First, Configure IP Phone Policy SignInMode parameter via powershell to enable associated apps on phone device.

  • With UserSignIn mode get Calls, People, Voicemail, Walkie Talkie and Calendar apps when Personal License is assigned to the account
  • With CommonAreaPhoneSignIn mode get Calls app when Shared Device License is assigned to the account. Additionally, you can enable “Advanced Calling” setting on phone device or Teams Admin Center to get People, Walkie Talkie and Voicemail apps.
  • With MeetingSignIn mode get Calendar app with meeting join experience when Teams Rooms Pro license is assigned to the account.

Then, choose from the below home screen experiences you want to enable for your users. On touch and non-touch phones you can choose to enable one of the following experiences:

  • Basic Calling Experience: On an account signed in with CommonAreaPhoneSignIn mode you can offer a basic Dialpad and Speed Dial view by disabling the “Advanced Calling” setting.
  • Advanced Calling Experience: On an account signed in with CommonAreaPhoneSignIn mode you can offer a home screen experience with Calls, People and Voicemail apps by enabling “Advanced Calling” setting.
  • Hotline Experience: On an account signed in with CommonAreaPhoneSignIn mode and assigned with Shared Device license you can enable “Hotline” setting to offer a PLAR (Private line auto ringdown) experience.

In addition to the above you can choose from following experiences on touch phones.

  • Calls App Experience: On an account signed in with UserSignIn mode or CommonAreaSignIn mode (with Advanced Calling enabled) you can set the Calls app to be your default home screen by disabling Homescreen.
  • Meeting Experience: An account signed in with MeetingSignIn mode will get meeting join experience.

 

Best Practices:

  • Manage firmware and Teams app updates: Enable auto updates of firmware via Teams admin center and assign devices to different rings (Validation, General, Final) to roll out updates in phases. You can assign the Validation ring to a small set of test phones and assign other phones to General and Final rings. Note: Auto updates on Teams application is coming soon. Currently, you can schedule Teams application update via Teams admin center.
  • Manage Authentication: For password management review Authentication best practices.
  • Configure calling policies: Configure different calling policies based on your needs.
  • Optimize phone memory usage: Enable daily or automatic restart of Teams application on the phone device via configuration profile to optimize phone performance.
  • Secure common area phones: Set an Admin PIN on common area phones via configuration profile to provide secured access to settings on phone devices in shared spaces.
  • Secure personal phones: Ask your users who use phones in personal spaces to set a phone device lock PIN for secured access instead of setting a default phone device lock PIN via configuration profile.

 

Updated Nov 30, 2023
Version 4.0
  • MatthiasMichl's avatar
    MatthiasMichl
    Brass Contributor

    well, this is a great overview, but there are substantial lacks that make Admins' life extremely difficult.

     

    When MS moved away from the Common Area Phone License to the Shared Device License, they have removed the option to run the MeetingSign in mode default calendar view (or calendar as a whole at all as it seems). To give those phones the full user experience is way too much, and giving them the calls only experience is way too less.

     

    Which means, for Common Area Phones that are the Yealink CP96x or the Poly Trio (voice only devices), you either need to assign an Fx-License with PhoneSystem - which for those Devices is overkill - they simply need to call... Or you assign the Meeting Room Pro, which is complete overkill. (or Basic - yes, but 25 free licenses for a 10.000+ user company - you do not come very far with that...)

     

    in turn, it is stated here, that "People, Walkie Talkie and Voicemail" can be enabled with the CommonAreaPhone Signin, by enabling advanced calling. Problem: if i want the CAP experience only, but the Phone(-account) itself should be part of a Call Queue/Group Pickup, i am screwed as well. quote: ("

    Then, choose from the below home screen experiences you want to enable for your users. On touch and non-touch phones you can choose to enable one of the following experiences:

    • Basic Calling Experience: On an account signed in with CommonAreaPhoneSignIn mode you can offer a basic Dialpad and Speed Dial view by disabling the “Advanced Calling” setting."

     

    Then, a little off topic, 

     

    What to do if you want a shared device (android smartphone, not Teams Phone) enrolled in intune as such and with an F- or E- Licensed user signed in to receive the reduced Teams Android client experience - similar as an account that would sign in with a Shared Device License?

     

    Also off topic: on Android devices (Teams Phone + Android Smartphone) the Teams client when attempting a new call in the dial pad view and search is enabled, a "," (comma) is NOT accepted when searching. it simply is ignored. A Ticket with MS lead to nowhere and the statement was that the issue does come from the underlying SDK, where Teams is programmed with... (sigh...). (Workaround option suggested: "Do not use commas in Displaynames"...) (sigh)

     

    (btw - my list is longer...)

  • AntCraig's avatar
    AntCraig
    Brass Contributor

    Agreed with both above posters. 

     

    The entire Phone experience is a mess. It should be a single license and the ability to change the UI for purpose. Requiring a MTR license for a Meeting room audio conferencing device is ridiculous. 

     

    I would also like to add that the documentation and information provided for configuring highly secure Intune and conditional access policies for these devices without is lackluster. Understanding the authentication processes is not readily available.   Add the Teams SIP Gateway into the mix and now Phones and devices might be the most difficult aspect of Microsoft Teams to design and implement successfully in large organizations.  

  • Pezz1980's avatar
    Pezz1980
    Copper Contributor

    Totally agree with MatthiasMichl, we have a customer with a lot of Poly Trio C60 and we are struggle on which type of license assign to the accounts: teams shared device license is non sense since these devices need calendar, teams rooms basic license fights with the limit of 25. The only choice is Fx+Teams Phone Standard but it is too much for this devices.

    Also I read "With CommonAreaPhoneSignIn mode get Calls app when Shared Device License is assigned to the account. Additionally, you can enable “Advanced Calling” setting on phone device or Teams Admin Center to get People, Walkie Talkie and Voicemail apps", but from my understanding from this ms learn document https://learn.microsoft.com/en-us/microsoftteams/set-up-common-area-phones#ip-phone-policies ,if an account is licensed with Teams Shared Device license the ip phone policy is not necessary. Is it only a way to classify the device as a Common Area Phone in Teams Admin Center?