brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
route-environmentsCheck 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.
Independent GitHub snapshot · Automated classification · Original documentation governs
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>.
Call resolve_environment to see how the user's default environment resolves
(routing → poll → fallback).
Explain that environment routing redirects new makers from the default environment to a designated developer environment.
Key facts:
specificGroups rather than tenant-wideCall list_environments (use the query param to filter by name).
Show environment types and help the user identify:
Help the user understand which environment they'd land in by calling
resolve_environment.
admin.powerplatform.microsoft.com > Environments > Environment routingresolve_environment tool can check the current routing state but cannot modify itUser 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