Home
%3CLINGO-SUB%20id%3D%22lingo-sub-484160%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-484160%22%20slang%3D%22en-US%22%3E%3CP%3ECould%20this%20be%20clarified%20if%20it's%20actually%20for%20Skype%20for%20Business%20Online%20only%20-%20based%20on%20the%20explanation%2C%20assume%20Skype%20for%20Business%20is%20actually%20unaffected%20(i.e.%20the%20on-prem%20one)%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-484254%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-484254%22%20slang%3D%22en-US%22%3E%3CP%20dir%3D%22ltr%22%3EWill%20it%20be%20the%20same%20app%20%2F%20consent%20grant%20for%20all%20phones%2C%20or%20specific%20per%20provider%3F%20Can%20you%20provide%20the%20link%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-484453%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-484453%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25138%22%20target%3D%22_blank%22%3E%40Tom%20Morgan%3C%2FA%3E%26nbsp%3Beach%20phone%20parntner%20has%20to%20create%20thier%20own%20App%20ID%20and%20the%20admin%20has%20to%20grant%20permission%20for%20all.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9288%22%20target%3D%22_blank%22%3E%40Adam%20Fowler%3C%2FA%3E%26nbsp%3Bonly%20if%20you%20conifgured%20oAuth%20for%20onprem%20also.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-485719%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-485719%22%20slang%3D%22en-US%22%3E%3CP%3ESuggestion%3A%26nbsp%3B%20instead%20of%20publishing%20an%20article%20giving%20a%20brief%20synopsis%20of%20something%20that%20will%20be%20%22effective%20immediately%22%20and%20%22if%20you%20don't%20do%20this%20by%20'X'%20date%2C%20logins%20will%20fail%22%2C%20include%20the%20pertinent%20information%20for%20IT%20Professionals%20and%20Service%20Owners%20to%20act%20accordingly.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EWhat%20firmware%20versions%20are%20required%20per%20vendor%3F%3C%2FLI%3E%3CLI%3EAre%20AppIDs%20per%20vendor%2C%20per%20phone%20model%2C%20or%20other%3F%3C%2FLI%3E%3CLI%3EWhat%20S4B%20topologies%20does%20this%20impact%3F%3C%2FLI%3E%3CLI%3EHow%20does%20this%20apply%20to%20ExO%2C%20specifically%20regarding%20Web%20Services%20access.%3C%2FLI%3E%3CLI%3EHow%20are%20the%20AppIDs%20configured%20and%20added%20to%20the%20Office365%20tenant%2FAzure%20AD%3F%3C%2FLI%3E%3CLI%3EHow%20does%20this%20impact%20LPE%20devices%20or%20non%203PIP%20devices%3F%3C%2FLI%3E%3C%2FUL%3E%3CP%3EI%20cannot%20emphasize%20how%20frustrating%20it%20is%20for%20customers%20(and%20partners)%20to%20receive%20messaging%20from%20the%20PG%20like%20this%20-%20which%20causes%20an%20immediate%20knee-jerk%20reaction%20-%20and%20then%20have%20to%20sift%20through%20subsequent%20communications%20for%20pertinent%20details%20on%20implementation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMeasure%20twice%2C%20cut%20once%20-%20you're%20doing%20us%20all%20(including%20yourselves)%20a%20favor.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-487656%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-487656%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Folks%2C%20some%20more%20background%20on%20this%20article%20%3CA%20href%3D%22http%3A%2F%2Fimaucblog.com%2Farchive%2F2019%2F04%2F26%2Fmicrosoft-online-device-registration-with-oauth-2-0-via-3rd-party-azure-application-id%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-503345%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-503345%22%20slang%3D%22en-US%22%3E%3CP%3E...and%20a%20good%20summary%20from%20Tom%20here%3A%3C%2FP%3E%3CP%3E%3CFONT%3E%3CA%20href%3D%22https%3A%2F%2Ftomtalks.blog%2F2019%2F04%2Fall-skype-for-business-ip-phones-must-be-firmware-updated-by-july-1st-2019-to-continue-to-sign-into-office-365%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftomtalks.blog%2F2019%2F04%2Fall-skype-for-business-ip-phones-must-be-firmware-updated-by-july-1st-2019-to-continue-to-sign-into-office-365%2F%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-503442%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-503442%22%20slang%3D%22en-US%22%3E%3CP%3EAudiocodes%20will%20have%20a%20new%20firmware%20available%20shortly%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETom%20Arbuthnot%20has%20done%20good%20post%20here%20explaining%20the%20change%2C%20with%20links%20to%20each%20vendor%20as%20they%20release%20the%20firmware%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftomtalks.blog%2F2019%2F04%2Fall-skype-for-business-ip-phones-must-be-firmware-updated-by-july-1st-2019-to-continue-to-sign-into-office-365%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftomtalks.blog%2F2019%2F04%2Fall-skype-for-business-ip-phones-must-be-firmware-updated-by-july-1st-2019-to-continue-to-sign-into-office-365%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-507868%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-507868%22%20slang%3D%22en-US%22%3EOur%20Polycom%20phones%20firmware%20is%20currently%20managed%20by%20Microsoft%20directly%20(we%20don't%20have%20our%20own%20provision%20server).%20Will%20Microsoft%20be%20releasing%20the%20new%20firmware%20for%20our%20phones%20so%20these%20update%20automatically%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-519604%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-519604%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F331227%22%20target%3D%22_blank%22%3E%40ElectroRich%3C%2FA%3E%20Yes%2C%20we%20will%20post%20the%20Polycom%20firmware%20as%20soon%20as%20it%20is%20available.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-524994%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-524994%22%20slang%3D%22en-US%22%3E%3CP%3EWill%20Microsoft%20push%20the%20release%20out%20to%20Polycom%20phones%20(automatic%20update)%20or%20will%20you%20just%20post%20a%20link%3F%26nbsp%3B%20We%20use%20Microsoft%20as%20the%20provisioning%20server%20and%20they%20normally%20only%20push%20out%20the%20major%20release%20%23%205.7%2C%205.8%2C%205.9.%26nbsp%3B%20My%20understanding%20is%20the%20update%20will%20be%205.9.3.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324128%22%20target%3D%22_blank%22%3E%40Diana_Vank%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3ETo%20provide%20our%20customers%20with%20best-in-class%20security%20across%20our%20services%2C%20Microsoft%20is%20implementing%20the%20use%20of%20%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Fazure%252Factive-directory%252Fdevelop%252Fv2-permissions-and-consent%26amp%3Bdata%3D04%257C01%257Cdivank%2540microsoft.com%257Cd0ccce79697f419b3fd608d6cceaeaec%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C636921706677845927%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C-1%26amp%3Bsdata%3DyyQa6SgUMjZoHV9NROFbWjIio%252FSP1%252Fb0e25X84iYKQs%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20Identity%20Platform%202.0%3C%2FA%3E%20(an%20evolution%20of%20the%20Azure%20Active%20Directory%20identity%20service)%20which%20uses%20the%20OAuth%202.0%20authorization%20protocol.%20OAuth%202.0%20is%20a%20method%20through%20which%20a%20third-party%20app%20can%20access%20web-hosted%20resources%20on%20behalf%20of%20a%20user%2C%20through%20a%20third-party%20application%20ID.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20change%20only%20impacts%20Skype%20for%20Business%20IP%20Phones%20certified%20under%203PIP%20program.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%3CP%3E%3CSTRONG%3EDeployment%20Type%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FTD%3E%3CTD%3E%3CP%3E%3CSTRONG%3EImpact%20Statement%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CP%3ESkype%20for%20Business%20Online%3C%2FP%3E%3C%2FTD%3E%3CTD%3E%3CP%3EAll%20phones%20must%20be%20updated%20by%20July%201st%20and%20tenant%20admins%20must%20have%20approved%20phone%20partners%20App%20ID%20using%20the%20consent%20URL%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CP%3ESkype%20for%20Business%20On-Premises%20Hybrid%20(With%20Modern%20Auth%20Deployed)%3C%2FP%3E%3C%2FTD%3E%3CTD%3E%3CP%3EAll%20phones%20must%20be%20updated%20by%20July%201st%20and%20tenant%20admins%20must%20have%20approved%20phone%20partners%20App%20ID%20using%20the%20consent%20URL%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CP%3ESkype%20for%20Business%20On-Premises%20Hybrid%20(No%20Modern%20Auth)%3C%2FP%3E%3C%2FTD%3E%3CTD%3E%3CP%3ENo%20Impact%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CP%3ESkype%20for%20Business%20On-Premises%20No%20Hybrid%3C%2FP%3E%3C%2FTD%3E%3CTD%3E%3CP%3ENo%20Impact%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20result%20of%20this%20change%2C%20Skype%20for%20Business%20IP%20Phone%20partners%20have%20made%20a%20code%20change%20to%20embed%20the%20partner%20specific%20application%20ID%20in%20their%20firmware.%20The%20customer%20tenant%20admin%20will%20be%20required%20to%20confirm%20consent%20to%20allow%20the%20third-party%20phone%20application%20to%20be%20granted%20the%20necessary%20permissions%20(the%20same%20permissions%20currently%20being%20used%20by%20Skype%20for%20Business%20IP%20Phones).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20216px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F111219i424DCDF6C241157E%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22consent%20permissions.png%22%20title%3D%22consent%20permissions.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESkype%20for%20Business%20IP%20Phone%20partners%20will%20provide%20customers%20with%20a%20partner%20specific%20consent%20URL.%20Customer%20admin%20will%20need%20to%20perform%20a%20one%20time%2C%20tenant%20wide%20(all%20users)%2C%20consent%20per%20IP%20Phone%20partner%20(i.e.%20one%20consent%20URL%20for%20Yealink%2C%20one%20consent%20URL%20for%20Crestron%2C%20etc.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20IP%20Phone%20partners%20will%20post%20additional%20information%20via%20their%20own%20communication%20channels%2C%20including%20the%20firmware%20version%20that%20includes%20the%20necessary%20changes.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20change%20requires%20customers%20to%20perform%20a%202%20step%20process%3A%3C%2FP%3E%3CP%3EStep%201%3A%20Accept%20permissions%20request%20using%20the%20consent%20URL%20(can%20be%20done%20at%20any%20time)%3C%2FP%3E%3CP%3EStep%202%3A%20Upgrade%20all%20impacted%20phones%20to%20the%20firmware%20version%20communicated%20by%20the%20Microsoft%20IP%20Phone%20partners%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20certified%20Skype%20for%20Business%20IP%20phones%20must%20be%20updated%20by%20July%201st%2C%202019.%20Without%20the%20update%2C%20successful%20authentication%20to%20Microsoft%20services%20on%20IP%20Phones%20will%20fail.%20Specifically%2C%20signing%20to%20the%20device%20via%20web%20or%20using%20a%20user%20name%2Fpassword%20on%20the%20phone%20will%20fail.%20Customers%20are%20encouraged%20to%20work%20with%20their%20certified%20Skype%20for%20Business%20IP%20Phone%20provider%20to%20make%20the%20update%20before%20the%20deadline.%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-549087%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-549087%22%20slang%3D%22en-US%22%3EAny%20update%20on%20the%20Polycom%20VVX%20and%20Trio%20firmware%E2%80%99s%3F%20I%20see%20Polycom%20UC%20Software%206.0.0.4796%20already%20available%20on%20their%20website.%20This%20versioning%20seems%20greater%20than%20the%20%E2%80%9C5.9.3%E2%80%9D%20posted%20above.%20Does%20that%20mean%20it%E2%80%99ll%20work%20with%20Microsoft%E2%80%99s%20Modern%20Auth%2F%20OAuth%202.0%20changes%20post-July%201st%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-549622%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-549622%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESome%20more%20updates%20from%20Poly%20(Polycom).%3C%2FP%3E%0A%3CP%3E1.%20We're%20working%20with%20Microsoft%20to%20push%20the%20new%20UCS%20builds%20(via%20Skype%20for%20Business%20Online%20Update)%20that%20incorporate%20the%20new%20App%20ID.%3C%2FP%3E%0A%3CP%3E2.%20We%20have%20an%20official%20announcement%20coming%20hopefully%20by%20the%20end%20of%20this%20week.%20Refer%20to%20%3CA%20href%3D%22http%3A%2F%2Fimaucblog.com%2Farchive%2F2019%2F04%2F26%2Fmicrosoft-online-device-registration-with-oauth-2-0-via-3rd-party-azure-application-id%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Emy%20blog%3C%2FA%3E%20in%20the%20interim%20for%20updates.%3C%2FP%3E%0A%3CP%3E3.%20Initial%20testing%20suggests%20the%20users%20will%20not%20be%20logged%20out%20when%20the%20upgrade%20is%20completed%2C%20provided%20the%20consent%20is%20performed%20prior%20to%20roll-out%20and%20before%20the%20cut-off%20date.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20hope%20this%20helps!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-%20Adam%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-550411%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-550411%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F338325%22%20target%3D%22_blank%22%3E%40phake%3C%2FA%3E%26nbsp%3BDon't%20think%206.0.0%20has%20the%20App%20ID%20change.%20Also%20note%20support%20for%20many%20older%20VVX%20models%20ends%20with%206.0.0%20-%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Fdownloads.polycom.com%2Fvoice%2Fvoip%2Fuc_sw_releases_matrix.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fdownloads.polycom.com%2Fvoice%2Fvoip%2Fuc_sw_releases_matrix.html%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-550434%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-550434%22%20slang%3D%22en-US%22%3E%3CP%3EVersion%20guidance%20below%3C%2FP%3E%0A%3CTABLE%20class%3D%22wp-block-table%20aligncenter%22%20style%3D%22background-attachment%3A%20scroll%3B%20background-clip%3A%20border-box%3B%20background-color%3A%20%23ffffff%3B%20background-image%3A%20none%3B%20background-origin%3A%20padding-box%3B%20background-position-x%3A%200%25%3B%20background-position-y%3A%200%25%3B%20background-repeat%3A%20repeat%3B%20background-size%3A%20auto%3B%20border-collapse%3A%20collapse%3B%20color%3A%20%23333333%3B%20display%3A%20table%3B%20font-family%3A%20Verdana%2CTahoma%2C%26amp%3Bquot%3B%20bitstream%20vera%20sans%26amp%3Bquot%3B%2Carial%2Chelvetica%2Csans-serif%3B%20font-size%3A%2012px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20width%3A%20auto%3B%20word-spacing%3A%200px%3B%20padding%3A%200px%3B%20margin%3A%205px%205px%2010px%205px%3B%20border%3A%202px%20solid%20%23cccccc%3B%22%3E%0A%3CTBODY%20style%3D%22padding%3A%200px%3B%20margin%3A%200px%3B%22%3E%0A%3CTR%20style%3D%22padding%3A%200px%3B%20margin%3A%200px%3B%22%3E%0A%3CTD%20style%3D%22text-align%3A%20left%3B%20vertical-align%3A%20top%3B%20padding%3A%203px%2010px%203px%2010px%3B%20margin%3A%200px%3B%20border%3A%201px%20solid%20%23cccccc%3B%22%3E%3CSTRONG%20style%3D%22padding%3A%200px%3B%20margin%3A%200px%3B%22%3EDevice%20name%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%20style%3D%22text-align%3A%20left%3B%20vertical-align%3A%20top%3B%20padding%3A%203px%2010px%203px%2010px%3B%20margin%3A%200px%3B%20border%3A%201px%20solid%20%23cccccc%3B%22%3E%3CSTRONG%20style%3D%22padding%3A%200px%3B%20margin%3A%200px%3B%22%3ESoftware%20Version%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%20style%3D%22text-align%3A%20left%3B%20vertical-align%3A%20top%3B%20padding%3A%203px%2010px%203px%2010px%3B%20margin%3A%200px%3B%20border%3A%201px%20solid%20%23cccccc%3B%22%3E%3CSTRONG%20style%3D%22padding%3A%200px%3B%20margin%3A%200px%3B%22%3ETimeline%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%20style%3D%22padding%3A%200px%3B%20margin%3A%200px%3B%22%3E%0A%3CTD%20style%3D%22text-align%3A%20left%3B%20vertical-align%3A%20top%3B%20padding%3A%203px%2010px%203px%2010px%3B%20margin%3A%200px%3B%20border%3A%201px%20solid%20%23cccccc%3B%22%3EVVX%20Phones%3C%2FTD%3E%0A%3CTD%20style%3D%22text-align%3A%20left%3B%20vertical-align%3A%20top%3B%20padding%3A%203px%2010px%203px%2010px%3B%20margin%3A%200px%3B%20border%3A%201px%20solid%20%23cccccc%3B%22%3E5.9.3%3C%2FTD%3E%0A%3CTD%20style%3D%22text-align%3A%20left%3B%20vertical-align%3A%20top%3B%20padding%3A%203px%2010px%203px%2010px%3B%20margin%3A%200px%3B%20border%3A%201px%20solid%20%23cccccc%3B%22%3EMid-May%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%20style%3D%22padding%3A%200px%3B%20margin%3A%200px%3B%22%3E%0A%3CTD%20style%3D%22text-align%3A%20left%3B%20vertical-align%3A%20top%3B%20padding%3A%203px%2010px%203px%2010px%3B%20margin%3A%200px%3B%20border%3A%201px%20solid%20%23cccccc%3B%22%3EPoly%20Trio%3C%2FTD%3E%0A%3CTD%20style%3D%22text-align%3A%20left%3B%20vertical-align%3A%20top%3B%20padding%3A%203px%2010px%203px%2010px%3B%20margin%3A%200px%3B%20border%3A%201px%20solid%20%23cccccc%3B%22%3E5.9.0%20Rev%20AB%3C%2FTD%3E%0A%3CTD%20style%3D%22text-align%3A%20left%3B%20vertical-align%3A%20top%3B%20padding%3A%203px%2010px%203px%2010px%3B%20margin%3A%200px%3B%20border%3A%201px%20solid%20%23cccccc%3B%22%3EMid-May%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%20style%3D%22padding%3A%200px%3B%20margin%3A%200px%3B%22%3E%0A%3CTD%20style%3D%22text-align%3A%20left%3B%20vertical-align%3A%20top%3B%20padding%3A%203px%2010px%203px%2010px%3B%20margin%3A%200px%3B%20border%3A%201px%20solid%20%23cccccc%3B%22%3EGroup%20Series%3C%2FTD%3E%0A%3CTD%20style%3D%22text-align%3A%20left%3B%20vertical-align%3A%20top%3B%20padding%3A%203px%2010px%203px%2010px%3B%20margin%3A%200px%3B%20border%3A%201px%20solid%20%23cccccc%3B%22%3E6.2.1.1%3C%2FTD%3E%0A%3CTD%20style%3D%22text-align%3A%20left%3B%20vertical-align%3A%20top%3B%20padding%3A%203px%2010px%203px%2010px%3B%20margin%3A%200px%3B%20border%3A%201px%20solid%20%23cccccc%3B%22%3EMid-June%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-555180%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-555180%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F150806%22%20target%3D%22_blank%22%3E%40Tristan%20Griffiths%3C%2FA%3Eand%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2814%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E%20-%206.0.0.4796%20is%20confusing%20as%20you'd%20think%20it%20would%20logically%20have%20the%20App%20ID%20changes.%20Very%20confusing!%20I'll%20wait%20for%205.9.3.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20currently%20have%20Skype%20on-premise%20(Modern%20Auth)%20enabled%20and%20Exchange%20Online%20(Modern%20Auth%20enabled)%20for%20some%20users%20and%20our%20VVX%20501's%20are%20working.%20EWS%20is%20not%20-%20will%205.9.3%20save%20the%20day%20in%20that%20regard%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-555466%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-555466%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F338325%22%20target%3D%22_blank%22%3E%40phake%3C%2FA%3E%20totally%20understand%20the%20confusion%2C%206.x%20is%20part%20of%20a%20different%20fork%20which%20is%20yet%20to%20be%20certified%20for%20Skype%20for%20Business%20(which%20is%20why%20this%20is%20not%20published%20on%20the%20Skype%20for%20Business%20VVX%20f%2Fw%20page).%206.x%20will%20be%20certified%20in%20the%20future%20though%2C%20stay%20tuned.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERegarding%20the%20issue%20you're%20having%2C%20this%20is%20not%20expected%20and%20should%20work%20with%20the%20existing%20App%20ID.%20Please%20raise%20a%20support%20ticket%20and%20we%20can%20dig%20into%20this%20further.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-556136%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-556136%22%20slang%3D%22en-US%22%3E%3CP%3EOne%20big%20problem%20with%20this%20is%20we%20now%20have%20to%20assess%20Polycom%20as%20a%20sub%20processor%20of%20data%20because%20consenting%20to%20the%20app%20permissions%20gives%20the%20app%20full%20access%20to%20all%20users%20mailboxes%2C%20which%20could%20lead%20to%20data%20breach%20if%20the%20polycom%20service%20and%20app%20is%20breached.%20How%20can%20we%20ensure%20the%20app%20is%20secure%20and%20how%20do%20we%20get%20validation%20the%20app%20will%20not%20explore%2C%20use%20or%20digest%20information%20in%20users%20mailboxes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-556248%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-556248%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F150806%22%20target%3D%22_blank%22%3E%40Tristan%20Griffiths%3C%2FA%3E%26nbsp%3B%20Yeah%2C%20hence%20why%20no%20one%20should%20accept%20this.%20You%20are%20giving%20the%20app%20full%20mailbox%20access%20to%20every%20user.%20Without%20a%20contract%20in%20place%20with%20the%20app%20vendor%20or%20a%20suitable%20privacy%20and%20terms%20of%20use%20policy%2C%20most%20companies%20should%20not%20allow%20this%20access.%20Microsoft%20need%20to%20address%20this.%20It%20would%20be%20fine%20if%20the%20app%20only%20needed%20access%20to%20read%20and%20write%20calendar%20events%20but%20allowing%20full%20mailbox%20access%20gives%20way%20to%20significant%20risk%20of%20data%20breach.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-556158%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-556158%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F339629%22%20target%3D%22_blank%22%3E%40Graham705%3C%2FA%3E%26nbsp%3Bideally%20Polycom%2FCrestron%2FAudioCodes%2FYealink%20would%20link%20to%20a%20terms%20and%20conditions%2Fprivacy%20document.%20Looks%20like%20they%20have%20opted%20to%20not%20provide%20one.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20366px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F112855i2E2008BE06F78919%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.PNG%22%20title%3D%22Capture.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-558754%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-558754%22%20slang%3D%22en-US%22%3E%3CP%3EAh%2C%20thanks%20so%20much%20for%20the%20clarification%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2814%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E.%20!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERE%3A%20current%20VVX%20501's%20and%20our%20recent%20Skype%20for%20Business%20on-premise%20enabling%20of%20HMA%2C%20I'm%20digging%20into%20the%20VVX%20501%20logs%20to%20find%20out%20why%20it's%20not%20allowing%20the%20EWS%20%2B%20OAuth%20magic%2C%20and%20will%20put%20in%20a%20Polycom%20ticket.%20Thanks.%20Any%20links%20or%20obvious%20config%20I'm%20making%20will%20greatly%20help%20300%2B%20people!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-565068%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-565068%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%20official%20tech%20advisory%20published%20by%20Poly%20%3CA%20href%3D%22https%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fdam%2Fpolycom-support%2Fproducts%2Fvoice%2Fpolycom-uc%2Fother-documents%2Fen%2F2019%2Fmicrosoft-online-registration-azure-application-id.pdf%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-570648%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-570648%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20to%20confirm%20the%20firmware%20update%20is%20no%20longer%20required%20by%20July%201%2C%202019%20but%20rather%20January%2015th.%20Is%20that%20correct%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482876%22%20slang%3D%22en-US%22%3EOAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482876%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20provide%20our%20customers%20with%20best-in-class%20security%20across%20our%20services%2C%20Microsoft%20is%20implementing%20the%20use%20of%20%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Fazure%252Factive-directory%252Fdevelop%252Fv2-permissions-and-consent%26amp%3Bdata%3D04%257C01%257Cdivank%2540microsoft.com%257Cd0ccce79697f419b3fd608d6cceaeaec%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C636921706677845927%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C-1%26amp%3Bsdata%3DyyQa6SgUMjZoHV9NROFbWjIio%252FSP1%252Fb0e25X84iYKQs%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20Identity%20Platform%202.0%3C%2FA%3E%20(an%20evolution%20of%20the%20Azure%20Active%20Directory%20identity%20service)%20which%20uses%20the%20OAuth%202.0%20authorization%20protocol.%20OAuth%202.0%20is%20a%20method%20through%20which%20a%20third-party%20app%20can%20access%20web-hosted%20resources%20on%20behalf%20of%20a%20user%2C%20through%20a%20third-party%20application%20ID.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20change%20only%20impacts%20Skype%20for%20Business%20IP%20Phones%20certified%20under%203PIP%20program.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CTABLE%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%3E%3CP%3E%3CSTRONG%3EDeployment%20Type%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%3E%3CP%3E%3CSTRONG%3EImpact%20Statement%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%3CP%3ESkype%20for%20Business%20Online%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%3E%3CP%3EAll%20phones%20must%20be%20updated%20and%20tenant%20admins%20must%20have%20approved%20phone%20partners%20App%20ID%20using%20the%20consent%20URL%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%3CP%3ESkype%20for%20Business%20On-Premises%20Hybrid%20(With%20Modern%20Auth%20Deployed)%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%3E%3CP%3EAll%20phones%20must%20be%20updated%20and%20tenant%20admins%20must%20have%20approved%20phone%20partners%20App%20ID%20using%20the%20consent%20URL%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%3CP%3ESkype%20for%20Business%20On-Premises%20Hybrid%20(No%20Modern%20Auth)%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%3E%3CP%3ENo%20Impact%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3E%3CP%3ESkype%20for%20Business%20On-Premises%20No%20Hybrid%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%3E%3CP%3ENo%20Impact%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20result%20of%20this%20change%2C%20Skype%20for%20Business%20IP%20Phone%20partners%20have%20made%20a%20code%20change%20to%20embed%20the%20partner%20specific%20application%20ID%20in%20their%20firmware.%20The%20customer%20tenant%20admin%20will%20be%20required%20to%20confirm%20consent%20to%20allow%20the%20third-party%20phone%20application%20to%20be%20granted%20the%20necessary%20permissions%20(the%20same%20permissions%20currently%20being%20used%20by%20Skype%20for%20Business%20IP%20Phones).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20216px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F111219i424DCDF6C241157E%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22consent%20permissions.png%22%20title%3D%22consent%20permissions.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESkype%20for%20Business%20IP%20Phone%20partners%20will%20provide%20customers%20with%20a%20partner%20specific%20consent%20URL.%20Customer%20admin%20will%20need%20to%20perform%20a%20one%20time%2C%20tenant%20wide%20(all%20users)%2C%20consent%20per%20IP%20Phone%20partner%20(i.e.%20one%20consent%20URL%20for%20Yealink%2C%20one%20consent%20URL%20for%20Crestron%2C%20etc.)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMicrosoft%20IP%20Phone%20partners%20will%20post%20additional%20information%20via%20their%20own%20communication%20channels%2C%20including%20the%20firmware%20version%20that%20includes%20the%20necessary%20changes.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20change%20requires%20customers%20to%20perform%20a%202%20step%20process%3A%3C%2FP%3E%0A%3CP%3EStep%201%3A%20Accept%20permissions%20request%20using%20the%20consent%20URL%20(can%20be%20done%20at%20any%20time)%3C%2FP%3E%0A%3CP%3EStep%202%3A%20Upgrade%20all%20impacted%20phones%20to%20the%20firmware%20version%20communicated%20by%20the%20Microsoft%20IP%20Phone%20partners%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAll%20certified%20Skype%20for%20Business%20IP%20phones%20must%20be%20updated%20by%20%3CSTRONG%3EJanuary%2015%2C%202020%3C%2FSTRONG%3E.%20Without%20the%20update%2C%20successful%20authentication%20to%20Microsoft%20services%20on%20IP%20Phones%20will%20fail.%20Specifically%2C%20signing%20to%20the%20device%20via%20web%20or%20using%20a%20user%20name%2Fpassword%20on%20the%20phone%20will%20fail.%20Customers%20are%20encouraged%20to%20work%20with%20their%20certified%20Skype%20for%20Business%20IP%20Phone%20provider%20to%20make%20the%20update%20before%20the%20deadline.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-482876%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDevices%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EGeneral%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EProduct%20Updates%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-570215%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-570215%22%20slang%3D%22en-US%22%3E%3CP%3EPlease%20note%20deadline%20change%20in%20the%20original%20post%2C%20now%20%3CSTRONG%3EJanuary%2015%2C%202020%3C%2FSTRONG%3E.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-570679%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-570679%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25258%22%20target%3D%22_blank%22%3E%40Larry%20Thomas%3C%2FA%3E%20correct!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-571269%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-571269%22%20slang%3D%22en-US%22%3E%3CP%3EFolks%20-%20minor%20update%20to%20a%20statement%20I%20made%20above%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%200px%3B%22%3EHi%20All%2C%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%200px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%200px%3B%22%3ESome%20more%20updates%20from%20Poly%20(Polycom).%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%200px%3B%22%3E1.%20We're%20working%20with%20Microsoft%20to%20push%20the%20new%20UCS%20builds%20(via%20Skype%20for%20Business%20Online%20Update)%20that%20incorporate%20the%20new%20App%20ID.%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%200px%3B%22%3E2.%20We%20have%20an%20official%20announcement%20coming%20hopefully%20by%20the%20end%20of%20this%20week.%20Refer%20to%20%3CA%20style%3D%22background-color%3A%20transparent%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%23146cac%3B%20text-decoration%3A%20underline%3B%22%20href%3D%22http%3A%2F%2Fimaucblog.com%2Farchive%2F2019%2F04%2F26%2Fmicrosoft-online-device-registration-with-oauth-2-0-via-3rd-party-azure-application-id%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Emy%20blog%3C%2FA%3E%20in%20the%20interim%20for%20updates.%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%200px%3B%22%3E3.%20Initial%20testing%20suggests%20the%20users%20will%20not%20be%20logged%20out%20when%20the%20upgrade%20is%20completed%2C%20provided%20the%20consent%20is%20performed%20prior%20to%20roll-out%20and%20before%20the%20cut-off%20date.%20%3CSTRONG%3E%26lt%3B-%20the%20latter%20is%20only%20true%20for%20users%20that%20signed-in%20locally%20on%20the%20device.%20For%20users%20that%20signed-in%20with%20Web%20Sign-in%20they%20will%20be%20logged%20out%2C%20this%20is%20due%20to%20the%20fact%20that%20their%20credentials%20are%20not%20cached%20on%20the%20device%20and%20so%20tokens%20cannot%20be%20renewed%20without%20intervention%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%200px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%200px%3B%22%3EI%20hope%20this%20helps!%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%200px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20margin%3A%200px%3B%22%3E-%20Adam%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-571301%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-571301%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20this%20shift%20into%20using%20an%20AppID%20seems%20to%20be%20inline%20with%20OAuth%20authentication%20in%20general%2C%20does%20this%20mean%20that%20devices%20should%20not%20have%20to%20re-authenticate%20when%20a%20user%20password%20has%20expired%2Fchanged%20as%20it'll%20be%20using%20a%20token%20created%20specifically%20for%20that%20User%2FAppID%20at%20time%20of%20sign%20in%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20noticed%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F339629%22%20target%3D%22_blank%22%3E%40Graham705%3C%2FA%3E%20comment%20on%20mailbox%20access.%26nbsp%3B%20I%20suspect%20this%20is%20required%20for%20the%20voicemail%20access%20due%20to%20how%20the%20devices%20access%2Fmanage%20the%20voicemail.%20Is%20that%20correct%3F%26nbsp%3B%20My%20understanding%20is%20that%20while%20you%20are%20granting%20the%20AppID%20access%20to%20mailboxes%20as%20the%20signed%20in%20user%2C%20it%20would%20mean%20that%20the%20device%20would%20only%20have%20access%20to%20the%20mailbox%20that%20user%20has%20access%20to%2C%20not%20ever%20mailbox%20on%20the%20platform%20(unless%20that%20user%20has%20that%20level%20of%20access).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-544733%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-544733%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324128%22%20target%3D%22_blank%22%3E%40Diana_Vank%3C%2FA%3E%26nbsp%3BTrying%20to%20settle%20a%20discussion%20with%20some%20of%20our%20team.%20The%20discussion%20is%20whether%20basic%20authentication%20to%20Office%20365%20will%20be%20unaffected%20by%20Microsoft's%20OAuth%2FAppID%20change.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20a%20Poly(com)%20VVX%2FTrio%20UC%20device%20when%20authenticating%20to%20Office%20365%3A%3C%2FP%3E%3CP%3E1.%20Modern%20Auth%20is%20used%20by%20the%20%22Web%20Sign-In%22%20feature%20and%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fsphone%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fsphone%3C%2FA%3E%20application.%3C%2FP%3E%3CP%3E2.%20Basic%20Auth%20is%20used%20when%20entering%20credentials%20via%20the%20web%20browser%2Fserver%20interface%20option%20Settings-%26gt%3BSkype%20for%20Business%20Sign-in.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20a%20firmware%20update%20to%205.9.3%2B%2C%20we're%20expecting%20devices%20using%20method%20%231%20will%20be%20forcibly%26nbsp%3Bsigned-out%26nbsp%3Band%26nbsp%3Busers%20will%20be%20required%20to%26nbsp%3Bre-authenticate%26nbsp%3B(with%20administrator%20approval%20of%20new%20appID)%26nbsp%3B---%20CONFIRMED%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSkype-for-Business-Blog%2FOAuth-2-0-and-third-party-application-ID%2Fbc-p%2F571269%2Fhighlight%2Ftrue%23M2122%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSkype-for-Business-Blog%2FOAuth-2-0-and-third-party-application-ID%2Fbc-p%2F571269%2Fhighlight%2Ftrue%23M2122%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe're%20expecting%20nothing%20will%20change%20with%20method%20%232%20(phones%20happily%20keep%20basic%20auth-ing).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20this%20sound%20correct%3F%20If%20not%2C%20will%20edit%2Fremove%20this%20post%20so%20that%20false%20info%20isn't%20out%20there%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-574000%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-574000%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324128%22%20target%3D%22_blank%22%3E%40Diana_Vank%3C%2FA%3E%26nbsp%3BWhich%20post%20does%20mention%20about%20date%20moved%20to%20Janurary%2015th%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-575106%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-575106%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F343012%22%20target%3D%22_blank%22%3E%40msabat%3C%2FA%3EThe%20main%20post%20at%20the%20top%20has%20had%20the%20date%20changed%2C%20and%20now%20marked%20in%20bold.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-544359%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-544359%22%20slang%3D%22en-US%22%3E%3CP%3EOfficial%20posts%20which%20includes%20the%20partner%20specific%20consent%20URL%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.crestron.com%2Fapp%2Fanswers%2Fanswer_view%2Fa_id%2F1000349%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ECrestron%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fonline.audiocodes.com%2Foauth-2-0-appid%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAudioCodes%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.yealink.com%2Fnews_187.html%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EYealink%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fdam%2Fpolycom-support%2Fproducts%2Fvoice%2Fpolycom-uc%2Fother-documents%2Fen%2F2019%2Fmicrosoft-online-registration-azure-application-id.pdf%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EPoly%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-582081%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-582081%22%20slang%3D%22en-US%22%3E%3CP%3E%22Specifically%2C%20signing%20to%20the%20device%20via%20web%20or%20using%20a%20%3CSTRONG%3Euser%20name%2Fpassword%3C%2FSTRONG%3E%20on%20the%20phone%20will%20fail.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%E2%80%99d%20be%20curious%20to%20learn%20whether%20that%20goes%20for%20PIN%20authentication%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-614343%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-614343%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F343012%22%20target%3D%22_blank%22%3E%40msabat%3C%2FA%3EExtension%2BPIN%20authentication%20is%20unaffected.%20Only%20authentications%20using%20ADAL%2FModern%20Auth%2FOAuth%20are%20affected.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-681520%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-681520%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F150806%22%20target%3D%22_blank%22%3E%40Tristan%20Griffiths%3C%2FA%3E%26nbsp%3Bso%20also%20anywhere%20EWS%20is%20needed%20and%20Oauth%20is%20used%20with%20EWS.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-682055%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-682055%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F270764%22%20target%3D%22_blank%22%3E%40oradcliffe%3C%2FA%3E%26nbsp%3Byes%2C%20if%20you're%20signing%20on%20to%20the%20device%20using%20web%20sign-in%20(code%20%2B%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fsphone%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fsphone%3C%2FA%3E).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E(we'll%20ignore%20that%20we%20can%20override%20Exchange%20authentication%20via%20provisioning%20file)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-683100%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-683100%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F150806%22%20target%3D%22_blank%22%3E%40Tristan%20Griffiths%3C%2FA%3E%3CSPAN%3E%26nbsp%3Boauth%20is%20used%20a%20bunch%20of%20other%20places%2C%20not%20just%20web%20sign%20in.%26nbsp%3B%20This%20change%20I%20believe%20will%20affect%20anything%20where%20the%20phone%20needs%20oauth%20authorization.%26nbsp%3B%20We've%20got%20web%20sign%20in%2C%20EWS%2C%20even%20username%2Fpass%20sign%20in%20to%20an%20on%20prem%20SfB%20environment%20if%20that%20environment%20uses%20Azure%20STS%20for%20auth.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-701644%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-701644%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F270764%22%20target%3D%22_blank%22%3E%40oradcliffe%3C%2FA%3E%3C%2FP%3E%3CP%3Eusername%2Fpass%2BSfBO%2BEXO%20-%20basic%20auth%3C%2FP%3E%3CP%3Eweb%20sign-in%2BSfBO%2BEXO%20-%20modern%20auth%2Foauth%3C%2FP%3E%3CP%3Eusername%2Fpass%2BSfB%2BEX%20on-prem%20-%20negotiate%20(ntlm)%20or%20basic%3C%2FP%3E%3CP%3Eweb%20sign-in%2BSFB%2BEX%20on-prem%20-%20modern%20auth%2Foauth%20(think%20this%20is%20now%20supported)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat's%20my%20understanding%20anyway.%20There%20would%20be%20other%20more%20complex%20arrangements%20with%20ADFS%20and%20hybrid%20environments%20but%20that%20hurts%20my%20head%20to%20think%20about.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-701647%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-701647%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F150806%22%20target%3D%22_blank%22%3E%40Tristan%20Griffiths%3C%2FA%3E%26nbsp%3Bthat%20is%20about%20right%20yeah%2C%20but%20don't%20forget%20you%20can%20enable%20OAuth%20in%20ExO%20and%20SfBO%2C%20as%20well%20as%20SfB%20on%20prem.%26nbsp%3B%20You%20can%20also%20disable%20basic%20auth%20in%20your%20O365%20tenant%2C%20and%20then%20you'd%20be%20either%20using%20OAuth%20or%20just%20failing%20to%20sign%20in%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-701660%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-701660%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F270764%22%20target%3D%22_blank%22%3E%40oradcliffe%3C%2FA%3E%20Yup%2C%20with%20basic%20auth%20disabled%20in%20SfBO%20or%20EXO%2C%20only%20web%20sign-in%20(%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fsphone%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fsphone%3C%2FA%3E)%20will%20work.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-701675%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-701675%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F150806%22%20target%3D%22_blank%22%3E%40Tristan%20Griffiths%3C%2FA%3E%26nbsp%3Bthat's%20not%20entirely%20true.%26nbsp%3B%20I%20can%20set%20up%2C%20for%20one%20example%2C%20Skype%20on%20prem%20to%20use%20Oauth%20with%20Azure%20as%20the%20token%20signer.%26nbsp%3B%20I%20could%20then%20disable%20basic%20auth%20in%20my%20tenant%20and%20still%20use%20username%2Fpass%20with%20my%20on%20prem%20deployment%2C%20and%20that%20would%20use%20OAuth%20via%20Azure.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-701819%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-701819%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F270764%22%20target%3D%22_blank%22%3E%40oradcliffe%3C%2FA%3E%26nbsp%3BWould%20your%20scenario%20include%20ADFS%3F%20Just%20trying%20to%20think%20what%20mechanisms%20that%20would%20permit%20getting%20that%20OAuth%20token%20from%20the%20on-prem%2Fazure%20environment%20given%20a%20username%2Fpass.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E(my%20comment%20should%20have%20been%20%22SfBO%20%3CSTRONG%3Eand%3C%2FSTRONG%3E%20EXO%22%20to%20be%20more%20accurate)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-734685%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-734685%22%20slang%3D%22en-US%22%3E%3CP%3EAnybody%20notice%20devices%20such%20as%20the%20Polycom%20Centro%20or%20any%20of%20the%20Polycom%20Group%20Series%20devices%20running%206.2%20suddenly%20stop%20working%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3E2019-07-02%2015%3A43%3A32.305%20WARNING%20%20logcat%3A%20hd%5B0%5D%3A%20System.err(2405)%3A%20com.microsoft.aad.adal4j.AuthenticationException%3A%20%7B%22error_description%22%3A%22AADSTS65001%3A%20The%20user%20or%20administrator%20has%20not%20consented%20to%20use%20the%20application%20with%20ID%20'a850aaae-d5a5-4e82-877c-ce54ff916282'%20named%20'Polycom%20-%20Skype%20for%20Business%20Certified%20Phone'.%20Send%20an%20interactive%20authorization%20request%20for%20this%20user%20and%20resource.%5Cr%5CnTrace%20ID%3A%20d9f50d5c-688f-4fb4-a9f9-26fe73281b00%5Cr%5CnCorrelation%20ID%3A%20976c1c4d-d9fa-4780-a398-6623f173b46a%5Cr%5CnTimestamp%3A%202019-07-02%2015%3A43%3A33Z%22%2C%22error%22%3A%22invalid_grant%22%7D%3C%2FPRE%3E%3CP%3EThis%20seems%20to%20have%20broken%20inline%20with%20the%20original%20date%2C%20not%20their%20new%20date.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-735004%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-735004%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F342739%22%20target%3D%22_blank%22%3E%40jangliss%3C%2FA%3E%26nbsp%3Bthe%20last%20upgrade%20for%20Group%20Series%20requires%20that%20the%20organization%20performs%20consent%20prior%20to%20upgrading.%20It%20seems%20this%20has%20not%20happened.%20Refer%20to%20notes%20%3CA%20href%3D%22https%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fsupport%2Fnorth-america%2Fusa%2Fen%2Fsupport%2Fvideo%2Fgroup-series%2Fgroup500.html%3Fproduct_type%3D%252Fcontent%252Fsupport%252Fnorth-america%252Fusa%252Fen%252Fsupport%252Fvideo%26amp%3Bcategory%3D%252Fcontent%252Fsupport%252Fnorth-america%252Fusa%252Fen%252Fsupport%252Fvideo%252Fgroup-series%252Fgroup500.html%26amp%3B%253Acq_csrf_token%3Dundefined%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere.%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ENotes%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%20class%3D%22product-notes%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EMicrosoft%20has%20announced%20changes%20related%20to%20the%20Microsoft%20Online%20device%20registration%20requirement.%20These%20changes%20affect%20RealPresence%20Group%20Series%20systems%20registered%20for%20Skype%20for%20Business%20accounts.%20Before%20upgrading%20your%20Microsoft%20environment%20RealPresence%20Group%20Series%20system%20to%206.2.1.1%2C%20see%20the%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fdam%2Fpolycom-support%2Fproducts%2Fvoice%2Fpolycom-uc%2Fother-documents%2Fen%2F2019%2Fmicrosoft-online-registration-azure-application-id.pdf%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ETechnical%20Advisory%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Efor%20specific%20changes%20and%20actions%20required.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E-%20Adam%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-759259%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-759259%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F218272%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E%3C%2FP%3E%3CP%3EIs%20there%20any%20harm%20to%20consenting%20to%20the%20Polycom%20App%20ID%20right%20now%20in%20our%20tenant%2C%20and%20will%20consenting%20affect%20current%20VVXs%20and%20Lync%20phone%20edition%20devices%3F%26nbsp%3B%20I%20assume%20the%20consent%20needs%20to%20happen%20before%20the%20devices%20are%20auto%20upgraded%20by%20MS%20to%20the%20supported%20firmware%3F%26nbsp%3B%20Is%20this%20still%20the%20correct%20timeline%20for%20the%20firmware%20releases%20that%20will%20be%20pushed%20down%20to%20the%20devices%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EVVX%20-%205.9.4%20(Q4%20Calendar%20Year%202019%3C%2FP%3E%3CP%3ETrio%20-%205.9.1AA%20(August%202019)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20still%20unclear%20on%20whether%20people%20will%20be%20logged%20out%20of%20their%20phones%20after%20the%20consent%20and%20firmware%20updates.%26nbsp%3B%20We%20have%20a%20mix%20where%20some%20are%20logged%20in%20via%20web%20sign-in%20and%20others%20with%20BTOE%20integration.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20help%20and%20advice!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-759810%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-759810%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20is%20no%20harm%20performing%20consent%20against%20your%20tenant%2C%20existing%20devices%20will%20not%20be%20impacted.%20Testing%20suggests%20that%20the%20upgrade%20process%20will%20not%20sign%20out%20the%20device%20unless%20a%20subsequent%20downgrade%20is%20performed.%20Dates%20will%20be%20more%20detailed%20once%20we%20have%20a%20release%20vehicle%20we%20have%20an%20HMA%20issue%20we're%20tracking.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-768008%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-768008%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2814%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20the%20help!%26nbsp%3B%20Is%20there%20a%20recommended%20route%20to%20the%20firmware%20updates%3F%26nbsp%3B%20Currently%20we%20have%20devices%20updating%20automatically%2C%20but%20normally%2C%20is%20the%20process%20where%20Polycom%20will%20release%20the%20update%20and%20can%20be%20downloaded%2Finstalled%20manually%20on%20the%20phone%20to%20test%3F%26nbsp%3B%20I%20assume%20that%20Microsoft%20will%20not%20automatically%20approve%20that%20firmware%20version%20and%20push%20it%20down%20to%20devices%20right%20when%20Polycom%20releases%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-768039%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-768039%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F359014%22%20target%3D%22_blank%22%3E%40myry1%3C%2FA%3E%26nbsp%3Brefer%20to%20support.polycom.com%20for%20manual%20updates%2C%20Microsoft%20typically%20pushes%20certified%20s%2Fw%20releases%20only%20and%20after%20Poly%20releases%20them%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-768146%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-768146%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F218272%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3EThanks%2C%20is%20there%20a%20typical%20time%20between%20Poly's%20release%20and%20Microsoft's%20certified%20push%3F%26nbsp%3B%20Best%20practice%20-%20automatic%20updates%20on%20phone%20or%20manual%20updates%3F%26nbsp%3B%20I%20haven't%20seen%20any%20issues%20with%20firmware%20updates%20in%20the%20past%2C%20but%20not%20sure%20if%20testing%20is%20more%20appropriate%20in%20this%20situation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-783486%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-783486%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F359014%22%20target%3D%22_blank%22%3E%40myry1%3C%2FA%3E%26nbsp%3BOnce%20the%20required%20update%20is%20available%20then%20it%20will%20likely%20be%20posted%20to%20the%20device%20update%20service%20quicker%20than%20in%20the%20past%20given%20the%20potential%20impact.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThat%20being%20said%2C%20Microsoft%20has%20ceased%20their%20device%20qualification%20program%20for%20Skype%20for%20Business%20%3CSTRONG%3EOnline%3C%2FSTRONG%3E%2C%20so%20any%20new%20firmware%20updates%20beyond%20this%20change%20will%20be%20certified%2C%20and%20likely%20the%20Device%20Update%20services%20online%20will%20continue%20to%20push%20the%20current%20versions%20until%20SfBO%20retirement%20in%20July%202021.%26nbsp%3B%20(An%20exception%20would%20be%20if%20one%20of%20those%20releases%20was%20found%20to%20have%20a%20critical%20security%20flaw%20in%20the%20future%20and%20would%20need%20to%20be%20replaced%20with%20a%20patched%20version%2C%20but%20even%20then%20it's%20quite%20possible%20that%20Microsoft%20just%20decides%20to%20disable%20the%20update%20service%20in%20general.%26nbsp%3B%20In%20short%2C%20it's%20always%20recommended%20to%20manage%20device%20updates%20in%20a%20different%20manner%20and%20disable%20the%20in-band%20update%20process%20as%20Adam%20mentioned%20earlier.)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENewer%20releases%20may%20still%20be%20able%20to%20qualify%20for%20Skype%20for%20Business%20%3CSTRONG%3EServer%3C%2FSTRONG%3E%2C%20but%20Microsoft%20does%20not%20manage%20those%20updates%2C%20the%20customer%20does%20in%20their%20own%20deployment.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870492%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870492%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324128%22%20target%3D%22_blank%22%3E%40Diana_Vank%3C%2FA%3E%20Microsoft%20is%20indicating%20that%20all%20phones%20must%20be%20updated%20by%20January%2015%2C%202020%20to%20support%20OAuth.%20The%20release%20notes%20for%20Polycom%20UC%20software%205.9.4%20indicates%20support%20for%20OAuth%2C%20but%20it%20seems%20that%20version%20is%20not%20on%20the%20approved%20list%20for%20Skype%20For%20Business%20Online%20implementations.%20Customers%20in%20Skype%20for%20Business%20deployments%20should%20only%20use%20software%20releases%20that%20have%20been%20qualified%20by%20Microsoft%20or%20the%20maintenance%20releases%20built%20on%20a%20qualified%20release.%20The%20current%20version%20which%20is%20qualified%20by%20Microsoft%20is%205.9.0.9373.%20When%20will%20Microsoft%20qualify%20the%20release%20version%205.9.4%3F%20both%20the%20below%20URL's%20from%20Poly%20and%20also%20Microsoft%20suggests%20us%20to%20stay%20in%205.9.0.%20Please%20advice!%20%3CA%20href%3D%22https%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fsupport%2Fnorth-america%2Fusa%2Fen%2Fsupport%2Fvoice%2Fpolycom-uc%2Fpolycom-uc-software-for-lync.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fsupport%2Fnorth-america%2Fusa%2Fen%2Fsupport%2Fvoice%2Fpolycom-uc%2Fpolycom-uc-software-for-lync.html%3C%2FA%3E%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fcertification%2Fdevices-ip-phones%23conference-phones%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fcertification%2Fdevices-ip-phones%23conference-phones%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870505%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870505%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70306%22%20target%3D%22_blank%22%3E%40Vinay%20N%20V%3C%2FA%3E%20all%20Poly%205.9.x%20builds%20are%20currently%20certified%20for%20SFB.%20The%20listing%20on%20docs.microsoft.com%20implies%20that%20any%20version%20greater%20than%20the%20certified%20build%20listed%20is%20also%20certified.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870838%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870838%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70306%22%20target%3D%22_blank%22%3E%40Vinay%20N%20V%3C%2FA%3Eas%20indicated%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F324128%22%20target%3D%22_blank%22%3E%40Diana_Vank%3C%2FA%3E%20and%20the%20release%20notes%20you%20can%20use%20any%20maintenance%20release%20built%20on%20top%20of%20the%205.9.0%20version%2C%20e.g.%205.9.4.%20Poly%20is%20working%20to%20reword%20the%20notes%20on%20the%20%3CA%20href%3D%22https%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fsupport%2Fnorth-america%2Fusa%2Fen%2Fsupport%2Fvoice%2Fpolycom-uc%2Fpolycom-uc-software-for-lync.html%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Elink%3C%2FA%3E%20provided%20and%20make%20it%20more%20clear.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-877526%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-877526%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Folks%20-%20Group%20Series%2C%20Trio%20and%20VVX%20builds%20are%20now%20released%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CTABLE%20class%3D%22wp-block-table%20aligncenter%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%3E%3CSTRONG%3EDevice%20name%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3E%3CSTRONG%3ESoftware%20Version%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3E%3CSTRONG%3ETimeline%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3CTD%3E%3CSTRONG%3EDownload%3C%2FSTRONG%3E%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3EVVX%20Phones%3C%2FTD%3E%0A%3CTD%3E5.9.4.3247%3C%2FTD%3E%0A%3CTD%3ELate-Sept%3C%2FTD%3E%0A%3CTD%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fsupport%2Fnorth-america%2Fusa%2Fen%2Fsupport%2Fvoice%2Fpolycom-uc%2Fpolycom-uc-software-release.html%235.9.4%22%20target%3D%22_blank%22%20rel%3D%22noreferrer%20noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20aria-label%3D%22%20(opens%20in%20a%20new%20tab)%22%3EURL%3C%2FA%3E%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3EPoly%20Trio%3C%2FTD%3E%0A%3CTD%3E5.9.1.10419%3C%2FTD%3E%0A%3CTD%3ELate-Sept%3C%2FTD%3E%0A%3CTD%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fsupport%2Fnorth-america%2Fusa%2Fen%2Fsupport%2Fvoice%2Fpolycom-trio%2Fpolycom-trio-8800.html%22%20target%3D%22_blank%22%20rel%3D%22noreferrer%20noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20aria-label%3D%22URL%20(opens%20in%20a%20new%20tab)%22%3EURL%3C%2FA%3E%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%3EGroup%20Series%3C%2FTD%3E%0A%3CTD%3E6.2.1.1%3C%2FTD%3E%0A%3CTD%3EMid-June%3C%2FTD%3E%0A%3CTD%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fsupport%2FNorth_America%2FUSA%2Fen%2Fsupport%2Fvideo%2Fgroup-series.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EURL%3C%2FA%3E%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-886675%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-886675%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Adam%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20confirm%20the%20links%20you%20provided%20take%20us%20to%20the%20latest%20Polycom%20UC%20software%20Release%2C%20however%20when%20you%20go%20to%20the%20latest%20UC%20Software%20for%20Skype%20for%20Business%20Deployments%20the%20latest%20is%26nbsp%3B%3CSTRONG%3E5.9.0.9373.%20%3C%2FSTRONG%3E%3CSPAN%3EThe%20version%20you%20are%20referring%20to%20is%20just%20on%20the%20Poly%20latest%20side.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20please%20confirm%20that%20%3CSTRONG%3E5.9.4.3247%3C%2FSTRONG%3E%20is%20supported%20by%20MS%20and%20indeed%20is%20the%20resolution%20for%20OAuth%202.0%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3ELarry%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-886973%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-886973%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32653%22%20target%3D%22_blank%22%3E%40Larry%20Thomas%3C%2FA%3E%26nbsp%3Bwe're%20in%20the%20process%20of%20updating%20this%20page%2C%20whereby%205.9.4.3247%20will%20be%20supported%20for%20Microsoft%20customers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-887124%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-887124%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20the%20clarification%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELarry%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-893542%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-893542%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20I%20am%20currently%20testing%20the%20new%20firmware%20in%20our%20organization.%20We%20use%20MFA%20for%20all%20our%20users.%20%3CFONT%3EI%20have%20%3C%2FFONT%3E%3CFONT%3Eaccepted%20the%20consent%20URL%20for%20online%20device%20registration%2C%20and%20it%20shows%20as%20such%20in%20going%20into%20the%20Azure%20portal.%20%3C%2FFONT%3EI%20am%20having%20the%20following%20issue%20and%20just%20wanted%20some%20clarification.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20our%20users%20use%20the%20BToE%20software%2C%20and%20login%20into%20their%20phone%20using%20the%20user%20credential%20method.%20Since%20going%20to%205.9.4.3247%20all%20users%20get%20the%20following%20message%20on%20their%20VVX%20---%20%22Not%20able%20to%20connect%20to%20Calendar%20data%26nbsp%3B%20%26amp%3B%20other%20exchange%20services%20%E2%80%A6%E2%80%A6%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20only%20way%20I%20am%20able%20to%20resolve%20this%20error%20is%20to%20have%20the%20user%20sign%20in%20using%20the%20web%20sign-in%20method.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGoing%20forward%2C%20am%20I%20correct%20in%20that%20this%20new%20firmware%20does%20not%20support%20the%20user%20credential%20method%20and%20all%20will%20have%20to%20use%20web%20sign-in%3F%20I%20was%20of%20the%20understanding%20that%20accepting%20the%20online%20device%20registration%20for%20our%20tenant%20this%20would%20not%20be%20the%20case.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3ELarry%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-893649%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-893649%22%20slang%3D%22en-US%22%3EHi%2C%20I%20have%20just%20tried%20to%20upgrade%20our%20VVX%20phones%20to%205.9.4.3247.%20However%2C%20once%20they%20have%20been%20upgraded%20they%20reboot%20and%20revert%20back%20to%205.9.0.9373.%20I%20remember%20this%20happening%20in%20the%20past%20when%20I%20tried%20to%20upgrade%20the%20firmware%20and%20I%20raised%20this%20with%20Microsoft%20and%20they%20said%20that%20the%20Skype%20Online%20server%20reverts%20the%20phones%20back%20as%20that%20is%20the%20latest%20supported%20version.%20It%20seems%20Microsoft%20are%20yet%20to%20approve%20this%20software%20update.%20When%20will%20this%20be%20done%20so%20that%20I%20can%20update%20to%20the%20latest%20version%20without%20it%20being%20downgraded%20automatically%3F%20I%20don't%20want%20to%20go%20through%20the%20steps%20of%20setting%20up%20my%20own%20provisioning%20server%20etc.%20Thanks%2C%20Richard%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-893716%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-893716%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32653%22%20target%3D%22_blank%22%3E%40Larry%20Thomas%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFirst%20ensure%20you're%20using%20the%20latest%20version%20of%20our%20BToE%20software%20-%204.1.0.0%20is%20posted%20%3CA%20href%3D%22https%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fsupport%2Fnorth-america%2Fusa%2Fen%2Fsupport%2Fvoice%2Fbusiness-media-phones%2Fvvx501.html%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESecond%2C%20there's%20a%20known%20issue%20in%20relation%20to%20calendaring%2C%20for%20folks%20using%20Exchange%202013%20on-premises%20with%20HMA%20(refer%20to%20release%20notes)%2C%20we're%20working%20with%20Microsoft%20on%20this.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThird%2C%20we%20updated%20the%20consent%20URL%20some%20time%20back%20as%20some%20Exchange%20scopes%20needed%20to%20be%20added%20per%20Microsoft's%20recommendation.%20If%20you%20performed%20the%20consent%20some%20time%20ago%20this%20may%20be%20the%20issue.%20The%20most%20recent%20consent%20URL%20is%20%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2Fcommon%2Fadminconsent%3Fclient_id%3Da850aaae-d5a5-4e82-877c-ce54ff916282%26amp%3Bredirect_uri%3Dhttps%3A%2F%2Fdialin.plcm.vc%2Fteams%2Fpostconsent.html%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELet%20me%20know%20how%20you%20get%20on!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-%20Adam%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-893907%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-893907%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Adam%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAppreciate%20you%20getting%20back%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20answer%20your%20questions%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tried%20the%20newest%20BToE%20(we%20also%20have%20a%20few%20people%20who%20don't%20use%20the%20BToE)%20and%20have%20logged%20into%20the%20phone%20from%20the%20Web%20UI%20and%20they%20have%20same%20issue%20-%20so%20can't%20be%20a%20BToE%20issue%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20100%25%20online%20for%20Exchange%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20retried%20the%20consent%20yesterday%20and%20then%20again%20this%20morning%20from%20your%20comments.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20all%20the%20above%20--%20same%20issue%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20further%20thoughts%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-894154%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-894154%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32653%22%20target%3D%22_blank%22%3E%40Larry%20Thomas%3C%2FA%3E%26nbsp%3BI've%20DM'd%20you%2C%20let's%20take%20offline%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-896467%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-896467%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20also%20preparing%20for%20this%20change%20within%20our%20company.%26nbsp%3B%20We%20performed%20the%20consent%20(it's%20visible%20in%20the%20Azure%20Enterprise%20applications)%20and%20after%20that%20we've%20installed%20the%20required%20software%20upgrades%20on%20some%20test%20Poly%20devices%20(Poly%20VVX301%2C%20VVX601%20and%20Trio8800).%3C%2FP%3E%3CP%3EWe%20can't%20find%20back%20the%20authentication%20in%20Azure%20or%20find%20a%20way%20in%20confirmation%20that%20these%20devices%20are%20fine%20now%20for%20the%20change%20that%20will%20take%20place%20on%20January%2015th.%3C%2FP%3E%3CP%3EWhere%20can%20we%20get%20confirmation%3F%3C%2FP%3E%3CP%3ESecondly%2C%20is%20the%20target%20date%20still%20January%2015th%202020%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%20for%20any%20feedback.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-897383%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-897383%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F255408%22%20target%3D%22_blank%22%3E%40JeffB%3C%2FA%3E%20%2C%26nbsp%3B%3CFONT%3EI%20can't%20find%20the%20application%20that%20you%20have%20highlighted%20on%20your%20screenshot.%26nbsp%3B%20After%20we%20performed%20the%20consent%20the%20only%20Polycom%20applications%20I%20can%20see%20in%20our%20tenant%20are%20as%20follows%3A%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F135676iABADC2815473EBE0%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Tenant.png%22%20title%3D%22Tenant.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3E%26nbsp%3B%3C%2FFONT%3E%3CFONT%3EDid%20we%20miss%20something%3F%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3EThanks%20in%20advance%20for%20your%20feedback!%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-897699%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-897699%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F253285%22%20target%3D%22_blank%22%3E%40Hmerckx%3C%2FA%3E%26nbsp%3Bthat's%20the%20one.%20You%20can%20search%20for%20our%20App%20ID%20also%2C%20which%20is%3A%26nbsp%3Ba850aaae-d5a5-4e82-877c-ce54ff916282%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-897705%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-897705%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F218272%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20can%20we%20get%20confirmation%20that%20our%20Polycom%20devices%20are%20fine%20now%20for%20the%20change%20that%20will%20take%20place%20on%20January%2015th%3F%3C%2FP%3E%3CP%3EWhere%20can%20we%20see%20confirmation%20that%20the%20accounts%2FPolycom%20devices%20authenticate%20the%20right%20wat%3F%3C%2FP%3E%3CP%3ESecondly%2C%20is%20the%20target%20date%20still%20January%2015th%202020%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%20for%20your%20feedback!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-897863%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-897863%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-mentions-hints-description%22%3E%3CSPAN%20class%3D%22lia-mentions-symbol%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F253285%22%20target%3D%22_blank%22%3E%40Hmerckx%3C%2FA%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3EThere%20are%20two%20requirements%3A%3C%2FDIV%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EPerform%20the%20consent.%20Once%20completed%20this%20will%20show%20up%20within%20your%20Office%20365%20tenant%20(within%20Azure%20AD%20applications)%20-%20you%20showed%20this%20in%20your%20earlier%20thread%3C%2FLI%3E%0A%3CLI%3EEnsure%20you%20Poly%20endpoints%20are%20updated%20with%20the%20right%20f%2Fw%20level%20that%20supported%20the%203rd%20party%20app%20ID.%20Firmware%20versions%20are%20published%20%3CA%20href%3D%22http%3A%2F%2Fimaucblog.com%2Farchive%2F2019%2F04%2F26%2Fmicrosoft-online-device-registration-with-oauth-2-0-via-3rd-party-azure-application-id%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20date%20has%20not%20changed%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-897896%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-897896%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F218272%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E%26nbsp%3BThanks%2C%20I%20got%20that.%3C%2FP%3E%3CP%3EBut%20is%20there%20a%20way%20to%20check%20upfront%20Jan%2015th%202020%20of%20it%20will%20work%3F%20We%20know%20the%20consent%2Fapplication%20is%20ok%2C%20we%20also%20know%20the%20%26nbsp%3Bsoftware%20is%20ok%20...%20but%20can%20we%20test%20it%20upfront%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-897901%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-897901%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F253285%22%20target%3D%22_blank%22%3E%40Hmerckx%3C%2FA%3E%26nbsp%3Byes%2C%20as%20soon%20as%20you%20upgrade%20to%20the%20builds%20I%20shared%20previously%20the%20new%203rd%20part%20app%20will%20be%20used.%20The%20Jan%202020%20date%20is%20just%20when%20the%201st%20party%20Microsoft%20app%20gets%20turned%20off.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-897312%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-897312%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20find%20the%20application%20in%20your%20tenant%20by%20going%20to%20the%20Enterprise%20Applications%20section%20of%20the%20Azure%20AD%20admin%20center%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fportal.azure.com%2F%23blade%2FMicrosoft_AAD_IAM%2FStartboardApplicationsMenuBlade%2FAllApps%2FmenuId%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fportal.azure.com%2F%23blade%2FMicrosoft_AAD_IAM%2FStartboardApplicationsMenuBlade%2FAllApps%2FmenuId%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F135692iD33C2FDB1DC5F287%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Clipboard01.jpg%22%20title%3D%22Clipboard01.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E(Edit%3A%20oops%2C%20I%20had%20the%20wrong%20app%20highlighted%20before.%26nbsp%3B%20This%20is%20the%20correct%20app%20for%20phone%20authentication%20among%20the%20various%20Poly%20apps.)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-898088%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-898088%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F218272%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E%26nbsp%3B%20Is%20there%20a%20way%20to%20check%20in%20Azure%20if%20the%20account%2Fdevice%20uses%20that%203th%20party%20app%3F%20I%E2%80%99m%20just%20looking%20for%20that%20black%20on%20white%20prove.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-898328%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-898328%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F253285%22%20target%3D%22_blank%22%3E%40Hmerckx%3C%2FA%3E%26nbsp%3Bnot%20that%20I'm%20aware%20of%2C%20you%20could%20review%20device%20logs.%20But%20as%20soon%20as%20you%20upgrade%20to%20the%203rd%20party%20app%20device%20f%2Fw%20this%20is%20enforced.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-898461%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-898461%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F218272%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E%26nbsp%3B%20do%20you%20have%20a%20screenshot%20example%20of%20what%20we%20should%20see%20in%20de%20device%20logs%20in%20order%20to%20be%20sure%20things%20are%20working%20the%20way%20they%20should%3F%26nbsp%3B%20We%20just%20wan't%20to%20avoid%20a%20big%20surprise%20on%20January%2015th%202020.%3C%2FP%3E%3CP%3EAnother%20question%20about%20these%20software%20upgrades.%26nbsp%3B%20The%20table%20you%20have%20with%20the%20versions%2C%20...%20any%20newer%20versions%20than%20the%20one%20in%20your%20table%2C%20will%20they%20also%20do%20what's%20needed%3F%26nbsp%3B%20Or%20can%20it%20be%2C%20for%20now%2C%20only%20be%20that%20specific%20versions%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-898503%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-898503%22%20slang%3D%22en-US%22%3E%3CP%3EOn%20another%20note%20we%20are%20facing%20some%20other%20issue%20as%20well%20when%20we%20are%20performing%20the%20software%20upgrade%20on%20the%20Polycom%20VVX601.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Upgrade%20from%20version%205.9.0.9373%20to%20version%205.9.4.3247%20worked%20fine%20...%20but%20after%20a%20while%20the%20Polycom%20device%20showed%20a%20message%20that%20there%20was%20a%20device%20update%20available.%26nbsp%3B%20When%20I%20checked%20the%20details%20of%20that%20device%20update%20I%20can%20see%20that%20it%20wants%20to%20downgrade%20again%20to%20the%20older%20version%205.9.0.9373.%26nbsp%3B%20If%20I%20ignore%20that%20message%20to%20update%20it%20will%20automatically%20reboot%20and%20downgrade%20after%20a%20few%20minutes.%3C%2FP%3E%3CP%3ESee%20below%20screenshots%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F135772i561B0DC87AD98B89%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22DeviceUpdateAvailable.jpg%22%20title%3D%22DeviceUpdateAvailable.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F135773iF4535457CD7FC0ED%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22UpdateAvailableVersion.jpg%22%20title%3D%22UpdateAvailableVersion.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3BWhy%20is%20it%20doing%20this%3F%26nbsp%3B%20And%20how%20can%20we%20prevent%20this%20from%20happening%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-899058%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-899058%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F253285%22%20target%3D%22_blank%22%3E%40Hmerckx%3C%2FA%3E%20What%20Adam%20is%20saying%20is%20that%20there%20is%20no%20need%20to%20'validate%20anything'%20as%20the%20phone%20will%20not%20successfully%20authenticate%20if%20the%20app%20was%20not%20approved.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3EThis%20is%20how%20it%20works%3A%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3EStarting%20with%20the%26nbsp%3B%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23f8f8f8%3B%20color%3A%20%23333333%3B%20font-family%3A%20'SegoeUI'%2C'Lato'%2C'Helvetica%20Neue'%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E5.9.4.3247%3C%2FSPAN%3E%20release%20the%20VVX%20can%20%3CEM%3Eonly%3C%2FEM%3E%20authenticate%20to%20Skype%20for%20Business%20Online%20using%20the%20app%20model.%26nbsp%3B%20Sign-in%20will%20simply%20not%20work%20unless%20the%20Poly%20app%20has%20been%20manually%20approved%20by%20an%20administrator%20for%20the%20tenant%20where%20the%20user%20account%20is%20homed%20that%20is%20attempting%20to%20sign-in%20to%20the%20phone.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOnce%20the%20app%20has%20been%20approved%20in%20the%20tenant%20(which%20you%20have%20done)%20then%20all%20VVX%20phones%20running%205.9.4.3247%20will%20successfully%20sign-in.%26nbsp%3B%20They%20cannot%20use%20the%20older%20user%20authetnication%20method%20regardless%20of%20the%20app's%20status%2C%20so%20there%20is%20nothing%20to%20confirm%20in%20any%20logs.%26nbsp%3B%20If%20a%20VVX%20running%205.9.4.3247%20or%20newer%20succesfully%20signs-in%2C%20then%20it's%20using%20the%20new%20app%20model%20and%20will%20continue%20to%20work%20that%20way%20from%20that%20release%20though%20all%20future%20releases.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3ERegarding%20the%20firmware%20version%20issue%2C%20it%20is%20recommended%20to%20disable%20Device%20Updates%20in%20your%20Office%20365%20tenant%20for%20this%20reason%3A%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CA%20href%3D%22http%3A%2F%2Fblog.schertz.name%2F2016%2F07%2Fdevice-updates-with-skype-for-business-online%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fblog.schertz.name%2F2016%2F07%2Fdevice-updates-with-skype-for-business-online%2F%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMicrosoft%20typically%20does%20not%20update%20the%20published%20version%20for%20most%20minor%20updates%2C%20and%20when%20they%20are%20it%20historically%20takes%20a%20long%20time.%26nbsp%3B%20I%20expect%20this%20version%20will%20be%20posted%20to%20the%20updates%20services%20at%20eventually%20though%20as%20it'll%20be%20required%20before%20long.%26nbsp%3B%20But%20for%20now%20you'll%20want%20to%20disable%20the%20updates%20to%20prevent%20the%20phones%20from%20rolling%20back%20automatically.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-899110%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-899110%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F311774%22%20target%3D%22_blank%22%3E%40Jeff_Schertz%3C%2FA%3E%20Surely%20Microsoft%20need%20to%20publish%20the%205.9.4.3247%20firmware%20sooner%20rather%20than%20later%20if%20they%20want%20to%20push%20forward%20with%20these%20changes%20otherwise%20there%20will%20be%20a%20lot%20of%20tenants%20that%20get%20stuck%20when%20they%20switch%20off%20the%20older%20authorization%20versions.%20I%20would%20prefer%20to%20keep%20the%20Skype%20online%20updates%20active%20so%20I%20know%20our%20phones%20are%20running%20the%20latest%20certified%20builds%20without%20having%20to%20go%20into%20each%20phone%20individually%20to%20update%20it%20or%20set%20up%20our%20own%20provisioning%20server.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-899303%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-899303%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F14769%22%20target%3D%22_blank%22%3E%40Jeff%20Schertz%3C%2FA%3E%3A%20I%20fully%20agree%20with%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F331227%22%20target%3D%22_blank%22%3E%40ElectroRich%3C%2FA%3E%20I%20would%20like%20to%20leave%20the%20update%20process%20enabled.%20How%20can%20we%20push%20Microsoft%20ahead%20with%20providing%20the%20last%20version%20on%20their%20servers%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20an%20absolute%20need%2C%20especially%20if%20the%20date%20of%20Jan%2015%2C%202020%20stays..%20(%3CFONT%3EUpdate%20Polycom%20devices%2C%20required%20for%20'Microsoft%20Online%20Device%20Registration%20updates%2C%20MC178633)%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-899393%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-899393%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F14769%22%20target%3D%22_blank%22%3E%40Jeff%20Schertz%3C%2FA%3E%20and%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2814%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E%3A%20This%20might%20be%20a%20fairly%20dumb%20question%2C%20but%20we've%20started%20updating%20our%20Polycom%20Trio%208800's%20to%20use%20the%20Microsoft%20Teams%20base%20profile.%20Will%20we%20need%20to%20update%20to%20the%205.9.1.10419%20firmware%20version%20before%20Jan%202020%3F%20We're%20currently%20at%205.9.0.11398.%20Bonus%20question%3A%20Updating%20the%20Polycom%20Trio%20firmware%20is%20fairly%20easy%2C%20but%20how%20do%20we%20update%20the%20Microsoft%20Teams%20software%20version%3F%20We're%20noticing%20some%20Trio's%20going%20%22Offline%22%20in%20the%20TAC%20-%26gt%3B%20Devices%20section%20and%20rebooting%20them%20seems%20to%20set%20them%20to%20%22Online%22.%20I%20was%20thinking%20some%20regular%20MS%20Teams%20software%20pushes%20might%20help%20the%20devices%20be%20more%20healthy%3F%20Thanks!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-899803%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-899803%22%20slang%3D%22en-US%22%3E%3CP%3EAgreed%20that%20Microsoft%20needs%20to%20push%20that%20firmware%20update%20to%20the%20device%20update%20services%20as%20soon%20as%20possible.%26nbsp%3B%20I'm%20just%20stating%20that%20until%20that%20happens%20the%20only%20way%20to%20prevent%20rollback%20is%20by%20disabling%20updates.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20app%20is%20only%20applicable%20to%20registration%20to%20Skype%20for%20Business%2C%20not%20for%20Teams.%26nbsp%3B%20Using%20Teams%20profile%20on%20the%20Trio%20is%20native%20and%20not%20impacted%20by%20any%20of%20this.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20Teams%20application%20should%20automatically%20update%20itself%20when%20a%20newer%20version%20is%20available.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-899816%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-899816%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F311774%22%20target%3D%22_blank%22%3E%40Jeff_Schertz%3C%2FA%3E%26nbsp%3B%20awesome%2C%20this%20is%20the%20info%20I%20was%20looking%20for!%20Thanks%20for%20taking%20the%20time.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-899833%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-899833%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F338325%22%20target%3D%22_blank%22%3E%40phake%3C%2FA%3E%26nbsp%3Bregarding%20your%20bonus%20question%2C%20we've%20working%20with%20Microsoft%20on%20this.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-899841%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-899841%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F218272%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E%26nbsp%3B%20love%20it%2C%20thanks.%26nbsp%3B%3Afolded_hands%3A%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-915644%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-915644%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F218272%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F311774%22%20target%3D%22_blank%22%3E%40Jeff_Schertz%3C%2FA%3E%26nbsp%3Bwe're%20testing%20out%20firmware%26nbsp%3B%3CSPAN%3E5.9.4.3247%20and%20ran%20into%20some%20issues%20with%20EWS%20(Calendar%2C%20Contacts%2C%20etc)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsing%3A%26nbsp%3B%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Foutlook.office365.com%2FEWS%2FExchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foutlook.office365.com%2FEWS%2FExchange.asmx%3C%2FA%3E%20for%20EWS%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CDIV%3E%3CDIV%20class%3D%22copy-paste-block%22%3EVVX%20501%2C%205.9.2.3446%20firmware%2C%20User%20Skype%20onprem%2C%20EXO%20homed%20%3D%20Success%26nbsp%3B%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22copy-paste-block%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22copy-paste-block%22%3E%3CSPAN%3EVVX%20501%2C%20%3C%2FSPAN%3E%3CSPAN%3E5.9.4.3247%20firmware%2C%20User%20Skype%20onprem%2C%20EXO%20homed%20%3D%20Failure%3C%2FSPAN%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22copy-paste-block%22%3E%3CSPAN%3E%3CBR%20%2F%3EVVX%20501%2C%205.9.4.3247%20firmware%2C%20User%20Skype%20Online%20(Teams%20only)%2C%20EXO%20homed%20%3D%20Failure%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EAny%20insight%3F%20Have%20you%20guys%20run%20into%20this%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-915725%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-915725%22%20slang%3D%22en-US%22%3E%3CP%3EWe're%20running%20into%20this%20in%20another%20office%20as%20well.%20Confirmed%20errors%20in%20another%20network%20environment.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20714px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F137653iDA850FF270E5F42F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222019-10-15_10-01-12.jpg%22%20title%3D%222019-10-15_10-01-12.jpg%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20739px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F137654i6CF76F0E7A5953B0%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222019-10-15_10-01-34.jpg%22%20title%3D%222019-10-15_10-01-34.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-915787%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-915787%22%20slang%3D%22en-US%22%3E%3CP%3ELooks%20like%20there's%20a%206.0.0.4839%20and%20a%206.1.0.6189%20but%20do%20we%20now%20if%20it%20has%20the%203rd%20party%20application%20ID%20baked%20in%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20220px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F137662i4BB1D2292F5A543B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222019-10-15_10-20-05.jpg%22%20title%3D%222019-10-15_10-20-05.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-915930%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-915930%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F338325%22%20target%3D%22_blank%22%3E%40phake%3C%2FA%3E%26nbsp%3Bonly%26nbsp%3B%3CSPAN%3E5.9.4.3247%20has%20the%20new%20app%20ID%20baked%20in%20and%20is%20the%20latest%20recommended%20Microsoft%20firmware%20load.%20Please%20stay%20away%20from%206.x%20these%20are%20not%20Microsoft%20sanctioned%20releases.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EPlease%20re-perform%20the%20consent%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2Fcommon%2Fadminconsent%3Fclient_id%3Da850aaae-d5a5-4e82-877c-ce54ff916282%26amp%3Bredirect_uri%3Dhttps%3A%2F%2Fdialin.plcm.vc%2Fteams%2Fpostconsent.html%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-915978%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-915978%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2814%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E-%20HA!%20That%20did%20it.%20Sigh%2C%20sorry.%20We%20must%20have%20jumped%20at%20the%20previous%20deep%20link%20URL%20months%20ago.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWorks%20now.%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%3CSPAN%3EEWS%20Information%3C%2FSPAN%3E%3C%2FTD%3E%3CTD%3E%3CSPAN%20class%3D%22updateFromLyncStatusInfo%22%3EEWS%20deployed%3C%2FSPAN%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CSPAN%3EEmail%3C%2FSPAN%3E%3C%2FTD%3E%3CTD%3E%3CSPAN%20class%3D%22updateFromLyncStatusInfo%22%3Ebanff_room_booking%40ehs.com%3C%2FSPAN%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CSPAN%3EConfigured%20Exchange%20URL%3C%2FSPAN%3E%3C%2FTD%3E%3CTD%3E%3CSPAN%20class%3D%22updateFromLyncStatusInfo%22%3E%3CA%20href%3D%22https%3A%2F%2Foutlook.office365.com%2FEWS%2FExchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foutlook.office365.com%2FEWS%2FExchange.asmx%3C%2FA%3E%3C%2FSPAN%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CSPAN%3EEWS%20Internal%20URL%3C%2FSPAN%3E%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CSPAN%3EEWS%20External%20URL%3C%2FSPAN%3E%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CSPAN%3EExchange%20Calendar%3C%2FSPAN%3E%3C%2FTD%3E%3CTD%3E%3CSPAN%20class%3D%22updateFromLyncStatusInfo%22%3ESynchronized%3C%2FSPAN%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CSPAN%3EExchange%20Call%20logs%3C%2FSPAN%3E%3C%2FTD%3E%3CTD%3E%26nbsp%3B%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CSPAN%3EExchange%20Voicemail%3C%2FSPAN%3E%3C%2FTD%3E%3CTD%3E%3CSPAN%20class%3D%22updateFromLyncStatusInfo%22%3ESynchronized%3C%2FSPAN%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CSPAN%3EExchange%20Outlook%20Contacts%3C%2FSPAN%3E%3C%2FTD%3E%3CTD%3E%3CSPAN%20class%3D%22updateFromLyncStatusInfo%22%3ESynchronized%3C%2FSPAN%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CSPAN%3EServer%20Missed%20Call%20Status%3C%2FSPAN%3E%3C%2FTD%3E%3CTD%3E%3CSPAN%20class%3D%22updateFromLyncStatusInfo%22%3ENot%20Available%3C%2FSPAN%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-915982%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-915982%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F338325%22%20target%3D%22_blank%22%3E%40phake%3C%2FA%3E%26nbsp%3Bwhen%20we%20originally%20published%20the%20consent%20URL%20we%20(Poly%20and%20Microsoft)%20noticed%20some%20Exchange-related%20permission%20issues.%20So%20glad%20this%20fixed%20it.%20If%20anyone%20else%20here%20perform%20consent%20some%20time%20back%2C%20please%20also%20follow%20suit.%20Also%20(and%20as%20always)%2C%20Poly's%20latest%20Microsoft%20releases%20are%20published%20on%20%3CA%20href%3D%22https%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fsupport%2Fnorth-america%2Fusa%2Fen%2Fsupport%2Fvoice%2Fpolycom-uc%2Fpolycom-uc-software-for-lync.html%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ethis%20page%3C%2FA%3E%20-%20bookmark%20it%20now!%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fhtml%2Fimages%2Femoticons%2Fsmile_40x40.gif%22%20alt%3D%22%3Asmile%3A%22%20title%3D%22%3Asmile%3A%22%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-915986%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-915986%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F218272%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E%26nbsp%3BThanks!%20You%20saved%20us%20some%20heartache.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-915990%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-915990%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F218272%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E%26nbsp%3B%2C%20...%20starting%20from%20when%20(date)%20the%20consent%20is%20the%20good%20one%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-916001%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-916001%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F253285%22%20target%3D%22_blank%22%3E%40Hmerckx%3C%2FA%3E%26nbsp%3BI%20believe%20the%20updated%20consent%20URL%20was%20published%20in%20mid-June.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-918768%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-918768%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F218272%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E%26nbsp%3B...%20is%20the%20Group%20Series%20500%20software%20version%3CSPAN%3E%26nbsp%3B6.2.2-580140%20complient%20for%20the%20new%20app%20ID%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-918789%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-918789%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F253285%22%20target%3D%22_blank%22%3E%40Hmerckx%3C%2FA%3E%26nbsp%3BGroup%20Series%20version%26nbsp%3B%3CSPAN%3E6.2.1.1%20and%20higher%20introduces%20support%20for%203rd%20party%20app%20ID.%20So%20yes%2C%20confirmed.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-964205%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-964205%22%20slang%3D%22en-US%22%3E%3CP%3EI%20see%20Poly%20has%20put%20a%20new%20version%20of%20firmware%20for%20SFB%20deployments%20--%26nbsp%3B%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fsupport%2Fnorth-america%2Fusa%2Fen%2Fsupport%2Fvoice%2Fpolycom-uc%2Fpolycom-uc-software-release.html%235.9.5%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ELatest%20Maintenance%20Release%20UCS%205.9.5.0614%3C%2FA%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20testing%20neither%20Web%20Sign%20In%20or%20User%20Credential%20method%20works.%20continuously%20tries%20authenticating%20and%20fails%20a%20fetching%20user%20certificate.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F151816i1F0AD27B88BD6B6D%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-964494%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-964494%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32653%22%20target%3D%22_blank%22%3E%40Larry%20Thomas%3C%2FA%3E%26nbsp%3BI'll%20bring%20this%20to%20the%20attention%20of%20engineering%20team.%20Please%20do%20however%20continue%20to%20use%20official%20support%20channels!%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-966818%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-966818%22%20slang%3D%22en-US%22%3E%3CP%3EWill%20do%20thanks%20Adam.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20someone%20please%20confirm%20that%20if%20using%20MFA%20the%20only%20method%20which%20is%20supported%20is%20the%20Web%20Sign%20In%20method%20as%20is%20from%20the%20latest%20on%20MS%20web%20site%3F%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20749px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F152079i893520FF04560684%2Fimage-dimensions%2F749x413%3Fv%3D1.0%22%20width%3D%22749%22%20height%3D%22413%22%20alt%3D%22clipboard_image_1.png%22%20title%3D%22clipboard_image_1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-968692%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-968692%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32653%22%20target%3D%22_blank%22%3E%40Larry%20Thomas%3C%2FA%3E%26nbsp%3B(and%20others)%20please%20refrain%20from%20using%20this%20newer%20build%2C%20it's%20not%20been%20approved%20for%20use%20within%20Skype%20for%20Business%20Online.%20Microsoft%20are%20in%20the%20process%20of%20adding%20this%20version%20to%20their%20CVC%20database.%20We're%20investigating%20why%20this%20build%20was%20published%20early%20to%20our%20Skype%20for%20Business%20download%20page.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-968727%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-968727%22%20slang%3D%22en-US%22%3E%3CP%3EHello%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20experiencing%20the%20same%20as%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32653%22%20target%3D%22_blank%22%3E%40Larry%20Thomas%3C%2FA%3E%3CSPAN%3E%26nbsp%3Bin%20regards%20to%20MFA.%20With%20new%20firmware%205.9.4.3247%20we%20can%20no%20longer%20connect%20using%20the%20user%20credential%20method%20(BToE).%20Web%20Sign%20is%20the%20only%20method%20that%20works.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWe%20have%20performed%20the%20consent%20and%20it%20does%20show%20in%20our%20Enterprise%20Applications%20in%20Azure%20as%20%3CSTRONG%3EPolycom%20-%20Skype%20for%20Business%20Certified%20Phone%3C%2FSTRONG%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAre%20all%20users%20now%20required%20to%20sign%20in%20with%20the%20web%20sign%20in%20method%3F%20User%20credential%20no%20longer%20supported%3F%20Going%20to%20be%20a%20bit%20of%20a%20headache%20if%20we%20have%20to%20get%20all%20our%20users%20to%20change%20the%20login%20method%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-968796%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-968796%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F437360%22%20target%3D%22_blank%22%3E%40O365Admin1799%3C%2FA%3E%26nbsp%3B%26nbsp%3BUser%20sign-in%20is%20supported%20also%2C%20I%20suspect%20there's%20something%20else%20in%20play%20here.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-969548%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-969548%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20to%20know%2C%20thanks%20for%20answering%20as%20that%20is%20what%20I%20thought.%3C%2FP%3E%3CP%3EReason%20I%20asked%20is%20I%20did%20open%20a%20ticket%20(SR%23%201-14239375988)%20up%20with%20Polycom.%20The%20support%20specialist%20said%20he%20raised%20to%20the%20T3%20VOIP%20department%20and%20he%20has%20confirmed%20that%20MFA%20is%20%3CU%3ENOT%3C%2FU%3E%26nbsp%3Bsupported%20with%20user%20credentials%20and%20that%20I%20have%20to%20use%20web%20sign%20in.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20you%20can%20see%20my%20confusion%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-978805%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-978805%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F437360%22%20target%3D%22_blank%22%3E%40O365Admin1799%3C%2FA%3E.%20Have%20just%20received%20a%20definitive%20response%20that%20the%20only%20method%20of%20sign%20in%20that%20is%20supported%20for%20MFA%20enabled%20accounts%20is%20the%20web-sign%20in%20method.%20User%20credentials%20or%20BToE%20is%26nbsp%3B%3CU%3E%3CSTRONG%3ENOT%3C%2FSTRONG%3E%3C%2FU%3E%26nbsp%3Bsupported%20nor%20does%20it%20work.%20I%20Hope%20this%20saves%20you%20and%20any%20others%20the%20grief%20I%20went%20through%20in%20getting%20this%20answer.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-978911%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-978911%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20what%20happens%20when%20you%20have%20users%20hosted%20on%20prem%2C%20but%20still%20use%20Modern%20Auth%2FMFA%3F%26nbsp%3B%20Polycom%20phones%20just%20cease%20to%20work%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-980458%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-980458%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20understanding%20would%20be%20if%20you%20are%20on%20premise%20only%20you%20do%20not%20have%20worry%20about%20having%20to%20update%20your%20firmware%20for%20the%20Oauth%202.0%20as%20you%20are%20would%20be%20unaffected%20it%20is%20SFB%20O365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20644px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F154740i8388CF6608688ACF%2Fimage-dimensions%2F644x203%3Fv%3D1.0%22%20width%3D%22644%22%20height%3D%22203%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-981518%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-981518%22%20slang%3D%22en-US%22%3E%3CP%3ENo%2C%20you%20would%20still%20need%20to%20update%20your%20firmware%20and%20accept%20the%20Poly%20phone%20agreement.%26nbsp%3B%20For%20MA%20to%20work%20with%20Skype%20on%20prem%2C%20it%20sends%20your%20request%20to%20Azure%20STS.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSkype-for-Business-Blog%2FHybrid-Modern-Authentication-for-Skype-for-Business%2Fba-p%2F134751%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSkype-for-Business-Blog%2FHybrid-Modern-Authentication-for-Skype-for-Business%2Fba-p%2F134751%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20you%20can%20use%20MFA%2C%203rd%20party%20IdP%2C%20etc%20with%20Skype%20on-prem.%26nbsp%3B%20The%20issue%20here%20is%20that%2C%20if%20you%20are%20doing%20this%2C%20and%20MFA%20is%20only%20supported%20with%20Poly%20phones%20using%20web%20sign-in%2C%20you're%20kind%20of%20stuck%20because%20you%20can't%20use%20web%20sign-in%20with%20an%20on-prem%20deployment.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-981759%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-981759%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F270764%22%20target%3D%22_blank%22%3E%40oradcliffe%3C%2FA%3E%26nbsp%3B%20you%20can%20actually%20use%20Web%20Sign-In%20with%20SfB%20onprem%2C%20please%20check%20%3CA%20href%3D%22https%3A%2F%2Fdocuments.polycom.com%2Fbundle%2Fucs-sfb-dg-5-9-0%2Fpage%2Fc-ucs-sfb-web-sign-in-for-skype-for-business-online.html%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocuments.polycom.com%2Fbundle%2Fucs-sfb-dg-5-9-0%2Fpage%2Fc-ucs-sfb-web-sign-in-for-skype-for-business-online.html%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22note__title%22%3ENote%3A%3C%2FSPAN%3E%20Web%20Sign%20In%20for%20Skype%20for%20Business%20server%20supports%20only%20when%20the%20Hybrid%20Modern%20Authentication%20(HMA)%20environment%20is%20enabled.%20To%20use%20the%20capability%20of%20HMA%20with%20Skype%20for%20Business%20On-Premise%20AAD%20should%20be%20federated%20with%20Azure%20AD.%20For%20more%20information%20to%20configure%20HMA%20in%20your%20environment%2C%20refer%20to%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSkype-for-Business-Blog%2FHybrid-Modern-Authentication-for-Skype-for-Business%2Fba-p%2F134751%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3EHybrid%20Modern%20Authentication%20for%20Skype%20for%20Business%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-981814%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-981814%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F57075%22%20target%3D%22_blank%22%3E%40Leonardo%20Mezzanotti%3C%2FA%3E%26nbsp%3B-%20thank%20you%2C%20that%20slipped%20my%20mind.%26nbsp%3B%20Makes%20sense%20actually.%26nbsp%3B%20But%20that%20means%20no%20third%20party%20IdP%3F%26nbsp%3B%20For%20example%2C%20I%20couldn't%20have%20Skype%20on%20prem%20with%20Okta%20doing%20the%20auth%20right%3F%26nbsp%3B%20So%20SfB%20on%20prem%20-%26gt%3B%20Azure%20STS%20-federatedwith-%26gt%3B%20Okta%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-985662%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-985662%22%20slang%3D%22en-US%22%3E%3CP%3EI%20do%20not%20see%20an%20issue%20by%20using%203rd%20party%20IdPs%20with%20Web%20Sign-In%2C%20it%20should%20work%20and%20VVX%20should%20receive%20the%20tokens%20but%20I'll%20leave%20for%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F218272%22%20target%3D%22_blank%22%3E%40Adam%20Jacobs%3C%2FA%3E%20for%20confirmation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-985701%22%20slang%3D%22en-US%22%3ERe%3A%20OAuth%202.0%20and%20third-party%20application%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-985701%22%20slang%3D%22en-US%22%3E%3CP%3EI%20agree%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F24046%22%20target%3D%22_blank%22%3E%40Leonardo%20Mezzanotti%3C%2FA%3E%26nbsp%3Bthis%20should%20work%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

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).

 

consent permissions.png

 

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 January 15, 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.

106 Comments

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)?

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

@Tom Morgan each phone parntner has to create thier own App ID and the admin has to grant permission for all.

 

@Adam Fowler only if you conifgured oAuth for onprem also.

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.

Hi Folks, some more background on this article here

 

Senior Member

Audiocodes will have a new firmware available shortly

 

Tom Arbuthnot has done good post here explaining the change, with links to each vendor as they release the firmware  https://tomtalks.blog/2019/04/all-skype-for-business-ip-phones-must-be-firmware-updated-by-july-1st-...

Frequent Visitor
Our Polycom phones firmware is currently managed by Microsoft directly (we don't have our own provision server). Will Microsoft be releasing the new firmware for our phones so these update automatically?
Microsoft

@ElectroRich Yes, we will post the Polycom firmware as soon as it is available. 

Occasional Contributor

Will Microsoft push the release out to Polycom phones (automatic update) or will you just post a link?  We use Microsoft as the provisioning server and they normally only push out the major release # 5.7, 5.8, 5.9.  My understanding is the update will be 5.9.3.

 

Thanks


@Diana_Vank wrote:

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 by July 1st 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 by July 1st 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).

 

consent permissions.png

 

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 1st, 2019. 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.


 

Microsoft

Official posts which includes the partner specific consent URL:

Crestron

AudioCodes

Yealink

Poly

Senior Member

@Diana_Vank Trying to settle a discussion with some of our team. The discussion is whether basic authentication to Office 365 will be unaffected by Microsoft's OAuth/AppID change.

 

On a Poly(com) VVX/Trio UC device when authenticating to Office 365:

1. Modern Auth is used by the "Web Sign-In" feature and https://aka.ms/sphone application.

2. Basic Auth is used when entering credentials via the web browser/server interface option Settings->Skype for Business Sign-in.

 

After a firmware update to 5.9.3+, we're expecting devices using method #1 will be forcibly signed-out and users will be required to re-authenticate (with administrator approval of new appID) --- CONFIRMED https://techcommunity.microsoft.com/t5/Skype-for-Business-Blog/OAuth-2-0-and-third-party-application...

 

We're expecting nothing will change with method #2 (phones happily keep basic auth-ing).

 

Does this sound correct? If not, will edit/remove this post so that false info isn't out there :)

Occasional Contributor
Any update on the Polycom VVX and Trio firmware’s? I see Polycom UC Software 6.0.0.4796 already available on their website. This versioning seems greater than the “5.9.3” posted above. Does that mean it’ll work with Microsoft’s Modern Auth/ OAuth 2.0 changes post-July 1st?

Hi All,

 

Some more updates from Poly (Polycom).

1. We're working with Microsoft to push the new UCS builds (via Skype for Business Online Update) that incorporate the new App ID.

2. We have an official announcement coming hopefully by the end of this week. Refer to my blog in the interim for updates.

3. Initial testing suggests the users will not be logged out when the upgrade is completed, provided the consent is performed prior to roll-out and before the cut-off date.

 

I hope this helps!

 

- Adam

Senior Member

@phake Don't think 6.0.0 has the App ID change. Also note support for many older VVX models ends with 6.0.0 - http://downloads.polycom.com/voice/voip/uc_sw_releases_matrix.html

Version guidance below

Device name Software Version Timeline
VVX Phones 5.9.3 Mid-May
Poly Trio 5.9.0 Rev AB Mid-May
Group Series 6.2.1.1 Mid-June
Occasional Contributor

@Tristan Griffithsand @Adam Jacobs - 6.0.0.4796 is confusing as you'd think it would logically have the App ID changes. Very confusing! I'll wait for 5.9.3.

 

We currently have Skype on-premise (Modern Auth) enabled and Exchange Online (Modern Auth enabled) for some users and our VVX 501's are working. EWS is not - will 5.9.3 save the day in that regard?

Hi @phake totally understand the confusion, 6.x is part of a different fork which is yet to be certified for Skype for Business (which is why this is not published on the Skype for Business VVX f/w page). 6.x will be certified in the future though, stay tuned.

 

Regarding the issue you're having, this is not expected and should work with the existing App ID. Please raise a support ticket and we can dig into this further.

 

Frequent Visitor

One big problem with this is we now have to assess Polycom as a sub processor of data because consenting to the app permissions gives the app full access to all users mailboxes, which could lead to data breach if the polycom service and app is breached. How can we ensure the app is secure and how do we get validation the app will not explore, use or digest information in users mailboxes.

Senior Member

@Graham705 ideally Polycom/Crestron/AudioCodes/Yealink would link to a terms and conditions/privacy document. Looks like they have opted to not provide one.

Capture.PNG

Frequent Visitor

@Tristan Griffiths  Yeah, hence why no one should accept this. You are giving the app full mailbox access to every user. Without a contract in place with the app vendor or a suitable privacy and terms of use policy, most companies should not allow this access. Microsoft need to address this. It would be fine if the app only needed access to read and write calendar events but allowing full mailbox access gives way to significant risk of data breach.

Occasional Contributor

Ah, thanks so much for the clarification @Adam Jacobs. !

 

RE: current VVX 501's and our recent Skype for Business on-premise enabling of HMA, I'm digging into the VVX 501 logs to find out why it's not allowing the EWS + OAuth magic, and will put in a Polycom ticket. Thanks. Any links or obvious config I'm making will greatly help 300+ people!

Hi All, official tech advisory published by Poly here 

Microsoft

Please note deadline change in the original post, now January 15, 2020

Occasional Contributor

So to confirm the firmware update is no longer required by July 1, 2019 but rather January 15th. Is that correct?

Microsoft

@Larry Thomas correct!

Folks - minor update to a statement I made above:

 

Hi All,

 

Some more updates from Poly (Polycom).

1. We're working with Microsoft to push the new UCS builds (via Skype for Business Online Update) that incorporate the new App ID.

2. We have an official announcement coming hopefully by the end of this week. Refer to my blog in the interim for updates.

3. Initial testing suggests the users will not be logged out when the upgrade is completed, provided the consent is performed prior to roll-out and before the cut-off date. <- the latter is only true for users that signed-in locally on the device. For users that signed-in with Web Sign-in they will be logged out, this is due to the fact that their credentials are not cached on the device and so tokens cannot be renewed without intervention

 

I hope this helps!

 

- Adam

Visitor

As this shift into using an AppID seems to be inline with OAuth authentication in general, does this mean that devices should not have to re-authenticate when a user password has expired/changed as it'll be using a token created specifically for that User/AppID at time of sign in?

 

I noticed @Graham705 comment on mailbox access.  I suspect this is required for the voicemail access due to how the devices access/manage the voicemail. Is that correct?  My understanding is that while you are granting the AppID access to mailboxes as the signed in user, it would mean that the device would only have access to the mailbox that user has access to, not ever mailbox on the platform (unless that user has that level of access).

 

Cheers

New Contributor

@Diana_Vank Which post does mention about date moved to Janurary 15th?

Visitor

@msabatThe main post at the top has had the date changed, and now marked in bold.

New Contributor

"Specifically, signing to the device via web or using a user name/password on the phone will fail."

 

I’d be curious to learn whether that goes for PIN authentication as well.

Senior Member

@msabatExtension+PIN authentication is unaffected. Only authentications using ADAL/Modern Auth/OAuth are affected.

Occasional Contributor

@Tristan Griffiths so also anywhere EWS is needed and Oauth is used with EWS.

Senior Member

@oradcliffe yes, if you're signing on to the device using web sign-in (code + https://aka.ms/sphone).

 

(we'll ignore that we can override Exchange authentication via provisioning file)

Occasional Contributor

@Tristan Griffiths oauth is used a bunch of other places, not just web sign in.  This change I believe will affect anything where the phone needs oauth authorization.  We've got web sign in, EWS, even username/pass sign in to an on prem SfB environment if that environment uses Azure STS for auth.

Senior Member

@oradcliffe

username/pass+SfBO+EXO - basic auth

web sign-in+SfBO+EXO - modern auth/oauth

username/pass+SfB+EX on-prem - negotiate (ntlm) or basic

web sign-in+SFB+EX on-prem - modern auth/oauth (think this is now supported)

 

That's my understanding anyway. There would be other more complex arrangements with ADFS and hybrid environments but that hurts my head to think about.

Occasional Contributor

@Tristan Griffiths that is about right yeah, but don't forget you can enable OAuth in ExO and SfBO, as well as SfB on prem.  You can also disable basic auth in your O365 tenant, and then you'd be either using OAuth or just failing to sign in :)

Senior Member
@oradcliffe Yup, with basic auth disabled in SfBO or EXO, only web sign-in (https://aka.ms/sphone) will work.
Occasional Contributor

@Tristan Griffiths that's not entirely true.  I can set up, for one example, Skype on prem to use Oauth with Azure as the token signer.  I could then disable basic auth in my tenant and still use username/pass with my on prem deployment, and that would use OAuth via Azure.

Senior Member

@oradcliffe Would your scenario include ADFS? Just trying to think what mechanisms that would permit getting that OAuth token from the on-prem/azure environment given a username/pass.

 

(my comment should have been "SfBO and EXO" to be more accurate)

Visitor

Anybody notice devices such as the Polycom Centro or any of the Polycom Group Series devices running 6.2 suddenly stop working?

 

2019-07-02 15:43:32.305 WARNING  logcat: hd[0]: System.err(2405): com.microsoft.aad.adal4j.AuthenticationException: {"error_description":"AADSTS65001: The user or administrator has not consented to use the application with ID 'a850aaae-d5a5-4e82-877c-ce54ff916282' named 'Polycom - Skype for Business Certified Phone'. Send an interactive authorization request for this user and resource.\r\nTrace ID: d9f50d5c-688f-4fb4-a9f9-26fe73281b00\r\nCorrelation ID: 976c1c4d-d9fa-4780-a398-6623f173b46a\r\nTimestamp: 2019-07-02 15:43:33Z","error":"invalid_grant"}

This seems to have broken inline with the original date, not their new date.

Hi @jangliss the last upgrade for Group Series requires that the organization performs consent prior to upgrading. It seems this has not happened. Refer to notes here.

 

Notes

 

  • Microsoft has announced changes related to the Microsoft Online device registration requirement. These changes affect RealPresence Group Series systems registered for Skype for Business accounts. Before upgrading your Microsoft environment RealPresence Group Series system to 6.2.1.1, see the Technical Advisory for specific changes and actions required.

- Adam

Regular Visitor

@Adam Jacobs

Is there any harm to consenting to the Polycom App ID right now in our tenant, and will consenting affect current VVXs and Lync phone edition devices?  I assume the consent needs to happen before the devices are auto upgraded by MS to the supported firmware?  Is this still the correct timeline for the firmware releases that will be pushed down to the devices?

 

VVX - 5.9.4 (Q4 Calendar Year 2019

Trio - 5.9.1AA (August 2019)

 

I am still unclear on whether people will be logged out of their phones after the consent and firmware updates.  We have a mix where some are logged in via web sign-in and others with BTOE integration.

 

Thanks for the help and advice!

 

 

There is no harm performing consent against your tenant, existing devices will not be impacted. Testing suggests that the upgrade process will not sign out the device unless a subsequent downgrade is performed. Dates will be more detailed once we have a release vehicle we have an HMA issue we're tracking.

Regular Visitor

@Adam Jacobs 

Thank you for the help!  Is there a recommended route to the firmware updates?  Currently we have devices updating automatically, but normally, is the process where Polycom will release the update and can be downloaded/installed manually on the phone to test?  I assume that Microsoft will not automatically approve that firmware version and push it down to devices right when Polycom releases it?

@myry1 refer to support.polycom.com for manual updates, Microsoft typically pushes certified s/w releases only and after Poly releases them

Regular Visitor

@Adam JacobsThanks, is there a typical time between Poly's release and Microsoft's certified push?  Best practice - automatic updates on phone or manual updates?  I haven't seen any issues with firmware updates in the past, but not sure if testing is more appropriate in this situation.

@myry1 Once the required update is available then it will likely be posted to the device update service quicker than in the past given the potential impact.

 

That being said, Microsoft has ceased their device qualification program for Skype for Business Online, so any new firmware updates beyond this change will be certified, and likely the Device Update services online will continue to push the current versions until SfBO retirement in July 2021.  (An exception would be if one of those releases was found to have a critical security flaw in the future and would need to be replaced with a patched version, but even then it's quite possible that Microsoft just decides to disable the update service in general.  In short, it's always recommended to manage device updates in a different manner and disable the in-band update process as Adam mentioned earlier.)

 

Newer releases may still be able to qualify for Skype for Business Server, but Microsoft does not manage those updates, the customer does in their own deployment.

Occasional Visitor
@Diana_Vank Microsoft is indicating that all phones must be updated by January 15, 2020 to support OAuth. The release notes for Polycom UC software 5.9.4 indicates support for OAuth, but it seems that version is not on the approved list for Skype For Business Online implementations. Customers in Skype for Business deployments should only use software releases that have been qualified by Microsoft or the maintenance releases built on a qualified release. The current version which is qualified by Microsoft is 5.9.0.9373. When will Microsoft qualify the release version 5.9.4? both the below URL's from Poly and also Microsoft suggests us to stay in 5.9.0. Please advice! https://support.polycom.com/content/support/north-america/usa/en/support/voice/polycom-uc/polycom-uc... https://docs.microsoft.com/en-us/skypeforbusiness/certification/devices-ip-phones#conference-phones
Microsoft

@Vinay N V all Poly 5.9.x builds are currently certified for SFB. The listing on docs.microsoft.com implies that any version greater than the certified build listed is also certified.