Clicking through endless installation wizards is a massive waste of time when deploying software across enterprise networks, making automated deployments essential. Deploying Azure Developer CLI to multiple machines no longer requires tedious manual configuration. IT administrators can effortlessly streamline this rollout using tools like Microsoft Intune, SCCM, or PDQ by executing the verified silent install command. This ensures a consistent, background machine-level setup that requires administrative privileges while seamlessly integrating into your existing software packaging and detection workflows.
Quick snapshot: Silently install Azure Developer CLI on Windows
Run in an elevated Command Prompt or PowerShell:
msiexec /i "Microsoft.Azd.1.34.300.X64.msi" /qn REBOOT=ReallySuppress INSTALLEDBY="winget" MSIINSTALLPERUSER=0Overview
| Application | Azure Developer CLI |
|---|---|
| Version | 1.25.700 |
| Publisher | Microsoft Corporation |
| Installer type | MSI |
| Install scope | System / machine-wide |
| Requires admin | Yes |
| Silent install | Available |
| Silent uninstall | Available |
| Detection method | MSI product code |
| Installer file | Microsoft.Azd.1.34.300.X64.msi |
Silent install steps
Run any one of the methods below to install Azure Developer 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.Azd.1.34.300.X64.msi) to a local folder, for exampleC:\Installers.
- Open Command Prompt as Administrator:Press Start→Type
cmd→Right-click Command Prompt→Choose Run as administrator
- Switch to the installer folder, then run the silent install command:
msiexec /i "Microsoft.Azd.1.34.300.X64.msi" /qn REBOOT=ReallySuppress INSTALLEDBY="winget" MSIINSTALLPERUSER=0C:\> cd /d "C:\Installers"C:\Installers> msiexec /i "Microsoft.Azd.1.34.300.X64.msi" /qn REBOOT=ReallySuppress INSTALLEDBY="winget" MSIINSTALLPERUSER=0Installing Azure Developer CLI 1.25.700…Installation complete — exit code 0.C:\Installers> ▋
Method 2: Install with PowerShell
Run the same silent install through PowerShell (elevated).
- Download or stage the installer (
Microsoft.Azd.1.34.300.X64.msi) to a local folder, for exampleC:\Installers.
- Open PowerShell as Administrator — right-click Start (or press Win+X), then:
- On Windows 10: choose Windows PowerShell (Admin).
- On Windows 11: choose Terminal (Admin) — it opens Windows Terminal running PowerShell.
- Run the command:
Start-Process -FilePath "msiexec.exe" -ArgumentList '/i "Microsoft.Azd.1.34.300.X64.msi" /qn REBOOT=ReallySuppress INSTALLEDBY="winget" MSIINSTALLPERUSER=0' -Wait -NoNewWindowPS C:\> Set-Location 'C:\Installers'PS C:\Installers> Start-Process -FilePath "msiexec.exe" -ArgumentList '/i "Microsoft.Azd.1.34.300.X64.msi" /qn REBOOT=ReallySuppress INSTALLEDBY="winget" MSIINSTALLPERUSER=0' -Wait -NoNewWindowInstalling Azure Developer CLI 1.25.700…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 | Administrator privileges required |
|---|---|
| Install scope | Machine |
| Restart behavior | No restart expected |
Detection Rules
Configure your deployment tool with the detection rule below to confirm a successful install of Azure Developer CLI. The same rule work for Microsoft Intune, SCCM, PDQ Deploy, and most RMM platforms — just paste the values into the matching fields.
MSI product code detection
| Product code | {253C20C0-1CC3-43FD-8362-2A9489070FD9} |
|---|
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 Azure Developer CLI is detected and 1 otherwise.
$Code = '{253C20C0-1CC3-43FD-8362-2A9489070FD9}'
$Paths = @(
"HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\$Code",
"HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$Code"
)
if ($Paths | Where-Object { Test-Path $_ }) { exit 0 }
exit 1Silent Uninstall Steps
Remove Azure Developer 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 as Administrator.
- Run the silent uninstall command.
msiexec /x "{253C20C0-1CC3-43FD-8362-2A9489070FD9}" /qn REBOOT=ReallySuppressMethod 2: Uninstall with PowerShell
Run the same silent uninstall command through PowerShell.
- Open PowerShell as Administrator.
- Run the silent uninstall command.
Start-Process -FilePath "msiexec.exe" -ArgumentList '/x "{253C20C0-1CC3-43FD-8362-2A9489070FD9}" /qn REBOOT=ReallySuppress' -Wait -NoNewWindowDeployment Examples
Drop one of the snippets below into your deployment tool, Group Policy, or scheduled task. Each script wraps the silent install command for Azure Developer CLI as a batch file or PowerShell script — copy, save, and run.
Batch file example
Save the following content as install-azure-developer-cli.bat in the same folder as the installer.
@echo off
cd /d "%~dp0"
msiexec /i "Microsoft.Azd.1.34.300.X64.msi" /qn REBOOT=ReallySuppress INSTALLEDBY="winget" MSIINSTALLPERUSER=0
exit /b %errorlevel%PowerShell script example
Save the following content as install-azure-developer-cli.ps1 in the same folder as the installer.
Set-Location -Path $PSScriptRoot
$Installer = 'Microsoft.Azd.1.34.300.X64.msi'
& msiexec.exe /i $Installer /qn REBOOT=ReallySuppress INSTALLEDBY="winget" MSIINSTALLPERUSER=0
exit $LASTEXITCODEFrequently asked questions
Can I silently install Azure Developer CLI on Windows?
Do I need administrator privileges to install Azure Developer CLI?
Will installing Azure Developer CLI restart the computer?
REBOOT=ReallySuppress to block any automated system restarts during deployment.How do I verify Azure Developer CLI installed successfully?
How do I silently uninstall Azure Developer CLI?
msiexec /x along with the MSI product code and the /qn REBOOT=ReallySuppress parameters.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 as administrator | Make sure Command Prompt or PowerShell is opened as Administrator. This installer writes to a machine-wide location and will fail silently without elevated permissions. |
|---|---|
| Verify the installer file name | Confirm that the installer file name matches the command shown in this guide: Microsoft.Azd.1.34.300.X64.msi. |
| 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 (add /L*v install.log to msiexec for a verbose MSI 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. |