Skype for Business phones (3PIP) support with Microsoft Teams

Published Aug 06 2019 07:43 AM 56.7K Views
UPDATE: Support for Skype for Business (3PIP) phones has been extended beyond 2023, so you can continue to use your existing Skype for Business phones as you move to Teams. Additionally, we will be supporting core calling features on SIP phones from Cisco, Yealink, Polycom, and others with Teams. Support for SIP phones will be available in the first half of 2021. For more information click here.


We recently announced that Skype for Business Online will be retired on July 31, 2021, and we’re encouraging existing customers to start planning their migrations to Teams. This blog post answers questions about Teams support for Skype for Business phones, also known as 3rd Party IP or 3PIP phones.


What does this mean for customers who have 3PIP Phones with Skype for Business Online?

Skype for Business Online customers who move to Teams can continue using their 3PIP phones with some functionality limitations until July 31st, 2023. For more details on the supported feature set see our post from last November on this topic.


After July 31st, 2023, we will no longer support 3PIP phones on Teams. To ensure business continuity, these phones should be replaced with native Teams certified phones. We are continuously working on enhancing the feature set available on Teams phones.


What are the benefits of a native Teams phone?

Some of the key benefits customers would experience using a native Teams phone include contacts* and calendar management, one-touch join for meetings, companion* experience between the Teams phones and PC/MAC clients and voicemail transcriptions on the phones.


Along with these features, customers can now deploy and manage their native Teams phones using the Device Management portal available through Admin Center, making it easier for tenant administrators to keep all their Teams devices up to date with the right policies.

*Features under development and will be made available soon.


What is the recommendation moving forward for customers?

Our recommendation for customers moving to Teams is to work with our phone partners who have various programs to support a refresh schedule to native Teams phones or Teams Capable phones. Customers should also consider establishing a phone refresh schedule along with a device persona evaluation which would help define the right Teams device for the right working style.


Phones Blog.png


Are there any implications for customers who remain on Skype for Business Server?

No, customers can continue to use and procure the 3PIP phones for use with Skype for Business Server. Note that we will no longer be adding any new Skype for Business certified devices to any product category, including phones.


What if I have bought a Skype for Business phone which is upgradeable to Teams?

Customers who purchased upgradable Skype for Business phones (Teams Capable Phones) should plan and align their upgrade of the Teams UI on the phone to that of their scheduled Teams migration.


Are there partner led programs/offers available?

Yes, our partners are offering programs and support to ensure that customers can move to Teams phones, current offers are:

Where can our customers go to see the broad portfolio of Teams devices which are available?

Customers can visit our Teams Devices Showcase for devices across Personal and Shared spaces. Customers have the choice in manufacturer and models from AudioCodes, Crestron, and Yealink who have native Teams certified phones available in market today. Poly have also recently announced their native Teams phones which is planned to GA late this year.


We are convinced that our portfolio of Teams devices will allow our customers to have a broader selection of purpose-built devices which offers them new and exciting features.


Our customers have the opportunity today, to re-evaluate the way they work and communicate using devices. As customers advance forward with Teams, the opportunity to become even more productive using a Teams device is now.

Version history
Last update:
‎Feb 02 2021 10:57 AM
Updated by: