For MSPs maintaining Microsoft 365 procedures
Microsoft 365 changed, and now your admin SOP is wrong.
Microsoft renames a blade, relocates a setting in the admin center, or flips a security default, and the runbook your technicians follow no longer matches the screen. No alert fires. The document still looks finished. A tech finds out the hard way, mid-task, in front of a client.
The problem
M365 moves on its own schedule. Your documentation doesn't.
If you run an MSP, your Microsoft 365 admin procedures are some of your most-used and most-fragile documents. They describe menus, blade names, and policy screens that Microsoft revises constantly. Here are the kinds of changes that silently break them.
"Azure Active Directory" became "Microsoft Entra ID"
Every SOP that tells a tech to open Azure AD, reset MFA there, or manage a user's sign-in methods now points at a name and a menu path that no longer exist in the portal.
Settings move between the M365, Exchange, and Entra portals
Mailbox, licensing, and security controls migrate between admin.microsoft.com, the Exchange admin center, and the Entra portal. A runbook screenshot of the old location sends a technician to a dead end.
MFA and Conditional Access defaults shift
Microsoft's push toward mandatory MFA and per-user MFA deprecation changes where and how you enforce sign-in policy. An offboarding or new-user SOP that assumes the old toggle is now inaccurate.
A confirmation step gets added or reordered
Deleting or converting a mailbox, or transferring a user's data, gains a new required prompt. Your step 5 is now step 5 and 6, and the tech skips the part that isn't written down.
How ProcedurePulse helps
Point it at your M365 procedures. Read one report a week.
You connect the SOPs your team relies on and name the Microsoft 365 sources each one depends on. ProcedurePulse watches those sources, and when something changes, its weekly report gives you four things for every affected procedure.
Affected SOP
The specific M365 procedure the change touches, named, not a list of "pages that changed."
Exact outdated step
The line, menu path, or screenshot inside that SOP that no longer matches the live portal.
Evidence
What changed at the source, quoted, so a technician can confirm it in seconds.
Proposed revision
A suggested edit to the step, ready for a human to approve or adjust before it lands.
Why it beats the alternatives
Your docs tool stores the SOP. A diff tool watches a URL. Neither says "your MFA reset runbook is wrong."
Compared with Hudu, IT Glue, Notion, and Word
They hold your Microsoft 365 procedures well, but they assume the words stay true. They have no idea when Entra was renamed or a blade moved.
ProcedurePulse watches the M365 surfaces your SOPs describe and tells you which stored procedure is now inaccurate.
Compared with generic page-change monitors
A page-diff tool tells you a Microsoft docs URL changed. You still have to decide whether it matters and which of your runbooks it breaks.
ProcedurePulse maps the change back to the exact procedure and step, so you get a fix to review, not a diff to investigate.
FAQ
Microsoft 365 SOP drift, answered.
Why do our Microsoft 365 SOPs keep going out of date?
Microsoft ships changes to the M365 admin center, Entra, and security policies on a schedule you do not control. Blades get renamed, settings move, and defaults change. Your written steps stay frozen while the product moves, so the doc still looks finished even though the screen no longer matches.
Does ProcedurePulse edit our documentation automatically?
No. It sends a weekly report naming the affected SOP, the exact outdated step, the evidence from the source, and a proposed revision. A human on your team approves or adjusts the change before it lands.
How is this different from a page-change monitor?
A page-diff tool tells you a URL changed. ProcedurePulse maps that change back to the specific runbook and step it breaks, so you review a fix instead of investigating a diff.
Early access
Stop finding out about M365 changes mid-ticket.
Leave your work email and we'll reach out as we bring teams on. We build the initial monitoring around what early users actually document.
Prefer email? Write to [email protected].