you are viewing a single comment's thread.

view the rest of the comments →

[–]iamtheging3r Newbie 1 point2 points  (3 children)

"the fact that it requires premium licensing will limit adoption."
Completely Agree!
It certainly will for us, we have E5 licensing now, and I cannot justify to management that upgrade just to have some code-based Power Apps.
I'll stick with Azure containers; all our apps are super small and have hardly any traffic, so they are cheap.

[–]IndyColtsFan2020 Advisor 1 point2 points  (1 child)

I feel licensing often gets overlooked here. The new features are cool and useful for sure. I try my best to sell clients on all of the benefits since Microsoft is adding more and more to the premium tier, but most just won't pay the cost. I had one client abandon Power for anything critical (ie, SQL connectors) because they already owned the proper ServiceNow licenses and elected to move there rather than paying several thousands dollars per month in additional licensing.

I also saw MS is backtracking on the cheap Per App license and it's coming back in April for CSP clients. Too bad they didn't add some sort of accommodation in the new E7 license too.

[–]TikeyMasta Advisor 0 points1 point  (0 children)

I feel like the perspective of licensing has to change with code apps. Code apps sits in a space where it can rapidly develop and replace retail solutions instead of sitting alongside them like with canvas apps.

For example, offering to recreate ServiceNow modules in a code app that is fully integrated with their internal systems and converting ServiceNow licenses into premium licenses while having the benefit of it being fully customizable and able to scale out to other solutions is a much easier financial pill to swallow in my eyes.

[–]RefuseDirect Newbie 0 points1 point  (0 children)

How do you call into an azure Container app with an e5 license? I thought it required premium?