Last year, I wrote about how Power Pages was getting smarter with Copilot answers from website data and natural language filtering for lists. At the time, I saw those updates as a sign that Microsoft was starting to make Power Pages more intuitive for end users.
A few months later, that direction feels even clearer.
Because now we are not just talking about a smarter user experience. We are talking about a more modern platform direction.
Microsoft’s single-page application support for Power Pages reached general availability on January 31, 2026, after first entering public preview on May 31, 2025.
And I think this is one of the more significant Power Pages updates in a while.
This is a different kind of shift
When people think about Power Pages, many still think in terms of classic portals. Pages, forms, lists, authentication, and content wrapped around Dataverse.
That is still true, of course.
But Microsoft is clearly opening the door to something broader. With SPA support, Power Pages can now support the creation and deployment of single-page applications built with modern front-end frameworks like React. Microsoft says this includes a code-first development approach, direct deployment into a Power Pages site, integration with Dataverse data, and support for secure back-end interactions through Power Pages Web APIs.
That is a pretty big evolution.
This is no longer just about building a portal in the traditional sense. It is about using Power Pages as the secure, hosted, Microsoft-connected foundation for more modern external web experiences.
Why this matters
I think the biggest story here is flexibility.
Some use cases fit very well into classic Power Pages patterns. Others need richer interactivity, more tailored front-end behavior, or more control over the user journey. Microsoft specifically calls out scenarios requiring highly interactive UI, real-time updates, or tailored user journeys as a fit for SPA support.
That matters because it changes the Power Pages conversation.
Instead of asking whether Power Pages can only handle traditional portal use cases, it becomes easier to ask whether Power Pages can sit underneath a much more custom front-end while still giving you the benefits of the platform.
And that is a much more interesting position for Power Pages to be in.
The bigger picture
What makes this even more interesting is that this is happening after the usability improvements we saw last year.
First, Microsoft made the platform smarter for end users:
- natural language filtering for lists
- Copilot answers from website data
Now, Microsoft is making the platform more flexible for developers:
- modern single-page application support
- React-friendly front-end approach
- code-first development and deployment into Power Pages
- integration with Dataverse and Web APIs
That is not a random collection of features.
To me, it looks like Power Pages is steadily moving away from the old perception of being “just a portal tool” and toward being a more serious external experience platform.
My take?
Power Pages does not need to become everything to everyone. Its strength is still in the combination of security, identity, Dataverse, business data, and the broader Microsoft stack. But it does need to feel more modern.
Last year’s updates helped improve how users interact with a site. This update improves how developers can shape that site in the first place. Together, those changes tell a much stronger story about where Power Pages is heading.
If you are still thinking about Power Pages only as a classic portal platform, it may be time to update that view.