Power Pages for external-facing portals: what to know before you start

Power Pages is Microsoft's answer to external-facing web portals on the Power Platform. It handles authentication, Dataverse integration, role-based access control for external users, and responsive design — all with a studio that business teams can participate in meaningfully.

It is also a tool with some architectural decisions that will surprise you if you go in without preparation.

The authentication model

Power Pages handles external user authentication differently from internal Power Apps. External users authenticate through identity providers — Azure AD B2C, Azure AD, Microsoft, Google, LinkedIn, or local accounts.

The most important decision you make early is which identity provider to use. For business-to-business portals, Azure AD federation (where your customer's employees use their own corporate credentials) is usually the cleanest experience. For consumer-facing portals, local accounts or social login providers work well.

Plan your authentication strategy before you build anything. Changing it later is painful.

Table permissions: Dataverse for external users

External users in Power Pages access Dataverse through table permissions — a permission model specific to portals that is separate from the standard Dataverse security roles.

Table permissions define what external users can do with each table: read, create, write, delete, append, append to. Critically, they can be scoped to records related to the authenticated user — so a customer can only see their own orders, not all orders in the system.

This is powerful but requires careful design. Spend time mapping out which tables each user role needs access to and at what scope before you start configuring permissions.

Liquid templating

Power Pages uses Liquid — an open-source templating language — for dynamic content on pages. If you have developers involved, they will be comfortable with it quickly. If your stakeholders expect no-code, there is a learning curve.

The Power Pages Studio lets you do a lot without touching Liquid. But any serious portal customisation eventually touches Liquid templates. Plan for this in your team's skill set.

Performance and caching

Power Pages has its own caching layer that can make changes take time to appear. When you are iterating on page content during development, you will frequently need to clear the server-side cache to see updates. This is not a bug — it is how the platform manages performance — but it will frustrate developers who are used to seeing changes immediately.

Add "clear portal cache" to your development workflow documentation on day one. Your team will thank you for it.

Licensing

Power Pages licensing is based on the number of monthly active users (authenticated) or page views (anonymous). This is different from most Power Platform licensing and can surprise finance teams used to per-seat models.

Estimate your expected user volumes before you commit to a portal architecture. For very high volume external-facing scenarios, the numbers may point you toward a different architecture.