Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
So today i went into my Pipeline and Notebook and a Connection has shown up whereas before I just had Workspace ID and Pipeline ID.
Thank fully I got admin to sort out a service principle in Azure but I have some issues.
1. Microsoft told me to parameterise everything. i cant parameterise this connection ID
2. It says Notebook and my name so even thorugh a service princaple has been used it seems to be a personal connection.
This is useless when you want to push your code base back into main dev workspace. or for example if another developer pulls the codebase into their dev workspace to work on it. I have been using library variables for the workspace Id and Notebook ID, Everyone and every environment has there own. But this has really thrown it.
So yes, is anyone else finding this and what can be done. Apart from waiting for microsoft to sort it out?
Solved! Go to Solution.
Hi @DebbieE ,
Thank you for reaching out to Microsoft Fabric Community.
Fabric recently added automatic Notebook Connections, but they currently get created as personal user connections and cannot be parameterized, which breaks Dev/Test/Prod workflows.
As a Workaround:
Ignore the auto-created connection - don’t rely on it.Authenticate inside the Notebook using your Service Principal (client ID + secret).This makes the Notebook fully portable for all developers and all workspaces.You can safely delete the personal connection if it appears.
Hi @DebbieE ,
If you are running the notebook through a pipeline, the following Microsoft documentations will help:
1.Notebook activity (pipeline execution + SPN/WI auth):
Notebook activity - Microsoft Fabric | Microsoft Learn
2.General guidance for notebooks (including support for parameters):
Develop, execute, and manage notebooks - Microsoft Fabric | Microsoft Learn
3.REST API for running notebooks (optional for external automation):
Manage and execute Fabric notebooks with public APIs - Microsoft Fabric | Microsoft Learn
Thank you.
Hi @DebbieE ,
May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.
Thank you.
Hi @DebbieE ,
I wanted to check if you had the opportunity to review the information provided and resolve the issue..?Please let us know if you need any further assistance.We are happy to help.
Thank you.
Hi @DebbieE ,
If you are running the notebook through a pipeline, the following Microsoft documentations will help:
1.Notebook activity (pipeline execution + SPN/WI auth):
Notebook activity - Microsoft Fabric | Microsoft Learn
2.General guidance for notebooks (including support for parameters):
Develop, execute, and manage notebooks - Microsoft Fabric | Microsoft Learn
3.REST API for running notebooks (optional for external automation):
Manage and execute Fabric notebooks with public APIs - Microsoft Fabric | Microsoft Learn
Thank you.
Hi @DebbieE ,
Thank you for reaching out to Microsoft Fabric Community.
Fabric recently added automatic Notebook Connections, but they currently get created as personal user connections and cannot be parameterized, which breaks Dev/Test/Prod workflows.
As a Workaround:
Ignore the auto-created connection - don’t rely on it.Authenticate inside the Notebook using your Service Principal (client ID + secret).This makes the Notebook fully portable for all developers and all workspaces.You can safely delete the personal connection if it appears.
Are they going ro sort this out. It feels like a poor show?
Also, I think I would need a lot more information re the workaround? I wouldnt know what to do from that? I am running the notebook through a pipeline. So definitely more information is needed.