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/

[JohnP]

The new pricing model does not scale well. Organizations may have thousands of *potential* or *occasional* users for any given app. Forcing licenses on all of them is not fair. The total silence from MS is not very surprising, but still disturbing.

[WillEdz]

This is starting to feel a bit like the moment when Microsoft sent out the message that Access Web Apps was being shut down. That caused a major wobble. The answer from Microsoft was rebuild all your stuff in PowerApps its great and free.... here we are a relatively short while later and the message is "Thanks for rebuilding everything (at your cost) - but since you have its time to pay again - but this time we are really going to make you pay - and we mean pay allot each month"

The questions and raised eyebrows that are being fired towards me are not good. 

Label1.Text="Your"

Label2.Text="Fired"

Text(Label1.Text, " ", Label2.Text)

[pulsebeat]

I prefer the string concatenation operator.

Set(varFirstPart, "I'm screwed.  Good time to");

Set(varSecondPart, "retire")

varFirstPart & " " & varSecondPart

[FredericForest]

Considering the utter lack of response from MS on some very genuine concern from the community (not even a "sorry guys but that's that") I'd say there's still some issue with the Communication connector 😉

Notify("Hello world ?", NotificationType.Warning);

[WillEdz]

Careful you might need to upgrade to a $40 a month per user if you use variables 😏

[robinlotz]

Office 365 E5 (Skype (with Phone call );Teams;Power BI Pro;Word;
Excel;Sharepoint;Outlook;OneDrive;PowerPoint;OneNote...) = 35$/user/month

Power Apps "Unlimited" (with ur own dev team / application maintenance team + licensing for ur cloud data base on AZURE ofc ) = 40$/user/month

Just saying...
The pricing before the update of the premium SQL connector was ok ...

[Woods]

Consider myself lucky that I didn´t go all in down this path. Been looking at it for a year and used a fair amount of hours learning the basics in both BI/PA in my free time. I was so engaged. "This is really the future" i told my partners. Now I feel really sorry for all the consultants out there selling solutions based on the Power platform. You're product is now sh*t because of price. I feel really sorry for all the people used countless of hours creating awesome in-house solutions that now will be non-sustainable. You're product is now sh*t because of price. Both of you will have serious problems explaining this for your customer/ management.

What the heck MS?! You know you have to work hard to gain trust after this blunder? Even if you turned down prices cheaper than before, i wouldn't touch it without a guarantee on 5-10 year pricing for my company. For a long time after the new price-model was out I thought there was something i had missed, because who want to pay that amount of money? I run a consultancy company, and have been working with developers for the past 5 years. They are expensive, and too often act like they're God himself, but they at least got integrity and for the most part i can trust them. 

All those hours down the drain... Still I consider myself lucky, because I bet It's nothing compared to most of you. Now what? I still feel this is the future but MS is out until they've cleared this mess! What is the best solution compared to Power Apps?

[FredericForest]

Just saw the MS Ignite presentation on Power Apps licensing. Boy that made me sad... 

Once there was beautiful platform full of potential. Then one day, the Licensing fairy came and cast a wicked spell on her...

The end.

[strategery]

I learned of this via pop-up when a user was trying to start an app. So my questions are

1) Is it apps created before Oct 1 that get the grace period or published before Oct 1?

2) Can we safely ignore this pop-up or is it indicative the app will be rendered useless soon?

Just my 2 cents.

I've been a contributor on the forums and helped others, spent many hours developing my own skills on this product. We already pay an Office365 subscription. When "on-premises" sources were deemed premium, I thought "well, it kinda makes sense...payback for developing the gateway, etc.". I convinced them to get Azure SQL by subscription, made sense, an easy sell.  Now this feels like the rug has been pulled from under us. So we pay for Office365, we pay for Azure SQL, and you want to charge more to bridge the gap? Is Microsoft trying to kill this product?  I'll be moving away from PowerApps if nothing changes, simply for the fact I can't provide solutions without the worry somewhere down the road taxes will be added to it. I'm a developer, not a salesman.

[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.