Forum Discussion
desktop Power Query
Hi HFT,
Thank you for the follow up.
Based on my understanding, the slow refresh issue is primarily caused by storing and processing large volumes of consultant data through API embedding without an optimized storage layer. Power Query or PPU handles large datasets less efficiently without dedicated Fabric capacity or a high performance data source such as ADLS Gen2 or Blob Storage.
As SQL is not an option, please consider the following supported non‑SQL storage alternatives for improved performance:
- Azure Data Lake Storage Gen2 which supports large datasets, high-performance Parquet or Delta formats, and seamless integration with Power BI and Fabric.
- Azure Blob Storage which is a suitable alternative if ADLS Gen2 is not available.Use Parquet format for faster reads.
- Dataverse which is appropriate for managed relational data storage when operating within your organisation’s Power Platform environment.
- Dataflow Gen2 which requires Fabric capacity (F‑SKU). Power BI Pro Per User (PPU) alone does not include Fabric capacity.
- Classic Dataflows (Gen1) which remain usable under PPU, but performance and features such as Direct Lake and advanced refresh are limited.
If possible, request Fabric capacity or use a trial to leverage Dataflow Gen2 with ADLS Gen2 storage for faster and more reliable refreshes. If Fabric capacity is not available, use Azure Blob Storage or ADLS Gen2 with Classic Dataflows or a direct file connection.
Please refer to the links below for further information:
Azure Data Lake Storage Gen2 - Power Query | Microsoft Learn
Azure Blob Storage - Power Query | Microsoft Learn
Create a Power BI report using the Microsoft Dataverse connector - Power Apps | Microsoft Learn
Understand Microsoft Fabric Licenses - Microsoft Fabric | Microsoft Learn
Configuring dataflow storage to use Azure Data Lake Gen 2 - Power BI | Microsoft Learn
Power Query Parquet connector - Power Query | Microsoft Learn
Dataflows best practices - Power BI | Microsoft LearnWe hope this information helps to resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.
Hi HFT,
We would like to follow up and check whether the details we shared have helped to resolve your problem.
If you need any more assistance, please feel free to connect with the Microsoft Fabric community.
Thank you.
Thankyou, andrewsommer, for your response.
Hi HFT,
We appreciate your inquiry on the Microsoft Fabric Community Forum.
In addition to the response provided by andrewsommer , please follow the steps below, they may help resolve the issue.
- Power Query currently does not support mid refresh token renewal. You must obtain a new token before each API call or use a method that handles token refresh outside Power Query. Implement token retrieval via a custom Power Query connector.
- Optimise data loads by using incremental refresh, paging, and query folding, and consider using dataflows to stage large datasets.
For further information, please refer to the links below:
Handling authentication for Power Query connectors - Power Query | Microsoft Learn
Configure incremental refresh and real-time data for Power BI semantic models - Power BI | Microsoft Learn
Understanding query evaluation and query folding in Power Query - Power Query | Microsoft Learn
Dataflows best practices - Power BI | Microsoft Learn
We hope the information provided helps to resolve the issue. If you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.