Microsoft Power Pages is one of the most strategically positioned products in the Power Platform stack — and one of the least understood by Microsoft partners. It’s the low-code platform Microsoft built for external-facing websites: customer portals, partner portals, citizen service sites, vendor onboarding, anything that needs to live outside the firewall and talk natively to Dynamics 365 and Dataverse.
For partners, the question isn’t whether Power Pages is a real platform anymore — Microsoft answered that with the 2022 rename from Power Apps Portals and the GA of Server Logic in April 2026. The question is when to use it, when not to, what it costs, and how to deliver it well at scale.
This guide covers what Microsoft Power Pages is in 2026, the features partners need to know, current pricing, real use cases, and where the platform fits in the Microsoft delivery conversation.
What Is Microsoft Power Pages?
Microsoft Power Pages is a low-code platform inside the Microsoft Power Platform for building secure, data-driven, external-facing websites. It connects natively to Microsoft Dataverse, integrates with Dynamics 365, supports authenticated and anonymous user access, and runs on Microsoft’s managed cloud — no separate hosting to provision.
Power Pages replaced Power Apps Portals in October 2022. The underlying technology evolved from Adxstudio, which Microsoft acquired in 2015 and built into the Dynamics CRM portals product. That history matters: Power Pages is not a new platform — it’s the most mature external-facing web product in the Microsoft stack, with more than a decade of partner delivery behind it.
Who Power Pages Is For
Power Pages is built for organisations that need to:
- Give customers, partners, vendors, or citizens secure access to data living in Dataverse or Dynamics 365
- Build branded external websites without standing up a separate web hosting environment
- Combine low-code speed with pro-code extensibility for complex business logic
- Integrate AI agents, Copilot, and Power Platform automation into external user experiences
It’s not the right platform for marketing brochure sites, content-heavy publishing, or e-commerce with high product catalogue complexity. For those, traditional CMSs and dedicated commerce platforms still win.
Key Features of Power Pages in 2026
Power Pages has matured significantly in the last 24 months. The 2026 feature set partners need to know about:
Low-Code Design Studio
A drag-and-drop design environment for building pages, forms, lists, and navigation. Templates include prebuilt sites for Dynamics 365 Customer Service, Field Service, Partner Portal, and industry verticals like government and education. Real low-code productivity, but the templates are starting points — most partner builds go well beyond them.
Native Dataverse and Dynamics 365 Integration
This is Power Pages’ biggest moat. Forms, lists, and data grids connect directly to Dataverse tables — including custom and virtual tables, system tables, and Dynamics 365 application tables. Permissions are managed through web roles and table permissions, so a partner can map portal access directly to the Dataverse security model.
Pro-Code Extensibility
For anything the low-code studio can’t do, partners can drop down to code. Liquid templates handle server-side rendering, JavaScript handles client behaviour, CSS handles styling, and as of April 2026, Power Pages server logic handles secure server-side execution. The platform also supports Power Pages CLI for VS Code development and full ALM via solutions.
Modern Frontend Options
Power Pages now supports a Power Pages SPA preview model for pro-code teams building React-based single-page experiences. Combined with server logic on the backend, this gives partners a credible alternative to running Power Pages alongside a separate React app and Azure Functions stack.
AI and Copilot Integration
Copilot is integrated into the design studio for generating pages, forms, and content from natural language prompts. Copilot Studio agents can be embedded into Power Pages sites to handle support, FAQs, and workflow triggering. For partners delivering AI-enabled portals in 2026, Power Pages is the lowest-friction option in the Microsoft stack.
Enterprise Security
Authentication providers include Microsoft Entra ID, Entra External ID (B2C), LinkedIn, Google, Microsoft, and custom OpenID providers. Role-based access through web roles, page-level and table-level permissions, multi-factor authentication, and CDN-backed delivery. All standard for an enterprise external-facing platform.
Content Delivery Network
Built-in Microsoft-managed CDN for global performance, included in paid tiers. Partners don’t need to configure Azure Front Door or Cloudflare separately for standard portal performance needs.
Microsoft Power Pages Pricing in 2026
Microsoft Power Pages uses a capacity-based pricing model. The 2026 price points (as listed on Microsoft’s official pricing page):
| Plan | Price | What You Get |
|---|---|---|
| Free trial | Free for 30 days | Full feature access, branded sites, templates, Dataverse connection — 2 GB database, 16 GB file capacity |
| Authenticated users per website | $200 per 100 users / site / month, paid yearly | Authenticated portal access, CDN, 2 GB database + 16 GB file capacity per subscription |
| Anonymous users per website | $75 per 500 users / site / month, paid yearly | Anonymous browsing, CDN, 500 MB database + 4 GB file capacity per subscription |
A few things partners need to flag for clients:
- Users are metered per website per calendar month — a user accessing two Power Pages sites consumes capacity in both
- Capacity packs are sold at 100 authenticated or 500 anonymous units — not per individual user
- Capacity is environment-level — not user-assigned, which simplifies licensing administration
- Dataverse capacity pools at the tenant level — partners should plan storage across the broader Power Platform footprint
The model rewards scale. For a partner portal with 5,000 authenticated users hitting one site, the cost is $10,000 per month — predictable and significantly cheaper than the equivalent custom-built and hosted alternative once you factor in development, hosting, and security overhead.
Real-World Use Cases for Power Pages
Power Pages fits a specific shape of project. The use cases partner delivery teams see most often:
Customer Self-Service Portals
The most common Power Pages use case. Customers log in to view their accounts, submit support requests, track service tickets, download invoices, manage subscriptions, and access knowledge base content. Native Dynamics 365 Customer Service integration means the portal is reading and writing to the same case, contact, and account tables the agent uses.
Partner Portals
Distributor, reseller, and channel partner portals built on the same Dynamics 365 backend the internal sales team uses. Partners log in to register deals, access marketing materials, submit co-op claims, and view performance dashboards. Web roles map partner organisations to access scopes.
Citizen Service and Government Portals
Permit applications, grant management, complaint intake, citizen service requests, volunteer coordination. Government departments use Power Pages to digitise paper-based processes while keeping the data inside a secure, audited Microsoft cloud environment.
Vendor and Supplier Portals
Vendor onboarding, contract management, purchase order acknowledgment, invoice submission, shipment visibility. Direct integration with Dynamics 365 Finance and Operations or Business Central makes Power Pages the natural front-end for supplier engagement.
Industry-Specific Portals
Patient portals (healthcare), matter management portals (legal), student portals (education), member portals (associations and not-for-profits). Where the back-office runs on Dynamics 365 or Dataverse, Power Pages is the lowest-friction way to give external users access.
When to Use Power Pages (and When Not To)
Power Pages is a sharp tool, but not a universal one. Where it wins and where it doesn’t:
Use Power Pages When
- You need an external-facing site that reads or writes Dataverse or Dynamics 365 data
- Authentication, role-based access, and per-user permissions matter
- The build needs to ship in weeks, not months
- The client already runs on Microsoft Power Platform or Dynamics 365
- AI and Copilot integration are part of the requirement
Don’t Use Power Pages When
- The site is primarily marketing content with no Dataverse interaction (use WordPress, Webflow, or similar)
- You need a high-volume transactional e-commerce platform with complex product catalogues
- Public-facing performance demands sub-100ms response with millions of concurrent anonymous users
- The data backend is non-Microsoft and won’t be moving (Power Pages can connect to external sources, but its value collapses without Dataverse)
Power Pages vs Power Apps Portals — What Changed
For partners who haven’t touched a portal build since the Power Apps Portals era, here’s what’s changed in the last three years:
| Capability | Power Apps Portals (pre-2022) | Power Pages (2026) |
|---|---|---|
| Brand | Power Apps Portals | Microsoft Power Pages |
| Design studio | Basic, primarily configuration | Full visual design studio with templates |
| AI/Copilot | None | Native Copilot integration for page generation |
| Server-side code | Liquid + Azure Functions | Liquid + server logic (GA April 2026) |
| Modern frontend | Limited | SPA preview model with React support |
| Pricing | Per authenticated/anonymous user | Capacity packs (100 auth / 500 anon per site) |
| Pro-code tooling | Power Pages CLI in VS Code | Mature CLI + full ALM via solutions |
The most important change for partner delivery: Power Pages in 2026 is a credible pro-code platform, not just a low-code site builder. That changes which projects partners can confidently propose Power Pages for.
How MTC Delivers Microsoft Power Pages for Partners
MTC has been delivering on the Power Pages stack since the Adxstudio days — over a decade of portal builds across customer service, legal, healthcare, government, and vendor management verticals. Our delivery model is built specifically for Microsoft implementation partners who need a development-first portal team without hiring one in-house.
A typical engagement covers:
- Architecture and design — Dataverse data model, web role and permission mapping, authentication flow
- Implementation — page and form development, Liquid and JavaScript customisation, server logic for secure backend operations
- Integration — Dynamics 365 sync, external API calls, Power Automate orchestration, AI agent embedding
- ALM and governance — solution-based deployment, environment promotion, code reviews, security review
- Post-launch support — monitoring, performance optimisation, ongoing enhancement
We work as a Microsoft Power Pages partner behind the scenes for Microsoft CSPs, ISVs, and boutique consultancies — the client never sees us, you keep the relationship.
For partners running broader portal programmes, we also deliver hybrid builds combining Power Pages with custom React or .NET layers through our Power Pages portal development services.
Frequently Asked Questions
When should partners choose Power Pages instead of WordPress or a custom web application?
The deciding factor is what’s behind the login. If users need to read or write Dataverse or Dynamics 365 data with role-based permissions, Power Pages wins on every metric we measure — speed of build, ongoing maintenance, security posture, and total cost. We’ve shipped Power Pages portals for legal matter management, government citizen services, and partner deal registration where Dataverse was the entire reason the portal existed. For a content-led site that doesn’t touch Dataverse, we recommend WordPress and don’t push Power Pages — it’s the wrong tool.
How long does a typical Power Pages implementation take?
Our shipped timelines: a basic customer self-service portal lands in 4–6 weeks. A partner portal with multiple user roles, deal registration, and Dynamics 365 sync runs 8–12 weeks. An industry-specific build with custom integrations, AI agent embedding, or complex workflow design typically takes 12–16 weeks. The biggest variable isn’t the build itself — it’s whether the client’s Dataverse data model is ready. We’ve seen 4-week projects stretch to 10 weeks when data model decisions get made mid-build.
Is Power Pages worth the cost compared to building a custom portal?
For organisations already running on Microsoft, the math works in Power Pages’ favour almost every time. The platform includes hosting, CDN, authentication, security patching, and native Dataverse integration in the licence — none of which is free on a custom build. Where it stops making sense: very high-volume anonymous public sites (the per-500-anonymous-user model gets expensive past 50,000 users), and any portal where the back-end is non-Microsoft. We’ve had clients save 40–60% over their custom React + Azure quote by going Power Pages — but we’ve also told clients to walk away from Power Pages when their use case didn’t fit.
Conclusion
Microsoft Power Pages in 2026 is a more capable, more credible platform than most partner conversations give it credit for. The combination of Server Logic, SPA preview, Copilot integration, and a decade of mature delivery patterns makes it the lowest-friction external-facing platform in the Microsoft stack — provided the use case fits.
For Microsoft partners planning a customer portal, partner portal, vendor portal, or citizen service build, Power Pages should be the default architectural starting point. When the use case fits, it ships faster, costs less, and integrates more cleanly than any alternative.
Need a development-first Power Pages partner for your next engagement? Talk to MTC’s Power Pages team — 80+ Microsoft consultants in Hyderabad, 25+ AppSource add-ons live, white-label delivery for Microsoft partners worldwide.
