The Power BI Deprecation Nobody Is Going to Call You About

If your team runs a Power BI dashboard for council packets, budget transparency, or operational reporting, there is a date on Microsoft’s calendar that nobody is going to call you about: August 31, 2026.

That’s when Microsoft completes its retirement of legacy Power BI import models the kind most public sector teams stood up between 2018 and 2022, back when uploading an Excel file straight into Power BI Service was the default path. There is no email warning. No banner in the interface. No “your dashboard will stop working” alert. The refresh will simply fail one morning. A few weeks later, the dashboard will fail to load at all.

Most owner-managers the city clerk, the housing authority finance director, the school district data lead won’t see this coming because the vendor who built the thing three budget cycles ago isn’t watching either. This is a plain-language tour of what breaks, how to tell if you’re exposed, and what your honest options are.

The Three Dates That Matter

Put these on whatever calendar your team actually checks.

May 31, 2026 the entry point closes. You can no longer create a new legacy import model in Power BI Service. The old “Get data > Files > Local file” upload path is removed from the user interface. Existing models still work; you just can’t make a new one the old way. This milestone tells you Microsoft is serious but it doesn’t actually break anything you already have.

July 31, 2026 refreshes stop. Existing legacy import models stop refreshing. The dashboard still loads. The numbers still display. But those numbers are now frozen at whatever the last successful refresh captured. This is the silent fail. Nothing visibly breaks. Your council packet, your transparency report, your operational scorecard they all keep rendering with stale data, and nobody upstream is going to tell you.

August 31, 2026 the dashboard goes dark. Legacy import models can no longer be queried. The report stops loading. Users get an error. This is when phone calls start.

How to Tell If Your Dashboard Is Exposed

Three indicators, in order of how easy they are to check.

1. Age. If your dashboard was built before mid-2022 and hasn’t been rebuilt since, assume exposure until proven otherwise. The legacy Excel/CSV upload path was the default for years. Most public sector dashboards from that era used it.

2. License tier. Open Power BI Service in your browser, click your profile in the top right, and check the license. If it says “Power BI Pro” not “Premium Per User,” “Premium Capacity,” or “Fabric Capacity” you are statistically more likely to be running a legacy import model. Premium-tier tenants tend to have already migrated.

3. Refresh history. In Power BI Service, open the workspace, find the semantic model (the dataset behind the dashboard), and look at refresh history. If the source type shows as “Excel” or “CSV” rather than “Power BI Desktop” or “Dataflow,” that’s the deprecated path.

If all three indicators point the same way, you are exposed. If only one does, get a second opinion before spending money on remediation the actual deprecation is narrower than it first sounds.

Why This Matters on a Public Sector Calendar

The damage isn’t financial. It’s reputational, and on the cycles elected officials care about, that’s worse.

Council packets. Most are assembled the Friday before the Monday or Tuesday meeting. If your “FY2026 Budget vs. Actual” dashboard quietly froze a month ago, the numbers in the packet are wrong but they look right. Two or three meetings can pass before anyone catches it, and when they do, it’s during open comment, on video, on the record.

Transparency and FOIA. If your published transparency dashboard is the canonical source residents and journalists check, stale data is a public records problem. “We thought it was refreshing” is not a sentence anybody wants to put in a follow-up letter, and a frozen dashboard that’s still publicly accessible is the kind of thing a local reporter notices.

Operational reporting. Housing authority occupancy, school district enrollment, county public health case counts anything driving a Monday morning standup. When this goes dark, it doesn’t fail loud. It just stops being there, and decisions get made on memory instead.

Election-year visibility. 2026 is a midterm year. If your jurisdiction’s data goes stale or dark during the run-up, expect questions you’d rather not answer.

What Your Options Actually Are

Three migration paths. None of them are great, all of them are real.

(a) Upgrade to Premium or Fabric capacity. Microsoft’s preferred path. You pay meaningfully more often 5–10x and the migration is largely automatic. Right answer for tenants with twenty-plus active models. Overkill for a department with one or two.

(b) Migrate to dataflows. Rebuild the data ingestion as a Power BI dataflow, then point the existing reports at the new source. Stays on Pro licensing. Requires someone who can read Power Query and understand the original data shape. Two to ten hours per model.

(c) Reauthor in Excel plus Power Automate, or in Power BI Desktop (PBIX). Step sideways. PBIX import-mode files published to the service are not affected by this deprecation. For simple dashboards, sometimes the right call.

If You Want a Second Set of Eyes

If you’re not sure whether you’re exposed, we run a free Tier 0 audit: we identify which of your models are on the deprecated path, 24-hour turnaround. No sales call attached.

If remediation is needed, the Tier 1 sprint ($1,995, 3–5 days) rebuilds one dashboard onto a supported source. The Tier 2 sprint ($4,950, 7–10 days) handles up to ten models and includes documentation your successor can actually use.

Reach us at swhconsultants.com/contact. We don’t work on enterprise IT migrations. We work on small public sector dashboards that need to keep working through 2026 and into the next budget cycle.