OneSecurity error: Unable to build a fully qualified table name. Required configuration is missing:

Hello rxt 

I think Spark 3.5  requires explicit workspace identification when accessing lakehouse tables, whereas Spark 3.4 allowed implicit resolution through environment defaults.

no direct documentation to support this but

Microsoft Fabric documentation for the Spark connector also emphasizes the need to specify the workspace ID and lakehouse or warehouse item ID when accessing data across workspaces

https://learn.microsoft.com/en-us/fabric/data-engineering/spark-data-warehouse-connector

Hi rxt ,

Thank you for reaching out to the Microsoft Fabric Community Forum.

You're correct that the issue began after upgrading to Spark 1.3 (Spark 3.5). As highlighted by nilendraFabric  thanks for the insight, Spark 3.5 enforces stricter resolution rules and requires explicit identification of the workspace and lakehouse to access tables unlike Spark 1.2, which allowed implicit context.

To resolve the error, please ensure you're using fully qualified references to your lakehouse tables or explicitly set the workspace and lakehouse context in your notebook. This change is in line with platform enhancements for access control and workspace scoping.

Downgrading to Spark 1.2 is a valid temporary workaround, but we recommend adapting to Spark 1.3 for long-term compatibility.

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Thankyou.