Skip to content
Sentinel 1.5 | Preview

Streamline Dynamics 365 finance and operations apps integration

2026 Release Wave 1 · Financial Reporting

Microsoft source
Score 56/100 · MediumImpact MediumSwiss relevance LowPublic Preview

Dx365 Analysis

Our interpretation — not a Microsoft statement

What is changing?

Business performance planning will be able to use finance and operations data through the Business performance analytics data layer. Planning administrators can select relevant analytical tables, apply basic shaping rules, and load the resulting datasets into Dataverse for planning scenarios.

Current state today

Organizations using Business performance planning commonly prepare source data through separate Dataverse imports, Power Query or dataflow logic, file-based exchanges, or custom integration pipelines. Consultants must identify finance and operations entities, translate technical structures into planning dimensions and measures, and manage refresh and reconciliation logic. This can duplicate data-engineering work and create differences between operational balances, analytical data, and planning models.

Future state after release

For customers using both Business performance analytics and Business performance planning, the analytics layer is expected to become a more direct source for planning data. Administrators should be able to select available analytical tables and apply operations such as filtering or aggregation before loading data into Dataverse. This may reduce custom ingestion work, but model mapping, reconciliation, security, refresh design, and performance testing will still be required.

Why it matters

The feature could simplify the data supply chain for budgets, forecasts, and management planning. Its value depends on whether the supplied analytical structures match the customer’s legal-entity, chart-of-accounts, dimension, currency, and planning requirements. It should not be treated as a replacement for statutory financial reporting or as proof that all planning data will be current without validating refresh timing.

Who is affected?

Dynamics 365 Finance solution architectsFinance and financial reporting consultantsBusiness performance analytics administratorsBusiness performance planning administratorsFP&A and controlling teamsPower Platform and Dataverse specialistsData integration architectsSecurity and compliance administrators

Consultant impact — Medium

The capability is automatically exposed, but meaningful adoption requires design and validation rather than simple configuration. Projects using both planning and analytics should review table selection, dimension mappings, legal-entity scope, currency treatment, transformations, refresh schedules, Dataverse capacity, security, and balance reconciliation. Customers not using these products are unlikely to require immediate work.

Likely required work

  • Identify customers using or evaluating both Business performance analytics and Business performance planning.
  • Document existing planning-data interfaces and determine which custom imports or dataflows might become redundant.
  • Validate mappings for main accounts, financial dimensions, fiscal calendars, legal entities, currencies, scenarios, and versions.
  • Define reconciliation controls between Finance balances, the analytics layer, Dataverse, and planning outputs.
  • Review row-level access, legal-entity segregation, Dataverse permissions, and exposure of sensitive planning data.
  • Test transformation rules, refresh duration, data volumes, failure recovery, and Dataverse capacity consumption.
  • Update integration architecture, operating procedures, support documentation, and administrator training if the feature is adopted.
  • Avoid production redesign until preview limitations and a general availability timeline are clear.

Swiss relevance — Low

The integration can support planning and management reporting for Swiss organizations, but no Swiss localization, VAT, banking, ISO 20022, statutory reporting, or compliance capability is indicated. Any relevance is therefore generic rather than country-specific.

What should customers do now?

  • Track the September 2026 preview and confirm tenant, region, licensing, and prerequisite availability before planning a pilot.
  • Use a non-production environment to compare the new route with the current planning-data pipeline.
  • Build reconciliation tests covering CHF and foreign-currency balances, eliminations, dimension hierarchies, and fiscal-period cut-offs where applicable.
  • Retain existing interfaces until data completeness, refresh reliability, performance, and security have been demonstrated.
  • Treat the feature as an optional architecture improvement, not an automatic reason to change customers that have stable planning integrations.

Release Radar score — 56/100 (Medium priority)

The feature has meaningful relevance for FP&A and management reporting and could reduce integration effort, but its reach is limited to customers adopting both Business performance analytics and Business performance planning. It has no identified Swiss-specific functionality, remains at an upcoming preview stage, and has no published general availability date, which reduces urgency.

Assumptions, not Microsoft-confirmed facts

  • The release information does not define licensing, regional availability, prerequisites, supported table coverage, refresh frequency, or volume limits.
  • It is assumed that data selected from the analytics layer will be copied or materialized in Dataverse rather than queried live; this must be confirmed during preview.
  • The phrase 'automatically enabled' is interpreted as feature availability in eligible environments, not automatic creation of production-ready planning models or data loads.
  • No conclusion can yet be made about whether all Finance financial dimensions, custom fields, posting layers, consolidations, or historical transactions will be available.
  • The available information does not establish real-time processing; actual data currency will depend on analytics refresh and import schedules.
  • It is assumed that existing Business performance planning integrations will continue to operate during preview, but coexistence and migration behavior require confirmation.

Microsoft information

Quoted from the release plan

Business value

When you streamline access to Dynamics 365 Finance data with Business performance planning, you get the following benefits: - Boosted efficiency: Save time by reducing manual data entry so you can focus on the analysis that matters. - Improved accuracy: With direct integration, your planning uses the latest financial data you can trust. - Smooth experience: A unified platform delivers a consistent, user-friendly experience that makes your tools easier to use. - Real-time insights: Get up-to-date financial information that helps you make quick, informed decisions. - Cost cuts: Fewer systems lower maintenance and training costs. - Strategic edge: An integrated data approach gives you an advantage by helping you spot trends and opportunities first. This feature makes financial planning more efficient, accurate, and strategic, so you drive better business outcomes.

Feature details

The integration between Business performance planning and Business performance analytics enhances financial planning, forecasting, and operational efficiency by providing a seamless connection between Business performance planning and Dynamics 365 finance and operations apps. With this feature, you can leverage analytical tables built by Business performance analytics to enable better decision-making and agility in planning. The integration addresses key challenges such as data inconsistencies, lack of direct data import methods, unfriendly table names, and performance issues. By simplifying the process and providing prebuilt planning data models, this integration helps you make timely, data-driven decisions and improves the overall user experience. - Access the Business performance analytical tables. - Pick and choose the tables you need to start planning. - Perform transformation operations such as "Group By" and "Filter" on those tables before importing them into Microsoft Dataverse.

Change history

Differences detected between scans

  • status01 Sept 2026

    The release status moved from Upcoming to Public Preview.

    Previous
    Upcoming
    Current
    Public Preview
  • updated21 Aug 2026

    Microsoft changed the public preview date.

    Previous
    -
    Current
    Sep 2026
  • updated21 Aug 2026

    Microsoft changed the general availability date.

    Previous
    Sep 2026
    Current
    -
  • delayed13 Aug 2026

    Microsoft moved the general availability date out by 62 days.

    Previous
    Jul 2026
    Current
    Sep 2026
  • status13 Aug 2026

    The release status moved from Generally Available to Upcoming.

    Previous
    Generally Available
    Current
    Upcoming
  • added12 Aug 2026

    Microsoft added this feature to the Dynamics 365 Finance release plan.

    Previous
    —
    Current
    Generally Available
Back to Release Radar³