The Power Platform line on most EA renewal quotes is the least scrutinized and the most overpriced. Power BI Premium capacity sized for a peak load. Power Apps per user licenses assigned across a population that uses one or two apps. Power Automate licenses purchased independently of the M365 entitlement that already covers the workflow. A clean Power Platform bundle redesign typically saves twenty to forty percent of the existing Power Platform spend at renewal.
Power Platform is structurally four pricing models in one product family. Power BI Premium is capacity priced. Power Apps offers per user and per app license options. Power Automate is split between standalone licenses and the entitlements bundled inside M365 and Dynamics. The bundle work selects the cheapest defensible pricing model per workload, not the model Microsoft account teams default to.
Power BI Premium capacity (the F, P, and EM SKU families) is the largest line on most Power Platform renewals. The capacity is purchased in fixed units sized for peak load. Sustained utilization in most enterprise tenants runs at thirty to fifty percent of capacity. The renewal opportunity is to right size capacity against measured sustained load with documented headroom, then negotiate the new tier against the lower commit. Fabric capacity has compounded this complexity. The buyer side decision is whether the Fabric move is value accretive at the same capacity tier or whether it should be paired with a tier downgrade.
Power Apps per user licenses are priced for unlimited app access. Power Apps per app licenses are priced per user per app. The break even point sits around two to three apps per user. Populations using one or two apps belong on per app licensing. Populations using three or more apps belong on per user. The renewal is the cleanest moment to reassign the entire base.
Five moves drive the Power Platform bundle math at renewal. Each move requires telemetry and each surfaces in the anchor letter to survive the conversation with the Microsoft account team.
Power BI Premium capacity is sized against sustained load with a documented headroom band, not against the peak load on the busiest day. Most enterprise tenants run a third under the capacity they pay for. Right sizing the capacity to current sustained load with a fifteen to twenty percent headroom band typically saves a full tier on the SKU. The savings are protected by an annual ramp clause that allows tier increases if measured sustained load exceeds the threshold.
Per app licensing breaks even against per user licensing at roughly two to three apps per user, depending on tier and market. The bundle work reads per user app consumption across the audit window and moves single app and dual app users to per app licensing. The savings compound across populations that use a handful of internal apps.
Power Automate is included as an entitlement inside M365 and Dynamics for a wide range of workflows that touch first party connectors. The standalone Power Automate Premium license is required only for premium connectors and unattended RPA. The bundle work audits the existing Automate license assignments against the workflows actually running and downgrades the seats where the M365 entitlement is sufficient.
Tenants accumulate multiple Premium capacities over time as different business units stand up workspaces. The renewal opportunity is to consolidate capacities, retire underutilized nodes, and run the workload on a smaller number of larger nodes. Consolidation is operationally complex but produces a meaningful net capacity reduction in nearly every engagement we run.
The Power Platform line is where carry forward pricing is most damaging. Three of the four pricing models are usually wrong for the actual usage pattern.Practice principle · Power Platform engagements
The table below summarizes the typical recovery bands we observe when each lever is applied cleanly in an EA renewal engagement.
| Lever | Telemetry source | Typical recovery |
|---|---|---|
| Premium capacity right size | Capacity metrics app, six month window | 20 to 40 percent of capacity line |
| Per user to per app migration | App access logs | 30 to 60 percent of Power Apps line |
| Automate entitlement substitution | Flow analytics, premium connector usage | 40 to 70 percent of Automate line |
| Capacity consolidation | Workspace utilization per capacity | 10 to 20 percent of capacity line |
| Maker license rationalization | Active maker counts | 15 to 30 percent of maker line |
Across the 28 Power Platform engagements in our practice, the recovery rate at renewal consistently exceeds what the buyer side teams expect at the start of the engagement. The reason is structural. Power Platform pricing complexity (four models, multiple capacities, layered entitlements) creates a default behavior in which buyers carry the existing assignments forward without scrutiny. Microsoft account teams generally do not surface the right sizing opportunities because the Power Platform line is profitable at its carry forward level. The opportunity is therefore concentrated entirely on the buyer side. The work is mechanical. Pull the telemetry, run the per user app analysis, measure sustained capacity load, audit Automate flows against entitlement scope, and surface the new bundle math in the anchor letter. Buyer side teams that complete this work consistently land a Power Platform line twenty to forty percent below the carry forward quote, with the upper band reached when capacity consolidation is included.
The Power Platform bundle redesign produces the strongest outcomes when the work is executed in a specific order. The sequence reflects the underlying dependencies between the four pricing models and the telemetry sources that drive each move.
The capacity utilization audit produces the largest single dollar move and the cleanest data set in the bundle work. The audit measures sustained utilization across a six month window and identifies the headroom band the current capacity tier carries. The right size target is set at sustained utilization plus a fifteen to twenty percent headroom band. The annual ramp clause protects against tier increases if measured load exceeds the threshold mid term.
The Power Apps segmentation work follows the capacity audit. The segmentation reads app access per user across the same six month window and identifies the single app and dual app populations that belong on per app licensing. The migration produces consistent double digit savings on the Power Apps line. The licensing reassignment is operationally complex but the dollar value justifies the work.
The Automate entitlement audit follows the Apps work. The audit cross references standalone Automate Premium licenses against the workflows actually running and identifies the seats that should be running on the bundled M365 or Dynamics entitlement. The downgrade is mechanical and the recovery is real across nearly every engagement we run.
The final step is the maker license audit. The audit identifies active makers (users building Apps or Flows) versus passive users and rationalizes the maker license assignment against the actual making population. The maker population is consistently smaller than the licensed maker base, and the rationalization produces a meaningful recovery on the maker line.
Three patterns from Power Platform bundle redesigns across the practice. Each shapes the renewal math.
Across the 28 Power Platform engagements in our practice, the existing Power BI Premium capacity has been oversized in nearly every case. Sustained utilization in the thirty to fifty percent range is common. The capacity was sized for a peak load that either never materialized or that has since passed. The renewal opportunity is to right size the capacity against measured sustained load with a documented headroom band. The savings are typically one full tier on the SKU. The annual ramp clause protects against the tier increase if measured load exceeds the threshold.
Microsoft account teams default to per user Power Apps licensing because the per user price is higher than the per app alternative for most populations. The buyer side teams that audit app access per user across a six month window routinely identify populations of single app and dual app users that belong on per app licensing. The migration from per user to per app for those populations consistently produces double digit savings on the Power Apps line. The licensing model change requires an operational reassignment but the dollar value justifies the work.
Power Automate is included as an entitlement inside M365 and Dynamics for a wide range of workflows. Standalone Power Automate Premium is required only for premium connectors and unattended RPA. Across our engagements, the audit of standalone Automate licenses against the actual workflows running consistently finds a meaningful share of seats that should be running on the bundled entitlement. The downgrade saves the seat cost and simplifies the licensing footprint. The audit is mechanical but the recovery is real.
The Power Platform bundle work converts into negotiated value at the anchor letter stage, where the buyer side restates the Power Platform line as the right sized total with capacity, per app, and entitlement decisions all documented. Microsoft account teams that receive a fully documented Power Platform bundle anchor cannot credibly argue back to the carry forward total because the data is unambiguous. The probes will continue, but they will be probes against documented telemetry rather than against intent. The buyer side teams that complete the bundle work and then fail to surface it in the anchor letter consistently end the renewal with a Power Platform line near the carry forward number. The act of writing the bundle math into the anchor letter is worth two to four percent of total EA value on its own. The bundle work without the anchor letter is operational hygiene without commercial reward.
Each lever on the renewal interacts with every other lever. The related notes below cover the adjacent posture work.
Two analyst calls. No pitch. We tell you what we would do, what the leverage actually is on your renewal, and whether we are the right firm for this engagement. Buyer side only. Never affiliated with Microsoft.