Forum Discussion
Deploy Fabric Artefacts with folder structure
- Anonymous1 year ago
Hi WGW ,
Thanks for reaching out to the Microsoft Fabric community.
We understand that keeping the folder structure intact while deploying an end-to-end Fabric solution is important, and currently, Git integration in Fabric does not retain workspace folder structures. However, there are a few approaches that might help you achieve what you're looking for.
1. Using Deployment Pipelines:Fabric’s Deployment Pipelines support folder structure preservation when promoting content across environments (Dev --> Test --> Prod). If your goal is to move all artifacts while keeping them organized, setting up a deployment pipeline might be the best option.
You can either deploy everything at once or choose specific items to move while maintaining the workspace structure. More details on how this works can be found here: https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process
2. Automating Deployment with REST APIs:If Deployment Pipelines don’t fully meet your needs, another approach is to use Microsoft Fabric REST APIs to manually recreate the folder structure in the target workspace.
You can start by retrieving artifacts from the source workspace using the List Items API, which provides a list of active Fabric and Power BI items. After that, you can deploy them into the new workspace while preserving the structure.
3. Using Azure DevOps for Version Control & CI/CD:
While Fabric’s Git integration doesn’t store folder structures, you can still organize your deployments effectively by using Azure DevOps repositories. One common approach is to maintain separate folders for different environments (Dev/Test/Prod) within a single repository.
Two Git branches (Test & Release) can be used to connect to their respective workspaces, ensuring better version control and a structured, scalable deployment workflow.
Git-based folder structure retention is a highly requested feature, and it is planned for future updates. Microsoft is continuously enhancing Fabric, so I recommend staying updated on the latest feature releases through the Microsoft Fabric Blog
Hope this helps. Let us know if you have any specific questions or if there’s anything else we can assist with.
If this post helps, then please consider "Accept it as the solution" to help the other members find it more quickly and a kudos would be appreciated.Best regards,
Vinay.
Hi WGW ,
Thanks for reaching out to the Microsoft Fabric community.
We understand that keeping the folder structure intact while deploying an end-to-end Fabric solution is important, and currently, Git integration in Fabric does not retain workspace folder structures. However, there are a few approaches that might help you achieve what you're looking for.
1. Using Deployment Pipelines:
Fabric’s Deployment Pipelines support folder structure preservation when promoting content across environments (Dev --> Test --> Prod). If your goal is to move all artifacts while keeping them organized, setting up a deployment pipeline might be the best option.
You can either deploy everything at once or choose specific items to move while maintaining the workspace structure. More details on how this works can be found here: https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/understand-the-deployment-process
2. Automating Deployment with REST APIs:
If Deployment Pipelines don’t fully meet your needs, another approach is to use Microsoft Fabric REST APIs to manually recreate the folder structure in the target workspace.
You can start by retrieving artifacts from the source workspace using the List Items API, which provides a list of active Fabric and Power BI items. After that, you can deploy them into the new workspace while preserving the structure.
3. Using Azure DevOps for Version Control & CI/CD:
While Fabric’s Git integration doesn’t store folder structures, you can still organize your deployments effectively by using Azure DevOps repositories. One common approach is to maintain separate folders for different environments (Dev/Test/Prod) within a single repository.
Two Git branches (Test & Release) can be used to connect to their respective workspaces, ensuring better version control and a structured, scalable deployment workflow.
Git-based folder structure retention is a highly requested feature, and it is planned for future updates. Microsoft is continuously enhancing Fabric, so I recommend staying updated on the latest feature releases through the Microsoft Fabric Blog
Hope this helps. Let us know if you have any specific questions or if there’s anything else we can assist with.
If this post helps, then please consider "Accept it as the solution" to help the other members find it more quickly and a kudos would be appreciated.
Best regards,
Vinay.