Power Pages
Power Pages: portals for customers, partners and members.
With Power Pages, customers, partners or members sign in, submit requests and see their own data from Dataverse. Table permissions decide who sees what.
For organisations whose customers, partners or members should submit requests and see their own data online.
- Power Pages
- Dataverse
- Entra External ID
- Copilot Studio
- Power Automate
- Power Platform CLI

Portal or website
Power Pages fits when external people sign in and work with your data: a customer portal with orders, a partner area with documents, requests from members. A public website with editors and a website agent we build on a headless CMS. The two connect when an enquiry later continues in the portal.
Sign-in, forms, permissions
We set up sign-in, build pages and forms on Dataverse tables and define who sees which records. Requests go into processing through Power Automate, and your team sees them in a model-driven app. Design and copy follow your brand. The building blocks of a portal:
- Sign-inCustomers register through Microsoft Entra External ID, partners sign in with their company account, members with an account they already have.Result: every person has an account your IT knows and can block.
- Forms and listsRequests, orders and documents live in Dataverse tables, with required fields, validation rules and file storage.Result: a request reaches the responsible person complete.
- Web roles and table permissionsAccess per account, per company or per membership, separate for reading, creating and changing.Result: a customer sees her company's orders and no others.
- Server logicJavaScript on the server validates input, queries your ERP or an Azure Function and keeps credentials away from the browser.Result: status, prices and availability come current from the business system.
- Agents in the portalAn agent from Copilot Studio answers questions from the portal content or helps fill in a form; web roles decide who sees it.Result: simple questions are answered before anyone picks up the phone.
- Your own interfaceA React, Angular or Vue application runs as a single-page app on Power Pages, built with Claude Code or GitHub Copilot.Result: the design is free, and web roles and table permissions still apply.
Who signs in and what is visible
We clarify which groups sign in, which data they may see and change and how many people use the portal, because licensing counts authenticated and anonymous visitors per website. An agent in the portal also consumes Copilot Credits. For personal data we record what is stored and logged.
Checked with external test users
External test users sign in, submit a request and see only their own records. We check web roles, form validation, accessibility, the agent's answers and the handover to your team. A process for content and permissions and a responsible person are part of the handover.
Sound familiar? Tell us where you stand today.
ContactWhat's new.
As of: October 2026
- Since April 2026
Server logic is generally available.
JavaScript runs on the server, protected by web roles and table permissions, and calls Dataverse actions, REST interfaces or Azure Functions. Administrators can block outbound calls per website. Keys for business systems stay on the server.
Source: Microsoft Learn: Power Pages server logic overview - As of July 2026
Portals as single-page apps.
Power Pages accepts React, Angular or Vue applications, uploaded through the Power Platform CLI. Web roles and table permissions apply to every Web API call. Liquid and the pages and styling workspaces are not available for these websites, and search engines index them only to a limited extent.
Source: Microsoft Learn: Create and deploy a single-page application - As of July 2026
Several agents on one website.
Agents are created in the Set up workspace or directly from a form. Visitors see the agents their web role allows and switch between them in the chat window. When a person is needed, the agent can hand over to Dynamics 365 Customer Service.
Source: Microsoft Learn: Add an agent to Power Pages - Since May 2026
Move from Azure AD B2C with the existing user directory.
The High Scale Compatibility mode of Microsoft Entra External ID is generally available. It keeps the existing user directory while portals and applications move to External ID step by step. Some advanced customisations are limited in this mode.
Source: Microsoft Learn: What's new in Microsoft Entra
External users on shared data.
Partners who work on the same Dataverse foundation as the internal team at AEW myHome, and coupons that AEW customers redeem through a web portal, with shared reporting.
Related to your task
How customers, partners and members work on shared data, from request to reporting.
Business appsThe internal app in which your team processes requests from the portal.
Agentic websitesThe public website with editors and an agent that passes enquiries into the portal.
ERP integrationShow orders, invoices and master data from Abacus, bexio or SAP in the portal.
Data protection under the FADPWhat a portal stores, logs and deletes again when it handles personal data.
What people ask before the first portal.
Do our customers need a Microsoft account?
No. Customers register with their email address through Microsoft Entra External ID or sign in with an account they already have. Partners with their own Microsoft 365 use their company account. Which routes you allow, we define per group.
How is Power Pages licensed?
Per website, by authenticated and anonymous visitors per month, through capacity packs or pay-as-you-go through an Azure subscription. An agent in the portal also consumes Copilot Credits. We estimate usage with you and read it off in the pilot before the portal opens to everyone.
Can we decide the design freely?
Yes. In the design studio we adapt colours, fonts and page layout to your brand. If the interface should be entirely your own, we build it as a single-page app with React or Vue; the same permissions then apply, but search engines index the pages only to a limited extent.
How does data from our ERP reach the portal?
In two ways: server logic queries the business system on every call, or Power Automate syncs the data with Dataverse at regular intervals. When a detail such as a delivery status must be current, we choose the query, for master data the sync. We plan the connection to Abacus, bexio or SAP with your system owners.
What applies to personal data in the portal?
We record which details the portal stores, who sees them, what is logged and when data is deleted. We create the Dataverse environment in the region your requirements call for. For access requests we set up a process with which your team finds all data on a person.
Agree on a useful next step
Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.


