Unsupported Activities in PowerShell Migration from ADF to Fabric

Hi Mahimaa29,

That behavior is expected today. The PowerShell upgrader only converts activities that exist in Fabric; unsupported ADF activities are left as placeholders (often a simple “Wait”) so the pipeline structure survives. You’ll need to replace those with Fabric-native equivalents or call back to ADF temporarily. See: PowerShell migration guide and the ADF>Fabric parity/limits: Activity continuity (parity), Data Factory limitations.

What’s supported vs not (as of Oct 2025)
Microsoft maintains a live parity matrix. Highlights: most control/movement tasks (Copy, ForEach, Lookup, If, Switch, Web, etc.) are supported; some ADF items are not available in Fabric yet (e.g., Validation, Mapping Data Flow, SSIS IR, HDInsight family). Sources: parity matrix, limitations.

Recommended workarounds you can use now

1. Invoke back to ADF for gaps – Use Fabric’s Invoke pipeline to call the original ADF pipeline for steps that require SSIS IR or Mapping Data Flows until you fully replace them. See: migration planning (Invoke pipeline).
2. Replace ADF Validation – Rebuild with Get Metadata + If/Until patterns in Fabric pipelines.
3. Replace Mapping Data Flows – Reimplement in Dataflow Gen2 (Power Query) or in Notebooks / SQL depending on your transform style. See: planning guide.
4. Auth/connector edge cases – Note current limits (e.g., Web activity SPN auth not supported yet). Check the live list: limitations and supported connectors: connector overview.

How to manage the migration cleanly

• Pre-scan with the parity matrix to tag activities that will need rebuilds: parity.
• Migrate with resolutions and then search for Wait/no-op placeholders and replace them step-by-step: PowerShell upgrader.
• Track the roadmap for when gaps close: Fabric Data Factory roadmap.

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.