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 101-125 of 143 flagged pages
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-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides configuration instructions for rolling upgrades with MaxSurge using the Azure Portal, Azure CLI, PowerShell, and ARM templates. The PowerShell example is included as a dedicated tab, which is primarily a Windows tool. The CLI example uses Azure CLI, which is cross-platform, but the PowerShell example is given equal prominence, suggesting a Windows-centric approach. No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, nor are there any references to Linux/macOS-specific considerations. The order of examples places Portal (web), CLI, PowerShell, and ARM Template, with PowerShell appearing before ARM Template, which may subtly prioritize Windows users.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users, demonstrating equivalent Azure CLI commands.
  • Clarify that Azure CLI works on Linux/macOS and provide any OS-specific notes if needed.
  • Consider adding a note about PowerShell Core availability on Linux/macOS, or clarify if the PowerShell example is Windows-only.
  • Review the ordering of examples to avoid implicit prioritization of Windows tools.
  • Include troubleshooting or configuration notes relevant to Linux/macOS environments if applicable.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.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 most networking tasks, but PowerShell (a Windows-centric tool) is frequently presented before CLI, and some sections (such as querying public IPs) give more detailed PowerShell examples. Windows-specific scenarios (like Windows VM activation) are mentioned explicitly, while Linux/macOS equivalents are not discussed. There is a slight tendency to mention or demonstrate Windows tools and patterns before their cross-platform or Linux alternatives.
Recommendations
  • Present CLI examples before PowerShell, or side-by-side, to emphasize cross-platform parity.
  • Ensure all PowerShell examples have equivalent CLI examples, especially for querying and management tasks.
  • Include Linux/macOS-specific notes or troubleshooting where Windows-specific scenarios are discussed (e.g., VM activation).
  • Add explicit statements that all CLI commands work on Linux/macOS, and clarify any platform-specific differences.
  • Review example links and references to ensure Linux templates/examples are as visible as Windows ones.
GitHub Create Pull Request
Virtual Machine Scale Sets Performing manual upgrades on Virtual Machine Scale Sets ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-perform-manual-upgrades.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 parity across Azure Portal, CLI, PowerShell, and REST API, but the PowerShell section is given equal prominence to the CLI, and PowerShell is a Windows-centric tool. The CLI section uses Azure CLI, which is cross-platform, but PowerShell is not as common on Linux/macOS. The 'Next steps' section lists Azure CLI before PowerShell, but both are mentioned. There are no Linux-specific tools or shell examples (e.g., bash scripts), but the CLI example is sufficient for Linux users.
Recommendations
  • Clarify that Azure CLI commands work cross-platform and are recommended for Linux/macOS users.
  • Consider adding a bash script example or explicitly noting that the CLI example is suitable for Linux/macOS.
  • If PowerShell is included, mention that it is primarily for Windows users (unless cross-platform PowerShell is supported and common).
  • Ensure that Linux/macOS users are not left uncertain about which method to use.
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-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 provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones, but PowerShell (Windows-centric) examples are given equal prominence and detail as CLI. The ARM template section references both Linux and Windows, but the main walkthroughs and update instructions do not show explicit Linux shell commands or workflows. The order of presentation often puts PowerShell before REST API or ARM templates, and there are no bash-specific or Linux-native instructions for updating scale sets. This creates mild friction for Linux/macOS users, who may prefer bash or native shell commands over PowerShell.
Recommendations
  • Add explicit bash/Linux shell examples for all CLI commands, including update operations.
  • Clarify that Azure CLI is fully cross-platform and highlight its use for Linux/macOS users.
  • Consider presenting CLI (bash) examples before PowerShell in each section to signal parity.
  • Include troubleshooting or environment setup notes for Linux/macOS users where relevant.
  • Where PowerShell is used, note that it is available cross-platform, but provide bash alternatives.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parity between Linux and Windows in terms of template links and deployment instructions. However, in the 'Next steps' section, PowerShell is mentioned before CLI, and a sample template link references a Windows deployment. This ordering and example selection may subtly prioritize Windows users and tools.
Recommendations
  • Alternate the order of Linux and Windows examples in lists to avoid implicit prioritization.
  • Provide sample template links for both Linux and Windows, or use a Linux example if referencing only one.
  • List Azure CLI before PowerShell in 'Next steps' or present both together to avoid tool bias.
  • Explicitly state that instructions and templates are available for both platforms throughout the documentation.
GitHub Create Pull Request
Virtual Machine Scale Sets Spot Placement Score ...les/virtual-machine-scale-sets/spot-placement-score.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides platform-specific instructions for accessing the Spot Placement Score via Azure CLI and Azure PowerShell, with PowerShell (a Windows-centric tool) given its own dedicated section and example. The ordering of examples places Azure CLI before PowerShell, but both are presented as separate tabs. No explicit Linux/macOS shell examples (e.g., Bash) are provided, nor is there mention of Linux-specific considerations or parity for command-line usage. The REST API section is platform-neutral, but the lack of explicit Linux/macOS shell examples and the inclusion of PowerShell may create mild friction for non-Windows users.
Recommendations
  • Add explicit Bash or Linux/macOS shell examples for calling the REST API (e.g., using curl or httpie).
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS, and provide example installation links for those platforms.
  • Consider reordering or grouping CLI and PowerShell examples under a general 'Command-line' heading, with notes about platform compatibility.
  • Mention that PowerShell Core is available on Linux/macOS if PowerShell usage is recommended.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure PowerShell, Azure CLI, REST API, and Azure Portal. However, PowerShell examples are consistently presented before CLI examples, and there is a notable emphasis on PowerShell cmdlets throughout the page. There are no explicit Linux/macOS shell script examples, nor are there references to Linux-specific tools or environments. The CLI examples use generic Azure CLI commands, which are cross-platform, but the ordering and prominence of PowerShell may create a perception of Windows bias.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is natively cross-platform.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
  • Add example shell scripts for Linux/macOS environments where appropriate.
  • Clarify that PowerShell Core is available on Linux/macOS, if PowerShell examples are retained.
  • Balance the number and detail of CLI and PowerShell examples.
  • Avoid language such as 'PowerShell and Azure CLI' when referring to cross-platform tools; use 'Azure CLI and PowerShell' or clarify cross-platform support.
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-13 06:17
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, but PowerShell is given equal prominence as CLI and is presented before REST. PowerShell is a Windows-centric tool, and its inclusion as a primary example may indicate a bias toward Windows users. There are no Linux-specific shell examples (such as Bash or curl), nor is there explicit mention of Linux/macOS usage patterns. The CLI example is cross-platform, but the absence of Linux/macOS-specific guidance or troubleshooting tips suggests a mild Windows bias.
Recommendations
  • Add explicit Bash/curl examples for REST API usage to help Linux/macOS users.
  • Clarify that Azure CLI is cross-platform and provide installation/troubleshooting links for Linux/macOS.
  • Consider listing CLI examples before PowerShell, as CLI is more universally available.
  • Include notes or sections addressing Linux/macOS users, especially for command-line usage.
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-13 06:17
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 consistently presented immediately after CLI, and PowerShell-specific deployment commands (New-AzResourceGroupDeployment) are mentioned alongside CLI for ARM/Bicep templates. There is a notable emphasis on PowerShell and Windows-centric tools, with no explicit mention of Linux/macOS alternatives for PowerShell or deployment commands. The ordering and tool selection may subtly favor Windows users and workflows.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
  • Clarify that PowerShell Core is available on Linux/macOS, or provide Bash script examples where appropriate.
  • When listing deployment commands for ARM/Bicep templates, mention az deployment group create first, or provide a Linux/macOS workflow example.
  • Consider alternating the order of CLI and PowerShell examples, or grouping cross-platform tools together.
  • Add a note about platform compatibility for each tool, especially for PowerShell.
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-13 06:17
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 (PowerShell) example is shown first and references a PowerShell script, while the Linux (bash) example follows. The initial tutorial links mention Azure CLI and PowerShell, but do not explicitly mention Linux-specific tools or examples. There is a slight preference for Windows tools and ordering.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side.
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Include links or references to Linux/macOS-specific documentation or troubleshooting guides.
  • Add a note clarifying parity between Windows and Linux support for all features discussed.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Windows-centric tooling (PowerShell) as a primary option, with a dedicated tab for PowerShell examples. The order of tabs places PowerShell before ARM Template, and the PowerShell example is detailed. However, Azure CLI examples (cross-platform) are present and shown before PowerShell, and there are no exclusive Windows-only tools or missing Linux/macOS instructions.
Recommendations
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and highlight its cross-platform nature.
  • Consider moving the PowerShell tab after ARM Template to reduce perceived Windows prioritization.
  • Add a note for Linux/macOS users that Azure CLI is the recommended tool for cross-platform automation.
  • Explicitly mention that PowerShell Core is available on Linux/macOS if users prefer PowerShell.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides configuration instructions for rolling upgrades with MaxSurge on Azure Virtual Machine Scale Sets using the Azure Portal, Azure CLI, PowerShell, and ARM templates. While the CLI and ARM template examples are cross-platform, the PowerShell example is Windows-centric and is given equal prominence as the CLI. There is no explicit Linux/macOS bias, but PowerShell is a Windows-first tool and its inclusion may suggest a slight Windows bias. The CLI example is platform-neutral and appears before PowerShell, which helps mitigate bias.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS.
  • Consider mentioning that PowerShell Core is available cross-platform, or clarify if the example is for Windows PowerShell only.
  • If relevant, add Bash or shell script examples for Linux/macOS users, especially for automation scenarios.
  • Explicitly state platform compatibility for each tool in the documentation tabs.
GitHub Create Pull Request
Virtual Machine Scale Sets Encrypt disks for Azure scale sets with Azure CLI ...cles/virtual-machine-scale-sets/disk-encryption-cli.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Heavy Minor Linux Example
Summary
The documentation page is titled and described as focusing on Windows Virtual Machine Scale Sets, but the main CLI examples use Linux images and Linux-specific extensions (Custom Script Extension for Linux, .sh scripts). However, the overall framing, title, and some references (such as the PowerShell link and batch file example for Linux) suggest a Windows-first approach. Linux is supported in the examples, but parity is not fully clear, and Linux-specific guidance is less prominent.
Recommendations
  • Update the title and description to clarify that the instructions apply to both Windows and Linux VMSS, or provide separate sections/examples for each OS.
  • Provide explicit examples for both Windows and Linux VMSS creation and disk encryption, including Windows-specific extensions and scripts where relevant.
  • Include clear guidance on OS-specific prerequisites and supported scenarios, referencing both Windows and Linux documentation equally.
  • Move or duplicate the Linux batch file example into the main body, not just as a 'next steps' link.
  • Ensure references to PowerShell and ARM templates are balanced with Bash/shell scripting and Linux automation options.
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-13 06:17
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 by referencing Windows password requirements first and linking to a Windows-specific FAQ for password complexity. The Linux SSH key option is mentioned second, with its documentation link provided after the Windows reference. No explicit Linux-specific examples or screenshots are given, and the password requirements section is Windows-centric.
Recommendations
  • Present Linux and Windows options with equal prominence and order, e.g., 'For Windows, use a password; for Linux, use SSH keys or a password.'
  • Link to both Windows and Linux documentation for password and SSH key requirements, not just Windows.
  • Include Linux-specific screenshots or examples where relevant.
  • Clarify that password requirements apply to both Windows and Linux VMs, or specify differences if any.
  • Ensure that Linux users are not directed to Windows-only documentation for critical steps.
GitHub Create Pull Request
Virtual Machine Scale Sets Use Azure Log Analytics to monitor standby pool events ...achine-scale-sets/standby-pools-monitor-pool-events.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring diagnostic settings, but PowerShell (a Windows-centric tool) is given equal prominence as CLI. There is no explicit mention of Linux-specific tools or guidance, and the instructions for creating resources and querying logs are focused on the Azure portal, which is platform-agnostic but often associated with Windows environments. The absence of Bash or Linux shell-specific examples, and the lack of explicit Linux/macOS parity checks, indicate a mild Windows bias.
Recommendations
  • Add explicit Bash/Linux shell examples for configuring diagnostic settings (e.g., using az CLI from Bash).
  • Clarify that Azure CLI commands work cross-platform and provide any Linux/macOS-specific notes if needed.
  • Consider mentioning or linking to documentation for using Azure CLI on Linux/macOS.
  • If PowerShell is shown, also show Bash equivalents or note cross-platform PowerShell Core usage.
  • Explicitly state that all steps can be performed from Linux/macOS environments.
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-13 06:17
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 configuring and updating Spot Priority Mix, but PowerShell examples are always present and shown after CLI. There is no explicit mention of Linux/macOS shell scripting or tools, nor are Bash-specific instructions or cross-platform notes provided. The Azure CLI examples use Ubuntu images, but the CLI itself is cross-platform. The PowerShell examples may imply a Windows-centric audience, especially since Azure PowerShell is most commonly used on Windows. No Linux-specific tools or patterns are mentioned, and the documentation does not clarify CLI usage on Linux/macOS.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash shell script examples for common tasks, or clarify that CLI examples are suitable for Bash/zsh.
  • Add a note about installing and using Azure CLI on Linux/macOS.
  • Consider moving CLI examples before PowerShell to reduce perceived Windows-first bias.
  • If relevant, mention cross-platform automation options (e.g., Terraform, Ansible) for advanced users.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides example commands for Azure CLI, PowerShell, and REST API. PowerShell is featured as a primary example, which is a Windows-centric tool, and is presented immediately after the CLI example. There is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments (such as using curl for REST API calls or jq for parsing output). The CLI example is cross-platform, but the PowerShell example and its prominence indicate a mild Windows bias.
Recommendations
  • Add explicit Bash/Linux/macOS shell examples, such as using curl to query the REST API and jq to parse the output.
  • Clarify that Azure CLI works on Linux/macOS and Windows, and provide sample commands for those platforms (e.g., Bash syntax).
  • Consider reordering examples so that cross-platform tools (CLI, REST) appear before Windows-specific tools (PowerShell).
  • Add notes or links for Linux/macOS users about installing and using Azure CLI.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell for all operations. While Azure CLI is cross-platform and shown before PowerShell, PowerShell examples are always present, and there are no explicit Bash or Linux shell script examples. Some troubleshooting links and migration steps reference Windows-specific documentation (e.g., converting unmanaged to managed disks and proximity placement group docs under 'windows'). This subtly prioritizes Windows tools and patterns, and may create friction for Linux/macOS users.
Recommendations
  • Add explicit Bash or Linux shell script examples where relevant, especially for common automation tasks.
  • Where documentation links reference Windows-specific guides (e.g., converting disks, proximity placement groups), provide equivalent Linux documentation links or clarify if the process is identical.
  • Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Consider adding a short section or callout for Linux/macOS users, highlighting any OS-specific considerations or best practices.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Minor Windows Config Notes
Summary
The documentation provides both Windows and Linux parity in terms of supported OS images and configuration methods (REST API, Azure CLI, PowerShell, ARM templates, Bicep). However, there are signs of Windows bias: PowerShell examples are given before CLI, ARM/Bicep template defaults use Windows images, and configuration notes often reference Windows-specific properties (e.g., enableAutomaticUpdates, drive letters) without equivalent Linux notes. Windows terminology and tools (PowerShell, Windows Update) are referenced more frequently and sometimes exclusively in requirements and troubleshooting sections.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI first to better serve Linux/macOS users.
  • In ARM/Bicep template examples, provide Linux image defaults alongside Windows defaults.
  • Add Linux-specific configuration notes where relevant (e.g., handling device naming, custom boot scripts for Linux).
  • Clarify that PowerShell is Windows-specific and recommend Azure CLI for cross-platform use.
  • Ensure troubleshooting and requirements sections include Linux equivalents (e.g., how Linux handles disk reattachment, patching, and health probes).
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents the Azure portal workflow for autoscaling VM Scale Sets in a platform-neutral way, but consistently references Azure PowerShell before Azure CLI when mentioning alternative methods. The 'Next steps' section links only to PowerShell-based management documentation, omitting CLI or Linux-native alternatives. This ordering and emphasis subtly prioritize Windows tools and workflows, potentially creating friction for Linux/macOS users.
Recommendations
  • When listing alternative methods, mention Azure CLI first or equally alongside PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • In the 'Next steps' section, add links to equivalent Azure CLI documentation for managing VM Scale Sets.
  • Explicitly state that both PowerShell and CLI are supported on all platforms, and provide guidance for Linux/macOS users where relevant.
  • Consider including a brief comparison table or note highlighting platform compatibility for each tool.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides examples for Azure Portal, Azure CLI, ARM Template, and PowerShell. PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. In each major section (setting/updating policy, getting status, canceling, restarting), PowerShell examples are presented as a primary method alongside CLI, but there are no explicit Linux/macOS shell or scripting examples (e.g., Bash, Cloud Shell specifics). The CLI examples are cross-platform, but the presence and prominence of PowerShell throughout the documentation indicate a Windows bias. There is no mention of Linux-specific tooling or workflows, and PowerShell is listed before ARM Template in most cases.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows equally, and consider showing Bash-specific usage (e.g., environment variables, piping, jq for JSON parsing).
  • Add explicit Bash or shell script examples for common operations, especially for status checking and automation.
  • Mention Azure Cloud Shell as a cross-platform option for both CLI and PowerShell, and clarify its OS-agnostic nature.
  • If PowerShell is shown, note that PowerShell Core is available on Linux/macOS, or provide links/instructions for Linux/macOS users.
  • Consider listing CLI (Bash) examples before PowerShell to reduce Windows-first perception.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and ARM templates. While the CLI example is cross-platform, PowerShell is Windows-centric and is given equal prominence as CLI. There is no explicit Linux/macOS bias, but PowerShell is not natively available on Linux/macOS, and no Bash or shell script examples are provided. The ordering places PowerShell before ARM templates, which may subtly prioritize Windows workflows.
Recommendations
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and is the recommended cross-platform tool.
  • Consider providing Bash or shell script examples for Linux/macOS users, especially for automation scenarios.
  • Note that PowerShell Core is available on Linux/macOS, but most users on those platforms prefer CLI or Bash.
  • Reorder examples to put CLI before PowerShell, emphasizing cross-platform parity.
  • Add a brief section or note about tool availability and platform compatibility.
GitHub Create Pull Request
Virtual Machine Scale Sets Performing manual upgrades on Virtual Machine Scale Sets ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-perform-manual-upgrades.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parity across Azure Portal, CLI, PowerShell, and REST API. However, PowerShell is given a dedicated section, and the 'Next steps' section lists Azure CLI before PowerShell, but the presence of a PowerShell tab and examples may indicate a slight Windows bias. There are no Linux/macOS-specific instructions or notes, but the Azure CLI example is cross-platform. No critical tasks are Windows-only.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to reassure non-Windows users.
  • Add a note clarifying that PowerShell examples are for users on Windows or those who have PowerShell Core installed on Linux/macOS.
  • Consider including Bash or shell scripting examples for common automation scenarios, or at least reference that Azure CLI is the recommended cross-platform tool.
  • If possible, add a short section or FAQ addressing platform compatibility for each method.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI examples for configuring scale-in policies, but PowerShell (a Windows-centric tool) is shown before CLI in each section. There are no Linux/macOS-specific shell examples (e.g., Bash scripts), and PowerShell is highlighted as a primary method, which may create friction for Linux/macOS users who typically use CLI or ARM templates. However, Azure CLI and ARM template examples are present and fully functional for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly note that Azure CLI commands work on Linux/macOS and Windows, while PowerShell is primarily for Windows.
  • Add Bash script examples for common tasks to further support Linux/macOS users.
  • Clarify in introductory sections that all operations can be performed using CLI, ARM templates, or REST API, not just 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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure Portal, CLI, PowerShell, and REST API. The PowerShell example is given equal prominence to the CLI example, but PowerShell is a Windows-centric tool. The ordering of examples places PowerShell before REST API, and the CLI example does not explicitly mention Linux or macOS usage, nor does it provide any Linux-specific context. There is no explicit Windows-only bias, but the inclusion and prominence of PowerShell may create a subtle Windows bias.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
  • Add notes or examples showing CLI usage on Linux/macOS terminals (e.g., bash), including any OS-specific considerations.
  • Consider moving PowerShell examples after CLI and REST API, or label them as Windows-specific.
  • If there are any differences in behavior or prerequisites for Linux/macOS users, document them explicitly.
GitHub Create Pull Request
← Previous Page 5 of 6 Next →