ARTICLE · DYNAMICS 365 · POWER PAGES

Customer and partner portals with Power Pages: what they are for, what they cost, how they are built

In short: Microsoft Power Pages is the web front end of Dynamics 365 and Dataverse for external users, the successor of Power Apps portals (originally Dynamics 365 portals). Customers, partners or suppliers sign in and see and edit the same Dataverse data your internal team works with in Dynamics 365 – but only what the table permissions allow. Licensing is per website and number of users: Microsoft’s list price is USD 200 per month for 100 authenticated users and USD 75 per month for 500 anonymous users.

What is Power Pages?

Power Pages is part of the Microsoft Power Platform: it is used to build secure business websites that work with data stored in Dataverse. Microsoft launched it as a standalone product in 2022, building on the capabilities of Power Apps portals. If your company uses Dynamics 365 Customer Service or Sales, the portal reads and writes the same tables (case, contact, account, knowledge article) – no separate database and no synchronisation.

DataDataverse is the shared data layer: a case submitted on the portal appears for the agent in Dynamics 365 immediately. More: Microsoft Dataverse.
Front endDesign studio with templates, pages, forms and lists; Liquid templates, JavaScript and CSS for fine-tuning.
SecuritySign-in through external identity providers, web roles, table and column permissions.

Which portals are built with Power Pages?

PortalFor whomTypical functions
Customer self-service portalcustomerscreating and tracking cases (tickets), knowledge base, own data
Partner portalresellers, distributors, supplierssharing leads and opportunities, joint activities, documents
Registration or supplier portalapplicants, registrants, suppliersforms, document upload, status tracking
Event portalattendeesregistration, sessions, confirmation

Microsoft also provides Dynamics 365 templates, including customer self-service and partner portals. They are available when the environment runs a Dynamics 365 app (Sales, Customer Service, Field Service). A template is a good starting point, but real portals usually get their own forms, processes and branding.

Security: contacts, web roles, table permissions

A portal user is a contact record in Dataverse, with a permission model separate from the Dynamics security roles of internal staff:

Web roleLinks users and permissions. A user can have several web roles; the rights add up.
Table permissionDefines which Dataverse rows a role may see and change – for example only the cases of the user’s own account.
Page and column permissionsHide or protect whole pages or individual columns.
Microsoft’s security guidance warns against global table permissions for sensitive business data, because they open every row of the table to the role. Most portal issues come from this setting, so before go-live we test the permissions role by role.

Sign-in: Entra External ID, Azure AD B2C or local accounts?

  • External identity provider: Power Pages supports OpenID Connect, SAML 2.0 and WS-Federation providers and social sign-in, including Microsoft Entra External ID.
  • Azure AD B2C: according to Microsoft’s FAQ it has not been available to new customers since 1 May 2025; existing tenants keep working. For new projects Microsoft Entra External ID is therefore the natural choice.
  • Local accounts: the portal’s own username and password. Microsoft Learn recommends moving to an external provider and offers a setting to deprecate local sign-in.
  • Internal staff: can sign in to the same portal with the company’s Microsoft Entra ID.

Connection to Dynamics 365 Customer Service and Sales

Copilot and AI agents on the portal

In the Power Pages design studio, Copilot can draft a site, a page or a form from a text description – this speeds up the first version, but the final structure and the permissions still have to be designed. The site agent for visitors answers from the site’s content by default and can be extended with Copilot Studio. Part of the documentation describes preview features, so we check the exact capabilities before implementation.

What does a Power Pages licence cost?

LicenceUnitList price (USD, paid yearly)
Authenticated users100 users / site / monthUSD 200
Anonymous users500 users / site / monthUSD 75
Pay-as-you-gomonthly active users, via an Azure subscriptionby actual usage
  • Capacity is counted per website: a user who signs in to two portals counts on both.
  • In the pay-as-you-go model the company pays for monthly active users through an Azure subscription; worth comparing for small or fluctuating user numbers.
  • Internal staff use Dynamics 365 or Power Apps licences, not portal capacity.

We supply licences as well: Microsoft 365 and Dynamics 365 licensing.

Data protection and security (GDPR)

  • Data minimisation: expose only the columns external users really need.
  • Registration and consent: invitation-based or approved registration, privacy notice, cookie handling.
  • File upload: size and type limits; uploaded documents stored in Dataverse or SharePoint with controlled permissions.
  • Auditing and testing: Dataverse auditing records changes; before go-live we test permissions and security.

When is Power Pages not the right choice?

If you only need a company website, a campaign landing page or a blog, without sign-in and without Dataverse data, a conventional website is cheaper and more flexible. Power Pages pays off where external users work with company data: they submit requests, follow status, upload data, and it appears in Dynamics 365 immediately.

How is a Power Pages portal built?

  1. Requirements: who signs in, what they see, what they may change, which processes they start.
  2. Data model and security: tables, web roles, table permissions, identity provider.
  3. Front end: template or custom structure, branding, forms, lists, multiple languages.
  4. Automation and integration: Power Automate, notifications, external systems.
  5. Testing: permission tests per role, load and security aspects.
  6. Go-live and operations: development, test and production environments, solution-based deployment, follow-up: Dynamics 365 support.

We also work as an EU nearshore partner: Dynamics 365 nearshore partner.

Frequently asked questions

What is the difference between Power Pages and Dynamics 365 portals?

It is the same product line: Dynamics 365 portals became Power Apps portals, which became Power Pages in 2022. It still builds on Dataverse data, with a new design studio and Copilot features.

Do I need Dynamics 365 for Power Pages?

No, Power Pages also works on its own in a Dataverse environment. If the portal has to work with service cases or sales data, Dynamics 365 Customer Service or Sales provides the data and the internal interface.

What does a customer portal licence cost?

Microsoft’s list price is USD 200 per website per month for 100 authenticated users and USD 75 per month for 500 anonymous users (paid yearly); there is also a pay-as-you-go model. Development cost depends on the requirements, so we quote after an assessment.

Which sign-in should the portal use?

For new projects Microsoft Entra External ID, because Azure AD B2C has not been available to new customers since 1 May 2025. Microsoft also recommends deprecating local username and password sign-in.

Is Power Pages secure?

Yes, if permissions are configured properly: web roles, table and column permissions, and no global permissions on sensitive data. Before go-live we test access role by role.

Can the portal have a chatbot?

Yes: the site agent answers from the site’s content by default and can be extended with Copilot Studio. Some features are still in preview.

Let’s talk about your project.

Tell us what you are planning and we will get back to you within a few days.

Get in touch

Cookie settings

Choose what you consent to. We remember your choice for 6 months; change it any time via “Cookie settings” in the footer.

Privacy notice