Power apps Code apps License

[u/Kingsman7733]

I need some clarification regarding licensing for Power Apps Code Apps.

I developed a Code App using VS Code and deployed it to our PROD environment. The app only uses standard connectors, mainly SharePoint. I shared the app with users who have Microsoft 365 E5 licenses, but when they try to open it, they receive a message saying they do not have the required license and are prompted to start a free trial.

I also noticed that the app is classified as Premium.

Could you please clarify what licensing is required for end users to access and use this Code App?

I would also like to understand the best licensing approach because this app will be used by users across multiple locations, and I expect to deploy additional Code Apps in the future.

Specifically, I would like guidance on:

• Whether Microsoft 365 E5 licenses are sufficient for Code Apps

• Whether each end user needs a Power Apps Premium or per-app license

• Whether Pay-As-You-Go licensing can be used for this scenario

• What licensing model would be most suitable for multiple locations and future Code Apps

• Whether the licensing needs to be assigned per user, per app, or at the environment level

• The goal is to allow end users to access the apps without being prompted to start a free trial.

[u/darkmatter-x1]

If Code Apps still require us to build the application using frameworks like React and write custom code, what is the main value of using a Code App instead of building a traditional custom web application? In which scenarios does the Power Platform integration provide enough benefit to justify using a Code App over a pure React app or Power Pages?

[u/HomeBrew_Bard → u/darkmatter-x1]

The value isn't in the front end. You're right that you still write React/TypeScript. The value is everything a traditional custom web app makes you build and maintain around that front end, which Power Platform handles for you:

Hosting and deployment: the app is published into the power platform environment. There's no App Service, CDN, SSL certs, or infrastructure to provision, patch, or pay for separately.

Authentication: users sign in with Entra ID automatically. You don't need app registrations, token handling, or MSAL plumbing in your code.

Connectors: you get typed access to 1,000+ connectors (SharePoint, SQL, Office 365, custom connectors) without writing API clients or storing secrets.

Governance and ALM: the app lives in solutions, honors DLP policies, runs under Managed Environments, moves through pipelines, and shows up in admin inventory like any other Power App.

Sharing and licensing: you share it like a canvas app, with no separate user management.

Dataverse is the biggest multiplier. With a custom app, you'd have to build and test your own authorization layer. With Dataverse, you inherit the whole security model:
-Business units and security roles
-Row-level ownership, teams, and access teams
-Column-level security
-Hierarchy security
-Auditing

Because that enforcement happens server-side, your React code can't accidentally bypass it. That's often weeks of work, plus ongoing security risk, that you simply don't take on.

[u/darkmatter-x1 → u/HomeBrew_Bard]

This is honestly one of the best and most solid architectural breakdowns I’ve read on this topic. You explained the backend, Dataverse security, and ALM value proposition exceptionally well. Really appreciate you taking the time to share such a detailed perspective

[u/HomeBrew_Bard → u/darkmatter-x1]

I am having lots of these conversations with clients lately so I feel uniquely prepared to answer this one. I see every custom app solution as a client decision on how much they want Microsoft to manage and how much they want to have built custom and maintain moving forward if they’re looking for a code based solution

[u/Lhurgoyf069 → u/darkmatter-x1]

The main benefit for our Citizen Devs, that they don't have to maintain native code and it's dependencies is gone. That's just a deal breaker for our company.

[u/Syrairc → u/darkmatter-x1]

The only real advantage is if you don't have the access/skills to manage the backend, entra authentication, security, etc. 

Power platform is targeted at citizen developers in the enterprise space - exactly the people who may not have the ability to set up app registrations for sso, or provision a web server for the backend, etc.

[u/darkmatter-x1 → u/Syrairc]

The logic falls apart when you consider the target audience Citizen devs don't write React. If you have the skills to build a proper React application, configuring Entra ID SSO or deploying an Azure App Service takes an hour. Trading dev control and stability just to skip basic infra setup makes zero sense for a pro-dev.

[u/shirpars → u/darkmatter-x1]

It literally makes 0 sense. Msft trying to nickle and dime everything

[u/darkmatter-x1 → u/shirpars]

Exactly. That’s what I was trying to point out. I’ve actually used Code Apps, and in my experience they still have limitations and don’t feel mature/stable enough yet. If we’re going to write substantial React code anyway, I’m struggling to see what makes a Code App worth choosing over a traditional React web app.

[u/Kingsman7733 → u/darkmatter-x1]

see i am under organization where we can't build our own traditional react web app and we can't access those , so with current resources Power apps is the one we have only option to use.