BYO-UI
Microsoft

Power BI

Curated anchor platform in business intelligence and semantic models with material relevance to the Marcom operating stack and a first-party developer surface.

Analytics, SEO & experimentationSystem of intelligenceAgent-accessible SaaS
Representative source ↗Product site ↗
System roleSystem of intelligence
Access maturityAgent-accessible SaaS
Agent postureFirst-party provider
Reference updatedNot stated by publisher
BYO-UI reviewedJul 10, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Remote: schema/DAX query and insights from existing semantic models; local: create/modify semantic models

02 · Data you can retrieve

Remote: schema/DAX query and insights from existing semantic models; local: create/modify semantic models

03 · Actions and write paths

Power BI's first-party MCP/agent surface includes state-changing tools in the documented capability area: Remote: schema/DAX query and insights from existing semantic models; local: create/modify semantic models. The audit did not enumerate every mutation; verify the current tool catalog and require explicit confirmation for consequential actions.

04 · Authentication and permissions

For Power BI, the audited authentication model is: Authentication model is documented by the vendor; inspect the cited source before implementation. The effective permission model is: Existing vendor identity, account, tenant, and permission controls should be treated as the authorization boundary. Reconfirm the cited first-party source before implementation.

05 · Monitoring, approval, and recovery

Require explicit human confirmation for costly, externally visible, destructive, or hard-to-reverse actions. Official Microsoft docs clearly separate remote query surface from local authoring surface; both preview.

06 · Gaps and implementation limits

Official Microsoft docs clearly separate remote query surface from local authoring surface; both preview.

First-party access

Documented surfaces

DAX semantic-model query ↗Power BI supports governed DAX queries against semantic models through REST APIs. Tenant settings, Build permission, row-level security, SSO, capacity, and service-principal limitations apply; this is not arbitrary SQL against the underlying source database.Source: Develop with the Execute DAX Queries REST APIMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceProduct ↗Native platform experience

Agent access

MCP and adjacent posture

Verified first-party provider MCPMicrosoft remote and local MCP serversPreview

Role: provider

Read scope: Remote: schema/DAX query and insights from existing semantic models; local: create/modify semantic models

Write scope: State-changing tools are present in the documented scope; review the official tool catalog and require confirmation for consequential actions.

Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.

Approval boundary: Require explicit human confirmation for costly, externally visible, destructive, or hard-to-reverse actions.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access1
Identity4
Governance4
Agent access3
UI extensibility3
Portability4
Observability3
Documentation4

Proposed interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that Microsoft ships these experiences.

Single-platform patterns

  • Executive metrics and semantic-model workbench
  • Executive insight brief
  • Experiment review board
  • Anomaly investigation room
Use in the brief composer →

Multi-platform compositions

  • Power BI + warehouse or semantic layer: executive insight brief
  • Power BI + CRM or lifecycle platform + work-management system: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

5 recorded sources
APISource inventory
https://learn.microsoft.com/en-us/rest/api/power-bi/ ↗

First-party API reference or API overview recorded for this platform.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Developer docsSource inventory
https://learn.microsoft.com/en-us/power-bi/developer/ ↗

First-party developer documentation or platform overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://powerbi.microsoft.com/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

DAX semantic-model queryTargeted review
Develop with the Execute DAX Queries REST API ↗

Power BI supports governed DAX queries against semantic models through REST APIs. Tenant settings, Build permission, row-level security, SSO, capacity, and service-principal limitations apply; this is not arbitrary SQL…

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Targeted first-party access review

Verified fact

Tied to the representative first-party source or targeted access review.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.