An IT director at a distribution company got her Power Platform renewal quote back in August and the per-app line item had a note attached: new purchases under that SKU were no longer available through her Enterprise Agreement’s normal channel. She had eleven apps running on per-app capacity packs, covering everything from a driver check-in tool to a rebate approval workflow, and nobody on her team had ever audited whether those apps still needed dedicated capacity or whether half their users had moved to other roles. The renewal conversation, which was supposed to be a formality, turned into a scramble to figure out what she was actually paying for, and into the kind of overdue Power Platform license optimization exercise most IT organizations keep putting off until a contract forces it.
That scramble is becoming common. Microsoft ended new sales of the Power Apps per-app plan on January 2, 2026, and the way that retirement plays out depends entirely on which purchasing channel an organization uses: Enterprise Agreement customers can keep renewing and adjusting counts through their normal true-up process, MPSA customers lose access to the SKU when their current agreement expires and get sixty days to move to something else, and CSP customers were largely unaffected, with the plan returning to availability there in early April. Three different outcomes for the same retirement, depending on how procurement happens to be structured, is exactly the kind of detail that gets missed until a renewal quote forces the question.
The timing matters because it coincides with something genuinely useful: Microsoft has finally shipped a way to see what a Power Platform license estate is actually being used for, instead of relying on procurement records and institutional memory. Getting that visibility in place before the next renewal cycle is the difference between a defensible Power Platform license optimization decision and another round of guessing.
Why Power Platform License Optimization Has Been Mostly Guesswork
Until recently, an organization trying to right-size Power Apps and Power Automate licensing had to stitch together the answer from several disconnected places: the Microsoft 365 admin center for what was purchased and assigned, PowerShell exports like Get-AdminPowerAppLicenses for a point-in-time snapshot, and whatever the CSP or EA reseller could pull from their own systems. None of those sources actually answered the question a CFO cares about, which is how many of the licenses being paid for are being used by someone doing real work in a given month.
The license consumption experience now available (in preview) inside the Power Platform admin center closes that gap. Under Licensing, administrators can pull up Power Apps and see, side by side, per-user licenses purchased against per-user licenses actually consumed by someone who launched an app in the last 90 days, per-app licenses allocated to environments against what was purchased, and any pay-as-you-go billing plans linked in the same view. It breaks down by environment as well as organization-wide, and it will export a CSV of active users, their last app launch, and which license type they used to get in. For an IT director trying to answer “do we actually need eleven per-app packs,” that is the first time the honest answer has been sitting in one screen rather than scattered across three systems and a spreadsheet someone built two years ago.
There is a companion version of this reporting for Dynamics 365 Finance and Operations environments connected through the Power Platform admin center, and it is worth calling out separately because F&O licensing carries its own compliance exposure that per-app and per-user Power Apps licensing does not. That report maps security roles to license requirements and flags users who are under-licensed for the roles they hold, over-licensed relative to what they actually use, or missing a license entirely despite having role access. For a finance organization worried about a true-up or compliance review turning up unlicensed F&O access, that role-to-license breakdown is arguably more valuable than the Power Apps consumption view, because F&O license gaps carry direct compliance risk rather than just wasted spend.
What This Changes About the Renewal Conversation
None of this reporting makes the decision automatically. It gives a CIO or CFO the input needed to make a real one, and there are three moves worth having on the table before the next renewal.
The first is treating the per-app retirement as a forcing function to re-evaluate whether per-app capacity was ever the right model for those specific apps in the first place, rather than assuming the goal is simply to find a like-for-like replacement. An app used constantly by a stable group of forty employees usually still makes sense on a capacity or per-user model. An app used sporadically by three hundred people across the organization, the kind of low-frequency, wide-distribution use case Microsoft explicitly points pay-as-you-go at, is often cheaper and administratively simpler on a consumption model tied to an Azure subscription, where there is no license procurement cycle at all and the organization pays only for sessions that actually happen.
The second is using the consumption report before, not after, the renewal negotiation. A vendor conversation about right-sizing an estate is a different conversation when the buyer walks in with an export showing which per-app allocations have had zero active users in the trailing ninety days versus one built on assumptions. That data also gives Finance a defensible basis for the true-up number instead of an estimate carried forward from the prior year.
The third is recognizing that pay-as-you-go billing plans allow granular cost allocation that traditional licensing does not. Because a billing plan links specific environments to an Azure subscription, and because Azure’s own cost management and resource tagging can then split charges by team or department, an organization running Power Platform across multiple business units can get a real chargeback model instead of a Power Platform budget line that IT absorbs and never breaks down by consumer. That is a meaningfully different conversation for a CFO than “the Power Platform bill went up again this year.”
What to Do Before the Next Renewal
For an organization anywhere in the Power Platform per-app transition, the practical sequence is straightforward even if the underlying decisions are not. Pull the license consumption report for Power Apps and, if applicable, the F&O consumption report, before assuming a renewal quote reflects actual need. Segment the app portfolio by usage pattern rather than by however licenses happen to be allocated today, since a capacity pack purchased three years ago for a pilot may now be covering an app that either died quietly or scaled to a very different usage profile. Confirm which purchasing channel governs the organization’s contracts, since an EA customer facing no disruption and an MPSA customer facing a sixty-day migration window are working against very different timelines, and the MPSA customer in particular should not wait for the renewal notice to start that conversation. And treat pay-as-you-go as a genuine option for the specific subset of apps that fit its profile, rather than a fallback only considered after per-user and per-app options are exhausted.
None of this requires a platform migration or a change to how the apps themselves work. It requires pulling data that, for the first time, is actually sitting in one place, and using it to make a licensing decision on facts rather than habit. Organizations that have gone through a Power Platform license optimization exercise with us tend to find the same thing: the spend was rarely wildly wrong, but it was almost never right, and the gap between those two states is usually worth the afternoon it takes to run the report.
Routeget Technologies works with IT and finance teams on Power Platform governance and licensing reviews as part of broader Dynamics 365 and Power Platform engagements.
#PowerPlatformLicensing #LicenseOptimization #PowerAppsPerApp #PayAsYouGo #PowerPlatformGovernance #ITCostGovernance
No comment yet, add your voice below!