Fabric lakehouse schemas group tables for access and four-part SQL

Lakehouse schemas let Fabric users group tables into named collections—examples given are sales, marketing, and hr. Several features require schema-enabled lakehouses: browsing by business area instead of a flat list; granting teams different schema access and applying row- and column-level security inside schemas; referencing tables with a four-part namespace across lakehouses and workspaces in one Spark SQL query; mapping a schema shortcut to another lakehouse folder or ADLS Gen2 so external Delta tables appear local; and using advanced features such as materialized lake views.

Schemas are enabled by default in the Fabric portal via a checkbox at lakehouse creation; REST API creation must enable them explicitly. A schema-enabled lakehouse always includes a dbo default schema under Tables that cannot be renamed or removed. New schemas are created under Tables; names may contain only letters, numbers, and underscores. Code must include the schema name when saving a table, or the table lands in dbo.

Schemas are a shared namespace for meaning: domain labels on table groups that security and SQL both honor. Four-part names and shortcuts extend that namespace across workspaces and external storage, so the same schema.table identity can be governed and queried without flattening everything into one undifferentiated catalog.