{
  "id": "power-platform-governance-dataverse-security",
  "name": "Power Platform Governance & Dataverse Security Review",
  "type": "skill",
  "provider": "microsoft",
  "harnesses": [
    "codex",
    "claude-code",
    "cursor",
    "gemini",
    "kiro",
    "other"
  ],
  "summary": "Review Power Platform environment strategy, DLP policy design, Dataverse security roles, business unit hierarchy, table/row/column permissions, connector governance, and Center of Excellence alignment for least-privilege and sprawl risks. Static review only; production DLP changes are live-guard gated.",
  "source_type": "original",
  "official_docs": [
    "https://learn.microsoft.com/power-platform/guidance/adoption/environment-strategy",
    "https://learn.microsoft.com/power-platform/guidance/adoption/dlp-strategy",
    "https://learn.microsoft.com/power-platform/admin/wp-security-cds",
    "https://learn.microsoft.com/power-platform/admin/wp-data-loss-prevention",
    "https://learn.microsoft.com/power-platform/admin/database-security",
    "https://learn.microsoft.com/power-platform/guidance/coe/starter-kit"
  ],
  "security_notes": "Production DLP policy changes are live-guard gated and must never be auto-applied. Never request or accept tenant IDs, environment IDs, connection strings, service principal secrets, or customer data. Refuse requests to disable or broadly relax DLP for convenience. All privilege grants in Dataverse are additive and accumulative — over-permissioning cannot be hidden by app-level controls alone. Connector classification disputes must document business justification before any reclassification.",
  "last_verified": "2026-06-16",
  "path": "skills/microsoft/power-platform-governance-dataverse-security",
  "author": "github: VincentChuWaiChow",
  "version": "0.1.0",
  "category": "security",
  "companion_agents": ["power-platform-governance-dataverse-security-agent"]
}