Managing and monitoring Microsoft Entra ID as Code - Is it worth it?

Overview

In a corporate world we've used to our identity provider being something that is constantly changing due to the need to manage identities, groups and other objects. This has been traditionally done via ClickOps or later semi-automated using PowerShell scripts. In public cloud and in Microsoft Entra ID the same legalities apply. We still have most admins maintaining Entra ID from the Portal experience and some using PowerShell. What if there was another way to manage your tenant configuration? And monitor that it stays that way? In this session I will challenge the audience to think unconventionally about managing Microsoft Entra ID, something that is typically done via 'point-and-click' method inherited from Active Directory management. Topics included are: - Pros and cons of different methods of Microsoft Entra ID management - Seeing if there is a use case for IaC based management - Can IaC-based management help with resilience and business continuity? - Technical walk-through of setting up IaC best practices for Entra ID tenant - Current limitations of the Bicep in Entra management - Monitoring for configuration changes In the demo part I'm going to cover how to start managing your tenant as code and how to set up continuous monitoring.