Older Power BI Desktop Builds Lose OneDrive and SharePoint Save and Share

In Short: What Is Changing for Power BI Desktop Save and Share

Microsoft is retiring the old way Power BI Desktop saved and shared files in OneDrive and SharePoint. Starting in October 2026, Power BI Desktop versions from March 2026 or earlier no longer support saving and sharing to OneDrive and SharePoint. To keep using it, you need a newer build of Desktop.

This is not a future deadline any more. It is late October 2026, and Microsoft gives a month rather than a specific day, so treat any author still on a March 2026 or older build as affected now. The fix is simple - update Desktop - but in organisations where IT controls installs, it can take longer than people expect. This post covers what is changing, who is affected, how to check your version, how to update, what the new flow looks like, and a short checklist for admins.

What Exactly Is Changing

Power BI Desktop can open, save and share .pbix files directly in OneDrive and SharePoint, without going through a synced folder. Microsoft calls this the OneDrive and SharePoint integration, and it runs through a file picker built into Desktop.

The timeline, from Microsoft Learn:

• April 2026 - the new file picker became the default, and users "can no longer access the old file picker experience"
• October 2026 - Power BI Desktop versions from March 2026 or earlier "will no longer support saving and sharing"

Microsoft's What's New page lists this under General as the "Deprecation of old file picker experience in Power BI Desktop". It says users on those older builds "will no longer be able to save and share files to OneDrive and SharePoint", and adds: "Update Power BI Desktop to keep using this functionality."

In other words, the old picker is already gone from current builds. What changes in October is that the builds which still carry it stop working for this one job.

What Microsoft has not said is just as useful to know:

• No exact date. The notice says October 2026, not a day.
• No detail on what users see. Microsoft doesn't describe the message an author on an old build gets when a save or share fails.
• Nothing about local saving. The notice covers the OneDrive and SharePoint save and share experience inside Desktop. It says nothing about saving to a local drive, and we have seen nothing from Microsoft suggesting that is affected.

We'd rather say that plainly than guess. In every case Microsoft describes, the fix is the same: update Desktop.

Who Is Affected

You are affected if both of these are true:

• someone in your organisation saves or shares .pbix files to OneDrive or SharePoint from inside Power BI Desktop - through Save as, the OneDrive option, or the Share button
• they run a Desktop build from March 2026 or earlier

The people most at risk are rarely the enthusiasts who update every month. They are:

• Authors on locked-down laptops, where IT packages Desktop and pins a version
• Teams that standardised on one build so everyone could open each other's files
• Occasional authors - finance or operations staff who open Desktop once a month and ignore the update prompt
• Machines with update notifications turned off. Microsoft documents a registry value, DisableUpdateNotification, that organisations use to stop users being prompted. Those users won't be nudged.

This change does not touch publishing to the Power BI service. If your authors publish to workspaces and never save to OneDrive or SharePoint from Desktop, they are not affected - see our comparison of Power BI Desktop and the Power BI service for how the two fit together. Microsoft also says only .pbix files can be saved to OneDrive and SharePoint this way, so teams working in Power BI Project (PBIP) format with Git are on a different path anyway. Our guide to PBIP and PBIR covers that route.

How to Check Your Power BI Desktop Version

In Power BI Desktop, go to the Help ribbon, select About, and read the Version line.

Versions are numbered, not just dated. Microsoft's change log lists the March 2026 build as version 2.152.1057.0, and the February 2026 build as 2.151. So in practice:

• 2.152 or lower - March 2026 or earlier. Affected. Update.
• Higher than 2.152 - April 2026 or later. Not caught by this change, although Microsoft only supports the latest version, so stay current anyway.

If you manage a lot of machines, your device management or software inventory tool can report installed versions of Power BI Desktop. That is quicker and more reliable than asking people for screenshots.

How to Update Power BI Desktop

There are two ways to install Desktop, and they update differently. Microsoft releases Desktop monthly, and only the latest version is supported - if you contact support, you'll be asked to upgrade first.

Microsoft Store version

The Store version keeps itself current. Microsoft says Windows "automatically downloads the latest version in the background as soon as it's available", and no admin rights are needed to install it. If a Store install looks stuck on an old build, open the Microsoft Store and check for updates.

Download Center installer

The .exe installer from the Microsoft Download Center does not update itself. Download the latest 64-bit version and run it. You need admin rights to install it this way. The 32-bit version is no longer supported.

Two warnings from Microsoft's documentation:

• Don't mix installs. Having the older msi-based install and the Store version on the same machine isn't supported, so uninstall one before installing the other. A Store install also doesn't copy user settings from the .exe version, so people may need to reconnect data sources and re-enter credentials.
• Update teams together. Earlier versions can't open files created or saved in newer releases. If half a team updates and half doesn't, the half on old builds will be locked out of files the others have saved.

Managed IT deployment

For packaged rollouts, the installer supports silent installation with command-line switches, including -quiet, -norestart and ACCEPT_EULA=1, plus DISABLE_UPDATE_NOTIFICATION=1 if you want to control the update cadence yourself. If your deployment tool needs an .msi, Microsoft describes extracting one from the .exe with the WiX Toolset, and notes that upgrading from an .exe install to an extracted .msi isn't supported - uninstall the old version first.

If you pinned a build for stability, this is the moment to change the policy. A pin on March 2026 or earlier now breaks a feature your authors may depend on.

What the New Flow Looks Like

On a current build, the experience is the one Microsoft has made the default since April 2026:

• Open: File, then Open, then OneDrive. You can move between OneDrive and SharePoint folders, use Quick access to reach other locations, and pin or unpin recent files and folders.
• Save: the first time you save a report, you name it and choose a OneDrive or SharePoint location from a list of recent places, or select More options. If your organisation requires it, you also pick a sensitivity label. For an existing file, use Save as and choose OneDrive.
• Share: the Share button at the top right opens the Microsoft 365 share dialog. You can share with people or groups, or copy a link, and Manage Access sits under the same button. The file must be saved in OneDrive or SharePoint first.
• Version history: select the file name in the title bar, then Version History, to see earlier versions without leaving Desktop.

Sharing follows your existing OneDrive and SharePoint sharing policies, and sensitivity labels are respected, with the strictest permission winning.

One known gap: Microsoft says the updated picker has no way to add a SharePoint site by URL. If a library is missing, follow the site in SharePoint and restart Desktop, and it should appear.

Admin Checklist

• Find affected authors. Pull installed Desktop versions from your inventory tool and list anyone on 2.152 or lower.
• Prefer the Store version where you can. It updates itself and needs no admin rights.
• Refresh pinned packages. Rebuild any packaged installer from the latest Download Center build and push it out.
• Review DisableUpdateNotification. If it is set, you own the update cadence. Put a monthly check on someone's calendar.
• Update shared teams together. Avoid a mix of old and new builds working on the same files.
• Check the tenant setting. "Users can share links to Power BI files stored in OneDrive and SharePoint through Power BI Desktop" is on by default. Confirm that matches your sharing policy. Users can also switch the save and share options off in Desktop's own settings.
• Tell authors what changed. A two-line note - update Desktop, then save and share as before - heads off most help desk tickets.

One oddity worth knowing: Microsoft's integration page still carries a public preview note, and the sharing tenant setting is still labelled preview, even though the new file picker is now the only option. Check the Learn page again before you publish internal guidance.

How We Help

This is a small change, but it lands hardest in organisations where nobody owns Power BI Desktop as a product. As part of our Power BI and analytics services, we review how your authors build, save and share reports, set a sensible update policy for Desktop, and move teams that have outgrown .pbix files on SharePoint onto PBIP, Git and deployment pipelines.

Sources and Further Reading

• Power BI Desktop OneDrive and SharePoint integration - Microsoft Learn
• What's new in Power BI - Microsoft Learn
• Download Power BI Desktop - Microsoft Learn
• Change log for Power BI Desktop - Microsoft Learn
• Integration admin settings - Microsoft Learn