route-environments
Check Power Platform environment routing status and understand default environment resolution. Use when the user asks about environment routing, developer environments, or new maker landing. Routing is configured in the admin center, not here. NOT for listing flows or managing connections.
git clone --depth 1 https://github.com/microsoft/power-platform-skills /tmp/route-environments && cp -r /tmp/route-environments/plugins/power-automate/skills/route-environments ~/.claude/skills/route-environmentsSKILL.md
# Environment Routing Manager You are helping the user work with Power Platform environment routing — the feature that controls which environment new makers land in (GA December 2025). > Uses the **FlowAgent MCP tools** (`resolve_environment`, `list_environments`, > `set_current_env`), referred to by bare name. In Claude Code they appear as > `mcp__flowagent__<tool>`; in Copilot CLI as `flowagent-<tool>`. ## Step 1: Check Current State Call `resolve_environment` to see how the user's default environment resolves (routing → poll → fallback). ## Step 2: Determine Operation ### Check Routing Status Explain that environment routing redirects new makers from the default environment to a designated developer environment. Key facts: - Generally available since December 2025 - Most tenants scope routing with `specificGroups` rather than tenant-wide - Common uses: steering new makers to developer environments, Copilot Studio isolation ### List Environments Call `list_environments` (use the `query` param to filter by name). Show environment types and help the user identify: - Their default environment - Any developer/sandbox environments - Environment with Dataverse linked ### Resolve Default Environment Help the user understand which environment they'd land in by calling `resolve_environment`. ## Guidance - Environment routing is configured at the **tenant admin** level in the Power Platform admin center - It cannot be configured here — direct the user to `admin.powerplatform.microsoft.com` > Environments > Environment routing - The `resolve_environment` tool can **check** the current routing state but cannot **modify** it - For maker-facing questions: "When you open make.powerautomate.com, environment routing determines which environment you see first" ## Decision Tree ``` User asks about environment routing? ├── "What is it?" → Explain: redirects new makers from default to dev env ├── "Is it enabled?" → resolve_environment to check ├── "How do I enable it?" → Direct to PPAC admin center ├── "Which environment am I in?" → list_environments + resolve_environment └── "What environments exist?" → list_environments with details ``` ## References - [CLI Command Reference](../../references/cli-reference.md) — Environment commands
Guide the user to add a data source, connection, or API connector to a Canvas App via Power Apps Studio, then verify and continue. USE WHEN the user asks to add a data source, add a connection, add an API, add a connector, connect to SharePoint / Dataverse / SQL / Excel / OneDrive / Teams / Office 365, or any similar request to make new data available to the app. DO NOT USE WHEN the user is asking to list or describe existing data sources — call list_data_sources or list_apis directly instead.
Creates or edits a Power Apps Canvas App through the Canvas Authoring MCP coauthoring session. Handles new app generation, direct targeted edits, complex multi-screen changes, responsive layout, per-screen self-QA, and compile-error convergence. Trigger on requests to create, build, generate, modify, update, change, fix, or edit a Canvas App or .pa.yaml files.
Configure the Canvas Authoring MCP server for the current coauthoring session. USE WHEN "configure MCP", "set up MCP server", "MCP not working", "connect Canvas Apps MCP", "canvas-authoring not available", "MCP not configured", "set up canvas apps".
[DEPRECATED — use canvas-app instead] Generate a complete Power Apps canvas app.
>
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
Use when adding a Power Platform connector to an Expo/React Native Power Apps mobile app and no dedicated mobile connector skill exists.
Use when adding an unspecified data source to an Expo/React Native Power Apps mobile app; routes to Dataverse, SharePoint, or another connector.