Plan a change and read its receipt
Stage the exact change, pass safety checks, get scoped approval, run it after Microsoft setup, and read the receipt state.
TenantVigil only reads your Microsoft 365 tenant. It never changes a setting: you apply each fix yourself.
Need a hands-on starting point?
Start with one tenant or talk to the team if you want help evaluating fit, permissions, or rollout approach.
Build the exact plan
Stage the exact operation and target before approval. A plan names the customer, the action and the object it changes.
TenantVigil runs preflight safety checks against the plan. A change that is not in the supported list, or a body that does not match the allowed shape, is refused before it is sent.
Get scoped approval
A supported change needs scoped approval from an authorized customer decision maker. For many native changes, an independent partner admin also approves.
Approval is for that exact plan. Editing the plan invalidates the approval.
Run it after Microsoft setup
Before a native change can run, its Microsoft permission must be granted and its callback URI registered for the customer. The customer may also need to re-consent for a newly added permission.
The current default for approved fixes is stated at the top of this page. Even when fixes are on, a change still needs the plan, approval and Microsoft setup.
Read the receipt
A receipt records what was attempted and what Microsoft returned. The exact state is per operation, not a blanket promise.
The common states are Ready, not sent; Applied, not verified; Verified in Microsoft; and Outcome unknown; check before retrying.
Not every path reaches verified. An unclear outcome is never resent automatically. A change with no clean undo says so on its receipt.
Manual Exchange work
These Exchange changes have no supported Microsoft API, so they stay manual: mail forwarding, FullAccess, SendAs, distribution-list membership and an unsupported organisation setting.
A technician makes them in Microsoft 365 or PowerShell, then reports back. A resolved request does not prove a later scan verified the change.
Next action
Review desired state and drift, or read the full supported-changes reference.
- Review desired state and drift
- Supported changes and manual work