QuickBooks Online to Power BI after the connector retirement: your options

What Microsoft has published

Microsoft's built-in connection from QuickBooks Online into Power BI was the QuickBooks Online (Beta) connector. The public pages do not agree on a single end date. This note quotes them and does not guess which date your tenant is on.

The Power Query end-of-support list includes QuickBooks Online (Beta), with a sunset of August 2025. That page says the listed connectors are no longer supported and no longer appear in Power Query.

The Power BI June 2025 feature summary says the connector is under deprecation. Starting June 2025, it will not be shown in the Power BI service, and the entry will be removed from Power BI Desktop in the July 2025 release.

The Power BI March 2026 feature summary says the QuickBooks Online connector is being retired and will no longer be supported as of March 2026. After retirement, customers will no longer be able to create new connections, and existing connections may no longer function.

Those statements do not use the same date. Before the next close, open the Power BI service and see whether the model that reads QuickBooks still refreshes. A file that opens on one laptop is not the same as a pack the rest of finance refreshes from the service. The end-of-support list does not name a replacement connector.

Three ways to keep the pack current

These are options a finance team can weigh. They are not a ranked list from Microsoft.

A third-party connector

A vendor connector, or a sync app that lands the QuickBooks tables you need where Power BI can read them, can be the shortest way back to a scheduled refresh. It fits a pack that uses a small set of tables, such as the chart of accounts, invoices, bills, and payments, when you do not want to run a database.

You still own the vendor relationship. Before you commit, ask which tables are included, whether the refresh runs in the Power BI service or only on a desktop, how the QuickBooks sign-in is stored, and who answers when a refresh fails during close. This note does not name vendors. A name here would sound like an endorsement, and coverage changes.

A database you control, then Power BI

Copy QuickBooks into a database your company controls, on a schedule, and point Power BI at that database. The pack no longer depends on the retired connector.

Choose this when the numbers have to hold across many closes, or when the chart of accounts, classes, and locations need to match definitions the board pack already uses. It is also how you line QuickBooks up with payroll, billing, or the plan without a spreadsheet reconcile the weekend before the meeting.

It is more setup than a connector. What you get is a refresh you can see. Someone can say whether last night's copy succeeded before the pack goes out.

Microsoft Fabric

Fabric fits when QuickBooks is one of several systems in the finance pack, and you want the model, the refresh, and access in one place.

Do not assume Fabric has a QuickBooks button. Microsoft's comparison of Azure Data Factory and Fabric Data Factory lists QuickBooks as a source for Azure Data Factory, and not as a Fabric Data Factory connector. Azure Data Factory documents a separate QuickBooks connector, and lists version 2.0 as general availability. That connector is a different product from the Power BI connector in the retirement notices.

A practical Fabric path is to land QuickBooks with a supported copy, such as that Azure Data Factory connector, and then build the finance model in Fabric for Power BI. If the rest of your reporting already lives in Fabric, keeping QuickBooks on that same model avoids a second refresh that only one file uses. Recheck Microsoft's connector list before you commit. Connector lists change.

How to choose

Start from the close, not from the tool. If one person refreshes a small pack and a vendor connector covers the tables you actually open, that can be enough. If several people rely on the same numbers, or QuickBooks has to agree with other systems, a database or Fabric gives those definitions a home.

Name an owner for the refresh, and a check you run before the pack is sent. A report that opens is not proof that it refreshed.

For the finance pack itself, see financial reporting. For landing QuickBooks beside the other systems that feed that pack, see data engineering and integration.