Power Platform Licensing Explained

Power Platform licensing is confusing by design. Microsoft has changed the model multiple times, and different components have different licensing requirements. Here's a practical guide based on our actual usage.

The Basic Model

Power Platform licensing comes in several flavors: seeded licenses (included with other Microsoft products), per-app licenses (access to specific apps), and per-user licenses (access to everything). Plus capacity-based components like Dataverse storage and API request limits.

Most organizations start with seeded licenses. If you have Microsoft 365, you get limited Power Platform capabilities included. But "limited" means very limited - certain connectors, certain capacity, certain features.

Where You Hit the Wall

Premium connectors. Some data connectors - including Dataverse, SQL Server, and many business systems - are "premium" and require paid licenses. This is where the seeded entitlements fall short for real business applications.

Dataverse storage. Your tenant gets a base allocation of Dataverse storage. When you exceed it, you buy more. At $40/GB/month for database storage, this adds up fast. Plan data architecture carefully to avoid unnecessary costs.

API requests. Power Automate flows make API calls. Premium flows can make a lot of them. If you hit the limits, flows get throttled or fail. Monitor usage and upgrade licenses if needed.

Our Licensing Strategy

We run a mix of per-user and per-app licenses depending on the use case. Power users who need access to everything get per-user licenses. Employees who only use one or two specific apps get per-app licenses at lower cost.

The D365 licenses we're planning include Power Platform entitlements. One reason D365 is attractive is the integrated licensing - Dataverse storage, Power Platform capabilities, and ERP all in one commercial relationship.

Negotiation Tips

Microsoft licensing is negotiable, especially at scale. Bundle deals across products usually beat a la carte pricing. Multi-year commitments can reduce per-unit costs. Work with a Microsoft licensing specialist (either Microsoft or a partner) to model scenarios.

Don't commit to more than you need, but do plan for growth. Adding licenses is easy; reducing them is contractually complicated.

The Bottom Line

Power Platform licensing isn't cheap at scale. But neither is custom development or alternative low-code platforms. The ROI calculation should include developer productivity, time-to-deployment, and maintenance costs - not just license fees.

We've found the investment worthwhile for the citizen development and integration capabilities. But you have to manage it actively or costs can spiral.