Portfolio rationalization is the engagement that removes the over assignment, the duplication, the shelfware, and the edition mismatch that accumulate across a multi year Microsoft contract. The work is not a cost cut for its own sake. It is the discipline that resets the estate to the actual workload and produces the right size baseline that every downstream negotiation will run against. The renewal negotiates against the rationalized estate. The audit defends the rationalized estate. The optimization compounds against the rationalized estate.
Microsoft enterprise estates drift in one direction. Edition mix shifts toward the higher SKUs. Add on stacks accumulate. Tenant counts multiply through M&A and reorganization. Power Platform capacity is bought against pilots that never went production. Azure subscriptions sprawl through team self service. Each individual decision was rational in the moment. The aggregate is an estate that no one designed, that costs more than the workload requires, and that carries variance exposure no one is tracking.
Rationalization addresses four predictable drift categories. Over assignment, where users are on a higher SKU than their consumption warrants. Duplication, where the same capability is licensed twice through different SKUs. Shelfware, where licenses were purchased against pilots or seasonal demand and never decommissioned. Capacity drift, where Azure subscriptions, Power BI Premium capacities, and Dataverse storage exceed the workload they were sized for.
Each category is addressable independently. The engagement scopes per category, prioritizes by recoverable dollar value, and sequences against operational risk. The customer chooses where the rationalization concentrates against the recoverable opportunity and the change tolerance of the affected business.
The output is the rationalized estate footprint, the documented methodology, and the executed deployment changes. The customer ends the engagement with a smaller, cleaner, defensible estate that matches the workload. The renewal posture work that follows runs against this baseline rather than against the inflated pre rationalization footprint.
Across the practice, portfolio rationalization engagements typically recovered 11 to 23 percent of annual Microsoft spend depending on the size and complexity of the estate. The recovery is durable because it is structural, not negotiated. The estate is genuinely smaller.
Rationalization is a sequenced engagement. Discovery before design. Design before execution. Execution before close out. The phases produce dependencies that earn their place in the order.
Estate scan across M365, Azure, Dynamics, Power Platform. Deployment versus entitlement. Consumption versus deployment. The quantified inventory.
Per category, per product line, the recoverable dollar value. The operational complexity of recovery. The change risk. The prioritized opportunity stack.
The target state estate. The persona ladder. The tenant consolidation map. The capacity right size. The runbook per workstream.
The deployment changes. License reassignment, edition step down, shelfware removal, capacity reset, subscription consolidation. Operational support through the cutover.
The post rationalization estate document. The methodology record. The renewal handoff. The contract memory the next negotiation will run from.
The recoverable opportunity concentrates in six lenses. Each lens runs as its own workstream with its own analyst owner inside the engagement. Workstreams run in parallel where the dependencies allow.
The persona segmentation across E5, E3, F3, Business Premium. The downgrade candidates. The frontline candidates. The Copilot eligibility test. The shape of the right size persona distribution against the workload.
Every add on SKU attached to a base license tested against consumption. Defender for Office, Entra ID Plan 2, Purview, Teams Phone, Audio Conferencing. Where the add on is unused, it detaches. Where two add ons overlap, the redundancy resolves.
MACC commitment versus actual consumption. Reserved instance allocation versus runtime. Hybrid benefit application coverage. Savings plan posture. The Azure commitment right sized against the workload roadmap.
Full user versus team member assignments. Attach licensing across the Dynamics modules. Multiplexing posture review. The Dynamics user count rebased against the actual operational use.
Power BI Premium capacity utilization. Power Apps per app versus per user economics. Power Automate flow inventory and capacity mapping. Dataverse storage and API consumption. The platform sized to the active workload.
Multi tenant estates carry duplicated entitlement and operational overhead. The consolidation analysis identifies which tenants can merge, what the integration cost is, and what the steady state savings deliver. Not every tenant should merge. The analysis is honest about the right number.
Portfolio rationalization fails in three predictable ways when it is run without buyer side discipline. The engagement scopes against each failure mode and structures the work to avoid it.
Reseller led rationalization optimizes for the reseller margin. The recommendations preserve the SKUs the reseller earns the most on. The customer recovers a fraction of the available opportunity and reads the engagement as a success because the dollar recovery is real, even though it is materially below what the buyer side engagement would produce.
An engagement that quantifies the opportunity but does not produce the operational runbook leaves the recovery on paper. The licenses are not actually deprovisioned. The Azure commitments are not actually restructured. The recovery shows up in the slide deck and not in the budget. The engagement design includes the execution layer for this reason.
An estate that is rationalized inside an existing contract releases the dollar value at renewal, not before. Without the contract reset, the customer continues to pay against the inflated commitment for the remainder of the term. The engagement coordinates with the contract calendar so the rationalization timing produces the negotiating leverage at the right moment.
The renewal does not produce savings on its own. Rationalization produces the savings. The renewal converts the rationalized estate into a contract that holds the savings through the term. The two engagements are halves of the same job.Managing analyst · Portfolio and renewal practice
The same four questions surface at the discovery stage of every engagement in this service line. The short answers are below. The full conversation happens against the customer specifics on the first analyst call.
A reseller earns margin on what you buy from Microsoft. Our economics are inverted. We are paid by the customer to reduce or restructure what the customer commits to Microsoft. No SKU we recommend produces revenue for the firm. No customer outcome we deliver compromises a reseller relationship the firm does not hold. The advice is buyer side without qualification, and the engagement structure is built around that posture.
This is the reason most reseller produced analyses recommend keeping the SKUs the reseller earns the most on. Our analyses do not have that incentive. The recommendations follow the customer interest, full stop.
The engagement is buyer side and confidential. Analyst access to customer data runs against a signed NDA with the engagement entity, not against any Microsoft visible data sharing arrangement. The artifacts produced for the customer are not shared with Microsoft unless the customer chooses to share them in negotiation. The methodology footnotes are designed to be defensible if surfaced and silent if not.
The engagement does not surface to the customer Microsoft account team. The seller will see the customer producing better counter analysis than the seller proposed pricing accounts for. The seller will not see the source of the counter analysis unless the customer chooses to disclose it.
Most engagements run as a fixed scope, fixed fee, fixed timeline structure. The fee is set on day one against the scope agreed in the engagement letter. Success based or contingent fee structures are available for specific engagement types where the outcome is cleanly attributable, but they are the exception rather than the default. Buyer side advisory works best when the analyst incentive is to do the right thing rather than to maximize a contingent number.
The first two analyst calls are scoped at no fee and produce the engagement letter only if the fit is right. We do not propose engagements we cannot deliver the outcome on.
The customer provides access to the contract record, the procurement file, the relevant administrative telemetry, and a single point of contact who can authorize the data access and the stakeholder interviews. The engagement does not require dedicated customer resourcing beyond the point of contact. The analyst team runs the work and surfaces findings into the customer cadence.
The data access is scoped tightly. Read only telemetry is sufficient for most workstreams. Where elevated access is required, the engagement scopes the access against a specific runbook with the customer security team in the loop.
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.