Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Example task
The user asks: "Help me plan a Power BI executive sales dashboard. It needs revenue, pipeline, win rate, region, segment, refresh status, and permissions. I have not exported the semantic model or permission list yet." This is an illustrative example. Names, metrics, and evidence are synthetic.
Without the bundle
Create pages for revenue, pipeline, win rate, region, and segment. Use cards, line charts, and slicers. Add refresh status and share it with executives. Issue: the answer invents readiness without asking for semantic model evidence, metric definitions, filters, refresh, security, permissions, or owner approval.
Using the bundle
Readiness decision: blocked pending evidence, but enough context exists to draft a requirements plan. Source note: Power BI product behavior should be checked against Microsoft Learn source categories for reports, dashboards, semantic models, refresh, RLS, permissions, and sharing. Local evidence used: only the user's requested metrics and audience. Missing before final design: workspace/app/report evidence, semantic model export, field and measure definitions, DAX/M logic, filters, source-of-record definitions, refresh/gateway evidence, RLS/OLS roles, workspace roles, item permissions, app audience, export/sharing settings, data classification, and owner approval.
Why this is better: The bundle-assisted output is stronger because it: - includes a visible source note; - distinguishes user-provided facts from missing verification; - avoids inventing semantic model fields, measures, filters, roles, and permissions; - checks refresh, lineage, RLS/OLS, sharing, and publishing risks; - requires explicit confirmation before live Power BI actions.
Inspect this example in the repositoryTool guide
Microsoft Power BI
Defines safe, source-aware use of Microsoft Power BI in OpenKnowledgeBank bundles.
Read the fileWorkflow
Plan Power BI Report
Evidence-first workflow for planning a Power BI report or dashboard.
Read the fileWorkflow
Review Power BI Publishing and Permissions
Checklist workflow for source-aware Power BI publishing, sharing, export, embedding, and permission risk review.
Read the fileTemplate
Power BI Report Readiness Plan
Output format for planning or reviewing a Power BI report, dashboard, semantic model, refresh, and sharing workflow.
Read the fileIs this bundle right for your task?
Who it is for
- People who configure, operate, integrate, govern, or review work performed in Microsoft Power BI
- Teams working in analytics, data, business-intelligence
When to use it
- A proposed Microsoft Power BI configuration or workflow change needs current IDs, permissions, dependencies, tests, and rollback evidence.
- A report, export, integration, or automation result needs to be reconciled against actual workspace state and current product documentation.
What you need to provide
- The product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner.
- Current IDs, settings, records, logs, screenshots, integration details, and test evidence needed to verify the requested change.
Tasks and expected outputs
Questions it helps answer
- Plan Power BI reports and dashboards without inventing workspaces, semantic models, fields, measures, filters, or permissions.
- Separate official Microsoft Learn product and API behavior from user-provided tenant, workspace, semantic model, and report evidence.
- Review refresh, lineage, RLS, sharing, export, embedding, and publishing decisions with explicit confirmation boundaries.
- Produce Power BI readiness plans that include source notes, metric validation, security review, and governance checks.
What it helps produce
- Power BI report readiness plan
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner. Ask the agent to review Microsoft Power BI and produce Power BI report readiness plan that maps configuration evidence, dependencies, permissions, tests, rollback, and actions that still require approval. Begin with Microsoft Learn — En Us / Power Bi, then confirm that the reference is current and applicable. Inspect Microsoft Power BI before drafting.
Context path: bundles/tools/microsoft-power-bi
What the bundle includes
Tools
- Microsoft Power BI
- Power BI Desktop
- Power BI service
- Microsoft Fabric
- Power BI REST APIs
Frameworks
- verify-first BI planning
- semantic model evidence check
- source-of-record reconciliation
- publishing and permissions confirmation boundary
Commands
/plan-power-bi-report
Evaluations
- Power BI report plan quality check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Changing live configuration, records, permissions, automations, integrations, or shared data without verified scope, testing, rollback, and approval.
Known limitations
- Not a complete Power BI Desktop, Power BI service, Microsoft Fabric, DAX, Power Query M, REST API, pricing, licensing, connector, capacity, tenant administration, or release reference.
- Requires user-provided tenant, workspace, semantic model, report, dashboard, dataflow, field, measure, filter, RLS/OLS, refresh, lineage, gateway, capacity, permission, and governance evidence before final conclusions.
- Does not replace Power BI administrator, BI governance, data owner, security, privacy, accessibility, legal, procurement, or compliance review.
Safety notes
- Require explicit confirmation before publishing, overwriting, deleting, exporting, embedding, sharing, changing permissions, triggering refreshes, changing schedules, changing gateway/credential settings, or broadening access.
- Do not claim access to Power BI tenants, workspaces, semantic models, reports, dashboards, dataflows, permissions, refresh history, or APIs unless the user provides evidence or authorized tool access.