Back to Blog
Office 365 legacy authentication5/30/2023 ![]() Next, we’ll use Add filters to add a filter based on client app: We’ll first make sure the information we need is clearly displayed by adjusting the columns displayed by adding client app, as shown below: In this section, you will see all sign-in attempts to Azure AD, including sign-in to all Microsoft 365 services from all your clients. Learn more: Introducing Certificate-Based Authentication for Exchange Online Remote PowerShell with Microsoft MVP Vasil Michev To do this, navigate to the Azure AD portal and then select Sign-ins under Monitoring. You can do this in the Azure Active Directory portal by reviewing sign-in logs using dedicated capabilities to filter based on legacy authentication. ![]() Reviewing legacy sign-ins to Exchange Onlineīefore disabling legacy authentication for Exchange Online, it is essential to ensure that clients won’t be affected or prevented from signing in, or if they will, gather enough information so that you can inform people who will be impacted. In this article, we will walk through the process to identify clients using legacy authentication, then utilize the new functionality available to Exchange Online to disable legacy auth for selected protocols. Recent improvements to Exchange Online make this simple to configure, and you can now retrieve the information you need to identify potential clients that might be affected. ![]() Unless you already have a good understanding of your clients, it may present a risk. ![]() Keeping legacy authentication enabled in your Microsoft 365 tenant should be avoided however, going ahead and disabling has traditionally been difficult. ![]()
0 Comments
Read More
Leave a Reply. |