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:
⚠️
powershell_heavy
⚠️
windows_tools
⚠️
missing_linux_example
Summary:
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell scripts for advanced resource identification (e.g., identifying Traffic Manager endpoints and retrieving both site properties and config values). There are no equivalent Bash, Azure CLI, or cross-platform script examples provided for Linux or Mac users. The documentation assumes access to and familiarity with PowerShell, which is traditionally a Windows-centric tool, although it is now available cross-platform. However, no Linux-native or Bash alternatives are mentioned, and PowerShell is referenced as the default scripting environment for automation tasks.
Recommendations:
- Provide equivalent Bash or Azure CLI script examples for all PowerShell scripts referenced, ensuring Linux and Mac users can perform the same tasks without needing PowerShell.
- When referencing scripts, clarify if they are cross-platform or provide explicit instructions for running them on Linux/Mac (e.g., using PowerShell Core).
- List Azure CLI and REST API options before or alongside PowerShell to avoid the impression that Windows tools are preferred or required.
- Where possible, use Azure CLI for automation examples, as it is natively cross-platform and familiar to both Windows and Linux users.
- Explicitly mention that PowerShell scripts can be run on Linux/Mac with PowerShell Core, or provide links to documentation on installing PowerShell on those platforms.
Create pull request