Tier 4 · MCA E architecture

The billing account hierarchy is the pricing instrument.

MCA E exposes a three layer hierarchy of billing accounts, billing profiles, and invoice sections. The hierarchy looks administrative. The hierarchy is the cost allocation engine, the chargeback ledger, the discount tier qualifier, and the M&A separation instrument. The architecture decision determines what the buyer can negotiate, what the buyer can charge back, and what the buyer can separate cleanly when the corporate structure changes.

Contact Us MCA E overview →
Savings recovered
$420M+
Across Microsoft renewals, true ups, and audit settlements
Engagements delivered
340+
Fortune 500, mid market, regulated, public sector
Audit exposure cut
79%
Average reduction on formal compliance reviews
Practice depth
20+ yrs
Combined experience across the Microsoft estate
Hierarchy

What the three layers actually do.

Every MCA E estate sits inside a hierarchy of billing constructs. The default architecture Microsoft proposes is a single account, a single profile, and a flat invoice section list. The default works and it forfeits almost every architectural lever the framework was designed to expose. Understanding the three layers is the prerequisite for designing them.

Layer 01
Billing account

The billing account is the contract

The billing account is the legal entity that carries the MCA E commercial relationship. Each billing account ties to a tax registration, a payment instrument, and a signing authority. Most enterprises operate with a single billing account because the simplification looks attractive. Multinational and conglomerate buyers should consider multiple billing accounts for legal entity separation, tax optimization, and audit posture isolation.

  • Tax registration, payment instrument, signing authority
  • Legal entity boundary for audit and indemnification
  • Cannot be split or merged after creation without renegotiation
Set once, lives forever·
Layer 02
Billing profile

The billing profile is the discount unit

Billing profiles sit inside billing accounts. Each profile carries its own invoice cycle, currency, and discount qualification. Volume tier eligibility is computed per profile by default. The number of profiles, the spend in each, and the alignment with business unit boundaries determine the concession the buyer is eligible for.

  • Invoice cycle, currency, payment terms set per profile
  • Volume tier qualification per profile, not per account
  • Profile spend visible to procurement and to the deal desk
Architecture is pricing·
Layer 03

Invoice sections

Invoice sections sit inside profiles and slice spend for chargeback. Sections do not affect pricing but do affect cost transparency. Used well, sections deliver business unit P&L visibility the EA never offered.

Layer 04

Subscriptions attached

Azure subscriptions, M365 tenants, and Dynamics environments attach to invoice sections. The attachment is what routes consumption to the right ledger. Default attachment routes everything to one section.

Layer 05

Tenant overlay

Microsoft Entra tenants are a separate construct from billing accounts. Tenant design and billing architecture must be aligned, not assumed identical. The mismatch is where many estates accumulate operational friction.

Leverage

What the architecture unlocks.

The billing architecture lever is one of the few buyers control unilaterally without negotiation. The leverage is real, large, and almost universally underused because the procurement function rarely owns architectural decisions inside the Microsoft portal.

Lever 01

Tier qualification

Consolidate qualifying spend into fewer profiles to clear higher volume tier thresholds. The mechanic is direct: the qualifying number is per profile, the higher tier carries a meaningful concession step, and consolidation is administrative work, not negotiation work.

Lever 02

Chargeback truth

Profile and section design that mirrors the buyer P&L creates chargeback ledgers that match how the business reports internally. The reconciliation friction at month end drops. The cost visibility at the business unit level becomes negotiable internally.

Lever 03

Currency discipline

Multinational estates can set profile currency to match the underlying business unit reporting currency. The translation noise that complicates EA reconciliation disappears. The CFO sees consumption in the currency the budget is denominated in.

Lever 04

Audit scope

Audit posture can be applied at the account or profile level. Buyers can isolate the regulated business unit profiles from the rest of the estate and negotiate stricter audit terms only where the regulatory regime requires them.

Lever 05

M&A separability

Designing profiles to match plausible separation lines protects the buyer in carve out scenarios. The divested business unit can take its profile with it in a much cleaner motion than untangling consumption inside a single profile.

Lever 06 · Underused

Discount renegotiation windows

Each profile renewal creates a discrete renegotiation moment. Buyers who stagger profile anniversaries deliberately create rolling renegotiation events that maintain procurement engagement without imposing a single annual cliff.

Common traps

What goes wrong in the design.

Five recurring architectural traps account for most of the value leakage we see when EA shops migrate to MCA E. The patterns repeat because the migration is usually treated as an operational task rather than an architectural one.

Trap 01
Most common

Single profile default

Buyers accept the default single billing profile because the migration motion does not surface the alternative. The result is a flat structure that disqualifies the buyer from many of the architectural levers the framework offers. Profile design must precede migration, not follow it.

Trap 02

Profile sprawl below threshold

The opposite mistake also occurs. Buyers concerned with chargeback granularity create too many profiles, each falling below the volume tier threshold. The lost concession on each profile aggregates to a meaningful annual cost. Profile count is a tradeoff, not a preference.

Trap 03

Profile boundary cross misaligned

Profiles drawn by geography conflict with profiles drawn by business unit. The same spend cannot be allocated cleanly to both. Buyers who do not pick a primary segmentation axis end up with profiles that satisfy neither stakeholder. The design has to choose.

Trap 04

Tenant tenant mismatch

Tenant boundaries set in Entra do not automatically match profile boundaries set in billing. The mismatch produces consumption that cannot be allocated cleanly to a section. The cleanup requires a tenant migration, which is operationally expensive and politically painful.

Trap 05 · Quiet but expensive
Carve out exposure

Designing for the current organization, not the next one

The most expensive architectural mistake is designing the billing profile structure against the current org chart without considering plausible carve outs, spin offs, or acquisitions over the next three years. When the corporate event happens, the buyer discovers that consumption cannot be cleanly separated, the divested business cannot take its commitments with it, and the M&A counsel has to negotiate a side agreement to manage the entanglement. The cost is usually invisible until it appears. The fix is unavoidable when it does. Design the architecture against the plausible corporate trajectory, not against the current org chart alone.

Our angle

How we advise billing architecture.

The practice runs a defined design exercise on billing architecture before any subscription is provisioned. The exercise produces a blueprint that procurement, finance, and IT can sign off on collectively. Without the blueprint the default architecture wins by inertia.

We start by mapping the buyer organization against three trajectories. The current state map captures business units, geographies, and legal entities as they exist today. The reporting state map captures how finance reports internally, which is rarely identical to the current state. The corporate trajectory map captures plausible carve outs, divestitures, and acquisitions over the next three years. The three maps inform the profile boundary decisions.

We then run the tier qualification math. Each plausible profile design produces a different volume tier eligibility profile. We model the concession capture under each design and surface the tradeoff against the chargeback granularity and the carve out separability. The math frames the design conversation. Without the math the design conversation is opinion against opinion.

The design closes with a tenant alignment check. The billing architecture has to match the tenant architecture or the consumption will not flow cleanly into the right sections. Misaligned designs produce operational friction at month end that erodes the architectural benefit over time. The check catches the misalignment before it is provisioned.

Once the blueprint is approved, we provision against it deliberately. Subscriptions, tenants, and commitments are attached to the right profiles and sections from day one. The provisioning order matters because reorganizing after the fact triggers commercial events Microsoft will use as renegotiation moments. We give Microsoft none of those moments by getting the architecture right at the start.

Our buyer side independence matters here because the integrators advising migration almost universally have margin on the operational provisioning work. We have no margin on any of it. The architecture we recommend is the architecture that serves the buyer across the next decade, not the architecture that minimizes the implementation invoice.

Outcome

One representative architecture engagement.

Anonymized but verifiable on reference call. Drawn from active engagements in the trailing twelve months.

Architecture redesign · Multinational holding company · 19,000 seats

A multinational holding company redesigned its billing architecture and recovered $14M annually.

The buyer had migrated to MCA E with a single billing profile because the migration motion did not surface alternatives. Twelve months later, an acquisition exposed the inability to separate the acquired entity cleanly. We redesigned the architecture around the holding company structure, consolidated qualifying spend to clear the next volume tier, and aligned tenant boundaries to profile boundaries. The architectural changes were administrative. The recovered concession was material.

We thought billing structure was an accounting question. It turned out to be a procurement strategy question we had answered without realizing.Group Treasurer · Multinational holding company
Annual concession recovered
$14M
Tier clearance
+1
Profiles redesigned
11
Tenant alignment
100%
Timeline
10 wks
Design patterns

The four canonical architectures.

Across the practice the billing architectures that work cluster into four patterns. Each pattern serves a different buyer profile. None of them is the Microsoft proposed default. The buyer who picks the pattern deliberately captures the architectural lever the default forfeits.

Pattern 01
Holding

Holding company pattern

Multiple billing accounts at the legal entity level, each with profiles aligned to operating subsidiaries. Used by diversified holding companies and private equity portfolios. Maximizes carve out separability and isolates audit posture per entity. Cost is administrative overhead at the account level.

Pattern 02
Consolidated

Consolidated enterprise pattern

One billing account, two to four profiles aligned to division or geography. Used by integrated enterprises with stable organizational boundaries. Maximizes volume tier qualification while preserving meaningful chargeback granularity. Cost is reduced flexibility on entity level separation.

Pattern 03
Regulated

Regulated business unit pattern

One billing account with profiles segregating regulated business units. Used by financial services, healthcare, and defense contractors. Isolates audit posture and compliance reporting per regulatory regime. Cost is duplicated administrative effort across profiles with similar consumption profiles.

Pattern 04
Acquirer

Active acquirer pattern

One billing account with profiles reserved for incoming acquisitions. Used by serial acquirers who need clean integration paths for purchased entities. Maximizes M&A flexibility while preserving consolidated negotiation posture. Cost is unfilled capacity in reserved profiles between deals.

Initiate engagement

Write before the quote becomes a position.

Two analyst calls. No pitch. We tell you what we would do, what the leverage actually is, and whether we are the right firm for this engagement.

Who we work for.Buyer side only. No reseller relationship with Microsoft. No partnership of any kind. We earn nothing from products sold or renewed, only from outcomes delivered against the contract.