Golden Data

Issue #11 · July 3, 2026

The BI Brief Changed in June. The JD Hasn't.

Paul Brown Writes Golden Data from Ogden, Utah 5 min read

Every Friday I check what the analytics craft is being asked to do. This week the answer involves a screenshot and a demo that worked.

Microsoft shipped Agent Skills for Power BI at Build 2026 on June 2. The demo: an AI takes a screenshot of a dashboard and rebuilds it from scratch. It works. The room moved the way rooms move when a tool does exactly what the job description said a human was for.

The job description hasn’t caught up. Most Power BI JDs at enterprise shops still list report authoring as a primary scope item. The governance layer — who defines what a metric is, who validates what the AI built, who owns what the agent is allowed to touch — that’s a different brief. It’s the one being paid for.

Senior ICs and BI Directors at Fabric shops have a narrow window before Q3 reviews to name the work they actually do. Microsoft made the distinction visible on June 2 and opened the skilling path on June 15. Most people in those roles haven’t looked at both calendars.

What’s actually moving in the market

Microsoft Build 2026 (June 2–3) shipped Agent Skills for Power BI — the report-authoring seat is being automated. Agent Skills for Power BI lets AI tools build reports from natural language or a screenshot — end-to-end, in production. Rayfin, a new SDK and CLI also announced at Build, brings agentic scaffolding to Fabric app development. Both target what “Power BI Developer” means as a function. The governance scope — semantic model ownership, metric definition, AI output validation — was not part of the demo. It was the assumption underneath it.

PBIR is now the default Power BI report format. The migration is already running. PBIR (Power BI Enhanced Report Format) became the default in the Power BI service on January 25, 2026 and in Desktop in March. Existing reports migrate automatically on next save. The format stores reports as structured, text-based files — git-trackable, diff-able, deployable through CI/CD. Power BI development now requires developer hygiene: version control, commit conventions, deployment pipelines. JDs at Fabric shops updated in Q1. The rest update when they hit the migration.

ServiceNow cut hundreds of employees on June 11, citing AI efficiencies in its own operations. Solution consulting, product marketing, and learning and development were in scope. The roles that deploy, train on, and sustain platform work are the ones clearing. At Oracle in March, at Salesforce in May–June, and now at ServiceNow in June: AI handles the maintenance layer. The role that governs what AI produces is a different brief. The roles in scope are the ones that explained the tool, not the ones that owned its output.

The Fabric specialist premium over the Power BI developer is $30K–$65K in 2026. Fabric specialists command $195K while Power BI developers land at $130K–$165K, per KORE1’s 2026 hiring guide. The Fabric specialist owns the semantic model, manages data products as code, and defines metric governance enterprise-wide. The Power BI developer builds the reports the model produces. Build 2026 is automating the second role. The first is where the premium lives.

What I’d do this week

Register for one Microsoft Data Days governance session before June 30.

Data Days runs June 15 through August 7, 2026 — free, 100+ live sessions covering Fabric, Power BI, Azure SQL AI, and certification tracks. The governance and semantic model sessions are running now.

  • The user moment: This Saturday morning or Monday before standup. The Data Days schedule is searchable and sessions are registerable in under five minutes.
  • The shape: Research block — 20 minutes to find the right session. Register for one governance or semantic model session before June 30.
  • The time budget: 20 minutes to find and register. One hour to attend.
  • The artifact: One session attended. One sentence written: what the session covered that your current JD doesn't mention. That sentence is the gap document. It exists whether you write it or not. This week you write it.
  • What success looks like: In the Q3 comp or promotion conversation, you name a specific session you attended in June while the governance requirement was still being written into JDs. Most people will encounter it in the September posting. You read it in the June agenda.

Open one Power BI report you own and check its format.

If the report predates March 2026, it’s still in .pbix format. The next save migrates it to PBIR. That migration creates a trackable change. The senior who does this deliberately — and commits it — has a governance artifact. The one who hits it by accident has a surprise.

  • The user moment: Tuesday morning before the sprint standup, or the next time "update the dashboard" lands in your queue.
  • The shape: Tool drill — open the report, save it, observe the PBIR migration. If your team has Git integration, commit the change with a clear message.
  • The time budget: 30 minutes. 20 to run the migration. 10 to write one sentence about what moved: metric definitions, visual properties, page layout — now visible as diff-able text.
  • The artifact: One migrated report in PBIR format. If your shop doesn't have Git integration yet, that's also the artifact — name it in your next 1:1 as a governance gap you've identified.
  • What success looks like: When "are our Power BI reports version-controlled?" comes up in Q3, you have the answer and a concrete example. Most BI developers will be learning what PBIR means when that question is asked. You ran the migration in June.

Sources

Crafting runs weekly. The job is to be useful, not to sell. If a line in here is close to a move you're working on, the email reaches a person.

Hiring rather than hunting? Signal is the column for your side of the desk.

Email me Read more Crafting

← All Crafting issues · Drafted with Claude · Edited by Paul Brown