Hello Mohammed Abdullah,
Greetings! Thanks for raising this question in the Q&A forum.
Since you've confirmed this happens across multiple notebooks and even with a different Microsoft account from a separate organization, this rules out a workspace-specific permission or tenant configuration issue. That points to either something in your local browser/network environment blocking the notebook editor's resources, or a broader client-side rendering issue rather than a backend outage tied to one workspace. The notebook experience in Azure ML Studio loads a heavy JavaScript-based editor plus a live WebSocket connection to your compute instance, so it is especially sensitive to browser extensions, proxies, and cached files.
Here is how to narrow it down.
1. Check Azure Service Health first
Go to Azure Portal > Help + Support > Service Health > Service issues and filter for Azure Machine Learning in your region. This confirms whether there's a known active incident before you spend time on client-side troubleshooting.
2. Confirm your compute instance is Running
In Azure Machine Learning Studio, go to Compute and check the state of the compute instance backing the notebook. If it shows Stopped, Creating, or Failed, the notebook editor can hang indefinitely trying to attach a kernel. Start it if stopped, or recreate it if failed.
3. Test in a clean browser session
Open an incognito/private window with all extensions disabled and try the notebook again. Ad blockers, security extensions, and content filtering extensions are a common cause of exactly this symptom, since they can silently block the WebSocket or script requests the notebook editor depends on.
4. Clear browser cache and try a different browser
Clear cache and cookies for https://ml.azure.com, then retry. If possible, test in a completely different browser (for example Edge if you were using Chrome) to isolate whether it's browser specific.
5. Try opening the notebook in Jupyter or VS Code Web instead of the Studio editor
From the notebook toolbar, use the dropdown next to the editor selector and try Jupyter or VS Code (Web) instead of the default Studio notebook editor. This helps identify whether the issue is specific to the Studio notebook rendering engine itself.
6. Check for network or proxy blocking
If you're on a corporate network, VPN, or behind a proxy, confirm that your firewall isn't blocking the storage account or Azure ML dependent URLs used to load notebook content. Since you reproduced this on a second organization's account too, this is less likely, but still worth ruling out if both environments share the same network path (for example, same corporate VPN or DNS).
7. Open a support ticket if it persists
If none of the above resolves it, this needs backend investigation. Open a ticket through https://aka.ms/azuresupport with Service set to Azure Machine Learning, and include your workspace region, browser and version, and whether Jupyter/VS Code Web modes also hang.
If this answer helps you kindly accept the answer which will help others who have similar questions.
Best Regards,
Jerald Felix.