Copy the whole database
To move one change, an outage is scheduled and everything is copied, all or nothing: test data, half-finished work and the single setting you actually wanted.
The result: disruption, delayed improvements and unnecessary risk.
A manifesto for configuration governanceWarden · For Dynamics 365 Finance and Supply Chain Management
Good governanceshould notdependon memory.
- 01Capture
- 02Compare
- 03Review and decide
- 04Authorise
- 05Deploy
- 06Monitor
Every Dynamics 365 programme ends with a configuration that was designed, tested and signed off. Then the project closes, the consultants leave, and the record of what was agreed moves into spreadsheets, mailboxes and one person’s head. Warden keeps that configuration visible, accountable and recoverable — inside the environment you already run.
/001The driftWarden · Configuration governance
Nothing breaks.It drifts.
Nobody decides to abandon the signed-off configuration. It moves one urgent fix at a time, through three habits every live ERP has.
Hand-carry a package
A data package is exported, e-mailed and imported. There is no preview of what it will overwrite, no record of who approved it and nothing to stop the wrong one.
The result: a silent overwrite and an incident that takes days to trace.
Spreadsheets and memory
The spreadsheet becomes the unofficial source of truth and is out of date the moment it is saved. Whatever it misses lives in one consultant’s memory.
The result: every audit starts with detective work.
The takeaway
You wrote the rules. Nothing is enforcing them.
/002Five principles of configuration governanceWarden · Configuration governance
Fiveprinciples.
Each one is a sentence you could print on a wall. Each one is enforced by a Warden capability that is live today.
- 01
Know what changed.
A difference is only a problem once you can see it. Compare any two environments at setting level, and check production against the configuration you signed off.
Enforced byCompareBaseline
- 02
Nothing moves unapproved.
The person who requests a change never approves it. Nothing is written until a second person has said yes, and the exact approved scope is retained.
Enforced bySeparation of duties
- 03
Every change has a name and a time.
Requester, approver and timestamp on every change. The next audit is a lookup, not an investigation.
Enforced byAccountable history
- 04
Always a way back.
A recovery point is created before anything is written. Restoring an approved value is a controlled, approved action, not a scramble.
Enforced byRecovery point
- 05
Watch when nobody is.
Scheduled checks run against the baseline without anyone remembering to run them. The responsible people hear about drift before users feel it.
Enforced byScheduled drift checks
/003One alertWarden · Configuration governance
One alert.A clear decision.
When production moves away from its baseline, Warden opens a drift alert inside Dynamics 365: the baseline value beside the live value, who changed it and when (from F&O database logging) — and the restore waits for an approver before anything is written.
1 modified0 missing0 added
Customer groups1
| Status | Key | Snapshot value | Environment value | ||
|---|---|---|---|---|---|
| Modified | 30Modified by Jamie Oliver on 13/10/2026, 09:14:02 | Terms of payment: Net30 | Terms of payment: Net10 |
/004AdoptionWarden · Success by adoption
Governance people will use.
A governance framework that lives in a document is a promise. One that lives in the system is a control. Warden puts the control cycle inside Dynamics 365, in the screens your application team already open — nothing to host, nothing to remember, nothing to chase.
That is how Warden measures every engagement: not by what was delivered, but by what people keep using. Success by adoption.
- Finance director
Posting rules stay as signed off, with an audit-ready approval trail.
- IT manager
Move configuration in working hours, with a clear route back.
- ERP programme owner
Governance that operates in the system, not just in a document.
- Application team
See drift, owner and timing before business users do.
/005Book a walkthroughWarden · Configuration governance
Adoptionthat works.
A 45-minute walkthrough on your own environments, legal entities and scenarios. Bring the setting that worries you most; we will show you what Warden knows about it.