I spend a lot of time switching between the Entra admin center, the Azure portal and PowerShell - reading extension properties, filtering users by those properties, and checking user status and details. They are good tools, but they show everything, one blade or command at a time. And that is the problem. The questions I ask every day are not โshow me this objectโ. They are: ...
Maester is an amazing tool. Point it at an Entra ID tenant. A few minutes later you have one self-contained HTML report. It tells you which of about 280 security controls hold and which do not: CIS, CISA/SCuBA, EIDSCA, ORCA, plus any custom Pester test you write yourself. Run it once and it is excellent. Run it every night, across several tenants, and you learn something else. A report is not the same thing as a practice. After a few months you have a blob container with hundreds of files, three per run: ...
๐๐จ๐ฐ ๐๐จ ๐ฒ๐จ๐ฎ ๐๐ง๐ฌ๐ฎ๐ซ๐ ๐๐จ๐ฆ๐ฉ๐ฅ๐ข๐๐ง๐๐ ๐๐ง๐ ๐๐ฎ๐๐ข๐ญ๐๐๐ข๐ฅ๐ข๐ญ๐ฒ ๐ฐ๐ก๐๐ง ๐ฆ๐๐ง๐๐ ๐ข๐ง๐ ๐๐๐ซ๐ฏ๐ข๐๐ ๐๐ซ๐ข๐ง๐๐ข๐ฉ๐๐ฅ๐ฌ ๐๐ง๐ ๐๐๐ ๐๐ฉ๐ฉ๐ฅ๐ข๐๐๐ญ๐ข๐จ๐ง๐ฌ ๐ข๐ง ๐๐ข๐๐ซ๐จ๐ฌ๐จ๐๐ญ ๐๐ง๐ญ๐ซ๐ ๐๐? Hereโs a proven architecture that combines developer self-service with strong governance: The Flow: Developers request identities via Backstage Backstage generates Terraform configs as Pull Requests Identity Operations team reviews and approves GitHub Actions provisions resources in Entra ID via Terraform Maester continuously audits all non-human identities against Entra as Code (Terraform) Compliance issues are automatically detected and reported Key Benefits: ...