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 51-75 of 274 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-03-09 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. While the CLI example is cross-platform, the PowerShell example is Windows-centric and is presented immediately after the CLI example, potentially giving undue prominence to Windows tooling. There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for CLI commands. The PowerShell section is substantial, but not exclusive, and the CLI example is suitable for Linux/macOS users.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider placing the CLI example before the PowerShell example to reinforce cross-platform parity.
  • Add a note for Linux/macOS users clarifying that PowerShell is optional and not required for these tasks.
  • Optionally, provide Bash shell scripting examples for advanced automation scenarios.
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-09 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 are given equal prominence to Azure CLI, and Windows-specific extension names (e.g., ApplicationHealthWindows) are used in PowerShell examples, while Linux-specific extension names (ApplicationHealthLinux) are used in CLI examples. Portal instructions are platform-neutral, but PowerShell is a Windows-centric tool and is presented alongside CLI, which is cross-platform. The PowerShell examples and references to Windows-specific extension types are not always matched with Linux equivalents or explanations, and PowerShell is given as a primary automation option, which may create friction for Linux/macOS users.
Recommendations
  • Clarify that Azure PowerShell can be used cross-platform (on Linux/macOS via PowerShell Core), but CLI is generally preferred for Linux users.
  • In PowerShell examples, provide both ApplicationHealthWindows and ApplicationHealthLinux extension types, or explain when to use each.
  • Consider showing Azure CLI examples first, as CLI is more universally available across platforms.
  • Add a note about PowerShell Core support for Linux/macOS, or link to guidance for Linux users.
  • Ensure that all extension configuration examples are clearly labeled for Windows or Linux VM images.
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-09 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 operations, but PowerShell is featured equally alongside CLI and is presented in its own dedicated sections. PowerShell is a Windows-centric tool, and its presence may create friction for Linux/macOS users who do not have access to PowerShell by default. However, Azure CLI examples are present and shown before PowerShell in each section, ensuring Linux parity. No Windows-only tools or patterns are mentioned, and the documentation is not Windows-specific.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider explicitly stating that PowerShell examples are primarily for Windows users, while Azure CLI is suitable for all platforms.
  • Add a brief note at the start of the 'PowerShell' sections indicating PowerShell Core is available for Linux/macOS, but Azure CLI is generally easier for non-Windows users.
  • Ensure that CLI examples remain prominent and are not overshadowed by PowerShell content.
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-09 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) show PowerShell examples before CLI or in more detail. Portal instructions are generic, but scripting examples sometimes favor PowerShell. There are no Windows-only tools or patterns used, and Linux parity is generally maintained, but the ordering and occasional emphasis on PowerShell may create minor friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell in all sections, as CLI is cross-platform.
  • Ensure all PowerShell examples have equivalent Azure CLI examples, especially for querying resources.
  • Explicitly note that Azure CLI is recommended for Linux/macOS users.
  • Where possible, add Bash shell script examples for common tasks.
  • Review example ordering in tabbed content to avoid 'windows_first' bias.
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-09 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 VMs between scale sets), but consistently includes Azure PowerShell examples alongside Azure CLI, which is primarily a Windows-centric tool. Azure PowerShell examples are often more detailed and shown immediately after CLI, potentially creating a perception of Windows preference. However, Azure CLI is cross-platform and all examples use it, including Linux-centric VM images (e.g., Ubuntu2204), and there are no Windows-only tools or patterns. No critical steps are Windows-only.
Recommendations
  • Consider explicitly noting that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • If possible, provide Bash shell script examples for common tasks (especially for Linux users) in addition to Azure CLI.
  • Clarify that Azure PowerShell is available on Linux/macOS, but CLI is generally more native for those platforms.
  • Ensure parity in detail between CLI and PowerShell examples.
  • If showing both CLI and PowerShell, consider showing CLI first to reinforce cross-platform parity.
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-03-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Minor Windows Defaults
Summary
The documentation provides both Windows and Linux coverage for Azure Virtual Machine Scale Sets automatic OS image upgrades. However, there are several signs of Windows bias: Windows terminology and configuration properties (e.g., enableAutomaticUpdates, Windows Update) are discussed in detail, often before or more prominently than Linux equivalents. PowerShell examples (a Windows-centric tool) are given equal prominence to Azure CLI, but are listed first in most cases. ARM template and Bicep examples default to Windows images. Some explanations reference Windows-specific behaviors (e.g., drive letter reassignment) without Linux equivalents. However, Linux images and Azure CLI examples are present throughout, and the feature is not Windows-only.
Recommendations
  • Ensure ARM template and Bicep examples use both Windows and Linux images, or provide Linux-focused variants.
  • When discussing configuration properties, clarify Linux-specific requirements or behaviors alongside Windows (e.g., mention Linux patching differences).
  • Alternate the order of PowerShell and Azure CLI examples, or explicitly state that Azure CLI is cross-platform.
  • Add notes about Linux disk mount behavior (e.g., device naming) where Windows drive letter reassignment is mentioned.
  • Where possible, use neutral language and avoid defaulting to Windows terminology when describing generic features.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides a comprehensive overview of orchestration modes for Azure Virtual Machine Scale Sets, focusing on platform features and APIs. While most content is platform-neutral, there are minor instances where Windows terminology or links are presented before Linux equivalents, such as referencing managed identities with a Windows VMSS portal link and mentioning Azure Site Recovery 'via PowerShell' without a Linux CLI equivalent. However, the majority of examples and guidance are generic and applicable to both Linux and Windows VM workloads.
Recommendations
  • Ensure that all references to managed identities and Azure Site Recovery include both Linux and Windows guidance, or clarify if a feature is Windows-only.
  • Where PowerShell is mentioned, provide equivalent Azure CLI or Bash examples for Linux/macOS users.
  • Review links and examples to ensure Linux parity, especially in sections referencing VM extensions, backup, and recovery.
  • Explicitly state when a feature or example is Windows-only to avoid confusion.
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-09 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, but there is a notable Windows bias. PowerShell examples and Windows-specific extension types (ApplicationHealthWindows) are presented alongside Linux equivalents, but Windows terminology and tools (PowerShell, Windows extension type) are often shown first or in parallel. The PowerShell section is more detailed than the Bash section, and Windows-specific extension names are used in several code snippets. The CLI and REST examples are neutral, but the PowerShell examples are prominent and sometimes precede Linux/Bash examples. Overall, Linux users can complete all tasks, but Windows tools and patterns are emphasized.
Recommendations
  • Ensure Linux examples (Bash, ApplicationHealthLinux) are presented before or equally with Windows examples in all sections.
  • Expand Bash/Linux sample scripts to match the detail and completeness of PowerShell examples.
  • Clarify extension type usage: explicitly state when to use ApplicationHealthLinux vs ApplicationHealthWindows, and provide Linux-focused sample JSON.
  • Balance CLI and PowerShell coverage, ensuring Linux commands are not overshadowed by Windows/PowerShell.
  • Add troubleshooting steps for Linux/Bash environments, not just generic or Windows-centric guidance.
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-03-08 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides four methods for accessing Spot Placement Score: Azure portal, REST API, Azure CLI, and Azure PowerShell. The PowerShell example is presented last, after CLI and REST API, and all examples are generic and cross-platform. There is no evidence of Windows-specific tools or patterns being prioritized, nor are Linux equivalents missing. However, the inclusion of Azure PowerShell as a method may be considered a minor Windows-first bias, as PowerShell is most commonly used on Windows, though it is available cross-platform.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform (Windows, Linux, macOS) to avoid perception of Windows-only bias.
  • Ensure that CLI and REST API examples are equally detailed and highlighted, as they are the most platform-neutral.
  • Consider adding explicit notes or links for Linux/macOS users, such as installation instructions for Azure CLI and PowerShell on those platforms.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
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 or in greater detail. There are no Linux-specific shell examples (e.g., Bash), and Windows tools/patterns (PowerShell) are sometimes emphasized. However, Azure CLI is cross-platform and is included throughout, mitigating most bias. No critical networking features are Windows-only, and Linux users can complete all tasks.
Recommendations
  • Present Azure CLI examples before PowerShell to prioritize cross-platform guidance.
  • Ensure all PowerShell examples are matched with equivalent Azure CLI examples.
  • Where possible, include Bash shell scripting examples for Linux users.
  • Explicitly note that Azure CLI works on Linux/macOS/Windows to reassure non-Windows users.
  • Review for any PowerShell-only workflows and add CLI alternatives if missing.
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-08 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 operations, but PowerShell (a Windows-centric tool) is always presented after CLI and before ARM template examples. There are no Linux-specific examples or mentions of Linux tools (e.g., Bash scripting, cloud-init), and PowerShell is given equal prominence to CLI, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Clearly indicate that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are preferred for Linux/macOS users.
  • Add a note at the start of each section clarifying which tools are cross-platform and which are Windows-only.
  • Consider providing Bash shell scripting examples for common tasks, or referencing how to use Azure CLI in Bash for Linux users.
  • Move PowerShell examples to a separate tab labeled 'Windows PowerShell' to clarify its platform specificity.
  • Add explicit guidance for Linux/macOS users, such as 'For Linux/macOS, use Azure CLI or ARM templates.'
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-08 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 (such as feature registration), PowerShell is listed after CLI but receives equal prominence. Portal instructions are also included, which are platform-agnostic. There is a minor bias in the PowerShell examples: the Application Health extension is shown as 'ApplicationHealthWindows', while the CLI example uses 'ApplicationHealthLinux', potentially causing confusion for Linux users. The documentation does not omit Linux-compatible instructions, but Windows tools and patterns are given equal or slightly more prominence than Linux equivalents.
Recommendations
  • Clarify when to use 'ApplicationHealthWindows' vs 'ApplicationHealthLinux' in extension examples, and ensure both are shown for cross-platform parity.
  • Explicitly note that Azure PowerShell is available on Linux/macOS (via PowerShell Core), or link to cross-platform installation instructions.
  • Consider listing Azure CLI examples before PowerShell, as CLI is natively cross-platform.
  • Where possible, provide both Linux and Windows extension examples in PowerShell and CLI sections.
  • Add a brief note about the cross-platform nature of Azure CLI and PowerShell to reduce perceived Windows bias.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all tasks, with the Azure CLI (cross-platform) example always shown before the PowerShell (Windows-centric) example. However, the inclusion of PowerShell examples throughout, and the use of Azure PowerShell cmdlets, may be seen as a mild Windows bias. There are no Linux-specific shell examples (e.g., Bash scripts), but the CLI commands are cross-platform and use a Linux image in the example. No Windows-only tools or patterns are mentioned, and the documentation is not exclusive to Windows.
Recommendations
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • Optionally, add a short Bash script example for common attach/detach operations to further demonstrate Linux parity.
  • Explicitly state that PowerShell examples are for users who prefer PowerShell, and that Azure CLI is recommended for cross-platform use.
  • Ensure that all troubleshooting links and referenced docs have Linux equivalents where relevant.
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-03-08 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Minor Arm Template Bias
Summary
The documentation provides both Windows and Linux parity in terms of supported OS images and Azure CLI/PowerShell examples. However, there are some minor biases: Windows terminology and properties are often mentioned first (e.g., ARM template defaults, property names), PowerShell examples are prominent and sometimes appear before CLI, and Windows-specific configuration details (like drive letters, enableAutomaticUpdates) are discussed in detail. ARM template and Bicep examples default to Windows images, and some explanations use Windows-centric language. Overall, Linux users can complete all tasks, but Windows is subtly prioritized.
Recommendations
  • Ensure ARM template and Bicep examples use both Windows and Linux image defaults, or alternate examples.
  • Where possible, present Azure CLI and PowerShell examples together, or alternate which appears first.
  • Explicitly mention Linux-specific considerations where Windows-specific details are discussed (e.g., drive letter reassignment vs. Linux mount points).
  • Clarify that all features and steps apply equally to Linux and Windows unless otherwise noted.
  • Add a note in sections with Windows-specific properties (like enableAutomaticUpdates) to indicate Linux users can ignore these.
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-08 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 are several instances of Windows bias: PowerShell examples are consistently present and often shown before or alongside CLI/Bash examples; Windows-specific extension types (ApplicationHealthWindows) are used in some sample code and REST payloads, sometimes without clear Linux equivalents; and Windows tools (PowerShell) are given equal or greater prominence compared to Linux tools (Bash/Python). REST examples default to Windows extension types. Overall, Linux users can complete the task, but Windows patterns and tools are frequently prioritized or shown first.
Recommendations
  • Ensure Linux and Windows extension types are both shown in REST and JSON examples, or clarify when to use each.
  • Alternate the order of CLI/Bash and PowerShell examples so Linux tools are not always second.
  • Explicitly state that both ApplicationHealthLinux and ApplicationHealthWindows are supported, and provide clear guidance for Linux users.
  • Provide more Linux-native sample scripts (e.g., Python, Bash) for configuring the health endpoint, and link to Linux-specific troubleshooting resources.
  • In REST and JSON examples, show both Linux and Windows extension types, or use a placeholder to indicate either can be used.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and neutral, describing orchestration modes for Azure Virtual Machine Scale Sets without favoring Windows-specific features. However, there is minor evidence of Windows bias: in the 'Backup and recovery' section, Azure Site Recovery is noted as supported for Flexible orchestration mode 'via PowerShell' only, without mentioning Linux CLI or Bash alternatives. Additionally, the only explicit CLI example uses Azure CLI, which is cross-platform, but the documentation sometimes references PowerShell in the context of Azure Site Recovery, potentially implying Windows-first tooling.
Recommendations
  • Clarify whether Azure Site Recovery for Flexible orchestration mode can be managed via Azure CLI or Bash on Linux/macOS, not just PowerShell.
  • Where PowerShell is mentioned, add equivalent Azure CLI or Bash examples if available.
  • Ensure that all examples and tooling references are explicitly cross-platform unless a feature is truly Windows-only.
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-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is sometimes presented before or alongside CLI examples. The CLI examples are cross-platform, but there are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is referenced throughout, which may create friction for Linux/macOS users. The Azure Resource Manager template section does mention both Linux and Windows, but the overall pattern is to treat PowerShell as a primary method.
Recommendations
  • Ensure Azure CLI examples are presented before PowerShell examples, as CLI is cross-platform.
  • Add explicit Bash shell examples where relevant, especially for scripting tasks.
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide guidance for Linux/macOS users.
  • Consider reducing PowerShell prominence or adding notes for Linux/macOS users about alternative tools.
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-07 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 (e.g., adding a VMSS to Application Gateway) feature more detailed PowerShell scripts. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is referenced as a primary scripting method, which may create friction for Linux/macOS users. However, Azure CLI examples are present throughout, and ARM templates are used for platform-neutral configuration.
Recommendations
  • Present Azure CLI examples before PowerShell to prioritize cross-platform tools.
  • Ensure all PowerShell examples have equivalent Azure CLI examples with equal detail.
  • Explicitly mention that Azure CLI works on Linux/macOS and Windows, and link to installation guides for non-Windows platforms.
  • Consider adding Bash shell scripting examples for common tasks where appropriate.
  • Clarify that PowerShell Core is available cross-platform, but Azure CLI is generally preferred for Linux/macOS users.
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-03-07 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux examples for preparing data disks in Service Fabric clusters, but the Windows example is presented first. There is no evidence of missing Linux examples, PowerShell-heavy bias, or exclusive mention of Windows tools. Both Azure CLI and PowerShell tutorials are referenced equally, and Linux parity is maintained throughout the article.
Recommendations
  • Present Windows and Linux examples side-by-side or alternate their order to avoid implicit prioritization.
  • Explicitly state that both Windows and Linux are supported for all relevant operations.
  • Ensure future updates maintain parity in examples and tool references.
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-07 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 programmatic examples, but consistently lists PowerShell examples immediately after CLI and before ARM templates. Portal instructions are also included. There is no explicit bias toward Windows tools, but PowerShell is presented as a primary scripting option alongside CLI, which may subtly prioritize Windows users. No Linux-specific tools or shell examples (e.g., Bash) are provided, but Azure CLI is cross-platform and sufficient for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI commands are fully supported on Linux/macOS and are the recommended cross-platform option.
  • Consider explicitly mentioning Bash or shell scripting as an alternative for Linux/macOS users, if relevant.
  • If possible, provide brief notes or links for Linux/macOS users about installing and using Azure CLI.
  • Ensure that PowerShell is not presented as the default or primary scripting method for cross-platform scenarios.
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-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation covers both Windows and Linux VM images for Azure Virtual Machine Scale Sets and provides parity in supported OS SKUs and configuration methods. However, there are minor signs of Windows bias: Windows terminology and properties (e.g., drive letters, enableAutomaticUpdates) are mentioned first or exclusively in some requirements, and PowerShell examples are presented before Azure CLI examples. ARM template snippets default to Windows image values. No critical Linux gaps are present, but Windows-centric patterns are slightly prioritized.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • In ARM template and Bicep examples, provide both Windows and Linux image values, or use a neutral example.
  • Where Windows-specific properties (e.g., drive letters, enableAutomaticUpdates) are discussed, clarify Linux equivalents or explicitly state if not applicable.
  • Ensure Linux terminology (e.g., mount points, file systems) is referenced where relevant, not just Windows drive letters.
  • Review for any subtle language that assumes Windows as the default and adjust for neutrality.
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-07 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, including CLI, Bash, PowerShell, and REST API. However, there are several areas where Windows/PowerShell examples are presented first or in greater detail, and Windows-specific extension types (ApplicationHealthWindows) are used in sample code. PowerShell examples are prominent, and Windows tools/patterns (such as PowerShell scripts and extension names) are mentioned alongside or before Linux equivalents. Linux parity is generally good, but minor ordering and naming biases exist.
Recommendations
  • Ensure Linux examples (CLI, Bash, ApplicationHealthLinux) are presented before or alongside Windows/PowerShell examples, especially in critical sections.
  • Clarify in sample code and tables that both ApplicationHealthLinux and ApplicationHealthWindows are supported, and provide explicit Linux-focused examples where possible.
  • Review ordering of tabs and examples to avoid Windows-first bias; alternate or group by OS where appropriate.
  • Expand Bash/Linux sample scripts to match the detail and completeness of PowerShell examples.
  • Explicitly mention macOS compatibility where relevant (e.g., Bash, Python examples).
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-07 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides a comprehensive overview of orchestration modes for Azure Virtual Machine Scale Sets and is largely platform-neutral. However, in the 'Backup and recovery' section, Azure Site Recovery is noted as supported 'via PowerShell' for Flexible orchestration mode, without mentioning Linux CLI or portal alternatives. Additionally, the only explicit CLI example uses Azure CLI, which is cross-platform, but the PowerShell mention appears before any Linux equivalent. Overall, the documentation does not heavily favor Windows, but there is a minor tendency to mention Windows/PowerShell tools first.
Recommendations
  • Clarify that Azure Site Recovery can be managed via Azure CLI and Portal, not just PowerShell, for Linux/macOS users.
  • Where PowerShell is mentioned, also provide Azure CLI or portal instructions/examples if available.
  • Ensure examples and tool references are presented in a platform-neutral order or explicitly state cross-platform support.
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-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI examples, and in some sections (such as updating scale sets), PowerShell is listed before REST API and after CLI. There is no explicit Linux shell example (e.g., Bash), and PowerShell is a Windows-centric tool, though it is now cross-platform. The CLI example uses az CLI, which is cross-platform, but there are no explicit Linux/macOS shell commands or notes about Linux-specific considerations. The Resource Manager template section references both Linux and Windows getting started articles, which is positive for parity. Overall, the bias is minor and mostly in the ordering and prominence of PowerShell.
Recommendations
  • Ensure that CLI (az CLI) examples are always listed first, as they are cross-platform and preferred for Linux/macOS users.
  • Add explicit Bash shell examples or notes clarifying that Azure CLI commands work on Linux/macOS terminals.
  • Where PowerShell is used, clarify that it is available cross-platform, or provide Bash equivalents if there are any subtle differences.
  • Consider adding a brief section or note for Linux/macOS users to highlight any OS-specific considerations or prerequisites.
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-06 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, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI and REST, and Windows-specific extension names (e.g., ApplicationHealthWindows) are used in PowerShell examples. Portal instructions are platform-neutral, but PowerShell is given equal prominence to CLI, and PowerShell examples use Windows-centric extension types, while CLI examples use Linux-centric types. The ordering of tabs sometimes puts PowerShell before CLI, and Windows tools are referenced throughout.
Recommendations
  • Ensure that Linux and macOS users are equally supported by providing Bash shell examples where relevant, especially for scripting tasks.
  • Clarify that Azure PowerShell can be used cross-platform, but highlight Azure CLI as the preferred tool for Linux/macOS users.
  • In PowerShell examples, explain the difference between ApplicationHealthWindows and ApplicationHealthLinux extensions, and provide both where applicable.
  • Consider ordering CLI examples before PowerShell, or explicitly stating that CLI is recommended for Linux/macOS users.
  • Add a note about cross-platform compatibility for Azure CLI and PowerShell, and link to installation guides for Linux/macOS.
GitHub Create Pull Request
← Previous Page 3 of 11 Next →