Entra ID and Maester are central to the security topics I want to explore on frank.cloud. Both lead back to the same question: how do we turn a security configuration we set up once into something we can keep checking?
Configuration is not a finishing line.
A tenant changes. New applications arrive, access policies evolve, and exceptions sometimes outlive the reason they were created. A manual review captures one moment in that process.
Maester makes security requirements for the Microsoft cloud executable as tests. The open-source PowerShell framework checks Microsoft cloud configuration and produces reports that let you investigate individual results.
From requirements to repeatable checks.
The available tests include checks from EIDSCA, and you can add your own requirements. Recurring runs can be integrated with GitHub Actions or Azure DevOps, so changes to a tenant can be checked against the same expectations over time.
That is the space I want to explore here: Entra ID, Conditional Access, managed identities and the practical use of Maester. The original articles on CAE and Logic Apps are also preserved in the archive.
What a green result actually tells you.
A passing test demonstrates the specific condition it checked at the time it ran. Test coverage, permissions and the evidence behind a result deserve just as much attention as its colour.
Future field notes will explore which requirements are useful to test, what needs to be tailored to an organisation, and how to turn findings into improvements you can follow up on.
Official Maester documentation · Explore the Entra ID archive
Maester is an independent community project.