agentleFS
korchard333korchard333/claude-power-platform-community/.claude/skills/governance/SKILL.md

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

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
  1. Distinctive:

    If you're starting from zero, do these in order:

    line 50
  2. Distinctive:

    No DLP policies at all (any connector can talk to any connector — data exfiltration risk)

    line 63
  3. Distinctive:

    No visibility into what makers are building (shadow IT grows silently)

    line 66
  4. Distinctive:

    No compliance controls until an audit happens (too late)

    line 69

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

PillarDescriptionKey Tools
Data ProtectionControl which connectors can be used togetherDLP policies, connector classification
Maker ControlsGovern who can build what, whereTenant settings, sharing limits, environment routing
VisibilityUnderstand what's been built and by whomCoE Starter Kit, audit logs, analytics
ComplianceMeet regulatory requirementsPurview, audit logging, data residency, encryption
Cost ManagementControl capacity and licensing spendManaged 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

LevelDescriptionKey Actions
1 — ReactiveNo governance, default environment sprawlEnable tenant-level DLP, lock down default env
2 — FoundationalBasic DLP + env strategyEnvironment groups, maker routing, basic CoE
3 — ManagedManaged Environments + CoE monitoringFull CoE deployment, audit logging, compliance
4 — OptimizedAutomated governance, self-service within guardrailsAdvanced DLP, auto-claim licensing, catalog

Quick Start: Day-1 Governance

If you're starting from zero, do these in order:

  1. Create a tenant-level DLP policy — classify connectors, block dangerous ones (see dlp-policies.md)
  2. Lock down the default environment — restrict sharing, remove premium connector access
  3. Enable default environment routing — route makers to personal developer environments
  4. Enable Managed Environments on all non-dev environments
  5. Deploy CoE Starter Kit Core module — get visibility into what's been built (see coe-starter-kit.md)
  6. 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 groups
  • alm — Solution Checker enforcement, pipeline governance
  • security — Security roles, column security, row-level security
  • licensing — License compliance, Managed Environment entitlements
  • copilot-studio — Agent governance, DLP for Copilot Studio

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.