Deploy Bicep CLI to Microsoft Intune
Microsoft CorporationWindowsversion 0.48.1, 5 October 2026
Bicep CLI is in the PatchBee catalog as a Windows app from Microsoft Corporation, synced from the Windows Package Manager community repository (winget). Pick it in the App Library and PatchBee writes the deployment plan below, builds the package, publishes it to your Intune tenant and assigns it to the Entra groups you choose. New versions then follow through your update rings.
Install from the command line
winget install --id Microsoft.Bicep -e --silentPatchBee runs the same silent install of Bicep CLI for you in Intune: the installer winget points at, verified, packaged with the switches and detection rule below, and published to your tenant.
The plan PatchBee writes
Bicep CLI as an Intune app
The standard form for a Inno Setup (x64, per machine). The real plan is generated from the installer when you package, and shown in full before anything is published; every field can be changed.
- Intune app type
- Windows app (Win32), .intunewin
- Install
- "BicepCLI.exe" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-
- Uninstall
- "unins000.exe" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART
- Detection
- Registry: the Inno Setup uninstall key. Uninstall key {7EF9DE63-59B1-4325-955A-937F3E0A4EA8}_is1, DisplayVersion 0.48.1 or newer.
- Requirements
- x64, ARM64 · per machine
Why these values: silent install switches and detection rules, explained.
Installers in version 0.48.1
| Architecture | Type | Scope | Hash |
|---|---|---|---|
| x64 | Portable executable | scope decided at plan time | SHA-256 published |
| x64 | Inno Setup | per machine | SHA-256 published |
| ARM64 | Portable executable | scope decided at plan time | SHA-256 published |
PatchBee downloads the installer from the publisher's own URL and verifies its SHA-256 against the catalog before packaging. "None published" means the source carries no hash for this download, so that check has nothing to compare against; packaging still works.
About Bicep CLI
Bicep is a Domain Specific Language (DSL) for deploying Azure resources declaratively. It aims to drastically simplify the authoring experience with a cleaner syntax, improved type safety, and better support for modularity and code re-use. Bicep is a transparent abstraction over ARM and ARM templates, which means anything that can be done in an ARM Template can be done in Bicep (outside of temporary known limitations). All resource types, apiVersions, and properties that are valid in an ARM template are equally valid in Bicep on day one (Note: even if Bicep warns that type information is not available for a resource, it can still be deployed).
Bicep code is transpiled to standard ARM Template JSON files, which effectively treats the ARM Template as an Intermediate Language (IL).
- Publisher
- Microsoft Corporation
- Homepage
- github.com/Azure/bicep
- License
- MIT
- Source
- winget · Microsoft.Bicep
- Versions in catalog
- 72
How this becomes an app in your tenant
Sign in with your Microsoft work account and connect your Intune tenant once. Find Bicep CLI in the App Library, open its plan (the commands, detection rule and requirements above, editable) and publish: PatchBee downloads and verifies the installer, builds the package, creates the Intune app and assigns your groups. When Microsoft Corporation ships a new version, PatchBee detects it and rolls it out through your rings, with supersedence and rollback.
Read the step-by-step guideMore Windows apps
Catalog data as of 11 October 2026, from the Windows Package Manager community repository (winget). The product re-reads the source every night and plans against the live catalog, so the version here may already be one behind. Nothing is published to a tenant without an administrator approving the plan.