AI-built Power Pages still need governance checks
Diesen Beitrag auf Deutsch lesen
A Claude Code Power Pages preview built and deployed a site, but missed table permissions, a WebAPI setting and non-Entra authentication steps.
TL;DR
Microsoft's Claude Code Power Pages plugin preview built and deployed a site, including Dataverse tables, relationships, authentication, and environment activation. The test used human approval, but consumed three daily allocations before a Pro to Max upgrade; it also missed table permissions, a WebAPI site setting, and non-Entra ID authentication setup.
Original by Nick Doelman, on ReadyXRM Blog. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Keep human approval in the build process because the preview can produce a working site while missing important configuration.
- Admins/CoE: Validate table permissions, WebAPI site settings and authentication before activating a generated site in an environment.
- Security/Compliance: Treat non-Entra ID authentication as a manual control and review permissions before deployment.
Frequently asked questions
What can the Power Pages plugin for Claude Code build without manual setup?
In the author test it produced a complete Power Pages site from a prompt: data model, Dataverse tables, relationships and authentication, followed by deployment and activation.
Which configuration gaps did the author find in the AI-built Power Pages site?
The plugin was not solution aware, missed critical table permissions (one table was forgotten) and missed a Web API site setting. Authentication other than Microsoft Entra ID needs manual configuration.
What should a reviewer verify before an AI-generated Power Pages site goes live?
Check whether the site is solution aware, whether table permissions are complete, whether the Web API site setting exists and whether any authentication other than Microsoft Entra ID was set up manually.