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/

[pulsebeat]

Convinced organization that Power Platform was way to go....check.

Spent year+ ramping up skills .... check.

Developed 20 plus business applictions now in use throughout organization....check.
Have many other apps in the pipeline....check.

Won't be able to take budget hit...check.

Earlier today I spoke to our MS reps about this, trying to get some clarity.    They did their best to explain but were noticably subdued.  You can tell that they were like "Even I can't believe this".  

[opit]

What will happen with shared apps in Office 365 environment? For example, let’s say I have an app that uses Azure SQL connector (which will become Premium) that I shared with 10 other Office 365 users. Will all 10 app users have to purchase a PowerApps plan or is 1 plan enough for the app owner starting from the 1st of October 2019?

[Eickhel]

All users will need to have a license.

Keep in mind of the grandfathered period until 2024 if you already have your app in production using the Azure SQL connector.

[opit]

@Eickhel  could you please comment on "app in production"? for example: if i create and publish an app till 1st of october, will it count as app on production?

And if i am going to make some changes, updates to this app after 1st of october?

[Eickhel]

According to the docs ( you can also check your Office 365 message center ), if the app was deployed before Oct. 1st it will be granted the grandfathered period. During this period you will be able to use the Azure SQL connector as if it was a standard one.

[Pstork1]

App in production just means an app that has been shared and Published.  It should also include any apps that you wrote for yourself.

[JohnP]

@Pstork1 

So, if I create and deploy 50 dummy apps (basically just a start screen and the connector) to production those apps will be free to use the next 5 years? I can then change/update the apps as needs within the organization arises; i.e. App39 can be the new ticketing system 2 years from now?

[Pstork1]

Theoretically, yes.  But its a clear attempt to do an end run around the new licensing.  So will it hold up if MS takes notice?  Not sure.

The problem is that to establish the connector you need a database and I don't think you can really edit the connector and change the database later.  So you would also need to spin up 50 databases on 50 different server aliases (so that you could move them later if needed).

[JohnP]

@Pstork1 

How about using an SQL elastic pool? I think you can have any number of db's within a fixed cost base. The more active databases you get you can just scale up the resources of the pool. I'm not really sure if this would work.

[Pstork1]

I don't know if that would work either.  I've never tried connecting to an elastic pool.  Either way its still violates the spirit of the exception even if it doesn't violate the letter of the law.