MicrosoftMicrosoftTristan Griffiths I believe the 'OAuth' portion of this change is what's causing a bunch of confusion. Technically, it irrelevant. What is relevant is that Microsoft originally provided access for 3PIP phones to O365 resources and authentication via a built-in Azure enterprise app which all 3PIP-qualified IP phones from all partners have been using. They want to change that so that the IP phones will only leverage a new, per-vendor app that customers can manage themselves (provide consent on a per-vendor level, and remove the app if desired). The fact that OAuth 2.0 and Identity Platform 2.0 are involved is really moot, as there is only one course of action: move to the new app model before they disable the old one.
New firmware versions for impacted devices, once updated, will only use the new app and not the old. So the process is:
1. Approve the third-party vendor app(s) for the device you have.
2. Update one device to at least minimum supported firmware version, or anything newer.
3. Test.
4. Update all devices so that none remain on older versions which can only use the original app as these will stop working at some point.
Once you get there, then it doesn't matter if/when Microsoft performs this change as you'll no longer be leveraging the old app.
