That’s 3 hours of my life that I’ll never get back, hopefully this can save you from the same fate. HKCU\Software\Microsoft\Exchange\AlwaysUseMSOAuthForAutoDiscover DWORD 1īasically after configuring that setting via PowerShell, Outlook was able to add the account straight away. Issue Update: Partners have reported Outlook 2016 prematurely connecting to Office 365 without any identifiable.
I also, prior to this PowerShell tweak, set a registry key that may or may not have helped in the end, although it didn’t help at the time. Outlook 2016 users are not yet active in Office 365, but have mailboxes provisioned in Office 365 Autodiscover is not working on the source server or the connection between a computer and the source email server is interrupted. To check that this command worked: Get-OrganizationConfig | Format-Table Name,OAuth* -Auto Then, it was a matter of running this one-liner: Set-OrganizationConfig -OAuth2ClientProfileEnabled $true Oh, this first required setting a hidden preference in the Chromium version of Microsoft Edge as well, just because, well why not at this stage?Īfter installing the module, I could log into PowerShell, and connect to Exchange Online with modern auth.
This required me to download the Microsoft Exchange Online Remote Powershell Module, which I could get via logging into the Exchange Admin Console for Office 365 and going to hybrid > setup and clicking the Configure button to download the module.
I had to update the tenancy settings via PowerShell, but in a cruel twist of fate, for some reason the Global Admin account had MFA turned on via SMS that I couldn’t disable. I eventually found a forum post with what I think was the solution. I tried everything – creating a new profile in Outlook, even creating a totally new user account on the computer. There was absolutely nothing that I could enter into this dialog box that would work.
No matter how I tried to configure the account, it would eventually pop up the Windows Security dialog box, asking for a username and password – and this was the end of the line. Outlook on the user’s primary workstation.įor some reason, no matter what I tried, Outlook kept trying to sign in with legacy authentication, not modern authentication. We have a case open with Microsoft, but still no word yet on the cause and permanent fix.I had a really thorny problem recently with a client who responded to a phishing email and their account was compromised.Īs part of reviewing their account security, I enabled Multi-factor Authentication.Įverything went well signing back into the account, except for on one device. We did a reg hack to disable Office's call to WAM and force ADAL, until we updated our Win10 machines to v1809. If Office didn't see WAM running, there was no automatic fall back to leverage ADAL. This is similar to what occurred 2018 Q4 / 2019 Q1 when Office updated its authentication mode by leveraging WAM on Win10 machines not yet running v1809. Office apps can still run, even if the silent login fails, except Outlook because it still needs to login to Exchange Online. Recall when running O365 setup, and you get the prompt to sign into cloud, then after, it does the silent login. Office apps with their licenses sourced in the O365 Cloud authenticate there each time you launch one of the apps. That's your clue that the issue is not with Outlook / Exchange, but with the O365 client.
They should show connections to the Sharepoint and OneDrive for Business sites tied to your O365 Cloud account.
Check the Account settings (File tab > Account) in any Office app - Word, Excel, Powerpoint - and see the Connected Services section. This is not an issue with Outlook, but with the Office 365 desktop client.
It's less disruptive than disabling WAM entirely. This happens especially in the case of newly configured email accounts. There's a simpler workaround by removing two Binary String entries under the 'Identity' subkey. Most common reason for ‘Outlook cannot connect to SMTP server’ error is the wrong configuration settings of Outlook.