PAID, FIXED-SCOPE ASSESSMENT

Make shared Fabric capacity accountable before the next renewal, scale decision or incident.

The Fabric Economics Assessment connects the commercial bill, Microsoft-native usage evidence and the customer’s ownership context. It creates a defensible baseline, a draft policy, an exceptions ledger and a decision-ready intervention plan — then asks the customer whether a recurring close is valuable.

Target delivery
Three weeks after the Data-Ready Notice.
Commercial status
Fixed scope, quoted through an objective estate-complexity rubric.
Delivery
Professional services through FabOps Operate.
Required participation
Platform and Finance or FinOps methodology owners.

START WITH THE TRIGGER

A live Fabric accountability decision must exist.

The assessment is designed for a renewal, bill, capacity, ownership or intervention decision — not for a generic dashboard request.

  • Capacity renewal or reservation
  • Unexpected bill or variance
  • Throttling or overage event
  • Executive cost or accountability mandate
  • Rapid AI workload growth
  • Disputed shared consumption
  • Inability to assign owners
  • Requirement to prove whether an intervention worked

Entry criteria

Required

  • Shared or complex Fabric estate
  • Active trigger and consequence
  • Executive or economic sponsor
  • Platform champion
  • Finance or FinOps methodology participant
  • Bill, commitment and native usage evidence route
  • Ownership context
  • Security and procurement route
  • Buyer decision plan

Defer or disqualify

  • No active problem
  • No Finance or evidence route
  • Generic dashboard request
  • Guaranteed savings or formal accounting chargeback required
  • General cloud FinOps request
  • Material bespoke software needed before the assessment
  • Procurement falls outside the current proof window with no viable route

OBJECTIVE COMPLEXITY

The quote follows the estate, evidence and assurance required.

Public experiment prices remain withheld while commercial, legal and claims review is open. Scope is classified through the factors below; the complex band is not unlimited complexity.

BOUNDED

Bounded estate

  • One or a small number of capacities
  • Limited SKU and commitment complexity
  • Manageable number of owners
  • Substantially available ownership data
  • Aligned billing and usage periods
  • Standard evidence and access route
  • One primary platform and Finance approver

COMPLEX / MULTI-CAPACITY

Complex estate

  • Several capacities, SKUs or commitments
  • Multiple domains or cost centres
  • Fragmented ownership
  • Several approvers
  • Service-principal ambiguity
  • Restricted-access or regulated handling
  • Multiple reconciliation anchors
  • Historical or seasonal complexity

Out of rubric: narrow, phase, separately scope through FabOps Operate or Onyx consulting, or defer.

DATA-READY GATE

The delivery clock starts only after written Data-Ready notice.

The minimum pack connects commercial, native usage and ownership evidence for an agreed period.

  • Fabric or Azure billing, Cost Management or FOCUS evidence for the agreed period
  • Capacity Metrics, Chargeback or an approved equivalent native usage source
  • Capacity and SKU inventory
  • Contract, rate, reservation or commitment context where applicable
  • Workspace, item, domain or tag inventory
  • Ownership and cost-centre map
  • Finance methodology owner
  • Secure transfer or access path

Critical prerequisite

A missing item prevents the method or clock start.

Degradable limitation

Work can continue with lower confidence and a disclosed exception.

Optional enrichment

The input improves the decision but is not required.

WHAT WE DO

From evidence intake to a written recurrence decision.

  1. 01

    Intake and Data-Ready

    Classify evidence, quality, period alignment and limitations.

  2. 02

    Reconciliation

    Connect bill and commitment evidence to native usage, disclose coverage and explain variance.

  3. 03

    Ownership and policy

    Map consumption where evidence supports it; draft shared-cost, idle-capacity and exception treatment.

  4. 04

    Confidence-rated showback

    Show allocated, unallocated and disputed amounts with source, method, version and confidence.

  5. 05

    Intervention and verification

    Prioritise opportunities and state the guardrails, owner, expected mechanism and measurement card.

  6. 06

    Executive readout

    Review with platform and Finance participants; record accepted, provisional and disputed states.

  7. 07

    Recurrence decision

    The customer selects one of four outcomes in writing.

What the customer receives

  • Intake and evidence-quality report
  • Reconciliation statement
  • Ownership and shared-cost policy draft
  • Allocation and showback working paper
  • Exception and dispute ledger
  • Intervention register
  • Verification cards
  • Board or executive readout
  • 90-day plan
  • Recurrence decision
  • Data deletion and offboarding evidence as contracted

ACCEPTANCE AND CONFIDENCE

A polished output does not hide uncertainty.

Draft

Not customer reviewed.

Methodology reviewed

Comments are recorded.

Accepted with exceptions

Disputed or low-confidence items are identified.

Accepted

The customer confirms the criteria are met.

Provisional

A required approver is unavailable; no Finance-accepted claim is made.

Target method controls

  • At least 80% bill reconciliation where the evidence supports it
  • A 70–85% allocation range where the data supports it
  • Unallocated amounts disclosed rather than forced
  • Below-60% critical data quality triggers a pause or scope decision
  • Second-person calculation QA
  • Formula and method version with evidence IDs

Targets are method gates, not guaranteed customer results.

VALUE CLASSIFICATION

Observed is not realised.

  1. 01

    Observed

    A condition exists.

  2. 02

    Addressable

    It may be changed under the customer’s constraints.

  3. 03

    Approved

    The customer accepts the action, owner, guardrails and method.

  4. 04

    Realised

    The result is measured and accepted.

Only realised, customer-confirmed financial results may be discussed as realised savings. The FEA normally produces observed, addressable or approved evidence and a verification plan — not instant realised value.

FOUR VALID ENDINGS

The assessment does not force a subscription.

Quarterly customer-run Accountability Close

The initial default recurring-product hypothesis.

Monthly customer-run Accountability Close

An enterprise-custom route for sufficient complexity and economics.

90-day intervention-verification cycle

A bounded services and evidence route without assuming recurring software.

No recurring requirement

A valid conclusion. The customer retains the assessment evidence; Onyx does not force a subscription.

COMMERCIAL AND TRUST BOUNDARIES

The engagement states what it does, where it runs and what is not included.

The engagement-specific route states where work executes, what authorised evidence moves, who can access it, retention and deletion. No universal architecture statement substitutes for that schedule.

Outcome-data permission is separate, explicit and optional. Case-study consent is separate. Declining does not reduce the purchased deliverables.

Review the current trust statement

Not included

  • Accounting or general-ledger chargeback
  • Guaranteed savings
  • Implementation of all interventions
  • General cloud FinOps
  • Broad Fabric migration or build
  • Cross-customer benchmark output
  • Statutory assurance
  • Unlimited support

CONDITIONAL TRANSACTION ROUTE

Microsoft Marketplace

Where current eligibility and billing arrangements permit, the FEA may be transacted as professional services through a Microsoft Marketplace customer private offer.

Security, legal, DPA, architecture, procurement and customer purchase approval may still be required. The route is never represented as decrementing MACC or Azure commitment, eliminating vendor onboarding or applying to every customer or geography.

COMMON QUESTIONS

Before qualification

Why pay for this if Microsoft has Chargeback and Capacity Metrics?

Those tools can provide important native evidence. The FEA tests the additional customer-specific job: commercial reconciliation, ownership policy, confidence and exceptions, accepted actions and a verification method.

Is this a chargeback implementation?

No. The initial method is transparent management showback. Formal chargeback and accounting treatment belong to the customer’s Finance policies and any later approved scope.

Will you identify savings equal to the fee?

No guarantee is made. The assessment records evidence and opportunities, separates value states and states how approved interventions would be verified.

What happens if data quality is poor?

Critical missing evidence can pause or delay the clock. Degradable limitations are disclosed with lower confidence and exceptions rather than hidden.

Must we buy FabOps afterwards?

No. The written ending can be a customer-run close, a 90-day verification cycle or no recurring requirement.

QUALIFICATION ROUTE

Find out whether there is a real Fabric accountability decision worth assessing.

The qualification call tests the trigger, estate, Finance route, evidence, security and buyer decision. It is not a free mini-assessment and does not force a product outcome.

Before submitting

  • A platform owner and Finance or FinOps methodology participant must be available.
  • Billing, commitment and Microsoft-native usage evidence must have a viable route.
  • The assessment does not guarantee savings or provide accounting-grade chargeback.
  • Security, legal, data-protection, architecture, procurement and customer purchase approval may still be required.

Review customer results