Power Pages AI Plugin Adds Traditional Site Support: Copilot CLI, Claude Code and PAC CLI Timeline

Read it carefully, because the roadmap promises a specific set of things and nothing beyond them.

What the roadmap item says​

The roadmap entry lists these points:

• What it does: Developers type natural-language prompts into GitHub Copilot CLI or Claude Code. The agent can then create a new traditional Power Pages site, or download, inspect and update the metadata of an existing one.
• How changes get back: Updates are uploaded to the Power Platform environment through the Power Platform CLI (PAC CLI).
• Metadata it covers:
  • Web pages
  • Web templates
  • Content snippets
  • Basic forms and multistep forms
  • Lists
  • Table permissions
  • Web roles
  • Site settings
• Status: In development
• Platform: Developer
• Cloud: Worldwide (Standard Multi-Tenant) only
• Timeline: Preview in October 2026, general availability in November 2026. Both are month-level estimates with no specific day.

Microsoft's roadmap page says its dates are estimates and that all information is subject to change. As of this writing the item is still listed as in development. Treat "October" and "November" as forecasts, not promises.

Section summary: The plugin is moving from SPA-only to traditional sites too, covering eight named types of site metadata, with PAC CLI handling the upload. Preview is forecast for this month and GA for next month.

How the plugin got here​

The plugin has developed quickly this year:

• February 2026: Microsoft announced a public preview of the Power Pages plugin for GitHub Copilot CLI and Claude Code. The idea was that you simply describe the site you want in natural language. The plugin takes care of everything else, from project scaffolding and Dataverse setup to API integrations, permissions, and deployment.
• Platform focus: Microsoft said the plugin understands table permissions, web roles, site settings, setting up authentication and Web API patterns.
• April 2026: Microsoft added three new skills for the Power Pages agentic code plugin for GitHub Copilot and Claude Code CLI for server-side logic. A Power Platform blog post later announced the plugin as generally available.
• Recently: SPA template support arrived. The /create-site skill can now create your site from a ready-made single-page application (SPA) template, instead of generating every page and component from scratch.

Through all of that, the plugin served one kind of site. Microsoft Learn's current guide says it provides an AI-assisted workflow for creating, deploying, and managing modern single-page application (SPA) sites on Power Pages. MSDynamicsWorld's coverage of the preview made the same point, describing it as meant to reduce manual configuration when developing a new Power Pages single-page application (SPA) site.

Even the template gallery is SPA-only. Microsoft Learn notes it currently shows only SPA templates, not traditional Power Pages templates.

Why traditional sites matter here​

SPA sites and traditional sites are built very differently. Microsoft's SPA documentation explains that an SPA site runs entirely in the browser and, unlike traditional sites, is managed only through source code and CLI tools.

The same documentation lists traditional-site features that SPA sites don't support:

A large share of the Power Pages sites in use today were built the traditional way, with Liquid web templates, basic and multistep forms, and lists. Until now, teams running those sites have been left out of the agent-assisted workflow.

The metadata list in roadmap item 577900 matches that work closely:

• Web templates and content snippets are where traditional sites keep their layout and reusable text.
• Basic and multistep forms and lists are the built-in components SPA sites can't use.
• Table permissions and web roles control who can see and change Dataverse data.

The roadmap item doesn't spell out how each of these will be handled. It doesn't mention Liquid editing directly, and it doesn't say the agent can do everything the design studio can. The SPA limitations in the table above describe the SPA model; they are not a list of what the new feature will support.

Section summary: This expansion covers the traditional sites many organizations already run. The listed metadata types correspond to the parts of those sites that are tedious to edit by hand.

What the workflow will probably look like​

Microsoft hasn't published documentation for the traditional-site workflow yet, so the details are still unknown. Based on the roadmap description, the steps are:

1. Point your coding agent at a new or existing traditional site.
2. Download the existing site's metadata so the agent can work with it locally.
3. Ask for changes in plain English, such as updating a content snippet, adding a web role or adjusting a table permission.
4. Upload the changes to the environment through PAC CLI.

Microsoft's SPA documentation describes the commands pac pages download-code-site and pac pages upload-code-site. Those are documented for SPA sites only. The roadmap doesn't say which PAC CLI commands the traditional-site workflow will use, so don't assume it's the same pair.

The roadmap also doesn't cover:

• Required minimum versions
• Prompt syntax or new slash commands
• How conflicting edits are resolved
• Whether changes go to live sites or through staging

What you need for the plugin today​

These are the documented requirements for the existing SPA workflow. They are not confirmed requirements for the traditional-site feature, but they show what the plugin already expects:

• Software: Microsoft Learn lists Node.js 18.0 or later, Azure CLI, GitHub Copilot CLI or Claude Code, and PAC CLI 2.6.3 or later. The 2.6.3 minimum applies specifically to server logic.
• Accounts and environment: Microsoft's preview announcement said you also need a Power Platform environment with Power Pages and authenticated sessions for both PAC CLI and Azure CLI.
• Installation: In Claude Code, add the Microsoft marketplace: /plugin marketplace add microsoft/power-platform-skills. Install the Power Pages plugin: /plugin install power-pages@power-platform-skills. Then restart the agent so the plugin's skills appear as slash commands. For GitHub Copilot CLI, Microsoft points to the Copilot CLI extensions documentation for the equivalent steps.
• Updates: The quick-install script turns on auto-update. That's worth having on when new capabilities like this one arrive through the plugin.

Troubleshooting tip carried over from the SPA guide: The coding agent runs commands on your own machine. If you see "command not found" or "is not recognized," a required tool is missing. Install it and run the workflow again.

A warning about permissions​

The new feature can edit table permissions and web roles, and on a Power Pages site those settings decide which external users can read which Dataverse records. Microsoft's own guidance says code and configuration generated by the agent can be inaccurate. It tells developers to review, test and validate everything before approving or deploying it, and it identifies overly permissive table permissions as a common security risk.

That's especially important for traditional sites. Many of them are older production portals, built up over years and sometimes running on configuration nobody fully remembers. Before you let an agent change one:

• Test in a development environment first. Don't let the first experiment touch production.
• Keep the downloaded metadata in source control. Then every agent change shows up as a diff you can review and roll back.
• Ask the agent to explain its plan before approving any change to permissions or roles. Microsoft recommends this habit for the SPA workflow, and it applies here too.
• Use the security skills the plugin already has. It includes /audit-permissions and /security-review. Microsoft hasn't said whether they will work on traditional sites, so check before relying on them.

Who benefits, and the open questions​

Teams that run traditional portals, and the partners who maintain them, gain the most. Bulk changes to snippets, reviewing permissions across many tables, and updating site settings are tedious but structured tasks. That's the kind of work coding agents tend to handle well.

There are reasonable questions to ask, though:

• How well will the AI handle Liquid? Liquid is a templating language with platform-specific objects, and an agent that knows React well may not know Power Pages Liquid conventions. The roadmap promises web template editing but says nothing about how good the results will be.
• Is the timeline too short? The forecast puts preview this month and GA the next, which is very little preview time for a feature that changes security settings. If the GA date slips, that won't be surprising.
• What about other clouds? Only Worldwide (Standard Multi-Tenant) is listed. Government cloud customers shouldn't expect this feature yet.

Some community writers saw the SPA plugin as a sign of where Power Pages is heading. Nick Doelman's ReadyXRM blog titled its review "The end of Power Pages? (As we know it?)" Adding traditional-site support suggests Microsoft wants the agent-driven approach to cover existing sites as well as new SPA builds.

Bottom line​

Roadmap item 577900 says the Power Pages plugin for GitHub Copilot CLI and Claude Code will create and edit traditional sites. It covers web pages, templates, snippets, forms, lists, table permissions, web roles and site settings, with PAC CLI uploading the changes. Preview is forecast for October 2026 and GA for November 2026, in the worldwide commercial cloud only.

Until Microsoft publishes documentation for the traditional-site workflow, the commands and edge cases are unconfirmed. If you maintain a traditional portal, you can prepare now: set up a development environment, put your site metadata under source control, and plan to review every permission change the agent proposes.