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.
Since my somewhat detailed post, which was an on-topic reaction to this announcement that contained no profanity or other community-guidelines violations that I could tell, appears to have been deleted without any explanation. Could someone from Microsoft or a moderator of this community please explain to me the opinion of these changes I'm allowed to have?
EDIT (Original Post, however I did remove the part where I called the move a bait-and-switch, stated that Microsoft should be ashamed, and compared their 5-year grace period to adding sugar to poison, just in case those statements crossed a line):
Microsoft should recognize the damage this move has done to their brand. They have been selling us on this idea of "low-code-no-code" and then pulled the carpet out from under their customers by jacking up the price to an unreasonable degree. They have taken what was a platform full of promise and potential and turned it into a cash grab. It doesn't matter which team this decision comes from, at the end of the day, it is coming from Microsoft. If they don't have the ability to oversee and to make sure their teams are working together and not hurting each other's customers, then they have bigger problems than PowerApps users having access to AzureSQL. The Powerapps-AzureSQL scenario being "too good to be true" and in need of adjustment is just giving them too much benefit of the doubt. I'm paying for PowerApps, I'm paying for AzureSQL, both products are within the Microsoft ecosystem, why in the world do I then need to pay a third time to connect them? And why does connecting the products cost 3x as much as the individual products themselves?
But this decision doesn't just damage Microsoft's brand and the trust they'd built with us. With this decision, Microsoft has injured my own brand and credibility with my company. I've spent the past year learning, developing, and selling my company on the idea of the Power Platform and to embrace the tools that we are paying for with our Office 365 and Azure licenses. My company has invested in my time and paid for training on the Power Platform, gaining me skills that I now won't be able to utilize. I have to go back to them and explain that our new processes involving the Power Platform are only a stopgap, because in 5 years the cost of continuing to use them will explode exponentially.
We can't just go back to using Sharepoint as our data source, it is too insecure. And the cost of the new licensing model is quite frankly out of our reach. We aren't a large company. The potential savings from continuing to use the Power Platform to streamline our processes doesn't come close to covering this new cost of the product. There is no scenario where we can afford this.
What could they have done instead?
I am pressing on with my PowerApps development for the time being, with the hopes that Microsoft course-corrects on this. I know there is more to the new licenses than just the AzureSQL and Blob Storage connectors, but from my perspective, making those connectors Premium is what places the new licenses out of my reach.
I've contemplated just building a bunch of blank template PowerApps/Flows and adding these connectors to them, for future development after the Oct 1 mark, but I feel like this would be cheating the system, and I'd rather not treat Microsoft the way they are treating us.
hey @AngryBatVoice ,
I get your point (I'm more or less in the same situation, with similar consequences), but I really do think that, despite all, it IS really a matter of perspective and markets. The dynamics team that 40$/month is quite cheap compare to where they are coming from. We, from the Azure or Office world feel... differently! ^^
Personally, I couldn't really care less about CDS (no offense) and that really shows the divide between the two realities. If, through licensing, the Power Plateform team is not willing to accomotade the SQL-based reality (which to me adresses a whole different, non-canibalizing market), then its a real shame... but we'll have to accept it (aka : leave, for most of us).
On another note, I thought you made some interesting comments on your ideas of what could be done.
And my personal fav : a price per daily login (ideally around 1$), more akin to the pay-as-you-go on Azure.
The beauty with these is that the could work WITH the existing new plans (not against them). Much easier to communicate.
For the guys that were around back then, Power BI also had a bit of an identity crisis with its licensing scheme during its initial release. First part of Excel, when the service (v1) was initially launched, it had a efty 40$/month price points for the full platform access. The results were disapointing to say the least. When v2 was relauched later, the new price point of 10$/month allowed the product to completly explode and become the success it is today, generating much more total revenu than v1 (yay for pricing elasticity). Hopefully, this lesson is being discussed internally as well...
For the record...
Not sure what happened to the original post. I never saw it so I don't know why it was deleted.
I don't disagree with some of your points and I've registered my concern that this is a very bad PR move with Microsoft directly.
As a 20+ year champion of most Microsoft causes I can clearly state that this is the type of maneuver that winds up looking like Windows Phone. While the Power Platform has a ton of promise it is still not fully mature and asking this much for a service that is still growing is truly unfortunate. The value of having a relatively low cost platform that promotes sales of other profit centers such as O365, SharePoint, Dynamics and Azure services was brilliant. This new concept that the Power platform IS the profit center rather than increasing sales in the other profit centers is a bad miscalculation and if it sticks will absolutely kill this platform.
My company has already spoken on the matter and will likely have to divest ourselves of the platform which we were in the process of ramping up on. This decisions single handidly eliminated the growth of the platform which will kill off our Azure and O365 usage as well. The words from our leadership's mouth is what you will hear across the world "Not gonna happen".
I am not against Microsoft trying to make money on the Power platform and hope they do. However, going from O365 licenses covering end-user usage of the system to everybody pays $40/app/user/month is ridiculous. Microsoft really needs to reconsider this. In the meantime, development in the platform will cease in a few weeks while we search for alternatives.
I am still trying to get all the facts so I can give my customers proper advice.
I have one app in pilot-stage for the moment. It connects to Azure SQL. How many API-calls would be measured in the following cases:
- I use Filter() on the Items property in a gallery. The database-table holds 2000 rows, but through the filter i request 100 rows
- I use Patch() to update five columns for one item (row) i the database-table.
- I use Filter() on the Items property in a gallery. The database-table holds 2000 rows, but through the filter i request 500 rows. The filter statement is fully delegated. The end user scrolls down 10 times in the gallery to see all the rows.
It would be quite handy to be able to see the API-calls for each PowerApp in the Analytics view. Do anyone know if that is possible?
I cannot agree more. Its not enough to have us all using O365, Windows Desktop & Azure SQL Server. Now they want more money to be able to collaborate and automate using the tools we are already paying for.
I agree, I feel like the past 2 years developing apps in PowerApps has been a total waste of time. All our apps rely on SQL Server and this will just kill it. There is no way we can afford an additional $40 per user per month on top of the $20 per user for O365 and $10 per user for PowerBI.
I agree its tough at this point to calculate API calls based on actions. But in general what you describe is probably one API call each. Batching things will cut down on the number of API calls.
This new license change is confusing to me. We have one canvas app on a customer tenant that utilizes CDS. The app consumers/users have an E5 license, so there is no extra cost associated with using the app besides the E5 license. How will this change on October 1?
According to the documentation, if using CDS, every user must have a minimum of PowerApps per app plan:
PowerApps per app plan which allows individual users to run applications (2 apps and a single portal) for a specific business scenario based on the full capabilities of PowerApps for $10/user/app/month. This plan provides an easy way for customers to get started with the platform before broader scale adoption.
The E5 license won't suffice
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!
Check out the community blog page where you can find valuable learning material from community and product team members!