Virtual Machine Scale Sets

95
Total Pages
80
Linux-Friendly Pages
15
Pages with Bias
15.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

274 issues found
Showing 101-125 of 274 flagged pages
Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI (cross-platform) and PowerShell (Windows-centric) examples for all major operations. However, PowerShell examples are consistently presented after CLI, and both are given equal prominence. There are no Linux-specific shell (bash) or scripting examples, but the CLI examples use Linux images and Application Health extensions for Linux, which helps parity. The PowerShell examples use the ApplicationHealthWindows extension, which could confuse Linux users. There are no references to Windows-only tools, but PowerShell is a Windows-first automation tool. No critical steps are Windows-only, and all tasks can be completed with CLI or REST API.
Recommendations
  • Clarify in PowerShell examples when the ApplicationHealthWindows extension is used, and provide a Linux equivalent (ApplicationHealthLinux) if the VMSS is Linux-based.
  • Add a short note at the start of each section explaining that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider including bash script snippets for common tasks to further improve Linux parity.
  • In PowerShell examples, explicitly mention that PowerShell Core is available cross-platform, or clarify if examples are only for Windows.
  • Ensure that the documentation does not default to Windows-centric extension types (like ApplicationHealthWindows) in generic examples.
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-03-02 00:00
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, and Azure PowerShell in all major sections. However, in each case, the Azure PowerShell (a Windows-centric tool) example is always presented, and sometimes appears before or at parity with Azure CLI. While Azure CLI is cross-platform and shown in all cases, PowerShell is not as commonly used on Linux/macOS. There are no explicit Linux/macOS-specific instructions or notes, but the CLI examples use Ubuntu images, indicating some Linux awareness. The order of examples (Portal, CLI, then PowerShell) is generally neutral, but the presence of PowerShell in all cases may create a slight perception of Windows bias.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users, perhaps with a short note at the start of CLI sections.
  • Optionally, add a brief note in PowerShell sections that PowerShell Core is available cross-platform, but is less common on Linux/macOS.
  • Consider providing Bash shell script examples for common operations, or clarifying that Azure CLI commands are intended for Bash/Unix shells as well as Windows.
  • If possible, add a small section or callout for Linux/macOS users, confirming that all operations are supported equally on those platforms via Azure CLI.
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-03-02 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 examples are often presented before CLI examples, and some sections (e.g., querying public IPs) show PowerShell commands before CLI. Portal instructions are also included, but there is a slight tendency to present Windows/PowerShell patterns first. All features are cross-platform and Linux parity is generally maintained, but minor ordering bias exists.
Recommendations
  • Present Azure CLI examples before PowerShell examples, or side-by-side, to emphasize cross-platform support.
  • Ensure that CLI and PowerShell examples are equally detailed and prominent.
  • Where possible, clarify that PowerShell examples work on both Windows and Linux (via PowerShell Core), but CLI is native to Linux/macOS.
  • Add explicit statements that all features and examples are applicable to both Linux and Windows VMSS unless otherwise noted.
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-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response and for managing VMSS extensions. However, in several places, Windows/PowerShell examples are presented before or alongside Linux equivalents, and the PowerShell section is notably detailed. The REST and Azure CLI examples are platform-neutral, but the PowerShell examples are prominent and sometimes shown before Bash/Linux. The extension installation section uses 'ApplicationHealthLinux' and 'ApplicationHealthWindows' types, but the PowerShell example defaults to 'ApplicationHealthWindows'.
Recommendations
  • Ensure Linux/Bash examples are presented before or equally with Windows/PowerShell examples in each section.
  • In PowerShell examples, clarify how to use 'ApplicationHealthLinux' for Linux VMSS instances.
  • Add explicit notes or guidance for macOS users where relevant (e.g., Bash examples).
  • Where possible, provide parity in troubleshooting steps for both Windows and Linux environments.
  • Consider adding a table or summary showing which commands/tools are available for each OS.
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-03-02 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-specific and is presented equally alongside CLI. The CLI example is shown before PowerShell, but both are given equal prominence. There are no exclusive Windows tools or patterns mentioned, and Linux users can complete all tasks using the CLI or ARM Template. However, the inclusion of PowerShell as a primary example may create minor friction for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add explicit notes indicating PowerShell is Windows-centric and suggest CLI for non-Windows environments.
  • Consider including Bash shell scripting examples for Linux users, if relevant.
  • Ensure parity in example coverage and ordering, with CLI examples shown first and PowerShell as an alternative.
GitHub Create Pull Request
Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides a conceptual overview of orchestration modes for Azure Virtual Machine Scale Sets and is largely platform-neutral. However, there is a minor instance of Windows bias: in the 'Managed Identity' row of the comparison table, the link for configuring user-assigned managed identity points to a Windows VMSS-specific guide, even though Flexible orchestration supports both Linux and Windows VMs. Additionally, the Azure Site Recovery feature is noted as 'Yes (via PowerShell)' for Flexible orchestration, which may imply Windows-centric tooling, though PowerShell is cross-platform. All CLI/API examples use Azure CLI, which is cross-platform, and Linux is explicitly mentioned as supported throughout.
Recommendations
  • Update managed identity documentation links to reference both Linux and Windows guides, or a platform-neutral guide.
  • Clarify that Azure Site Recovery via PowerShell is available on Linux/macOS as well, or provide Bash/Azure CLI alternatives if possible.
  • Ensure that any referenced extension or tooling is described as available for both Linux and Windows, or provide links to Linux-specific documentation where relevant.
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-03-01 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 PowerShell examples for most tasks, but PowerShell examples are often given before CLI examples, and some sections (e.g., querying public IPs) provide more detailed PowerShell usage. There is a slight preference for Windows/PowerShell tools, but Linux parity is generally maintained via CLI and ARM template examples.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side or in a consistent order (e.g., CLI first, then PowerShell) to avoid implicit Windows-first bias.
  • Ensure that CLI examples are as detailed as PowerShell examples, especially in sections like querying public IPs.
  • Explicitly mention that Azure CLI works cross-platform (Linux/macOS/Windows) to reassure non-Windows users.
  • Where PowerShell is used for advanced tasks, provide equivalent CLI commands or note any limitations.
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-03-01 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 configuring rolling upgrades on Virtual Machine Scale Sets. However, PowerShell examples are given equal prominence to CLI, and are presented in dedicated tabs throughout. While Azure CLI is cross-platform, PowerShell is primarily used by Windows users, and there are no explicit Linux/macOS-specific instructions or notes. The order of examples is generally CLI first, then PowerShell, which is positive, but the presence of PowerShell throughout may suggest a mild Windows bias. No critical functionality is Windows-only, and Linux/macOS users can complete all tasks using Azure CLI or ARM templates.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, and that CLI is suitable for all platforms.
  • Consider including Bash or shell script examples for common automation scenarios, or linking to relevant Linux/macOS guidance.
  • Ensure that all screenshots and instructions referencing the Azure portal are platform-neutral.
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-03-01 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 templates. The PowerShell example is present, which is Windows-centric, and appears after the CLI example. However, the CLI example is cross-platform and is shown before PowerShell. No Windows-specific tools or patterns are mentioned exclusively, and Linux parity is generally maintained. There are no missing Linux examples, as Azure CLI is the recommended cross-platform tool. The bias is minor, mainly due to the inclusion of PowerShell and its labeling, but does not significantly impact Linux/macOS users.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Optionally, add a note that PowerShell is available cross-platform, but is most commonly used on Windows.
  • Ensure that CLI examples are always shown before PowerShell to reinforce Linux parity.
  • Consider adding Bash shell scripting examples if relevant for advanced automation.
GitHub Create Pull Request
Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
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 enabling Automatic Zone Balance on Virtual Machine Scale Sets. However, PowerShell examples (which are Windows-centric) are consistently presented alongside or immediately after CLI examples, and the PowerShell section uses Windows-specific extension names (e.g., ApplicationHealthWindows). Portal instructions reference Windows UI patterns. There is a slight bias in the order and prominence of Windows tools and examples, but Linux parity is generally maintained via Azure CLI and REST API instructions.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell examples in each section.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is Windows-centric.
  • For VMSS extension examples, explicitly mention both ApplicationHealthLinux and ApplicationHealthWindows, and clarify which to use for Linux/Windows VM images.
  • Consider adding a short note at the start of each section indicating which tools are cross-platform and which are Windows-only.
  • Ensure screenshots and portal instructions are not overly Windows UI-specific, or clarify that the portal is platform-agnostic.
GitHub Create Pull Request
Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides an Azure CLI example for VM creation, but does not specify whether the example is for Windows or Linux, nor does it provide explicit Linux-specific guidance or parity. The mention of Azure Site Recovery 'via PowerShell' in the backup/recovery section suggests a Windows-centric tool is referenced without a Linux alternative. Overall, the documentation is mostly platform-neutral, but there is a mild bias in tool references and lack of explicit Linux examples.
Recommendations
  • Provide explicit Linux-specific examples alongside Windows/PowerShell examples, especially for VM creation and management.
  • Clarify whether Azure CLI commands are applicable to both Windows and Linux, and provide any necessary OS-specific flags or considerations.
  • When referencing Azure Site Recovery via PowerShell, mention if there are equivalent CLI or REST API options for Linux users.
  • Add sample workflows or links for Linux VM scale set scenarios, such as deploying Linux workloads, configuring extensions, or monitoring health.
  • Ensure that all referenced tools (e.g., Azure CLI, PowerShell) are presented with parity, and note cross-platform compatibility.
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-03-01 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 and custom metrics. However, there are several instances where Windows/PowerShell examples are presented before Linux/Bash examples, and Windows-specific tools (PowerShell cmdlets, ApplicationHealthWindows extension type) are referenced prominently. The PowerShell example for installing the extension uses 'ApplicationHealthWindows' as the type, while the Bash example uses 'ApplicationHealthLinux'. Both are shown, but Windows tools and patterns are often mentioned first or in more detail.
Recommendations
  • Ensure Linux/Bash examples are presented before or alongside Windows/PowerShell examples, especially in critical sections.
  • Clarify that both 'ApplicationHealthLinux' and 'ApplicationHealthWindows' extension types are supported, and provide explicit guidance for each OS.
  • Balance the detail and prominence of PowerShell and Bash examples, ensuring Linux instructions are as comprehensive as Windows ones.
  • Where possible, use neutral language and tools (e.g., Azure CLI, REST API) before platform-specific tools.
  • Explicitly state OS-specific requirements or differences where relevant.
GitHub Create Pull Request
Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority View Details →
Scanned: 2026-02-28 00:00
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 enabling Automatic Zone Balance on VM Scale Sets. However, PowerShell examples (which are Windows-centric) are consistently presented alongside or immediately after CLI examples, and some extension examples use 'ApplicationHealthWindows' as the type, even in contexts where Linux is also supported. Portal instructions reference Windows UI patterns. There is no explicit Linux/macOS bias, but the PowerShell and Windows-centric extension naming may cause confusion for Linux users. All major tasks can be completed via CLI and REST API, so Linux/macOS users are not blocked, but Windows tools and patterns are given prominent placement.
Recommendations
  • Ensure that examples for Linux (e.g., ApplicationHealthLinux extension) are provided and clearly separated from Windows examples.
  • Clarify when PowerShell examples are Windows-only and provide Bash or shell script equivalents for Linux/macOS users.
  • Present CLI examples before PowerShell examples to reduce Windows-first bias.
  • Explicitly state OS support for each extension type (e.g., ApplicationHealthLinux vs ApplicationHealthWindows) and when to use each.
  • Add notes or links for Linux/macOS users where PowerShell is referenced, suggesting CLI or REST API alternatives.
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-28 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. Some sections, such as querying public IPs, show PowerShell examples before CLI, and the Application Gateway integration section has PowerShell and CLI tabs, with PowerShell appearing first. There are no Linux-specific shell examples (e.g., Bash), but CLI commands are cross-platform. No Windows-only tools or patterns are used, and Linux parity is generally maintained.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly note that Azure CLI commands work on Linux/macOS, and consider adding Bash shell script snippets where appropriate.
  • Ensure that all PowerShell examples are matched with CLI equivalents, and vice versa.
  • Where possible, clarify any OS-specific requirements or limitations for commands.
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-02-28 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 all tasks, but PowerShell (a Windows-centric tool) is always presented after CLI and before ARM template examples. There are no Linux-specific shell examples (e.g., Bash), but Azure CLI is cross-platform. The PowerShell examples are detailed and prominent, which may create a perception of Windows bias, especially for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Explicitly note that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
  • Consider adding Bash shell script examples for common tasks, or clarify that Azure CLI commands can be run in Bash, Zsh, etc.
  • Reorder examples so CLI is shown first, and PowerShell is clearly marked as Windows-specific.
  • Add a short section or note for Linux/macOS users, highlighting their recommended tools and workflows.
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-28 00:00
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. It includes example commands for Azure CLI, PowerShell, Portal, and ARM Template. The PowerShell example is present, which is Windows-centric, but the CLI example (Azure CLI) is cross-platform and appears before PowerShell. There is no exclusive use of Windows tools, and Linux/macOS users can use Azure CLI or ARM templates. However, the inclusion of PowerShell and its detailed example may indicate a mild Windows bias, and PowerShell is listed after CLI but before ARM Template.
Recommendations
  • Clarify that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform tool.
  • Consider adding Bash shell script examples for Azure CLI usage to further highlight Linux parity.
  • Explicitly mention that PowerShell examples are for Windows users, while Azure CLI is cross-platform.
  • Ensure that all features described are accessible via CLI and ARM templates, and note any limitations for Linux/macOS users if present.
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-28 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 custom metrics and the application health extension. However, there are several instances where Windows/PowerShell examples are presented before Linux/Bash equivalents, and Windows-specific tools (PowerShell cmdlets) are emphasized. The REST and Azure CLI examples are cross-platform, but PowerShell is given equal or greater prominence, and some sample code uses Windows-centric extension types (e.g., ApplicationHealthWindows) even when Linux equivalents exist.
Recommendations
  • Ensure Linux/Bash examples are presented before or alongside Windows/PowerShell examples, especially in sections where both are relevant.
  • Clarify in sample code and tables that both ApplicationHealthLinux and ApplicationHealthWindows extension types are supported, and provide explicit Linux-focused examples.
  • Where PowerShell cmdlets are used, provide equivalent Bash/CLI commands for Linux users.
  • Review sample outputs and snippets to ensure Linux and macOS users are not overlooked, and that instructions are clear for both platforms.
  • Consider adding a note at the start of the page indicating parity between Linux and Windows VMSS support for custom metrics and rolling upgrades.
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-27 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 sections (such as querying public IPs) give PowerShell examples before CLI. Portal instructions are generic, but scripting examples sometimes default to PowerShell first. There are no Windows-only tools or patterns, and Linux parity is generally maintained, but the ordering and emphasis may create minor friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell in each section, as CLI is cross-platform.
  • Ensure all PowerShell examples are matched with CLI equivalents.
  • Explicitly note that Azure CLI works on Linux/macOS and is recommended for cross-platform use.
  • Where possible, add Bash shell examples for tasks that can be done outside Azure CLI/PowerShell.
  • Review the ordering of tabbed content to avoid implicit Windows-first bias.
GitHub Create Pull Request
Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority View Details →
Scanned: 2026-02-27 00:00
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 enabling Automatic Zone Balance on Virtual Machine Scale Sets. However, PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and in some sections, Windows-specific extension names (e.g., ApplicationHealthWindows) are used. In tabbed sections, PowerShell is often listed after CLI, but the PowerShell examples are detailed and prominent. There is minor bias in extension naming and the prominence of PowerShell, but Linux users can complete all tasks using Azure CLI or REST API. The documentation does not exclusively favor Windows, but minor friction exists for Linux users.
Recommendations
  • Ensure that Linux-specific extension names (e.g., ApplicationHealthLinux) are used in PowerShell examples when deploying Linux VMSS, or clarify when to use ApplicationHealthWindows vs ApplicationHealthLinux.
  • Add explicit notes or examples for macOS users where CLI usage is relevant.
  • Where PowerShell is used, clarify its cross-platform availability or provide Bash alternatives if possible.
  • Consider listing Azure CLI examples first in tabbed sections to reduce perceived Windows bias.
  • Add a short section explaining which tools are cross-platform and which are Windows-only.
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-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parity between Azure CLI and PowerShell for all command-line examples, but PowerShell examples are consistently presented immediately after CLI examples and before ARM template examples. There is no explicit Linux bias, but the ordering and inclusion of PowerShell throughout may subtly prioritize Windows users. However, Azure CLI is cross-platform and all tasks can be completed on Linux/macOS using CLI or ARM templates. No Windows-only tools or patterns are mentioned, and Linux users are not blocked from completing any task.
Recommendations
  • Consider alternating the order of CLI and PowerShell examples, or explicitly note that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add brief notes clarifying that PowerShell examples are for Windows users, while CLI and ARM templates are suitable for all platforms.
  • Ensure screenshots and UI references are not Windows-specific (currently, portal screenshots are neutral).
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-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides configuration instructions for rolling upgrades with MaxSurge on Azure Virtual Machine Scale Sets. It includes example commands for Azure CLI, PowerShell, Portal, and ARM templates. The PowerShell section is present and detailed, but the CLI section (az CLI) is also included and is cross-platform. However, the PowerShell example is shown after the CLI, and both are given parity. There is no evidence of Windows-only tools or patterns being mentioned exclusively or before Linux equivalents. The documentation does not provide Linux-specific shell examples (e.g., Bash scripting), but Azure CLI is inherently cross-platform. The bias is minor, mainly in the presence of PowerShell examples, which are more relevant to Windows users, but Linux/macOS users are fully supported via Azure CLI and ARM templates.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider adding Bash scripting examples for automation on Linux/macOS, if relevant.
  • Clarify that PowerShell examples are optional and primarily for Windows users, while CLI is recommended for cross-platform usage.
  • Ensure that any screenshots or UI references are not Windows-specific (e.g., Azure Portal is platform-agnostic).
GitHub Create Pull Request
Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md
Low Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides a balanced overview of orchestration modes for Azure Virtual Machine Scale Sets, with clear support for both Linux and Windows VMs. However, there is a minor bias in the 'Azure Site Recovery' feature row, which notes 'Yes (via PowerShell)' for Flexible orchestration mode, implying a Windows-centric tool for backup/recovery. Additionally, the only CLI example provided uses 'az vm create', which is cross-platform, but the documentation does not explicitly show Linux-specific commands or mention Linux tools, and Windows is mentioned first in some places.
Recommendations
  • Clarify that Azure Site Recovery can be used for Linux VMs and provide Linux-specific instructions or alternatives to PowerShell where possible.
  • Add explicit Linux examples or mention Linux compatibility in CLI instructions.
  • Ensure parity in mentioning both Linux and Windows when discussing supported operating systems, tools, and extensions.
  • Where PowerShell is referenced, also mention Bash/Azure CLI alternatives if available.
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-27 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 and Windows examples for configuring custom metrics for rolling upgrades on Virtual Machine Scale Sets. However, there is a notable Windows bias: PowerShell examples are consistently presented alongside Azure CLI and Bash, and Windows-specific extension types (ApplicationHealthWindows) are referenced before Linux equivalents. In several code snippets and REST examples, Windows extension types are shown as the default, and PowerShell is given equal prominence to Bash, despite Bash being more universally available across platforms. The ordering of examples sometimes puts Windows/PowerShell first or equally, rather than prioritizing cross-platform tools.
Recommendations
  • Ensure Linux and cross-platform examples (Azure CLI, Bash) are presented before Windows/PowerShell examples.
  • In REST and JSON configuration samples, use ApplicationHealthLinux as the default type, or show both Linux and Windows variants.
  • Clarify in each example which OS the extension type applies to, and avoid defaulting to Windows unless the scenario is Windows-specific.
  • Where possible, add macOS-specific notes or highlight that Bash/CLI examples work on macOS.
  • Consider grouping Windows/PowerShell examples in a separate section or tab, after Linux/cross-platform examples.
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-02-26 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 major operations (attach, detach, move VM between scale sets). However, PowerShell examples are always present and shown alongside CLI, which is cross-platform, but PowerShell is primarily used on Windows. Additionally, PowerShell examples are more verbose and detailed, sometimes including extra parameters (e.g., networking setup) not shown in CLI. The ordering of examples is mostly CLI first, then PowerShell, which is good, but the presence of PowerShell throughout may signal a slight Windows bias. No Windows-only tools or patterns are mentioned, and Linux parity is generally good.
Recommendations
  • Ensure that all PowerShell examples are clearly marked as Windows-specific, since Azure PowerShell is primarily used on Windows.
  • Consider adding Bash shell script examples for Linux users, especially for more complex operations.
  • Where PowerShell examples include extra parameters (e.g., networking), ensure the CLI examples are equally detailed for parity.
  • Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • If possible, provide links or references to Linux/macOS-specific guidance for Azure VM management.
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-02-26 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 PowerShell examples for all tasks, but PowerShell examples are always present and sometimes shown immediately after CLI, reinforcing Windows-centric tooling. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is not cross-platform by default in Azure context, so the documentation leans toward Windows users. However, Azure CLI is cross-platform and always included, mitigating the impact.
Recommendations
  • Explicitly note that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider adding Bash shell script examples for Linux users, especially for automation scenarios.
  • Clarify that PowerShell examples are for Windows PowerShell or PowerShell Core, and indicate their cross-platform support if relevant.
  • If possible, provide links or references to Azure CLI installation and usage on Linux/macOS.
GitHub Create Pull Request
← Previous Page 5 of 11 Next →