Forum Discussion
Cannot connect kernel from VS Code
Hi tdevinda , Thank you for reaching out to the Microsoft Community Forum.
This may be due to Fabric VS Code extension not being fully updated to support remote kernel binding for runtime 1.3. The extension still relies on patterns from runtime 1.2, where local execution was viable, causing the current incompatibility. This is not user error but a tooling limitation.
Currently, Microsoft has not yet released full support for remote notebook execution through VS Code for runtime 1.3. This limitation has been noted across the community, and an update to the extension is expected, but no timeline has been published. Until then, the Fabric web UI remains the only fully supported environment for executing notebooks using runtime 1.3, as it correctly provisions and binds the remote compute kernel.
If you want to monitor progress or confirm when support is added, the best place to watch is the Microsoft Fabric release notes .
If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Hi,
For the current kernel version 1.3, the issue was never resolved. I am waiting till some stable fix comes for 1.3.
Even for a fresh install, the 1.3 kernel's notebooks try to find a conda environment in VS Code. I think the extension needs an update.
Hi tdevinda , Thank you for reaching out to the Microsoft Community Forum.
This may be due to Fabric VS Code extension not being fully updated to support remote kernel binding for runtime 1.3. The extension still relies on patterns from runtime 1.2, where local execution was viable, causing the current incompatibility. This is not user error but a tooling limitation.
Currently, Microsoft has not yet released full support for remote notebook execution through VS Code for runtime 1.3. This limitation has been noted across the community, and an update to the extension is expected, but no timeline has been published. Until then, the Fabric web UI remains the only fully supported environment for executing notebooks using runtime 1.3, as it correctly provisions and binds the remote compute kernel.
If you want to monitor progress or confirm when support is added, the best place to watch is the Microsoft Fabric release notes .
If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.