Document Details
Install
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Detected Bias Types
windows_first
windows_tools
powershell_heavy
Summary
The documentation shows moderate Windows bias. Visual Studio (Windows-only) is presented as a primary authoring tool alongside Visual Studio Code, and PowerShell/Windows installer/Windows package managers (Chocolatey, Winget) are described in greater detail and with more installation options than their Linux/macOS equivalents. Windows-specific tools and patterns (e.g., PowerShell scripts, registry edits, Windows environment variables) are used and described in depth, while Linux and macOS installation instructions are more concise and less varied. In several sections, Windows options are listed before Linux/macOS, and PowerShell is the only scripting language shown for manual installation on Windows.
Recommendations
- Present Linux and macOS installation options before or alongside Windows options in all lists and tables to avoid 'windows_first' ordering.
- Expand Linux and macOS installation sections to include more package manager options (e.g., apt, yum, snap for Linux), mirroring the variety offered for Windows (e.g., Chocolatey, Winget).
- Provide Bash or shell script equivalents for all PowerShell examples, especially for manual installation and PATH modification.
- Where possible, use cross-platform language and avoid Windows-specific terminology (e.g., use 'home directory' instead of '%UserProfile%').
- Highlight cross-platform editors and tools (e.g., Visual Studio Code) before Windows-only tools (e.g., Visual Studio).
- Ensure troubleshooting and advanced sections include Linux/macOS-specific guidance, not just Windows/PowerShell.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-12 00:00 | #99 | completed |
Biased
|
| 2026-01-11 06:20 | #98 | completed |
Biased
|
| 2026-01-10 00:00 | #92 | completed |
 Clean
|
| 2026-01-09 00:00 | #87 | cancelled |
Clean
|
| 2026-01-06 22:28 | #78 | completed |
Clean
|
| 2025-12-29 18:00 | #48 | cancelled |
Biased
|
| 2025-12-15 00:00 | #7 | completed |
Clean
|
| 2025-12-14 05:05 | #6 | completed |
Clean
|
Flagged Code Snippets
choco install bicep
winget install -e --id Microsoft.Bicep
# Create the install folder
$installPath = "$env:USERPROFILE\.bicep"
$installDir = New-Item -ItemType Directory -Path $installPath -Force
$installDir.Attributes += 'Hidden'
# Fetch the latest Bicep CLI binary
(New-Object Net.WebClient).DownloadFile("https://github.com/Azure/bicep/releases/latest/download/bicep-win-x64.exe", "$installPath\bicep.exe")
# Add bicep to your PATH
$currentPath = (Get-Item -path "HKCU:\Environment" ).GetValue('Path', '', 'DoNotExpandEnvironmentNames')
if (-not $currentPath.Contains("%USERPROFILE%\.bicep")) { setx PATH ($currentPath + ";%USERPROFILE%\.bicep") }
if (-not $env:path.Contains($installPath)) { $env:path += ";$installPath" }
# Verify you can now access the 'bicep' command.
bicep --help
# Done!