New PowerApps and Flow Licensing coming October 1, 2019

[Pstork1]

If you haven't seen the announcement yet about the Licensing changes that are coming to PowerApps and Flow starting on October 1, 2019 you really need to read the following Blog. This announcement was originally made at Inspire this year, but has undergone a number of significant changes.  Make sure you read this and understand what it means to you and your organization.

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

[Pstork1]

The App is what is grandfathered in.  So adding another SQL connector to another table should be fine.  There are always going to be scenarios that are not specifically called out in the FAQs.  Its hard to cover every contingency.  But the exception is provided at the level of the App or Flow according to the FAQ, not a specific connector.

Assignment of the perApp license would be done like any other license, by the global admin, or someone the GA delegates that capability to.

[MagnusGöransson]

Thanks for clarification dileeps and Paul!

For the per app-licenses, is it possible that a citizen developer create an app that uses premium connectors and share it to a large amount of users that eventually start to use the apps and consumes all the available per app licenses available?

Or am I missing something? As far as i know we cannot prevent users from creating apps in the default environment.

/Magnus

[dileeps]

You will be able to prevent that because per app passes needs to be added to an environment. And as a Global admin, you will be able to control how much is added to each. This documentation would be live in few days.

[Pstork1]

@dileeps

One correction.  The per app licenses is $10 per app, per user, per month and is bound to both a specific app and a specific user.  But only user's who use the app need to be licensed.  So you could have one app with 10 users and another app with 20 users.  That would be 30 licenses and they would be assigned to specific users, although they can be re-assigned at any time.

[Pstork1]

For the App license - it needs to be assigned by someone with admin authority.  So a user would not be able to create an app that uses a premium connector under the app license, or share it, without approval.  An admin would have to assign the per app license to the app and to each user of the app.

[dileeps]

@pstork - so it is a bit different, per app passes are per user but they are not like user licenses which are pre-assigned to a specific user. They are assigned to an env like capacity.

Now, when a user use any app in that env which uses premium connector (which has opted in to use passes) and doesn't have a user license, they will automatically be tied to a per app pass. 

[DirectorMumbles]

This entire thing is a disaster and a good way to kill a promising platform

[AngryBatVoice]

@dileeps @Pstork1 

Wow.... thanks for the clarification. Good to know  </sarcasm>

Any reason the documentation wasn't released... oh I don't know... BEFORE rolling out this convoluted system?

[BrianHFASPS]

Where is the interface to assign these licenses to an environment? Also my tenant doesn't have Per User as option to purchase.

How can the documentation for a new billing practice be release after the billing goes into effect?

[dileeps]

Documentation for licensing constructs has already been released and is listed here aka.ms/licensefaq as well as Billing and Licensing Guide. 

Documentation for how you perform actions in product is being updated now, this is not prepublished since this follows product changes, hence it is done in stagerred manner similar to how product changes rollout