Azure Resource Manager
504
Total Pages
312
Linux-Friendly Pages
192
Pages with Bias
38.1%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
1281 issues found
Showing 101-125 of 1281 flagged pages
Azure Resource Manager
Deploy ARM template with SAS token - Azure Resource Manager | Microsoft Docs
...ce-manager/templates/secure-template-with-sas-token.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are consistently presented before Azure CLI examples, and file paths in examples use Windows-style (e.g., c:\Templates\azuredeploy.json). There is no explicit mention of Linux or cross-platform considerations, and the CLI section only briefly notes Bash compatibility without providing parity for other shells or platforms. The overall structure and examples favor Windows users and workflows.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to balance platform representation.
- Use platform-neutral file paths in examples (e.g., ./Templates/azuredeploy.json) or provide both Windows and Linux path examples.
- Explicitly mention Linux/macOS compatibility for Azure CLI commands, and provide notes or examples for common shell differences (e.g., zsh, fish).
- Add a section or callout for Linux users, highlighting any differences or considerations when using Azure CLI or PowerShell Core on Linux.
- Ensure that references to tools and workflows are not Windows-centric, and provide links to cross-platform documentation where relevant.
Create Pull Request
Azure Resource Manager
Create a template spec with linked templates
...urce-manager/templates/template-specs-create-linked.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits a Windows bias by consistently using Windows-style file paths (e.g., c:\Templates\...), presenting PowerShell examples before Azure CLI, and referencing Windows-specific issues (e.g., variable assignment in Windows PowerShell). There are no explicit Linux shell examples, and the directory creation instructions assume Windows conventions.
Recommendations
- Provide Linux/macOS file path examples alongside Windows paths (e.g., /home/user/Templates/linkedTS/azuredeploy.json).
- Include bash or shell commands for directory creation and file management, not just implicit instructions.
- Alternate the order of PowerShell and CLI examples, or present them side-by-side to avoid Windows-first presentation.
- Explicitly mention cross-platform compatibility and note any differences in behavior between Windows and Linux environments.
- Add troubleshooting notes for Linux/macOS users where relevant, not just Windows PowerShell issues.
Azure Resource Manager
Azure Resource Manager template specs
...les/azure-resource-manager/templates/template-specs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI throughout, but PowerShell is often listed first in code tabs and command explanations. The documentation refers to 'PowerShell script' as a standard deployment process, and repeatedly mentions Azure PowerShell as a primary tool. There is no explicit mention of Linux shells (e.g., Bash) or cross-platform scripting patterns, and no guidance is given for Linux-specific environments or considerations. All command-line examples are either PowerShell or Azure CLI, with PowerShell generally presented first.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or default to CLI first, as Azure CLI is cross-platform.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., Bash, zsh).
- Add notes or sections for Linux users, such as how to install Azure CLI and run commands in Bash.
- Avoid referring to 'PowerShell script' as the default automation pattern; mention Bash scripts and other cross-platform options.
- Where possible, include screenshots or walkthroughs from Linux terminals, not just Windows/PowerShell.
- Clarify that template specs and related tooling are fully supported on Linux and macOS, not just Windows.
Azure Resource Manager
Tutorial - Create and deploy template
...r/templates/template-tutorial-create-first-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools and patterns (PowerShell, Windows paths, screenshots) are presented either exclusively or before their Linux equivalents. PowerShell is given equal or greater prominence than Azure CLI, and CLI examples are written for Bash but with notes about adapting for Windows. Installation instructions list Windows first, and there are no explicit Linux-specific workflow examples (e.g., using Linux editors, shell environments, or file paths). Screenshots and instructions assume a Windows-style environment, with no mention of Linux desktop equivalents.
Recommendations
- Ensure installation instructions for Azure CLI list Linux and macOS before or alongside Windows, not after.
- Provide explicit Linux workflow examples, including using Linux-native editors (e.g., Vim, nano, gedit) and Linux file paths.
- Include screenshots from Linux environments (e.g., Ubuntu desktop, GNOME Terminal) alongside Windows screenshots.
- Clarify that Visual Studio Code is cross-platform and mention alternatives for Linux users.
- Add notes or tabs for running Azure CLI commands in Linux shells (e.g., zsh, fish) and explain any differences in environment variables or file paths.
- Avoid assuming Windows-style file paths and explain how to adapt instructions for Linux/macOS file systems.
- Balance PowerShell and CLI coverage, and consider highlighting Azure CLI as the default for cross-platform scenarios.
Azure Resource Manager
Deploy VM extensions with template
...er/templates/template-tutorial-deploy-vm-extensions.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows. All examples use Windows VMs, PowerShell scripts, and Windows-specific tools (e.g., Install-WindowsFeature, powershell.exe). There is no mention of Linux VM extensions, Bash scripts, or Linux configuration patterns. The tutorial title and flow focus exclusively on Windows, with no Linux parity or alternative paths.
Recommendations
- Add parallel examples for deploying VM extensions to Linux VMs, including Bash scripts and Linux-specific configuration (e.g., installing Apache or Nginx).
- Include links to both Windows and Linux extension documentation at the start.
- Show how to use Custom Script Extension with Bash or Python scripts on Linux VMs.
- Provide a Linux quickstart template (e.g., 'Deploy a simple Linux VM') and walk through editing it.
- Demonstrate retrieving the public IP address using Azure CLI or Bash commands, not only PowerShell.
- Clarify in the introduction that the tutorial is Windows-specific, or broaden the scope to cover both platforms.
Azure Resource Manager
Template with dependent resources
...ate-tutorial-create-templates-with-dependent-resources.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively using a Windows VM template for the example, referencing RDP for VM verification (which is Windows-specific), and omitting any mention of Linux VM templates or SSH access. The deployment instructions do provide both Azure CLI (Bash) and PowerShell examples, but the core scenario is centered on Windows resources and tools, with no Linux equivalents or parity in the walkthrough.
Recommendations
- Include a parallel example using a Linux VM template (e.g., 'Deploy a simple Linux VM') and provide the corresponding template URL.
- Add instructions for verifying a Linux VM deployment using SSH, alongside the RDP instructions for Windows.
- Mention both Windows and Linux VM scenarios in the introduction and throughout the tutorial, making it clear that ARM templates can deploy either.
- Ensure that resource cleanup and verification steps are platform-neutral or provide both Windows and Linux options.
- Consider alternating or randomizing the order of PowerShell and CLI examples, or presenting them side-by-side, to avoid implicit prioritization.
Azure Resource Manager
Use Azure Key Vault in templates
...e-manager/templates/template-tutorial-use-key-vault.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All code examples for interacting with Azure Key Vault and deploying ARM templates use Azure PowerShell, with no equivalent Azure CLI or Bash examples. The tutorial centers on deploying a Windows VM, referencing Windows-specific password requirements and RDP for validation, while omitting Linux VM scenarios and SSH-based access. Windows tools and patterns (PowerShell, RDP, Windows VM templates) are mentioned exclusively and before any Linux alternatives, which are not covered at all.
Recommendations
- Provide Azure CLI and Bash examples alongside PowerShell scripts for all deployment and validation steps.
- Include a parallel tutorial for deploying a Linux VM, referencing Linux-specific password/SSH key requirements and validation via SSH.
- Reference both Windows and Linux VM quickstart templates, and clarify differences in secret usage for each.
- Offer instructions for connecting to Linux VMs (e.g., using SSH) and validating credentials stored in Key Vault.
- Ensure all tooling instructions (Cloud Shell, VS Code) mention parity for Linux users and environments.
Azure Resource Manager
Use template reference
.../templates/template-tutorial-use-template-reference.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. Visual Studio Code is required as the editor, which is cross-platform but often associated with Windows. The deployment section gives both PowerShell and Azure CLI (Bash) examples, but PowerShell is mentioned first and in more detail. There is no mention of Linux-native editors or workflows, and the file upload instructions reference GUI actions typical of Windows environments. There are no explicit Linux tool recommendations or parity in editor instructions.
Recommendations
- Include instructions for opening and editing the template using Linux-native editors (e.g., Vim, nano, gedit) alongside Visual Studio Code.
- Present Azure CLI (Bash) examples before or alongside PowerShell examples, rather than after.
- Clarify that Visual Studio Code is available on Linux and macOS, or suggest alternatives.
- Add explicit instructions for file upload and verification using Linux command-line tools (e.g., scp, curl, ls, cat) outside of the Azure Cloud Shell GUI.
- Ensure that all steps (especially deployment and cleanup) have CLI-first examples, and avoid assuming a Windows GUI workflow.
Azure Resource Manager
Tutorial - Export and use Azure portal templates
...manager/templates/template-tutorial-export-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. While both Azure PowerShell and Azure CLI examples are provided for deploying templates, PowerShell is presented first, which can imply a Windows-first approach. The prerequisites mention both Azure PowerShell and Azure CLI, but do not provide explicit Linux-specific guidance or examples for installation or usage. There are no Linux shell (bash) examples for tasks like file manipulation or verification, and portal screenshots and instructions do not address platform differences. The clean-up and verification steps rely solely on the Azure portal, with no CLI or Linux shell alternatives.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI first to avoid Windows-first perception.
- Provide explicit instructions for installing and using Azure CLI on Linux, including bash shell examples for common tasks (e.g., verifying deployment, cleaning up resources).
- Include Linux-specific notes or screenshots where relevant, especially when discussing prerequisites and tool installation.
- Offer alternative verification and clean-up steps using Azure CLI commands, not just portal navigation.
- Clarify that both PowerShell and CLI are cross-platform, and highlight any platform-specific considerations.
Azure Resource Manager
Use condition in templates
...-manager/templates/template-tutorial-use-conditions.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by exclusively using a Windows VM template as the example, providing only PowerShell deployment scripts, and referencing Windows-centric resource names and patterns. There is no equivalent Linux VM example, nor are Azure CLI or Bash deployment scripts provided, despite mentioning Bash as an option in Cloud Shell.
Recommendations
- Include a parallel example using a Linux VM template (e.g., 'vm-simple-linux') alongside the Windows VM template.
- Provide Azure CLI and Bash script examples for template deployment, not just PowerShell.
- Reference both Windows and Linux resource templates in the 'Open a Quickstart template' section.
- Ensure instructions and screenshots show both PowerShell and Bash environments where relevant.
- Clarify that the tutorial applies to both Windows and Linux deployments, or specify if it is Windows-only.
Azure Resource Manager
SKU not available errors
...rce-manager/troubleshooting/error-sku-not-available.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation exhibits a moderate Windows bias. PowerShell examples and references (e.g., New-AzVM, Get-AzComputeResourceSku) are given equal prominence to Azure CLI, but Windows-specific tools and patterns (PowerShell scripting, Windows file paths in az rest output) are used without Linux equivalents. The REST example uses a Windows-style path (.\sku-list.json) for output, and PowerShell scripting is detailed extensively, while Bash or Linux shell scripting is absent. The ordering of tabs often places PowerShell before Portal or REST, and the initial error example uses New-AzVM before az vm create.
Recommendations
- Add Bash/Linux shell scripting examples for filtering and processing az vm list-skus output, similar to the PowerShell script provided.
- In REST examples, use cross-platform file paths (e.g., ./sku-list.json) or show both Windows and Linux variants.
- Ensure that CLI examples (az vm create, az vm list-skus) are presented before or alongside PowerShell examples, not after.
- Include notes or examples for Linux users, such as using jq for JSON processing, or grep/awk for filtering output.
- Balance the depth of scripting examples: if PowerShell scripts are shown, provide equivalent Bash scripts for Linux users.
Azure Resource Manager
Troubleshoot common Azure deployment errors
...ce-manager/troubleshooting/common-deployment-errors.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates some Windows bias. In the 'ResourceGroupNotFound' error, both Azure CLI and PowerShell are mentioned, but PowerShell (a Windows-centric tool) is listed second, which is positive. However, in other areas, Windows-specific links or examples are given before Linux equivalents (e.g., 'AllocationFailed' lists Linux first, but 'SubnetsNotInSameVnet' lists Windows first). There are also references to Windows-specific troubleshooting pages and tools, such as PowerShell, without always providing parity for Linux users. No explicit Linux command-line examples (e.g., bash) are given, and some links reference Windows VM documentation before Linux VM documentation.
Recommendations
- Ensure that Linux equivalents (e.g., bash, Azure CLI) are always mentioned alongside Windows tools like PowerShell, and consider listing Linux options first or alternating order.
- Add explicit Linux command-line examples where PowerShell is referenced, especially for common troubleshooting tasks.
- Where troubleshooting links are provided for Windows, ensure Linux links are also present and given equal prominence.
- Review all error mitigation steps to ensure Linux users are not required to infer steps from Windows-centric instructions.
- Consider a dedicated section or callout for cross-platform troubleshooting tips, highlighting differences and parity between Windows and Linux environments.
Azure Resource Manager
Enable debug logging
...source-manager/troubleshooting/enable-debug-logging.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Azure PowerShell (a Windows-centric tool) for enabling debug logging, explicitly stating that debug logging cannot be enabled via Azure CLI (the cross-platform tool). All example commands for enabling debug logging use PowerShell, with no Linux-native or Bash alternatives. The documentation refers to PowerShell cmdlets first and in more detail, while Azure CLI is only mentioned as a way to retrieve debug information, not to enable it. There are no examples or guidance for Linux users to achieve parity, and the documentation does not mention platform-specific limitations or workarounds for non-Windows environments.
Recommendations
- Provide clear guidance and examples for enabling debug logging using Azure CLI or other cross-platform tools, if possible.
- If debug logging truly cannot be enabled via Azure CLI, explicitly state this as a platform limitation and suggest alternative troubleshooting approaches for Linux/macOS users.
- Include Bash or shell script examples where possible, or clarify which steps are Windows-specific and which are cross-platform.
- Consider advocating for feature parity in Azure CLI to allow enabling debug logging, or link to feature requests/community discussions.
- Add a table or section summarizing platform/tool support for each operation (enable debug logging, retrieve logs, remove history) to help users quickly identify what is possible on their OS.
Azure Resource Manager
Create a troubleshooting template
...ger/troubleshooting/create-troubleshooting-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by mentioning Azure PowerShell (a Windows-centric tool) first when describing how to deploy the troubleshooting template, and by linking to PowerShell documentation before Azure CLI. There are no explicit Linux-specific examples or references to Linux shell usage, and no mention of platform differences or considerations for Linux users.
Recommendations
- Present Azure CLI examples before or alongside Azure PowerShell examples, as Azure CLI is cross-platform and preferred by many Linux users.
- Include explicit Linux shell usage examples (e.g., bash commands) for deploying ARM templates and Bicep files.
- Clarify that both Azure CLI and PowerShell are available on Windows, macOS, and Linux, and provide guidance for installation and usage on Linux.
- Avoid implying that PowerShell is the default or preferred method, and use neutral language when listing deployment options.
- Add troubleshooting steps or notes relevant to Linux environments, such as file path conventions or shell differences.
Azure Resource Manager
Deployment quota exceeded
...e-manager/troubleshooting/deployment-quota-exceeded.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI (Bash) and PowerShell examples for managing deployment quotas. However, the PowerShell section is given equal prominence, despite PowerShell being primarily a Windows tool (though it is cross-platform now). The Bash example is explicitly mentioned as requiring a Bash environment, but there is no mention of Windows Command Prompt equivalents or clarification for Linux users. The documentation does not provide explicit Linux-specific instructions or highlight platform differences, which may cause confusion for Linux users. The CLI examples assume Bash, which is standard on Linux but not on Windows by default.
Recommendations
- Explicitly state platform requirements for each example (e.g., Bash for Linux/macOS, PowerShell for Windows).
- Provide Windows Command Prompt equivalents for Azure CLI commands, or clarify that Bash is required on Windows (e.g., via WSL or Git Bash).
- Add notes or tabs for Linux-specific instructions, especially for scripting and environment setup.
- Clarify that PowerShell is available cross-platform, but is most commonly used on Windows, and provide guidance for Linux users who may not have PowerShell installed.
- Consider reordering examples or adding a 'Platform' note to ensure Linux users are not overlooked.
Azure Resource Manager
Resource not found errors
...re-resource-manager/troubleshooting/error-not-found.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell and Azure CLI together, but listing PowerShell first and providing a direct link to the Set-AzContext PowerShell cmdlet before the Azure CLI equivalent. No explicit Linux shell examples (e.g., Bash) are provided, and no mention is made of Linux-specific considerations or tools. The portal instructions are platform-neutral, but command-line guidance assumes familiarity with Windows tools and patterns.
Recommendations
- Alternate the order of PowerShell and Azure CLI references, or list Azure CLI first to balance platform representation.
- Provide explicit Bash/Linux shell examples for Azure CLI commands, including syntax and environment notes.
- Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Include troubleshooting steps or notes relevant to Linux users, such as verifying environment variables or shell context.
- Where possible, add links to Linux-specific documentation or guides for managing Azure resources.
Azure Resource Manager
Resource quota errors
...source-manager/troubleshooting/error-resource-quota.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides troubleshooting steps for resource quota errors in Azure, with command-line examples for both Azure CLI and PowerShell. However, the PowerShell example is given equal prominence to Azure CLI, despite PowerShell being primarily a Windows tool. There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific patterns or tools. The portal instructions are platform-neutral, but the command-line guidance leans toward Windows-centric tooling.
Recommendations
- Add explicit bash/Linux shell examples for quota checks using Azure CLI, demonstrating usage in a Linux environment.
- Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Consider reordering examples to present Azure CLI (cross-platform) before PowerShell (Windows-centric), or explicitly state platform applicability for each example.
- Mention that PowerShell Core is available on Linux/macOS, if relevant, but clarify typical usage patterns.
- Include a note or section for Linux users, highlighting any differences or additional steps required.
Azure Resource Manager
Overview of deployment troubleshooting for Bicep files and ARM templates
...les/azure-resource-manager/troubleshooting/overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. It references Azure PowerShell before Azure CLI when discussing error details, and provides PowerShell-specific command examples. There are no explicit Linux shell (bash) examples or references to Linux-specific troubleshooting tools or workflows. The guidance assumes Visual Studio Code as the editor, which is cross-platform, but does not mention alternative editors or command-line tools commonly used on Linux.
Recommendations
- Present Azure CLI examples before or alongside Azure PowerShell examples, as CLI is platform-agnostic and widely used on Linux.
- Include bash or shell script examples for common troubleshooting tasks, such as querying deployment operations or activity logs.
- Mention Linux-native editors (e.g., Vim, Emacs) or command-line validation tools for Bicep/ARM templates, if available.
- Clarify that Visual Studio Code and the listed extensions are available on Linux, and suggest installation instructions for Linux users.
- Ensure that troubleshooting steps and tools are described in a way that is not platform-specific, or explicitly provide parity for Linux environments.
Azure Resource Manager
Troubleshoot Bicep file deployments
...leshooting/quickstart-troubleshoot-bicep-deployment.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deployment and cleanup tasks, but PowerShell is a Windows-centric tool and is presented alongside Azure CLI without explicit Linux shell examples (e.g., Bash). There are no Linux-specific instructions, nor are Linux tools or shell patterns mentioned. The prerequisites mention Azure PowerShell before Azure CLI, and there is no mention of Linux-specific editors or shell environments. The documentation assumes Visual Studio Code, which is cross-platform, but does not discuss any Linux-specific considerations or alternatives.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands, including shell syntax for Linux/macOS users (e.g., use $HOME, clear line continuations, etc.).
- Clarify that Azure CLI commands work natively on Linux/macOS and provide any necessary environment setup instructions for those platforms.
- Reorder prerequisites to mention Azure CLI before Azure PowerShell, as CLI is cross-platform and PowerShell is more Windows-centric.
- Include notes or sections for Linux/macOS users, such as using terminal editors (vim, nano) or running commands in Bash.
- Where PowerShell is mentioned, clarify its cross-platform availability or provide alternative instructions for native Linux shells.
Azure Resource Manager
Troubleshoot ARM template JSON deployments
...ubleshooting/quickstart-troubleshoot-arm-deployment.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided alongside Azure CLI for every deployment operation, and references to PowerShell are present in the prerequisites. Visual Studio Code is recommended as the editor, which is cross-platform but often associated with Windows. The documentation mentions PowerShell before Azure CLI in the prerequisites and includes PowerShell-specific commands throughout. There is no explicit mention of Linux-specific tools, shell environments, or troubleshooting patterns, and no examples using Bash or Linux-native editors.
Recommendations
- Ensure Azure CLI examples are presented first, or alternate the order with PowerShell to avoid Windows-first bias.
- Add explicit references to Linux environments (e.g., Bash, zsh) and clarify that Azure CLI commands work natively on Linux and macOS.
- Include troubleshooting steps or examples using Linux-native editors (e.g., Vim, nano) or mention their usage for ARM template editing.
- Clarify that Visual Studio Code is available on Linux and macOS, and suggest alternatives for those platforms.
- Add notes or examples for using Azure CLI in Linux shell environments, including command syntax for Bash (e.g., environment variable usage, quoting differences).
- Consider mentioning cross-platform installation instructions for Azure CLI and PowerShell, or link to Linux/macOS-specific guides.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways: file path examples consistently use Windows-style paths (e.g., c:\jsontemplates) without showing Linux/macOS equivalents; installation and cache location instructions mention Windows first or exclusively; references to Azure PowerShell are present, but there are no equivalent Linux shell (bash/zsh) examples; and some commands (like install, upgrade, list-versions) are only shown for Azure CLI, which is cross-platform but often associated with Windows. Named pipe examples are shown for both Windows and Linux, but Windows syntax is presented first. There are no bash or Linux-specific command-line examples, and Linux file path conventions are rarely shown.
Recommendations
- For every file path example, provide both Windows (c:\path) and Linux/macOS (/home/user/path or ~/path) variants, ideally side-by-side.
- When referencing installation or cache locations, list all platforms equally and avoid listing Windows first by default.
- Add bash/zsh shell examples where appropriate, especially for command invocation and scripting.
- Include references to Linux-native tools or patterns (e.g., using export, chmod, etc.) where relevant.
- Ensure that documentation for commands available only in Azure CLI clarifies cross-platform support and provides platform-specific installation guidance.
- Where PowerShell is mentioned, also mention bash/zsh alternatives for Linux/macOS users.
- Review the order of platform mentions and examples to avoid implicit prioritization of Windows.
Azure Resource Manager
Quickstart: Integrate Bicep with Azure Pipelines
...ource-manager/bicep/add-template-to-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for resource cleanup, but the PowerShell example is presented alongside the CLI example, which can imply parity. However, in the pipeline YAML examples, only Bash scripting is shown for the Azure CLI task, and no PowerShell or Windows-specific scripting is used for pipeline steps. There is a slight Windows bias in the use of PowerShell for resource cleanup and the inclusion of Windows terminology (e.g., PowerShell tab), but overall, the pipeline instructions favor Linux (ubuntu-latest) as the default agent image and Bash scripting. No explicit Linux examples are missing, but the documentation could be more explicit about cross-platform compatibility.
Recommendations
- Clarify that both Azure CLI and Azure PowerShell are available on Windows, macOS, and Linux, and recommend CLI for cross-platform scenarios.
- Provide explicit instructions or notes for running PowerShell commands on Linux/macOS (e.g., using pwsh).
- Add a note that the YAML pipeline examples work on both Windows and Linux agents, and show how to switch the vmImage to windows-latest if desired.
- Ensure that any Windows-specific tools or patterns (such as PowerShell) are not presented as the default or only option, and always provide equivalent Linux/macOS instructions when possible.
- Consider listing Azure CLI examples before PowerShell examples to reinforce cross-platform parity.
Azure Resource Manager
Add module settings in the Bicep config file
...s/azure-resource-manager/bicep/bicep-config-modules.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell and Azure CLI as the primary credential sources, listing Azure PowerShell before other options, and omitting explicit Linux/macOS usage patterns or examples. No Linux-specific shell (e.g., Bash) or cross-platform authentication guidance is provided, and no mention is made of Linux package managers or environment setup. The credential precedence lists Azure PowerShell (a Windows-centric tool) before other options, and all examples and instructions assume familiarity with Windows tools.
Recommendations
- Add explicit examples and instructions for Linux/macOS users, such as using Bash or zsh for authentication and module management.
- Clarify that Azure CLI is cross-platform and provide usage examples for both Windows (PowerShell) and Linux/macOS (Bash).
- Include guidance on installing and configuring Bicep and Azure CLI on Linux, referencing package managers like apt, yum, or Homebrew.
- Reorder credential precedence to list cross-platform tools (Azure CLI, Environment) before Windows-specific tools (Azure PowerShell).
- Mention that Azure PowerShell is primarily for Windows and suggest alternatives for Linux/macOS users.
- Provide troubleshooting tips for authentication issues on Linux/macOS environments.
Azure Resource Manager
Use Bicep to deploy resources to tenant
...icles/azure-resource-manager/bicep/deploy-to-tenant.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting PowerShell examples and commands before or alongside Azure CLI, referencing PowerShell-specific tools (e.g., New-AzRoleAssignment, New-AzTenantDeployment), and using Windows-centric terminology and patterns. Linux-specific shell examples and guidance are missing, and there is no mention of Linux environments or considerations for non-Windows users.
Recommendations
- Provide Bash/Linux shell equivalents for all PowerShell commands, especially for role assignment and deployment steps.
- Explicitly mention that Azure CLI works cross-platform and highlight usage in Linux/macOS environments.
- Reorder examples to present Azure CLI (cross-platform) before PowerShell, or provide tabs for both with clear labeling.
- Avoid using Windows-centric terminology (e.g., PowerShell) as the default; instead, use neutral or cross-platform language.
- Include a section or note for Linux/macOS users, addressing any differences or prerequisites.
Azure Resource Manager
Develop a deployment script in Bicep
...re-resource-manager/bicep/deployment-script-develop.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI (Bash) and Azure PowerShell examples throughout, but there is a noticeable Windows bias. PowerShell examples and references (including Connect-AzAccount, Start-Sleep, and .ps1 scripts) are given equal or greater prominence than Bash/CLI examples. Windows-centric tools and APIs (such as CommandLineToArgvW) are referenced without Linux equivalents. PowerShell-specific patterns and troubleshooting steps (like $ErrorActionPreference and Start-Sleep) are described in detail, while Linux/Bash equivalents (e.g., set -e, sleep) are mentioned but not explained as thoroughly. The documentation does not reference Linux-native scripting tools or patterns beyond basic Bash usage, and Windows/PowerShell terminology is used in places where cross-platform alternatives could be highlighted.
Recommendations
- Ensure that Bash/CLI examples and explanations are given equal prominence and detail as PowerShell examples.
- When referencing Windows-specific APIs or tools (e.g., CommandLineToArgvW), provide Linux equivalents or clarify platform differences.
- Expand troubleshooting and scripting best practices for Bash (e.g., error handling with set -e, trap, exit codes), similar to the PowerShell guidance.
- Include references to Linux-native scripting tools and patterns (e.g., sed, awk, grep) where appropriate.
- Avoid using Windows/PowerShell terminology as the default; use neutral or cross-platform language where possible.
- Explicitly state platform compatibility for all examples and scripts, and provide guidance for running scripts on Linux/macOS as well as Windows.