Breaking the Shackles of Legacy Portals: Power Pages as Enterprise SaaS

Single-Page Application support in Power Pages reached General Availability on February 8, 2026, starting with site version 9.8.1.x and later. Developers can now build fully custom, client-side-rendered web applications using React, Angular, or Vue and deploy them directly to Power Pages with the Power Platform CLI. This is not a workaround or a bolt-on—Microsoft describes this GA release as making the SPA experience “production-ready”.  

What this means in practice: the traditional portal constructs—ASP.NET and Liquid templates, web forms, lists—become optional implementation details, not architectural constraints. Your UI is completely custom and API-driven, calling Power Pages Web APIs for all data operations. The GA release also fixed issues where Power Pages platform styles could override custom CSS and added updated guidance for authentication configuration and local development setup. Developers can run SPAs locally with full authentication and Web API access, plus hot reload and local debugging, without deploying changes to the portal on every iteration. 

At this point, the traditional portal schema becomes an implementation option—not a constraint. 

(Ensure your Power Platform CLI is on the latest version for full capabilities.)

Power Pages connects to Microsoft Dataverse, but you are no longer forced to borrow a Dynamics 365 schema. Teams can design their own data model from scratch—whether it has five tables or hundreds with complex relationships—tailored to the business domain. Those client-side-rendered portals serve the SPA directly via Web APIs, without needing to build model-driven or canvas apps.  

This is a fundamental departure. The platform uses the same shared business data stored in Dataverse that other Power Platform components can leverage, but your portal is no longer tethered to any pre-existing Dynamics module. You own your entity model entirely. The result: headless CMS flexibility backed by the security and reliability of Dataverse, without the overhead of a CRM schema you didn’t ask for.  

Goodbye, custom web hosting and plumbing. Power Pages is a fully managed SaaS platform—Microsoft handles provisioning, hosting, CDN, scaling, and availability. Authentication is built in, with full support for enterprise identity providers, including Microsoft Entra ID and Microsoft Entra External ID, plus table permissions and web role enforcement on every API call. Organisations can also allow anonymous access or configure private sites as needed.  

Even advanced backend needs are now covered natively. Server Logic in Power Pages reached General Availability on April 1, 2026, delivering native server-side JavaScript execution with the maturity, governance, and extensibility required for enterprise production workloads. Alongside GA, Microsoft announced two enhancements that reinforce enterprise readiness:  

• Governance control to disable external calls — administrators can restrict outbound connectivity from the Server Logic layer to comply with internal policies and regulatory requirements.  

• Support for unbound Dataverse custom actions — enabling deeper integration with existing business logic layers.  

The result? Teams focus only on business logic, integrations, and user experience. As Hope Bradford, Senior Director of IT at Kelly Staffing, stated: “Power Pages lets us build personalised client experiences without managing complex infrastructure while maintaining enterprise trust and security.“ Kelly Staffing’s Helix UX portal, built on Power Pages, Dataverse, and Power Automate, now handles over 38,000 client interactions per day.  

Security and governance are first-class citizens on the platform. The 2025–2026 release wave introduced enterprise-grade controls for Power Pages, including role-based access and authentication through Entra, Data Loss Prevention (DLP) rules for external data access, IP-based restrictions, maintenance mode options, and built-in diagnostics and monitoring dashboards. Across the broader Power Platform, Microsoft is investing in enterprise observability—the April 2026 update introduced alerting and data metrics in Power Platform Monitor (covering metrics such as app open success rate, time to interactive, data request success rate, and data request latency), enabling IT teams to define health thresholds, receive proactive notifications, and take guided action.  

This level of governance—audit, monitoring, diagnostics—used to require significant custom engineering. Now it is out of the box. 

One of the biggest licensing shifts: Power Pages became its own product, fully decoupled from Power Apps licensing. Both internal and external users now fall under the same licensing model, making Power Pages viable for internal use cases like HR services and request management—not just external portals.  

The model is usage-based (Monthly Active Users), purchased as capacity packs per site:  

• Authenticated Users (Pre-paid): $200 per site/month for 100 users  

• Anonymous Users (Pre-paid): $75 per site/month for 500 users  

• Authenticated Users (Pay-As-You-Go): $4.00 per user/site,/month, on-demand  

• Anonymous Users (Pay-As-You-Go): $0.30 per user/site/month, on-demand  

Each authenticated-user subscription plan includes 2 GB database capacity and 16 GB file capacity. For applications serving tens of thousands of users, this capacity-based model is strategically superior to per-user or per-app seat licenses. Pay-as-you-go costs roughly twice as much as pre-paid capacity packs but suits seasonal or unpredictable usage patterns (e.g., tax season, annual HR enrollment).  

Trade-off to consider: Pre-paid packs require upfront commitment and don’t roll over month to month, so organisations with highly variable traffic must carefully model usage to avoid over-provisioning.  

Pricing disclaimer: The figures above are illustrative examples sourced from publicly available Microsoft documentation. Actual costs may vary by customer type (enterprise vs corporate), volume commitments, negotiated agreements, and account structure. Microsoft account teams and contracts determine final pricing. 

Power Pages now integrates directly with AI-assisted development workflows. Microsoft announced the public preview of the Power Pages plugin for GitHub Copilot CLI and Claude Code on February 24, 2026, providing an AI-assisted workflow for creating, deploying, and managing modern SPA sites on Power Pages. Developers can scaffold pages, configure data access, and wire up logic using natural-language commands, dramatically reducing the time it takes to modernise large enterprise applications. 

Developers deploy SPAs with Power Platform CLI commands, streamlining the entire development loop for professional developers. This means even large, complex in-house enterprise applications—hundreds of tables, complex relationships, tens of thousands of users—can be remodelled on Power Pages far more efficiently than legacy approaches. You migrate your custom model to Dataverse, build your SPA, connect integrations, and the platform handles the rest.  

If you still manage custom Azure websites, maintain SQL servers, or stitch together bespoke PaaS stacks for internal business tools, you are carrying unnecessary operational weight. Power Pages is no longer just a D365 portal. It is a fully managed, enterprise-grade SaaS platform (GA since February 2026), with server-side logic (GA since April 2026), your own data architecture without D365 schema dependencies, built-in security and governance, and a licensing model that scales to enterprise volumes.  

The industry is underestimating this shift. The shackles are off. Deploy, don’t build. https://digitalberg.com uses Azure infrastructure.