Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
2222
Views
5
Helpful
3
Replies

Jabber Application in MS Teams won't authenticate

bukhari.shakil
Level 1
Level 1

‎12-28-2020 10:29 AM

Whenever I try using the Jabber app for MS Teams, it prompts me to give it 'permission' by signing into my work account. I sign in, then get a "you can't get there from here" error message. 

 

I read on a Microsoft forum that apparently "Teams cannot support both AADJoined machine and workplace Joined machine smoothly." So I tried the solution posted in that forum and created the registry key, thinking the join method could be the cause of the issue (which didn't work). I'm fairly certain our org is hybrid AD joined since we also connect to our VPN.

 

Now I'm thinking this could be some sort of configuration or federation/permission issue either at the MS admin level or the Cisco admin level. I am a Teams admin but don't think there's a configuration page for Jabber on the Teams side.

 

Any thoughts?

Preview file
38 KB
0 Helpful
3 Replies 3

Roger Kallberg
VIP
VIP

‎12-28-2020 12:30 PM - edited ‎12-28-2020 12:31 PM

The permission need to be granted by a domain admin in Azure where MS Teams runs. The permission is for an application, not an individual.



Response Signature


bukhari.shakil
Level 1
Level 1
In response to Roger Kallberg

‎12-30-2020 08:29 AM

Is there an Azure policy in particular you might be referring to? We tested adding a user to a conditional access policy - which worked but we don't want to apply the policy individually to everyone since our company works with sensitive information and the policy seems to apply to all apps and forms of log on. Our Azure admin said that the issue was with the Primary Refresh Token (PRT), basically in that the PRT wasn't coming through. Without the PRT, Azure is unable to identify the device and device state.

 

Its also worth noting that the same issue is present when using the Webex Call app for MS Teams (which makes sense).

 

Any further guidance is highly appreciated.

 

Authentication details:

Request Id: bf338eb1-9746-459b-9975-31f96d5c7d00
Correlation Id: eb545e2b-4347-4b06-931f-807feb34625b
Timestamp: 2020-12-30T16:25:58.657Z
App name: Jabber
App id: 223b6ef0-6b61-4867-ac7f-9eccc7413b46
IP address: [REDACTED]
Device identifier: Not available
Device platform: Windows 10
Device state: Unregistered

0 Helpful
Customers Also Viewed These Support Documents