Your Microsoft 365 test automation framework
summary
An open source PowerShell module called Maester ships runnable Pester tests that call Microsoft Graph, exercise about forty Entra/conditional access checks and use the new conditional access what-if API to simulate MFA outcomes. Tests produce an HTML summary, deep links into the conditional access blade, and CI integrations (GitHub Actions with workload identity, Azure DevOps) plus email alerts. Setup runs in minutes, requires reader-level consent scopes, and accepts community PRs for new tests.
AI-written summary · about
chapters (22)
- 0:00Maester framework intro
- 1:43Test automation for M365 security
- 4:09Cloud settings misconfig issues
- 6:37Maester’s test automation
- 7:00Installing and running Maester tests
- 10:52Maester architecture and Pester
- 14:24Maester name and philosophy
- 15:29Simplify test results for admins
- 16:56Maester setup with GitHub Actions
- 18:45Custom tests for your tenant
- 20:11Test conditional access policies
- 22:39Why test identity policies
- 23:22GitHub integration and results
- 25:09Email alerts and daily automation
- 26:12Maester team and open source
- 27:58Pester versioning and dependencies
- 30:28Expanding to other Microsoft services
- 31:11Secure auth without secrets
- 32:32Accepting new test PRs
- 33:39Excluding and customizing tests
- 35:45Updating Maester and tests
- 38:17Maester reporting future
related talks
46mLeverage from Pester to automate Azure Storage Account testing
01h 02m1,2,3… testing: is this thing on(line)? Meet your new Microsoft Testing tools
35mIaC Automated Assurance
43mBeyond Pester 102: Acceptance testing with PowerShell
40mTest Before You Deploy; How to Test Your ARM Deployments
39mWriting Pester Tests at Scale
06mAutomated and Manual Testing with Azure Test Plan
58mWho tests their cloud code anyway?