Poly Microsoft Online Registration Azure Application Id

User Manual: Poly Poly Trio is not able to sign in to Skype for Business upgrade to 5.9.1 | Poly, formerly Plantronics & Polycom

Open the PDF directly: View PDF PDF.
Page Count: 4

DownloadPoly  Microsoft-online-registration-azure-application-id
Open PDF In BrowserView PDF
TECHNICAL ADVISORY- 137008
PN-3725-86064-003

Regarding Microsoft Online Device Registration
with OAuth 2.0 via 3rd party Azure Application ID
This technical advisory addresses the change announced by Microsoft related to the Microsoft Online device
registration requirement planned for January 15th, 2020. This change impacts Poly devices registered for Skype
for Business accounts.
The following Poly products are impacted by this change.
•
•
•

VVX Series
Trio 8800/8500,
RealPresence Group Series

Executive Summary
Microsoft published a blog article which announced their plan to revoke support for the existing Azure application
ID leveraged by third party device vendors including Poly, and instead require a partner specific application ID.
This change goes into effect on January 15st, 2020. To ensure uninterrupted operation, the customer will be
required to perform a two-step process:
1. A tenant-wide consent by a customers’ administrator to permit these devices to register to Azure Active
Directory.
2. Update firmware to impacted devices to support new vendor specific application ID.
Microsoft has announced that all certified Skype for Business devices must be updated by January 15th, 2020.
Without the update, authentication to Microsoft services on these devices will fail and you will no
longer be able to sign in to Skype for Business from these devices. Check the impacted topology in
the table below, and if applicable, please complete these two steps by January 15th, 2020.

Deployment Topology - This is applicable to authentication via OAuth 2.0
Deployment Type

Impact Statement

Skype for Business Online

All phones must be updated by January
15th, 2020 and tenant admins must have
approved phone partners App id using the
consent URL

TECHNICAL ADVISORY - 137008

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

All phones must be updated by January
15th, 2020 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

Step 1. Perform a tenant-wide consent by tenant administrator
A customer administrator (tenant administrator) must go to the consent URL and accept permissions. This
process can be performed at any time prior to Endpoint Device Firmware upgrade.

2

TECHNICAL ADVISORY - 137008

Step 2. Update device firmware
Poly will release an update that supports new Poly application ID for the following products.
Device Name

Firmware Version

Timeline

VVX Phones

5.9.4

September 2019

Trio (8800,8500)

5.9.1AA

September 2019

RealPresence Group Series

6.2.1.1

June 2019

CX5500

TBD

TBD

Note: Only Microsoft certified devices are impacted due this change and SoundStructure is not
part of Certified O365 devices.

FAQ
Question: What happens if
an upgrade to respective
firmware (listed in the table
above) is not performed?

Answer: Effective January 15th, 2020 when users attempt to sign-in on
devices that are not upgraded authentication will fail.

Question: Would all 3PIPqualified releases (such as
UC Software releases)
include App ID changes
proposed by Microsoft?

Answer: No, only the specified and later versions in the table will
have the changes. We request that customers go through the tenantwide consent first, then upgrade the device software.

Question: What happens if
device firmware is upgraded
without going through the
Consent URL?
Question: When should
tenant administrators
perform the consent?

Answer: Impacted users’ authentication will fail to sign in; the tenant
administrators are requested to perform the consent and retry the
authentication.
Answer: Poly consent should be performed any time before upgrading
the device firmware to avoid authentication failures.

3

TECHNICAL ADVISORY - 137008

Question: If a tenant
Administrator performs
consent from the provided
URL prior to upgrading
firmware, will users have
any sign-in issues?

Answer: Users shall not have sign-in issues if tenant administrators
perform acceptance on consent URL & then proceed with device
Firmware upgrade.

Question: Are Lync phone
edition devices (CX Range)
impacted by this change?

Answer: Lync phones are out of support and end of life and will fail to
sign-in due to lack of support for TLS 1.2.

Question: Are the devices
connecting to Skype for
Business Server affected by
this change?

Answer: No, unless authentication is through OAuth to sign-in to the
Skype for Business Server account.

For any questions please contact:
William Marchant
Sr Manager Product Management
William.Marchant@poly.com

© 2019 Plantronics, Inc. All rights reserved. Poly and the propeller design are trademarks of Plantronics, Inc. The
Bluetooth trademark is owned by Bluetooth SIG, Inc. and any use of the mark by Plantronics, Inc. is under license.
All other trademarks are the property of their respective owners.
4
10/2/2019



Source Exif Data:
File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.7
Linearized                      : No
Page Count                      : 4
Language                        : en-US
Tagged PDF                      : Yes
XMP Toolkit                     : 3.1-701
Producer                        : Microsoft® Word for Office 365
Creator                         : Thomas Padakandla
Creator Tool                    : Microsoft® Word for Office 365
Create Date                     : 2019:10:02 02:18:46+05:30
Modify Date                     : 2019:10:02 02:18:46+05:30
Document ID                     : uuid:9C875F71-17EA-43FD-A913-68E5F0D8BCB9
Instance ID                     : uuid:9C875F71-17EA-43FD-A913-68E5F0D8BCB9
Author                          : Thomas Padakandla
EXIF Metadata provided by EXIF.tools

Navigation menu