Power Pages is a low-code, secure, enterprise-grade platform from Microsoft that enables organizations to build external-facing websites. These websites allow users—both internal and external—to interact with data stored in Microsoft Dataverse, perform business functions, and access various services.
Unlike internal Power Apps which are accessed by authenticated users within the same organization, Power Pages often need to serve external users (like partners, customers, or citizens), which introduces specific licensing and pricing requirements.
Understanding licensing is crucial to ensure compliance, manage costs effectively, and offer seamless digital experiences to external users.
1. Types of Users in Power Pages
Power Pages classifies users into the following types:
1.1 Authenticated Users
These are users who sign in using:
- Azure Active Directory (AAD)
- Microsoft Accounts
- External identity providers like LinkedIn, Facebook, Google, etc.
- Local authentication (username and password stored in the portal itself)
1.2 Anonymous Users
These are users who access your website without signing in. For example, when visiting a public webpage that doesn’t require login.
1.3 Internal Users
These are licensed Microsoft 365 or Dynamics 365 users inside the organization who access the Power Pages website via their enterprise credentials.
2. Licensing Models for Power Pages
Licensing for Power Pages is not user-based, as with other Microsoft services, but primarily usage-based, i.e., based on the number of authenticated users, anonymous users, and capacity used.
There are three core licensing models:
3. Authenticated User Licensing
3.1 Per Website Monthly Active Users (MAU)
Microsoft charges based on the number of unique authenticated users per website per month.
Key Points:
- Each user is counted only once per website per month, regardless of the number of logins.
- Pricing starts at a fixed tier (e.g., 100 users/month).
- If more users access the portal, charges are applied for the excess number of users.
- Additional user capacity can be purchased in packs.
Example:
If you have 150 unique users accessing your Power Pages website in a month:
- First 100 users: Covered by base tier
- Next 50 users: Covered via add-on packs
4. Anonymous User Licensing
4.1 Per Page View Model
Anonymous users are priced based on the number of page views per month.
Key Points:
- Page views include all requests made by anonymous users on your portal.
- Licensing is tiered, starting from a baseline threshold (e.g., 500K page views/month).
- Additional page views are purchased in packs (e.g., 500K page views per pack).
Important:
If your portal has high public traffic (like a government service portal), it’s crucial to estimate page views and purchase capacity accordingly.
5. Capacity Licensing (Dataverse)
Power Pages consumes Dataverse storage, and storage is not included with Power Pages licenses. Organizations must separately license Dataverse storage for:
- Dataverse Database (Data)
- Dataverse File (File storage)
- Dataverse Log (Audit and log data)
Your usage of Power Pages—especially if it involves uploading files or storing large volumes of records—will impact Dataverse capacity requirements.
6. Licensing for Internal Users (Optional Use)
If internal licensed Microsoft 365 or Dynamics 365 users access the Power Pages website, and they are accessing functionality that they already have access to via their existing license, they are not charged again under Power Pages.
Example:
An internal Dynamics 365 Sales user accessing customer records via the portal doesn’t need a separate license.
7. Licensing Components Summary
| Component | Licensing Type | Notes |
|---|---|---|
| Authenticated Users | Monthly Active Users (MAU) | Counted per unique user per month |
| Anonymous Users | Per Page View | Based on anonymous traffic |
| Dataverse Storage | Capacity-based | Charged separately |
| Internal Users | Existing Microsoft License | No additional license needed if accessing licensed services |
8. How to Purchase Power Pages Licenses
Licenses can be purchased in Power Platform admin center or via Microsoft Volume Licensing channels.
Available Packs:
- 100 Authenticated Users per Website
- 500K Anonymous Page Views per Website
- Additional capacity packs for Dataverse
Pricing may vary by region and agreement type. Always confirm the current rates via Microsoft’s pricing calculator or with your Microsoft Account Manager.
9. Monitoring & Reporting Usage
Microsoft provides tools to monitor your website’s usage:
- Power Platform Admin Center – To monitor MAU and page views.
- Azure AD Sign-in Logs – To track authentication patterns.
- Dataverse Analytics – To check storage usage and performance.
It is highly recommended to set up alerts or dashboards to avoid overages and ensure optimal capacity planning.
10. Trial and Development Use
Microsoft allows:
- Free development environment for Power Pages using the Power Apps Developer Plan.
- Limited access and usage but not for production use.
Trial environments are useful for:
- Testing
- Proof of Concept (POC)
- Learning
However, for production use, you must have proper licensing.
11. Licensing Scenarios
Scenario 1: A Customer Support Portal
- Requires authenticated access (login via email and password)
- 200 customers log in monthly
- Use case: Submit support tickets, track requests
Licensing Required:
- 100 Authenticated User base license
- 100 Authenticated User add-on license
- Dataverse capacity (for ticket data)
Scenario 2: A Public Info Website
- No login required
- 1M page views/month from anonymous users
Licensing Required:
- 500K base pack
- 1 add-on pack for 500K page views
Scenario 3: Internal Staff Portal
- Used by employees only
- They already have Microsoft 365 licenses
- Use for internal HR functions
Licensing Required:
- None for Power Pages (if only internal use and licensed users)
- Dataverse storage may still be needed
12. Licensing Misconceptions
Misconception 1: Power Pages is free with Microsoft 365
- False. Power Pages is a separate service, billed differently.
Misconception 2: Internal users don’t require any license
- Partially True. Only if the internal user already has the required Microsoft 365 or Dynamics 365 license and accesses data/functionality covered by their license.
Misconception 3: All traffic is anonymous until login
- Incorrect. Anonymous traffic is any access before login. As soon as the user logs in, they’re treated as authenticated users.
13. Best Practices for Licensing
- Estimate usage accurately: Monitor your user traffic patterns before choosing the licensing tier.
- Avoid overages: Set up alerts and reports.
- Combine services wisely: Leverage Azure AD B2C for scalable authentication if needed.
- Use Developer Plan for development, not production.