Does anyone have a solution for this? I'm experience the same issue on jabber for windows ver 12.0. Except my jabber conversation is not saving to outlook, however jabber is able to pickup my calendar meetings from outlook.
I have been having this intermittently with different users.
The fix has been to uncheck "save chats" and apply and then check "save chats" and apply.
I have one user that this has not worked for. Still working in this one.
also making sure the servers were set to: https://outlook.office365.com
Thanks jzellner, But in my case it appears to be MFA. My office 365 users have MFA enabled on their account, and Jabber does not authenticate with multifactor authentication turned on. I've raised a TAC case and they have confirm that this not yet supported, but their dev team are working on a solution.
Workaround - If possible disable MFA authentication for your users, or create an App MFA token for Jabber, when Jabber prompts you to enter exchange credentials user enters email address and the App MFA token. Obviously this will only work for as long as the user is signed into Jabber, when Jabber resets you'll have to re-enter the app MFA token, but the good thing is the app token remains the same, so no need to regenerate a token again.
I'll make sure to add the TAC solution when it becomes available.
Thanks for the update!
It looks like I am running into the MFA issue as well as the user with the issue was recently converted to MFA. I will test your workaround.
Here is the Bug - Keep an eye on it.
What string are you using for trying to auth to O365? Our Users auth to Jabber via SSO MFA, but authenticate into their PC using AD user/pass. We just swung over to modern auth(SSO) for O365 apps, and I am trying to see if we can swing Jabber over to use the token from signing into Jabber with auto sign into Outlook. Does the below config seem accurate?
Hi is this a parameter in jabber-config.xml, or where do we set this?
"configuring ExchangeUserIdType to 0 to use userid@domain to authentication against exchange can resolve this issue."
Our issue was related to some users not being able to sign in to O365 with basic auth. MS will be deprecating basic auth in Oct 2020.
As of Jabber version 12.6 there is now support for modern auth, users affected with "Invalid Exchange credentials" can now sign into O365 with this method.
The following parameters should only be required in your jabber-config:
Depending on your environment though, you may still see "session expiry" warnings in Outlook tab when going to and from MRA mode. Will require user action to "renew session".