Here’s what “easier” means

Your SSIS packages still pay the bills. They’ve earned that. The orchestration logic, the error handling, the parameter discipline, the framework patterns you’ve layered on over the years – that’s not legacy debt. That’s working software running mission-critical loads.

What you’ve also been carrying is the sense that the platform conversation has moved past them. ADF, then Synapse, now Fabric. Every keynote a new abstraction. Every analyst report a new mandate. And every time you’ve asked “what about the SSIS packages already in production,” the answer has been some version of “rewrite everything.”

That answer never sat right. You’ve known it doesn’t have to be either-or. Most enterprise data estates are not greenfield. The honest path forward is one that respects the working software while making the platform move possible.

What Microsoft Announced at FabCon Atlanta

Last month at FabCon Atlanta, Microsoft announced something that finally moves in that direction. The Invoke SSIS Package activity, currently in preview, lets a Fabric Data Factory pipeline execute an existing .dtsx package directly.

No rewrite.
No Azure-SSIS Integration Runtime to provision and manage.
Your SSIS logic runs natively inside the Fabric orchestration layer.

That’s a real shift. For the first time, “lift and shift to Fabric” is a sentence with technical substance behind it for SSIS shops, not just slideware.

But before anyone bakes this into a 2026 roadmap, the preview status matters.

What the Preview Does and Doesn’t Do Yet

Packages and execution logs live in OneLake. The activity exposes the Connection Managers and Property Overrides tabs you’d expect, so connection strings and credentials can be set dynamically at runtime via expressions, pipeline parameters, or system variables. What’s deliberately less clear in Microsoft’s announcement is exactly which connectivity scenarios work today versus which are coming. The “what’s next” section calls out expanded package sources, on-premises and private network connectivity, and custom or third-party component support as forthcoming capabilities rolling out through a series of private previews. That language tells you where the current gaps are without specifying every one.

The New Migration Questions

So the migration conversation does not end with “we’ll just use the Invoke SSIS Package activity.” It changes shape. The new questions are:

Which of your packages run cleanly against the current preview, and which depend on capabilities still being rolled out?

What’s the design pattern for hybrid orchestration — some pipelines invoking SSIS packages in Fabric, others still calling Azure-SSIS IR, others rebuilt as native Fabric pipelines?

When does the preview close enough gaps that retiring Azure-SSIS IR becomes a serious conversation?

What does Git integration, monitoring, and operational telemetry look like across that hybrid?

These are not blocking questions. They are design questions. The kind senior practitioners are good at, given clear information about what the platform actually does.

Software engineering solved the “how do I learn a new platform in a week without breaking production” problem years ago. Data integration mostly didn’t. The result has been twenty years of “burn a weekend reading docs, ship pilot project, hope it scales.” We can do better than that.

On 19 May, I’m running a full day on Fabric Data Factory. Live, online. We’ll work through what carries over from ADF, what doesn’t, the new Invoke SSIS Package activity and its current preview limits, the design patterns that survive the move, and the operational shape of running hybrid orchestration. Lecture and demo. No setup tax, no exercises, just a full day of getting senior practitioners to a working mental model.

If you’ve shipped pipelines in SSIS or ADF and you’re staring down a Fabric mandate, that day is built for you.

Register for A Day of Fabric Data Factory, 19 May 2026 →

Registration closes 16 May.