microsoft
Connections to Microsoft/Azure are unstable in this insider release
Type: Bug
I've just updated to the latest insider release and I'm asked to connect to Microsoft for the c# dev kit, but the extension is working fine. And the Azure extension is now in trouble, being busy all the time to fetch some data?
VS Code version: Code - Insiders 1.99.0-insider (14324bbbc2cca2ddb998d6ab577f02efe00efe0c, 2025-03-06T05:04:31.056Z) OS version: Darwin x64 24.3.0 Modes:
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (4 x 3200) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: unavailable_off raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | 10, 16, 10 |
| Memory (System) | 16.00GB (0.05GB free) |
| Process Argv | --crash-reporter-id 9b677732-85f0-4cb7-8a28-6c54b6257178 |
| Screen Reader | no |
| VM | 0% |
Extensions (23)
| Extension | Author (truncated) | Version |
|---|---|---|
| azurite | Azu | 3.34.0 |
| xml | Dot | 2.5.1 |
| gitlens | eam | 16.3.2 |
| copilot | Git | 1.277.1411 |
| copilot-chat | Git | 0.26.2025030601 |
| vscode-azure-github-copilot | ms- | 0.3.153 |
| vscode-azureappservice | ms- | 0.25.4 |
| vscode-azurefunctions | ms- | 1.16.2 |
| vscode-azureresourcegroups | ms- | 0.10.7 |
| vscode-docker | ms- | 1.29.4 |
| vscode-language-pack-fr | MS- | 1.98.2025030509 |
| csdevkit | ms- | 1.17.48 |
| csharp | ms- | 2.63.32 |
| dotnet-maui | ms- | 1.9.15 |
| vscode-dotnet-runtime | ms- | 2.2.8 |
| vscodeintellicode-csharp | ms- | 2.2.3 |
| data-workspace-vscode | ms- | 0.6.0 |
| mssql | ms- | 1.29.0 |
| sql-bindings-vscode | ms- | 0.4.0 |
| sql-database-projects-vscode | ms- | 1.4.6 |
| remote-containers | ms- | 0.402.0 |
| auto-tfs | nik | 1.3.8 |
| markdown-all-in-one | yzh | 3.6.2 |
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256197
pythonvspyt551:31249597
vscod805cf:30301675
py29gd2263:31024238
c4g48928:30535728
962ge761:30841072
dsvsc014:30777825
dsvsc015:30821418
h48ei257:31000450
pythontbext0:30879054
cppperfnew:30980852
pythonait:30973460
dwnewjupytercf:31046870
nativerepl1:31134653
pythonrstrctxt:31093868
nativeloc1:31118317
e80f6927:31120813
iacca1:31150324
notype1:31143044
dwcopilot:31158714
c3hdf307:31184662
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
hdaa2157:31222309
copilot_t_ci:31222730
f27dg485:31233432
g012b348:31231168
jda6j935:31233686
copilothoveron:31247701
pythoneinst12:31251391
bgtreat:31252123
fh1c7952:31247580
With today's release, the connection problem is gone but the main problem with the azure extension remains. The Azure extension not only is busy permanently, but it doesn't work as expected for what I need, deployments to App Servcices/Function App.
Everything works fine under VS-Code non insider, though.
Can you follow these steps so that we can get more information on what's going on?
Enable trace logging
- Open the Command Palette (cmd/ctrl+shift+p)
- Run the
Developer: Set Log Level...command - To the right of
Trace, click the double check mark button. ✔️ ✔️ (enables trace logging as the default)
Now wait for the issue to happen or trigger it...
Getting the logs
- Open the Command Palette again (cmd/ctrl+shift+p)
- Run the
Output: Show Output Channels...command - Choose
Microsoft Authentication - Copy and paste the contents of what opens in the panel in this issue (if the contents is too large, you may need to upload it as a file)
Reverting trace logging (optional)
When we're done here, to revert the log level back to the default:
- Open the Command Palette
- Run the
Developer: Set Log Level...command - To the right of
Info, click the double check mark button. ✔️ ✔️ (to set the default back to info)
AzureExtensionNotWorking.txt.zip
The output is updating indefinitely.
Hope that helps. Kind regards.
Nice find. I've got a fix out for this. The culprit is how the C# Dev Kit asks for auth... they do something that's technically valid... but weird. If you disable that extension, then this will stop looping forever. Monday will have the fix.