Power Pages needs a governed delivery path as AI moves into portal design

With agentic coding tools now generally available for Power Pages, a useful site can appear in an afternoon. The question I care about is what happens on the second day: can someone else understand the change, check its permissions and deploy it again?

Power Pages belongs in your normal ALM

A common mistake is treating a portal as a separate web project that happens to use Dataverse. It is not. Power Pages changes can be packaged in a Dataverse solution and moved through environments with Power Platform pipelines, the same way as your apps and flows.

That matters because a portal sits on the boundary between your organisation and the public. A small design change can affect permissions, privacy, performance and what customers think your process is.

Two approvals, not one

Portals have two kinds of change, and they need different reviewers:

• Content — wording, images, page order. A business or marketing owner approves this.
• Technical — table permissions, web roles, forms, server logic, authentication. A platform owner approves this.

Mixing them causes trouble both ways. Either content edits wait weeks for a technical review, or a permission change slips through because it looked like "just a page update".

How I would release a portal change

1. Agree the acceptance criteria first — the visitor experience, the records created or read, the roles that can see them, and the error message when something fails.
2. Build in development, with or without an AI-assisted tool.
3. Package the site and its Dataverse components in a solution and review it.
4. Validate in test as an anonymous visitor and as each signed-in role.
5. Deploy through the pipeline with an approval for production.
6. Record what was asked for, what was generated, who approved it and the deployment reference. Future support will thank you.

Things to check before planning around new features

The 2026 release wave includes stronger analytics and server logging, finer external authentication controls and security assistance. Some are planned, some rolling out, some available. Confirm the state in your environment and region before a release depends on one.

Agentic development in Power Pages is a test of our delivery habits. If a change cannot be explained, checked and reproduced, the team has gained speed without control.

A practical next step

Choose one journey with a clear business owner, such as a customer enquiry, and send one small change through steps 1 to 6. Note where the process felt slow and where it caught something. That tells you which part of the path to improve first.