Released: March 2024 Exchange Server Security Updates

>We tried the following under advanced settings that worked

>Email adress: entered it
>Password: Entered it
>Description: Entered it
>Server: Entered it
>Domain: Ommited this field (left it blank)

Peter, as I already stated:

Unfortunately, that does not work, all permutations of userID and password and domain result in:

"An error occurred during authentication please try again"

I'm not even seeing an invalid userID in the Event Log.

This started after the Mar update.  Since ours was working previously and now it's not after the update, and yours was broken previously perhaps if you apply the update it will fix yours, lol.

At this point I don't want to even try removing the update as I can't even trust that Microsoft wrote the uninstaller properly.

I don't know what I'm supposed to do.  Outlook for Mobile is a free product, thus absolutely no contractual basis exists between us and Microsoft so I can't even file a bug where I have a right to demand a fix since I haven't paid anything for the product.  NONE of you have, for that matter.

What is even stupider is the only channel I can find for even reporting a bug in Outlook Mobile is the in-app help:

https://support.microsoft.com/en-us/office/get-in-app-help-for-outlook-for-ios-and-android-218a22d1-9fa5-4889-b689-de1c63493243

which only works when you have a working account that you can open email with!!!!!   How stupid!!!  It's like the phone company telling people if you have a problem with your phone then call them!!!

By releasing a product for the mobile space that is partially borked in this way, without releasing the source code of that product, all it serves to do is lead users astray. There's NOTHING I can do about it other than switching users over to the Gmail and Apple mobile email apps. 

I'll point out that the Gmail app source code is here:

https://github.com/aosp-mirror/platform_packages_apps_email

If MS made source of it's free Outlook Mobile app also publicly available, the bug would have been identified by now and corrected.  They make zero revenue from this product, they don't even spamvertise adverts with it, all it is for them is something they can wave around by their sales group and say they have a mobile app.  So, drop the flipping source and let devs out in the real world fix it!  They do that plenty already with other stuff that they DO make money off of.

I saw this kind of problem happening with the on-prem version of Office 2019, when that dropped Outlook was modified to make a first check at office 365 for an account and would come back with an error if there was no account at Microsoft.  You could then override it and tell it to go to the real on-prem mailserver.  There's even a registry fix out there to correct this.  I strongly suspect the same thing is going on with this mobile app.  We DON'T use O365 and stuff like this just enhances our determination to NEVER go that way.