Power Apps and Dynamics 365 Licensing

🔹 Dynamics 365 and Power Platform Licensing – Detailed Breakdown

I will be honest — Microsoft licensing wasn’t always my favorite topic. Like many Power Apps developers, I focused on building solutions, not figuring out who’s allowed to use what.

A few months ago, I was leading a Power Apps project, during a project review meeting, questions started piling up:

• “Can’t we just give everyone Power Apps licenses instead of Dynamics licenses to save cost?”
• “Can a Team Member run this flow?”
• “Is this Dataverse table covered by our license?”
• “Do we need a Sales license just to store contact data?”

That’s why I’m writing this post. I’m writing this post because I’ve seen firsthand how confusing licensing can be. I’ve seen organizations spend weeks in building apps, and realize later that users aren’t even licensed to run them. Others overspend on licenses just to be safe, or under-license out of ignorance. In this blog i tried to break down the licensing into plain English — grounded in real project experience — so you can make decisions right from the start.

🔹 1. Power Apps Per User License: What Can You Do?

If a user has a Power Apps per user license, they can:

• Build and run unlimited custom apps using Dataverse.
• Use premium connectors (like SQL Server, Dataverse, HTTP, etc.).
• Create workflows using Power Automate.

Important note: If you're building apps that use data from the same tables used by D365 Sales, that's fine — as long as you don’t use the full Sales app experience.

Dynamics 365 Sales is a packaged solution. So while Power Apps lets you read/write Sales data through your own custom apps, it does not give access to the full Sales interface or built-in processes.

✅ OK: Custom canvas or model-driven apps using Dataverse.
❌ Not OK: Using the full D365 Sales app UI or mimicking its full functionality.

🔹 2. Dynamics 365 Sales Enterprise License: What’s Included?

The D365 Sales Enterprise license gives users:

• Full use of the packaged Sales app.
• Rights to build and use custom Power Apps.
• Access to Power Automate and premium connectors.

This means users can build apps, automate flows, and extend the Sales module — all without needing a separate Power Apps license.

🔹 3. D365 Customer Service Enterprise: Same Rules Apply

The Customer Service Enterprise license works the same way as Sales Enterprise.

Users can:

• Use the full Customer Service app.
• Build custom apps and flows for service-related tasks.
• Access Dataverse and premium connectors.

No additional licensing needed for building extended solutions here either.

🔹 4. Dynamics 365 Team Member License: What Can’t You Do?

This is a lightweight license meant for basic tasks like:

• Viewing data
• Entering notes or time entries
• Reading dashboards

However, users with this license cannot:

• ❌ Build or run custom apps that access restricted tables (like Opportunity or Case).
• ❌ Use Power Automate flows with premium connectors.
• ❌ Run apps that replicate full D365 Sales/Service features.

Bottom line: This is for occasional users only — not for app builders or power users.

✅ Quick Summary Table

User License	Can Use Custom Apps?	Can Use D365 Apps?	Use Premium Connectors?	Custom Flows Allowed?
Power Apps Per User	✅ Yes, for custom data	❌ No, for full D365 apps	✅ Yes	✅ Yes
D365 Sales Enterprise	✅ Yes	✅ Yes	✅ Yes	✅ Yes
D365 Customer Service	✅ Yes	✅ Yes	✅ Yes	✅ Yes
D365 Team Member	⚠️ Limited	⚠️ Limited	❌ No	⚠️ Very Limited