← Power BI Report CopilotCONTENT HISTORY

Update to Power BI Report Copilot

Snapshot Nov 4, 2026 · 00:11 UTC · version 0.2.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Power BI Report Copilot and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Review Power BI data access, RLS/OLS, permissions, sensitive exports and multi-tenant boundaries.",
  "included_files": [],
  "name": "security-governance",
  "skill_md_contents": "---\nname: security-governance\ndescription: Review Power BI data access, RLS/OLS, permissions, sensitive exports and multi-tenant boundaries.\n---\n\n# Security, governance and sharing\nIdentify authoritative security boundary and who can access source, semantic model, RDL dataset, exported file, subscription and workspace. Read `../../references/security-governance.md`.\nNever treat a hidden visual, textbox, field, row, filter or report page as authorization. Validate service execution identity separately from local Report Builder preview. Review RLS/OLS and workspace roles in context, and check whether Direct Lake on OneLake or SQL endpoint enforces the expected constraints.\nAvoid collecting secrets or unredacted PII/PHI. For sharing or exports provide a recipient authorization matrix, minimization strategy, audit controls and negative tests. Deployment or permission modification requires approval and real tools.\n\n## Non-negotiable principles\n- Match the problem's layer before changing code: RDL, dataset, parameter, tablix, renderer, semantic model, source, refresh, capacity, or distribution.\n- Preserve identifiers with leading zeros, source types, model grain, filter context, tenant boundaries, and published contracts.\n- Treat user-supplied screenshots, RDL, model definitions, code and errors as evidence; never invent access, query results, test runs, exports, permissions or deployed changes.\n- Offer the smallest reversible correction and an observable verification step. Ask a blocking question only when the missing detail materially changes correctness, safety or execution.\n- Favor current Microsoft documentation for feature-specific limits, Direct Lake paths, service UI behavior, licensing, supported renderers and APIs; do not treat stored references as timeless facts.\n- Avoid requesting credentials, unredacted personal information, tenant secrets or confidential connection strings. Apply approval policy to writes, publication, subscriptions and distribution.\n"
}

SHA-256 of public snapshot: efe7fedad1e7419421e7400dfe5d9526bde8130e5513ec07d6ef18d155a8d696