For Microsoft Dynamics partners
Turn configuration governance into a repeatable service.
Move beyond reactive support with structured services for drift, releases, upgrades, compliance and operational investigation.
The opportunity
Make governance part of the service-not an emergency response.
ConfigCompare gives delivery, support and managed-service teams a consistent evidence model across customer environments and lifecycle stages.
Find drift before it becomes an incident.
Turn deterministic evidence into focused advice.
Build a governed service customers can rely on.
Four service foundations
From delivery assurance to ongoing governance.
Each service uses the same Snapshot and Deterministic Comparison foundation, applied to a different customer objective.
- 01Proactive visibility
Drift-as-a-Service
Monitor configuration Differences over time and provide focused analysis, commentary and recommended action.
- 02Safer releases
Release governance
Validate whether configuration moved correctly through DEV, TEST, UAT, GOLD and PROD.
- 03Faster investigation
Support triage
Use same-environment-over-time and environment-to-environment comparison to establish whether Configuration Drift may explain an incident.
- 04Controlled updates
Upgrade assurance
Use pre- and post-upgrade Snapshots, configuration comparison and metadata analysis to reduce uncertainty.
Expand the managed-service portfolio
One evidence model supports more than four services.
Partners can combine recurring monitoring with project-scoped governance for implementation, audit, rollout and hypercare requirements.
- Configuration compliance
- Audit evidence preparation
- Golden template governance
- Hypercare monitoring
- Multi-company rollout governance
Worked example
Upgrade commentary you can read before you sell it.
AXImprove publishes curated commentary on Dynamics 365 F&SCM releases openly. Each one is produced by running upgrade analysis against a Contoso reference environment, then cross-referencing the deterministic structural findings against Microsoft's published release documentation.
Schema change, mapped to announcements
What technically changed in the schema, set against what Microsoft functionally announced.
Undocumented findings, called out
Data initialisation classifications and findings with no published documentation are stated explicitly rather than left implicit.
A reference, not a prediction
The analysis runs against Contoso. A customer's own environment carries a different profile, which is exactly where a partner engagement starts.
Repeatable for your customers
Partners can deliver the same style of curated commentary against customer-specific environments as part of upgrade assurance engagements.
Build the service
Add proactive governance to your Dynamics offer.
Explore the customer estates, delivery stages and managed-service models where ConfigCompare can create repeatable value.
Arrange a partner demo