A Ghacks article proves that this feature has been available on Outlook.com since 2013. Since Outlook.com has been using a version of Office 365 for a couple years now, how is it possible that full-blown Office 365 doesn't have this? It's a superset of Outlook.com! So it must have been a deliberate choice.
Here's one that I don't think has been suggested yet. See the response from Joe Backiewicz at the bottom of p.1.
No Registry changes, just removing the account (if it exists) in this Windows settings area: Settings/Accounts/"Access work or school" area.
I don't know what kind of crazy clash is occurring between Outlook and that, especially out of the blue, but it's the only thing that solved it for me, and I tried everything else.
DisableADAWAM isn't mentioned anywhere else though. Seems hard to believe it could be right for any version of Office.
Your logic is just because DisableADALatopWAMOverride and DisableAADWAM are different in the middle?! What if those middles stand for different things, like Azure Active Directory Authentication Library (ADAL) and Azure Active Directory (AAD)?
2 votesBrian shared this idea ·