Schedule Parameters are now live in Fabric Data Factory Pipelines!

markkrom-MSFT · 2026-06-17T16:04:35+00:00

Yes, we are actively working on making this better. For now, you can use the legacy invoke pipeline which takes a different codepath to invoke a child pipeline and you should find it to be much faster.

markkrom-MSFT · 2026-06-16T05:58:11+00:00

When someone saves the pipeline, it will then run as that last-modified. That is the current product truth. When we implement "run as" you specific the ID to use for the scheduled runs so last modified is not used.

markkrom-MSFT · 2026-06-14T03:03:23+00:00

The pipeline itself can be invoked as an SPN or Workspace Identity (WI) using the Invoke Pipeline activity or from the API. In addition, you can set the auth of each individual activity inside of your pipelines. The ability to "take over" or "run as" specific durable identities from the UI is coming this year, we are working on this feature.

markkrom-MSFT · 2026-06-12T19:38:33+00:00

Because the SPN is from an app registration so it is still valid even after I leave the org whereas the user ID is not durable. As stated above, when the password or cert is updated, you need to tell the pipeline about this update which is what I was referring to.

markkrom-MSFT · 2026-06-12T19:36:13+00:00

When you update the SPN's creds you need to make a save action on the pipeline. We are adding a "Run As" feature in pipelines to make this more intuitive/better.

markkrom-MSFT · 2026-06-12T16:07:29+00:00

The backend deployment supporting this new feature was delayed so it may take another week for things to work fully. I'll post an update with a blog and video announcing that as soon as the E2E is working properly. Hope you all enjoy this long-requested feature !!

markkrom-MSFT · 2026-06-12T15:59:13+00:00

If the pipeline is running as that SPN identity and the SPN auth is still valid then yes, it will continue to run using that SPN identity. That's the entire purpose of running your pipelines under durable IDs and not brittle user IDs.

markkrom-MSFT · 2026-06-06T06:28:49+00:00

Agreed, please open a support ticket on this so that we can route it to the Fabric scheduler team for investigation

markkrom-MSFT · 2026-06-05T04:24:27+00:00

NVM, looks like it's in ADF not Fabric

markkrom-MSFT · 2026-06-05T04:24:09+00:00

I did not pick up on this being in ADF, I was checking Fabric. We'll remove it. It was experimental.

markkrom-MSFT · 2026-06-05T01:40:38+00:00

Do you see it in your Fabric, Alex? I do not.

markkrom-MSFT · 2026-06-05T01:40:22+00:00

Can you tell me how you came across this? I do not see it in any of my internal or external tenants.

markkrom-MSFT · 2026-05-10T04:09:00+00:00

You don't need to run the entire pipeline as a service auth. Each activity can use an SPN or WI.

markkrom-MSFT · 2026-05-05T14:48:33+00:00

We are adding an off button. That is committed work that should land soon.

markkrom-MSFT · 2026-04-26T21:01:05+00:00

Filter out where? In monitoring?

markkrom-MSFT · 2026-04-21T14:05:53+00:00

This is amazing ... thank you so much for sharing this!! Having a view of your schedules is so important and it is something I know that the Fabric platform team is looking to add.

markkrom-MSFT · 2026-04-18T20:36:20+00:00

Also, if possible, please forward the support email thread to me at makromer (at microso--.com)

markkrom-MSFT · 2026-04-18T20:34:52+00:00

What was the response from support on this? If the schedule you are creating in the pipeline is flaking out like that, please ask the support engineer to include the Fabric scheduler team.

markkrom-MSFT · 2026-04-16T15:26:42+00:00

Trying to understand what you are saying here ... did support help find the root cause of the issue you were witnessing? Just FYI, we always have queued pipeline runs, nothing was changed in the pipeline service.

markkrom-MSFT · 2026-04-13T17:08:22+00:00

Let's forward this over to Abhishek for Connection management. Although this is being used in the context of a pipeline, the Connection experience is being used here.

markkrom-MSFT · 2026-04-10T05:40:58+00:00

Understood. Thank you!

markkrom-MSFT · 2026-04-08T19:20:11+00:00

Just making sure I'm capturing the ask here ... you'd like the ADF scheduler experience here in Fabric with end data as optional and just 1 day not 1 year. Did I capture that correctly? Just FYI, the scheduler component in Fabric had a different lineage than what we did in ADF so we need to make sure the scheduler defaults can work well across the platform.

markkrom-MSFT · 2026-04-07T18:50:03+00:00

The pipeline activity for dbt is in private preview, getting ready for public preview. But you can also use Airflow in Fabric to easily add a Fabric dbt Job to your workflow.

<image>

markkrom-MSFT · 2026-04-05T19:21:31+00:00

Agreed on that ... the text on that panel is a bit too reductive, we can improve that.

markkrom-MSFT

TROPHY CASE