Virtual Machine Scale Sets

186
Total Pages
138
Linux-Friendly Pages
48
Pages with Bias
25.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

143 issues found
Showing 76-100 of 143 flagged pages
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all operations (attach, detach, move VMs), but consistently lists PowerShell examples after CLI and portal instructions. PowerShell is a Windows-centric tool, and while Azure CLI is cross-platform, there are no explicit Linux/macOS shell examples (e.g., Bash, zsh). The documentation does not reference Windows-only tools or patterns, but the presence of PowerShell examples and lack of Linux-specific shell instructions may create minor friction for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI commands are fully supported on Linux/macOS and Windows.
  • Consider adding explicit Bash/zsh shell examples for Azure CLI usage, especially for scripting scenarios.
  • Mention that PowerShell Core (pwsh) is cross-platform, but traditional Azure PowerShell is Windows-centric.
  • Ensure parity in troubleshooting and limitations sections by referencing both CLI and PowerShell where appropriate.
  • If possible, provide links to Azure CLI installation guides for Linux/macOS users.
GitHub Create Pull Request
Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides configuration examples for rolling upgrades with MaxSurge using Azure Portal, Azure CLI, PowerShell, and ARM Template. While the CLI and ARM Template examples are cross-platform, the PowerShell example is Windows-centric, and PowerShell is presented as a distinct tab alongside CLI. The CLI example is shown before PowerShell, which is positive, but the presence of PowerShell-specific instructions may create friction for Linux/macOS users who do not have access to PowerShell by default.
Recommendations
  • Clarify that PowerShell instructions are optional and primarily for Windows users.
  • Add Bash shell scripting examples for Azure CLI where relevant.
  • Explicitly note that Azure CLI works on Linux/macOS and provide links to installation guides for those platforms.
  • Consider adding a note in the PowerShell section about cross-platform PowerShell Core availability, if applicable.
  • Ensure parity in example complexity and completeness between CLI and PowerShell sections.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response and for extension installation. However, in several sections, PowerShell/Windows examples are presented before or with more detail than Linux equivalents. The PowerShell tab for installing the extension uses 'ApplicationHealthWindows' as the default type, while the CLI example uses 'ApplicationHealthLinux'. The PowerShell HTTP server example is more elaborate than the Bash/Python one. The documentation sometimes refers to Windows-specific extension types first and provides more PowerShell-centric guidance, which may create friction for Linux users.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence, and alternate which is shown first in tabbed sections.
  • When referencing extension types, clarify when to use 'ApplicationHealthLinux' vs. 'ApplicationHealthWindows' and provide explicit Linux-focused examples in PowerShell sections if relevant.
  • Balance the detail and complexity of Linux and Windows sample scripts (e.g., the Bash/Python HTTP server could include more robust error handling or logging, similar to the PowerShell example).
  • Where possible, provide cross-platform (e.g., Python-only) examples that work on both Linux and Windows.
  • In troubleshooting and verification sections, ensure Linux commands (e.g., Bash/curl) are as detailed as PowerShell equivalents.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as 'Create zone spanning or zonal scale sets'), PowerShell is listed before ARM templates and REST API. There are no Linux-specific shell examples (e.g., Bash), and the CLI examples are generic but do not reference Linux-specific considerations. The documentation does not mention Windows tools exclusively, but the ordering and prominence of PowerShell may create a slight Windows bias.
Recommendations
  • Ensure that Azure CLI examples are clearly labeled as cross-platform and, where relevant, provide Bash shell examples for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell in sections to emphasize cross-platform parity.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Add notes or links for Linux/macOS users regarding SSH key generation and authentication differences, if relevant.
  • Review the ordering of example sections to avoid implicit Windows prioritization.
GitHub Create Pull Request
Virtual Machine Scale Sets Azure Virtual Machine Scale Sets Attached Data Disks ...cale-sets/virtual-machine-scale-sets-attached-disks.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Windows and Linux examples for preparing data disks in scale sets, but the Windows example (PowerShell) is shown first and uses a named script (prepare_vm_disks.ps1) with explicit PowerShell invocation. The Linux example follows, using bash and a .sh script. The initial tutorial links mention Azure CLI and Azure PowerShell, but do not explicitly mention Linux-specific tools or show Linux-first patterns.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
  • Explicitly mention that Azure CLI is cross-platform and provide Linux/macOS-specific command examples where relevant.
  • Include references to Linux-native tools or patterns (e.g., cloud-init, shell scripting) in addition to PowerShell.
  • Clarify that both Windows and Linux are fully supported and provide parity in documentation structure and example depth.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell examples are given equal prominence and detail as CLI, which may indicate a Windows bias. PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every section can create friction for Linux/macOS users, especially since PowerShell is not the default shell on those platforms. However, Azure CLI is cross-platform and shown in all cases, so Linux/macOS users can complete all tasks. No Windows-only tools or patterns are present, and examples are not exclusively Windows-focused.
Recommendations
  • Clarify that Azure CLI is the recommended and cross-platform tool for Linux/macOS users.
  • Add a note in each section indicating that PowerShell examples are primarily for Windows users, while CLI is suitable for all platforms.
  • Consider listing CLI examples before PowerShell examples to reinforce CLI as the default for non-Windows environments.
  • Optionally, provide Bash script snippets or highlight CLI usage in Linux/macOS terminals for greater parity.
GitHub Create Pull Request
Virtual Machine Scale Sets Use scale-in policies with Azure Virtual Machine Scale Sets ...ale-sets/virtual-machine-scale-sets-scale-in-policy.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for configuring scale-in policies, but PowerShell examples (typically associated with Windows) are presented before CLI examples, and CLI examples do not explicitly highlight Linux/macOS usage. There is no mention of Linux-specific tools or shell environments, nor any guidance for Linux/macOS users regarding prerequisites or differences. The ordering and emphasis may subtly favor Windows users.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux/macOS users.
  • Explicitly state that Azure CLI works cross-platform and provide example commands in bash/zsh syntax where appropriate.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, and provide installation links or instructions.
  • Include troubleshooting or environment setup notes for Linux/macOS users (e.g., SSH key generation, shell differences).
  • Where possible, provide examples using native Linux tools or scripts if relevant.
GitHub Create Pull Request
Virtual Machine Scale Sets Create and encrypt a Virtual Machine Scale Set with Azure Resource Manager templates ...e-scale-sets/disk-encryption-azure-resource-manager.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists both Linux and Windows options for template deployment, but in the 'Next steps' section, Windows/PowerShell resources are mentioned before Linux/Azure CLI equivalents. Additionally, the sample template link in the note references a Windows example only, which may create friction for Linux users seeking parity.
Recommendations
  • In 'Next steps', list Azure CLI (Linux-friendly) resources before or alongside PowerShell resources.
  • Provide sample template links for both Linux and Windows scenarios in notes and examples.
  • Ensure that examples and references are balanced between Linux and Windows, or clearly labeled for each platform.
GitHub Create Pull Request
Virtual Machine Scale Sets Creating and configuring a key vault for Azure Disk Encryption ...irtual-machine-scale-sets/disk-encryption-key-vault.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions Azure CLI, Azure PowerShell, and Azure portal as supported tools, but places Azure PowerShell (a Windows-centric tool) prominently alongside Azure CLI. The 'Next steps' section lists PowerShell examples before CLI, and there are no explicit Linux/macOS-specific instructions or examples, nor any mention of platform-specific considerations. There is a subtle bias toward Windows tools and workflows.
Recommendations
  • Ensure Azure CLI examples are shown first, as CLI is cross-platform.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation links for those platforms.
  • Add Linux/macOS-specific notes or troubleshooting tips where relevant.
  • Balance PowerShell and CLI coverage, or clarify when PowerShell is required.
  • Consider adding Bash shell examples for common tasks.
GitHub Create Pull Request
Virtual Machine Scale Sets Create virtual machines in a Flexible scale set using Azure portal ...ale-sets/flexible-virtual-machine-scale-sets-portal.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias: password requirements link to a Windows-specific FAQ, and Windows terminology is referenced before Linux equivalents. While Linux options (SSH keys, supported distros) are mentioned, examples and links prioritize Windows resources, and Linux-specific guidance is less detailed.
Recommendations
  • Provide direct links to Linux password/username requirements, not just Windows FAQ.
  • Ensure Linux and Windows examples are presented with equal detail and prominence.
  • Include explicit Linux-focused screenshots or walkthroughs where applicable.
  • Reference Linux documentation first or alongside Windows resources when discussing OS-specific features.
GitHub Create Pull Request
Virtual Machine Scale Sets Resilient create and delete for Virtual Machine Scale Sets (Preview) ...rtual-machine-scale-sets/resilient-vm-create-delete.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for enabling Resilient create and delete using Azure Portal, CLI, PowerShell, and REST API. PowerShell is presented as a distinct tab, which is primarily a Windows tool, and its presence may indicate a slight Windows bias. However, the CLI examples use Azure CLI, which is cross-platform, and REST API examples are platform-agnostic. The documentation does not provide Linux-specific shell examples (e.g., bash scripts), but the CLI commands are suitable for Linux/macOS. There is a minor bias in that PowerShell is given equal prominence to CLI, and no explicit Linux shell scripting guidance is provided.
Recommendations
  • Add explicit bash or shell script examples for Linux/macOS users, especially for automation scenarios.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider mentioning cross-platform compatibility in the prerequisites or introduction.
  • If PowerShell is shown, consider also showing equivalent bash scripting for parity.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a scale set that uses Azure Spot Virtual Machines ...b/main/articles/virtual-machine-scale-sets/use-spot.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples for Azure CLI, PowerShell, ARM templates, and REST API. While Azure CLI and ARM templates are cross-platform, PowerShell is Windows-centric and is given equal prominence. The REST API example references a Windows-specific documentation link for further information. There is a slight Windows bias in the ordering and references, and Linux-specific examples or troubleshooting are missing, especially in the PowerShell and REST API sections.
Recommendations
  • Add explicit Linux/macOS troubleshooting or usage notes, especially for PowerShell (e.g., mention Azure PowerShell on Linux, or alternatives).
  • Ensure REST API follow-up links include both Linux and Windows examples, not just Windows.
  • Where PowerShell is mentioned, clarify cross-platform support or provide Bash/shell alternatives if available.
  • In the ARM template section, provide a direct Linux-focused example, not just a generic template.
  • Review ordering so that cross-platform tools (CLI, ARM) are presented before Windows-centric tools (PowerShell).
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows-specific scenarios (such as VM activation and Windows updates) are mentioned before Linux equivalents, and troubleshooting links are provided only for Windows activation. There are no explicit Linux-focused migration examples, nor are Linux-specific tools or troubleshooting resources referenced. The Azure CLI is used for examples, which is cross-platform, but no Linux-specific shell commands or package manager details are given.
Recommendations
  • Add explicit Linux migration scenarios and troubleshooting resources, such as links to common Linux VM issues or activation steps.
  • Include examples or notes for Linux package manager outbound connectivity (e.g., apt, yum, zypper) and how to ensure access for updates.
  • Provide parity in troubleshooting links, such as a reference to Linux VM connectivity or update problems.
  • When listing outbound connectivity requirements, mention Linux package manager access before or alongside Windows activation and updates.
  • Consider including bash or shell script examples for common tasks, not just Azure CLI.
GitHub Create Pull Request
Virtual Machine Scale Sets Understand the health state of your standby pool ...rtual-machine-scale-sets/standby-pools-health-state.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides example commands for Azure CLI, PowerShell, and REST API. While Azure CLI is cross-platform and shown first, PowerShell (a Windows-centric tool) is given its own section and example, which may imply Windows preference. There are no explicit Linux/macOS shell examples (e.g., Bash/cURL), nor is there mention of Linux-specific usage patterns. REST API usage is shown generically, but without Linux-oriented command-line examples.
Recommendations
  • Add explicit Bash/cURL examples for Linux/macOS users in the API section.
  • Clarify that Azure CLI works on Linux/macOS and provide sample output for those platforms.
  • Consider including links or notes about installing Azure CLI and PowerShell on non-Windows platforms.
  • Ensure parity in troubleshooting and next steps for Linux/macOS users.
GitHub Create Pull Request
Virtual Machine Scale Sets Delete or update a standby pool for Virtual Machine Scale Sets ...tual-machine-scale-sets/standby-pools-update-delete.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for updating and deleting standby pools, but PowerShell examples are presented alongside CLI in every section, and deployment instructions for ARM and Bicep templates mention PowerShell's New-AzResourceGroupDeployment before CLI's az deployment group create. This ordering and emphasis on PowerShell and Windows-centric tools may create friction for Linux/macOS users, though CLI and REST options are available.
Recommendations
  • Present CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
  • When listing deployment commands for ARM and Bicep templates, mention az deployment group create before New-AzResourceGroupDeployment.
  • Add explicit notes clarifying that all CLI commands work on Linux/macOS, and link to installation guides for Azure CLI on those platforms.
  • Consider adding bash script examples or references to shell scripting for Linux users.
  • Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., avoid showing Windows-only features in portal screenshots).
GitHub Create Pull Request
Virtual Machine Scale Sets Change the upgrade policy mode on Virtual Machine Scale Sets ...ts/virtual-machine-scale-sets-change-upgrade-policy.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides separate tabs for Portal, CLI, PowerShell, and ARM Template methods. While CLI and ARM Template are cross-platform, PowerShell is Windows-centric and is given equal prominence. There is no explicit Linux shell example (e.g., Bash), and PowerShell is presented as a primary method, which may imply Windows bias. The CLI example is cross-platform, but PowerShell is a Windows-first tool and its inclusion without a Linux shell equivalent may create friction for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and consider adding a Bash shell example or note for Linux/macOS users.
  • Indicate that PowerShell is primarily for Windows users, or provide guidance for using PowerShell Core on Linux/macOS if relevant.
  • Consider reordering tabs so that cross-platform methods (CLI, ARM Template) are shown before Windows-centric ones (PowerShell).
  • Add explicit statements about platform compatibility for each method.
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Minor Windows Links
Summary
The documentation provides parity between Azure CLI and Azure PowerShell examples for all major operations (attach, detach, update), and both are cross-platform tools. However, PowerShell (traditionally Windows-centric) is always presented as a primary scripting alternative, and some troubleshooting links and migration steps reference Windows-specific documentation (e.g., converting unmanaged disks, proximity placement groups) that point to Windows VM docs. Azure CLI is shown before PowerShell, which is positive, but the persistent inclusion of PowerShell and Windows documentation links introduces a mild Windows bias.
Recommendations
  • Ensure all troubleshooting and migration links have Linux equivalents or point to OS-agnostic documentation (e.g., proximity placement group removal, disk conversion).
  • Where possible, clarify that Azure CLI and PowerShell are both cross-platform, and consider adding Bash or shell script examples for common tasks to reinforce Linux parity.
  • Audit linked documentation to ensure Linux users are not redirected to Windows-only guides.
  • Explicitly state that Azure CLI and PowerShell are available on Linux/macOS, and provide installation links for these platforms.
  • If referencing PowerShell, consider also referencing Bash or other Linux-native scripting where appropriate.
GitHub Create Pull Request
Virtual Machine Scale Sets Set the upgrade policy mode on Virtual Machine Scale Sets ...-sets/virtual-machine-scale-sets-set-upgrade-policy.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Windows-centric tools (PowerShell) and lists PowerShell examples before ARM template examples, but does include Azure CLI examples, which are cross-platform. There is a mild ordering bias, with PowerShell (Windows) shown before ARM templates, and no explicit mention of Linux/macOS alternatives for scripting or automation. However, the CLI section uses Ubuntu in its example, which helps Linux parity.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and can be used on Linux/macOS/Windows.
  • Consider listing CLI examples before PowerShell to emphasize cross-platform support.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, or provide Bash scripting examples for Linux users.
  • Ensure ARM template examples are given equal prominence as scripting options for all platforms.
GitHub Create Pull Request
Virtual Machine Scale Sets Get high availability and cost savings with Spot Priority Mix for Virtual Machine Scale Sets ...ticles/virtual-machine-scale-sets/spot-priority-mix.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides platform-specific instructions for configuring Spot Priority Mix via the Azure Portal, Azure CLI, and Azure PowerShell. The CLI examples use Ubuntu images, which is Linux-friendly, but the PowerShell examples are given equal prominence and detail. The tab order presents Portal first (cross-platform), then CLI (Linux/macOS/Windows), then PowerShell (Windows-only), but PowerShell is included throughout. There are no Linux shell-specific examples (e.g., Bash scripts), and no mention of Linux-specific tools or patterns. However, the CLI instructions are fully usable on Linux/macOS, and the ARM template method is platform-neutral.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for scripting or automation.
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS/Windows.
  • Consider moving PowerShell examples after CLI examples, or labeling them as Windows-only.
  • Add a note about platform compatibility for each method.
  • Include troubleshooting tips for Linux users (e.g., CLI installation on Linux).
GitHub Create Pull Request
Virtual Machine Scale Sets Get standby pool and instance details ...irtual-machine-scale-sets/standby-pools-get-details.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell is given equal prominence as CLI, and is the only shell scripting example shown (no Bash, Linux shell, or macOS-specific guidance). PowerShell is a Windows-centric tool, and its inclusion alongside CLI can create a perception of Windows bias, especially as there are no Linux/macOS-specific shell examples or troubleshooting notes. However, the Azure CLI examples are cross-platform and shown first, mitigating the severity.
Recommendations
  • Add Bash or shell scripting examples for Linux/macOS users, especially for parsing JSON output or automating tasks.
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
  • Include troubleshooting notes for Linux/macOS environments (e.g., authentication, environment setup).
  • Clarify that PowerShell examples are optional and primarily for Windows users.
  • Consider adding links to platform-specific setup guides for Azure CLI and PowerShell.
GitHub Create Pull Request
Virtual Machine Scale Sets Get Prediction Results for Standby pools for Virtual Machine Scale Sets (Preview) ...machine-scale-sets/standby-pools-prediction-results.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. However, the PowerShell example is given equal prominence to the CLI, and PowerShell is a Windows-centric tool. There is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there examples tailored for Linux users (such as using curl for REST calls or jq for parsing). The ordering of examples (CLI, then PowerShell, then REST) is common, but the inclusion of PowerShell as a primary tab can be seen as Windows-first. No explicit Windows-only tools are referenced, but the lack of Linux/macOS-specific guidance or troubleshooting tips is notable.
Recommendations
  • Add Bash and curl examples for REST API calls to demonstrate Linux/macOS usage.
  • Include notes or examples using jq for parsing JSON output in Linux/macOS environments.
  • Clarify that Azure CLI is cross-platform and provide troubleshooting tips for Linux/macOS users if relevant.
  • Consider reordering tabs or explicitly stating cross-platform compatibility to avoid perceived Windows-first bias.
  • Add a section or note for Linux/macOS users about environment setup or differences, if any.
GitHub Create Pull Request
Virtual Machine Scale Sets Automatic instance repairs with Azure Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-instance-repairs.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides examples and instructions for Azure PowerShell, Azure CLI, REST API, and Azure Portal. However, PowerShell examples are consistently present and detailed, and in several sections (especially creation and update flows), PowerShell is listed before CLI. The documentation references PowerShell-specific cmdlets and patterns, which are primarily Windows-centric, and does not mention Linux/macOS-specific shell usage (e.g., bash, zsh) or alternative scripting environments. There are no explicit Linux/macOS shell script examples, nor any mention of OS-specific considerations for CLI usage.
Recommendations
  • Add explicit bash/zsh shell script examples for Azure CLI commands, showing usage on Linux/macOS (e.g., environment variable syntax, quoting, file redirection).
  • Clarify that Azure CLI commands work cross-platform and provide notes or tips for Linux/macOS users (e.g., installation, authentication differences, file path conventions).
  • Balance the order of examples so that CLI and REST API instructions are shown before or alongside PowerShell, not after.
  • Where PowerShell is referenced, note that it is available cross-platform, but provide links or instructions for Linux/macOS installation if relevant.
  • If there are any OS-specific caveats (e.g., for health extension endpoints, networking, or authentication), call them out explicitly.
GitHub Create Pull Request
Virtual Machine Scale Sets Automatic OS image upgrades with Azure Virtual Machine Scale Sets ...e-sets/virtual-machine-scale-sets-automatic-upgrade.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Minor Windows Config Details
Summary
The documentation provides both Windows and Linux information, but there is a mild Windows bias. Windows-specific configuration details (e.g., enableAutomaticUpdates property, drive letter reassignment) are mentioned explicitly and sometimes before Linux equivalents. PowerShell examples are given alongside Azure CLI, but PowerShell is a Windows-centric tool. ARM template and Bicep examples default to Windows images. No Linux-specific troubleshooting or configuration nuances are discussed, and Windows configuration properties are described in more detail.
Recommendations
  • Add Linux-specific configuration details and troubleshooting steps, such as handling /etc/fstab for data disk mounting after upgrades.
  • In ARM template and Bicep examples, alternate between Windows and Linux images or provide parallel examples for both.
  • Clarify that Azure CLI is cross-platform and highlight its parity with PowerShell for Linux/macOS users.
  • When discussing OS-specific properties (e.g., enableAutomaticUpdates), explicitly state the Linux equivalent or clarify that it is not needed.
  • Include Linux-first or at least Linux-equal examples in all code sections, especially where Windows properties or behaviors are described.
  • Add notes or links to Linux-specific upgrade behaviors, such as package manager updates, disk mounting, and extension compatibility.
GitHub Create Pull Request
Virtual Machine Scale Sets Autoscale Virtual Machine Scale Sets in the Azure portal ...le-sets/virtual-machine-scale-sets-autoscale-portal.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page primarily describes how to configure autoscale rules for Azure Virtual Machine Scale Sets using the Azure portal, which is cross-platform. However, references to command-line alternatives (Azure PowerShell and Azure CLI) consistently list PowerShell before CLI, and the 'Next steps' section links only to PowerShell-based management documentation, omitting CLI or Linux-native options. This ordering and emphasis may subtly favor Windows users and workflows.
Recommendations
  • When mentioning command-line alternatives, list Azure CLI before or alongside PowerShell to reflect cross-platform parity.
  • In the 'Next steps' section, include links to both Azure CLI and PowerShell management guides.
  • Explicitly state that both Azure CLI and PowerShell are available on Windows, Linux, and macOS, and provide links to installation guides for each platform.
  • Where possible, provide example links for both PowerShell and CLI in parallel, rather than only PowerShell.
GitHub Create Pull Request
Virtual Machine Scale Sets Reimage a virtual machine in a scale set ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-reimage-virtual-machine.md
Low Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, Azure PowerShell, and REST API. While the CLI and REST API are cross-platform, the PowerShell example is Windows-centric and is presented as a top-level tab alongside CLI, rather than as a secondary or alternative option. The ordering of tabs places PowerShell before REST, and the PowerShell example is not explicitly marked as Windows-only, which may imply parity or preference. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux/macOS nuances for CLI usage.
Recommendations
  • Clarify that PowerShell examples are primarily for Windows users and suggest alternatives for Linux/macOS users.
  • Add explicit Bash shell examples for the Azure CLI to demonstrate usage on Linux/macOS.
  • Consider reordering tabs so that cross-platform tools (CLI, REST) appear before Windows-specific tools (PowerShell).
  • Include notes or callouts about platform compatibility for each example.
GitHub Create Pull Request
← Previous Page 4 of 6 Next →