agentleFS
korchard333korchard333/claude-power-platform-community/.claude/skills/power-pages/SKILL.md

power-pages

Skill46 starsChanged 8 months agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use {% substitution %} blocks for content that should NOT be cached

    line 111
  2. Distinctive:

    Use Portal Web API for client-side data loading (reduces server rendering)

    line 113
  3. Distinctive:

    No table permissions defined (users see nothing — silent failure)

    line 150
  4. Very specific:

    Not enabling CSRF token validation on Web API calls (__RequestVerificationToken)

    line 155
  5. Distinctive:

    Not testing as anonymous user (unauthenticated page exposure)

    line 158
  6. Distinctive:

    Not associating web roles with table permissions (permissions without roles are ineffective)

    line 163

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Power Pages (External Portals)

When to Use

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.


When to Use Power Pages vs Alternatives

ScenarioBest ChoiceWhy
External customer self-service portalPower PagesBuilt-in Dataverse integration, external auth
Internal business appModel-Driven or Canvas AppSimpler, no portal overhead
Public marketing websiteAzure Static Web Apps / WordPressPower Pages is overkill
External API for partnersCustom Connector + APIMNo UI needed
Complex custom frontend for externalsCode App + Microsoft Entra ID B2CFull React control
Simple form intake from externalsPower Pages or Microsoft FormsDepends on data destination

Architecture Overview

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

⚠️ REQUIRED: Load Sub-Files Before Implementation

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:

  • Web Roles & Table Permissions — Web roles, table permission scopes (Global/Contact/Account/Parent/Self), page permissions, Append/AppendTo rules
  • Liquid Templating — Variables, conditionals, loops, FetchXML in Liquid, Web API in Liquid, content snippets
  • Entity Lists, Forms & Web Forms — Entity lists (data grids), entity forms (single-record CRUD), form metadata overrides, web forms (multi-step wizards)
  • Authentication — Identity providers, Microsoft Entra ID B2C setup, Contact = User model, auth in Code Sites
  • Custom JavaScript & Portal Web API — Entity form scripts, client-side AJAX via Portal Web API, enabling Web API via site settings, Client APIs (Wave 1 2026) for Form/List/User/Web API
  • Code Sites (SPA) — Framework reference, PAC CLI workflow, Web API client pattern (anti-forgery token), service patterns, lookup rules, table permissions for Code Sites
  • Agent API — Agent API for Power Pages (March 2026), custom chat experiences backed by Copilot Studio agents, API endpoints, authentication, custom UI

Site Settings (Key Configuration)

SettingValuePurpose
Authentication/Registration/EnabledtrueAllow new user registration
Authentication/Registration/RequiresConfirmationtrueEmail verification required
Authentication/Registration/RequiresInvitationtrueInvitation-only portal
Webapi/[table]/enabledtrueEnable Web API for table
Webapi/[table]/fieldsfield1,field2Allowed fields via Web API
Search/EnabledtrueEnable global search
HTTP/X-Frame-OptionsSAMEORIGINPrevent clickjacking

CLI Site Management (Wave 1 2026)

Preview (Wave 1 2026): Create and delete Power Pages sites from the command line.

CommandDescription
pac pages create-siteCreate a new site (CI/CD automation, environment provisioning)
pac pages delete-siteDelete a site (cleanup of test/temporary sites)

ALM for Power Pages

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

Performance

  • Enable CDN (Content Delivery Network) in portal admin for static assets
  • Enable server-side caching for entity lists and web templates
  • Use {% substitution %} blocks for content that should NOT be cached
  • Minimize FetchXML queries in Liquid — each one is a Dataverse round-trip
  • Use Portal Web API for client-side data loading (reduces server rendering)
  • Set appropriate page sizes on entity lists (don't load 100+ records)

Server Logic (Wave 1 2026)

GA (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:

  • TypeScript/JavaScript — familiar languages
  • pac pages CLI authoring via VS Code
  • Web role-scoped API access — endpoints respect web roles
  • Dataverse access — read/write with elevated or user-scoped permissions
ScenarioBest ChoiceWhy
Simple field validationEntity form metadataNo code needed
Complex business rules on submitServer logicSecure, server-side, no Azure dependency
External API integrationServer logic or Azure FunctionsServer logic if simple; Functions for complex orchestration
Client-side interactivityClient APIs / JavaScriptRuns in browser

Impact: Reduces the need for Azure Functions as a backend-for-frontend layer for portal-scoped business logic.


Web Application Firewall (WAF) — Preview

  • DDoS protection and bot mitigation
  • OWASP rule sets for common attack patterns
  • Configurable via Power Platform Admin Center
  • Available as a preview feature — evaluate for production readiness

Anti-Patterns

  • No table permissions defined (users see nothing — silent failure)
  • Global scope table permissions on sensitive data (everyone sees everything)
  • Using Dataverse security roles for portal access (they don't apply — use web roles + table permissions)
  • Direct DOM manipulation with jQuery when entity form metadata would suffice
  • Hardcoded record GUIDs in Liquid templates
  • Not enabling CSRF token validation on Web API calls (__RequestVerificationToken)
  • Missing HTTP/X-Frame-Options site setting (clickjacking vulnerability)
  • Authentication without email verification (spam accounts)
  • Not testing as anonymous user (unauthenticated page exposure)
  • Complex business logic in client-side JavaScript (should be in plugins or flows)
  • FetchXML queries in Liquid without top limit (unbounded queries)
  • Embedding secrets in web templates (visible in page source)
  • Using polymorphic lookups in parent-child table permissions (not supported)
  • Not associating web roles with table permissions (permissions without roles are ineffective)

Power Pages Plugin for GitHub Copilot / Claude Code

A Power Pages plugin is available (preview) that provides 9 skills for building Power Pages Code Sites from AI-assisted CLI tools:

#SkillCommandDescription
1Create site/create-siteScaffolds a site (React/Vue/Angular/Astro), applies design, builds pages
2Deploy site/deploy-siteBuilds and uploads via PAC CLI
3Activate site/activate-siteProvisions website record and assigns public URL
4Set up data model/setup-datamodelCreates Dataverse tables, columns, relationships
5Add sample data/add-sample-dataPopulates tables with realistic test records
6Integrate Web API/integrate-webapiGenerates typed API client, services, table permissions
7Set up authentication/setup-authAdds sign-in/sign-out and role-based access
8Create web roles/create-webrolesGenerates web role YAML files
9Add SEO/add-seoGenerates 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


Related Skills

  • security — Web roles and table permissions for portal access
  • dataverse-web-api — Portal Web API calls to Dataverse
  • copilot-studio — Copilot Studio agents that back Power Pages chat experiences

Eval Files

The 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.