In my case, most of the events were associated with native email clients on smartphones, they need to be migrated to the MS Outlook app.ĪllowBasicAuthReportingWebServices : Falseįor security purposes, you can create a separate policy with different Basic Auth permissions for specific protocols and assign it to users using the legacy application. You need to migrate the found applications to the Modern Auth protocol. This will allow you to find users and applications that are still using Basic Authentication.

Select all Legacy Authentication Clients for this filter.

Go to the Azure Active Directory -> Sign-in logs.

It will appear when connecting to Microsoft 365 services or connecting to Azure (including PowerShell connections).īasic Authentication Sign-in Log in Azure ADīefore enabling modern authentication and disabling basic authentication, check which authentication protocols your Microsoft 365 users and apps use. The window for entering a username and password when performing modern authentication looks like this. Modern Auth supports additional authentication factors including MFA.

Apps don’t store or use user credentials, and authentication is based on time-limited tokens. Modern Authentication is based on ADAL (Active Directory Authentication Library) and OAuth 2.0 protocols.Applications store and explicitly use the username and password for authentication. This authentication type doesn’t support MFA (Multifactor Authentication) and is not robust against brute-force attacks. Basic auth is performed through a simple Windows Security window that prompts for a credential (username and password) and prompts you to save your password to the Windows Credential Manager.

Basic Authentication – this type of authentication is familiar to all Windows users.Microsoft currently supports the following types of authentication for Office 365 (Microsoft 365): How to Enable Modern Authentication for Microsoft 365 Tenant?.Basic Authentication Sign-in Log in Azure AD.

Office 2013 modern authentication