topic Re: Connection Property of Notebook Activity in Pipelines Unavailable - Help in Data Engineering

Connection Property of Notebook Activity in Pipelines Unavailable - Help

sean_cochran — Mon, 08 Dec 2025 15:45:28 GMT

This blog post announced a new feature - notebook activities in pipelines have a "connection" property that allows users to specify whether to run the notebook as a user, a workspace identity, or a service principal:

This feature doers not appear for us. I checked both new and existing notebooks/pipelines. The notebook activity documentation explains the feature but does not mention any steps to take. Has anyone had any luck finding and/or using this feature?

Re: Connection Property of Notebook Activity in Pipelines Unavailable - Help

Ugk161610 — Mon, 08 Dec 2025 16:34:59 GMT

Hi sean_cochran ,

We ran into the same thing this week. The blog post and docs are already updated, but the actual “Connection” option hasn’t reached every tenant yet. Nothing is missing on your side it simply hasn’t rolled out everywhere.

A few things we noticed:

The option only appeared for us after the workspace received the most recent backend update. Older workspaces still don’t show it.
Creating a brand-new workspace made the connection dropdown appear for some people, so rollout seems to be workspace-level, not tenant-level.
If you're in a region that usually gets features later, you may just not have the update yet.

There’s no setting to turn it on and nothing you can configure manually. It’s just a staggered rollout, and we’re waiting for it as well.

Once the update hits your tenant, the connection dropdown will show up automatically.

GopiKrishna

Re: Connection Property of Notebook Activity in Pipelines Unavailable - Help

sean_cochran — Mon, 08 Dec 2025 16:38:50 GMT

Thanks for the response!

Re: Connection Property of Notebook Activity in Pipelines Unavailable - Help

sean_cochran — Mon, 08 Dec 2025 17:44:50 GMT

Update for anyone else who is working through this - I tried creating a new workspace and that did not enable the feature. It appears that waiting is the only option.