$ ~/registry/skill/microsoft-plugins-power-pages-skills-setup-auth

SKILL

setup-auth

Name: setup-auth
Author: microsoft

Set up authentication, authorization, and identity providers for Power Pages sites.

Stars

★ 440

Source

GitHub

Updated

2026-07-11

// securityCaution

Prompt only, no code
Open source

Summary

The material indicates this is an open-source, prompt-only skill with no declared secrets or remote endpoints, so the overall risk is low. It primarily guides authentication and authorization setup for a Power Pages site; caution is limited to local project auth-related code/config changes, with no clear data exfiltration or major red flags shown.

CredentialsLow risk

The material explicitly states that no secrets or environment variables are required, and the README does not ask for tokens, API keys, or account credentials. Although the subject matter involves identity provider configuration, the disclosed content does not show the skill itself collecting, storing, or transmitting credentials.

Network egressLow risk

No remote endpoints are declared; based on the provided material, this appears to be a prompt-only skill for generating/guiding authentication configuration, with no described transmission of user data to third-party services. References to Entra ID, Google, and Facebook are identity provider options, not evidence that the skill itself performs outbound network calls.

Code executionCaution

The README includes a plugin-check command `node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js"`, and the workflow mentions validating that builds succeed, indicating the usage context may involve running local checks or build commands in the project environment. For a skill/tool, this is a normal local development capability that warrants attention, but the material does not show privilege escalation or requests for unusually broad system permissions.

Data accessCaution

The documentation instructs locating `powerpages.config.json`, checking `.powerpages-site`, detecting existing auth code, and creating/modifying auth services, authorization utilities, and UI, indicating access to and modification of local project files. This scope is generally consistent with the stated function, and there is no indication of data access beyond what is needed for authentication setup.

Supply chainLow risk

The source is an open-source Microsoft-related GitHub repository, making the code auditable and materially lowering supply-chain risk. Cautionary context remains: the repo shows 0 stars, no declared license, and unknown maintenance status, but the provided material does not show a closed-source package, deceptive provenance, or suspicious injection red flags.

Recommendations

Apply the skill’s generated authentication changes in a controlled branch or test site first, then perform manual code review.
Focus review on added or modified login/logout logic, role checks, route protection, and any local mock identity data files.
If you later connect Entra ID, Google, Facebook, or other providers, separately verify callback URLs, secret storage, and least-privilege configuration.
Confirm the repository’s license and maintenance status before production use, and pin a specific version/reference to reduce change risk.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "setup-auth" skill from askskill:
1. Download https://raw.githubusercontent.com/microsoft/power-platform-skills/main/plugins/power-pages/skills/setup-auth/SKILL.md
2. Save it as ~/.claude/skills/setup-auth/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Configure enterprise single sign-on

Prompt

Set up Microsoft Entra ID login for my Power Pages site, including sign-in, sign-out, protected page access control, and the configuration steps I need to change.

Expected

A configuration plan for Entra ID authentication and authorization, including sign-in, sign-out, and protected page settings.

Add local account login

Prompt

Help me enable local username-password login in Power Pages, with sign-up, sign-in, sign-out, and pages accessible only to authenticated users.

Expected

Instructions to enable local authentication, configure user access restrictions, and implement the setup.

Integrate a third-party identity provider

Prompt

Integrate Google sign-in for my Power Pages site and configure role-based access to different pages after login.

Expected

A third-party sign-in integration plan and recommendations for role-based page authorization.

// docs

Plugin check: Run node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js" — if it outputs a message, show it to the user before proceeding.

Set Up Authentication & Authorization

Configure authentication (login/logout) and role-based authorization for a Power Pages code site. This skill supports multiple identity providers -- Microsoft Entra ID, Entra External ID (for customer-facing apps with self-service sign-up), OpenID Connect (generic), SAML2, WS-Federation, local authentication (username/password), Microsoft Account, Facebook, and Google. It also supports optional features including invitation-based registration and Terms & Conditions acceptance. Power Pages built-in 2FA is intentionally not scaffolded because the SendCode/VerifyCode pages are server-rendered and cannot be integrated into a SPA experience — use IdP-level MFA instead. It creates an auth service, type declarations, authorization utilities, auth UI components, and role-based access control patterns appropriate to the site's framework and chosen identity provider(s).

Core Principles

Client-side auth is UX only — Power Pages authentication is server-side (session cookies). Client-side role checks control what users see, not what they can access. Server-side table permissions enforce actual security.
Framework-appropriate patterns — Every auth artifact (hooks, composables, services, directives, guards) must match the detected framework's idioms and conventions.
Development parity — Include mock data for local development so developers can test auth flows and role-based UI without deploying to Power Pages.

Initial request: $ARGUMENTS

Prerequisites:

An existing Power Pages code site created via /create-site

The site must be deployed at least once (.powerpages-site folder must exist)

Web roles must be created via /create-webroles

Workflow

Phase 1: Check Prerequisites — Verify site exists, detect framework, check web roles
Phase 2: Plan — Gather auth requirements and present plan for approval
Phase 3: Create Auth Service — Auth service with login/logout and type declarations
Phase 4: Create Authorization Utils — Role-checking functions and wrapper components
Phase 5: Create Auth UI — Login/logout button integrated into navigation
Phase 6: Implement Role-Based UI — Apply role-based patterns to site components
Phase 7: Verify Auth Setup — Validate all auth files exist, build succeeds, auth UI renders
Phase 8: Review & Deploy — Summary and deployment prompt

Phase 1: Check Prerequisites

Goal: Confirm the project exists, identify the framework, verify deployment status and web roles, and check for existing auth code.

Actions

1.1 Locate Project

Look for powerpages.config.json in the current directory or immediate subdirectories:

**/powerpages.config.json

If not found: Tell the user to create a site first with /create-site.

1.2 Detect Framework

Read package.json to determine the framework (React, Vue, Angular, or Astro). See ${CLAUDE_PLUGIN_ROOT}/references/framework-conventions.md for the full framework detection mapping.

1.3 Check Deployment Status

Look for the .powerpages-site folder:

**/.powerpages-site

If not found: Tell the user the site must be deployed first:

"The .powerpages-site folder was not found. The site needs to be deployed at least once before authentication can be configured."

Use AskUserQuestion:

Question	Options
Your site needs to be deployed first. Would you like to deploy now?	Yes, deploy now (Recommended), No, I'll do it later

If "Yes, deploy now": Invoke /deploy-site, then resume.

If "No": Stop — the site must be deployed first.

1.4 Check Web Roles

Look for web role YAML files in .powerpages-site/web-roles/:

**/.powerpages-site/web-roles/*.yml

…

View full docs ↗

Inspect and configure WAF protection for a Power Pages production site.

microsoftGet→

$ loading_