Journey toward the Target Architecture

Adopting Microsoft Fabric is a journey. Business priorities and the desire to unlock new capabilities—such as AI-powered analytics, self-service data governance, or real-time insights—influence how fast an organization matures its Fabric environment.

Over time, organizations iterate and enhance the deployed Fabric services, processes, and skills necessary to reach a scalable, governed, and secure state. This evolution doesn't happen overnight. The journey varies by company size, technical legacy, and internal competencies.

On-Ramps to the Fabric Landing Zone Journey

Imagine your journey as a freeway: multiple on-ramps, one shared direction—the target architecture for Microsoft Fabric. Where you begin determines your initial focus areas.

On-ramp	Description	Further guidance
Start	You begin your Fabric journey (greenfield) and want to implement a new environment based on best practices and patterns.	- What is a Fabric landing zone? - Fabric landing zone design principles
Align	You have an existing Fabric workspace or set of services that need to align with governance and architectural best practices (brownfield).	- Refactor a Fabric landing zone - Transition existing environment
Enhance	Your current implementation is aligned but you want to add features, enforce more policies, or improve operations.	- Improve Fabric operations - Enhance Fabric governance - Enhance Fabric security