There is a quiet but important shift happening in Power Pages.
For a long time, Power Pages has been great at exposing data, building self-service experiences, and giving organizations a secure way to connect external users to business data. But let’s be honest, the user experience has often depended on people knowing exactly where to go, what to click, and how to filter through information.
That is starting to change.
Microsoft has introduced two new capabilities in Power Pages that point in a very interesting direction. Natural language filtering for data lists entered public preview on May 31, 2025, and Copilot answers from website data entered public preview on June 19, 2025.
This is not just another small usability update.
I think it is a sign that Power Pages is becoming much more intuitive for end users.
Natural language filtering makes lists feel less rigid
Anyone who has worked with list-heavy Power Pages implementations knows the challenge. Lists are powerful, but they can also feel quite functional. They work, but they are not always the easiest thing for end users to interact with.
Microsoft’s new natural language filtering changes that. Users can now type queries like “show tasks due next week” or “tasks created by John in May”, and Power Pages interprets the request and applies the right filters. Microsoft also notes that this is enabled by default for new lists.
That is a pretty meaningful improvement.
Instead of training users on how to use multiple filter controls or expecting them to understand the structure of the list, the site can now meet them in a much more natural way.
For portals with a lot of records, requests, tasks, cases, or applications, this has the potential to make self-service experiences feel a lot smoother.
Copilot answers bring a new kind of self-service
The second update is even more interesting.
Microsoft has added the ability for website users to ask questions in natural language and get answers from website data through a configured Copilot chatbot. The response is based on a structured data search of tables and still respects the roles and permissions configured for the site. Microsoft’s example is a customer service website user asking for the status of an open case and getting both the current status and a link to the case.
That is where things start to get exciting.
This is not just about finding information faster. It changes the overall way users interact with a Power Pages site. Instead of navigating through pages and menus to reach an answer, users can simply ask.
That is a much more modern self-service model.
And for customer portals, member portals, service request portals, or partner experiences, that can make a real difference.
Why this matters
Taken separately, each of these features is useful.
But together, they point to something bigger.
Power Pages is moving toward a more natural user experience. One where people do not always have to understand the structure of the site before they can get value from it.
That matters because good self-service is not just about exposing functionality. It is about reducing effort.
If users can filter lists without fighting the UI, and get answers without hunting through the site, the portal starts to feel less like a front-end on top of business data and more like a proper digital experience. That is the direction Microsoft is clearly moving toward with these two features.
My take?
I like this direction a lot.
Power Pages has always had strong fundamentals when it comes to security, data, and integration into the Microsoft ecosystem. What it has sometimes needed is a more intuitive end-user experience, especially for external users who do not live in the system every day.
Natural language filtering helps with that.
Copilot answers help with that.
These are the kinds of features that can quietly make a portal much better without forcing a complete redesign.
And I think this is only the beginning.
Happy integrating!