You must manually install for any use other than Azure CLI. The following methods install the Bicep CLI and add it to your PATH. To check your Bicep CLI version, run: bicep -version When you manually install the Bicep CLI, run the Bicep commands with the bicep syntax, instead of the az bicep syntax for Azure CLI. Azure PowerShell deployments fail if you haven't manually installed the Bicep CLI. The self-contained instance of the Bicep CLI installed by Azure CLI isn't available to PowerShell commands.

To upgrade to the latest version, use: az bicep upgrade To validate your Bicep CLI installation, use: az bicep version

To verify your current version, run: az -version You must have Azure CLI version 2.20.0 or later installed. Azure CLI automatically installs the Bicep CLI when a command is executed that needs it. When you use Azure CLI with Bicep, you have everything you need to deploy and decompile Bicep files. For more information, see Deploy Bicep files from Visual Studio Code. You can deploy your Bicep files directly from the VS Code editor. If you get an error during installation, see Troubleshoot Bicep installation. You should see the language mode in the lower right corner change to Bicep. To verify you've installed the extension, open any file with the. To install the extension, search for bicep in the Extensions tab or in the Visual Studio marketplace. The extension helps you create and validate Bicep files. Visual Studio Code with the Bicep extension provides language support and resource autocompletion. Visual Studio Code - If you don't already have Visual Studio Code, install it.īicep extension for Visual Studio Code. To create Bicep files, you need a good Bicep editor. To author and deploy Bicep files, we recommend any of the following options: Tasks

Let's make sure your environment is set up for working with Bicep files.

Homebrew install notepad++