Dataflows & Power Query

Prepare data repeatably instead of cleaning every spreadsheet again.

We prepare data from your sources with dataflows and Power Query, for migrations, master data and analysis. Before data lands in Dataverse or Fabric, we clean it, find duplicates and fill in missing details. Every load is repeatable and monitored.

Explore functions and applications ↓
Product view from Microsoft documentation
Microsoft product view with sample data. Interface and functionality depend on version, licensing and configuration. Source and details ↗
Dataflows Gen2

Data preparation in Microsoft Fabric

Power Query is available in Fabric too. Dataflows Gen2 belongs to the analytics platform, not the same deployment as a Power Platform dataflow for Dataverse. Sources, destinations and operations are selected separately.

Microsoft Fabric · Dataflows Gen2 · Power Query
Microsoft product view: Dataflows Gen2. Documentation ↗
Functions

What we deliver with dataflows

01

Connect sources

Tables, files, ERP and legacy systems, on premises through a gateway or directly from the cloud.

02

Clean and enrich

Power Query cleans formats, finds duplicates and fills in missing details, also from external sources. AI-based checks show early where quality falls short.

03

Load with keys

We map tables and columns and define keys so no duplicate records arise. Rejected rows go to a review list.

04

Monitor

Schedule, run history and errors are visible. No report keeps running unnoticed on stale data.

Business applications

Typical use cases for Dataflows & Power Query

Migration to CRM

When moving to Dynamics 365 we carry over the data from the old CRM, cleaned and without duplicates.

Master data from the ERP

Customers, items and prices come regularly from the ERP into your apps.

Preparation for analysis

For Fabric we use Dataflow Gen2 and pipelines, and load large volumes in parallel.

Modernise older dataflows

We review existing dataflows and move them to Dataflows Gen2 where it makes sense.

Architecture

Dataflows & Power Query in your system landscape

This explains the responsibilities. APIs, access and data ownership are agreed for your workflow.

  1. 01Your teamSourcesLegacy system, ERP, files
  2. 02NXTGNPower Queryclean and enrich
  3. 03NXTGNChecksDuplicates and quality
  4. 04NXTGNDestinationDataverse or Fabric
  5. 05NXTGNMonitoringRun history and errors
  6. 06Your teamYour apps and reportswith current data

delivered by NXTGNyour systems and teams

Requirements and boundaries

Microsoft treats Power BI Dataflow Gen1 as legacy. For new analytics we use Dataflows Gen2.

Dataflow or Power Automate?

Dataflows prepare data sets, Power Automate controls workflows and actions. We often use both.

Is every refresh real time?

No. Dataflows run on a schedule. For real time we build an integration in Azure.

What happens to faulty data?

It goes to a review list instead of the target system. Your team corrects it and the next run picks it up.

Related topics

Related products and services

Product documentationPower-Platform-Dataflows ↗Fabric Dataflow Gen2 ↗Lizenz- und Funktionsgrenzen ↗Editorial review: 12 October 2026. Features and availability can change.

Planning to use Dataflows & Power Query?

Discuss your workflow, existing systems, implementation and operational requirements with us.

Matthias Pirzer
Your contact

Matthias Pirzer

Data, CRM & reporting

Read profile →