What TenantWard automates
- Employee onboarding and offboarding runbooks in Microsoft 365
- MFA resets, session revocation and sign-in blocks
- SPF, DKIM and DMARC records pushed to Cloudflare, GoDaddy, Route 53 or Azure DNS
- Daily DNS snapshots with alerts when MX, NS or email records change
- Weekly rechecks of every domain and connected Microsoft 365
- Locking the account when an account looks hijacked
- A day-after check-in on careful and disruptive changes, and a weekly summary email
Guardrails on every automated change
- 1
Plan
What will change, who's affected, what might stop working and how to undo it, in plain words.
- 2
Back up
The current settings are saved first. If the backup fails, nothing runs.
- 3
Apply and verify
The change runs from a fixed, tested script, then TenantWard reads the setting back to confirm it took.
- 4
Record and follow up
Who approved it and when goes into the change history. A day after a careful or disruptive change, you're asked whether everything still works.
- 5
Undo
One click restores the saved settings.
AI explains, people set the limits
TenantWard's built-in assistant explains issues and drafts reports; it never writes or runs a change. AI agents you connect can propose changes; they run only through the tested catalog, routine ones within limits you set, and everything else after a person approves with two-factor sign-in. Every automated action comes from the same catalog of tested scripts and runs only when a person, or a rule a person set, approves it.
Questions
- Can IT automation run without me?
- Some of it, by your choice. Rechecks, monitoring and DNS snapshots run on their own. Locking a hijacked account can run automatically within limits you set. Other changes to people and settings wait for approval, unless your change policy or autopilot settings let them run.
See where your company stands
Check a domain for free. A free account also connects Microsoft 365 or Google Workspace read-only and shows every issue it finds; a plan shows who's affected and fixes it.