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 126-150 of 274 flagged pages
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-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 most tasks, but PowerShell examples are often presented before CLI examples, and some sections (e.g., querying public IPs) give more detailed PowerShell usage. Portal instructions are generic, but scripting examples sometimes favor PowerShell syntax and terminology, which is Windows-centric. However, Linux parity is generally maintained via CLI and ARM template examples.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side or in the same order throughout the document to avoid implicit Windows-first bias.
  • Ensure CLI examples are as detailed as PowerShell examples, especially in sections like querying public IPs.
  • Explicitly note that Azure CLI is cross-platform and encourage its use for Linux/macOS users.
  • Where possible, add Bash script examples for common tasks to further support Linux users.
  • Review tabbed content to ensure CLI tabs are not consistently after PowerShell tabs.
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-26 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, PowerShell examples are shown before or with equal prominence to CLI. The Application Health extension examples use both 'ApplicationHealthLinux' and 'ApplicationHealthWindows', but PowerShell examples default to 'ApplicationHealthWindows', potentially confusing Linux users. Portal instructions are platform-neutral, but PowerShell is a Windows tool and its presence throughout the doc, with no explicit mention of Linux alternatives (e.g., Bash scripts), suggests a mild Windows bias.
Recommendations
  • Ensure that Azure CLI examples are always presented before PowerShell, as CLI is cross-platform.
  • Clarify in PowerShell examples when 'ApplicationHealthWindows' should be used versus 'ApplicationHealthLinux', or provide both variants.
  • Add explicit notes that Azure CLI is recommended for Linux/macOS users.
  • Consider including Bash or shell script snippets for Linux users where relevant.
  • Where PowerShell is used, indicate its Windows-specific nature and suggest CLI for non-Windows users.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides a balanced overview of migrating to Virtual Machine Scale Sets in Flexible orchestration, referencing both Windows and Linux scenarios. However, in the 'Create scalable network connectivity' section, Windows-specific scenarios (Windows VM activation, Windows updates) are mentioned before Linux equivalents (Linux package managers), which may subtly prioritize Windows use cases. All tooling examples (Azure CLI, PowerShell, ARM Template) are cross-platform, and no critical migration steps are Windows-only.
Recommendations
  • When listing common outbound connectivity scenarios, alternate the order or explicitly mention Linux scenarios alongside Windows ones (e.g., 'Windows updates and Linux package manager access').
  • Ensure that examples and troubleshooting links for Linux (e.g., Linux VM activation, package manager connectivity) are provided where relevant.
  • Consider adding explicit Linux-focused migration tips or links, especially for package manager connectivity and OS-specific considerations.
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-26 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 example is cross-platform, the PowerShell example is Windows-centric and is presented immediately after the CLI example. There is no explicit Linux/macOS bias, but PowerShell is highlighted as a primary method, which may create friction for Linux/macOS users. The CLI example is sufficient for Linux parity, but the ordering and prominence of PowerShell may suggest a Windows-first bias.
Recommendations
  • Clearly indicate that Azure CLI is the recommended cross-platform method for Linux/macOS users.
  • Consider placing the CLI example before the PowerShell example, or labeling PowerShell as Windows-specific.
  • Add a note clarifying that PowerShell examples are intended for Windows users, and that CLI works on all platforms.
  • Optionally, provide Bash script examples for Linux users if relevant.
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-26 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 custom metrics and the application health extension on Azure Virtual Machine Scale Sets. However, in several sections, Windows/PowerShell examples are presented before or alongside Linux equivalents, and PowerShell usage is prominent. The REST and Azure CLI examples are platform-neutral, but PowerShell is given equal or greater prominence than Bash in some areas. The extension configuration examples use both ApplicationHealthLinux and ApplicationHealthWindows, maintaining parity, but the PowerShell example for installing the extension uses ApplicationHealthWindows by default, while the CLI example uses ApplicationHealthLinux.
Recommendations
  • Ensure Linux/Bash examples are always presented before or alongside Windows/PowerShell examples, especially in critical sections.
  • In PowerShell examples, clarify when ApplicationHealthWindows should be used versus ApplicationHealthLinux, and provide parallel Linux-focused examples.
  • Where possible, add explicit Linux-centric troubleshooting steps and highlight cross-platform commands.
  • Review sample code and ensure variable names and extension types are not Windows-centric by default.
  • Consider adding a table or section summarizing parity between Windows and Linux for extension configuration and custom metrics.
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as 'Use Azure PowerShell'), Windows-centric tooling is highlighted separately. The ordering of example sections sometimes places PowerShell before ARM templates, and the PowerShell example uses Windows-style syntax. There are no missing Linux examples, but the documentation could better emphasize cross-platform CLI usage and clarify that PowerShell is primarily for Windows users.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and recommended for Linux/macOS users, while PowerShell is primarily for Windows.
  • Consider placing Azure CLI examples before PowerShell examples to reinforce CLI as the default for Linux/macOS.
  • Add clarifying statements in PowerShell sections that it is Windows-centric.
  • Ensure that all example scripts (especially in update sections) are available in CLI format and shown first.
  • Where possible, add bash shell script snippets for Linux users, or link to Linux-specific quickstart guides.
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-25 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, in several sections, Windows/PowerShell examples are presented before Linux/Bash equivalents, and Windows-specific extension types (ApplicationHealthWindows) are used in sample code. PowerShell scripts are detailed and prominent, and Windows tools/terminology (e.g., PowerShell, Windows extension type) are mentioned alongside or before Linux options. REST and Azure CLI examples are cross-platform, but the ordering and emphasis slightly favor Windows/PowerShell.
Recommendations
  • Ensure Linux/Bash examples are presented before or alongside Windows/PowerShell examples, especially in critical configuration sections.
  • Explicitly clarify that both ApplicationHealthLinux and ApplicationHealthWindows extension types are supported, and provide sample code for both.
  • Where possible, use neutral terminology (e.g., 'application health extension for Linux/Windows') and avoid defaulting to Windows-specific names in generic examples.
  • Balance the depth and detail of Bash/Python and PowerShell sample scripts.
  • Add troubleshooting examples for Linux (e.g., systemd, firewall rules) alongside Windows troubleshooting steps.
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-25 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 in some sections, PowerShell examples reference Windows-specific extension types (e.g., ApplicationHealthWindows). Portal instructions are platform-neutral, but PowerShell is a Windows tool and is shown as a primary option. Azure CLI examples are present and use Linux images, but PowerShell examples reference Windows extension types, and the PowerShell section is not clearly marked as Windows-only. REST API examples are platform-neutral.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, but highlight that it is most commonly used on Windows.
  • In PowerShell examples, use both ApplicationHealthLinux and ApplicationHealthWindows extension types, or explain when to use each.
  • Ensure that Linux/macOS users are aware that Azure CLI is fully supported and often preferred for cross-platform scenarios.
  • Consider showing Azure CLI examples before PowerShell, or explicitly state that PowerShell is a Windows-centric tool.
  • Add a note in PowerShell sections about compatibility on Linux/macOS (via PowerShell Core), and clarify any Windows-specific limitations.
  • Where possible, provide Linux-specific guidance or highlight parity between Windows and Linux VMSS configurations.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all operations (attach, detach, move), but consistently includes PowerShell examples alongside CLI and portal instructions. PowerShell is a Windows-centric tool, and its inclusion may signal a Windows bias. Additionally, PowerShell examples are shown after CLI, but their presence may create friction for Linux/macOS users who do not use PowerShell. However, Azure CLI examples are present and use Linux-friendly syntax (e.g., Ubuntu image), mitigating the impact.
Recommendations
  • Clarify that Azure PowerShell is cross-platform, or note that Linux/macOS users should use Azure CLI.
  • Consider providing Bash shell script examples for common operations, or explicitly state that Azure CLI is recommended for Linux/macOS users.
  • If PowerShell is included, add a note that it is available on Linux/macOS, or link to installation instructions.
  • Ensure that all examples are equally accessible to Linux/macOS users, and avoid implying PowerShell is required.
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-25 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 and ARM template examples are cross-platform, the PowerShell example is Windows-specific and is given equal prominence. There is mild Windows bias in the inclusion of PowerShell as a primary example, and PowerShell is listed after CLI but before ARM templates. However, Linux/macOS users can use the Azure CLI and ARM templates without issue, and no critical steps are Windows-only.
Recommendations
  • Clarify that Azure CLI and ARM template methods are fully cross-platform and suitable for Linux/macOS users.
  • Consider adding Bash shell scripting examples for Azure CLI to reinforce Linux parity.
  • Explicitly note that PowerShell is Windows-centric and suggest CLI/ARM template for non-Windows environments.
  • Ensure ordering of examples does not imply Windows preference (e.g., list CLI first, then PowerShell).
GitHub Create Pull Request
Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md
Low Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as updating scale sets), PowerShell is listed before REST API and after CLI. There is a slight 'windows_first' bias in the ordering of example methods, as PowerShell is mentioned before ARM templates and REST API, and the PowerShell section is detailed. There are no missing Linux examples, as Azure CLI and ARM templates are cross-platform and the documentation references Linux-specific template guides. No Windows-only tools or patterns are used, and the page is not Windows-specific.
Recommendations
  • Consider listing Azure CLI examples before PowerShell in all sections, as CLI is more universally available across platforms.
  • Explicitly note that Azure CLI and ARM templates are cross-platform and suitable for Linux/macOS users.
  • Where PowerShell is shown, clarify that it is primarily for Windows users and suggest CLI for Linux/macOS.
  • Ensure that all example scripts and commands are available in CLI and ARM template formats, and reference Linux/macOS compatibility where relevant.
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-25 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 examples are consistently presented alongside CLI and portal options, sometimes immediately after CLI. While Azure CLI is cross-platform, PowerShell is primarily used on Windows, and its inclusion may suggest a Windows-centric approach. However, Linux/macOS users can fully use the Azure CLI examples, and there are no Windows-only tools or commands required. The order of examples sometimes puts PowerShell before ARM templates, but not before CLI.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider adding Bash shell script examples or clarifying that CLI commands work on all OSes.
  • If possible, mention that PowerShell Core is available on Linux/macOS, but CLI is preferred for cross-platform compatibility.
  • Ensure that CLI examples are always presented before PowerShell, and clarify OS compatibility for each tool.
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-25 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. In some sections, PowerShell is the only example given (e.g., querying public IPs), or CLI and PowerShell are both offered but PowerShell is listed 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, though minor ordering bias exists.
Recommendations
  • Present CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Where PowerShell is used exclusively, ensure a CLI equivalent is provided.
  • Explicitly note that Azure CLI commands work on Linux/macOS and Windows.
  • Consider adding Bash script examples for advanced scenarios, if relevant.
  • Review tab ordering to ensure CLI is the default or first tab.
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-25 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 generally platform-neutral. However, in the 'Managed Identity' row of the comparison table, the link for configuring User Assigned Identity points to a Windows VMSS-specific guide, and the section does not mention Linux explicitly. Additionally, the Azure Site Recovery feature is noted as supported 'via PowerShell' for Flexible orchestration, which may imply a Windows-centric tool, though PowerShell is cross-platform. No explicit Linux/macOS examples or tools are provided, but the overall content is not strongly biased toward Windows.
Recommendations
  • Add links and examples for configuring Managed Identity on Linux VMSS, not just Windows.
  • Clarify that Azure Site Recovery can be managed via Azure CLI or portal in addition to PowerShell, and provide Linux-friendly instructions.
  • Where PowerShell is mentioned, note its cross-platform availability and provide Azure CLI equivalents where possible.
  • Ensure that all example commands (e.g., az vm create) are platform-neutral and clarify their applicability to both Linux and Windows VMSS.
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-23 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 signs of Windows bias: PowerShell examples are consistently present and sometimes shown before Bash/Linux examples, and Windows-specific extension types (ApplicationHealthWindows) are used in several code snippets. The PowerShell section is detailed and prominent, and Windows tools (PowerShell cmdlets) are referenced throughout. Linux examples are present but not always as detailed or prominent as their Windows counterparts.
Recommendations
  • Ensure Linux/Bash examples are always shown alongside PowerShell, and consider showing Bash first or equally.
  • Provide more detailed Linux examples, especially for extension installation and querying, matching the depth of PowerShell examples.
  • Clarify when to use ApplicationHealthLinux vs ApplicationHealthWindows in all code snippets and tables.
  • Add troubleshooting steps for Linux environments (e.g., systemd, firewall rules, SELinux/AppArmor considerations).
  • Explicitly state that all features are supported on both Linux and Windows unless otherwise noted.
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-23 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 operations, but PowerShell examples are often presented before CLI examples, and some sections (such as querying public IPs) show PowerShell commands first or in greater detail. While Linux parity is generally good, the ordering and prominence of PowerShell may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI and PowerShell examples side-by-side or in parallel tabs, ensuring CLI (cross-platform) is not secondary.
  • Where both CLI and PowerShell are available, alternate which is shown first or default to CLI for cross-platform parity.
  • Ensure all PowerShell examples have equivalent CLI examples, and vice versa.
  • Explicitly note that Azure CLI works on Windows, Linux, and macOS to reinforce cross-platform support.
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-23 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 major operations, but PowerShell (a Windows-centric tool) is consistently presented as a first-class citizen alongside CLI, and in some sections, PowerShell examples are shown before or at parity with CLI. There are no explicit Linux shell script examples, but the CLI examples are cross-platform. The PowerShell examples use Windows-specific extension types (e.g., ApplicationHealthWindows), which may confuse Linux users. However, Linux users can complete all tasks using the Azure CLI or REST API, and the documentation does not block Linux/macOS users.
Recommendations
  • Clarify that Azure CLI examples are fully cross-platform and recommended for Linux/macOS users.
  • In PowerShell examples, clarify when an extension type (e.g., ApplicationHealthWindows) is for Windows VMs and provide the Linux equivalent (e.g., ApplicationHealthLinux) if applicable.
  • Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Explicitly state that all features are available to both Windows and Linux VMSS, unless otherwise noted.
  • Add a note in the prerequisites or intro about tool parity for Linux/macOS users.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation provides migration guidance for Azure Virtual Machine Scale Sets in Flexible orchestration. While the topic is cross-platform, there are subtle signs of Windows bias: Windows/PowerShell is mentioned alongside Azure CLI, and Windows-specific scenarios (activation, updates) are listed before Linux equivalents. However, Linux is referenced (e.g., package managers), and most examples use Azure CLI, which is cross-platform. No critical migration steps are Windows-only, but minor friction exists for Linux/macOS users.
Recommendations
  • Ensure Linux-specific migration scenarios (e.g., package manager access, SSH configuration) are given equal prominence alongside Windows scenarios.
  • Provide explicit Linux/macOS command examples (e.g., Bash, Azure CLI) before or alongside PowerShell examples.
  • Mention Linux tools and patterns (such as cloud-init, SSH, package managers) in relevant sections.
  • Clarify that Azure CLI is cross-platform and recommend it as the default for scripting unless Windows-specific features are required.
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-23 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 consistently presents PowerShell examples immediately after CLI and before ARM template examples. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. However, Azure CLI is cross-platform and all tasks can be completed with it, so Linux/macOS users are not blocked. There are no Windows-only tools or patterns mentioned, and no missing Linux examples.
Recommendations
  • Consider listing Azure CLI examples before PowerShell in each section, as CLI is cross-platform and more inclusive for Linux/macOS users.
  • Explicitly note that Azure CLI works on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
  • If possible, add Bash shell script snippets for common tasks to further improve Linux parity.
  • Ensure screenshots and portal instructions are not Windows-specific (they are not in this doc).
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-23 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 order of example links and references: the Managed Identity section links to a Windows VMSS portal example, and some references (such as Azure Site Recovery via PowerShell) mention Windows tools first. No critical sections are Windows-only, and Linux users can complete all tasks described.
Recommendations
  • Add explicit Linux example links alongside Windows ones, especially in sections referencing Managed Identity or Azure Site Recovery.
  • Clarify that Azure CLI and REST API examples work for both Linux and Windows users.
  • Where PowerShell is mentioned, also reference Bash/CLI equivalents for parity.
  • Ensure that all feature tables and comparisons highlight Linux support as clearly as Windows 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-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and in some sections (such as updating scale sets), PowerShell is presented before REST API and after CLI, with no explicit Bash or Linux shell examples. The CLI examples are cross-platform, but PowerShell is Windows-centric. There are no Linux-specific command-line examples (e.g., Bash scripts), and the documentation does not mention Linux tools or patterns. The Resource Manager template section references both Linux and Windows, but the overall example flow slightly favors Windows tools.
Recommendations
  • Add explicit Bash shell examples for Linux users, especially for update operations.
  • Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Consider mentioning or linking to Linux-specific quickstart guides or scripts where appropriate.
  • Ensure that PowerShell examples are not shown before CLI or REST API examples unless the feature is Windows-only.
  • Add notes or callouts for Linux/macOS users where PowerShell is referenced.
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-23 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 examples for the Azure Portal, Azure CLI, PowerShell, and ARM templates. The PowerShell example is presented after the CLI example, but both are given equal prominence. There is no evidence of Windows-only tools or patterns being mentioned exclusively, and the CLI example is cross-platform. However, PowerShell is a Windows-centric tool, and its inclusion may suggest a slight Windows bias, especially since no explicit mention is made of Bash or Linux-specific scripting. The ordering of examples (CLI before PowerShell) minimizes this bias, but the presence of PowerShell as a primary example is notable.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
  • Consider adding Bash shell scripting examples or explicitly noting that Azure CLI works on Linux/macOS.
  • If relevant, mention any Linux-specific considerations for VMSS upgrades (e.g., health extensions or probes).
  • Ensure parity in troubleshooting or advanced configuration sections, if present, for both Windows and Linux environments.
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-22 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. Portal instructions are platform-neutral, but PowerShell is emphasized in several places. No critical features are Windows-only, and Linux parity is generally maintained, but the ordering and emphasis subtly favor Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by Linux/macOS users.
  • Ensure all PowerShell examples have equivalent Azure CLI examples, especially for querying and updating resources.
  • Add explicit notes clarifying that Azure CLI commands work on Linux, macOS, and Windows.
  • Where possible, highlight cross-platform tools and workflows first.
  • Consider adding Bash script examples for advanced scenarios, if relevant.
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-22 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 tools and patterns are mentioned first or in more detail. For example, in the 'Install the application health extension' section, PowerShell is presented immediately after CLI, and the PowerShell example is more verbose and detailed. REST examples use 'ApplicationHealthWindows' as the extension type, even though Linux is also supported. In querying and troubleshooting, PowerShell is consistently given as a primary option alongside CLI and REST, sometimes with more explanation. The documentation does not omit Linux examples, but Windows/PowerShell tools and terminology are often prioritized or presented first.
Recommendations
  • Ensure Linux and macOS examples (Bash, Python, CLI) are presented before or alongside Windows/PowerShell examples, especially in critical sections.
  • Use 'ApplicationHealthLinux' as the default extension type in generic examples, or show both Linux and Windows variants equally.
  • Balance the detail and explanation between Bash/Python and PowerShell examples, so Linux users receive equally comprehensive guidance.
  • Where possible, clarify cross-platform support and highlight any OS-specific requirements or differences.
  • Consider adding macOS-specific notes or examples if relevant, especially for CLI usage.
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-22 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 configuring rolling upgrades on Virtual Machine Scale Sets. However, PowerShell examples are present throughout and in every major section, and in some cases, PowerShell is listed before ARM template examples. There is a slight Windows bias due to the heavy inclusion of PowerShell, which is primarily used on Windows, but Azure CLI examples (cross-platform) are also provided. No critical Linux/macOS parity issues are found, as all tasks can be completed using Azure CLI.
Recommendations
  • Ensure Azure CLI examples are always listed before PowerShell examples, as CLI is cross-platform.
  • Clarify that PowerShell is primarily for Windows users and Azure CLI is recommended for Linux/macOS.
  • Consider adding Bash shell scripting examples for advanced automation scenarios.
  • Explicitly mention that all Azure CLI commands work on Linux/macOS and Windows.
  • If possible, add a note about using Azure Cloud Shell, which is platform-agnostic.
GitHub Create Pull Request
← Previous Page 6 of 11 Next →