About
Built for admins who want to understand before they change.
SecureOps Playbooks is a practical Microsoft 365 security, PowerShell, and automation resource built around one simple idea: visibility and documentation should come before changes.
Who’s behind this
I’m Justin, and I work in IT as a Microsoft cloud engineer with a background in sysadmin and MSP environments. I’ve worked on real-world Microsoft 365 projects involving migrations, Entra ID, Conditional Access, Intune, SharePoint, PowerShell automation, security hardening, documentation, and technical planning for small and midsize organizations.
A lot of my work sits in the space between “the docs say this should work” and “here’s what actually happens when you roll it out for users.” I try to write from that perspective: careful, practical, and honest about tradeoffs, gotchas, and what should be reviewed before making changes.
I started SecureOps Playbooks to turn the notes, checklists, scripts, and lessons I wish I had earlier into something useful for other admins.
Why I’m building this
I started SecureOps Playbooks because I wanted a place to turn repeated Microsoft 365 admin work into practical, reusable playbooks.
Microsoft 365 admin work can get messy fast. Policies evolve. Licenses change. Guest users, mailbox forwarding, admin roles, authentication methods, SharePoint sharing, and Conditional Access can all affect each other. A setting that looks isolated on one screen can be part of a bigger story once you check the tenant around it.
The point of this site is to help admins slow down just enough to understand what they are checking before they change anything. Not to freeze the work. Not to make every task feel bigger than it is. Just enough review to avoid walking into a change window with assumptions where notes should be.
What I care about
I care about making technical work easier to understand. Admins should know what they are checking, what the output means, and what the workflow does not prove before they change anything.
The working principles
A good admin workflow should make the next decision clearer. If a script produces output but nobody can explain what the output does and does not mean, the work is not finished yet.
Who this is for
These guides are written for the admin who needs to understand what they are checking before they change anything: Microsoft 365 administrators, cloud engineers, MSP engineers, help desk technicians growing into admin work, and systems administrators taking on Microsoft 365 responsibilities.
A lot of admins are learning while doing real work. Sometimes that means a ticket queue, a security review, a licensing change, a new Conditional Access requirement, or a manager asking for an answer before the full picture is clear.
Those admins deserve resources that explain the why, not just the command. The goal here is to give you a steadier starting point, so you can read the output, document what you found, and decide what needs a deeper look.
What SecureOps Playbooks is becoming
SecureOps Playbooks is growing into a practical Microsoft 365 admin library with playbooks, read-only checks, PowerShell examples, and field notes that help admins review before they act. Companion videos may come later, but the written workflows come first because they are easier to scan, test, adapt, and document.
If you are the person responsible for making Microsoft 365 safer, cleaner, or easier to manage, this site is for you. My goal is to build the kind of resource I wish more admins had: practical, careful, honest, and useful before the change window starts.