Show Notes
Copy Job promises Pipeline power with Mirroring simplicity. But incremental mode charges double the CU rate, and that's before V-Order compression and per-table rounding stack on top. We do the maths.
More from Microsoft Fabric Architecture Podcast
Databricks and Fabric have five integration paths, not one. Each moves data. None moves permissions. We pull apart the one-credential model, the hour-long revoke delay, and the ADLS shortcut that silently bypasses Unity Catalog's row-level security.
Fabric doesn't charge you when work happens — it spreads the cost forward into 2,880 thirty-second timepoints. That one sentence explains every confusing capacity behavior, including why surge protection can reject the SQL it's supposed to protect.
Fabric domains look like governance boundaries but the documentation says otherwise. We unpack what a domain actually gives you, the default-domain mechanism that's still running in your tenant, and why the label on the cabinet is not the lock.
Cosmos DB has no schema. Delta tables need one. When mirroring bridges the two, the replicator guesses — and the guess only ever widens. We trace where the bytes come from, why renamed properties leave ghost columns full of nulls, and what stop replication actually does.
A workspace carries four boundaries — security, cost, region, lifecycle — and you configured one of them. This episode pulls apart what 'read-only' actually means in Fabric, why OneLake security cannot fence in a Contributor, and the silent security change hiding inside every role promotion.