{"id":4266,"date":"2023-05-09T00:00:17","date_gmt":"2023-05-08T23:00:17","guid":{"rendered":"https:\/\/www.sebae.net\/blog\/deadline-approaching-to-migrate-3pip-phones-to-microsoft-teams-through-sip-gateway\/"},"modified":"2023-05-09T00:00:17","modified_gmt":"2023-05-08T23:00:17","slug":"deadline-approaching-to-migrate-3pip-phones-to-microsoft-teams-through-sip-gateway","status":"publish","type":"post","link":"https:\/\/www.sebae.net\/blog\/deadline-approaching-to-migrate-3pip-phones-to-microsoft-teams-through-sip-gateway\/","title":{"rendered":"Deadline approaching to migrate 3PIP phones to Microsoft Teams through SIP Gateway"},"content":{"rendered":"
\n

Microsoft retired Skype for Business Online (SfBO) in July 2021, and the deadline to complete your SfBO upgrade\/migration is rapidly approaching.<\/p>\n

\u00a0<\/p>\n

To help protect the investment that you have made in Skype for Business Online phones (3PIP phones) and help you upgrade to Teams<\/a>, we offer a solution through SIP Gateway<\/a> to enable these devices to securely connect and function as Microsoft Teams endpoints. We encourage you to make necessary updates as soon as possible<\/strong> because Skype for Business Online will be permanently turned off on July 31, 2023<\/strong><\/u>.<\/p>\n

The following are a few scenarios that can help you chart the course of action for your organization:<\/p>\n

    \n
  1. You have compatible<\/a> 3PIP devices connecting to Teams via SIP Gateway on July 31, 2023 \u2013 no action needed on your part, your phones will continue to work via SIP Gateway.<\/li>\n
  2. You have compatible<\/a> 3PIP devices connecting to Teams, but not through Teams SIP Gateway on July 31, 2023 \u2013 your phones will stop working, unless you take steps described below to upgrade your devices to connect to Teams through SIP Gateway.<\/li>\n
  3. You have incompatible 3PIP devices connecting to Teams on July 31, 2023 \u2013 your devices will stop working, you must replace them with Teams phone devices or compatible<\/a> Teams SIP devices for continued scenario support.<\/li>\n<\/ol>\n

    How you can get help with your upgrading to SIP Gateway<\/strong><\/span><\/h2>\n

    SIP Gateway is the recommended approach for customers to continue using 3PIP phones to connect and work with Teams. We recognize that the upgrade of 3PIP devices to SIP Gateway can be lengthy, and so we highly encourage beginning the process as soon as possible. There are several resources available to support you through the migration process.<\/p>\n

      \n
    1. To help facilitate your migration, we will be providing a self-serve playbook to help you through the process step by step. Be sure to check this blog again in the coming days for a new link.<\/li>\n
    2. We are also pleased to announce a Microsoft Teams \u2018Ask Microsoft Anything\u2019 (AMA) live event specific to maintaining your 3PIP Phone<\/a> connectivity on Thursday, May 11. Similar to a \u201cYamJam\u201d on Yammer or an \u201cAsk Me Anything\u201d on Reddit, this AMA gives you the opportunity to connect with members of the product engineering team who will be on hand to answer your questions and listen to feedback.<\/li>\n
    3. Reach out to us through your Microsoft account representatives or Support if you have any questions and stay tuned for more details.<\/li>\n<\/ol>\n

      Discover Your Existing Deployed 3PIP Devices<\/strong><\/span><\/h2>\n

      To identify existing 3PIP devices deployed within your environment, the sign in logs contained within the Azure AD Admin Center<\/a> can be leveraged to identify recent sign registration events by filtering on “Skype for Business Certified Phone,”<\/strong> as shown below:<\/p>\n

      \"Skype<\/span><\/p>\n

      \u00a0<\/p>\n

      3PIP Discovery PowerBI Template<\/strong><\/span><\/h2>\n

      As an additional option to identify remaining active 3PIP devices deployed across your environment, a new PowerBI template has been released leveraging latest media session details (via Call Quality Dashboard) to further summarize locations where 3PIP devices may remain for migration:<\/p>\n