Fabric Migration Requirements

• Microsoft Fabric brings together several distinct data and analytics services (called experiences) as a single offering, easing collaboration, deployment, and maintenance.
• Many Fabric experiences are built on existing Azure services but some are not backward compatible.
• Migration effort from the existing services varies, with some requiring a complete re-architecture and deployment.
• To reduce risk, customers can migrate slowly, piece by piece, moving workloads and data separately.

Microsoft Fabric is a data and analytics offering, composed of specialized services (experiences) that can work together, sharing code, processes, data, and security. Some Fabric experiences are new, while others are an evolution of existing Azure services. However, migrating to Fabric experiences is not a lift-and-shift effort, as many of the Fabric experiences are not backward compatible with existing services. Additionally, Fabric uses a new back-end platform that requires redeploying security models and using a new UI, data-sharing concepts, and development tools. (For an overview of Fabric and migration efforts, see the chart “Fabric Migration by Experience”.)