Using older versions of Outlook for Mac in business environments
has this been fixed yet please? my boss is having this problem. thx.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
All-
As we know, one of the biggest bugs in Outlook for Mac 2016 is the ever-so-annoying repeated password prompt problem. This refers to the constant pop-ups that make it appear like Outlook is forgetting your password every few minutes, etc. The problem was much discussed during the Preview phase of Office for Mac 2016 but never corrected. I did some digging on the forums here and found other threads that covered this problem with slight variances, but the core issue is the same -- credentials are somehow not being stored properly or become corrupted during normal operation of the software. List of the relevant threads I found below. This list may not be comprehensive:
It seems odd that a major bug like this remained unresolved after the official release of Office for Mac 2016 ... and still hasn't been corrected! Per post responses on Microsoft's official Office Blog, they are looking into authentication issues with Exchange Server, but who knows what that means or how long that will take. Based on what I can gather:
e.g. username@DOMAIN vs. DOMAIN\username vs. username
A ticket submitted by forum member *Filip Herman* to Microsoft's technical support around early August 2015 indicated that Microsoft is aware of the problem and has a planned fix in progress. Obviously its been years since that. Others have submitted tickets to support since. Scroll to the end to read the most current progress.
I'd encourage everyone to mark this post, indicating that you "recommend this discussion." This thread has tens of thousands of views and hundreds of comments, so its clearly not an isolated issue. Unfortunately, my company abandoned the use of Outlook for Mac 2016 some while back because of this issue, so I don't have an active platform to test on anymore. However, keep trading ideas here as needed.
Best of luck-
Seattle_Expat
Using older versions of Outlook for Mac in business environments
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
has this been fixed yet please? my boss is having this problem. thx.
has this been fixed yet please? My boss is having this problem.
If you've cleared your keychain on your Mac and/or rebuilt your local folders by disconnecting/reconnecting Outlook, you should also check to see whether you have any other Mac devices with a cached/aged credential stored in the keychain on that machine. eg if you've accessed a single sign on web resource from the other machine and allowed keychain to store the credential.
Your domain administrator should be able to check your access logs and tell you which device is failing authentication to help you narrow it down.
Out of a sudden Version 15.17 (151206) stopped working with my Exchange credentials that I have provided on day one of my standalone Office 2016 usage.
What helped was to change DOMAIN/username to username@DOMAIN.
Thanks TonyMC98,
I could be wrong, but this might be the first post that suggested part of the problem was with Exchange Server instead of just the Outlook for Mac client. Then again, others have had the same issue connecting to Gmail accounts where no Exchange Server is present. But, this got me to thinking and I took a look at the Exchange Server service packs and rollup updates to see if there was any mention of this problem. Nothing seems to reference the "Outlook for Mac authentication issue" outright, but there are several nondescript references to MAPI and IMAP client crash issues.
For easy reference, I found these links on TechNet this might be useful for readers here. (Note: you might need to create a TechNet account to see the article content:
Exchange Server and Update Rollup Build Numbers <-- Exchange Server 2003 to 2010
Exchange Server 2013 and 2016 Build Numbers (with Cumulative Updates)
Hope this helps.
SeattleExpat