Description:
Today there's no way to fully clone a Fabric workspace: git sync and Deployment Pipelines move item definitions only, not the underlying data; Warehouse's zero-copy CREATE TABLE ... AS CLONE OF explicitly doesn't work across workspaces; and the Fabric CLI's recursive workspace copy (fab cp -r) copies items one by one, not warehouse row data.
This is a real gap for teams running feature-branch or test workspaces provisioned from git — after standing up a new workspace, we have to hand-build separate pipelines/notebooks just to reload representative data, because there's no platform-native "clone with data" step. This is exactly the scenario dbt-style dev/test/prod parity workflows need too.
Ask: a first-class "Clone workspace" action (portal, REST API, and Fabric CLI) that provisions a new workspace with both:
- All item definitions (as git sync/Deployment Pipelines already do), and
- Their underlying data — Lakehouse Delta tables/Files (likely straightforward via OneLake), and Warehouse table data (even a physical copy would help, given cross-workspace zero-copy clone isn't supported).
This would remove the need for bespoke data-reload pipelines every time a team needs a fully working, data-populated copy of a workspace for testing or development.
