Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides deployment examples for both Azure CLI and Azure PowerShell, but the PowerShell example uses Windows-style file paths (C:\MyTemplates\...), and PowerShell is a Windows-centric tool. The Visual Studio tip references a Windows-only IDE. The PowerShell example and related notes appear after the CLI example, but Windows tools and patterns (PowerShell, Visual Studio) are mentioned without Linux equivalents or parity notes. There are no explicit Linux shell examples (e.g., Bash), and no mention of cross-platform editors or file path conventions.
Recommendations
- Add explicit Linux shell (Bash) examples for deploying templates, including file paths using forward slashes.
- Clarify that Azure CLI is cross-platform and show examples with Linux/macOS file paths.
- Mention cross-platform editors (e.g., VS Code) in addition to Visual Studio, and provide equivalent instructions for Linux/macOS users.
- Note that PowerShell Core is available cross-platform, and provide examples using PowerShell on Linux/macOS.
- Avoid using Windows-specific file paths in examples, or provide both Windows and Linux/macOS path formats.
Create Pull Request