This skill should be used when the user asks to "activate site", "provision website", "activate a Power Pages website", "activate portal", "provision portal", "turn on my site", "enable website", or wants to activate/provision a Power Pages website in their Power Platform environment via the Power Platform REST API.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
This skill should be used when the user asks to "activate site", "provision website", "activate a Power Pages website", "activate portal", "provision portal", "turn on my site", "enable website", or wants to activate/provision a Power Pages website in their Power Platform environment via the Power Platform REST API.
{"Stop":[{"hooks":[{"type":"command","command":"node \"${CLAUDE_PLUGIN_ROOT}/skills/activate-site/scripts/validate-activation.js\"","timeout":30},{"type":"prompt","prompt":"If a Power Pages website was being activated in this session (via /power-pages:activate-site), verify before allowing stop: 1) Prerequisites were verified (PAC CLI auth + Azure CLI login), 2) Site name was read from config or user input, 3) The subdomain generator script was run AND the user was asked (via AskUserQuestion) whether to use the generated subdomain or enter a custom one, 4) The user confirmed activation parameters, 5) The POST to the websites API was made, 6) Provisioning status was polled to completion, 7) A summary with the site URL was presented. If incomplete, return { \"ok\": false, \"reason\": \"<specific issues>\" }. Otherwise return { \"ok\": true }.\n","timeout":30}]}]}
Activate Power Pages Site
Provision a new Power Pages website in a Power Platform environment via the Power Platform REST API.
Prerequisite: This skill expects an existing Power Pages code site created via /power-pages:create-site. Run that skill first if the site does not exist yet.
Core Principles
Cloud-aware URL resolution — Never hardcode API base URLs or site URL domains. Always derive them from the Cloud value returned by pac auth who.
Token handling — Scripts acquire and refresh Azure CLI tokens internally. The agent only needs to verify the user is logged in to Azure CLI.
Confirm before mutating — Always present the full activation parameters to the user and get explicit approval before POSTing to the websites API.
After installation, verify by running pac help again.
1.2 Check Authentication
Run pac auth who to check current authentication status.
pac auth who
If authenticated: Extract these values from the output:
Environment ID — the GUID after Environment ID:
Organization ID — the GUID after Organization ID: (this is the Dataverse org ID)
Cloud — the value after Cloud: (e.g., Public, UsGov, UsGovHigh, UsGovDod, China)
If not authenticated: Follow the same authentication flow as deploy-site — ask the user for their environment URL and run pac auth create --environment "<URL>".
1.3 Verify Azure CLI Login
Verify the user is logged in to Azure CLI (the activation scripts acquire tokens internally):
az account show
If az is not installed or not logged in: Instruct the user to install Azure CLI and run az login.
1.4 Check If Already Activated
Before gathering parameters, check whether the site is already activated by running the shared activation status script:
Where <PROJECT_ROOT> is the directory containing powerpages.config.json (use Glob with **/powerpages.config.json to locate it if not already known).
The script reads siteName from powerpages.config.json, looks up the websiteRecordId via pac pages list, queries the Power Platform GET websites API, and matches the response against both the websiteRecordId (exact GUID match) and name (case-insensitive). It outputs a JSON result to stdout.
Evaluate the result:
If activated is true: The site is already provisioned. Inform the user: "Your site is already activated at . No further provisioning is needed." Suggest next steps (Phase 5.3) and stop — do NOT proceed to Phase 2.
If activated is false: Proceed to Phase 2.
If error is present: The check could not complete. Proceed to Phase 2 (do not block the activation flow due to a failed check).
Output
PAC CLI installed and authenticated
Environment ID, Organization ID, and Cloud value extracted
Azure CLI login confirmed
Activation status checked (already activated → stop early, not activated → continue)
Phase 2: Gather Parameters
Goal: Determine the site name, generate or accept a subdomain, and look up the website record ID needed for the activation API call.
Actions
2.1 Read Site Name
Look for powerpages.config.json in the current directory or one level of subdirectories using Glob:
**/powerpages.config.json
Read the file and extract the siteName field. If not found, ask the user for the site name using AskUserQuestion.
2.2 Generate Subdomain Suggestion
CRITICAL — This step is MANDATORY. You MUST ask the user about the subdomain before proceeding. Do NOT skip this step or auto-select a subdomain without user input.
Run the subdomain generator script to create a random suggestion:
This outputs a string like site-a3f2b1. Resolve the correct site URL domain from the Cloud value obtained in Phase 1.2:
Cloud
Site URL Domain
Public
powerappsportals.com
UsGov
powerappsportals.us
UsGovHigh
high.powerappsportals.us
UsGovDod
appsplatform.us
China
powerappsportals.cn
Present the generated subdomain to the user and ask them to accept or enter their own using AskUserQuestion:
Question
Header
Options
Your site subdomain will be: <suggestion> (full URL: https://<suggestion>.<siteUrlDomain>). Would you like to use this subdomain or enter your own?
Subdomain
Use <suggestion> (Recommended), Enter a custom subdomain
If custom: The user provides their own subdomain via "Other" free text input. Validate it is lowercase, alphanumeric with hyphens only, and 3-50 characters.
2.3 Get Website Record ID
Run pac pages list to get the website record ID:
pac pages list
Parse the output to find the website record that matches the site name. Extract the Website Record ID (GUID). If pac pages list returns no results or the command is not available, set websiteRecordId to $null — the API will create a new website record.
Output
Site name determined (from config file or user input)
Subdomain chosen (generated or custom)
Website record ID resolved (GUID or null)
Phase 3: Confirm
Goal: Present all activation parameters to the user and get explicit approval before making the API call.
Actions
Present all activation parameters to the user using AskUserQuestion:
Question
Header
Options
Ready to activate your Power Pages site with these settings:\n\n- Site name: <siteName>\n- Subdomain: <subdomain>.powerappsportals.com\n- Environment ID: <environmentId>\n\nProceed with activation?
Activate
Yes, activate the site (Recommended), No, cancel
If "No": Stop the skill and inform the user they can re-run it later.
If "Yes": Proceed to Phase 4.
Output
User has explicitly approved the activation parameters
Phase 4: Activate & Poll
Goal: POST to the Power Platform websites API to start provisioning, poll until completion, and report the result.
Actions
4.1 Run Activation Script
Run the shared activation script, passing all parameters gathered in Phases 1–2:
The script acquires an Azure CLI token, POSTs to the websites API, extracts the Operation-Location header, and polls every 10 seconds for up to 5 minutes (refreshing the token periodically). It outputs a JSON result to stdout.
Note: This script may run for up to 5 minutes while polling. Use a Bash timeout of at least 360 seconds (6 minutes).
4.2 Handle Results
Evaluate the JSON output:
status value
statusCode / errorCode
Action
Succeeded
—
Provisioning complete. The result includes siteUrl. Proceed to Phase 5.
Subdomain already taken. Loop back to Phase 2 action 2.2 for a new subdomain, then re-run the script.
Failed
401
Token expired. Ask the user to run az login and retry.
Failed
403
Insufficient permissions. Inform user they need the "Power Pages site creator" or "System Administrator" role.
Failed
409
Website already exists. Inform user and suggest using /power-pages:deploy-site instead.
Failed
429 or 5xx
Throttling or server error. Wait 5 seconds and re-run the script once.
Failed
other
Present the error to the user and help troubleshoot.
Running
—
Provisioning still in progress after 5 minutes. Inform the user it may take up to 15 minutes and suggest checking the Power Platform admin center.
error field
—
Prerequisite failure (missing args, no token). Present the error and help troubleshoot.
Output
Provisioning status resolved (Succeeded with siteUrl, Failed with error details, or Running with timeout advisory)
Phase 5: Present Summary
Goal: Show the user the final site URL and suggest next steps.
Actions
5.1 Show Results
Present the activation summary using the siteUrl from the script output:
Power Pages site activated successfully!
Site Name: <siteName>
Site URL: <siteUrl>
Environment: <environmentName> (<environmentId>)
Status: Provisioned
The script already resolves the correct cloud-specific site URL domain, so use the siteUrl value directly.
