This effectively kills our PowerApps development. Please work on revising your latest license structure (Oct 2019) to allow us to use the product again.
For us this has gone from an effective enterprise form and app solution to an overpriced nightmare that will impact unsuspecting users who created applications prior to the change.
Could you elaborate a little bit?
I am finding difficulty to create a form using HTML tags. From the community forum, i understand that it is not possible to create a form using HTML tags instead i have to use code to create a simple button element.
For example, to create a simple button, i am writing code as below
<button type="button">Click me</button>
It would be handy if this feature is added to power apps component framework.
Trying to build a strategy based on the new Power platform component pricing is pretty much impossible. We have Office 365 E3 licenses, Dynamics 365 Enterprise licenses, and all of the useful bits have been pulled out and we now have to make a call on:
- User vs application
- PowerAutomate vs PowerApps (is it included? depends)
- Is that a custom connector? Do we get that with O365 E3 or D365 Enterprise? (sort of)
- How many page views on an external portal are we going to have?
- How many discrete 24 hour periods will our authenticated external portal user need?
- Plus a whole raft of others that appear to have been designed to make it impossible (like SA licensing in the past)
This is really cruel and unnecessary and is driving loyal Microsoft professionals like myself to look elsewhere for our future strategic plays.
I completely agree. Only moved across to PowerApps as they shutdown Access Web Apps (at very short notice), I guess they were hosting too many apps for free.
The Azure cost wasn't too much so PA seemed like a good option (if very buggy & limited). but paying somewhere in the region of $400 per month for its use is frankly shocking.
Considering Microsoft sold us PowerApps as a viable option, only to move everything worthwhile into the 'premium' section, it is pretty poor form
The new licensing only works if your PowerApps support a high value process used by a small number of users.
High value processes are usually pretty critical though, and the issues over maintenance and buggy updates rule out PowerApps as suitable for anything critical.
Looks like PowerApps will become just a way of making SharePoint lists a bit prettier and the platform will get a bad name as IT departments get lumbered taking care of user-created Apps built on sub-optimal architecture (SharePoint lists) when the local guru (citizen dev) moves onto a new role. I foresee PowerApps becoming the new MS Access (reputation-wise).