route-environments

Name: route-environments
Author: microsoft

523stars103forks

How to install route-environments?

microsoft/power-platform-skills/route-environments

$npx -y skills add microsoft/power-platform-skills --skill route-environments

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# Environment Resolution
2
3	You are helping the user understand and manage which Power Automate environment
4	they work in — where their flows are created, where they should build new ones,
5	and how to switch between environments.
6
7	> Uses the FlowAgent MCP tools (`resolve_environment`, `list_environments`,
8	> `set_current_env`, `get_current_env`).
9
10	## Step 1: Understand what the user needs
11
12	- "Which environment am I in?" → call `get_current_env` or `resolve_environment`
13	- "Where should I create flows?" → help them pick the right environment
14	- "What environments do I have?" → call `list_environments`
15	- "Switch my environment" → call `set_current_env`
16
17	## Step 2: List and explain environments
18
19	Call `list_environments` and present a clear summary:
20
21	\| Environment \| Type \| Location \| Notes \|
22	\|-------------\|------\|----------\|-------\|
23	\| ... \| Default / Developer / Sandbox / Production \| ... \| ... \|
24
25	Help the user identify:
26	- Default environment — shared, not recommended for production flows
27	- Developer environments — personal, ideal for building and testing
28	- Production/Sandbox — team environments for deployed flows
29
30	## Step 3: Set the working environment
31
32	If the user wants to create flows in a specific environment, call
33	`set_current_env` with that environment ID. This pins all subsequent
34	FlowAgent operations to that environment (no need to pass `--env` each time).
35
36	Recommendation for new users: If they have a Developer environment, suggest
37	using that. If not, suggest they ask their admin to provision one, or use the
38	default environment for simple personal automations.
39
40	## Guidance
41
42	- `resolve_environment` shows how the environment resolves (routing → poll → fallback)
43	- `set_current_env` changes the session default — it does NOT change tenant-level routing
44	- Tenant-level environment routing (which env new makers land in by default) is
45	configured at the admin level in `admin.powerplatform.microsoft.com` — direct
46	admins there if they ask about changing org-wide routing
47	- For maker-facing questions: "When you open make.powerautomate.com, your default
48	environment determines where new flows are created"
49
50	## Decision Tree
51
52	```
53	User asks about environments?
54	├── "Which environment am I in?" → get_current_env / resolve_environment
55	├── "What environments exist?" → list_environments with summary table
56	├── "Where should I build?" → Recommend Developer env; set_current_env
57	├── "Switch to X environment" → set_current_env
58	├── "How do I create a new environment?" → Direct to PPAC admin center
59	└── "What is environment routing?" → Explain: determines default for new makers
60	```

People who liked this also viewed

6 picks

Type

route-environments

523stars103forks

View on GitHub

How to install route-environments?

microsoft/power-platform-skills/route-environments

$npx -y skills add microsoft/power-platform-skills --skill route-environments

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Environment Resolution
2
3	You are helping the user understand and manage which Power Automate environment
4	they work in — where their flows are created, where they should build new ones,
5	and how to switch between environments.
6
7	> Uses the FlowAgent MCP tools (`resolve_environment`, `list_environments`,
8	> `set_current_env`, `get_current_env`).
9
10	## Step 1: Understand what the user needs
11
12	- "Which environment am I in?" → call `get_current_env` or `resolve_environment`
13	- "Where should I create flows?" → help them pick the right environment
14	- "What environments do I have?" → call `list_environments`
15	- "Switch my environment" → call `set_current_env`
16
17	## Step 2: List and explain environments
18
19	Call `list_environments` and present a clear summary:
20
21	\| Environment \| Type \| Location \| Notes \|
22	\|-------------\|------\|----------\|-------\|
23	\| ... \| Default / Developer / Sandbox / Production \| ... \| ... \|
24
25	Help the user identify:
26	- Default environment — shared, not recommended for production flows
27	- Developer environments — personal, ideal for building and testing
28	- Production/Sandbox — team environments for deployed flows
29
30	## Step 3: Set the working environment
31
32	If the user wants to create flows in a specific environment, call
33	`set_current_env` with that environment ID. This pins all subsequent
34	FlowAgent operations to that environment (no need to pass `--env` each time).
35
36	Recommendation for new users: If they have a Developer environment, suggest
37	using that. If not, suggest they ask their admin to provision one, or use the
38	default environment for simple personal automations.
39
40	## Guidance
41
42	- `resolve_environment` shows how the environment resolves (routing → poll → fallback)
43	- `set_current_env` changes the session default — it does NOT change tenant-level routing
44	- Tenant-level environment routing (which env new makers land in by default) is
45	configured at the admin level in `admin.powerplatform.microsoft.com` — direct
46	admins there if they ask about changing org-wide routing
47	- For maker-facing questions: "When you open make.powerautomate.com, your default
48	environment determines where new flows are created"
49
50	## Decision Tree
51
52	```
53	User asks about environments?
54	├── "Which environment am I in?" → get_current_env / resolve_environment
55	├── "What environments exist?" → list_environments with summary table
56	├── "Where should I build?" → Recommend Developer env; set_current_env
57	├── "Switch to X environment" → set_current_env
58	├── "How do I create a new environment?" → Direct to PPAC admin center
59	└── "What is environment routing?" → Explain: determines default for new makers
60	```

People who liked this also viewed

6 picks

Type