Build a metadata-driven Fabric ingestion and medallion scaffold with coding agents - then master the skill that travels across platforms: specifying, bounding, and validating generated data engineering work.
Microsoft is shipping assistant-driven workflows into Fabric: Copilot in the web experience, developer agents in VS Code, and a CLI that can turn workspace changes into repeatable commands. Databricks, Snowflake, and the rest of the modern data stack are moving in the same direction: more generated code, more resources controlled by automation, and more responsibility on the engineer to verify what happened.
Here's what the demos skip: generated code is confidently wrong in ways that only show up downstream. A plausible join that silently drops rows. A schema assumption nobody made. A deprecated pattern dressed up as best practice.
The engineers who win in this shift aren't the fastest typists. They're the ones who can specify precisely, automate aggressively, and validate ruthlessly. We implement the workflow in Fabric, but the judgment muscle transfers: guardrails, metadata contracts, validation evidence, deployment checkpoints, cost boundaries, and security review.
The core lab is a metadata-driven Fabric ingestion and medallion scaffold. You leave with the working Fabric solution, plus validation patterns, agent guardrails, and a prompt/scaffold library you can adapt to other modern data platforms.
Lakehouses, notebooks, and pipelines scaffolded by a coding agent driving the Fabric CLI - from an agent skill you author, with guardrails. Zero portal clicking.
One configurable pattern instead of N pipelines - config tables, parameterized notebooks, dynamic sources - generated with an agent and audited where the blast radius is largest.
Bronze-to-Silver-to-Gold transformations drafted with coding assistance - then audited by you, with the planted failure modes found and fixed.
An LLM called straight from a Fabric notebook with your own API key - classification, extraction, summarization - as proper pipeline steps. Designed for the trial path, no paid Fabric Copilot capacity needed.
The unloved work produced automatically and matched to a gold-standard exemplar you provide - with a CLI deployment pattern included so you can promote the solution after the workshop.
What stays the same when you move from Fabric to Databricks, Snowflake, or another stack - and what must be rebuilt because every platform has its own CLI, security model, runtime, and deployment surface.
This is a practical engineering workshop. You do not need to be a Fabric expert already, but you should be comfortable reading code and thinking carefully about data quality.
We implement the build in Microsoft Fabric because concrete beats abstract. But the professional habit you are practicing is broader than one vendor.
Bounded tasks, repo instructions, metadata contracts, scaffold prompts, validation checklists, generated test/docs patterns, LLM enrichment boundaries, cost review, and human deployment checkpoints.
CLI commands, resource definitions, identity and permissions, runtime behavior, deployment artifacts, observability, and cost model. Fabric users get the direct implementation; other platform teams get the map.
The dangerous part is rarely the button. It is the unchecked assumption: an inner join, inferred schema, overwrite mode, missing source behavior, or quietly duplicated fact table. Those mistakes follow you across platforms.
Every session moves the same Fabric build forward. The center of gravity is the ingestion framework and the validation habits around it; along the way, we call out which parts are Fabric-specific and which parts are portable engineering patterns.
The evolving role, the hype, and the three surfaces: Copilot in Fabric web for exploration, VS Code for developer workflows, the CLI for automation - and how to match the interaction model to the task. Plus the mental model the whole day runs on: agents in a context-bounded box with a well-defined task.
Fabric items as code instead of clicks. You author an agent skill with real guardrails - explicit targets, pause-for-review checkpoints, "present the plan and stop", "you may not commit" - then drive the agent to scaffold the medallion workspace from that specification.
One configurable pattern instead of N hand-written pipelines: config tables, parameterized notebooks, dynamic sources - generated with an agent. Then the audit that matters most, because a confidently-wrong config assumption breaks every table the framework drives at once. Reading generated PySpark critically is a different skill from writing it, and this is where you learn it.
Bronze-to-Silver-to-Gold driven phase by phase using the gold-standard exemplar pattern, so generated code matches your bar, not the model's guess. LLM-powered transforms called from the notebook with your own API key (classification, extraction, summarization), designed for the trial path. Then generating tests, quality checks, and documentation from what you built, with deterministic tools for repeatable agent behavior.
A CLI-driven deployment pattern, then the honest part no demo shows: what model features cost in capacity units, the security implications of agents on your tenant, an honest capability map of every surface, and what to never automate. Closes with where Data Agents fit on the consumption side of Fabric, how the same workflow maps to Databricks/Snowflake-style teams, and open Q&A.
No - and I'm not going to pretend the paid Copilot features don't exist, or quietly make you buy them. The workshop is designed around the licensing reality.
This is the founding cohort - the price goes up once this run's results and testimonials are in. In exchange, I'll ask you for honest feedback.
Paying through your company? Most attendees do. You'll get a proper VAT invoice and a ready-made justification one-pager for your manager. Team pack: 5 seats for €795. Private team workshop: from €6,500. Email for team invoices and private dates.
Minimum cohort size: the live workshop will run if at least 10 participants are registered. If the minimum is not reached, you will be offered a full refund or the option to transfer your seat to the next scheduled cohort.

I'm Nikola Ilic, better known as Data Mozart. Microsoft Data Platform MVP, Principal Data Architect at iLink Digital, book author, and creator of Fabric and Power BI training that has reached thousands of professionals through Pluralsight, O'Reilly, conferences, and the Data Mozart blog and YouTube channel.
The agentic CLI workflow at the center of this workshop comes from my own consulting projects - the field version, not the keynote version. We implement it in Fabric because that gives us a concrete build, but the real lesson is broader: how to direct coding agents safely inside a data engineering workflow. What works, what breaks, what it costs. No vendor pitch, because no vendor is paying for this.
The guarantee: attend the full workshop, and if you don't feel it was worth the price, email me within 7 days for a full refund. No awkward forms, no hard feelings.
They'll be the ones who can direct coding agents precisely and catch their mistakes confidently. Four hours from now, you can have the Fabric scaffold, the portable validation habits, and a clear-eyed view of what these tools really do.
Reserve your seat - €179