I used AI tools to help draft and edit this post. I checked the facts and the wording, and the original lives at geekindata.com . The diagrams are on that page.

Packaging follows ownership

Key takeaways

Treat medallion as meaning; treat lakehouses and schemas as packaging.

Prefer one schema-enabled lakehouse when layers share a domain, team, and release train.

Prefer separate lakehouses when ownership, sensitivity, or failure windows are real.

Enable schemas at create time; late discovery means recreate cost and id churn.

Parameterize lakehouse id, schema, and environment; never hard-code display names.

Draw the connection map before any consolidate or split; budget for rebinds.

Medallion architecture asks where bronze, silver, and gold live. In Fabric you can answer with many lakehouses or with schemas inside one lakehouse.

That choice leaks into shortcuts, SQL endpoints, notebooks, CI/CD, and how painful renames become later. It is not a folder preference.…