Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 38 ยท Getting Started

Licensing, Plans and Environments

Understand Power Apps standard and premium connectors, per-app and per-user plans, the free Developer Plan, and the environments where your apps live.

Before you build, you need two things: a place to build and permission to use what you build. In Power Apps those are environments and licenses. Misunderstanding either is the most common reason a finished app cannot be shared.

Microsoft changes plan names, prices and included capacity regularly. This lesson explains the concepts, which stay stable. Always confirm current details in the official licensing guide and with your administrator before you commit to a design.

Environments

An environment is a container for your apps, flows, tables, connections and solutions. It also defines a region, a security boundary and, optionally, a Dataverse database. Common types:

Type Purpose
Default One per tenant; every licensed user can make things here. Fine for personal productivity, risky for serious apps
Production Live apps used by the business
Sandbox Development and testing; can be reset or copied
Developer A personal environment created with the Developer Plan
Trial Temporary, for evaluation

A typical team uses at least Dev, Test and Prod environments, and moves work between them using solutions (see the Components and ALM chapter). Switch environments from the environment picker at the top right of the maker portal.

flowchart LR
  Dev["Dev environment"] -->|"export managed solution"| Test["Test environment"]
  Test -->|"approved"| Prod["Production environment"]

Build in Dev, validate in Test, deliver to Prod.

Standard and premium capabilities

Every connector and feature is classified as standard or premium. A few examples of the idea:

  • Standard: SharePoint, Office 365 Outlook, OneDrive, Excel (as a table in cloud storage).
  • Premium: SQL Server, Salesforce, HTTP, custom connectors, and Dataverse in most scenarios.

If your app uses any premium connector, every user of that app needs a premium-capable license. This single rule drives many licensing surprises.

Common license types

  • Seeded rights: many Microsoft 365 licenses include the right to run apps that use only standard connectors and the built-in Dataverse for Teams.
  • Per-app plan: a user can run a limited number of specific apps, including premium capabilities.
  • Per-user plan: a user can run unlimited apps, including premium capabilities, within fair-use capacity.
  • Developer Plan: a free plan for learning and testing. It gives you a personal developer environment with Dataverse. Apps built there are for development, not for sharing broadly in production.
  • Pay-as-you-go: usage is billed through an Azure subscription linked to the environment.

You can also meet capacity limits, such as Dataverse database, file and log storage and API request allowances. Think of them as quotas attached to licenses and tenants.

Which license does my app need?

Ask three questions:

  1. Which connectors and features does the app use? Any premium one makes the whole app premium.
  2. Who will run it, and how many apps will each person need?
  3. Does it use Dataverse (including model-driven apps)?

The stand-in below turns those questions into a function. It is a simplified model for learning, not Microsoft's official calculator.

JS Stand-in: does this app need a premium license?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Counting what a rollout would cost

Costs depend on how many users run how many apps. The next stand-in compares a per-app and a per-user plan with made-up prices, only to show the shape of the reasoning: per-app is cheaper for few apps, per-user wins as the number of apps grows.

JS Stand-in: per-app versus per-user (invented prices)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Practical advice

  • Start with the Developer Plan to learn, then ask your admin for a sandbox environment.
  • Avoid building business-critical apps in the default environment.
  • Document the connectors of each app; the licensing requirement follows them.
  • Remember that sharing an app with users who lack a license makes it fail to open for them.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. An app uses SharePoint and one premium connector. Who needs a premium-capable license?

    One premium connector makes the app premium for all of its users.
  2. 2. What is an environment?

    Environments separate work, data and security, for example Dev, Test and Prod.
  3. 3. Which plan is meant for learning and testing and is free?

    The Developer Plan gives you a personal development environment, not a license for broad production use.
  4. 4. Why avoid building critical apps in the default environment?

    The default environment is shared by all users and is poor for controlled delivery.

Summary

  • Environments separate development, testing and production work.
  • Connectors and features are standard or premium; one premium item makes the app premium.
  • Plans include seeded rights, per-app, per-user, Developer and pay-as-you-go.
  • Prices and names change, so check official sources.

Next: Power Apps Studio and the maker portal