Power Apps licensing choice

[datalearner]

Hi Community,

As I know in order to consume a canvas app connected to a premium datasource the user should acquire either per user or per app plan.

Seaching on internet I found that Power App is available as standalone (Power Apps for Office365) and also as developper which confuses me.

1. Could you please clarify the difference between PowerApps for Office365 vs Developer Plan and whether they can replace Per User or Per App plans in the mentioned scenario?

2. Would a powerapps license allow a user to run a power automate flow linked to SQL?

Thank you in advance.

[akandis]

Hello @datalearner 

I response below each point of you questions.

1. Could you please clarify the difference between PowerApps for Office365 vs Developer Plan and whether they can replace Per User or Per App plans in the mentioned scenario?

- Developer plan is a plan that create a Environment exclusively for the person who have the Developer plan, so neve this environment has to be used as a production one or to share apps with other users.

- Power Apps for Office 365 is a plan includedn in most of the M365 license that allows to execute Standalone application. This license is the proper license to execute unlimited standalond apps across environments.

2. Would a powerapps license allow a user to run a power automate flow linked to SQL?

- Sure when you link a Flow with a Power Apps trigger this will make Premium the app. So the app will be premium when the flow is executed in the context of the Power Apps.

So based on this you have to analyze the connectors used and if this connectors make you app Premium then you should acquire the proper Power Apps license.

For more infor please download the license guide -> https://go.microsoft.com/fwlink/p/?linkid=2085130

[datalearner]

Hi @akandis 

I do appreciate your reply, allow me to come back to you with few questions accordingly

1. Could you please clarify the difference between PowerApps for Office365 vs Developer Plan and whether they can replace Per User or Per App plans in the mentioned scenario?
- Developer plan is a plan that create a Environment exclusively for the person who have the Developer plan, so neve this environment has to be used as a production one or to share apps with other users.

Developer plan can not be userd to share apps with other users? 

- Power Apps for Office 365 is a plan includedn in most of the M365 license that allows to execute Standalone application. This license is the proper license to execute unlimited standalond apps across environments.

Would this option allow me as a creator to create an app with premium connectors? Is this license enough for a consumer with whom I will share the same app?

2. Would a powerapps license allow a user to run a power automate flow linked to SQL?
- Sure when you link a Flow with a Power Apps trigger this will make Premium the app. So the app will be premium when the flow is executed in the context of the Power Apps.

I will paraphrase my question in here, will acquiring a Power Apps license would allow me to create apps and also create flows in Power Automate?

Thank you @akandis  in advance.

Readers, If you think you can enrich this discussion please don't hesitate.

[Pstork1]

1) The Developer Plan is only good for one user and is only licensed for learning and development work.  It cannot be used as a production environment. It does allow the use of Premium connectors, but not for Production.  The Office 365 license is included with Microsoft 365 licensing, but only covers Standard connectors.  

2) SQL connector is Premium.  Office 365 license doesn't cover it.  Per app license covers it for a specific app. Per user license covers it for any app that user uses.

[akandis]

@datalearner question: I will paraphrase my question in here, will acquiring a Power Apps license would allow me to create apps and also create flows in Power Automate?

Yes will allow you to create Apps and flows. But you have to understand that you can execute premium connectors if the flow is in the context of the app. This means that the flow have to be executed from Power Apps (with Power App trigger).

If you have a Power Automate without being executed in Power Apps then yes you should consider Power Automate licensing.

Hope is useful.

[datalearner]

Hi @Pstork1 

1) The Developer Plan is only good for one user and is only licensed for learning and development work.  It cannot be used as a production environment. It does allow the use of Premium connectors, but not for Production.  The Office 365 license is included with Microsoft 365 licensing, but only covers Standard connectors.  

Under a developer plan I tried to creating a dataverse database but I got the following error message 

A self-service signup plan is required to successfully complete this request

[Pstork1]

Did you make sure that you switched to the Developer plan Environment?  The developer license only covers the developer environment that is created when you sign up for the license.  If you used a work or school account you will also have access to other environments in your tenant, but the developer license only applies to the developer environment.  I just tested it with one of my developer only accounts and I can create a Dataverse database in the developer environment.

[Pstork1]

Let me clarify what @akandis said.  A Power Apps license will let you create Power Automate flows related to a Power App application you create.  The simplest case is the one @akandis mentions, where the flow is triggered from the Power App.  But that isn't actually a requirement.  Its a bit fuzzier than that.  For example, If I create a Power App that will be used to edit a SQL database and then create a flow that triggers automatically when a record is added to the same SQL database that would be considered "related" if the flow does something that supports what the app is doing. It is not a requirement that it be triggered by the app.  But it cannot be a completely standalone flow that has no connection with what the app is doing.