Scenario:
We are planning to migrate Microsoft Fabric artifacts across tenants using Azure DevOps.
I would like to understand the feasibility of this approach and identify which Microsoft Fabric artifacts can be migrated using an Azure DevOps pipeline.
Migration Approach:
We have two Azure tenants: Tenant 1 and Tenant 2. Tenant 2 has its own Azure DevOps Services environment.
The requirement is to migrate Microsoft Fabric items from a workspace in Tenant 1 to a Microsoft Fabric workspace in Tenant 2.
To achieve this, I am planning to:
- Configure Git Integration for the Fabric workspace in Tenant 1 using a Service Principal.
- Commit the Fabric artifacts to an Azure DevOps repository in a dedicated folder (for example, Fabric Artifacts) within a repository branch.
- Create an Azure DevOps YAML pipeline along with a Python script that dynamically deploys the artifacts from the repository into the target Fabric workspace in Tenant 2.
- Use the attached Python script to automate the deployment process.
We currently have the following artifact types in the source Microsoft Fabric workspace. I would like to understand whether there are any limitations with this approach and if all of these artifacts can be migrated successfully using an Azure DevOps pipeline.
| Artifact Types |
| Activator |
| CopyJob |
| DataflowFabric |
| Environment |
| EventStream |
| GraphQL |
| KustoDatabase |
| KustoEventHouse |
| Lakehouse |
| MLExperiment |
| MountedRelationalDatabase |
| Pipeline |
| SQLDbNative |
| SynapseNotebook |
| User Data Functions |
| Variables |
| Warehouse |
| Dataset |
| OrgApp |
| PaginatedReport |
| Report |
