Dynamics 365 Finance and Supply Chain Management spans 24+ modules with thousands of parameters spread across them. When multiple legal entities are involved, the effort required to maintain consistency and detect parameter drift multiplies quickly.
ConfigWatch automatically monitors parameter-table changes across the application and every legal entity, then streams a structured change feed to Azure Application Insights - helping platform engineering and application management teams detect changes before a single unnoticed parameter disrupts live operations.
Capture the complete parameter-change landscape, then analyse it using familiar Azure observability tools.
Dynamics 365 configuration changes
All parameter tables across the application
ConfigWatch telemetry service
Structured event, user, timestamp and before/after context
Azure Application Insights
Centralised, queryable telemetry outside the F&O database
Core capabilities
Turn parameter-table changes into structured, searchable telemetry that platform engineering, infrastructure, application management, support and governance teams can use across every legal entity.
Capture the previous and new values for monitored fields so teams can quickly understand exactly what changed.
Record who made the change, when it occurred and the relevant legal entity or organisational context.
Monitor parameter tables across the application and all legal entities by default, with no manual table selection required.
Search and correlate change events using Kusto Query Language across users, environments, tables and time periods.
Build operational dashboards, scheduled summaries and proactive alerts for high-risk or unexpected changes.
Add an intelligent layer that can summarise changes, identify patterns and support root-cause investigations.
The traditional challenge
Thousands of settings across 24+ modules
Critical operational behaviour is distributed across a broad configuration landscape that is difficult to review manually.
Multi-entity complexity multiplies quickly
Each legal entity adds another configuration footprint to compare, maintain and investigate.
A single drift can disrupt live operations
Unnoticed parameter changes can affect posting, planning, inventory, fulfilment and other business-critical processes.
Database logging adds more overhead
Teams must configure logging, manage storage growth and rely on cumbersome reporting to investigate changes.
Built for target users
ConfigWatch gives platform engineering, infrastructure and application support teams a seamless way to monitor system configuration changes across the live Dynamics 365 environment - without configuring database logging, consuming additional transactional storage or running cumbersome reports.
Lower application-database footprint
Change telemetry is sent to Application Insights rather than retained as broad database-log data in F&O.
Better operational visibility
Use dashboards, saved queries and alerts tailored to platform engineering, infrastructure, support, security and release-management teams.
Flexible analytics foundation
Correlate configuration changes with deployments, incidents, performance signals or support tickets.
Extensible for AI and automation
Expose curated telemetry to copilots or agents that can explain recent changes and highlight unusual activity.
Capacity-aware by design
As enterprise data platforms increasingly use capacity-based commercial models, retaining high-volume audit data in transactional stores can create avoidable pressure. ConfigWatch captures the full parameter-change landscape by default and lets customers manage retention and analysis in the Azure observability layer.
Solution architecture
ConfigWatch keeps capture close to Dynamics 365 while moving analysis and retention to the Azure observability layer.
Users update parameter records through normal application processes across any legal entity.
A purpose-built extension automatically creates structured events for parameter-table changes and sends them as telemetry.
Application Insights stores and exposes the feed for KQL queries, dashboards, alerts and intelligent analysis.
The exact telemetry scope, retention period, redaction rules and alerting model can be aligned to each customer's governance and compliance requirements.
Approach comparison
ConfigWatch complements a broader audit strategy by offering a focused, analytics-ready option for complete parameter-table change visibility.
| Consideration |
ConfigWatch — Application Insights |
Standard database log | Custom export / integration |
|---|---|---|---|
| Primary design | check_circlePurpose-built All parameter-table changes emitted as structured telemetry. |
△ Generic Database-level logging configured across chosen tables and fields. |
△ Custom Data extracted or copied through bespoke interfaces and storage. |
| Storage location | Azure Application Insights / Log Analytics, outside the core F&O transactional database. | Application database records that must be retained, reviewed and managed. | Customer-designed staging database, lake, integration platform or data store. |
| Database-capacity impact | check_circleReduced Avoids using broad database-log storage for the monitored feed. |
Potentially higher - volume can grow significantly depending on scope and activity. | Moves capacity elsewhere but introduces separate storage and integration costs. |
| Setup and maintenance | Focused product configuration and a consistent event model. | Can become cumbersome when many tables, fields and retention needs are involved. | Requires API, export, transformation, schema and support ownership. |
| Analytics experience | check_circleNative KQL Search, correlate, aggregate, alert and visualise using Azure tools. |
Typically relies on application navigation or purpose-built operational reports. | Depends entirely on the custom platform and reporting implementation. |
| Near-real-time monitoring | Designed for rapid telemetry availability and alerting. | Records are available in the application, but proactive monitoring requires additional work. | Depends on integration frequency, latency and failure handling. |
| Agentic extension | Well suited to summarisation, anomaly detection and natural-language investigation over curated events. | Possible, but raw database-log records generally need extraction and shaping first. | Possible after designing a trusted, searchable data model. |
| Best fit | Complete monitoring of parameter-table changes across the application and all legal entities using modern Azure observability. | Broad in-application audit requirements where standard database logging is mandated or sufficient. | Specialised cross-system audit platforms with dedicated integration investment. |
Key advantage: ConfigWatch captures the full parameter-change landscape by default and lets customers manage retention and analysis in the Azure observability layer, reducing pressure on capacity-based transactional storage.
KQL-powered analysis
Once the feed is in Application Insights, authorised users can build their own KQL queries, workbooks and dashboards - or use the telemetry as grounding for an agentic experience.
Find all changes before an incident
Filter by environment, company, table, user and time range.
Detect unusual behaviour
Highlight out-of-hours changes, repeated reversals or high-risk parameter updates.
Build executive and operational views
Create dashboards for change volume, hotspots, top users and impacted modules.
customEvents | where name == "F&O Configuration Change" | extend Table = tostring(customDimensions.TableName), ChangedBy = tostring(customDimensions.UserId), OldValue = tostring(customDimensions.OldValue), NewValue = tostring(customDimensions.NewValue) | where timestamp > ago(7d) | summarize Changes = count() by Table, ChangedBy, bin(timestamp, 1d) | order by Changes desc
"What changed before yesterday's posting issue?"
Investigate recent relevant parameter changes.
"Summarise high-risk changes this week."
Generate a concise governance briefing.
"Alert when this parameter changes."
Turn monitoring logic into proactive action.
Business outcomes
A modern monitoring foundation for platform engineering, infrastructure, support, audit, security, release and application-management teams.
Complete
Capture all parameter-table changes across every legal entity.
Searchable
Query change history with KQL across time and context.
Scalable
Use Azure telemetry retention rather than broad transactional logging.
Extensible
Add dashboards, alerts, automation and agentic analysis.
Powered by Microsoft
ConfigWatch stays close to standard Dynamics 365 and Azure services, helping simplify security, support, retention and day-to-day operations.
See how ConfigWatch can provide a complete view of parameter changes, reduce database-log dependency and create an analytics-ready audit feed.