PowerApps Licensing Bait and Switch

[KiewitGraves]

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.

[kungfu7]

Could you elaborate a little bit?

[vani2000]

Hi,

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

private button: HTMLButtonElement;

this.button = document.createElement("button");

this.button.setAttribute("type", "button");

 this._container = document.createElement("div");

 this._container.appendChild(this.button);

container.appendChild(this._container); 

instead of easy one as below

<div>

<button type="button">Click me</button>

</div>

It would be handy if this feature is added to power apps component framework.

Regards

Vani

[Manager2020]

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.

[Joe1098]

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

[PaulD1]

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

[FredericForest]

I completly agree with @PaulD1.

We've painted ourselves in a corner. Either :

• It's a critical business process (cost is justified) but PowerApps ain't just quite there to support it yet.
• It's not critical at all (aka we're industrializing an excel spreadsheet) in which case the only option is SPO lists... with all it inferes

PowerApps should be the MS Access of Office 365 : a great added value to a key package to MS strategy. Sure it can have a premium offering, but it shouldn't become MS Visio : a great piece of software, completly overpriced, that remains marginal for all of its useful life rather than becoming a mainstream product. 

[JohnP]

Scaling is the key. Apps with a high number of users which requires a premium connector will be priced through the roof with the October 2019 change. You have to either go with SharePoint lists or abandon your project. Paying millions just because you chose to store data on Azure SQL (which you already pay for) is insane.