governance
Skill46 starsChanged 8 months agoMITView on GitHub
Power Platform governance, DLP policies, Center of Excellence, tenant administration. Use when: DLP, data loss prevention, governance, CoE, Center of Excellence, tenant settings, sharing limits, compliance, audit, data residency, connector classification, maker controls, admin API.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- plugin87/ux-ui-agent-skillstheir own version, first seen Nov 10, 2026
- BrendenKennedy/claude-for-ai-platformstheir own version, first seen Oct 13, 2026
- wrsmith108/governance-claude-skilltheir own version, first seen Oct 11, 2026
- thegeekybeng/architecture-governancetheir own version, first seen Jul 21, 2026
- CarbeneAI/Forgetheir own version, first seen Apr 22, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- plugin87/ux-ui-agent-skills★ 3.2ksame name
- wrsmith108/governance-claude-skill★ 13same name
- CarbeneAI/Forge★ 9same name
- BrendenKennedy/claude-for-ai-platforms★ 1same name
- thegeekybeng/architecture-governance★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- accessibility-uxSkill
- ai-builderSkill
- almSkill
- architectureSkill
- azure-openaiSkill
- business-process-flowsSkill
- canvas-appsSkill
- code-appsSkill
- code-reviewerSkill
- copilot-studioSkill
- custom-connectorsSkill
- dashboardsSkill
- data-migrationSkill
- dataverse-mcpSkill
- dataverseSkill
- dataverse-web-apiSkill
- devops-engineerSkill
- env-strategySkill
- integration-patternsSkill
- licensingSkill
- m365-integrationSkill
- model-driven-appsSkill
- observabilitySkill
- pcfSkill
- perf-optimiseSkill
- platform-builderSkill
- pluginsSkill
- power-automateSkill
- power-biSkill
- power-pagesSkill
- power-platform-teamSkill
- project-managerSkill
- securitySkill
- solutions-architectSkill
- spec-driven-devSkill
- test-engineSkill
- testingSkill
- uat-coordinatorSkill
- web-resourcesSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 50
If you're starting from zero, do these in order:
- Distinctive: line 63
No DLP policies at all (any connector can talk to any connector — data exfiltration risk)
- Distinctive: line 66
No visibility into what makers are building (shadow IT grows silently)
- Distinctive: line 69
No compliance controls until an audit happens (too late)
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Power Platform Governance
When to Use
Trigger when designing data loss prevention policies, configuring tenant-level settings, deploying the Center of Excellence Starter Kit, establishing compliance controls, setting up audit logging, or managing maker governance at scale.
Governance Pillars
| Pillar | Description | Key Tools |
| Data Protection | Control which connectors can be used together | DLP policies, connector classification |
| Maker Controls | Govern who can build what, where | Tenant settings, sharing limits, environment routing |
| Visibility | Understand what's been built and by whom | CoE Starter Kit, audit logs, analytics |
| Compliance | Meet regulatory requirements | Purview, audit logging, data residency, encryption |
| Cost Management | Control capacity and licensing spend | Managed Environments, pay-as-you-go monitoring |
⚠️ REQUIRED: Load Sub-Files Before Implementation
SKILL.md is a summary only — it is NOT sufficient for implementation.
The detailed content (complete payloads, XML templates, working examples, edge-case handling) lives in sub-files in the same directory as this SKILL.md. Before writing any code, you MUST use read_file on the sub-files relevant to your task:
- DLP Policies — connector classification (Business/Non-Business/Blocked), policy design patterns, enforcement stages, limits, HTTP connector blocking, custom connector governance, action-level controls
- CoE Starter Kit — Core/Governance/Nurture/Audit modules, installation prerequisites, configuration, monitoring dashboards, upgrade patterns, common customizations
- Tenant Administration — tenant settings, sharing limits, maker controls, connector consent, default environment routing, environment groups, Power Platform admin API and cmdlets
- Compliance & Audit — audit logging (Dataverse + Microsoft Purview), data residency, GDPR compliance, data export, encryption (CMK), Lockbox, IP firewall, customer-managed keys
Governance Maturity Model
| Level | Description | Key Actions |
| 1 — Reactive | No governance, default environment sprawl | Enable tenant-level DLP, lock down default env |
| 2 — Foundational | Basic DLP + env strategy | Environment groups, maker routing, basic CoE |
| 3 — Managed | Managed Environments + CoE monitoring | Full CoE deployment, audit logging, compliance |
| 4 — Optimized | Automated governance, self-service within guardrails | Advanced DLP, auto-claim licensing, catalog |
Quick Start: Day-1 Governance
If you're starting from zero, do these in order:
- Create a tenant-level DLP policy — classify connectors, block dangerous ones (see
dlp-policies.md) - Lock down the default environment — restrict sharing, remove premium connector access
- Enable default environment routing — route makers to personal developer environments
- Enable Managed Environments on all non-dev environments
- Deploy CoE Starter Kit Core module — get visibility into what's been built (see
coe-starter-kit.md) - Configure audit logging — enable Dataverse audit + Purview (see
compliance-audit.md)
Anti-Patterns
- No DLP policies at all (any connector can talk to any connector — data exfiltration risk)
- DLP so restrictive that makers can't build anything useful (governance should enable, not block)
- Ignoring the default environment (it accumulates ungoverned apps)
- No visibility into what makers are building (shadow IT grows silently)
- Governance policies without enforcement tooling (documented but not implemented)
- Manual governance reviews instead of automated policy enforcement
- No compliance controls until an audit happens (too late)
- Tenant settings left at defaults (overly permissive by default)
- CoE Starter Kit deployed but never monitored or updated
- Different governance standards per project with no central policy
Related Skills
env-strategy— Environment topology, Managed Environments, environment groupsalm— Solution Checker enforcement, pipeline governancesecurity— Security roles, column security, row-level securitylicensing— License compliance, Managed Environment entitlementscopilot-studio— Agent governance, DLP for Copilot Studio
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

