Data Import & Export

How to Fix Excel Not Refreshing Power BI Semantic Model Connections

Bushra ParveenBushra Parveen Nov 10, 2026 868 views

Question details

Users are unable to successfully refresh live Excel connections to Power BI semantic models, causing reports and PivotTables to display outdated data.

How to Fix Excel Not Refreshing Power BI Semantic Model Connections
Product
Microsoft Excel
Device & OS
not provided
Scenario
Attempting to update Excel PivotTables or reports connected to a Power BI semantic model via XMLA or live connection after a scheduled dataset refresh.
Observed behavior
The Excel manual or scheduled refresh operation completes without throwing an error, but the data in the PivotTable remains outdated instead of reflecting the latest Power BI data.
Before you start

Verify that your Power BI workspace is hosted on Premium capacity and that the XMLA endpoint is enabled in your tenant settings, as XMLA read/write operations require specific licensing.

Solution 1Recommended

Use the Native Power BI Data Connector

If you do not have a Power BI Premium capacity for XMLA, connecting directly via the native Power Platform data connector provides a stable alternative for Pro license users.

The XMLA endpoint strictly requires Premium capacity. If you are using a standard Pro license, switching to the native Fabric & Power Platform connector bypasses this limitation and ensures reliable data refreshes.

1
Access the Data tab

Open your Excel workbook and navigate to the 'Data' tab on the ribbon.

2
Select the Power BI connector

Click on 'Get Data', hover over 'From Power Platform' (or 'From Fabric & Power Platform'), and select 'From Power BI'.

3
Choose your semantic model

A side pane will appear. Search for and select the target semantic model you want to connect to.

4
Insert the PivotTable

Choose to insert a PivotTable or Table to establish a robust live connection that refreshes reliably.

Analyze in Excel: Alternatively, you can start directly from the Power BI service online. Locate your dataset, click the 'More options' menu, and select 'Analyze in Excel' to generate a pre-configured connection file.
Free Microsoft Office alternative

Try WPS Office for Efficient Data Analysis

While live connections to Power BI semantic models via XMLA rely exclusively on the Microsoft ecosystem, WPS Office provides a powerful, lightweight, and free alternative for managing exported datasets, building advanced PivotTables, and handling your daily spreadsheet tasks.

  1. 1. Export Data from Power BI: Export your Power BI visual data as an .xlsx or .csv file.
  2. 2. Open with WPS Spreadsheet: Launch WPS Office and open the exported file seamlessly without formatting loss.
  3. 3. Analyze Data: Use WPS Spreadsheet's built-in PivotTables and formulas to analyze your data efficiently.
100% compatible with Microsoft Excel formats (.xlsx, .csv, .xlsm).Powerful built-in PivotTable and advanced data analysis features.Free, lightweight, and fast to launch on Windows, Mac, and Linux.Familiar user interface requiring zero learning curve for Excel users.
microsoft office alternative - wps office

Frequently Asked Questions

Do I need a Power BI Premium license to connect Excel to a semantic model?

Yes, connecting via the XMLA endpoint specifically requires Power BI Premium or Premium Per User (PPU) capacity. If you only have a Pro license, you should use the 'Get Data > From Power BI' connector instead.

Why does 'Analyze in Excel' result in an empty PivotTable?

An empty PivotTable is expected upon creation. You must drag and drop fields from the PivotTable Fields pane into the Rows, Columns, or Values areas to build your report. Also, ensure you have 'Build' permissions for the underlying semantic model.

How do I force a complete reconnection to my Power BI model in Excel?

Go to 'Data' > 'Queries & Connections', right-click your current Power BI connection, choose 'Delete', and then establish a brand-new connection using the 'Get Data' menu. This clears stale caches.

What causes the connection to fail during scheduled refreshes?

Connection failures during automated or scheduled refreshes are often caused by expired authentication tokens, background refresh conflicts, or workspace administrators disabling the XMLA endpoint permissions.