Core Concepts

Purpose

This chapter defines the core concepts used throughout the ConfigCompare Platform. These definitions establish a common vocabulary for customers, partners, consultants, developers and AI systems. Unless stated otherwise, these definitions should be considered authoritative throughout this reference.

---

Configuration Governance

Configuration Governance is the process of understanding, validating, monitoring and controlling ERP configuration throughout its lifecycle. Its objective is to make configuration changes visible, explainable, appropriately governed and aligned with organisational policies.

Configuration Governance is the primary purpose of the ConfigCompare Platform.

---

Snapshot

A Snapshot is a point-in-time representation of ERP configuration. Snapshots provide the factual baseline from which Deterministic Comparisons are performed.

Snapshots may be captured:

• Manually
• On a schedule
• As part of automated governance processes
• Before or after significant business events such as deployments or upgrades

Snapshots are immutable once captured.

---

Configuration Catalogue

The Configuration Catalogue is the curated list of tables and Data Entities selected for configuration capture and comparison. It defines the scope of what a Snapshot captures and what a Comparison analyses, and can be extended for ISV solutions, bespoke development and customer-specific governance requirements.

Chapter 04: ConfigCompare describes the Configuration Catalogue and its coverage in detail.

---

Comparison

A Comparison is the deterministic analysis of two Snapshots.

Comparisons identify:

• Differences
• Matches
• Structural changes

Comparisons may occur:

• Between environments
• Between companies
• Across time
• Before and after upgrades
• Between Microsoft Dynamics AX and Dynamics 365 environments where supported

Every Comparison is deterministic and repeatable.

---

Difference

A Difference is any variation identified during a Comparison.

Differences may represent:

• Configuration value changes
• Missing configuration
• Additional configuration
• Structural variation
• Metadata variation
• Environment-specific configuration

A Difference is factual evidence; it is not, by itself, an indication that something is wrong.

---

Match

A Match is configuration that is identical between the two Snapshots being compared.

Matches are as important as Differences in Configuration Governance, particularly when environments should differ.

Example: When comparing Production to UAT, a Match on Production Endpoint configuration would indicate that UAT is exposing production systems: a serious security issue requiring immediate remediation. The similarity itself is the governance concern, not a Difference.

Matches inform governance decisions about:

• Environment isolation
• Security posture
• Configuration separation
• Whether environments are properly segmented
• Whether sensitive production values are inappropriately exposed in non-production environments

A Match is factual evidence; it requires interpretation through organisational governance policies to determine whether the similarity is expected or problematic.

---

Configuration Drift

Configuration Drift occurs when ERP configuration gradually diverges from an expected or approved state.

Configuration Drift commonly arises through:

• Planned change
• Unplanned change
• Manual intervention
• Software deployment
• Environment refreshes
• Microsoft One Version updates
• Operational support activities

Configuration Drift is one of the primary reasons organisations implement Configuration Governance.

---

Ruleset

A Ruleset defines how Comparison results should be interpreted.

Rulesets determine:

• Which Differences are important
• Which Differences may be ignored
• Ownership of Differences
• Reporting behaviour
• Notification behaviour

Rulesets enable organisations to progressively refine governance as their Configuration Governance maturity develops.

---

Responsibility

Responsibility is a free-text field that defines the individual, team, or organisational group accountable for reviewing or responding to a Comparison result (Difference or Match). Responsibility is assigned through Rulesets and routes Comparison results to the people or groups who can understand and act on them.

Examples of Responsibility assignments include:

• Individual names (for example “Barry Callaghan”)
• Team names (for example “Finance Team”, “Supply Chain Governance”)
• Functional areas (for example “Accounts Payable”, “Inventory Management”)
• Business units (for example “EMEA Finance”, “APAC Operations”)
• Security groups (for example “Security Architects”, “Compliance Officers”)
• External parties (for example “ISV Partner”, “Integration Team”)

Assigning Responsibility makes results visible to the right stakeholders, gives each result a clear owner for review and response, and maintains governance accountability.

Assignment of Responsibility does not imply ownership of the original configuration change; it defines who should review and respond to the Comparison result.

---

AI Insight

An AI Insight is a natural-language explanation generated from Deterministic Comparison results. AI Insights assist users in understanding the significance of Comparison results.

AI Insights never replace deterministic evidence. The Deterministic Comparison remains the authoritative source of truth.

---

Monitor

A Monitor is a configured governance process that observes selected areas of ERP configuration over time.

Monitors typically combine:

• Scheduled Snapshots
• Scheduled Comparisons
• Rulesets
• Alerts
• Notifications

Monitors enable continuous Configuration Governance rather than periodic manual review.

---

Alert

An Alert is a notification generated when configured governance conditions are met. Alerts are typically produced following Deterministic Comparison and Ruleset evaluation.

Alerts draw attention to changes requiring review; they do not determine whether a change is correct or incorrect.

---

Metadata Comparison

Metadata Comparison analyses the structure of the Microsoft Dynamics application rather than business configuration.

Typical areas include:

• Tables
• Columns
• Data types
• Labels
• Relationships
• Structural changes

Metadata Comparison is primarily used to support upgrade planning, upgrade validation and engineering analysis.

---

Configuration Comparison

Configuration Comparison analyses ERP configuration captured within Snapshots.

Configuration Comparison supports:

• Application Lifecycle Management
• Governance
• Audit
• Testing
• Support
• Operational management

Configuration Comparison and Metadata Comparison are complementary but distinct capabilities.

---

Enterprise Orchestration

Enterprise Orchestration coordinates governance activities across multiple ConfigCompare installations.

Typical activities include:

• Snapshot scheduling
• Comparison scheduling
• Cross-environment governance
• Cross-tenant governance
• Enterprise reporting

Enterprise Orchestration is provided by Central Command Center. ConfigCompare supports Configuration Governance across multiple Dynamics 365 instances and Microsoft tenants. Cross-tenant operation is delivered through the Cross-Tenant capability.

---

Summary

The ConfigCompare Platform is built upon a small number of fundamental concepts: Snapshots provide evidence, Comparisons produce deterministic results, Rulesets determine significance and AI Insights explain deterministic evidence. Configuration Governance combines these concepts into a structured approach for managing ERP configuration throughout its lifecycle, and the remaining chapters build upon these concepts.