But, let’s say you don’t know or can’t recall when your Office 365 tenants were created. In my case, I was dealing with the latter and I knew that my Office 365 tenants were created before August 1, 2017. However, if you are running an Office 365 tenant which was created BEFORE August 1, 2017, Modern Auth is DISABLED by default and you must enable it via PowerShell. If you are running an Office 365 tenant which was created AFTER August 1, 2017, Modern Auth is ENABLED by default and your Office 365 tenant should be good to go. Now let’s start off with the Office 365 tenant … Since Office 365 tenants can vary in complexity, I’m going to focus on simple Office 365 tenants (ex: a basic Office 365 tenant setup for a small business) however, if you have a more complex environment which utilizes third-party applications, custom scripts and so forth, you’ll need to do further research before transitioning to Modern Auth. A lot of the relevant material is spread across various webpages and isn’t organized well. I’ve gone through Microsoft’s support and technical documents on this topic and it may make your head spin. Now is the time to prepare and make sure your Office 365 tenants and your desktop and mobile e-mail client applications support and are ready for Modern Auth to avoid disruption to service on or after October 13, 2020.
