Blog Post

Skype for Business Blog
2 MIN READ

OAuth 2.0 and third-party application ID: Timeline extended to June 30, 2022!

Diana_Vank's avatar
Diana_Vank
Icon for Microsoft rankMicrosoft
Apr 25, 2019

New implementation timeline: June 30, 2022

 

To provide our customers with best-in-class security across our services, Microsoft is implementing the use of Microsoft Identity Platform 2.0 (an evolution of the Azure Active Directory identity service) which uses the OAuth 2.0 authorization protocol. OAuth 2.0 is a method through which a third-party app can access web-hosted resources on behalf of a user, through a third-party application ID.

 

This change only impacts Skype for Business IP Phones certified under 3PIP program.

 

Deployment Type

Impact Statement

Skype for Business Online

All phones must be updated and tenant admins must have approved phone partners App ID using the consent URL

Skype for Business On-Premises Hybrid (With Modern Auth Deployed)

All phones must be updated and tenant admins must have approved phone partners App ID using the consent URL

Skype for Business On-Premises Hybrid (No Modern Auth)

No Impact

Skype for Business On-Premises No Hybrid

No Impact

 

As result of this change, Skype for Business IP Phone partners have made a code change to embed the partner specific application ID in their firmware. The customer tenant admin will be required to confirm consent to allow the third-party phone application to be granted the necessary permissions (the same permissions currently being used by Skype for Business IP Phones).

 

 

Skype for Business IP Phone partners will provide customers with a partner specific consent URL. Customer admin will need to perform a one time, tenant wide (all users), consent per IP Phone partner (i.e. one consent URL for Yealink, one consent URL for Crestron, etc.)

 

Microsoft IP Phone partners will post additional information via their own communication channels, including the firmware version that includes the necessary changes.

 

This change requires customers to perform a 2 step process:

Step 1: Accept permissions request using the consent URL (can be done at any time)

Step 2: Upgrade all impacted phones to the firmware version communicated by the Microsoft IP Phone partners

 

All certified Skype for Business IP phones must be updated by July 15th, 2020 (originally January 15th, 2020). Without the update, successful authentication to Microsoft services on IP Phones will fail. Specifically, signing to the device via web or using a user name/password on the phone will fail. Customers are encouraged to work with their certified Skype for Business IP Phone provider to make the update before the deadline.

Updated Jun 07, 2021
Version 7.0

134 Comments

  • rovert506's avatar
    rovert506
    Iron Contributor

    Suggestion:  instead of publishing an article giving a brief synopsis of something that will be "effective immediately" and "if you don't do this by 'X' date, logins will fail", include the pertinent information for IT Professionals and Service Owners to act accordingly.

     

    • What firmware versions are required per vendor?
    • Are AppIDs per vendor, per phone model, or other?
    • What S4B topologies does this impact?
    • How does this apply to ExO, specifically regarding Web Services access.
    • How are the AppIDs configured and added to the Office365 tenant/Azure AD?
    • How does this impact LPE devices or non 3PIP devices?

    I cannot emphasize how frustrating it is for customers (and partners) to receive messaging from the PG like this - which causes an immediate knee-jerk reaction - and then have to sift through subsequent communications for pertinent details on implementation.

     

    Measure twice, cut once - you're doing us all (including yourselves) a favor.

  • Will it be the same app / consent grant for all phones, or specific per provider? Can you provide the link?

  • Adam Fowler's avatar
    Adam Fowler
    Iron Contributor

    Could this be clarified if it's actually for Skype for Business Online only - based on the explanation, assume Skype for Business is actually unaffected (i.e. the on-prem one)?