microsoft/route-environments
plugins/power-automate/skills/route-environments/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add microsoft/power-platform-skills route-environmentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Aug 18, 2026, 3:36 AM148.9s1 file scanned
SKILL.md
- 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
- model:
- opus
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 details
References
- CLI Command Reference — Environment commands
Related Skills
microsoft/app-builder
development
VerifiedTrustedCommunity
(Preview) Builds and edits a model-driven Power Apps app from a natural-language intent — tables, columns, relationships, adaptive forms with sub-grids, views, Choice-column charts, generative page intents for overview/dashboard surfaces (page `.tsx` generated in generate-pages after plan approval), and an app module + sitemap — via the headless cds-maker-sdk. Runs an interactive, multi-turn authoring flow (env selection, jobs-to-be-done first, then design-only App Spec authoring across confirmed levels, guardrail lint, plan-mode approval, generate-pages, full build) and a narrated build, and can download a deployed app back into an editable spec to change it. Use when the user says "build an app for X", "create a model-driven app", "make me an app to manage Y", or "edit/add to my app". This skill stands alone and does not require /genpage — but for a standalone generative page added to an app that already exists, use /genpage instead.
825SKILL.mdUpdated Aug 6, 2026
microsoft/setup-offline-profile
data-ai
VerifiedTrustedCommunity
Use when the user wants to enable offline mode for a Power Apps mobile app and create a Mobile Offline Profile in Dataverse — designs per-table row scope, relationships, columns, and sync frequency through a 3-gate approval flow.
825SKILL.mdUpdated Jul 1, 2026
microsoft/setup-datamodel
data-ai
VerifiedTrustedCommunity
Use when the user wants to design or redesign the Dataverse schema and connector plan for an existing mobile app, or has an ER diagram (image, Mermaid, or text) to apply. Skip when the user is creating a brand-new app — /create-mobile-app handles the data model inline.
825SKILL.mdUpdated Jul 1, 2026
microsoft/report-issue
tools
VerifiedTrustedCommunity
Use when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.
825SKILL.mdUpdated Jul 1, 2026