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 one year grace period should apply to the tenant in general.  But the 5 year extension for SQL is only for apps that existed prior to Oct. 1.

[PaulD1]

Time for a mini-rant.

Earlier this week I have spent considerable time and effort porting an App from D365 to CDS connectors (prompted by the banner in the designer) only to discover there is a known bug with the CDS connector with no resolution other than to keep deleting and recreating galleries until you get lucky and it works (for a while, then you have to go through the process again).

Yesterday in trials of an App, saving an image to Azure Blob Storage from PowerApps takes a couple of seconds on Web and iOS and a couple of minutes on Android - still investigating but very much seems like a platform issue.

This morning the behaviour of Explicit Column Selection has been changed breaking existing production apps used by hundreds of our users.

MS thinks this platform is mature enough to charge $10 per App per User per Month?

[Anonymous]

@PaulD1  well put, I totally agree that its not ready to be charging at this level and stand up to the competition. 

I could build a case for this in our business but in the back of my mind I am worried about the bugs that I am aware of that I know would hold us back - they did this a year too early I think. One can only hope that any new funds that they get as a result of the licence change quickly results in massive input into the platform which will resolve these issues fast. I hope that MS do this becuase I love the Powerplatform and I want to see it help businesses reach their potential! 

[pulsebeat]

@CurtisJohnson81  

"I could build a case for this in our business"

I would really like to know what that is. I just don't see it, no matter how many ways I work the numbers, no matter what color tinted glasses I put on, no matter how much I squint my eyes.  Maybe I have missed something - some magic coefficient that makes the case.  If you know of one, please do tell.  Like you, I really love the Power platform but at .5 million, I'm now back on the market looking for love in a new relationship.  

[DirectorMumbles]

@pulsebeat only thing I can see at this point is small one off apps. Nobody would use this at any scale anymore.  If I need an app for one or two people, not a big deal. Scale that out to 100 and I might as well not use the platform at all because the ROI is no longer there.

[Anonymous]

@pulsebeat  hey man I am with you and totally agree, I just got skills in my case building is all - I jest, I jest.

In the specific scenario it does stack up against suppliers, when you are at scale, nothing is cheap, apart from cheap crap. what I agree with is that Powerapps is not the best platform you can get for you money, so building a case, yes, going for it in production - maybe not so much.

besides, if case building was that difficult, marketing wouldn't exist : ) 

[monkeyclass]

So we took the consequence of the new licensing model and replaced our entire backlog of PowerApps projects, and made it into Django projects. We finished the first project within a month and now how it running it production (hosted as an app service on Azure). The project will also work as the template for the coming projects, which should decrease the development time. It took time to get flying but it seems like the right approach considering we can now develop real web-apps rapidly, and do not have to pay licenses to add extra users. Everyone is validated against our Active Directory and everyone is happy. Goodbye PowerApps.

[pulsebeat]

@monkeyclass  Thanks for the post.  This really  gives  me a good place to start with my PowerApps replacement program.  Best of luck to you.  

[BillSull]

Can anyone recommend a good replacement for just automating document creation?
We were looking at using Flow to merge new SharePoint List entries into Word Templates but with Word being a premium connector, that is out. 
I know we can do it with SharePoint Designer but I question how long that will last when Microsoft sees people using it instead of Flow (PowerAutomate)

[DavesTechTips]

Hello everyone,

I can't seem to find the answer for this online.

a) The Power Automate Per Flow plan entitles us to use Business Process Flows. For a user to take part in a Business Process Flow, they need a Model Driven App. Can you access the Business Process through a Model Driven App if you only have Power Apps Office 365 seeded licenses?

b) The Power Automate Per Flow plan entitles us to use Premium Connectors, Custom Connectors and Data Gateways. Can you use a Canvas app (through an O365 seeded license) to access Flow who then in turn connects to all of these, or would you still need a PowerApp standalone plan?

Thank you very much everyone, have a great day.

[dchasanidis]

Hello everyone,

I have a Dynamics 365FO subscription (which includes a power automate licence as metioned in licencing info) and Office 365 subscription too. Can I use the premium Dynamics connectors? I am a little bit confused here. Any help given would be invaluable.

Thanks in advance.

[farhandsome]

@Pstork1 

What is the ruling for apps created prior to Oct 2019, but the SQL connector has been modified and changed after that date?

[Pstork1]

That depends somewhat on what changes were made to the SQL connector.  In general if the SQL connector existed in the app prior to October, 2019 it should be covered by the grandfathering.

[farhandsome]

@Pstork1 

understood. The connector was removed and readded in March. 

So this will break in October? The app was made in September 2019

[Pstork1]

If its working now then it should continue to work for the next 5 years.  If you create a new app now and add a SQL connector that would require premium.  But if its still working then it didn't detect that the SQL connector was removed and re-added.  It still thinks its been there since Sept, 2019

[farhandsome]

@Pstork1 ,

wow that’s great news!! I thought it would break October 1st, 2020.. it says the license designation is premium but none of the users who are using the app have been prompted for anything like that. 

any way to ensure they won’t break at that time? 

[Pstork1]

No way to really check before October.  The problem is that all apps were grandfathered in for one year, but SQL connections got 5.  The problem is there is no way to tell whether its still working due to the one year extension or the 5 year SQL extension.  

[farhandsome]

@Pstork1 

Understood.

the SQL connector says it was created in March, but the app was made back in September of last year. 

guess there’s no way to know for sure. That’s pretty problematic for citizen developers like myself. 

@Pstork1 

[BillSull]

After reading this whole thread, it got me wondering about how many apps are around that use premium connectors.  Microsoft will surely know this and in a few weeks will be billing those who do.

I searched a bit and found some PowerShell scripts for this and other useful things.  

https://powerapps.microsoft.com/en-us/blog/powershell-scripts-to-discover-powerapps-and-flows-with-s...

If you do try this, let us know your experience with it please.

[Sonapsen]

What is going to happens with the existing free versions of PowerApps? Will it begin to incur a cost?