Blog Post

Power BI Updates Blog
4 MIN READ

Upgrade Power BI Dataflows Gen1 to Fabric Dataflows Gen2 with the Upgrade Wizard (Preview)

eranbenayun's avatar
eranbenayun
Icon for Microsoft Employee rankMicrosoft Employee
1 month ago

Upgrading Power BI Dataflows Gen1 is now easier with the Dataflows Upgrade Wizard. Now in preview for eligible workspaces assigned to Fabric capacity, the wizard provides a guided experience to upgrade Power BI Dataflows Gen1 items to Fabric Dataflows Gen2 (CI/CD). The wizard preserves key properties of the existing dataflow and assesses each item before you begin, helping you understand the upgrade scope and expected follow-up actions. 

Modernize at your own pace 

Power BI Dataflows Gen1 remains supported in a legacy state, while new feature investment focuses on Fabric Dataflows Gen2 (CI/CD), as shared in a previous post about the future of Dataflows. The Upgrade Wizard gives dataflow owners a guided self-service path to start that modernization without rebuilding their Power Query logic. 

You don't need to upgrade your full estate at once. Start with a representative set of dataflows, validate the results, and expand at a pace that works for your organization. For detailed migration planning and inventory guidance, review Migrate from Dataflow Gen1 to Dataflow Gen2. 

Build on the benefits of Dataflows Gen2 

Fabric Dataflows Gen2 (CI/CD) builds on the Power Query authoring experience already used in Power BI Dataflows Gen1, while adding capabilities designed for development, operations, and integration across Fabric. 

Dataflows Gen2 supports a broad set of data destinations: Azure SQL Database, Azure Data Explorer (Kusto), Azure Data Lake Storage Gen2, Fabric Lakehouse tables, Fabric Lakehouse files, Fabric Warehouse, Fabric KQL database, Fabric SQL database, SharePoint Files, Snowflake database, and PostgreSQL database. You can begin with the upgraded dataflow and add destinations when you are ready. 

As a native Fabric item, Dataflows Gen2 (CI/CD) supports Git integration and Fabric deployment workflows. Teams can bring dataflow definitions into source control, collaborate through established development practices, and move changes across development, test, and production environments. Refresh history and Fabric monitoring experiences provide operational details that help teams review runs and investigate failures. 

Capabilities such as Fast Copy, Modern Evaluator, and Partitioned Compute improve performance and scale for different workload patterns. Microsoft's published Dataflow Gen2 cost and performance benchmarks show refresh times improving by 1.6 to 21 times with Dataflows Gen2. Results vary by data, capacity, connector, gateway usage, and query design, so validate your representative workloads. 

Dataflows Gen2 (CI/CD) also benefits from tiered Standard Compute pricing, with a lower rate after the first 10 minutes of each mashup-engine query. Separate meters apply to high-scale compute and Fast Copy data movement. 

Copilot in Data Factory enhances Dataflow Gen2 authoring with natural language. It can generate transformation steps, create queries, and summarize a query and its applied steps. These capabilities help authors understand and review complex query logic, improving productivity during transformation design. 

The bottom line is simple: upgrade now, then modernize when it adds value. 

Upgrade one or more dataflows from the same workspace 

Ready to begin? Open the menu next to a Power BI Dataflows Gen1 item and select Upgrade to Dataflow Gen2 (Preview). The Dataflows Upgrade Wizard opens with the selected item and lets you add other Dataflows Gen1 items from the same workspace. 

Figure: Start the Dataflows Upgrade Wizard from a Dataflows Gen1 item.

 

The upgraded item preserves its ID, schedule, queries, and connections. Keeping the same item ID helps downstream semantic models and reports continue using the upgraded dataflow without source remapping. The dataflow name also stays the same unless the assessment identifies a required naming change.

After the upgrade is completed, the Fabric Dataflows Gen2 (CI/CD) item replaces the original Power BI Dataflows Gen1 item, and the upgrade can't be reversed. If you need to keep the original Power BI Dataflows Gen1 item, use Save As to create a separate Fabric Dataflows Gen2 (CI/CD) item instead.

Know what needs attention before the upgrade

Before making any changes, the Upgrade Wizard assesses the Power BI Dataflows Gen1 items in your workspace, giving you a clear view of which dataflows are ready and where you may need to act before or after upgrading:

• Ready to migrate: The wizard didn't identify a manual step needed before or after the upgrade. Review the known limitations because the assessment doesn't detect every limitation.

• Needs Attention: You can proceed, but review the reasons and complete the recommended actions.

• Upgrade unavailable: You don't own the dataflow. Ask the owner to upgrade it or use Take over first.

Figure: The assessment shows which dataflows are ready and which need attention.

A Needs Attention status can currently identify incremental refresh, Bring Your Own Lake storage, linked dataflows, possible DirectQuery consumers, or naming changes. Hover over the status to see the reason, then review the Upgrade Wizard documentation for follow-up actions and more information. The scenarios represented by each assessment status may expand as we further enhance the assessment capabilities.

After the upgrade

Once the wizard finishes, complete these follow-up steps to validate your upgraded dataflows and reconnect any dependencies.

• Refresh each upgraded dataflow to load its data.

• Open and save each downstream dataflow to rebind it.

• Complete any remaining recommended Needs Attention actions.

• Update consumers (for example, semantic models or linked dataflows) using the legacy Power BI Dataflows connector to the modern Power Platform Dataflows connector. The assessment doesn't detect legacy connector use.

Learn more

Ready to explore the Upgrade Wizard? Review the prerequisites, assessment guidance, and complete workflow in Upgrade Dataflow Gen1 to Dataflow Gen2 (CI/CD) using the Upgrade Wizard. We look forward to hearing about your experience during preview.

Updated 1 month ago
Version 1.0

10 Comments

  • Hi, we were told by MS Support two months ago that minimal consumers access to a DF Gen2 was workspace contributor, instead of workspace viewer like DF Gen1. Is it still the case?

    It's an important consideration before migrating, and it is not well documented in the migration process/limitation.

    thx

    • mllopis's avatar
      mllopis
      Icon for Community Admin rankCommunity Admin

      Thanks for the feedback - That is unfortunately still the case (you should be able to see the Dataflow Gen2 item in the Dataflows connector, just not the tables within it).

      This is something that we're looking into so that we reestablish Workspace Viewer access to the Gen2 items, which should simplify the Gen1->Gen2 migration.

      Thanks,
      M.

  • We need the ability to provide access to the individual Fabric items like Dataflow Gen2 without users having the ability to create other items like lakehouses, warehouses, notebooks, etc...  You can't deprecate a capability like DF Gen 1 without giving customers the ability to granular secure the new capabilities. 

    • mllopis's avatar
      mllopis
      Icon for Community Admin rankCommunity Admin

      Thanks for the feedback - Providing all Dataflow Gen1 users with a path to Dataflow Gen2 is a top priority for us, as we discussed in detail in this blog earlier this year: 

      https://powerbi.microsoft.com/en-us/blog/dataflows-thank-you-for-eight-years-of-gen1-and-why-gen2-is-the-future/

      While we don't have specific updates to share at this point yet, rest assured that this is something that we're pushing on before taking further steps on Gen1 deprecation. This blog focuses on streamlining the upgrade path for those users who already have access to Fabric / Dataflow Gen2.

      Thanks,
      M.

  • DClark21044's avatar
    DClark21044
    Frequent Visitor

    Great feature! If you have reports connected to a gen1 dataflow and you upgrade to gen 2, will the report connections break?

    • mllopis's avatar
      mllopis
      Icon for Community Admin rankCommunity Admin

      With the new Migration Wizard, upgraded Dataflows will keep the same ID as the original Dataflow Gen1, meaning that downstream references (such as Semantic Model / Report queries) will point to the results of the upgraded dataflow. The main goal of that is to enable seamless upgrade for exactly the scenario that you're describing.

      The main caveat to raise, as others have done in Comments in this blog, is that Workspace Contributor role is required at the moment to be able to access Dataflow Gen2 tables, instead of "just" Workspace Viewer as it is the case for Dataflow Gen1 tables. This is a divergence that we're trying to address in the future, to keep the migration simple.

      Thanks,
      M.

  • jxdu's avatar
    jxdu
    Regular Visitor

    So what is the future of dataflows in PRO workspaces?

    • eranbenayun's avatar
      eranbenayun
      Icon for Microsoft Employee rankMicrosoft Employee

      Thanks for asking, this is an important question for Pro customers.

      Dataflow Gen1 in Pro workspaces remains supported, and existing workloads can continue to run as-is. Depending on your scenario, Gen1 can still be the right choice today.

      The Upgrade Wizard covered in this post is not available for Pro workspaces yet, as it requires the workspace to be assigned to a Fabric capacity. As we introduce new Dataflow Gen2 paths for Pro, we will share clear guidance and recommended steps to help with a smooth transition. We don't have a specific update to share yet.

      Thanks, Eran

  • With using the deployment pipeline across environments, (IE Dev, Test, Prod) to deploy objects to each stage.  When use the wizard to update a dataflow to gen2 in environments it does not rebind the dataflows. It treats them as separate objects in each environment. Keeps the ID of the gen1 data flow but deployment pipeline treats them as separate objects.  Is there away to rebind the objects. 

    • eranbenayun's avatar
      eranbenayun
      Icon for Microsoft Employee rankMicrosoft Employee

      Hi,

      This is a known limitation. We are working on adding a Needs attention assessment status for dataflows associated with Deployment Pipelines.

      The required steps are:

      1. Upgrade the dataflow Gen1 in Dev, Test, and Prod.
      2. After the dataflows Gen1 is upgraded in all environments, run the Deployment Pipeline.


      Please note that Gen1 deployment rules and some connection bindings may still require manual reconfiguration in Gen2.