The Security Feature That’s Actually About Speed

Here's the thing nobody's saying about Fabric Eventstream's new Custom CA and mTLS support: it isn't really a security feature. Or rather, it is, but the teams who'll benefit most aren't security teams. They're Spark engineers who've been running…

What the March 2026 Fabric Influencers Spotlight Tells Us About Where Spark Architecture Is Actually Heading

The Fabric community has a habit of telling you the future before the product team ships it. You just have to know where to listen. Microsoft's March 2026 Fabric Influencers Spotlight…

Workspace Customer-Managed Keys for BYOK in Microsoft Fabric: Where Native Acceleration Pays Off and Where Fallbacks Bite

Somewhere inside a regulated financial services firm, a platform engineer stared at two Fabric capacities on her screen. One ran Power BI semantic models encrypted with BYOK…

Your Fabric Spark Jobs Have Been Failing in Silence. That Just Changed.

You schedule a notebook. You schedule a pipeline. You walk away. That's the deal. Set it and forget it. Except "forget it" has a dark side nobody warns you about. When a scheduled Spark job dies at 2 AM, it dies quiet. No…

What “Upgrade your Synapse pipelines to Microsoft Fabric with confidence (Preview)” actually means for Fabric Spark teams in production

Preview posts are written to soothe. Production teams read them like incident reviewers. They want to know what moves, what stays off, and what still needs proof…

Fabric notebook resources in Git give Spark teams a real release boundary

Most Spark notebook trouble is not caused by the notebook. It is caused by the little files loitering around it. A notebook runs fine in dev. In test, it quietly depends on a config file somebody copied by hand. In prod, a…

What the February 2026 gateway release really means for Fabric Spark teams

Monthly gateway release posts are usually the corporate equivalent of dry toast. A version number appears. Power BI Desktop compatibility gets a polite bow. Then everyone goes back to moving data and arguing with refresh…

Bulk Import and Export Item Definitions Are the Fabric APIs Ops Teams Needed

Most Fabric deployment pain is not dramatic. It is slow, dumb, and expensive in the worst way. Somebody asks you to move a workspace full of notebooks, pipelines, reports, and models. Then the afternoon disappears into…

The API layer that wasn’t supposed to matter

The strangest platform announcements are usually the boring ones. Nobody throws a party for source control. Nobody leans back and says, "Hell yes, deployment pipelines," with a straight face. The applause goes to the flashy stuff: faster engines, new…

The Moment Your Spark Pipeline Stops Being a Pet

There's a team, a data engineering squad at a mid-size financial services firm, who spent eighteen months building their Lakehouse architecture on Microsoft Fabric. They had notebooks. They had Spark job definitions. They had a deployment process…

DeltaFlow just changed the CDC conversation for Fabric Spark teams

DeltaFlow preview in Fabric Eventstreams can turn raw Debezium CDC into analytics-ready streams for four supported database sources. For Spark teams, the opportunity is obvious and the caveat is too: test it now, but do not cut…

Operationalizing Fabric’s February 2026 feature drop: what actually matters for Spark teams

Operationalizing Fabric's February 2026 feature drop: what actually matters for Spark teams Microsoft's monthly feature summaries have a familiar problem. They flatten every change into the same cheerful…

Operationalizing the semantic model permissions update for Fabric data agents

Operationalizing the semantic model permissions update for Fabric data agents Permissions in data platforms have a remarkable talent for turning a two-minute job into a small municipal drama. You want one ordinary thing.…

ExtractLabel just changed how your Spark pipelines should handle unstructured data

ExtractLabel just changed how your Spark pipelines should handle unstructured data Every data engineer eventually inherits the same cursed pipeline. Upstream sends you a blob of human text. Somewhere in that blob…

What “Recent data” in Fabric means for Spark teams when time is the real bottleneck

Microsoft Fabric's February 2026 update shipped a small feature called Recent data in Dataflow Gen2. For Spark data engineering teams, it removes repeated navigation friction at the ingestion layer -- if you pair…

From CDC to Lakehouse: Making Fabric Eventstreams SQL Survive Contact with Production Spark

From CDC to lakehouse: making Fabric Eventstreams SQL survive contact with production Spark Every data team eventually has the same bright idea: "Let's do CDC so everything is real time." What follows is…

Fabric Spark's Native Execution Engine: What Speeds Up, What Falls Back, and What to Watch

Open Mirroring + OneLake: Spark patterns that keep latency from eating your weekends

Open Mirroring is deceptively simple to set up and tricky to run well with Spark at scale. Here are the architecture choices, anti-patterns, and validation checks that keep your pipelines from falling apart in…

What “Execute Power Query Programmatically” Means for Fabric Spark Teams

What “Execute Power Query Programmatically” Means for Fabric Spark Teams Somewhere in a Fabric workspace right now, two teams are maintaining the same transformation twice. The BI team owns it in Power Query. The Spark team…

What the February 2026 Fabric Influencers Spotlight means for your Spark team

What the February 2026 Fabric Influencers Spotlight means for your Spark team Microsoft published its February 2026 Fabric Influencers Spotlight last week. Twelve community posts. MVPs and Super Users. Most people skim…

Fabric Spark failure playbook: OneLake and mirroring under real production pressure

A field-tested runbook for the failures that hide between Spark, OneLake, and mirroring in Microsoft Fabric: detection signals, triage sequences, and remediation tradeoffs from real production incidents.

The most boring technology announcement might be the most important one for your Fabric Spark team Microsoft's new ODBC Driver for Fabric Data Engineering looks like a checkbox feature. It isn't. Here's what it means for production Spark teams, the migration risks nobody's talking about, and a concrete rollout checklist.

The most boring technology announcement might be the most important one for your Fabric Spark team

Microsoft's new ODBC Driver for Fabric Data Engineering looks like a checkbox feature. It isn't. Here's what it means for production Spark teams, the migration risks nobody's talking about, and a…

fabric-cicd Is Now Officially Supported — Here’s Your Production Deployment Checklist Three days ago, Microsoft promoted fabric-cicd from community project to officially supported tool. That Python library your team has been running in a “don’t look too closely at our deployment process” sort of way now carries Microsoft’s name and their support commitment. That shift matters. Your compliance team can stop asking “is this thing even supported?” You can open Microsoft support tickets when it breaks. The roadmap is no longer a volunteer effort, so features will land faster and bugs will get fixed on a schedule. But here’s where most teams trip.

fabric-cicd Is Now Officially Supported — Here's Your Production Deployment Checklist

The Spark-to-Warehouse Connector in Fabric: What It Does, How It Breaks, and When to Use It The Spark connector for Fabric Data Warehouse lets your notebooks read from and write to Warehouse tables with one line of code. Here's what it does, how it breaks, and when to use Warehouse vs Lakehouse as your serving layer.

The Spark-to-Warehouse Connector in Fabric: What It Does, How It Breaks, and When to Use It

Fabric Spark billing just got clearer. Here’s how to make the most of it. Microsoft split AI function consumption out of Spark billing into its own meter. Your total cost stays the same, but your alerting, thresholds, and capacity plans probably need updating. Here's a concrete checklist.

Fabric Spark billing just got clearer. Here's how to make the most of it.

From Demo to Production: ML-Enriched Power BI in Microsoft Fabric Microsoft's new end-to-end pattern for enriching Power BI reports with ML in Fabric looks clean in the demo. Here's the production migration checklist for Spark teams crossing the gap from notebook to ops.

From Demo to Production: ML-Enriched Power BI in Microsoft Fabric

Microsoft's new end-to-end pattern for enriching Power BI reports with ML in Fabric looks clean in the demo. Here's the production migration checklist for Spark teams crossing the gap from notebook to ops.

Microsoft Fabric Warehouse + Spark: Interoperability Patterns That Actually Work If you’ve spent any time in a Fabric workspace with both Data Engineering (Spark) and Data Warehouse, you’ve probably had this moment: Spark is great for big transformations, complex parsing, and “just let me code it.” The Warehouse is great for a curated SQL model, concurrency, and giving the BI world a stable contract. And yet… teams still end up copying data around like they’re paid by the duplicate. The good news: Fabric’s architectural bet is that OneLake + Delta is the contract surface across engines. That means you can design a pipeline where Spark and Warehouse cooperate instead of competing.

Microsoft Fabric Warehouse + Spark: Interoperability Patterns That Actually Work

What SQL database in Fabric actually means for your Spark pipelines There is a particular kind of excitement that sweeps through data engineering teams when Microsoft announces a new database option. It is the same mixture of curiosity and low-grade dread you might feel upon learning that your neighborhood is getting a new highway interchange. Useful, probably. Disruptive, definitely. Someone is going to have to figure out the on-ramps. SQL database in Fabric went generally available in November 2025. Built on the same SQL Database Engine that powers Azure SQL Database, it is the first fully SaaS-native operational database living inside Microsoft Fabric.

What SQL database in Fabric actually means for your Spark pipelines

There is a particular kind of excitement that sweeps through data engineering teams when Microsoft announces a new database option. It is the same mixture of curiosity and low-grade dread you might feel upon learning that your…

Microsoft Fabric Table Maintenance Optimization: A Cross-Workload Survival Guide Your Delta tables are drowning. Thousands of tiny Parquet files pile up after every streaming microbatch. Power BI dashboards stall on cold-cache queries. SQL analytics endpoints grind through fragmented row groups. And somewhere in the middle of the medallion architecture, a Spark job is rewriting perfectly good files because nobody told it they were already compacted. This is the small-file problem at scale — and in Microsoft Fabric, where a single Delta table can serve Spark, SQL analytics endpoint, Power BI Direct Lake, and Warehouse simultaneously, it becomes a cross-workload survival situation.

Microsoft Fabric Table Maintenance Optimization: A Cross-Workload Survival Guide

Your Delta tables are drowning. Thousands of tiny Parquet files pile up after every streaming microbatch. Power BI dashboards stall on cold-cache queries. SQL analytics endpoints grind through fragmented row groups.…

Optimizing Spark Performance with the Native Execution Engine (NEE) in Microsoft Fabric Spark tuning often starts with the usual suspects (shuffle volume, skew, join strategy, caching)… but sometimes the biggest win is simply executing the same logical plan on a faster engine. Microsoft Fabric’s Native Execution Engine (NEE) does exactly that: it keeps Spark’s APIs and control plane, but runs a large portion of Spark SQL / DataFrame execution on a vectorized C++ engine. What NEE is (and why it’s fast) NEE is a vectorized native engine that integrates into Fabric Spark and can accelerate many SQL/DataFrame operators without you rewriting your code.

Optimizing Spark Performance with the Native Execution Engine (NEE) in Microsoft Fabric