mcpField
R
route-environments

route-environments

github.com/microsoftCloud & DevOps1.1k137 installsUpdated today
Repository

About route-environments

A skill for checking and explaining Power Platform environment routing. It uses FlowAgent MCP tools to resolve the default environment and list environments; routing changes must be made in the Power Platform admin center.

Key features

  1. 01Resolve the default environment
  2. 02List and filter environments
  3. 03Explain environment routing behavior
  4. 04Direct configuration to the admin center

Use cases

  1. 01Check where a new maker will land
  2. 02Find developer or sandbox environments
  3. 03Identify an environment linked to Dataverse

MCP support

Uses FlowAgent MCP tools resolve_environment, list_environments, and set_current_env. The documented workflow checks routing and lists environments; routing itself cannot be modified through this skill.

Install

Copy the command and run it in a terminal.

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

After installing, type/route-environmentsin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported