Microsoft Power Pages Enterprise Portals Guide (2026)

Power Pages is the right choice when the audience is external (customers, partners, citizens, vendors, applicants), the data already lives in Dataverse or will be put there, the workload is form-driven and content-driven rather than highly interactive, and the team owns or is building Power Platform skills. Canvas Power Apps are the right choice when the audience is internal employees on mobile devices, when the experience is pixel-precise and highly interactive, and when the Dataverse/SharePoint/SQL backend is appropriate. A custom Next.js build (the path EPC Group also delivers) is the right choice when the experience needs to be a marketing site at internet scale, when the design fidelity Power Pages can deliver is not enough, when there is heavy non-Dataverse data integration, or when the audience expects a consumer-grade brand experience the no-code platform cannot match. We have shipped patient portals on Power Pages and we have also told clients the right answer was Next.js on Vercel — pick on fit, not on platform allegiance.

Power Pages licenses two distinct capacity types and they are billed separately. Anonymous-user capacity is sold in packs of 100 anonymous monthly users — that is unique visitors counted by Power Pages telemetry per calendar month. Authenticated-user capacity is sold per authenticated monthly user — every distinct identity that signs into the portal in a calendar month counts toward this band. Authenticated users include B2C identities (Entra External ID), B2B guests (cross-tenant SSO), and custom identity providers. The two axes are independent — a portal can be heavy on one and light on the other, and you license both bands separately. EPC Group models both during architecture, builds a conservative initial license forecast, and includes capacity monitoring as a steady-state managed-operations responsibility. SKU details and pack sizes change; verify with Microsoft licensing at purchase date.

Dataverse capacity is licensed in three bands — database (the relational store), file (binary attachments, file-column content), and log (audit logs and long-running operations). Power Pages portals touch all three. A customer-service portal handling 200,000 cases per year with attachments will burn through file capacity faster than database capacity. A partner portal with light transaction volume but a five-year regulatory retention requirement will burn through log capacity. A vendor-onboarding portal collecting W-9 PDFs, COI PDFs, and qualification packets is file-heavy. EPC Group sizes each band during the Assess phase, recommends initial capacity, and instruments capacity monitoring as part of managed operations. Most enterprises buy too much database capacity and too little file capacity — the file column allowance per environment is finite and worth modeling.

Yes, and EPC Group treats this as table stakes. Power Pages content is exported and unpacked through the Power Platform CLI and source-controlled in Git alongside the rest of the solution. Power Platform Pipelines orchestrates promotion from dev to test to production environments, with approval gates between stages. The Power Platform Solution Checker runs on pull requests and blocks merges with critical findings. Managed solutions are the default for everything reaching production. The non-negotiables are the same ones we apply across the Power Platform — no maker authoring directly in production, no shortcut deploys, no unmanaged solutions in prod. Power Platform Pipelines is the native Microsoft surface; Azure DevOps Pipelines and GitHub Actions are both supported alternatives for teams already standardized there.

The Power Pages platform ships with accessibility-compliant building blocks — Bootstrap 5 components, accessible forms, ARIA-aware navigation, keyboard-navigable lists. The platform passes WCAG 2.1 AA at the component level. What the platform does not do is guarantee your custom content, your custom Liquid, your custom PCF components, your custom themes, or your editorial choices pass WCAG 2.1 AA. Accessibility on a Power Pages portal is the responsibility of the team that builds it — not the platform. EPC Group includes WCAG 2.1 AA testing in every portal engagement, runs accessibility audits before launch, and ships portals to government clients under Section 508 standards. The earlier accessibility is designed in, the less expensive it is to remediate — retrofitting accessibility two weeks before launch is a project all on its own.

Yes, through Power Automate and through custom code. The pattern is that the portal binds to Dataverse for the user-facing experience, and Power Automate cloud flows handle the integration with whatever system of record sits behind the workflow. A partner portal that needs to write opportunities to Salesforce uses a Power Automate flow with the Salesforce connector. A vendor portal that needs to read PO data from SAP uses Power Automate with the SAP ECC connector or a custom REST connector. A service portal that writes incidents to ServiceNow uses Power Automate with the ServiceNow connector. For high-volume or real-time scenarios, Azure Integration Services (Logic Apps, Service Bus, API Management) carries the traffic and Dataverse holds the working copy. EPC Group designs the integration architecture during the Assess phase — picking the right surface (Power Automate, Azure, custom code in a PCF component) for each integration.

They are different tools for different jobs. SharePoint external sharing — through guest accounts, Microsoft 365 groups with guest access, or SharePoint sites with external sharing enabled — is the right surface when the use case is document collaboration with named external counterparts. Think of a customer who needs to review draft contracts, a partner who needs to share product roadmaps, a vendor who needs to upload qualification documents. SharePoint is excellent at this and the per-user cost is favorable when the audience is small. Power Pages is the right surface when the use case is a structured application — forms, workflows, data capture, transaction processing, status tracking — that needs to scale to hundreds or thousands of external users, with a branded experience, with audience-specific identity, and with table-row-level security. Mixing the two is common — a Power Pages portal often surfaces SharePoint document libraries through embedded content for the document-collaboration parts of the journey.

The EPC Group Power Pages Accelerator runs $120,000 to $400,000 depending on portal complexity, the number of audiences (a partner portal serving distributors, resellers, and brokers is three audiences), the depth of integration (one Dataverse-only flow versus six external-system flows), the regulatory scope (HIPAA, FINRA, CMMC, FedRAMP-relevant), and the design fidelity required. Common bands — a single-audience customer self-service portal on Dataverse with one Salesforce integration and standard branding lands near the $120,000 floor. A multi-audience partner extranet with deal registration, commission visibility, three external integrations, custom PCF components, and a complete brand-system implementation lands near the $400,000 ceiling. Most engagements land in the $185,000 to $275,000 band. Managed operations and quarterly enhancement releases are priced separately to the portal footprint. Microsoft license costs (Power Pages capacity, Dataverse capacity, Entra External ID identities) are separate and modeled during Assess.