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
Bias Types:
⚠️
windows_first
⚠️
powershell_heavy
⚠️
windows_tools
Summary:
The documentation page demonstrates a subtle Windows bias in the 'Next steps' section, where Azure PowerShell and Visual Studio Code (a Microsoft product) are mentioned as primary tools for deploying and authoring Bicep files. Azure CLI is mentioned, but PowerShell is listed first, and there is no mention of Linux-native editors or deployment workflows. No explicit Linux examples or tools are highlighted, and the guidance assumes familiarity with Windows-centric tooling.
Recommendations:
- List Azure CLI before Azure PowerShell when suggesting deployment tools, as Azure CLI is fully cross-platform.
- Explicitly mention that all Bicep examples and deployment steps work on Linux, macOS, and Windows.
- Include links or references to Linux-native editors (such as Vim, Emacs, or JetBrains IDEs) that support Bicep, if available.
- Provide a brief example of deploying a Bicep file using Azure CLI from a Linux shell (e.g., Bash), to demonstrate parity.
- Clarify that Visual Studio Code is available on Linux and macOS, or suggest alternative editors for those platforms.
Create pull request