Does Fabric Runtime 2.0 update affect Querying LH via Fabric Browser UI functions?

Hi anon97242​,

Good question to ask before the migration. I can't confirm the exact internals from Microsoft documentation, so treat the first part as my understanding and the second part as a way to verify it in your own tenant.

Why SparkCore shows up for a Lakehouse: the SQL analytics endpoint (T-SQL) runs on the warehouse engine and is billed as SQL, not Spark. But several things you can do from the Lakehouse in the browser are Spark-backed even if you never open a notebook: Load to tables, table maintenance (OPTIMIZE / VACUUM), and some table or file previews. If your users are running Spark SQL or doing those actions through the Lakehouse UI, that would explain SparkCore usage on LH items.

Do you need to test for 2.0? Runtime applies as a workspace-level Spark setting, so the question to answer is which runtime those workspaces are on and whether the UI actions you rely on behave the same on 2.0. Check the current setting through the API:

GET https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/spark/settings

-> look at "environment.runtimeVersion"

Then, to find out what is actually generating the SparkCore usage:

1. Capacity Metrics app -> Item history -> filter SparkCore -> note the operation names and user
2. Monitor hub -> filter by item type / user -> match start times to the usage spikes
3. Ask one user to repeat the suspected action (preview, load to table, maintenance) and watch which operation appears

Finally, I'd run the same actions in a non-production workspace with Runtime 2.0 selected, since a runtime change affects the whole workspace, and compare results and CU usage with prod. If you don't use notebooks, that smaller test list is probably all you need.

So my overall approach would be:

Identify which UI actions generate SparkCore (Capacity Metrics + Monitor hub)
Check workspace runtime via Spark settings API
Repeat those actions in a test workspace on Runtime 2.0
Compare behaviour + CU, then roll out per workspace

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.

Hi anon97242​,

Fair point, my earlier steps only showed that Spark is involved, not who manages it. I am not aware of a Microsoft statement that settles whether the Lakehouse browser UI will keep working past the Runtime 1.x end-of-support date if the workspace runtime is never updated, so I would not rely on my reading of it.

The most reliable way to get a definitive answer is the Fabric runtime lifecycle documentation, and if it does not address the Lakehouse UI explicitly, a support ticket asking exactly your question (UI-initiated operations after the end-of-support date, no runtime change) will give you something citable. In the meantime, as noted by ShafiUllah-bc​, queries through the SQL analytics endpoint run on the SQL engine rather than Spark, so those should not depend on the runtime setting.

Hi anon97242​ ,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?

Regards,
Chaithanya