Chapter 04 · ConfigCompare

Technical reference · Chapter 04

ConfigCompare

Purpose

This chapter introduces ConfigCompare, the core product within the ConfigCompare Platform.

ConfigCompare provides Deterministic Comparison of ERP configuration and forms the factual foundation upon which the platform’s Configuration Governance capabilities are built.

Subsequent chapters describe the individual concepts and capabilities that together make up ConfigCompare.

This chapter describes concepts and behaviour; step-by-step operating guidance sits outside this reference.

Overview

ConfigCompare is a Configuration Governance Platform for Microsoft Dynamics 365 Finance & Supply Chain Management.

Its purpose is to help organisations understand, validate, monitor and govern ERP configuration throughout the application lifecycle.

Rather than relying on assumptions or manual investigation, ConfigCompare produces deterministic evidence describing how ERP configuration differs between environments, companies and points in time.

Every other capability within the platform builds upon this deterministic foundation.

What ConfigCompare does

ConfigCompare enables organisations to:

Capture ERP configuration as Snapshots from Tables and Data Entities.
Compare Snapshots deterministically across preselected configuration areas.
Identify Differences and Matches.
Detect Configuration Drift.
Support Application Lifecycle Management.
Support Governance & Audit.
Accelerate Testing and Support.
Assist Microsoft One Version upgrades with configuration and metadata analysis.
Generate AI-assisted explanations of Deterministic Comparison results.
Coordinate governance activities across enterprise environments.

Configuration scope

Microsoft Dynamics 365 Finance & Supply Chain Management contains approximately 14,000 tables.

ConfigCompare does not require customers to identify every relevant configuration table manually before it can provide value.

Instead, ConfigCompare provides a human-curated starter catalogue focused on configuration-relevant areas. This catalogue is maintained by D365 F&SCM version and currently includes approximately:

1,930 configuration tables.
200 Data Entities.

The catalogue is curated rather than generated: it is assembled by people who know which tables carry configuration decisions, so a comparison returns the configuration that matters rather than every table in the system. It can be loaded in full or by module, allowing teams to establish a meaningful configuration baseline quickly while still controlling the scope of capture and comparison.

The catalogue is not fixed. It can be extended to support ISV solutions, bespoke development, customer-specific configuration areas, and additional governance requirements.

Scope can also be widened beyond typical configuration areas (including master-data-style tables) where governance requires it. Two considerations govern how wide to go: capture and comparison cost grows with table size, and a tracked area is only worth tracking if someone will review its Differences. Data no one would review is transactional or document data and should not be in scope. Chapter 12: ConfigAudit applies the same test to event-level audit coverage.

Time to first value

A complete Configuration Governance rollout may include detailed Rulesets, Responsibility assignment, ConfigTrack workflows, approval processes, alerts, and operational reporting.

Those activities can require deeper implementation effort.

However, ConfigCompare is designed to provide value before the full governance model is complete.

After installing the deployable package and applying the licence, customers can load the curated configuration catalogue and begin capturing meaningful configuration evidence in around 15 minutes. This timing is based on the curated catalogue and a standard deployment; actual effort depends on the selected scope and the environment.

This allows teams to gain early visibility of configured areas, capture initial Snapshots, and begin comparing environments, companies, or points in time quickly.

Rulesets, ConfigTrack workflows, and more advanced governance controls can then be introduced progressively.

Base setup requirements

Base ConfigCompare setup requires a small number of core configuration items.

These include:

Install and licence: ConfigCompare is installed and licensed through a deployable package using the standard D365 F&SCM deployment method.
Environment name: The environment is named so that captured Snapshots and Comparisons can be identified clearly.
Modules and tables: The configuration scope is defined through the curated catalogue, manual entry, the form helper, or a combination of these methods.
Azure Storage: At least one Azure Storage Account is required to store and organise ConfigCompare artefacts.

Organisations may use a single Azure Storage Account or multiple Azure Storage Accounts depending on how they want to separate, file, retain, and manage configuration evidence across environments, tenants, customers, or governance scenarios.

The setup effort for these base requirements is separate from deeper governance design.

Rulesets, Responsibility assignment, ConfigTrack workflows, alerts, and operational reporting can be introduced progressively after the base setup is in place.

Extending configuration coverage

To support ISV solutions and bespoke development, ConfigCompare makes it easy to add tables to the configuration scope.

A helper is available from every D365 F&SCM form to surface the tables used as data sources by the current form.

Users can select relevant tables, assign module context, describe the purpose of the table, and save the result into the configuration tables parameter list.

This reduces the dependency on manual table discovery and helps implementation teams extend the curated catalogue with customer-specific configuration areas.

Extending coverage applies to new tables and entities only. Custom fields added by extension to a table already within the configuration scope are captured automatically; no separate registration is required for extension fields.

Deterministic Comparison

Deterministic Comparison is the core capability of ConfigCompare.

Given the same two Snapshots, ConfigCompare will always produce the same Comparison result.

This provides organisations with repeatable, evidence-based analysis that can be trusted throughout implementation, support, governance and audit activities.

Deterministic Comparison is separated from interpretation.

ConfigCompare identifies factual Differences and Matches.

Matches are as important as Differences when environments should differ but do not; for example, when production endpoints remain in a downstream environment such as UAT after a database restore.

Users, organisational processes and AI-assisted capabilities determine how those Differences and Matches should be understood and acted upon.

Supported comparison scenarios

ConfigCompare supports comparison:

Between environments (Environment to Environment).
Between legal entities (Company to Company).
Between many legal entities and a single reference company (N:1).
Across time (Historical Comparison).
Before and after upgrades.

Each comparison scenario is described in detail in Chapter 07: Comparison Types.

Upgrade Analysis is described separately (Chapter 16) because it analyses both ERP configuration and application metadata.

Business outcomes

Organisations typically adopt ConfigCompare to achieve one or more business outcomes.

Examples include:

Establishing early visibility of configured ERP areas.
Reducing deployment risk.
Reducing deployment costs through faster, more complete validation cycles.
Maintaining consistent configuration.
Detecting Configuration Drift.
Improving audit readiness.
Accelerating support investigations and reducing incident costs.
Simplifying Microsoft One Version updates and reducing upgrade risk.
Supporting ERP modernisation.
Improving confidence in ERP configuration.
Helping functional, technical, support, audit, and partner teams work from the same deterministic evidence.
Preventing costly configuration errors before they reach production, avoiding configuration reversal as well as data cleanup and remediation (for example, inventory revaluation if costing methods are incorrectly changed).

ROI drivers

Return on investment is typically realised by replacing manual investigation and spreadsheet-based validation with repeatable Snapshot capture and Deterministic Comparison.

Common ROI drivers include:

Reduced manual comparison effort.
Faster release and deployment validation.
Earlier detection of Configuration Drift.
Shorter support investigations.
Reduced risk of expensive production remediation.
Less effort preparing audit evidence.
Reusable governance rules that become more focused over time.
Better use of functional subject matter experts by routing results to the right responsible teams.

Relationship to the platform

ConfigCompare operates alongside the other platform components, each with a single clearly defined responsibility; the full component list is described in Chapter 01: The ConfigCompare Platform.

Design philosophy

ConfigCompare has been designed around several fundamental principles.

Deterministic evidence before interpretation.
Repeatable comparison.
Configuration Governance throughout the ERP lifecycle.
Separation of comparison from governance workflows.
Separation of deterministic analysis from AI-assisted explanation.
Enterprise scalability through modular platform capabilities.