Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hi Everyone,
I'm currently using the MS store version of Power BI desktop that updated this morning to Version: 2.151.1052.0 64-bit (February 2026)
When trying to edit the Direct Lake model in Desktop I'm getting this error message "Unable to open document" - This feature is unavailable for Power BI Free Users, please upgrade to continue
The workspace is Fabric capacity and I has a pro licence
Hi All,
Update Email from MS Fabric Support - they now have a link to previous versions of Power BI desktop, and they now have the Jan-26 version (previously this linked back to a Nov-25 version, when clicking on the Jan-26 file download)
Previous monthly updates to Power BI Desktop and the Power BI service - Power BI | Microsoft Learn
It's still worth noting, there is no known issues section that I can find for the Power BI Desktop versions - This would be useful (unless I'm being blind)
I have the same issue: Error: This feature is unavailable for Power BI Free Users, please upgrade to continue
(obviously I do have a subscription for PBI)
Facing the same issue.
Hi all,
Quick update on the Microsoft Fabric support ticket. (I strongly suggest anyone else that has the issue, to please also raise a support ticket, this will result in faster movement I'm sure)
Initially, support asked us to uninstall and reinstall the Desktop app, which wasn’t feasible because each installation requires involvement from our IT support provider.
I directed them to this forum thread, and the next day they arranged a Teams call. Fortunately, one of our team members who works more on the SQL side still had the February 26th version installed.
During the call we were able to reproduce the issue live and provide browser logs. It turns out my original description — that we were unable to edit a DirectLake model in Desktop — had been misunderstood.
Support has now successfully replicated the bug on their side as well. Their latest update is: “We will check internally and keep you posted once we have any update from our team.”
I’ll share more as soon as we hear back.
It seems posting on the forum, commenting on the Power BI update youtube, and sharing the issue on Twiter (X) - may have pushed this a little bit further up the list
Hi @101Mathew,
please do share the any updates or progress here. this helps other communtity members with similar issues
thanks,
Prashanth
I have the same issue 'This feature is unavailable for Power BiI Free users' when choosing to edit the model in PBI Desktop. This started after the latest update. This is clearly a bug microsoft. The workaround above worked fine. I suspect there are going to be many more affected!
Hi!
We are seeing the same issues with Power BI Desktop, we were able to edit Semantic Models within the Desktop app until recently and after the last update, we are being informed that "This feature is unavailable for Power BI Free Users".
Downgrading to an earlier version of Power BI Desktop resolved our issue.
Thanks !
Can add that we have the same problem after last release. Can not edit semantic models with Power BI desktop anymore after the release, which complains about licenses even though it exists. Forced to roll back version to be able to work in the wait for a new release.
Thank you for adding your voice to this issue - I've raised a bug with via MS Fabric - they replied with (see below) - not very helpful reply - as this items have already been tested and checked by our IT support
Next Action:
We sincerely apologize for the inconvenience you’re experiencing and understand how disruptive this issue can be.
Based on our initial analysis and Microsoft documentation, this scenario strongly indicates that a Power BI Pro license is required for editing Direct Lake semantic models in Power BI Desktop. As per the official requirements, this feature is unavailable for users with a free license:
To help rule out any environment or licensing-related factors, we kindly request that you try the following steps:
Once you’ve completed the above steps, please let us know the outcome or if you encounter any further issues.
Feel free to reference my responses, as several others are experiencing the same issue. Our entire team is affected — the older version continues to work, but we’re unable to work on other components that require a Pro license.
We have triple-checked our accounts and license assignments in both the Fabric portal and Power BI Desktop. Hopefully, this can be acknowledged as a bug and resolved before it impacts more users.
Thank you I will add this to link to the ticket email
Interesting that you've stated "but we’re unable to work on other components that require a Pro license."
Can you give more details - as when I've installed the older version it notes that I have a pro licence and all functions are working
If you are making use of User Defined Functions (UDFs) - this might need re-selecting in the options and settings -> options -> preview feature to enable it again (we had this issue)
Hi @101Mathew,
the account where you have the Pro license, is this account in the same tenant as your Fabric Capacity?
This is necessary as you can not use PBI Pro license within another tenant (as per standard settings).
Best regards!
Hi @Mauro89 confirmed - its the same account, I've been able to edit direct lake models with no issue for months till today - We tested this eith another user, one on an older version of Power BI desktop no issues at all, and another with the version noted above.
It worked for the older version
Version: 2.150.2455.0 64-bit (January 2026) but not for Version: 2.151.1052.0 64-bit (February 2026)
IT support have removed the MS store version and installed Version: 2.150.2455.0 64-bit (January 2026) - which now allows me to edit the Direct Lake model in Desktop with no issues
We are having the same issue which is definitely a bug and not related to Pro/Fabric license. Microsoft's ONLY suggestied solution was to roll back which is not possible for us due to scale.
Fortunately, we found the following workaround ourselves:
Thanks, that worked for me too!
| User | Count |
|---|---|
| 58 | |
| 45 | |
| 32 | |
| 16 | |
| 14 |
| User | Count |
|---|---|
| 82 | |
| 68 | |
| 43 | |
| 26 | |
| 25 |