- 01
/plugin marketplace add microsoft/power-platform-skills - 02
/plugin install power-automate@power-platform-skills
Explains Power Platform environment routing, the setting that decides which environment new makers land in, and checks how yours resolves. It can list your environments and show which one you'd land in, but routing itself is changed by an admin in the Power Platform admin center.
WHEN TO USE
USE FOR
- Find out whether environment routing is on in your tenant.
- See which environment you land in by default.
- Pick out developer, sandbox and Dataverse-linked environments.
NOT FOR
- Changing routing: an admin does that in the Power Platform admin center.
- Listing flows or managing connections: the other Power Automate skills do that.
This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.
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 asmcp__flowagent__<tool>; in Copilot CLI asflowagent-<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
specificGroupsrather 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_environmenttool 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 detailsReferences
- CLI Command Reference — Environment commands
Account or credentials required
2 FOR YOUAll items below are required.
- 01Install with the power-automate plugin, for its FlowAgent server
Install it with Microsoft's power-automate plugin. It works through the plugin's FlowAgent MCP server and points to the plugin's command reference, both outside this folder. The plugin sends usage data to Microsoft by default; /power-automate:telemetry off stops sending it.
- 02Node.js 18+ and the Azure CLI signed in
Node.js 18 or newer and the Azure CLI signed in (az login). The first time, run the plugin's setup skill.
This skill ships inside the Power Platform Skills plugin. Listed package contents include 25 agents, hooks and an MCP server. Installed components and skill versions may vary by AI tool.
Install as a Claude Code plugin
Typed inside the agent's own prompt, not in a terminal. This skill uses files kept elsewhere in its plugin, so install the whole plugin — on its own the skill would be missing them.
The repository is licensed under MIT — use, modification, and redistribution are allowed under that license’s terms.
View the repository’s license file on GitHub →