route-environments — Claude Code skill: Power Platform routing check
route-environments is a Claude Code skill that checks Power Platform environment routing and shows where new makers land when they open the platform.
MIT ★ 1,167 updated 2026-10-29
/plugin marketplace add microsoft/power-platform-skills
/plugin install power-automate@power-platform-skillsWhat route-environments does
The skill reveals where new makers are directed when opening Power Platform — default environment or a designated dev environment. It uses FlowAgent MCP tools: resolve_environment checks current routing state, list_environments outputs available environments with types and Dataverse connection status, set_current_env switches the working context.
Routing is configured by tenant admins at admin.powerplatform.microsoft.com; the skill only inspects state. When routing is active, new users skip the default environment and go straight to a sandbox or developer environment. The feature became generally available in December 2025 and is commonly used to isolate new projects and Copilot Studio.
To install via marketplace, run /plugin marketplace add microsoft/power-platform-skills, then /plugin install power-automate@power-platform-skills. Alternative method: npx skills add microsoft/power-platform-skills --skill route-environments -a claude-code.
What it helps with
- check if environment routing is enabled in the tenant
- find out where new makers will land
- see available environments and their types
- verify Dataverse connection for an environment
- switch current environment for flow operations
Example prompts for the agent
- Check which environment is active for new makers right now
- Show all Power Platform environments with their types
- Where will a user land if they open make.powerautomate.com now?
How to install route-environments
1Plugin marketplace
/plugin marketplace add microsoft/power-platform-skills/plugin install power-automate@power-platform-skillsThis installs the whole power-automate plugin with all its skills
2Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill route-environments -a claude-code3Manually: put the files in place
~/.claude/skills/route-environments/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/route-environments/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill route-environments -a codex2Manually: put the files in place
.agents/skills/route-environments/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill route-environments -a cursor2Manually: put the files in place
.cursor/skills/route-environments/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install microsoft/power-platform-skills plugins/power-automate/skills/route-environments2Manually: put the files in place
.github/skills/route-environments/SKILL.md1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill route-environments -a gemini-cli2Platform CLI
gemini skills install https://github.com/microsoft/power-platform-skills --path plugins/power-automate/skills/route-environmentsManually: put the files in place
.devin/skills/route-environments/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about route-environments
How to install route-environments in Claude Code?
Run /plugin marketplace add microsoft/power-platform-skills, then /plugin install power-automate@power-platform-skills. Alternatively, use npx skills add microsoft/power-platform-skills --skill route-environments -a claude-code.
What does route-environments do?
Checks where new Power Platform makers are redirected — to the default environment or a dedicated developer environment. Shows environment list, types, and Dataverse connection status.
Can route-environments enable routing?
No, the skill only inspects state. Routing is configured by admins in the Power Platform admin center at admin.powerplatform.microsoft.com under Environments → Environment routing.
Source text
SKILL.md · MIT
--- name: route-environments description: 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. user-invocable: true argument-hint: "[check|explain]" allowed-tools: Bash, Read, Write, Glob, Grep, AskUserQuestion, mcp__flowagent__list_environments, mcp__flowagent__set_current_env, mcp__flowagent__get_current_env, mcp__flowagent__resolve_environment, mcp__flowagent__whoami, mcp__flowagent__doctor, mcp__flowagent__reconnect, mcp__flowagent__list_accounts, mcp__flowagent__switch_account model: opus --- # 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
© Microsoft · MIT · microsoft/power-platform-skills