/images/avatar.png

Work and live with IT

Phase out Legacy Authentication - Endgame

Blog series This is the last part of the series on “Phase out Legacy Authentication”. Preface Enable Modern Authentication Create prerequisites Gain insights The first 90% The next 9% Endgame A lot of work lies behind you when you arrive here. Starting with the necessary preliminary work, the required changes, through reporting and maintaining exception lists. But the biggest hurdle for the next step was definitely the last 9%. Finding and removing every exception is time-consuming and tedious.

Phase out Legacy Authentication - The next 9%

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 Having disabled the majority of users who do not use Legacy Authentication in the last article, it is now time to use the methods outlined in part three to identify the user groups that are still affected. This data will be used to create an action plan for the deactivation of Legacy Authentication for these user groups.

The case of the... Intune SCEP Profil hangs in pending state

The case of the... In this category I publish blog post explaining a problem and the solution but more important the analysis that lead to the root cause. The name is a homage to “The Case of the Unexplained” from Mark Russinovich. The error Quote Trust of the root CA is best established by deploying a trusted certificate profile to the same group that receives the SCEP certificate profile. […] To use a SCEP certificate profile, a device must have also received the trusted certificate profile that provisions it with your Trusted Root CA certificate.

Phase out Legacy Authentication - The first 90%

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 The first three parts of the series set the stage (1/2) for the deactivation and used Entra ID (Azure AD) workbooks and Kusto queries to identify the first usergroup. Add AAD group members To go straight ahead, the Entra ID (Azure AD) group CAPolicy-Include-Block-Legacy-Authentication must be populated with the users from the last query.

Phase out Legacy Authentication - Gain insights

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.

Phase out Legacy Authentication - Create prerequisites

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.