If you're building a Power Apps Code App (React + TypeScript + Dataverse), there's
one requirement that can kill an otherwise finished project: every end user needs
a Power Apps Premium per-user license.
Not a per-app license. Not a free tier. A Premium license, per person, for
every single user who will open the app.
This sounds obvious once you say it out loud - but it's easy to miss during
scoping, especially when the business asks for "an app for everyone in the
company." I've seen this surface after an application was fully built,
tested, and approved by the business: the project was technically done, and
licensing is what put it on hold.
Why this matters more than it seems
- Power Apps Code Apps run on Dataverse, and Dataverse access via a custom app isn't covered by the free/basic tiers most organizations already have for Microsoft 365.
- The cost scales with headcount, not with app complexity. A simple five-screen app for 2,000 employees can be far more expensive to license than a complex app for 50 people.
- Procurement and budget approval for licensing often takes longer than building the app itself.
What to do instead
Ask this question before writing the first line of code, not during UAT:
"Who exactly will use this app, and do they already hold a Power Apps
Premium license for another reason?"
If the answer is "everyone in the company" or "we don't know yet," that's your
signal to escalate licensing to a budget conversation immediately - not a
technical one. A project that's code-complete but licensing-blocked is a
worse outcome than a project that never started, because by then the
business has already committed expectations.
Takeaway
Technical excellence doesn't protect a project from a licensing model nobody
priced in. If you're scoping a Power Platform Code App, put the licensing
question in the very first round of requirements - right next to "how many
levels does the approval workflow have."
I work on Power Platform / Dataverse architecture (Code Apps, Power Automate,
approval workflows, multi-entity permission models). Happy to discuss your
project's architecture if you're scoping something similar.
Top comments (0)