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 51-75 of 143 flagged pages
Virtual Machine Scale Sets Enable Azure Disk Encryption for Virtual Machine Scale Sets ...virtual-machine-scale-sets/disk-encryption-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page shows a notable Windows bias: Windows OS disk encryption is supported, while Linux OS disk encryption is explicitly not supported. Tutorial links mention PowerShell (Windows-centric) and CLI, but do not clarify if Linux-specific instructions or parity exist. The examples and guidance focus on Windows scenarios first, and Linux support is limited to data disks only, with no Linux OS disk encryption walkthrough.
Recommendations
  • Clearly state the limitations for Linux users at the top of the page.
  • Provide explicit Linux CLI examples and workflows, or link directly to Linux-specific guides.
  • Ensure that tutorial links clarify which OSes are supported and offer Linux alternatives where possible.
  • If Linux OS disk encryption is not supported, suggest alternative approaches or workarounds for Linux users.
GitHub Create Pull Request
Virtual Machine Scale Sets Proximity placement groups for Virtual Machine Scale Sets ...rtual-machine-scale-sets/proximity-placement-groups.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by presenting only PowerShell-based examples for creating and managing proximity placement groups and VM scale sets. Windows tools (PowerShell cmdlets) are used exclusively throughout the step-by-step instructions, with no equivalent Azure CLI or Linux/macOS shell examples provided. The only mention of Azure CLI is in a brief note at the end, without any concrete example or guidance. This creates friction for Linux/macOS users who primarily use Bash and Azure CLI.
Recommendations
  • Provide equivalent Azure CLI examples alongside PowerShell examples for all major tasks (creating proximity placement groups, listing them, creating scale sets, checking alignment status).
  • Clearly indicate cross-platform options at the start of the documentation, and avoid presenting Windows/PowerShell as the default or only method.
  • Add links to Linux/macOS-specific documentation where relevant, and ensure parity in example depth and clarity.
  • Consider reordering sections so that CLI and PowerShell examples are presented together, or alternate which is shown first.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a standby pool for Virtual Machine Scale Sets ...les/virtual-machine-scale-sets/standby-pools-create.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples, but PowerShell is given equal prominence as CLI, and deployment instructions for ARM and Bicep templates mention PowerShell tools (New-AzResourceGroupDeployment) alongside CLI. There is no explicit Linux/macOS bias, but the presence of PowerShell and Windows-specific tooling may create friction for Linux users. The portal instructions are platform-neutral, but PowerShell is a Windows-centric tool, and its mention may imply a Windows-first approach.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI for cross-platform usage.
  • List CLI examples before PowerShell examples to reduce Windows-first perception.
  • For ARM and Bicep deployment, highlight az deployment group create as the primary method, and mention PowerShell as an alternative for Windows users.
  • Add notes clarifying that PowerShell Core is available on Linux/macOS, if PowerShell usage is necessary.
  • Consider adding bash script examples for Linux users where relevant.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 (a Windows-centric tool) is given equal prominence to CLI, and in some update scenarios, CLI and PowerShell are shown before REST API/ARM template. There are no explicit Linux/macOS shell examples (e.g., Bash), and the ARM template section references both Linux and Windows but does not provide a full Linux-specific example. The documentation does not mention any Linux-specific tools or patterns, and the PowerShell examples may not be directly usable on Linux/macOS without additional setup.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users alongside Azure CLI commands.
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and provide installation/use links for those platforms.
  • Ensure that Linux examples (e.g., ARM template for Linux VMs) are shown with equal detail and prominence as Windows examples.
  • Consider listing Azure CLI (cross-platform) examples before PowerShell (Windows-centric) examples to reduce perceived Windows bias.
  • Add notes or links for Linux/macOS users on how to use PowerShell Core if needed.
GitHub Create Pull Request
Virtual Machine Scale Sets Azure Disk Encryption and Azure Virtual Machine Scale Sets extension sequencing ...ine-scale-sets/disk-encryption-extension-sequencing.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page claims to focus on enabling Azure Disk Encryption for Linux IaaS VMs, but the main sample templates and extension sequencing examples exclusively use Windows-centric tools and scripts (PowerShell, Windows disk formatting, Windows diagnostics extension). Linux-specific examples are only referenced as a link, not shown inline, and are not given equal prominence or detail.
Recommendations
  • Provide inline sample templates and extension sequencing examples using Linux tools (e.g., shell scripts for disk formatting, Linux diagnostics extensions).
  • Show Linux examples before or alongside Windows examples to match the stated Linux focus.
  • Replace or supplement PowerShell script references with bash or shell script references for Linux scenarios.
  • Explicitly mention Linux equivalents for extensions and commands where Windows-specific ones are shown.
  • Ensure that Linux users can follow the documentation without needing to consult external links for critical steps.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions Azure PowerShell and the Az module alongside Azure CLI and the portal, but does not provide explicit Linux/macOS-specific guidance or examples. The references to PowerShell and Az module, which are traditionally Windows-centric, are given equal prominence to the CLI, and no mention is made of Bash, shell scripting, or Linux-specific installation or usage patterns. There are no explicit Linux/macOS examples or troubleshooting notes, and the 'Next steps' section lists PowerShell before CLI.
Recommendations
  • Add explicit instructions or examples for Linux/macOS users, such as Bash or shell scripting with Azure CLI.
  • Clarify that Azure CLI is cross-platform and provide installation steps for Linux/macOS.
  • Ensure that CLI examples are shown before or alongside PowerShell examples.
  • Include troubleshooting notes for Linux/macOS environments where relevant.
  • Balance references to PowerShell with equivalent Linux/macOS tools or workflows.
GitHub Create Pull Request
Virtual Machine Scale Sets Customer intent: As a cloud administrator, I want to deploy and customize Virtual Machine Scale Sets, so that I can efficiently manage workloads and optimize resource utilization in my existing infrastructure. ...virtual-machine-scale-sets/includes/mvss-next-steps.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references deploying templates via Azure Resource Manager documentation specifically through a PowerShell link, suggesting a Windows-centric approach. There are no explicit Linux or cross-platform CLI examples or links provided, and PowerShell is mentioned before any Linux alternatives. While there is a mention of deploying a Linux scale set, the deployment instructions themselves are biased towards Windows/PowerShell.
Recommendations
  • Include links to Azure CLI and Bash deployment documentation alongside PowerShell.
  • Provide explicit examples for Linux/macOS users, such as using Azure CLI or Bash scripts.
  • Ensure that cross-platform tools are referenced equally and not only after Windows tools.
  • Add a section or note clarifying that all steps can be performed on Linux/macOS using supported Azure tools.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a scale set from a generalized image ...chine-scale-sets/instance-generalized-image-version.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides extensive PowerShell examples and advanced workflows using Windows-centric tools, while Linux/macOS equivalents (such as Bash scripting or cloud-init integration) are absent. PowerShell is given a dedicated, detailed section with both simplified and extended parameter sets, whereas CLI examples are briefer and lack comparable depth. Windows tools and patterns (e.g., Get-Credential, New-AzResourceGroup, New-AzLoadBalancer) are used exclusively in the PowerShell section, with no mention of Linux-native automation or scripting approaches. The ordering also places PowerShell after CLI but with much more detail, and there is no explicit parity for Linux users in advanced scenarios.
Recommendations
  • Add equivalent Bash or shell scripting examples for advanced workflows, matching the PowerShell extended parameter set.
  • Include guidance on using Linux-native tools (e.g., cloud-init, SSH key management, automation via Bash scripts) for scale set creation.
  • Explicitly mention cross-platform compatibility and provide notes for Linux/macOS users where PowerShell-specific commands are used.
  • Ensure advanced configuration steps (networking, load balancing, etc.) are shown using Azure CLI or ARM templates, not just PowerShell.
  • Balance example depth between PowerShell and CLI sections, and consider showing CLI/Bash examples first or side-by-side.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a Virtual Machine Scale Set with instance mix ...cles/virtual-machine-scale-sets/instance-mix-create.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples for Azure Portal, Azure CLI, Azure PowerShell, and REST API. However, the PowerShell section is notably more detailed, with multiple example commands and advanced usage (configuration object), while the CLI section is more basic. PowerShell is a Windows-centric tool, and its prominence and depth suggest a bias toward Windows users. Additionally, the prerequisites mention PowerShell before CLI, and the CLI examples use Ubuntu images but do not reference Linux-specific shell usage or scripting. There is no explicit Linux shell (bash) or macOS Terminal example, and PowerShell is presented as a primary automation tool, which may disadvantage Linux/macOS users.
Recommendations
  • Expand Azure CLI examples to include advanced scenarios, matching the depth of PowerShell examples.
  • Add explicit bash shell examples for Linux/macOS users, including scripting and automation patterns.
  • Clarify that Azure CLI is cross-platform and provide guidance for Linux/macOS environments (e.g., SSH key management, environment variables).
  • Reorder prerequisites to mention CLI before PowerShell, or present both equally.
  • Consider adding notes or links for installing and using Azure CLI and PowerShell on Linux/macOS.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a scale set from a specialized image version using the Azure CLI ...chine-scale-sets/instance-specialized-image-version.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides extensive PowerShell examples for creating a scale set from a specialized image, with detailed steps and resource configuration. The PowerShell section uses Windows-centric tools and patterns (e.g., New-AzLoadBalancer, RDP NAT pools), while the CLI examples are much simpler and do not cover equivalent networking or load balancer setup. The PowerShell example is significantly more comprehensive and appears before any Linux-specific guidance. There are no bash or Linux shell examples for advanced scenarios, and Windows tools/patterns are referenced exclusively in the PowerShell section.
Recommendations
  • Add equivalent bash/Linux shell examples for advanced scenarios, including networking and load balancer setup using Azure CLI.
  • Ensure that Linux/macOS users are guided through the same level of detail for resource creation as Windows/PowerShell users.
  • Explicitly mention cross-platform compatibility for CLI commands and clarify any OS-specific prerequisites.
  • Consider reordering sections so that CLI (cross-platform) examples are presented before PowerShell (Windows-only) examples.
GitHub Create Pull Request
Virtual Machine Scale Sets Spot Placement Score ...les/virtual-machine-scale-sets/spot-placement-score.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides platform-specific instructions for Azure PowerShell and Azure CLI, but the PowerShell section is more detailed and prominent. The CLI section does not clarify Linux/macOS usage or show shell-specific examples, and PowerShell is presented as a distinct tab, which may imply Windows-first bias. There are no explicit Linux/macOS shell examples (e.g., Bash), nor any mention of Linux-specific considerations. The Azure portal and REST API sections are platform-neutral, but the lack of Linux/macOS command-line examples and the prominence of PowerShell suggest a moderate Windows bias.
Recommendations
  • Add explicit Bash/Linux shell examples for the Azure CLI, showing usage in a Linux/macOS terminal.
  • Clarify that Azure CLI works cross-platform and provide example outputs for Linux/macOS.
  • Balance the PowerShell and CLI sections in detail and order, ensuring CLI instructions are as comprehensive as PowerShell.
  • Consider adding a note or section on Linux/macOS compatibility and any platform-specific caveats.
  • If possible, provide troubleshooting steps or error handling examples relevant to Linux/macOS environments.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure role permissions for standby pools ...hine-scale-sets/standby-pools-configure-permissions.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes role assignment and troubleshooting using the Azure Portal UI, with no mention of command-line alternatives. Where programmatic access is referenced, only PowerShell and CLI are mentioned, but no concrete examples are given for either. There are no Linux/macOS-specific instructions or examples, and the troubleshooting steps rely on Azure Portal and Log Analytics, which are cross-platform but presented in a way that assumes GUI usage typical of Windows users.
Recommendations
  • Provide equivalent Azure CLI commands for all role assignment steps, with explicit Linux/macOS usage examples.
  • Include instructions for using Azure PowerShell and Azure CLI for troubleshooting, with sample commands.
  • Clarify that Azure CLI is cross-platform and provide links to installation and usage guides for Linux/macOS.
  • Add a section or callout for Linux/macOS users, highlighting any differences or considerations.
  • Ensure REST API examples are accompanied by CLI and PowerShell equivalents, and show how to use curl or similar tools on Linux/macOS.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring diagnostic settings, but PowerShell (a Windows-centric tool) is given equal prominence to CLI. There is no mention of Bash or Linux-specific instructions, and the guidance for creating resources and configuring settings is oriented around the Azure portal and PowerShell, which are more familiar to Windows users. The CLI example is cross-platform, but the absence of explicit Linux/macOS guidance or troubleshooting tips creates a subtle Windows bias.
Recommendations
  • Add explicit Bash/Linux shell examples where CLI is shown, including notes about running az CLI on Linux/macOS.
  • Clarify that Azure CLI commands work on Linux/macOS and provide troubleshooting tips for common Linux issues (e.g., authentication, environment variables).
  • Add a note that PowerShell Core is available cross-platform, or provide Bash alternatives for PowerShell commands.
  • Consider listing CLI (cross-platform) examples before PowerShell to emphasize Linux parity.
  • Include links to Linux/macOS setup guides for Azure CLI and PowerShell Core.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 as the CLI, and PowerShell is a Windows-centric tool. There are no Linux/macOS-specific shell examples (such as Bash or curl), nor is there mention of Linux tools or workflows. The ordering of examples places CLI first, which is cross-platform, but PowerShell is still highlighted, and no explicit Linux guidance is given.
Recommendations
  • Add Linux/macOS-specific examples, such as using curl or httpie for the REST API.
  • Clarify that Azure CLI commands work on Linux/macOS and provide any necessary installation or usage notes for those platforms.
  • If PowerShell is mentioned, also mention Bash or other common Linux shells for parity.
  • Explicitly state platform compatibility for each tool in the documentation.
  • Consider adding a Bash script example for parsing the JSON output from Azure CLI.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Azure Spot Virtual Machines in scale sets, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and there are references to Windows-specific resources and examples. The ARM template section mentions both Linux and Windows but does not provide explicit Linux-centric examples. The eviction simulation section links only to a Windows/PowerShell guide for further information. Overall, there is a moderate Windows bias, especially in example tooling and follow-up resources.
Recommendations
  • Provide explicit Linux/macOS command-line examples, such as Bash scripts or Linux-specific CLI usage patterns.
  • Ensure that links to further reading or examples include Linux-focused documentation (e.g., simulate eviction with Azure CLI or REST from Linux).
  • When referencing PowerShell, clarify its cross-platform availability or provide alternatives for Linux users.
  • In ARM template sections, include concrete Linux VM examples and highlight Linux-specific considerations.
  • Balance the order of examples so that CLI (cross-platform) is shown before PowerShell, and avoid implying PowerShell is the default for all users.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 PowerShell is referenced heavily throughout, including in important notes and breaking change announcements. There is no explicit mention of Linux/macOS-specific considerations, nor are there any bash or shell script examples. The CLI examples use generic syntax, but PowerShell is given prominence, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Present Azure CLI examples before PowerShell examples, or alternate the order to avoid Windows-first bias.
  • Add explicit bash/shell script examples for common tasks, especially for enabling and updating policies.
  • Include notes clarifying that Azure CLI works natively on Linux/macOS and provide links to CLI installation guides for those platforms.
  • Reduce the emphasis on PowerShell in notes and breaking change announcements, or provide equivalent CLI-focused notes.
  • Where PowerShell is referenced, clarify that it is available cross-platform, or provide alternative commands for bash users.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux information, but there are several signs of Windows bias. Windows-specific configuration properties (e.g., enableAutomaticUpdates) are discussed in detail, and Windows Server SKUs are listed extensively. PowerShell examples are given before Azure CLI examples, and ARM/Bicep template snippets default to Windows images. Windows terminology and tools (e.g., drive letters, Windows Update) are mentioned more frequently and in more detail than Linux equivalents. However, Linux support is clearly stated and Azure CLI examples are present, so Linux users can complete the tasks with some friction.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples so Linux users see CLI first in some sections.
  • Add explicit Linux-focused configuration examples, especially for ARM/Bicep templates (e.g., show Canonical/Ubuntu image defaults).
  • Provide notes or examples for Linux-specific behaviors (e.g., disk mounting, extension scripts) where Windows drive letters or Windows Update are discussed.
  • Balance the discussion of OS-specific properties (e.g., mention Linux patching modes or update mechanisms where Windows Update is referenced).
  • Ensure that all examples (ARM, Bicep, CLI, PowerShell) show both Windows and Linux image configurations.
GitHub Create Pull Request
Virtual Machine Scale Sets Deploy an application to an Azure Virtual Machine Scale Set ...ne-scale-sets/virtual-machine-scale-sets-deploy-app.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Linux and Windows guidance, but several sections show Windows bias. Windows/PowerShell examples and tools (e.g., PowerShell DSC) are described in greater detail and appear before Linux equivalents. The Windows DSC example is extensive, while the Linux cloud-init section is shorter and lacks a direct example. References to PowerShell and Windows tools are frequent, and some links and next steps prioritize Windows management. Linux-specific examples and parity in detail are missing in some areas.
Recommendations
  • Provide equally detailed Linux examples for application deployment, matching the depth of the PowerShell DSC section (e.g., a full cloud-init YAML example).
  • Ensure Linux instructions and examples are presented alongside or before Windows ones, especially in summary tables and lists.
  • Include links to Linux management guides in 'Next steps', not just PowerShell/Windows ones.
  • Expand on Linux-native configuration management tools (e.g., Ansible, Chef) as alternatives to PowerShell DSC.
  • Where both Azure CLI and PowerShell are referenced, ensure CLI (cross-platform) examples are shown first or equally.
  • Add explicit Linux troubleshooting and best practices sections to match Windows coverage.
GitHub Create Pull Request
Virtual Machine Scale Sets Overview of autoscale with Azure Virtual Machine Scale Sets ...-sets/virtual-machine-scale-sets-autoscale-overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. Windows tools (PowerShell) are frequently mentioned and often listed before cross-platform alternatives (Azure CLI). Examples for manual scaling are given for Azure Portal, Azure CLI, and Azure PowerShell, but there is no explicit Linux shell example (e.g., Bash). In the 'Next steps' and other sections, PowerShell is often listed first or exclusively, and links to PowerShell-centric management guides are provided. While Azure CLI is cross-platform, the documentation does not provide parity for Linux/macOS users in terms of command-line examples or tool recommendations.
Recommendations
  • Provide explicit Bash/Linux shell examples alongside PowerShell, especially for common tasks.
  • Ensure Azure CLI examples are shown before or alongside PowerShell examples to emphasize cross-platform support.
  • Add links to Linux/macOS management guides for Virtual Machine Scale Sets.
  • Clarify that Azure CLI works on Linux/macOS and highlight any OS-specific considerations.
  • Balance references to Windows tools (PowerShell) with equivalent Linux/macOS tools or workflows.
GitHub Create Pull Request
Virtual Machine Scale Sets Use extension sequencing with Azure Virtual Machine Scale Sets ...ets/virtual-machine-scale-sets-extension-sequencing.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All concrete extension sequencing examples using Azure PowerShell and Azure CLI are explicitly for Windows-based scale sets, referencing Windows-specific extensions (ApplicationHealthWindows, CustomScriptExtension for Windows). There are no Linux-based extension examples, nor are Linux equivalents (e.g., ApplicationHealthLinux, CustomScriptExtension for Linux) mentioned. Windows tools and patterns (PowerShell, Windows extension names) are presented exclusively, and always before any Linux alternatives (which are absent).
Recommendations
  • Add parallel examples for Linux-based scale sets, using Linux-specific extensions (e.g., ApplicationHealthLinux, CustomScriptExtension for Linux).
  • Explicitly mention that extension sequencing applies to both Windows and Linux scale sets.
  • Provide CLI and PowerShell commands for Linux scenarios, including relevant extension names and settings.
  • Reference documentation for Linux extensions alongside Windows ones.
  • Avoid language that implies Windows is the default or only supported platform.
GitHub Create Pull Request
Virtual Machine Scale Sets Use Application Health extension with Azure Virtual Machine Scale Sets ...le-sets/virtual-machine-scale-sets-health-extension.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. REST API and PowerShell examples are provided first and are exclusively for Windows-based scale sets, while Linux examples appear only in the Azure CLI sections and are placed after Windows examples. PowerShell is emphasized as a primary tool, with no Linux shell or scripting equivalents. Troubleshooting and log location sections do mention Linux, but operational examples and walkthroughs are Windows-centric, and Linux users must infer or adapt steps for their platforms.
Recommendations
  • Provide REST API examples for both Windows and Linux scale sets, not just Windows.
  • Include PowerShell alternatives for Linux, such as Bash or Python scripts, or clarify PowerShell Core cross-platform usage.
  • Present Linux and Windows examples side-by-side or alternate which is shown first.
  • Expand troubleshooting and operational examples to include Linux-specific commands and workflows.
  • Clarify tool availability and usage for Linux users, especially where PowerShell is referenced.
GitHub Create Pull Request
Virtual Machine Scale Sets Maintenance notifications for Virtual Machine Scale Sets in Azure ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maintenance-notifications.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are presented before Azure CLI, and only PowerShell (a Windows-centric tool) is given as a script example, with no equivalent Bash or Linux shell example. References to scheduled events link to Windows-specific documentation. There is no explicit mention of Linux/macOS command-line environments or examples, and Linux users may need to infer usage from CLI commands.
Recommendations
  • Provide Bash/Linux shell examples alongside PowerShell, especially for scripting maintenance tasks.
  • Include links to Linux/macOS scheduled events documentation, not just Windows.
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and consider presenting CLI examples before or alongside PowerShell.
  • Add notes or sections for Linux/macOS users, highlighting any differences or considerations.
  • Ensure all referenced documentation (e.g., scheduled events) has Linux/macOS equivalents linked.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided for nearly every major operation, and Windows-specific extension types (ApplicationHealthWindows) are shown before or alongside Linux equivalents. In several places, Windows tools and patterns (PowerShell scripts, Windows extension types) are presented before Linux alternatives, and the PowerShell example for the health endpoint response is more elaborate than the Bash/Python example. However, Linux/CLI examples are present throughout, and REST API examples are provided, mitigating the impact.
Recommendations
  • Ensure Linux and Windows extension types are presented equally, with clear guidance for both (e.g., ApplicationHealthLinux and ApplicationHealthWindows).
  • Present CLI/Bash examples before PowerShell examples to avoid implicit prioritization of Windows workflows.
  • Expand Linux/macOS scripting examples (e.g., provide a shell-only or Python-only example for endpoint response, not requiring iptables or Python).
  • Clarify in each example which OS/platform it applies to, and provide parity for both where possible.
  • Where PowerShell is used, offer an equivalent Bash or shell script for Linux/macOS users.
  • Explicitly mention that all features are available on both Linux and Windows VMSS, and link to OS-specific extension documentation.
GitHub Create Pull Request
Virtual Machine Scale Sets Terminate notification for Azure Virtual Machine Scale Set instances ...s/virtual-machine-scale-sets-terminate-notification.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows and PowerShell are frequently referenced, with Windows links and examples often appearing before Linux equivalents. PowerShell examples are provided in detail, but there is no equivalent Bash or Linux shell scripting example. REST API and Azure CLI sections are platform-neutral, but the scripting guidance is Windows-centric. References to Scheduled Events link to Windows documentation first, and Linux links are secondary. There is a lack of Linux-specific command-line or scripting examples for enabling and responding to termination notifications.
Recommendations
  • Add Bash or shell script examples for enabling termination notifications, mirroring the PowerShell samples.
  • Ensure Linux documentation links are presented alongside or before Windows links, especially in sections discussing Scheduled Events.
  • Include explicit instructions or examples for Linux users to query and respond to scheduled events using curl, wget, or Python.
  • Balance the order of examples so that Linux and Windows are equally represented, or alternate which platform is shown first.
  • Reference Linux-specific troubleshooting steps if any platform differences exist.
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-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 PowerShell examples for most tasks, but PowerShell (a Windows-centric tool) is often presented before CLI, and some advanced configuration examples are more detailed in PowerShell. There are no Linux-specific shell examples (e.g., Bash scripts), and PowerShell is referenced more frequently than necessary, which may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Ensure all PowerShell examples have equivalent Azure CLI examples with equal detail and explanation.
  • Where possible, include Bash shell script examples for common tasks, especially for querying or manipulating resources.
  • Clarify in each section that Azure CLI commands work on all platforms, and PowerShell Core is available cross-platform if relevant.
  • Review tab ordering and ensure CLI is the default/first tab in tabbed code blocks.
GitHub Create Pull Request
← Previous Page 3 of 6 Next →