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.
More info at this link:
A key concern for our team is Azure SQL DB (among many other connectors) being reclassified as premium. We standardised on using Azure SQL DB as the datasource for our (PowerApps and Flow based) Apps as we consider it more capable (Views, Stored Procedures, better support for delegation) and easier to scale than SharePoint Lists or CDS (and most of our customers don't have CDS anyway).
For our clients who are already paying for PowerApps (via O365 license) and Azure SQL DB, it is going to be hard to explain why they now have to pay extra to continue using those services together in their existing apps.
What will happen to PowerApps and Flows that don't use a P1 or P2 license? Does the ability to use the free plans of PowerApp and Flow still exist if you are not using any premium connectors or does every user or end user need one of the new licenses?
Aah, feels good to see that this topic is finally debated ! It felt is was almost hush-hush for a while.
Don't get me wrong : the Office 365 Power App licence + Azure SQL DB was a deal that was just too good to be true, it needed reajusting. But now the pendulum swung quite violently to the other extreme...
We're extremly affected by these new changes. Like many others, we only use Azure SQL DB as a backend and HTTP Responses to return PROC data (for a variety of reasons we won't debate here). A client has already pulled out of a project days before production (didn't know about the 5 year grace...) and I expect others to soon follow. The client even suggested to switch the project to an Access database. Argh !
A lot of our current projects revolved around "profesionnalising" artisanal business processes (aka : Excel sheets grown too big for their own good). These scenarios often have a low usage (maybe once a month) but adress a large user-base (50+ users). The P1 licences just cannot work in such a scenario since business sponsors are not willing to pay 6K€/year in licensing fees to replace a single Excel-based process (or 25K€/years for mulitple ones...), no matter how clunky and error prone it is.
Personally, I'm hoping something akin to the daily-login licensing concept for the portal could be extended to the regular canvas apps. Azure has had tremandous success with the Pay-as-you-go formula since it allowed a real "land and expand" strategy. Give the people a taste of what PowerApps can do with cheap, easy to commit to scenarios and they'll remember you when the big lucrative use-cases come around.
My two cents anyway
ps: anyone know if the grace period also includes the HTTP responses ? Patch() is a handy little tool, but it's not going to cut it for complex business logic over large datasets ^^
Thanks for your reply, Paul
I hope i can get some official statement around the grace period - not that i dont trust you - but i would like to see something from Microsoft staff on this. Hopefully they wake up!
I have one big app just about to go into prod. It uses the Azure SQL connector. I need to convince my customer that they are safe during the five year exempt period otherwise they will pull out and buy a third party case management system instead.
In my particular case we are talking about approx 2000 users and we are already paying for the SQL Server in Azure and for Office 365 licenses. Also paying for the ability to communicate with SQL doesnt make a single sense to me.
Please, Microsoft staff, spread some ligth over this!
@Pstork1 Thanks for starting this thread.
I have several thoughts at the moment about the new licensing model. Two of them I would like to share. It are 2 questions about the "PowerApps per app" plan.
Canvas apps have been positioned for customized tasks and role-based apps and model-driven apps for back-office scenarios. A business solution (called application in the licensing F.A.Q.) I have in mind is build on this concept and contains a few model-driven apps and several canvas apps. The apps are role specific, meaning an employee would normally only need just a few of these apps. This setup is also based on a best practice not to make big apps.
The new "PowerApps per app" plan allows for 2 apps and a single portal per application. So how are these 2 apps determined? If this is max. 2 apps per user per business solution, then I think it is ok. If this is max. 2 apps per business solution, then I think, well,
Some business solutions only need to be executed once a year. Enabling a business solution for only one month could be an option. How will the billing be processed? Example: All apps present on the first of the month will be counted.
I work at a manufacturing facility, and I've been using PowerApps to really change how we do work in my department. All of my apps go through SQL as I'm connecting to various data sets used by other applications (e.g. Blue Mountain). I've been active in the forums, and I've really held out hope for PowerApps as a long term solution at my site - but this is killer. I might be able (MIGHT be able) to swing the money for a single P2 license and a few P1 licenses for my team to continue using the apps I've developed - but I'll never be able to expand my game-changing apps out to other groups (100's of employees). Why would I continue using a product that isn't expandable (expansion is cost prohibitive = not expandable)?
Someone up above said it best - this makes Powerapps a wasted opportunity. And others were correct as well - I'm going to have to stop using Powerapps and start making something else on my own. I'll go back to asp.net and eat the hours it takes to rebuild everything I've made in Powerapps on my own web page if I have to. At least it's something I can rely on!
*feeling very betrayed - drinking wine in T-MINUS 2 hours*
While investigation the impact of the license model changes on existing PowerApps apps, does anyone know if the request limits are grandfathered too on Azure SQL Databases for 5 years, or are they enforced from october 1, 2019? Does anyone know this? I have not found any info on this.
Join us for the first ever Power Platform Online Conference!
Look out for new contribution recognition badges coming SOON!
We've updated and improved the layout and uploading format of the Power Automate Cookbook!
Fill out a quick form to claim your user group badge now!
Find out where you can attend!
Watch & learn from the Power Automate Community Video Gallery!