Preferred IM Client
MS Teams Client hijacks the PreferredIMClient setting when tenant is in "Teams Only" mode. This is problematic for companies who use multiple IM clients (e.g. Cisco Jabber).
Please prevent the MS Teams client from hijacking the
HKEYCURRENTUSER\Software\IM Providers\DefaultIMApp value when in "Teams Only" mode.
A "FindTime" aside:
We needed to change our tenant to "Islands" mode to prevent the PreferredIMClient hijack behavior. In "Islands" mode, the FindTime "online meeting" option does not auto-schedule Teams meetings. In order to get FindTime "online meetings" to work, we have to be in "Teams Only" mode. We decided to break FindTime to fix the MS Teams client behavior.
Please fix! thank you
Ref: [Ticket #:16139055]
We need Jabber for calls and Teams for chatting. Teams takes over the calling part from within office apps even if we set HKCR\tel in the registry to Jabber.
Same issue here. This needs to be fixed asap.
We are experiencing the same issue. Microsoft please fix it ASAP.
Michael Del Corso commented
We also have this concern. These items need to be separated.
We use Jabber as our primary IM provider, however we have more and more people using MS Teams. We had to change the Coexistence mode from "Islands" to "TeamsOnly" in order for Federated messages to be delivered to Teams, this has caused the DefaultIMApp setting to be overwritten for anyone launching MS Teams. Even if you change it in the Teams application it is reset when you sign-out and back in. Please fix this! Thank you
we have to hack this with a custom script. seriously? why on earth would an enterprise have to do this in 2020? please fix this.
We have the same issue. Using teams in teamsonly mode for some time now. We need to onboard an new company who is currently using Jabber for chat and calling and they need to keep using this for some time. Any update regarding this?