Model-Driven Apps License Requirements (Read-Only Access)

(0) Share

Report

Posted on by CU23071050-2

Question

Can users access model-driven apps with custom tables in read-only mode without Power Apps licenses?

Background

I've reviewed the Microsoft Learn documentation and understand that:

Environment Maker security role users don't require licenses for model-driven apps
Custom table permissions must be configured by Power Platform administrators
Basic User security role can access apps if properly assigned

Specific Questions

Do custom tables change licensing requirements? Can read-only access to custom table data be provided without Power Apps licenses?
What's the recommended security role setup? Should we use Environment Maker role, create custom read-only roles, or modify Basic User permissions for custom tables?
Any licensing workarounds? Are there any proven approaches to minimize licensing costs while providing read-only access to custom table data?

Environment

Microsoft 365 environment
Model-driven app will use custom tables
Target: Read-only access for multiple users
No premium components planned

Has anyone successfully implemented similar scenarios? What licensing approach worked for you?

Thanks!

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Suggested answer

Michael E. Gernaey 53,969 Moderator on at

Like (0)

Report
Copy link

Link copied!

HI @CU23071050-2

If you are using Tables, and model driven apps, it means Dataverse, which requires a Premium license because its dataverse. The tables themselves being custom aren't the deciding factor.

The tables themselves, determine whether you need other licenses like Sales, or Marketing etc, but dataverse is dataverse and you need a license for it regardless.

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey

Was this reply helpful? Yes No
Verified answer

SS-31071509-0 17 on at

Like (0)

Report
Copy link

Link copied!
To give read-only access to a model-driven app with custom tables, you need Power Apps licenses, even for basic access. Microsoft 365 licenses don't include access to custom tables in model-driven apps. The recommended setup is as follows:

Use the Basic User role as a starting point.

Create a custom security role with read-only permissions on the custom tables.

Assign users a Power Apps per-app or per-user license.

The Environment Maker role is not for end users and does not eliminate the need for licenses. If cost is an issue, consider Power Pages for external read-only access or Dataverse for Teams (note that model-driven app support is not available there).

Thanks

Shrikant Sharma

Was this reply helpful? Yes No
Michael E. Gernaey 53,969 Moderator on at

Like (0)

Report
Copy link

Link copied!

@CU23071050-2

Yes, as I mentioned if you have Dataverse at all its a premium license, doesn't matter.

For Power pages as @Shrikant Sharma suggested, you still have to pay for Anonymous users so it won't be free (how many people a month would you have?), essentially correct, you create a new role based on Basic and add in what you need.

However, up until literally just a few days, you need to setup web roles that did not link to Table Roles, so it isn't as simple as just using power pages.

In the end, it depends what your app does, what each user has to do etc.

I am glad you found a solution and hope your app build goes well.

Was this reply helpful? Yes No