Flowstudio Power Automate Governance
Classify Power Automate flows, enforce compliance metadata, and audit connectors at scale through FlowStudio MCP without CoE Starter Kit or Dataverse.
Overview
FlowStudio Power Automate Governance is an agent skill for the Operate phase that classifies and audits Power Automate flows at scale using FlowStudio MCP cached-store governance metadata.
Install
npx skills add https://github.com/github/awesome-copilot --skill flowstudio-power-automate-governanceWhat is this skill?
- Govern via FlowStudio MCP cached store—no Dataverse or CoE Starter Kit required
- Classify flows by business impact, ownership, orphans, and connector usage audits
- Write governance metadata with update_store_flow; compute governance and archive scores
- Manage notification rules and generate compliance reports
- Pairs with flowstudio-power-automate-monitoring—same store_* tools, governance vs health intent
Adoption & trust: 637 installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have dozens of citizen flows with unclear owners, risky connectors, and no lightweight way to tag impact or run compliance reviews outside Dataverse.
Who is it for?
Solo builders or tiny IT leads managing Power Platform automation sprawl with a FlowStudio MCP subscription.
Skip if: Greenfield flow authoring only, Azure-only infra with no Power Automate, or teams without FlowStudio Teams/MCP Pro+ access.
When should I use this skill?
Asked to tag or classify flows, set business impact, detect orphans, audit connectors, check compliance, compute archive scores, manage notification rules, run governance review, generate compliance report, or offboard a
What do I get? / Deliverables
Flows carry governance metadata, compliance and archive scores, and audit-friendly reports written through FlowStudio store tools—ready for ongoing review cycles.
- Updated flow governance metadata via store writes
- Compliance or governance review report with classification and audit findings
Recommended Skills
Journey fit
Governance, ownership, archive scoring, and offboarding are ongoing production responsibilities—Operate is where solo builders keep citizen-automation estates under control. Iterate fits recurring governance reviews, notification rules, and metadata writes that refine how automations are allowed to run over time.
How it compares
FlowStudio cached-store governance via MCP—not the Microsoft CoE Starter Kit on Dataverse and not operational health dashboards alone.
Common Questions / FAQ
Who is flowstudio-power-automate-governance for?
Solo builders and small teams responsible for Power Automate and Power Apps hygiene who want agent-driven tagging, audits, and compliance reports through FlowStudio.
When should I use flowstudio-power-automate-governance?
During Operate iterate cycles when you must classify flows, detect orphans, audit connectors, set notification rules, offboard a maker, or generate a governance or compliance report.
Is flowstudio-power-automate-governance safe to install?
It drives MCP writes to flow metadata—review the Security Audits panel on this page, confirm subscription scope, and restrict connector credentials before enabling autonomous governance updates.
Workflow Chain
Then invoke: flowstudio power automate monitoring
SKILL.md
READMESKILL.md - Flowstudio Power Automate Governance
# Power Automate Governance with FlowStudio MCP Classify, tag, and govern Power Automate flows at scale through the FlowStudio MCP **cached store** — without Dataverse, without the CoE Starter Kit, and without the Power Automate portal. This skill uses the same `store_*` tool family as `flowstudio-power-automate-monitoring`, but with a different *intent*: governance writes metadata (`update_store_flow`) and reads for *audit and classification* outcomes. Monitoring reads the same tools for *operational health* outcomes. Don't try to memorize which skill "owns" which tool — pick by what the user is doing. For health checks and failure-rate dashboards, load `flowstudio-power-automate-monitoring` instead. > **⚠️ Pro+ subscription required.** This skill calls `store_*` tools that > only work for FlowStudio for Teams or MCP Pro+ subscribers. > > **If the user does not have Pro+ access:** the first `store_*` tool call > will return a 403/404 error. When that happens: > 1. STOP calling store tools > 2. Tell the user governance features require a Pro+ subscription > 3. Link them to https://mcp.flowstudio.app/pricing > > **Discovery:** load tool schemas via the meta-tools rather than `tools/list` — > call `tool_search` with `query: "skill:governance"` for the canonical bundle, > or `query: "select:update_store_flow"` for a single tool. This skill covers > workflow patterns and field semantics — things `tool_search` cannot tell you. > If this document disagrees with a real API response, the API wins. --- ## Critical: How to Extract Flow IDs `list_store_flows` returns `id` in format `<environmentId>.<flowId>`. **You must split on the first `.`** to get `environmentName` and `flowName` for all other tools: ``` id = "Default-<envGuid>.<flowGuid>" environmentName = "Default-<envGuid>" (everything before first ".") flowName = "<flowGuid>" (everything after first ".") ``` Also: skip entries that have no `displayName` or have `state=Deleted` — these are sparse records or flows that no longer exist in Power Automate. If a deleted flow has `monitor=true`, suggest disabling monitoring (`update_store_flow` with `monitor=false`) to free up a monitoring slot (standard plan includes 20). --- ## The Write Tool: `update_store_flow` `update_store_flow` writes governance metadata to the **Flow Studio cache only** — it does NOT modify the flow in Power Automate. These fields are not visible via `get_live_flow` or the PA portal. They exist only in the Flow Studio store and are used by Flow Studio's scanning pipeline and notification rules. This means: - `ownerTeam` / `supportEmail` — sets who Flow Studio considers the governance contact. Does NOT change the actual PA flow owner. - `rule_notify_email` — sets who receives Flow Studio failure/missing-run notifications. Does NOT change Microsoft's built-in flow failure alerts. - `monitor` / `critical` / `businessImpact` — Flow Studio classification only. Power Automate has no equivalent fields. Merge semantics — only fields you provide are updated. Returns the full updated record (same shape as `get_store_flow`). Required parameters: `environmentName`, `flowName`. A