Close the loop — without leaving the console
When a finding warrants action, you don't jump into a separate admin portal and hope you undid it correctly. You propose the action, review a read-only preview, approve it, and execute — all inside SBCMSP. The M365 action runs server-side, with no endpoint agent to deploy.
Propose & preview
Proposing an action runs a read-only preview first — it resolves the exact target, runs per-action safety checks, and captures the before-state for rollback. Nothing is changed at this step, and an action that fails preview never gets created.
Approve, then execute
A separate, audited approval by an owner or admin is required before anything can run. Execution only proceeds from an approved action — never straight from a proposal — so a human is always the last step before a change.
Verify & reverse
After a change, the engine re-reads the provider to confirm it actually took effect. Every reversible action carries a rollback reference — one call restores the prior state and re-verifies it, so a wrong call is never a dead end.