Microsoft Data Platform
A HeadToNet publicationMicrosoft architecture & engineering

Make your next Fabric decision with a clearer architecture.

Review where Fabric fits, what should remain in your Azure and enterprise estate, and which modernization decisions need evidence before delivery begins.

Six areas to assess together.

Fabric readiness & workload fit

Where does Fabric fit the decision?

Review use cases, tenant and region constraints, team readiness, workload requirements and services that should remain in Azure or elsewhere.

Synapse-to-Fabric modernization

Which dependencies shape modernization?

Assess dedicated SQL pools, Spark, pipelines and consumers separately; identify compatibility questions, validation needs, cutover constraints and rollback requirements.

Data engineering & integration

How will enterprise data reach its consumers?

Map source contracts, connectors, gateways, identities, transformations, recovery and freshness; compare ingestion, shortcuts and mirroring where supported.

OneLake architecture & governance

Who owns data and effective access?

Review OneLake organization, tenant/workspace/item/data boundaries, ownership, effective permissions, lineage and Microsoft Purview requirements where appropriate.

Power BI & semantic models

Can consumers trust definitions and access?

Review semantic models, report dependencies, storage modes, security, refresh and query patterns, plus author/viewer licensing requirements.

Capacity, performance & cost

What demand and cost drivers need evidence?

Review concurrency, refresh schedules, utilization, performance and sizing assumptions. Identify representative measurements and optimization hypotheses without guaranteeing savings or a capacity SKU.

Bring the architecture you have.

Agree the scope before work begins.

What you can take forward.

Decision brief

An executive account of the platform decision, evidence, assumptions, options and unresolved questions.

Estate & dependency map

The agreed current-state boundary, source-to-consumer dependencies, ownership and retained-service relationships.

Workload-fit matrix

Fabric adoption, modernization and coexistence options, with compatibility and licensing questions made explicit.

Target architecture options

Proposed integration, OneLake, governance and semantic-model boundaries with their tradeoffs and assumptions.

Risk & evidence register

Prioritized risks, evidence gaps and capacity/performance/cost hypotheses for representative validation.

Modernization decision roadmap

Sequenced next decisions, an advisory backlog and a pilot/acceptance outline with cutover and recovery questions where relevant.

A bounded engagement, agreed in stages.

  1. Qualify and bound

  2. Discover and review

  3. Test the decisions

  4. Read out and prioritize

Clear boundaries before delivery.

Start with the platform question you need to answer.

Share the decision, estate boundary and principal constraints. HeadToNet will qualify the request and agree the evidence, scope and commercial terms before work starts.

Discuss a Microsoft Fabric StackAudit