“Once Exchange Online Modern Authentication is enabled for Outlook for Windows, wait a few minutes.”

And here it comes! Expert advice and things to know We asked some experts at Microsoft who have been through this with some of our biggest customers for their advice. Is it because it all sounds too easy? Or because there is a fear of the unknown? Or spiders? (We’re all scared of spiders, it’s ok.) Set-OrganizationConfig -OAuth2ClientProfileEnabled $true You took a look at our docs, found the article called Enable or disable Modern Authentication for Outlook in Exchange Online | Microsoft Docs and saw that all you need to do is read the article (which it says will take just 2 minutes) and then run: Any change that might impact those users is never to be taken lightly.Īs Admin, you know you need to get those users switched from Basic to Modern Auth, and you know all it takes is one PowerShell command. This is the client most widely used by many of our customers, and the client that huge numbers of people spend their day in. This post is specifically about enabling Modern Authentication for Outlook for Windows. But the ‘getting there’ part might be the hard part, and that’s what this blog post is about. Modern Authentication, based on OAuth2, has a lot of advantages and benefits as we have covered before, and we’ve yet to meet a customer who doesn’t think it is a good thing. Since we announced in 2019 that we would be retiring Basic Authentication for legacy protocols we have been encouraging our customers to switch to Modern Authentication. I wanted to pass this Exchange Team Blog article along since it has come out with updates recently.

I worked with doing some OAuth calls when I was in EXO CSS at Microsoft. This type of authentication has been around since about 2017 timeframe with OAuth v1 and now has updated with OAuth2.

Exchange modern authentication