
Audit Permissions
Audit who can access what in a Power Platform environment before you ship or hand off an app.
Overview
audit-permissions is an agent skill for the Ship phase that helps solo builders review Power Platform permission and access posture before production.
Install
npx skills add https://github.com/microsoft/power-platform-skills --skill audit-permissionsWhat is this skill?
- Targets Power Platform permission and access posture in Microsoft’s skills pack context
- Pairs with other power-platform-skills for environment-wide governance workflows
- Fits solo builders shipping canvas or model-driven apps who must prove who has admin vs user rights
- Use when connectors, flows, or shared environments need a documented permission baseline
Adoption & trust: 73 installs on skills.sh; 349 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are shipping a Power App or automation but cannot confidently list who has environment admin, connection ownership, or excessive Dataverse roles.
Who is it for?
Indie builders on Power Platform who need a quick, agent-driven permissions pass before go-live or stakeholder sign-off.
Skip if: Teams that only need OneDrive file upload wiring without any governance review—use connector skills like add-onedrive instead.
When should I use this skill?
When you need to review or document Power Platform permissions before shipping or after environment changes.
What do I get? / Deliverables
You get a structured permission review your agent can execute so risky grants are visible and fixable before launch.
- Permission findings summary
- Remediation checklist for excessive grants
Recommended Skills
Journey fit
Permission auditing is a pre-release and ongoing governance step—canonical shelf is Ship because builders run it before production cutover or compliance reviews. Security subphase covers access reviews, least-privilege checks, and connector or Dataverse role exposure—not day-to-day feature coding.
How it compares
Governance-focused skill package for Power Platform access reviews, not a generic OWASP web-app scanner or an MCP server.
Common Questions / FAQ
Who is audit-permissions for?
Solo and small-team builders using Claude Code, Cursor, or Codex with Microsoft’s power-platform-skills who must verify roles and connector access before shipping.
When should I use audit-permissions?
During Ship (security) before production promotion, after adding new connections or shared environments, and during Operate when access drift is suspected.
Is audit-permissions safe to install?
Review the Security Audits panel on this skill’s catalog page and inspect the skill files in the microsoft/power-platform-skills repo before granting shell or tenant admin actions to your agent.
SKILL.md
READMESKILL.md - Audit Permissions
# audit-permissions Installs: 73 Source: microsoft/power-platform-skills { "url": "https://www.skills.sh/microsoft/power-platform-skills/audit-permissions", "name": "audit-permissions", "rank": 91, "slug": "audit-permissions", "source": "microsoft/power-platform-skills", "installs": 73, "skillsShId": "microsoft/power-platform-skills/audit-permissions", "sourceType": "github" }