Eliminating manual setup prompts ensures total deployment consistency across your entire developer infrastructure. Deploying Bicep CLI silently to user workspaces saves valuable administrative time and keeps developer environments standardized without disrupting active sessions. This practical guide walks IT administrators through preparing the package for modern endpoint management platforms like Intune, SCCM, and PDQ. By utilizing the verified silent install command alongside the required detection rule, you can automate this user-scope Microsoft Corporation application efficiently while maintaining a seamless, zero-touch experience for every end user.
Quick snapshot: Silently install Bicep CLI on Windows
Run in Command Prompt or PowerShell:
Microsoft.Bicep.0.47.16.X64.exe /SP- /SUPPRESSMSGBOXES /VERYSILENT /NORESTARTOverview
| Application | Bicep CLI |
|---|---|
| Version | 0.44.1 |
| Publisher | Microsoft Corporation |
| Installer type | Inno Setup |
| Install scope | User |
| Requires admin | No |
| Silent install | Available |
| Silent uninstall | Available |
| Detection method | Registry |
| Installer file | Microsoft.Bicep.0.47.16.X64.exe |
Silent install steps
Run any one of the methods below to install Bicep CLI silently with zero user interaction. Command Prompt and PowerShell produce the same result — use whichever fits your deployment workflow.
Method 1: Install with Command Prompt
- Download or stage the installer (
Microsoft.Bicep.0.47.16.X64.exe) to a local folder, for exampleC:\Installers.
- Open Command Prompt — press Start (or the Windows key), type
cmdand press Enter.
- Switch to the installer folder, then run the silent install command:
Microsoft.Bicep.0.47.16.X64.exe /SP- /SUPPRESSMSGBOXES /VERYSILENT /NORESTARTC:\> cd /d "C:\Installers"C:\Installers> Microsoft.Bicep.0.47.16.X64.exe /SP- /SUPPRESSMSGBOXES /VERYSILENT /NORESTARTInstalling Bicep CLI 0.44.1…Installation complete — exit code 0.C:\Installers> ▋
Method 2: Install with PowerShell
Run the same silent install through PowerShell.
- Download or stage the installer (
Microsoft.Bicep.0.47.16.X64.exe) to a local folder, for exampleC:\Installers.
- Open PowerShell — press Start (or the Windows key), type
powershelland press Enter.
- Run the command:
Start-Process -FilePath Microsoft.Bicep.0.47.16.X64.exe -ArgumentList '/SP- /SUPPRESSMSGBOXES /VERYSILENT /NORESTART' -WaitPS C:\> Set-Location 'C:\Installers'PS C:\Installers> Start-Process -FilePath Microsoft.Bicep.0.47.16.X64.exe -ArgumentList '/SP- /SUPPRESSMSGBOXES /VERYSILENT /NORESTART' -WaitInstalling Bicep CLI 0.44.1…Installation complete — exit code 0.PS C:\Installers> ▋
Deployment Notes
Key facts to confirm before rolling this out to production machines — permissions required, scope of install, and reboot behavior.
| Requirement | No administrator privileges required |
|---|---|
| Install scope | User |
| Restart behavior | No restart expected |
Detection Rules
Configure your deployment tool with the detection rule below to confirm a successful install of Bicep CLI. The same rule work for Microsoft Intune, SCCM, PDQ Deploy, and most RMM platforms — just paste the values into the matching fields.
Registry detection
| Key path | HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall\{7EF9DE63-59B1-4325-955A-937F3E0A4EA8}_is1 |
|---|---|
| Value name | DisplayVersion |
| Expected version | 0.47.16.16243 |
PowerShell detection script
Prefer a script-based check? Use this as a custom detection script in Microsoft Intune (or any tool that supports detection scripts). It exits 0 when Bicep CLI is detected and 1 otherwise.
$Key = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\{7EF9DE63-59B1-4325-955A-937F3E0A4EA8}_is1'
$Value = (Get-ItemProperty -Path $Key -Name 'DisplayVersion' -ErrorAction SilentlyContinue).'DisplayVersion'
if ($Value -eq '0.47.16.16243') { exit 0 }
exit 1Silent Uninstall Steps
Remove Bicep CLI silently from one machine or your entire fleet. The commands below uninstall without prompts and suppress automatic reboots so you control the timing.
Method 1: Uninstall with Command Prompt
Run the uninstall command from an elevated Command Prompt.
- Open Command Prompt.
- Run the silent uninstall command.
unins000.exe /SP- /SUPPRESSMSGBOXES /VERYSILENT /NORESTARTMethod 2: Uninstall with PowerShell
Run the same silent uninstall command through PowerShell.
- Open PowerShell.
- Run the silent uninstall command.
Start-Process -FilePath unins000.exe -ArgumentList '/SP- /SUPPRESSMSGBOXES /VERYSILENT /NORESTART' -WaitDeployment Examples
Drop one of the snippets below into your deployment tool, Group Policy, or scheduled task. Each script wraps the silent install command for Bicep CLI as a batch file or PowerShell script — copy, save, and run.
Batch file example
Save the following content as install-bicep-cli.bat in the same folder as the installer.
@echo off
cd /d "%~dp0"
Microsoft.Bicep.0.47.16.X64.exe /SP- /SUPPRESSMSGBOXES /VERYSILENT /NORESTART
exit /b %errorlevel%PowerShell script example
Save the following content as install-bicep-cli.ps1 in the same folder as the installer.
Set-Location -Path $PSScriptRoot
$Installer = 'Microsoft.Bicep.0.47.16.X64.exe'
& $Installer /SP- /SUPPRESSMSGBOXES /VERYSILENT /NORESTART
exit $LASTEXITCODEFrequently asked questions
Can I silently install Bicep CLI on Windows?
Do I need administrator privileges to install Bicep CLI?
Will installing Bicep CLI restart the computer?
How do I verify Bicep CLI installed successfully?
How do I silently uninstall Bicep CLI?
Which deployment tools support these commands?
Troubleshooting
If the install fails, exits with a non-zero code, or leaves no trace on the target machine, work through the checks below. Most issues come down to permissions, paths, or exit code handling.
| Run in the right context | Bicep CLI installs into the current user profile, so run the command as the logged-in user — no elevation required. |
|---|---|
| Verify the installer file name | Confirm that the installer file name matches the command shown in this guide: Microsoft.Bicep.0.47.16.X64.exe. |
| Run from the correct folder | Run the command from the folder that contains the installer file. For batch or PowerShell deployments, place the script and installer in the same folder. |
| Check exit codes | If the installer returns a non-zero exit code, review the installer log or your deployment tool's logs. Some packages use additional success exit codes. |
| Restart if required | If the application does not appear immediately after installation, sign out and sign back in, or restart the device — this refreshes Start menu shortcuts, file associations, and Path entries written by the installer. |
| Validate detection rules | If your deployment tool reports the app as not installed, verify that the detection rule matches the installed version, MSI product code, registry key, or file path. Use the Detection Rules section above to confirm whether the application was installed successfully. |