Blog series This is part three of the six-part series on “Phase out Legacy Authentication”. Preface Enable Modern Authentication Create prerequisites Gain insights The first 90% The next 9% Endgame Recap In the first part, Modern Authentication was enabled and in the second part, the prerequisites were created to create detailed reports and to disable Legacy Authentication for individual users. Conditional Access policy logic To better understand how it is possible to block individual users, let’s take a look at the Conditional Access Policies created and the login associated with them.

Blog series This is part three of the six-part series on “Phase out Legacy Authentication”. Preface Enable Modern Authentication Create prerequisites Gain insights The first 90% The next 9% Endgame Recap In the first part of the series, Modern Authentication was enabled for all Microsoft 365 services and can now be used. This part is about creating the prerequisites to gain a detailed insight into the usage of the different authentication methods and to make it possible to disable legacy authentication per user.

Blog series This is part two of the six-part series on “Phase out Legacy Authentication”. Preface Enable Modern Authentication Create prerequisites Gain insights The first 90% The next 9% Endgame Enable Modern Authentication This step may seem strange, but in old tenants (created before 01.08.2017) Modern Authentication for Exchange Online and Skype for Business Online is not necessarily enabled. Exchange Online For Exchange Online, the Exchange Online PowerShell V2 module must be installed to enable Modern Authentication.

In an Azure AD environment, legacy authentication is the Achilles heel of security. While modern clients take into account conditional access policies and multifactor authentication, the use of legacy clients and associated protocols such as SMTP, IMAP or Exchange ActiveSync creates an often overlooked gap in this protection. Since these protocols are not compatible with Conditional Access, they “bypass” the protection unless explicitly defined. This is not a security hole on Microsofts part, but a design decision and the impact on your own environment should therefore be well understood.

Wireshark is a powerful tool to analyze network data. However, it is another tool that needs to be regularly updated and that relies on additional software (Npcap) to capture network data. But Windows has a built-in tool to create a network trace. And with a small additional tool the created etl file becomes a pcap file which can be analyzed without any problems. An installation of Wireshark and Npcap is therefore not necessary to capture the data.

When analyzing network problems, a simple ICMP ping is never sufficient to verify if the connection between two devices works. Normally a TCP connection to a server is needed and PowerShell comes with an appropriate cmdlet Test-NetConnection. However, by default Test-NetConnection only supports TCP connections and also tests an ICMP ping each time. So, what’s up with UDP? There is no built-in tool for analyzing stateless UDP packets, so I wrote the following two functions.