Govern Power Automate flows and Power Apps at scale using the FlowStudio MCP cached store. Classify flows by business impact, detect orphaned resources, audit connector usage, enforce compliance standards, manage notification rules, and compute governance scores — all without Dataverse or the CoE St

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: 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 FlowStudio 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 FlowStudio store and are used by FlowStudio's scanning pipeline and notification rules. This means: ownerTeam / supportEmail — sets who FlowStudio considers the governance contact. Does NOT change the actual PA flow owner. rule notify email — sets who receives FlowStudio failure/missing run notifications. Does NOT change Microsoft's built in flow failure alerts. monitor / critical / businessImpact — FlowStudio 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 . All other fields optional. Settable Fields Field Type Purpose monitor bool Enable run level scanning (standard plan: 20 flows included) rule notify onfail bool Send email notification on any failed run rule notify onmissingdays number Send notification when flow hasn't run in N days (0 = disabled) rule notify email string Comma separated notification recipients description string What the flow does tags string Classification tags (also auto extracted from description hashtags ) businessImpact string Low / Medium / High / Critical businessJustification string Why the flow exists, what process it automates businessValue string Business value statement ownerTeam string Accountable team ownerBusinessUnit string Business unit supportGroup string Support escalation group supportEmail string Support contact email critical bool Designate as business critical tier string Standard or Premium security string Security classification or notes Caution with security : The security field on get store flow contains structured JSON (e.g. {"triggerRequestAuthenticationType":"All"} ). Writing a plain string like "reviewed" will overwrite this. To mark a flow as security reviewed, use tags instead. Governance Workflows 1. Compliance Detail Review Identify flows missing required governance metadata. Common compliance fields: description , businessImpact , businessJustification , ownerTeam , supportEmail , monitor , rule notify onfail , critical . Ask for the user's policy before flagging. 2. Orphaned Resource Detection Find flows owned by deleted or disabled Azure AD accounts. update store flow does not transfer actual PA ownership; use the admin center or PowerShell for that. Some orphaned looking flows are system generated; tag them instead of reassigning when appropriate. Store coverage is only as fresh as the latest scan. 3. Archive Score Calculation Compute an inactivity score (0 7) per flow to identify cleanup candidates. Archive via MCP means stop the flow and tag it. Deletion requires the portal or admin PowerShell. 4. Connector Audit Audit which connectors are in use across monitored flows. Useful for DLP impact analysis and premium license planning. Scope to monitored flows where possible; each get store flow call costs time. list store connections lists connection instances, not connector usage per flow. DLP policies are not exposed; ask the user for connector classifications. 5. Notification Rule Management Configure monitoring and alerting for flows at scale. Check monitoring limits before bulk enabling monitor=true . If no flows have critical=true , report that as a governance gap before configuring alerts. 6. Classification and Tagging Bulk classify flows by connector type, business function, or risk level. Store tags and description hashtags are separate systems. tags= overwrites store tags, so read/append/write. Avoid overriding computed tier unless asked. 7. Maker Offboarding When an employee leaves, identify their flows and apps, and reassign FlowStudio governance contacts and notification recipients. This changes FlowStudio governance contacts, not actual PA ownership. Power Apps ownership changes are manual/admin center work. 8. Security Review Review flows for potential security concerns using cached store data. Security signals: security.triggerRequestAuthenticationType , sharingType , connections , referencedResources , tier . Never overwrite the structured security field; tag reviewed flows instead. 9. Environment Governance Audit environments for compliance and sprawl. 10. Governance Dashboard Generate a tenant wide governance summary. Field Reference: get store flow Fields Used in Governance All fields below are confirmed present on the get store flow response. Fields marked with are also available on list store flows (cheaper). Field Type Governance use displayName string Archive score (test/demo name detection) state string Archive score, lifecycle management tier string License audit (Standard vs Premium) monitor bool Is this flow being actively monitored? critical bool Business critical designation (settable via update store flow) businessImpact string Compliance classification businessJustification string Compliance attestation ownerTeam string Ownership accountability supportEmail string Escalation contact rule notify onfail bool Failure alerting configured? rule notify onmissingdays number SLA monitoring configured? rule notify email string Alert recipients description string Documentation completeness tags string Classification — list store flows shows description extracted hashtags only; store tags written by update store flow require get store flow to read back runPeriodTotal number Activity level runPeriodFailRate number Health status runLast ISO string Last run timestamp scanned ISO string Data freshness deleted bool Lifecycle tracking createdTime ISO string Archive score (age) lastModifiedTime ISO string Archive score (staleness) owners JSON string Orphan detection, ownership audit — parse with json.loads() connections JSON string Connector audit, tier — parse with json.loads() complexity JSON string Archive score (simplicity) — parse with json.loads() security JSON string Auth type audit — parse with json.loads(), contains triggerRequestAuthenticationType sharingType string Oversharing detection (top level, NOT inside security) referencedResources JSON string URL audit — parse with json.loads() Related Skills flowstudio power automate monitoring — Health checks, failure rates, inventory (read only) flowstudio power automate mcp — Foundation skill: connection setup, MCP helper, tool discovery flowstudio power automate debug — Deep diagnosis with action level inputs/outputs flowstudio power automate build — Build and deploy flow definitions

flowstudio-power-automate-governance