flowstudio-power-automate-governance

Classify, audit, and govern Power Automate flows using the FlowStudio MCP cached store.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill flowstudio-power-automate-governance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flowstudio-power-automate-governance
Source: https://github.com/github/awesome-copilot/tree/main/skills/flowstudio-power-automate-governance
Command: npx skills add https://github.com/github/awesome-copilot --skill flowstudio-power-automate-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Power Platform administrators struggle to govern large numbers of Power Automate flows without Dataverse or the CoE Starter Kit, leaving flows unclassified, orphaned, non-compliant, and unmonitored.

Core Features & Use Cases

  • Compliance and Classification: Audit flows for missing governance metadata (business impact, owner team, support email) and bulk-write classification fields via the FlowStudio store.
  • Orphan Detection and Offboarding: Identify flows owned by deleted Azure AD accounts and reassign governance contacts when makers leave.
  • Archive Scoring and Connector Audits: Compute inactivity scores to find cleanup candidates and inventory connector usage for DLP and licensing analysis.
  • Use Case: An admin runs a quarterly governance review: list all store flows, flag those missing business impact or notification rules, tag archive candidates, and produce a tenant-wide governance dashboard.

Quick Start

Ask the AI to run a governance review of your Power Automate flows using the FlowStudio MCP store and report non-compliant or orphaned flows.

Frequently Asked Questions about flowstudio-power-automate-governance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify and tag Power Automate flows at scale?

Use list_store_flows to enumerate flows, then call get_store_flow per flow to read existing tags, and write classifications with update_store_flow. Tags can be mapped from connector names, and store tags must be read, appended, and rewritten since updates overwrite them.

How to detect orphaned Power Automate flows from deleted users?

Call list_store_makers and filter for deleted accounts that still own flows, then match flow owner principalIds from get_store_flow against those orphaned makers. Reassign the FlowStudio governance contact or tag flows for decommissioning.

Does Power Automate governance require Dataverse or the CoE Starter Kit?

No. This approach uses the FlowStudio MCP cached store to write governance metadata and run audits without Dataverse or the CoE Starter Kit. It does require a FlowStudio for Teams or MCP Pro+ subscription.

Why do FlowStudio store tools return a 403 or 404 error?

The store_* tools only work for FlowStudio for Teams or MCP Pro+ subscribers, so a 403 or 404 means the account lacks Pro+ access. Stop calling store tools and direct the user to the FlowStudio pricing page to upgrade.

Can update_store_flow change the actual Power Automate flow owner?

No. update_store_flow only writes metadata to the FlowStudio cache, such as ownerTeam and supportEmail, and does not modify the flow in Power Automate. Actual ownership transfers require the admin center or PowerShell.