Is it possible to do automatic selective deployment in our ADO pipeline deploying to Fabric WS?

Community Support

9 months ago

Please refer to below useful links:

Limitations:

The first-time sync of a workspace (e.g., when you connect a new branch/folder) will typically pull all items in that folder/branch. The docs label it like “If called after the Connect and Initialize Connection APIs, it will perform a full update of the entire workspace.”
When you switch branches or change the directoryName mapping, items present in the old branch/folder but not in the new one get deleted.
There’s no documented parameter in updateFromGit for “deploy only these paths/files” (at least in the public doc as of now). So full control is indirect (via folder/files structure) rather than native “include/exclude list”.
Permissions: Make sure your Service Principal has all required scopes and the workspace has capacity etc. Permissions issues show up if scope insufficient.
You’ll need good CI logging/tracking to ensure items you expect to deploy were actually deployed.

I’d encourage you to submit your detailed feedback and ideas via Microsoft's official feedback channels, such as the Microsoft Fabric Ideas.

Feedback submitted here is often reviewed by the product teams and can lead to meaningful improvement. since clearer guidance would definitely help capacity administrators interpret these metrics more confidently. This helps the product group prioritize improvements, and the more customers that raise this, the faster it gets addressed.

Thanks,

Prashanth Are

MS Fabric community

Forum Discussion