Forum Discussion
Direct Lake Desktop Edition Content Blocked
- 2 months ago
Hi @generop,
Based on the screenshot, this looks less like a Direct Lake model/XMLA issue and more like the browser/launch flow used by Edit in Desktop is being blocked.
is commonly seen when embedded Microsoft web content or sign-in content is blocked by browser privacy settings, tracking prevention, extensions, or third-party cookie settings.
I would first test the browser side:
- In Edge, go to Settings → Cookies and site permissions.
- Open Manage and delete cookies and site data.
- Temporarily set Block third-party cookies to Off.
- Set Tracking prevention to Balanced, not Strict.
- Disable any ad-block or privacy extensions for Power BI/Fabric sites.
- Fully close and reopen the browser, then try Edit in Desktop again.
If you do not want to allow third-party cookies globally, try adding these domains to the allow list:
- *.powerbi.com
- *.fabric.microsoft.com
- *.microsoftonline.com
I would also test opening the model directly from Power BI Desktop instead of launching from the browser:
Power BI Desktop → OneLake catalog / Power BI semantic models → select the Direct Lake model → Edit
Direct Lake semantic models are live-edited in the Fabric workspace from Power BI Desktop, not edited as a normal local PBIX file:
Direct Lake in Power BI Desktop
If the browser/cookie changes do not fix it, I would raise a Microsoft support ticket. There is a related community thread where Edit in Desktop for Direct Lake models stopped working for multiple users and Microsoft support reproduced the issue:
Power BI - Direct Lake model - choosing Edit in Desktop not working
Because this happens with new models too, I would not assume the semantic model itself is broken. It may be a browser/auth launch issue or a Direct Lake Edit in Desktop integration issue.
Best regards,
Solutions Architect · Microsoft Fabric Specialist · Parchitect💡Did my response help you? Clicking Kudos is a small gesture that goes a long way, it encourages contributors and helps the community thrive!
✔️Did I answer your question? Please mark my post as a Solution, it helps others find the answer faster.
Hi @generop,
Based on the screenshot, this looks less like a Direct Lake model/XMLA issue and more like the browser/launch flow used by Edit in Desktop is being blocked.
is commonly seen when embedded Microsoft web content or sign-in content is blocked by browser privacy settings, tracking prevention, extensions, or third-party cookie settings.
I would first test the browser side:
- In Edge, go to Settings → Cookies and site permissions.
- Open Manage and delete cookies and site data.
- Temporarily set Block third-party cookies to Off.
- Set Tracking prevention to Balanced, not Strict.
- Disable any ad-block or privacy extensions for Power BI/Fabric sites.
- Fully close and reopen the browser, then try Edit in Desktop again.
If you do not want to allow third-party cookies globally, try adding these domains to the allow list:
- *.powerbi.com
- *.fabric.microsoft.com
- *.microsoftonline.com
I would also test opening the model directly from Power BI Desktop instead of launching from the browser:
Power BI Desktop → OneLake catalog / Power BI semantic models → select the Direct Lake model → Edit
Direct Lake semantic models are live-edited in the Fabric workspace from Power BI Desktop, not edited as a normal local PBIX file:
Direct Lake in Power BI Desktop
If the browser/cookie changes do not fix it, I would raise a Microsoft support ticket. There is a related community thread where Edit in Desktop for Direct Lake models stopped working for multiple users and Microsoft support reproduced the issue:
Power BI - Direct Lake model - choosing Edit in Desktop not working
Because this happens with new models too, I would not assume the semantic model itself is broken. It may be a browser/auth launch issue or a Direct Lake Edit in Desktop integration issue.
Best regards,
Solutions Architect · Microsoft Fabric Specialist · Parchitect
💡Did my response help you? Clicking Kudos is a small gesture that goes a long way, it encourages contributors and helps the community thrive!
✔️Did I answer your question? Please mark my post as a Solution, it helps others find the answer faster.
I had the same problem this morning and it was affecting all workspaces. Clearing cookies & restarting the browser (Edge) fixed the issue. Thank you!