I'm helping a small organization with several Microsoft 365 Basic accounts. Most users are still running Outlook 2016, and security defaults and MFA are disabled. One user suddenly stopped connecting to Outlook. Their credentials work normally in webmail, but Outlook reports connection problems, cannot display folders, and eventually closes.
They deleted saved credentials, signed out of other Office apps, removed the Outlook profile, and tried various registry changes related to modern authentication. The account now fails to create an encrypted connection even on a newly configured Windows 11 computer with the latest Microsoft 365 installation. The authentication window appears briefly and disappears before it can be used.
The same failure occurs on three different computers, while every other mailbox in the tenant works. Autodiscover tests appear to pass. Microsoft's connectivity test reports a 401 failure during the MAPI stage, although testing known-good accounts also produced the same result there. MAPI is enabled for the affected user as far as I can tell.
Since the problem follows the account rather than the computer, what mailbox or Microsoft 365 settings should I investigate next? I'm also wondering whether Outlook 2016 compatibility or the previous registry changes could be involved.
3 Answers
Because the same account fails on multiple machines while webmail works, I’d focus on the mailbox and tenant configuration rather than reinstalling Outlook again. Verify that MAPI is enabled for that specific user and check the mailbox’s client-access settings. It may also be worth disabling and re-enabling MAPI, then creating a fresh profile after allowing time for the change to propagate. The fact that other users work does not rule out a per-mailbox setting or corruption.
The connectivity analyzer result should be interpreted carefully if known-good accounts fail at the same MAPI step too. That may be a limitation or expected behavior of the test rather than proof that MAPI is broken. Compare the affected user’s Exchange and client-access settings directly with a working user, and check the service health history since there was also a reported outage, even though the original problem predates it.
Outlook 2016 is old enough that authentication support and update level matter, especially with Microsoft 365. However, a current Microsoft 365 installation failing for only one account points more strongly to that mailbox, its licensing, or its assigned service settings than to Outlook 2016 itself. Check the user’s license and Exchange Online service assignment, confirm the account is not blocked or sign-in restricted, and review recent sign-in and authentication logs for the 401 response.
That matches where I’m leaning now. MAPI is currently enabled, but I’m going to toggle it and recheck the mailbox settings instead of making more changes on the client computers.