본문으로 건너뛰기
cccskills
무료GitHub에 공개

route-environments

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

microsoft/power-platform-skills1천2026년 10월 18일 업데이트

Integrates Power Pages generative-AI summarization APIs (PREVIEW) into a Single Page Application (SPA) site — the Search Summary API and the Data Summarization API — on any record-detail or list page. Generates per-target service code (CSRF-handled) and AI site settings; delegates Web API settings, table permissions, and web roles to `/integrate-webapi` and `/create-webroles`. Use whenever a user wants AI/Copilot output that condenses Dataverse content on a Power Pages site — an AI summary, AI-generated overview or "key insights" across a record or list, a search-results summary, a case/incident summary, or recommendation-chip refinement — even when phrased as "AI-generated paragraph", "insights", or "overview". Do NOT use for: generative pages in model-driven apps (use the model-apps `genpage` skill), Copilot Studio agents/chatbots, summarizing documents or PDFs, Power BI dashboards, plain keyword search with no AI summary, or plain Dataverse CRUD (use `/integrate-webapi`).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

microsoft/power-platform-skills1천2026년 10월 18일 업데이트

Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

microsoft/power-platform-skills1천2026년 10월 18일 업데이트

Internal implementation skill invoked by /add-native for camera, image picker, barcode scanner, QR scanner, and camera/gallery Dataverse artifact workflows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

microsoft/power-platform-skills1천2026년 10월 18일 업데이트

Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flows to additional pages without re-creating metadata. Use when the user wants to add, connect, register, or link a Power Automate cloud flow to their site.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

microsoft/power-platform-skills1천2026년 10월 18일 업데이트

Adds any Power Platform connector to a Power Apps code app. Generic fallback for connectors not covered by a specific skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

microsoft/power-platform-skills1천2026년 10월 18일 업데이트

microsoft의 스킬 모두 보기

이 스킬의 문제 신고