Route Environments (Microsoft)

---
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
metadata:
  origin: Microsoft
---

# 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