Route Environments

microsoft/route-environments

Manage environment resolution — check which environment you create flows in by default, list available environments, and set your working environment. Use when the user asks about environments, their default environment, where to create flows, or switching environments.

823 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

601

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/microsoft/power-platform-skills --skill route-environments

What it tells the agent to use

found in the instruction text

Bash runs shell commands — read the instruction before connecting

The instruction itself

6 sections, as written by the author

Environment Resolution

You are helping the user understand and manage which Power Automate environment

they work in — where their flows are created, where they should build new ones,

and how to switch between environments.

> Uses the FlowAgent MCP tools (resolve_environment, list_environments,

> set_current_env, get_current_env).

Step 1: Understand what the user needs

"Which environment am I in?" → call get_current_env or resolve_environment
"Where should I create flows?" → help them pick the right environment
"What environments do I have?" → call list_environments
"Switch my environment" → call set_current_env

Step 2: List and explain environments

Call list_environments and present a clear summary:

|-------------|------|----------|-------|

| ... | Default / Developer / Sandbox / Production | ... | ... |

Help the user identify:

Default environment — shared, not recommended for production flows
Developer environments — personal, ideal for building and testing
Production/Sandbox — team environments for deployed flows

Step 3: Set the working environment

If the user wants to create flows in a specific environment, call

set_current_env with that environment ID. This pins all subsequent

FlowAgent operations to that environment (no need to pass --env each time).

Recommendation for new users: If they have a Developer environment, suggest

using that. If not, suggest they ask their admin to provision one, or use the

default environment for simple personal automations.

Guidance

resolve_environment shows how the environment resolves (routing → poll → fallback)
set_current_env changes the session default — it does NOT change tenant-level routing
Tenant-level environment routing (which env new makers land in by default) is

configured at the admin level in admin.powerplatform.microsoft.com — direct

admins there if they ask about changing org-wide routing

For maker-facing questions: "When you open make.powerautomate.com, your default

environment determines where new flows are created"

Decision Tree

User asks about environments?
├── "Which environment am I in?" → get_current_env / resolve_environment
├── "What environments exist?" → list_environments with summary table
├── "Where should I build?" → Recommend Developer env; set_current_env
├── "Switch to X environment" → set_current_env
├── "How do I create a new environment?" → Direct to PPAC admin center
└── "What is environment routing?" → Explain: determines default for new makers

How to use it

Copy the folder

Take microsoft/route-environments from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.