Dynamics 365 Finance & Operations DMF Telemetry Reaches GA in Azure Application Insights

Microsoft has officially marked roadmap item 576817 as launched, bringing Data Management Framework (DMF) telemetry integration with Azure Monitor Application Insights to General Availability. Categorized under Microsoft Dataverse's finance and operations cross-application integration track, the capability rolled out in public preview on April 6, 2026, and reached General Availability on June 8, 2026.

Rather than altering how data imports or exports execute, this update gives administrators, makers, and analysts a direct telemetry pipeline from Dynamics 365 finance and operations apps into their own Azure Application Insights instances.

Why DMF Observability Matters in Cross-Application Architecture​

To understand why this update appears under the Microsoft Dataverse roadmap banner, it helps to look at how Microsoft connects its enterprise business applications. According to Microsoft Learn documentation on Power Platform data integration, finance and operations apps rely on the Data Management Framework to manage data entities and data entity packages, pulling and pushing high-volume data across systems. While Dataverse-based apps use OData APIs and parallelism, the DMF remains the heavy-lifting engine on the finance and operations side.

Historically, administrators already had options to stream standard model-driven app and Dataverse database telemetry to Application Insights for performance and error diagnostics. However, deep operational visibility into finance and operations DMF executions required digging through internal execution histories or staging logs inside the finance and operations client. By streaming DMF telemetry directly into Azure Application Insights, teams can correlate data movement health alongside their broader Power Platform and Azure observability stacks.

Section Summary:

• Feature Scope: Streams Dynamics 365 finance and operations DMF import and export telemetry directly to a customer-owned Azure Application Insights instance.
• Release Timeline: Entered public preview on April 6, 2026, reached General Availability on June 8, 2026, and is now marked as launched on the Microsoft 365 roadmap.
• Target Audience: Must be enabled or configured by administrators, makers, or business analysts for their environments.

Supported Versions, Builds, and Feature Flights​

Before hunting for DMF logs in Azure, administrators need to verify that their finance and operations environments meet the minimum platform update (PU) and build requirements. According to Microsoft Learn's available telemetry documentation for Dynamics 365 Finance and Supply Chain Management, DMF telemetry is supported in the following releases:

Under the hood, Microsoft controls this capability through two specific feature flights:

• DMFTelemetryConfigurationFlight
• DMFEnableAppInsightsLogsAndErrors

Microsoft's documentation notes that both flights are enabled by default in supported builds. When those flights are active, the new DMF telemetry signals appear under the Configure tab within the environment's monitoring setup. If you are running a supported build and do not see the options available, Microsoft advises contacting support to verify that the flights are active on your environment.

Section Summary:

• Requires at least PU69 (10.0.45), PU70 (10.0.46), or PU71 (10.0.47) at their respective minimum build thresholds.
• Controlled by DMFTelemetryConfigurationFlight and DMFEnableAppInsightsLogsAndErrors, which are enabled by default.

What Gets Logged: Signals and Error Tables​

Once configured with an active Azure Application Insights instance, the integration tracks the lifecycle of import and export jobs across three primary telemetry signals:

1. DMFJob Start: Records the exact timestamp when a DMF import or export job begins execution.
2. DMFJob End: Records the timestamp when the DMF job finishes.
3. DMFJob Status: Tracks stage-by-stage progression as data moves from source to staging tables and from staging to target tables.

Where to Find Failure Data in Application Insights​

One of the most practical details in Microsoft's telemetry documentation is how DMF separates standard framework errors from deeper platform exceptions. When troubleshooting a broken integration pipeline, querying the right table in Application Insights saves valuable time:

• Custom Events Table (customEvents): The Data Management Framework logs its granular DMF errors here, complete with associated error codes that map to Microsoft's documented data management error descriptions.
• Exceptions Table (exceptions): If a failure during a data job bubbles up to the underlying X++ application layer, the platform captures and logs it in the exceptions table instead.

In real-world troubleshooting, this distinction is critical. Does a nightly vendor invoice import fail because of malformed source CSV formatting, or did custom X++ business logic throw an unhandled null reference during target table insertion? By separating DMFJob Status transitions, DMF Custom Events error codes, and X++ Exceptions, operations teams can quickly isolate whether a failure belongs to the data integration team or the X++ development team.

Section Summary:

• Job timing and staging-to-target transitions are tracked via DMFJob Start, DMFJob End, and DMFJob Status.
• Granular DMF errors with error codes are written to the Application Insights Custom Events table, while errors that surface in the X++ layer are written to the Exceptions table.

Practical Analysis: What It Does—and What You Still Need to Build​

From an enterprise IT perspective, bringing DMF telemetry into the same Azure Monitor ecosystem that already tracks X++ exceptions, form load times, warehouse operations, and batch job throttling is a welcome step toward unified observability. Instead of treating finance and operations data imports as an isolated black box, administrators can build proactive alerts in Azure Monitor—for example, triggering a notification if a critical DMFJob Start event is not followed by a DMFJob End event within an expected maintenance window, or if specific error codes spike in the Custom Events table. Microsoft's documentation also points to a DMF Monitoring Dashboard resource alongside its existing plug-and-play dashboards for forms, X++ errors, and batch monitoring.

That said, administrators should keep a grounded view of what this integration entails:

• Customer-Managed Infrastructure: The telemetry streams into your organization's Azure Application Insights instance. While enabling the telemetry feed itself requires no custom code, organizations remain responsible for configuring their Application Insights connection and managing their own Azure Monitor data ingestion and retention settings.
• Observability, Not Auto-Remediation: Streaming granular failure messages and staging statuses to Azure Monitor accelerates root-cause analysis and dashboarding, but it does not change how DMF processes packages or automatically retry failed staging-to-target writes.

For teams managing hybrid Dataverse and Dynamics 365 finance and operations landscapes, verify your environment build numbers against the PU69–PU71 thresholds, check the Configure tab for the new DMFJob signals, and update your Application Insights queries to watch both the Custom Events and Exceptions tables during your next major data migration or integration run.