Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
schneiw
Advocate II
Advocate II

Deployment pipeline with feature branch/workspace

Hi

 

New to fabric but come from SSIS. 

 

Trying to set up Deployment Pipelines in conjunction with Git and undertand how Dev > Test > Prod work. And if I understand it correctly the deploymentrules to some extend help correct your environment connections (i.e. objects in Dev point to dependant objects in Dev etc.) 

 

I want to use the "branch out to new workspace" for our devops process for developers to create their feature branches. However, since I have a deployment pipeline that include my Dev, Test, and Prod workspaces, I cannot create another deployment pipeline for each developer to deploy from their feature branch workspace to the Development workspace (specifically I cannot choose Dev workspace again, since its in another deployment pipeline already). Yes, I understand that you can use Git to do a pull request, but then you get none of the functionality of the Deployment pipelines that lets you set up deployment rules, autobinding etc. What am I missing?  How to you set up a deployment pipeline to deploy from feature branch workspace to Devlopment workspace? 

1 ACCEPTED SOLUTION
suparnababu8
Super User
Super User

Hello @schneiw 

 

  • Set up  temporory testing space where your developers can upload and try  their new features before finalizing them.
  • Now, this workspaace serves as a temporary space where changes were tested beffore being added to the main development area.
  • Use Git to organizee different featurre updates, allowing ur developers to work saparately on new changes and then combine them into the main project.
  • After mergiing the changes, follow your existingg Dev -> Test -> Prod deployment process to move updates from ur  main development workspace to production.

Try this and let me know if it works.

 

Pls follow below links, it might helps you

CI/CD workflow options in Fabric - Microsoft Fabric | Microsoft Learn

mslearn-fabric

Git integration and deployment for data pipelines - Microsoft Fabric | Microsoft Learn

Fabric environment Git integration and deployment pipeline - Microsoft Fabric | Microsoft Learn

 

Thank you!!!

 

Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

View solution in original post

3 REPLIES 3
v-sgandrathi
Community Support
Community Support

Hi @schneiw,

Thanks for reaching out with such a detailed question and big thanks to @nilendraFabric  and @suparnababu8 for sharing a thorough explanation! They've covered the core points very well.

 

Just to add a few additional points that might help you even further:

Along with creating temporary feature workspaces, some teams also maintain a staging workspace where merged changes are validated once again before promoting them from Dev to Test.

While merging feature branches back into main, it’s a good practice to have a Pull Request checklist like verify dataset parameters, connection strings, object names to avoid small issues later in promotion stages.

If needed, you can also enable Auto-Deployment from Git to your Dev workspace. This way, every time a PR is merged, your Dev workspace gets automatically updated without manual syncs.

 

I hope this helped! Feel free to ask any further questions. If this resolved your issue, please mark it as "Accept as Solution" and give us Kudos to assist others.

 

Thank you.

nilendraFabric
Super User
Super User

@schneiw 

adding some more details for your information 

  1. Deployment Pipelines are designed for promoting content between fixed environments (Dev → Test → Prod) with deployment rules for managing connections between environments

  2. Git Integration allows for branching strategies where developers can work in isolated feature branches/workspaces and then merge changes back to the main branch

  • A workspace can only be part of one deployment pipeline

  • You cannot include a feature branch workspace in the main deployment pipeline

  • You cannot create separate deployment pipelines that include the same Dev workspac



I use this apprioach 

  1. Connect your Dev workspace to the main branch in your Git repository

  2. Developers branch out to their own workspaces using the "Branch out to another workspace" feature

  3. Development happens in isolated feature workspaces where developers can make and test changes

  4. Use Pull Requests to merge changes back to main which will then update the Dev workspace

  5. Use Deployment Pipelines only for promoting from Dev → Test → Prod after changes are merged to main

suparnababu8
Super User
Super User

Hello @schneiw 

 

  • Set up  temporory testing space where your developers can upload and try  their new features before finalizing them.
  • Now, this workspaace serves as a temporary space where changes were tested beffore being added to the main development area.
  • Use Git to organizee different featurre updates, allowing ur developers to work saparately on new changes and then combine them into the main project.
  • After mergiing the changes, follow your existingg Dev -> Test -> Prod deployment process to move updates from ur  main development workspace to production.

Try this and let me know if it works.

 

Pls follow below links, it might helps you

CI/CD workflow options in Fabric - Microsoft Fabric | Microsoft Learn

mslearn-fabric

Git integration and deployment for data pipelines - Microsoft Fabric | Microsoft Learn

Fabric environment Git integration and deployment pipeline - Microsoft Fabric | Microsoft Learn

 

Thank you!!!

 

Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

Helpful resources

Announcements
Fabric July 2025 Monthly Update Carousel

Fabric Monthly Update - July 2025

Check out the July 2025 Fabric update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.