Sad Tux - Windows bias detected
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
powershell_heavy
missing_linux_example
windows_tools
windows_first
Summary
The documentation page demonstrates a significant Windows bias. All command-line examples are provided exclusively using Azure PowerShell, with no mention or examples of Azure CLI (which is cross-platform and preferred by many Linux users). The 'PowerShell' tab is used for all scripted instructions, and there are no Bash or Linux shell equivalents. Additionally, the documentation refers to 'PowerShell' and 'Azure portal' as the only two options, omitting Linux-native workflows. The use of Windows-centric tools and patterns is evident, and the ordering of examples always places Windows/PowerShell first or exclusively.
Recommendations
  • Add Azure CLI (az) examples alongside PowerShell for all scripted operations, including exporting, modifying, and deploying ARM templates.
  • Include Bash/Linux shell command examples where relevant, especially for file operations (e.g., unzipping files, editing JSON).
  • Clearly label tabs as 'Azure CLI' and 'PowerShell' to provide parity and make it easier for Linux users to follow.
  • Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Ensure that references to creating or managing resources via command line include both PowerShell and CLI options, and avoid implying PowerShell is the only or primary method.
GitHub Create Pull Request

Scan History

Date Scan Status Result
2025-07-12 23:44 #41 cancelled Biased Biased
2025-07-12 00:58 #8 cancelled Clean Clean
2025-07-10 05:06 #7 processing Clean Clean

Flagged Code Snippets

    Get-AzSubscription
    
    Connect-AzAccount
    
    $context = Get-AzSubscription -SubscriptionId <subscription-id>
    Set-AzContext $context
    
    $resource = Get-AzResource `
      -ResourceGroupName <resource-group-name> `
      -ResourceName <resource-name> `
      -ResourceType <resource-type>
    
    Export-AzResourceGroup `
      -ResourceGroupName <resource-group-name> `
      -Resource $resource.ResourceId
    
    $resourceGroupName = Read-Host -Prompt "Enter the Resource Group name"
    $location = Read-Host -Prompt "Enter the location (i.e. eastus)"
    
    New-AzResourceGroup -Name $resourceGroupName -Location "$location"
    New-AzResourceGroupDeployment -ResourceGroupName $resourceGroupName -TemplateUri "<name of your local template file>"