I've already addresssed this earlier in this thread. The answer is that Yes, theoretically that would give you 15 grandfathered apps. It would also be a clear attempt to violate the spirit of the new licensing rules. So I don't recommend it.
Spirit? You think MS has a spirit? Or a soul? They are a greedy multi-billion corporation. I would recommend this practice all day. I'm currently exploring creating an SQL elastic pool with a 100 (or more) idle databases. Then create 100 (or more) empty apps that connects to all those databases. Then I'll be grandfathered for 5 years until I can think of a better alternative.
@iAm_ManCat This is one of the best posts I have seen on this whole thread and I think it really captures where I am at as well, our business is a little afraid of getting involved in dev ops, and PowerApps was helping massively with that, but now it looks like to get anything real done we will have to rely on suppliers and pay and wait, or push the issue and see if we can get an in-house dev ops team using c# and what not.
This was a major gap that powerapps totally plugged, and they have just priced themselves out of the gap - with the amount of disatisfied people from this change, it makes it clear that this is the case.
What would be really cool to see is if all the people who have been let down got together and made their own low code platform (Not proposing, just saying it would be cool and almost unsuprising to see)
I feel you here.
I have more than 10 years of experience in custom developing on SharePoint and Office 365. I know how to do apps with back-end or front-end technologies. After so many years, I finally got excited about something totally new, and I mean PowerApps and Flow with this. I mean, I'm far beyond citizen developer scope, but I do see the value.
With PowerApps, I'm able to discuss with that type of people, teams, and practices in different organizations that I haven't been able to reach before. They have seen the possibilities of small or medium size apps and service that would digitize their business done with PowerApps or Flow.
Unfortunately, these license changes are now pushing my clients to another direction. I'm also doubting that is it worth of the effort, money, and time to invest my own doing to this platform anymore?
@CurtisJohnson81 My hopeful heart is that this will get rectified (more reasonable cost is all I am asking, I'm not even asking for free) and I can keep on with the plan I made and built our whole business model around. However, my cynical, betrayed, heart is not so sure. We are shopping other options very aggressively.
Regarding Blog: "New licensing "options" for PowerApps and Microsoft Flow standalone paid plans
...we’re also listening to input about how to license and implement platform capabilities in standalone plans."
Not an option and not listening.
I could kudo probably 99% of the negative posts to Microsoft's new licensing plan. Does Microsoft even have a metric on what they will lose and hope to gain on this move?
I have (like many others) invested the last two years building a consulting business model centered around PowerApps for clients and I believe it will all be lost once I "have the talk" with my customers.
PowerApps had (and I mean had!) huge potential for capturing the cloud market on low code platform apps. It looked to me like Microsoft was investing a lot of time and money into developing and consolidating the Power Platform with Azure, and the Office 365 and Dynamics markets. Would I be wrong to say that PowerApps is still not mature enough to warrant any cost to use it instead of other options? I thought it was going in the right direction and despite some big gaps (printing, document handling, performance, and delegation limitations being a few) I think a lot of people were planning to hang in there hoping for some of those gaps to get filled.
Existing cost models were fairly "reasonable" as they stood. For my larger and mid-sized clients (and even smaller ones) I could make an argument that cost to value was acceptable. Now, the only companies I can imagine going with PowerPlatform are those huge companies that don't even look at their IT budgets.
Citizen Developer looking for other options.
Nice work Microsoft, you have truly shot yourself in the foot with this decision. Who do you think are making/using your apps? People with no/small budgets thats who.
For people looking for official notification of the 5 year grandfathering. Its in the Official Licensing FAQ which you can find here:
Here's an excerpt
Yes, existing apps and flows will continue to work. Customers who have been using PowerApps or Microsoft Flow with Office 365 using one or more of the connectors listed above will receive a transition period before the connector reclassification goes into effect. This transition period would be until October 1, 2020 or the expiration of their current Office 365 subscription term, whichever is longer. During the transition period customers can continue to create additional apps and flows using these connectors.
In addition, apps and flows created prior to October 1, 2019 which are using these connectors will receive an extended transition period until October 1, 2024. During this time, these qualifying apps and flows will be exempt from the Premium connector licensing requirements for the reclassified connectors.
Read the announcement for more information!
Congrats to the finalists of our ‘Better Together’-themed T-shirt design contest! Click for the top entries.
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!
The top training and networking event across the globe for Microsoft Business Applications