audit-tenant-settings
Automatically invoke this skill whenever the user asks about Fabric tenant settings or Power BI tenant settings or auditing tenant settings. You can use this skill if the user mentions "Fabric administration".
npx skills add data-goblin/power-bi-agentic-development --skill audit-tenant-settings --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Audit Tenant Settings Audit Fabric / Power BI tenant settings against a curated baseline, surface drift, enumerate delegated overrides at capacity / domain / workspace scope, investigate the Entra security groups those settings reference, and turn findings into a grounded discussion about what to do next. Always invoke the `fabric-cli` skill alongside this skill; it provides the `fab` CLI guidance, admin API references, and the `microsoft-learn` MCP server that this skill depends on. ## Prerequisites This plugin is an add-on to the `fabric-cli` plugin. It requires: - **fabric-cli plugin** installed and enabled; provides `fab` CLI guidance, the `microsoft-learn` MCP server, and admin API reference docs. - **fab CLI** (`ms-fabric-cli`) authenticated with a Fabric / Power BI admin account. - **az CLI** authenticated with Graph permissions (`Group.Read.All`, `User.Read.All`, `Directory.Read.All`, `RoleManagement.Read.Directory`) when investigating security groups. ## Settings Per-project configuration via `.claude/fabric-admin.local.md`: ```markdown --- enabled: true tenant_label: "Contoso" snapshot_path: "~/.cache/fabric-admin-audit/last-snapshot.json" drift_threshold_high: 5 drift_
- Prerequisites
- Settings
- When to use this skill
- Critical rules
- Authoritative sources (in order)
- Workflow
- 1. Verify prerequisites
- 2. Run the audit script
- 3. Review the script output
- 4. Enumerate delegated overrides
- 5. Investigate security group setup and strategy
- 6. Drill down on areas of drift
- 7. Present findings and open a grounded discussion
- 8. Formulate next steps with the user
uv run ${CLAUDE_PLUGIN_ROOT}/skills/audit-tenant-settings/scripts/audit-tenant-settings.py -o /tmp/tenant-audit.md
uv run ${CLAUDE_PLUGIN_ROOT}/skills/audit-tenant-settings/scripts/generate_audit_pdf.py -o /tmp/tenant-audit.pdf
grep -i -A6 '<keyword>' ${CLAUDE_PLUGIN_ROOT}/skills/audit-tenant-settings/references/tenant-settings-metadata.yaml
fab api "admin/tenantsettings" -q "text.tenantSettings[?settingName=='<API name>']"What does the audit-tenant-settings skill do?
Automatically invoke this skill whenever the user asks about Fabric tenant settings or Power BI tenant settings or auditing tenant settings. You can use this skill if the user mentions "Fabric administration".
How do I install it?
Run `npx skills add data-goblin/power-bi-agentic-development --skill audit-tenant-settings --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From data-goblin/power-bi-agentic-development, a repository with 833 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.