Developer license/User license/E1/2/3

[dungar]

I just want to make sure I present things clearly.

I have 2 apps created. 

App A will be used by 50 people, App B will be used by a subset of those 50, 5 people.  I believe all of them have E1 licenses.

From what i understand (very limited) the only way to let people use the apps would be for each one of them to have a powerapp user license, thus totaling $550 a month? (10 for the 50, and then an additional 10 for the 5 who have to use both).

In what way, if any, would other licenses affect this situation (developer/E2/E3)?

My current understanding is that developer would only affect my ability to make more apps, but we'd still be at the $10 per user per app issue, so until i've made 5+ apps that identical users are using, there's no point in it (and then each one of them needs a dev license?).

I've heard that an E2 or E3 would include powerapps useage, but I'm having trouble finding or confirming it (or really any of this).

[v-monli-msft]

Hi @dungar ,

Did you mean Office 365 E2/E3/E3 Developer license? If you already have one of these licenses, then it already included the Power Apps and Power Automate capabilities. You do not need to purchase additional PowerApps per app or per user plan.

More information could be found here:

https://download.microsoft.com/download/9/5/6/9568EFD0-403D-4AE4-95F0-7FACA2CCB2E4/Power%20Apps%20Po...

Regards,

Mona

[dungar · Accepted solution]

I do mean those, but I have to say the documentation is confusing me more because from what I'm reading I SHOULD be able to use it as intended, but very clearly cannot?

I have a user who has a a Office 365 Business Premium License sitting next to me.  This is listed as a license in Appendix D that comes with powerapps.  I've made an app in powerapps(no flow or anything else), and I've shared it with him.  When he clicks on the app it asks him if he wants to start a free trail.

Heck when I click play on the app it asks me if I want to start a free trial (i can only edit).

When i go to his account and look at his license, there's a "Power Apps for Office 365" option, and it's on, so what part of the equation i'm I missing/misunderstanding, and would upgrading to a different license even fix it?

Edit-

The only thing I can think of is because i'm using a "Premium" connector by using Azure SQL, but if that's the case fine...how what do I need so that others can use this then?

In fact looking at it more that seems to be the issue, but from what I can tell, there is NO license level which will fix this, we must get per user licenses for it to work?

[Hayes3d]

Any Premium connector will require a Power Apps Per App license or Per User license. O365 E3 includes a "standard" Power App license to use it within the context of O365 cloud. Nothing outside of it.

[dungar]

That doesn't seem to be completely correct?  Not trying to be pendantic but my reading of the documentation implies that Dynamics would include the premium connector, but it's the only other thing that would (and then i'm not sure if you can share you files as it's very unclear on that)

[Hayes3d]

Nope, you are correct that the Dynamics licenses include Power Apps with premium connectors.

My question would be, what are you trying to accomplish with this application? Is it using Dynamics 365 data? SharePoint Online? Azure/OnPrem SQL? What are you talking to?

Then, how many people would be using this application?

Answers to those questions I think will help determine what you need.

[dungar]

We're attempting to consolidate our company data into a data warehouse so that information can be gotten quickly and easily. We've created a SQL database to house this data, and it was recently moved to Azure.

Some of the data we need doesn't come out of applications, but instead comes from very outdated processes.  For example: one person writes numbers down, next person transcribes them to an email, next person puts them in an excel sheet, next person cleans up the data and re transcribes to excel, then finally someone loads them into the warehouse.

The alternative proposed was just to have the first person enter the data directly into the warehouse with powerapps (which could do data validation for 90% of what was being checked) and then a review process from one other.

There are many procedures like this that don't have an application associated with them, but have employees entering critical data.  The first app I made to test this involves one of our more important processes thats done every day at every location (more than 150 of those).  While every employee would not need accesses, there would be about 100 that do.

To eliminate other data entry procedures it could range anywhere from 200 to 1500 people depending on what's desired.

[Hayes3d]

So firstly, I'm not a licensing guru for Microsoft...unsure if anyone can truly keep that title as they constantly change licensing.

But I believe I understand what you are doing here, correct me if I'm wrong:

1. You want to enter data in a form(s) and save it to a single data source.
2. Multiple applications/users could be using this data source with (Create, Read, Update, Delete) CRUD operations.
3. First app needs about 100 users to access.
4. If this goes well, other apps could be created with up to 1,500 users leveraging these apps and data source (and most likely other data sources).

I'm not 100% sure what licenses are given to those 100 users, but if they are currently not licensed the most affordable option is the pay per app model. This will get your started.

For the other apps, the amount of data, types of data etc, I'm not going to guess on the best option for all of that.

But what I would recommend, something I have done at my own organization, leverage Microsoft. Schedule a "hackathon" with them, our local office did it for free, and they will pull out the business requirements and help develop a scalable structure with you. I have read that Azure SQL can work, but they have had some issues. Azure SQL Warehouse has other issues. Azure Table Storage and other options are also available. I don't know the best options for those, Microsoft engineers would and they will help.

We did this and created an application in 3 days, which allowed a process that typically took 2-3 months, about 15 minutes. What changed? They had access to all of the data immediately based on choices, to make a decision, and submit for approval. Previously this data was aggregated and filtered manually using spreadsheets which had data dumps from multiple data sources. But building a custom application to fix this was not considered a "large" enough project for our developers to do. 

[dungar]

I agree with what you're saying, but we're basically already down that road.

The short of it is(consultants and MS have been involved in getting here, I don't agree with every choice made but I also don't get to choose):

1. We do have Business Premium licensing for all relevant users

2. We must use a Azure SQL database to store the data (while it will function similar to data warehouse, it is not actually an Azure Data Warehouse, just an Azure MS SQL Server)

3. We currently have need for 100 users to make Insert/Update statements into 1 table.

4. We could expand to have need for 200 up to 1500+ users to do similar things (again different tasks, but mostly similar models).

5. Powerapps was proposed as part of our solution when we started this (many months ago), and the recent changes in October have caused a rather massive reassessment, which came at a bad time because it was just as we were getting to the point where we wanted to test/use powerapps (infrastructure wasn't ready).

From everything i've heard and read, point #2 forces us into either doing per user per app($10 per 2 apps per user), per user($40 per user), or dynamics($X?).  There are no other licenses that will allow a "premium connector" in a powerapps, and there's no bulk deal on any of these (maybe dynamics?).

[Pstork1]

To clarify a bit.

1) Business Premium is an Office 365 license, not a dynamics license so it only covers the use of standard connectors, not the premium ones like SQL.

2) You are correct in your conclusion that you need either a Per App, Per User, or Dynamics license for each of the 100 users who will use the app. Please note that the 2 apps mentioned in the Per App license need to be related to each other in their context.  For example, a model driven app with a mobile app that provides similar functionality when on your mobile device.  But it can't just be any two apps.

5) Yes, I've heard this from a number of people/organizations.  If your app was already using SQL on Oct. 1 then you should be able to continue using it as a standard connector in that app for 5 years. this should just work, but I've seen people have to open a support call to get the extended licensing enabled.