Even though bicep extension is there and installed not loading resources in VS studio

Question

Even though bicep extension is there and installed not loading resources in VS studio

Varma 1,620

I am expecting to see all resources like below ( which is from another source)

User's image

you can see bicep extension is installed but i am not seeing loading resources in my case and in my visual studio

User's image

I am not finding it , please see below screenshot

User's image

Awaiting for your response.

Senthil kumar 1,280 Reputation points

2026-05-10T08:51:17.6+00:00
Hi Varma,

Make sure reload your vs then try again. reload option :
ctrl+shift+p -> type reload window.

suppose not working close the vs and open again.

try this command on your CLI winget install --id Microsoft.Bicep --source winget
Varma 1,620 Reputation points

2026-05-10T08:51:28.52+00:00

Root cause: Old VS Code (1.86.2) and outdated Bicep extension (0.34.44) were incompatible with the newer Bicep CLI, so the Bicep language server/IntelliSense never loaded.

Fix: Updated VS Code, upgraded the Microsoft Bicep extension to 0.43.8, removed conflicting Bicep extensions, and restarted the VS Code extension host.
Varma 1,620 Reputation points

2026-05-10T08:51:58.8366667+00:00

HI Senthil

I have fixed the issue from my end:

Root cause: Old VS Code (1.86.2) and outdated Bicep extension (0.34.44) were incompatible with the newer Bicep CLI, so the Bicep language server/IntelliSense never loaded.

Fix: Updated VS Code, upgraded the Microsoft Bicep extension to 0.43.8, removed conflicting Bicep extensions, and restarted the VS Code extension host.
Senthil kumar 1,280 Reputation points

2026-05-10T08:54:42.5666667+00:00

Thanks for the update.
Siva shunmugam Nadessin 10,895 Reputation points Microsoft External Staff Moderator

2026-05-11T12:56:38.2133333+00:00

Thanks for sharing Varma,

Below resolution helped in resolving the issue.

Root Cause: The issue occurred because the installed version of VS Code (1.86.2) and the older Bicep extension (0.34.44) were not compatible with the updated Bicep CLI. As a result, the Bicep language server and IntelliSense features failed to initialize.

Resolution: Upgraded VS Code to the latest version, installed the newer Microsoft Bicep extension (0.43.8), removed any conflicting or duplicate Bicep extensions, and restarted the VS Code extension host to apply the changes.

1 answer

Your answer

Senthil kumar 1,280 Reputation points

2026-05-10T08:51:17.6+00:00

Hi Varma,

Make sure reload your vs then try again. reload option :
ctrl+shift+p -> type reload window.

suppose not working close the vs and open again.

try this command on your CLI winget install --id Microsoft.Bicep --source winget
Varma 1,620 Reputation points

2026-05-10T08:51:28.52+00:00

Root cause: Old VS Code (1.86.2) and outdated Bicep extension (0.34.44) were incompatible with the newer Bicep CLI, so the Bicep language server/IntelliSense never loaded.

Fix: Updated VS Code, upgraded the Microsoft Bicep extension to 0.43.8, removed conflicting Bicep extensions, and restarted the VS Code extension host.
Varma 1,620 Reputation points

2026-05-10T08:51:58.8366667+00:00

HI Senthil

I have fixed the issue from my end:

Root cause: Old VS Code (1.86.2) and outdated Bicep extension (0.34.44) were incompatible with the newer Bicep CLI, so the Bicep language server/IntelliSense never loaded.

Fix: Updated VS Code, upgraded the Microsoft Bicep extension to 0.43.8, removed conflicting Bicep extensions, and restarted the VS Code extension host.
Senthil kumar 1,280 Reputation points

2026-05-10T08:54:42.5666667+00:00

Thanks for the update.
Siva shunmugam Nadessin 10,895 Reputation points Microsoft External Staff Moderator

2026-05-11T12:56:38.2133333+00:00

Thanks for sharing Varma,

Below resolution helped in resolving the issue.

Root Cause: The issue occurred because the installed version of VS Code (1.86.2) and the older Bicep extension (0.34.44) were not compatible with the updated Bicep CLI. As a result, the Bicep language server and IntelliSense features failed to initialize.

Resolution: Upgraded VS Code to the latest version, installed the newer Microsoft Bicep extension (0.43.8), removed any conflicting or duplicate Bicep extensions, and restarted the VS Code extension host to apply the changes.

Answer 1

Resource completions in Bicep come from the Bicep language server that is part of the Bicep extension in Visual Studio Code or Visual Studio. The CLI (bicep command) is not required for IntelliSense, but the extension itself must be correctly installed and active for .bicep files.

Based on the context:

Verify that the Bicep extension is installed and enabled in the correct editor:
- For Visual Studio Code, install the Bicep extension from the marketplace as described in the Bicep tools installation guidance. After installation, open a file with the .bicep extension and confirm that the language mode in the lower-right corner shows Bicep.
- For Visual Studio (the full IDE), install the Bicep extension for Visual Studio from the Visual Studio Marketplace. Then open a .bicep file in a supported project.
Confirm that the file is recognized as Bicep:
- Open main.bicep.
- Check the status bar language mode. It must be Bicep. If it is not, change it to Bicep so that the extension’s language server is used and completions can load.
Check Bicep extension settings:
- In Visual Studio Code: File → Preferences → Settings → Extensions → Bicep.
- Ensure the extension is not disabled and that features such as completions are not turned off.
If the extension still does not provide completions, reinstall or repair it:
- Disable and re-enable the Bicep extension.
- If needed, uninstall and reinstall it from the marketplace.
The bicep CLI error in the terminal (bicep : The term 'bicep' is not recognized) only indicates that the standalone Bicep CLI is not installed on the machine. To use the CLI, install Bicep as documented in the Bicep tools installation article. This is optional for IntelliSense but required if running bicep commands directly from the terminal.

After these steps, opening a .bicep file in an editor where the Bicep extension is active should show resource type completions when defining a resource.

References:

Install Bicep tools