Context

We are automating Fabric workspace provisioning end-to-end via the public Fabric REST API:

• Create Web connection with allowUsageInUserControlledCode: true → works
• Upload notebook via POST /v1/workspaces/{wsId}/notebooks → works
• Trigger notebook remotely via RunNotebook job → works

The only manual step is binding the connection to the notebook (clicking "Connect" in the Connections pane). We need a way to automate this.

What we want

When we upload a notebook, we can include Lakehouse binding as part of the notebook metadata — fully automated, no UI step:

{
  "metadata": {
    "dependencies": {
      "lakehouse": {
        "known_lakehouses": [{ "id": "a4bdcfbf-..." }],
        "default_lakehouse": "a4bdcfbf-...",
        "default_lakehouse_name": "my_lake",
        "default_lakehouse_workspace_id": "029f9998-..."
      }
    }
  }
}

We want the same for Connections. Something like:

{
  "metadata": {
    "dependencies": {
      "lakehouse": { "..." : "..." },
      "connections": {
        "known_connections": [{ "id": "<connectionId>", "name": "my-web-conn" }]
      }
    }
  }
}

Or a REST API endpoint to bind after creation, similar to the existing Bind Semantic Model Connection API:

POST /v1/workspaces/{wsId}/notebooks/{nbId}/bindConnection

Observations

The binding creates a new UUID

After clicking "Connect" in the portal UI, the connection gets a new bound UUID different from the original connection ID. notebookutils.connections.getCredential() requires this bound UUID, not the original.

ID Source

Using the original connection ID with getCredential() fails with a 400 error: "Artifact Connection {id} does not exist." Only the bound UUID works.

The notebook definition does not change after binding

We downloaded the notebook .ipynb before and after the "Connect" step — they are identical. The binding is a server-side linkage with no representation in the notebook file. This is different from Lakehouse, where the binding is embedded in the notebook metadata.dependencies.

The portal performs this binding via an internal API

By inspecting browser network requests when clicking "Connect", we observed the portal calls an internal endpoint to create the binding. This internal endpoint is not part of the public Fabric REST API, does not resolve outside Fabric infrastructure, and rejects tokens obtained from notebookutils.credentials.getToken() inside notebooks.

Approaches we tried

Approach Result

Questions

1. Is there a way to include connection binding in the notebook metadata/definition (like Lakehouse dependencies) so it's bound at upload time via the Create/Update Notebook Definition API?
2. Is there a public REST API (or upcoming preview) to programmatically bind a connection to a notebook — similar to the Bind Semantic Model Connection API but for notebook items?
3. Is there a planned Fabric CLI command (e.g. fab assign or fab ln) to bind a connection to a notebook artifact?

References

• Fabric Connection in notebooks (Preview)
• Notebook Public APIs
• Connections REST API - Create Connection
• Bind Semantic Model Connection API
• Fabric CLI - Connection Examples

Environment

• Fabric capacity: Trial (Southeast Asia)
• Feature: "Fabric Connection in notebooks (Preview)" enabled
• Connection type: Web, Basic auth, allowUsageInUserControlledCode: true
• API version: v1
• Date: April 2026