SOLVED

Problems with Native Teams desk phones as Common Area Phones

%3CLINGO-SUB%20id%3D%22lingo-sub-1668763%22%20slang%3D%22en-US%22%3EProblems%20with%20Native%20Teams%20desk%20phones%20as%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1668763%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20gotten%20this%20to%20work%3F%20I've%20provisioned%20several%20user%20accounts%20to%20assign%20CAP%20license%20to%20as%20follows%20(and%20waited%20more%20than%2048%20hours)%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20Common%20Area%20Phone%20License%3CBR%20%2F%3E2.%20Microsoft%20365%20Domestic%20Calling%20Plan%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETrying%20to%20sign-into%20a%20Poly%20CCX%20and%20a%20Yealink%20T58%20native%20teams%20phone%2C%20and%20wind%20up%20in%20an%20endless%20device%20registration%20device%2Fsign-in%20loop.%20At%20first%20we%20thought%20it%20was%20limited%20to%20just%20the%20Poly%20CCX%20devices%2C%20but%20so%20far%20we%20haven't%20been%20able%20to%20get%20this%20to%20work%20on%20any%20of%20our%20native%20Teams%20phones%2C%20including%20phones%20from%20Yealink%20(T5Xs).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20use%20the%20same%20user%20account%20on%20a%203PIP%20phone%20(Polycom%20VVXs%2C%20for%20example)%2C%20it%20works%20as%20expected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWould%20love%20it%20if%20anyone%20could%20tell%20me%20what%20we%20might%20be%20doing%20wrong%2C%20or%20reproduce%20this%20issue%20for%20me%20before%20I%20go%20through%20the%20issue%20submission%20process.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETIA%2C%3C%2FP%3E%3CP%3EBob%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1668763%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECalling%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1671685%22%20slang%3D%22en-US%22%3ERe%3A%20Problems%20with%20Native%20Teams%20desk%20phones%20as%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1671685%22%20slang%3D%22en-US%22%3EHas%20your%20org%20been%20upgraded%20to%20Teams%20Only%20mode%20or%20are%20you%20still%20in%20a%20hybrid%20mode%20of%20some%20sorts%3F%20Have%20you%20gotten%20phones%20to%20work%20for%20normal%20users%20yet%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1713670%22%20slang%3D%22en-US%22%3ERe%3A%20Problems%20with%20Native%20Teams%20desk%20phones%20as%20Common%20Area%20Phones%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1713670%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe're%20having%20the%20same%20issue%20as%20the%20OP.%3C%2FP%3E%3CP%3EThe%20common%20area%20phone%20accounts%20in%20question%20are%20in%20Teams%20Only%20mode.%3C%2FP%3E%3CP%3ESome%20persons%20are%20still%20in%20Hybrid%2C%20but%20this%20shouldn't%20matter%20as%20the%20CAP%20is%20Teams%20Only%2C%20licensed%2C%20and%20configured%20properly.%3C%2FP%3E%3CP%3EThe%20problem%20comes%20when%20the%20device%20is%20trying%20to%20register%20with%20the%20tenant%20and%20InTune%20it%20will%20loop%20and%20eventually%20go%20back%20to%20the%20sign%20in%20screen.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20are%20logs%20in%20the%20Azure%20tenant%20where%20the%20initial%20log%20in%20is%20a%20success%2C%20but%20registration%20is%20a%20failure%20due%20to%20%22a%20change%20by%20your%20administrator%2C%20or%20you%20need%20to%20register%20for%20MFA%22.%20The%20account%20is%20exempted%20from%20MFA%20in%20conditional%20access%2C%20and%20has%20enrollment%20restrictions%20enabled%20for%20device%20administrator%20as%20well%20as%20been%20added%20as%20a%20Corporate%20managed%20device%20with%20serial%20number.%20Trying%20to%20log%20in%20with%20a%20normal%20account%20on%20the%20phone%20is%20a%20success%20with%20no%20MFA.%20Conditional%20Access%20%22What%20If%22%20testing%20shows%20no%20policies%20applied%20with%20the%20current%20scenario.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EVery%20interesting%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Regular Contributor

Has anyone gotten this to work? I've provisioned several user accounts to assign CAP license to as follows (and waited more than 48 hours):

 

1. Common Area Phone License
2. Microsoft 365 Domestic Calling Plan

 

Trying to sign-into a Poly CCX and a Yealink T58 native teams phone, and wind up in an endless device registration device/sign-in loop. At first we thought it was limited to just the Poly CCX devices, but so far we haven't been able to get this to work on any of our native Teams phones, including phones from Yealink (T5Xs).

 

If I use the same user account on a 3PIP phone (Polycom VVXs, for example), it works as expected.

 

Would love it if anyone could tell me what we might be doing wrong, or reproduce this issue for me before I go through the issue submission process.

 

TIA,

Bob

4 Replies
Highlighted
Has your org been upgraded to Teams Only mode or are you still in a hybrid mode of some sorts? Have you gotten phones to work for normal users yet?
Highlighted
Best Response confirmed by ThereseSolimeno (Microsoft)
Solution

@Chris Webb 

 

We're having the same issue as the OP.

The common area phone accounts in question are in Teams Only mode.

Some persons are still in Hybrid, but this shouldn't matter as the CAP is Teams Only, licensed, and configured properly.

The problem comes when the device is trying to register with the tenant and InTune it will loop and eventually go back to the sign in screen.

 

There are logs in the Azure tenant where the initial log in is a success, but registration is a failure due to "a change by your administrator, or you need to register for MFA". The account is exempted from MFA in conditional access, and has enrollment restrictions enabled for device administrator as well as been added as a Corporate managed device with serial number. Trying to log in with a normal account on the phone is a success with no MFA. Conditional Access "What If" testing shows no policies applied with the current scenario.

 

Very interesting issue.

Highlighted

Teams only, across the board. @Chris Webb 

Phones for regular users have "worked" otherwise for a couple years now.

Highlighted

Thanks for confirming! @RMLee