New licensing question?

[BrianHFASPS]

I have submitted a ticket to ask about this but figured I would ask here too. We are a school that has M365 A5 licenses which include PowerApps for Office 365 in it. We have nine apps used from 2-20 users. All of these apps are interconnected with a backend Azure SQL DB. Up until tomorrow these apps and their usage has been included in that PA for O365 license. It seems now mostly due to Azure SQL shifting to premium I may need to buy PowerApps per App or per User licenses? It seems my exisinting apps are grandfathered for 5 years but I won't be able to create any new apps connected to that DB without incurring additional cost. For the majority of my users that access 1-2 apps I can buy per App and then for the handful that need multiple I can get the per User. Is that all correct?

One issue I haven't really seen defined is shared device / account. I have kiosks around the school for sign-in / out and related activities. Those are iPad with the same account on all of them. Will there be an issue with that account being on multiple devices now? If it is a transaction limit these devices are doing under 500 actions a day.

If I assign the Per App license to a user does the user get assigned a specific app or is that they can't use more than 1-2 apps in a 24 hour period? If I have user who uses App1 on Monday and App2 on Wendsday and App3 on Friday is that ok? As long as they don't use them all in one day?

Due to these changes my costs are going from included in M365 (sort of free) to at least $450 a month to as much as $1600 a month. This is really crazy and could hurt our modernization of processes.

[RezaDorrani]

Hi @BrianHFASPS 

1 - That is correct. Per App - will grant them access to 2 apps and 1 portal - these apps can include any premium connectors

Per user plan will enable them to use premium connectors for multiple apps

So you will have to balance it out based on your use case

2- There is a transaction limit for PowerApps and Flow- Base licnese will cover 2k actions per day (24 hr period). SO this could potentially get affected. 

You might have to plan to puschase capacity add on which will give you additonal 10k requests/day. this can be done for that shared account. Once again plannign would be required

3-  Per App licnese will enale users to access 2 apps and 1 portal only - where premium connections are involved

So if there is a 3 rd app that users premium connector - then u will need additonal license (pre user plan in that case)

It is not based on day - it is based on the App - per App plan

Regards,

Reza Dorrani

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

[bettc]

kinda feels like PowerApps canvas just got shot dead in the water

struggling to make this new pricing model work

Charging per person, per month, per app, per service.  back to dot.net

[v-xida-msft]

Hi @BrianHFASPS ,

For your first question, yes, you are right. PowerApps Per App plan is designed to help organizations solve for one business scenario at a time, which may involve a combination of individual apps. Each “per app” license provides an individual user with rights to two apps (canvas and/or model-driven) as well as one PowerApps Portal, all within a single environment.

PowerApps Per User plan allows a user to run unlimited applications (within service limits) based on the full capabilities of PowerApps.

Please check the following article for more details:

https://docs.microsoft.com/en-us/power-platform/admin/powerapps-flow-licensing-faq#the-powerapps-per...

For your second question, to help ensure service levels, availability and quality, there are limits to the number of API requests users can make across PowerApps and Microsoft Flow. Service limits are set against normal usage patterns in both 5-minute and per 24-hour intervals, and most customers will not reach them.

https://docs.microsoft.com/en-us/power-platform/admin/powerapps-flow-licensing-faq#are-there-limits-...

For your third question, there is no limits on how many apps could be used within a 24 hour period (one day). Actually, the PowerApps Per App plan focus on how many canvas apps a user could be access to. Each “per app” license provides an individual user with rights to two apps (canvas and/or model-driven) as well as one PowerApps Portal, all within a single environment.

In other words, if a user own a PowerApps Per App plan, he could only access to 2 apps (canvas app or Model-Driven), if he want to run third apps, he may need to purchase additional PowerApps Per App license.

Please check the following article or blog for more details:

https://docs.microsoft.com/en-us/power-platform/admin/powerapps-flow-licensing-faq#are-there-limits-...

https://powerapps.microsoft.com/en-us/blog/new-licensing-options-for-powerapps-and-flow/

Best regards,

[Debug_Bug]

Microsoft, please wake up...Don't you see what you are doing here? Is there an adult anywhere?

After having just completed major investments in migrating on-prem databases to Azure SQL (to avoid using premium connectors) and having invested massively in creating a lot af small fit-to-purpose PowerApps - you suddenly change the whole game. This completly undermines, not only your image as a trustworthy partner but even worse, our (your loyal promoters and developers) trustworthyness. We have promoted cloud first and convinced our organisations to trust Microsoft with our business critical IT infrastructure - and then you pull a trick like this - increasing prices with hundreds of percent with almost no warning and at the same time making licensing so complex that we are all now forced to constantly review everything and constantly spend ressources on monitoring and adjusting the licenses.

I'm trying to comprehend the fact that you are doing this to your customers. I have never seen anything like it in my more than 20 years in IT. How can we all trust you in the future after this stunt?

[mogulman]

MS will surely see the impact of their decision over the next several months.  Obviously the connectors consume resources and they should be compensated.  I would prefer a pricing model like Azure Function apps.  The more you use the connector the more you pay.  For lightly used apps like vacation scheduling every can access it and only pay for the few times a year they use it.   Using the new model a company would completely change business practices.  They would have one person schedule all vacations.  You would send an email to that person with your request.  The new pricing promotes inefficiency.  MS will be known as the company that promotes inefficiency. 

[BrianHFASPS]

---

@v-xida-msft wrote:

Hi @BrianHFASPS ,

For your third question, there is no limits on how many apps could be used within a 24 hour period (one day). Actually, the PowerApps Per App plan focus on how many canvas apps a user could be access to. Each “per app” license provides an individual user with rights to two apps (canvas and/or model-driven) as well as one PowerApps Portal, all within a single environment.

In other words, if a user own a PowerApps Per App plan, he could only access to 2 apps (canvas app or Model-Driven), if he want to run third apps, he may need to purchase additional PowerApps Per App license.

---

I still think there is a missing detail. Are you saying a given user with Per App plan can only ever for the lifetime of that user can only access two apps? Lets says I have AppA and AppB and user uses them for a month. Then that user's job changes and they now need AppB and AppC. There is no timeout period where AppA is forgotten and can be replaced by AppC within allowance? That doesn't seem to make sense. Do I assign which apps user has access to and will be blocked if they have access to two apps already? How is this controlled and enforced?