メニュー
Power Pages (External Portals). Use when: building portals, web roles, table permissions, Liquid templating, entity lists, entity forms, web forms, Microsoft Entra ID B2C authentication, portal JavaScript, site settings, content snippets.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Model-Driven Apps Development. Use when: building Model-Driven Apps, forms, views, business rules, site map, command bar customization, custom pages, embedded Canvas Apps, subgrids, role-based form switching, generative pages.
Power Apps Code Apps Development (React + TypeScript + Vite). Use when: building Code Apps, three-layer architecture, PAC CLI workflow, Zustand state management, TanStack Query, shadcn/ui components, router basename, provider stack, form patterns, Dataverse integration from React.
WCAG 2.2 AA compliance, accessibility patterns, UX design for Power Platform. Use when: building accessible components, reviewing WCAG compliance, designing loading/empty/error states, responsive design, form accessibility, keyboard navigation, screen reader support, color contrast, focus management.
Dataverse Web API reference. Use when: CRUD operations, OData queries, FetchXML, bulk operations, batch requests, metadata operations, Custom APIs, file/image columns, change tracking, solution management via API, schema creation, programmatic builds.
PCF (Power Apps Component Framework) control development. Use when: building PCF controls, ReactControl, dataset controls, manifest patterns, Fluent UI v9 integration, Canvas App deployment, debugging PCF.
Dataverse C# Plugin development. Use when: writing plugins, IPlugin interface, execution pipeline, entity images, shared variables, unit testing with FakeXrmEasy, plugin registration, ITracingService, sandbox limitations.
| name | power-pages |
| description | Power Pages (External Portals). Use when: building portals, web roles, table permissions, Liquid templating, entity lists, entity forms, web forms, Microsoft Entra ID B2C authentication, portal JavaScript, site settings, content snippets. |
Trigger when building external-facing websites on Dataverse — customer portals, partner portals, self-service portals, community forums, or any authenticated web experience exposing Dataverse data to external users.
| Scenario | Best Choice | Why |
|---|---|---|
| External customer self-service portal | Power Pages | Built-in Dataverse integration, external auth |
| Internal business app | Model-Driven or Canvas App | Simpler, no portal overhead |
| Public marketing website | Azure Static Web Apps / WordPress | Power Pages is overkill |
| External API for partners | Custom Connector + APIM | No UI needed |
| Complex custom frontend for externals | Code App + Microsoft Entra ID B2C | Full React control |
| Simple form intake from externals | Power Pages or Microsoft Forms | Depends on data destination |
External User (Browser)
│
├── Authentication (Microsoft Entra ID B2C, local, SAML, OAuth)
│
├── Power Pages Runtime
│ ├── Pages (HTML + Liquid templating)
│ ├── Entity Lists (data grids)
│ ├── Entity Forms (single-record CRUD)
│ ├── Web Forms (multi-step wizards)
│ ├── Web Templates (reusable Liquid components)
│ └── Content Snippets (editable text blocks)
│
├── Security Layer
│ ├── Web Roles (external user roles)
│ └── Table Permissions (row-level access control)
│
└── Dataverse (data store)
└── Contact = portal user record
SKILL.md is a summary only — it is NOT sufficient for implementation.
The detailed content (complete payloads, XML templates, working examples, edge-case handling) lives in sub-files in the same directory as this SKILL.md. Before writing any code, you MUST use read_file on the sub-files relevant to your task:
| Setting | Value | Purpose |
|---|---|---|
Authentication/Registration/Enabled | true | Allow new user registration |
Authentication/Registration/RequiresConfirmation | true | Email verification required |
Authentication/Registration/RequiresInvitation | true | Invitation-only portal |
Webapi/[table]/enabled | true | Enable Web API for table |
Webapi/[table]/fields | field1,field2 | Allowed fields via Web API |
Search/Enabled | true | Enable global search |
HTTP/X-Frame-Options | SAMEORIGIN | Prevent clickjacking |
Preview (Wave 1 2026): Create and delete Power Pages sites from the command line.
| Command | Description |
|---|---|
pac pages create-site | Create a new site (CI/CD automation, environment provisioning) |
pac pages delete-site | Delete a site (cleanup of test/temporary sites) |
Power Pages sites are solution-aware:
- Site + all metadata included in solution export
- Deploy via managed solution like any Power Platform component
- Site Settings, Web Roles, Table Permissions travel with the solution
Per-environment configuration:
- Authentication provider settings differ per environment
- Use site settings + environment variables for environment-specific values
- B2C tenant may differ between dev/test/prod
{% substitution %} blocks for content that should NOT be cachedGA (Wave 1 2026): Secure server-side custom logic in Power Pages using TypeScript/JavaScript.
Server logic enables custom server-side code execution within Power Pages — no Azure Functions required. Key capabilities:
pac pages CLI authoring via VS Code| Scenario | Best Choice | Why |
|---|---|---|
| Simple field validation | Entity form metadata | No code needed |
| Complex business rules on submit | Server logic | Secure, server-side, no Azure dependency |
| External API integration | Server logic or Azure Functions | Server logic if simple; Functions for complex orchestration |
| Client-side interactivity | Client APIs / JavaScript | Runs in browser |
Impact: Reduces the need for Azure Functions as a backend-for-frontend layer for portal-scoped business logic.
__RequestVerificationToken)HTTP/X-Frame-Options site setting (clickjacking vulnerability)top limit (unbounded queries)A Power Pages plugin is available (preview) that provides 9 skills for building Power Pages Code Sites from AI-assisted CLI tools:
| # | Skill | Command | Description |
|---|---|---|---|
| 1 | Create site | /create-site | Scaffolds a site (React/Vue/Angular/Astro), applies design, builds pages |
| 2 | Deploy site | /deploy-site | Builds and uploads via PAC CLI |
| 3 | Activate site | /activate-site | Provisions website record and assigns public URL |
| 4 | Set up data model | /setup-datamodel | Creates Dataverse tables, columns, relationships |
| 5 | Add sample data | /add-sample-data | Populates tables with realistic test records |
| 6 | Integrate Web API | /integrate-webapi | Generates typed API client, services, table permissions |
| 7 | Set up authentication | /setup-auth | Adds sign-in/sign-out and role-based access |
| 8 | Create web roles | /create-webroles | Generates web role YAML files |
| 9 | Add SEO | /add-seo | Generates robots.txt, sitemap.xml, meta tags |
Install from microsoft/power-platform-skills. Targets SPA (single-page application) Power Pages Code Sites.
More info: Create a code site using Claude Code
security — Web roles and table permissions for portal accessdataverse-web-api — Portal Web API calls to Dataversecopilot-studio — Copilot Studio agents that back Power Pages chat experiencesThe evals/ directory contains 11 evaluation test cases for Power Pages skill validation — covering site creation, authentication setup, web roles, data modeling, Web API integration, SEO, permissions auditing, deployment, and testing workflows.