Will Invoke Pipeline (Legacy) be deprecated?

Hi benitovbreugel​ ,

Thank you for reaching out to fabric community.

• Continue using Invoke Pipeline (Legacy) for existing pipelines if it meets your requirements.
• Migrate selectively to the new Invoke Pipeline activity when you need cross-workspace invocation or child-pipeline monitoring.
• Regarding the deprecation status, no official deprecation date or removal timeline has been confirmed in the sources reviewed.
• i would recommendation to avoid rebuilding existing pipelines solely because the new activity is available. Test performance before migrating.

     Invoke pipeline activity - Microsoft Fabric | Microsoft Learn

Thanks!!

Hi benitovbreugel​,

Agreeing with v-sathmakuri's advice to keep Legacy where it already works and migrate selectively. I'm not aware of an announced deprecation date for the Legacy activity, so I'd check Microsoft's Fabric "What's new" and the Data Factory roadmap before planning around one.

A practical way to make that selective migration easy is to decide per pipeline, not per tenant:

Same workspace, simple fan-out, works today      -> stay on Invoke Pipeline (Legacy)
Child pipeline lives in another workspace         -> new Invoke Pipeline (needs a Connection)
You need the child run linked in monitoring       -> new Invoke Pipeline
Orchestration is perf-sensitive (many small calls) -> benchmark both before moving

Since you mentioned the performance reports, I'd measure rather than assume. Take one representative parent pipeline, run it a few times with each activity type, and compare the child-run start delay (time between the parent's activity start and the child's actual start) in the Monitor hub:

Parent run N: activity start -> child pipeline start  = orchestration overhead
Compare Legacy vs new over ~5 runs each, at similar times of day

To keep a later switch cheap, put the "call the child" logic behind a consistent pattern: one parent per domain, parameters passed the same way, and the child pipelines not depending on being invoked by a specific activity type. Then moving from Legacy to the new activity is swapping the activity and adding a Connection, with no change in the child.

Hi, I haven't seen any deprecation date announced for the legacy activity. The docs still show both side by side:
https://learn.microsoft.com/en-us/fabric/data-factory/invoke-pipeline-activity
When the new one was released, the team also mentioned legacy would continue to be supported. So it's fine to keep using it for same-workspace pipelines. For anything cross-workspace or where you want child run monitoring, I'd go with the new one since that's where new features are going.