Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
I'm running into all kinds of weird bugs when interacting with lakehouse tables. The main ones are 403 forbidden, and a related issue where the "saveAsTable" command seems to be trying to send data to the wrong lakehouse.
I've seen others mention that schema-enabled lakehouses have well-known bugs.
Is there a way to determine which lakehouses are schema-enabled? I don't think I turned this feature on deliberately. However I wouldn't be surprised if somehow fabric did the change behind my back. Does the following (sql analytics endpoint screenshot) indicates that my lakehouse is schema-enabled?
Also how do I disable the schema stuff, once it has become enabled? I'd like to use the non-buggy version of a lakehouse if possible.
Hi @dbeavon3,
Thank you @NandanHegde, for your insights.
The errors you are encountering are likely because Lakehouse schema support is still in public preview and has not reached general availability yet. Currently, there is no way to disable schema support after it has been enabled. The only solution is to create a new Lakehouse without enabling schema.
Below is the link for reference:
Lakehouse schemas (Preview) - Microsoft Fabric | Microsoft Learn
Thank you.
Thanks for the link. I don't have any schema commands listed in my drop-down menus.
So the mystery remains.
Why do I have an issue where the "saveAsTable" command randomly generates 403 errors when i'm connected to a default lakehouse? Is this a bug that the CSS folks at Mindtree would help with? Are there any other non-GA features that might impact the behavior?
In my logs, the initialization of the default lakehouse seems to happen properly. But when I start using that, it fails.
Hi @dbeavon3,
The issue might be caused by the session expiring, restarting during an operation, or a mismatch with the default lakehouse. If the problem continues, please raise a support ticket using the link below.
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Thank you.
Based on my understanding, once a lakehouse is created with schema option enabled; it is permanent (and cannot be disbaled back)
You might need to create a new lakehouse and sync the data from the schema enabled lakehouse to the new one
I took another look at the docs, and when I compare the commands available to me, it does NOT seem like I'm using the schema feature for lakehouse (which is good).
Yet I'm still having strange errors in my notebooks. Will probably have to open a ticket.