Power Platform licenses demystified - Power Apps

Hopping on a single bus line every day?

Running a single app day in and day out?

Then maybe the Per App subscription makes sense…

BUT – don’t forget – Line 106 in Manchester, is NOT Line 106 in Glasgow

The same app in different environments – is NOT the same app in terms of Per App subscription

An example of a Power Apps app that would fit under this concept is at XRM Vision we have a Time & Expense canvas app that employees use on a regular basis. It is connected to Dataverse, and for many employees, it's one of the only apps they access. In such a case, Per App plan fits well.

Just like XRM Vision when organizing an employee party so they head back home safely… 

There’s no easy way to know ahead of time how many employees will use this service, and where they’ll be heading… So, even if there’s a premium on the price, it is easier to manage a bill that is based on actual consumption than buy taxicab tickets ahead of time.

You’re launching a new app – organization-wide, not sure what will be the adoption of it, or just like an XRM Vision employee party that occurs only a few times a year – or once a year – you may not know how often users will run the app...

Then Pay as you go may be the way to go..

BUT Watch out – if you enable this subscription, then the Per Apps passes are ignored.

An example of a Power Apps app that would fit under this concept is an annual review app that is connected to Dataverse. It's accessed once or twice a year, at different moments, by different employees. It requires a premium (Power Apps) license, but only when the app is run by a user. Placing it in an environment enabled with Pay As You Go, would make sense.