Attackers will go after weaker credentials and passwords to gain network access. Small businesses often set up shared mailboxes that are used for various functions. If one set of credentials for a shared mailbox is compromised, it could have a wide impact on the company.If you\u2019ve enabled multi-factor authentication (MFA), you might think that you\u2019ve done enough to ensure you are protected. Unless you disable legacy authentication in your Office 365 implementation, however, you are still at risk. Basic authentication is enabled by default in all Office 365 implementations unless you disable it.First, how do you know if your Office 365 still supports basic authentication? Open Microsoft Outlook and look at the authentication window that pops up to ask you for a password. If it looks like the traditional authentication window you\u2019ve seen for years, basic authentication is still enabled. Susan BradleyTraditional sign-in window means basic authentication is still active(Note: All screenshots were taken in June 2019. Given that Office 365 and Azure are fluid platforms, they might look different when you view them later.)Before you disable basic authentication, review what applications are using it. Many applications rely on basic authentication and are not ready to be restricted to modern authentication. Go to the Azure Portal, into the Azure Active Directory and review the sign ins.Click on \u201cColumns,\u201d add client sign-ins to the view and click \u201cOK\u201d. Review for any applications that log in that use older legacy authentication. Some third-party applications that hook into Office 365 may still use basic authentication. For example, the native iPhone mail application still relies on basic authentication. If you disable basic authentication, you might have to set up an iPhone Exchange mail profile after MFA is enabled. To set it up, remove the iPhone Exchange profile, re-add the user account to set up the profile again, and then select \u201cSign in when prompted\u201d. You will then get the appropriate modern authentication window to trigger the proper authentication process. Susan BradleyReview sign-in activityTo limit the issues you might face, focus on client applications that use Unsupported Exchange ActiveSync and on the categories of Other clients. Narrow in on IMAP, MAPI, older office clients, POP and SMTP as these older applications will expose your Office 365 and Azure Active directory to password spray attacks. Susan BradleyFilter on older authentication techniquesDisabling unneeded authentication is an easy process. Go to the Microsoft Admin Portal. Select a user, go to mail, and then to \u201cManage email apps\u201d. Susan BradleyManage email appsDisable any authentication processes that you do not need: In particular focus in on disabling IMAP and POP as these two are targeted in password spray attacks. Susan BradleyDisable unneeded appsObviously, disabling IMAP and POP one mailbox at a time is not a viable methodology. Here\u2019s a PowerShell command to help:Get-Mailbox | Set-CasMailbox -PopEnabled $false -ImapEnabled $falseYou may also be able to disable SMTP, but this may depend on other applications. If you can disable all three, then use this PowerShell command:Get-Mailbox | Set-CasMailbox -PopEnabled $false -ImapEnabled $false-SmtpClientAuthenticationDisabled $trueTo ensure that any new account going forward does not have IMAP and POP enabled by default, \u00a0you might want to disable the authentication proactively. Use this PowerShell command to disable IMAP and POP on any new accounts:Get-CASMailboxPlan | Set-CASMailboxPlan -ImapEnabled $false -PopEnabled $falseTake the time to review if you still need legacy authentication in your Office 365 implementation. If a vendor requires it, ask them what their plans are \u2014 or rather were, as they should have been off legacy authentication a long time ago. It\u2019s time to forget the terms IMAP and POP and put them behind us.