topic Re: Fabric Notebook Error - AzureNotebookRef has been disposed in Data Engineering

Fabric Notebook Error - AzureNotebookRef has been disposed

pei2705ying — Mon, 08 Dec 2025 09:55:37 GMT

Hi, I am unable to open all of my Fabric notebooks in the workspace. When I click on it, the notebook viewer shows a “Something went wrong” page with a Retry button, and the diagnostic message:

AzureNotebookRef has been disposed.

Diagnostic ID: 5597c734-3de0-478a-85d5-84e84b1e8ccf

Steps I have already tried:

Opened the notebook in different browsers (Chrome, Edge)
Tried incognito mode
Cleared browser cache and cookies
Hard refresh (Ctrl+Shift+R)
Closed all other Fabric tabs

Despite this, the notebook still cannot be opened.

Any guidance or escalation would be appreciated. Thank you.

Re: Fabric Notebook Error - AzureNotebookRef has been disposed

AntoineW — Mon, 08 Dec 2025 15:13:36 GMT

Hi @pei2705ying,

Can you check the fabric capacity is it active or not ?

In the Admin Portal, go to Capacities, and check under Capacity, if the capacity status is active or paused.

Fabric notebooks run on a Fabric Capacity (compute). To verify if it’s active:

Go to your Fabric workspace.
Click on Settings (gear icon) → Manage capacities or Admin settings.
Check the status of the assigned capacity:
- Active / Running → OK.
- Stopped / Suspended → You may need to start it or contact your admin.

Hope it can help you !

Best regards,

Antoine

Re: Fabric Notebook Error - AzureNotebookRef has been disposed

pei2705ying — Tue, 09 Dec 2025 01:36:01 GMT

Hi @AntoineW,

Thank you for the suggestion, I’ve checked the Fabric capacity and it is currently Active (screenshot attached). So the capacity doesn’t seem to be the issue.

Appreciate any other suggestions

you may have for me to check. Thank you so much!

Re: Fabric Notebook Error - AzureNotebookRef has been disposed

Anonymous — Fri, 12 Dec 2025 11:13:04 GMT

Hi @pei2705ying ,

Thank you for reaching out to the Microsoft Fabric Community Forum and thank you for confirming that the Fabric capacity is active.

Since the issue persists across all notebooks, the behavior is more likely related to the notebook runtime environment or the workspace configuration rather than the capacity itself. To isolate the cause, please try creating a new blank notebook in the same workspace and check whether it opens successfully. If it fails with the same message, this points to a workspace-level issue.

Additionally, please test whether notebooks open correctly in another workspace to determine if the problem is isolated or tenant-wide. You may also review the Notebook Runtime Sessions under Monitor → Sessions to see if any sessions are stuck in a Starting or Failed state, as this can prevent new notebook environments from initializing. Lastly, ensure that the workspace is correctly assigned to the active capacity. Could you confirm whether a new notebook opens, whether notebooks work in other workspaces, and whether other users in your tenant are experiencing the same behavior?

Thank you.

Re: Fabric Notebook Error - AzureNotebookRef has been disposed

Anonymous — Tue, 16 Dec 2025 04:09:08 GMT

Hi @pei2705ying ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

Re: Fabric Notebook Error - AzureNotebookRef has been disposed

Anonymous — Fri, 19 Dec 2025 04:27:27 GMT

Hi @pei2705ying ,

We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.

Thank you.

Re: Fabric Notebook Error - AzureNotebookRef has been disposed

pei2705ying — Mon, 29 Dec 2025 05:32:54 GMT

Hi @Anonymous , sorry for late reply. I've identified that the issue is related to the clien't remote environment. The notebook opens and runs normally on my local laptop but fails to load when accessed from the client's remote machine.

This suggests the problem is environment specific (likely browser, network or VDI restrictions) rather than a Fabric notebook issue.

Thanks everyone for the guidance, it helped narrow this down.