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 151-175 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-02-22 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 sections are cross-platform, the PowerShell example is Windows-specific and is given equal prominence. The ordering of examples places PowerShell immediately after CLI, which may subtly prioritize Windows tools. However, no critical steps are Windows-only, and Linux/macOS users can complete all tasks using CLI or ARM templates.
Recommendations
  • Explicitly note that Azure CLI and ARM templates are fully cross-platform and suitable for Linux/macOS users.
  • Consider listing CLI examples before PowerShell, or grouping CLI and ARM Template as 'cross-platform' options.
  • Add a brief note in the PowerShell section indicating it is Windows-only, for clarity.
  • If possible, add Bash shell scripting examples for Azure CLI to further reinforce Linux parity.
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-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 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 (e.g., 'Create zone spanning or zonal scale sets'), PowerShell is listed before Resource Manager templates. There is a slight 'windows_first' bias in the ordering of example methods and in the inclusion of PowerShell examples, which are primarily relevant to Windows users. All CLI examples are cross-platform and there are links to both Linux and Windows ARM template guides, but no explicit Linux/macOS shell examples (e.g., Bash) are provided.
Recommendations
  • Ensure that Azure CLI examples are always listed before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
  • Consider adding explicit Bash shell examples or clarifying that Azure CLI commands work identically on Linux/macOS.
  • Where PowerShell is used, note that it is primarily for Windows users and suggest CLI for Linux/macOS.
  • Review the ordering of sections to avoid subtle 'windows_first' bias (e.g., PowerShell before ARM templates).
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-21 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 (a Windows-centric tool) is consistently presented alongside CLI, and in some sections, PowerShell examples are shown before or with equal prominence to CLI. There are no Linux-specific shell examples (e.g., Bash), but Azure CLI is cross-platform. No Windows-only tools or patterns are mentioned, and the content is not Windows-specific.
Recommendations
  • Explicitly note that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI for cross-platform users.
  • Consider showing Azure CLI examples before PowerShell, or labeling PowerShell as 'Windows only' where appropriate.
  • Add a brief note for Linux/macOS users clarifying that PowerShell examples are for Windows, and Azure CLI is the preferred option for non-Windows environments.
  • If relevant, include Bash scripting examples or highlight CLI usage in Linux/macOS terminals.
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-21 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 'Create zone spanning or zonal scale sets'), PowerShell is listed before ARM template examples. There is a slight bias in listing Windows-oriented tools (PowerShell) alongside cross-platform tools (CLI), and PowerShell examples are detailed and prominent. There are no missing Linux examples, as CLI and ARM templates are cross-platform, and the portal instructions are platform-agnostic.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users, while PowerShell is primarily for Windows (though PowerShell Core is available for Linux/macOS).
  • Consider listing Azure CLI examples before PowerShell examples to emphasize Linux parity.
  • Add clarifying notes about the platform compatibility of each tool.
  • Ensure that ARM template examples reference both Linux and Windows quick-start links equally, as is already done.
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-02-21 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides platform-specific instructions for accessing the Spot Placement Score via Azure CLI and Azure PowerShell, with PowerShell examples appearing after CLI. However, both CLI and PowerShell are cross-platform tools, and no Windows-specific tools or patterns are prioritized. No explicit Windows bias is present, but minor 'windows_first' bias is detected as PowerShell is listed after CLI, which is often associated with Windows, though both are available on Linux/macOS.
Recommendations
  • Clarify that Azure CLI and Azure PowerShell are available on Linux/macOS as well as Windows.
  • Consider adding explicit notes or links to installation guides for Azure CLI and PowerShell on Linux/macOS.
  • If possible, provide sample commands for Bash or other Linux-native shells to reinforce parity.
  • Ensure that all instructions and examples are platform-neutral unless a platform-specific difference exists.
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-21 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, CLI, PowerShell, and ARM templates. While the CLI example is cross-platform, the PowerShell example is Windows-specific and is given equal prominence. There is no explicit Linux bias, but PowerShell is highlighted as a main method, which may create friction for Linux/macOS users. The CLI example is not shown first; Portal is, then CLI, then PowerShell, which is a minor 'windows_first' bias.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
  • Consider adding Bash script examples or noting that PowerShell is Windows-specific.
  • Explicitly mention that PowerShell examples are for Windows users, and CLI is recommended for Linux/macOS.
  • Ensure parity in instructions for Linux/macOS users, such as troubleshooting or environment setup notes.
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-21 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 areas where Windows bias is evident: PowerShell examples are often presented before or alongside Bash, Windows-specific extension types (ApplicationHealthWindows) are used in sample code, and Windows tools (PowerShell cmdlets) are given equal prominence to cross-platform CLI commands. The REST API examples use ApplicationHealthWindows as the default extension type, even though ApplicationHealthLinux is also supported. The documentation does not omit Linux examples, but Windows terminology and tools are frequently mentioned first or in parallel, creating minor friction for Linux/macOS users.
Recommendations
  • Ensure Linux examples (Bash/Python) are shown before or equally with Windows/PowerShell examples, especially in critical sections.
  • Use ApplicationHealthLinux as the default extension type in generic sample code, or show both Linux and Windows variants.
  • Clarify in REST/CLI examples that both ApplicationHealthLinux and ApplicationHealthWindows are supported, and provide explicit Linux-focused samples.
  • Where possible, avoid using Windows-specific terminology or tools unless necessary, and always provide Linux equivalents.
  • Consider grouping examples by platform, or using tabs to clearly distinguish Linux and Windows workflows.
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-20 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). However, PowerShell examples are always present and are shown alongside CLI, which is cross-platform, but PowerShell is primarily used by Windows users. The CLI examples use Ubuntu images, but the PowerShell examples are more verbose and detailed, potentially giving Windows users more guidance. The order of examples is Azure portal, Azure CLI, then Azure PowerShell, which is a minor 'windows_first' bias. No Windows-only tools or patterns are mentioned, and Linux parity is generally good.
Recommendations
  • Ensure that Azure CLI examples are as detailed as PowerShell examples, especially for networking and advanced options.
  • Add explicit notes that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform tool.
  • Consider providing Bash shell script examples for common Linux workflows, or clarify that Azure CLI covers all Linux/macOS needs.
  • If PowerShell is used, mention that PowerShell Core is available cross-platform, but most Linux users will prefer Azure CLI.
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-20 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, monitoring, canceling, and restarting rolling upgrades on Virtual Machine Scale Sets. However, PowerShell examples are given equal prominence to CLI examples, and in some cases, PowerShell is presented immediately after CLI, which may subtly favor Windows users. There are no Linux-specific examples or explicit mentions of Linux tools or shell environments, but the Azure CLI is cross-platform and suitable for Linux/macOS users. The documentation does not use Windows-only tools or patterns, but could improve parity by clarifying CLI usage on Linux/macOS and avoiding implicit Windows-first ordering.
Recommendations
  • Explicitly state that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
  • Consider mentioning Bash or shell environments for Linux/macOS users when showing CLI examples.
  • Add a note for PowerShell examples indicating they are primarily for Windows users, while CLI is recommended for Linux/macOS.
  • If possible, provide sample Bash scripts or highlight CLI usage in Linux/macOS terminals.
  • Ensure CLI examples are shown before PowerShell, or clarify that both are equally supported.
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-20 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' and update operations), PowerShell is presented before REST API or ARM template examples. There is minor 'windows_first' bias, as PowerShell is a Windows-centric tool and is featured alongside CLI, but Linux users are not excluded from completing the tasks. All critical operations are covered with cross-platform tools (Azure CLI, ARM templates, REST API), and explicit Linux/Windows ARM template links are provided.
Recommendations
  • Ensure Azure CLI examples are always presented before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
  • Add explicit notes or links for Linux/macOS users where PowerShell is mentioned, suggesting Azure CLI as the preferred method.
  • Consider including Bash shell script examples where appropriate, especially for automation scenarios.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references Azure CLI, Azure PowerShell, and ARM templates for creating and migrating Virtual Machine Scale Sets, but does not provide explicit Linux/bash shell examples or mention Linux tools. Azure PowerShell is mentioned alongside Azure CLI, but PowerShell is a Windows-centric tool. Some example commands are shown in Azure CLI, which is cross-platform, but there are no explicit bash or Linux-specific instructions. Windows-specific scenarios (activation, updates) are listed before Linux equivalents, and Windows-centric tasks are described in more detail.
Recommendations
  • Provide explicit bash/Linux shell examples for key tasks, such as VM creation and migration.
  • Mention Azure CLI as the primary cross-platform tool, and clarify PowerShell is optional for Windows users.
  • When listing connectivity requirements, mention Linux package manager access before or alongside Windows activation and updates.
  • Add examples or references for Linux-specific migration considerations, such as handling SSH keys or Linux VM extensions.
  • Ensure parity in troubleshooting and operational guidance for both Windows and Linux VMs.
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-19 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), but the PowerShell examples are always present and sometimes more detailed. Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) is standard, but the PowerShell examples are shown after CLI, not before. No Windows-only tools or patterns are mentioned, and Linux parity is generally maintained. However, some troubleshooting links reference Windows-specific documentation (e.g., proximity placement groups), and PowerShell examples may be less relevant for Linux/macOS users.
Recommendations
  • Ensure all troubleshooting links reference both Linux and Windows documentation where applicable.
  • Clarify that Azure PowerShell can be used on Linux/macOS (via PowerShell Core), or provide Bash script examples for common tasks.
  • Consider adding a note that Azure CLI is recommended for Linux/macOS users.
  • Review troubleshooting steps to ensure they are not Windows-centric (e.g., disk conversion, proximity placement group removal).
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-19 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 in some cases, PowerShell examples are more detailed. There are no Linux-specific shell examples (e.g., Bash scripts), and PowerShell is listed before CLI in tabbed sections. However, Azure CLI is cross-platform and present for all major tasks, so Linux/macOS users are not blocked.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Where possible, add explicit Bash shell script examples for common tasks, especially for querying or scripting.
  • Clarify in the introduction that Azure CLI is fully supported on Linux/macOS and is recommended for cross-platform automation.
  • Ensure that all PowerShell examples have equivalent Azure CLI examples, and vice versa.
  • Consider adding a short section or note for Linux/macOS users highlighting CLI usage and installation.
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-19 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 'Update scale set to add availability zones'), PowerShell is listed before REST API and after CLI. The CLI examples are cross-platform, but PowerShell is Windows-centric. There is a minor bias in the ordering and prominence of PowerShell, and the documentation does not explicitly mention Linux/macOS compatibility or alternatives for PowerShell users. The ARM template section links to both Linux and Windows getting started articles, which is positive for parity.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell in all sections to reinforce cross-platform parity.
  • Add brief notes clarifying that Azure PowerShell is primarily for Windows users, and that CLI is the preferred method for Linux/macOS.
  • Ensure that all critical workflows have CLI examples and that CLI is not omitted in any section.
  • Optionally, add Bash shell script snippets or highlight Linux-specific considerations 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-19 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 as a first-class option. PowerShell is primarily a Windows tool, and its prominence may create friction for Linux/macOS users. However, all critical tasks are covered with Azure CLI examples, which are cross-platform, and no Windows-only tools or patterns are used exclusively. The ordering of examples sometimes puts PowerShell before ARM templates, but not before CLI. No Linux-specific tools or shell examples are missing, but Bash or Linux-native scripting is not referenced.
Recommendations
  • Consider explicitly mentioning that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add Bash shell scripting examples or clarify that Azure CLI commands can be run in Bash or other Linux shells.
  • Where PowerShell is referenced, note its availability on Linux/macOS, or link to installation instructions for PowerShell Core.
  • Ensure CLI examples are always shown before PowerShell, or provide a clear 'Linux/macOS' and 'Windows' labeling for each section.
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-19 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 included alongside CLI and Portal, and the CLI example is generic (az CLI, which works cross-platform). However, the PowerShell example is presented as a full script, and the section is labeled explicitly as 'PowerShell', which may signal Windows bias. Additionally, the PowerShell section appears immediately after the CLI section, which is standard but can be perceived as 'windows_first' bias since no Linux/macOS-specific shell examples (e.g., Bash) are provided.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and work on Windows, Linux, and macOS.
  • Consider adding Bash shell examples for Linux/macOS users, especially if there are nuances in scripting or environment variables.
  • Explicitly state that PowerShell is available cross-platform (PowerShell Core), or clarify if the example is Windows PowerShell only.
  • Ensure parity by mentioning that all configuration steps can be performed from any OS using Azure CLI or ARM templates.
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-19 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 response, as well as Azure CLI, PowerShell, and REST API instructions for extension installation and querying. However, there are several instances where Windows/PowerShell examples are presented before Linux/Bash equivalents, and Windows-specific extension types (ApplicationHealthWindows) are used in sample code. PowerShell examples are detailed and prominent, and Windows tools/patterns (e.g., PowerShell HTTP server) are given equal or greater emphasis compared to Linux. The documentation does not omit Linux examples, but Windows bias is evident in ordering and tool selection.
Recommendations
  • Present Linux/Bash examples before Windows/PowerShell examples, or alternate ordering to avoid implicit prioritization.
  • Ensure all sample code and extension configuration examples clearly show both ApplicationHealthLinux and ApplicationHealthWindows types, or use a neutral placeholder.
  • Expand Linux-specific troubleshooting and verification steps (e.g., using systemd, firewalld, or other common Linux tools for endpoint setup and firewall configuration).
  • Explicitly state that both Linux and Windows VMSS instances are supported, and clarify any OS-specific requirements.
  • Where possible, provide cross-platform scripts or highlight platform differences in a dedicated section.
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-18 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 after CLI examples, and the PowerShell extension configuration uses 'ApplicationHealthWindows' as the type, even in contexts where Linux is clearly supported. Portal instructions are platform-neutral, but PowerShell is a Windows tool and its prominence, as well as the lack of explicit Linux/macOS PowerShell guidance, creates a mild Windows bias. The CLI examples use Ubuntu images and 'ApplicationHealthLinux', showing Linux support, but PowerShell examples do not clarify Linux usage.
Recommendations
  • Clarify that Azure PowerShell can be used cross-platform (Windows, Linux, macOS) and provide explicit instructions/examples for Linux/macOS users if relevant.
  • In PowerShell extension examples, show both 'ApplicationHealthWindows' and 'ApplicationHealthLinux' usage, or explain when to use each.
  • Consider presenting CLI (Linux-friendly) examples before PowerShell (Windows-centric) examples, or explicitly state parity.
  • Add a note that both Azure CLI and PowerShell are available on all major platforms, and link to installation guides for Linux/macOS.
  • Ensure that screenshots and portal instructions do not assume Windows-only environments.
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-18 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 Flexible orchestration mode in Azure Virtual Machine Scale Sets. However, in the 'Create scalable network connectivity' section, Windows-specific scenarios (Windows VM activation, Windows updates) are mentioned before Linux equivalents (Linux package managers). There are no PowerShell-heavy examples, Windows tools, or missing Linux examples; the CLI and ARM Template are referenced alongside PowerShell, and all migration steps are generic to Azure VMs regardless of OS.
Recommendations
  • When listing common outbound connectivity scenarios, mention Linux package manager access before or alongside Windows activation and updates to avoid subtle Windows-first bias.
  • Ensure that any example commands or scripts (such as az vm create) are shown in both Azure CLI and PowerShell where relevant, and clarify OS-agnostic steps.
  • If referencing troubleshooting or update scenarios, provide links or notes for both Windows and Linux VM activation/update documentation.
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-18 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 presents PowerShell examples alongside CLI and portal instructions. PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias, especially since Linux/macOS users typically use Azure CLI or REST APIs. Additionally, PowerShell examples are sometimes more detailed than their CLI counterparts. However, Azure CLI examples are present and use Linux-friendly syntax (e.g., Ubuntu image), mitigating the bias.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows. Consider linking to instructions for installing Azure PowerShell on Linux/macOS.
  • Ensure that Azure CLI examples are as detailed as PowerShell examples, especially for networking and advanced options.
  • Consider adding REST API or ARM template examples for users who prefer those methods, especially on Linux/macOS.
  • Explicitly state that all operations can be performed from Linux/macOS using Azure CLI, and highlight any differences if present.
  • If possible, reorder examples to show Azure CLI before PowerShell, or alternate the order to avoid 'windows_first' bias.
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-18 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 or in greater detail. Portal instructions are also present, but Linux/macOS parity is generally good since Azure CLI is cross-platform and included for all major operations. However, the ordering and prominence of PowerShell examples may create minor friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell examples in each section to prioritize cross-platform tools.
  • Ensure that every PowerShell example is matched with an Azure CLI example, especially for querying and updating resources.
  • Explicitly note that Azure CLI is recommended for Linux/macOS users, and clarify any PowerShell-specific steps.
  • Consider adding Bash script snippets where appropriate, especially for advanced networking scenarios.
  • Review the documentation for any subtle language that implies PowerShell is the default or preferred tool.
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-18 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-specific tools, patterns, or terminology are presented first or more prominently. For example, PowerShell examples and Windows extension types are often shown before or alongside Linux equivalents, and the REST/ARM examples default to 'ApplicationHealthWindows'. The PowerShell section is detailed and uses Windows-centric variable names and extension types. The CLI examples are cross-platform, but Windows tools and patterns are mentioned at least as much as Linux ones, sometimes before them.
Recommendations
  • Ensure Linux and Windows extension types are presented equally in all code samples and explanations. For example, REST/ARM examples should show both 'ApplicationHealthLinux' and 'ApplicationHealthWindows' or clarify when to use each.
  • Alternate the order of Bash and PowerShell examples, or present Bash first to avoid implicit Windows-first bias.
  • Clarify which examples are for Linux and which are for Windows, especially in sections where only one is shown.
  • Add explicit Linux-focused troubleshooting and verification steps, such as using systemd or other Linux-native tools for health endpoint management.
  • Where possible, use neutral variable names and avoid Windows-centric naming in generic examples.
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-18 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 lists PowerShell examples after CLI and includes detailed PowerShell scripts. While Azure CLI is cross-platform, PowerShell examples are Windows-centric and may not be as relevant for Linux/macOS users. There are no Linux-specific tools or shell examples (e.g., Bash), and the documentation does not mention Linux/macOS explicitly, which may create minor friction for non-Windows users.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI as the preferred cross-platform method.
  • Add Bash shell examples or note that Azure CLI commands can be run in Bash/Terminal on Linux/macOS.
  • Consider reordering tabs so CLI appears first, emphasizing its cross-platform nature.
  • Explicitly state that PowerShell examples are optional and primarily for Windows users.
  • Mention prerequisites for CLI usage on Linux/macOS (e.g., installation links).
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-18 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides a conceptual overview and feature comparison for orchestration modes in Azure Virtual Machine Scale Sets. It generally maintains OS neutrality, but there is a minor bias in the order of presenting operating system support: Windows is mentioned before Linux in several places (e.g., 'Mix operating systems | Yes, Linux and Windows can reside in the same Flexible scale set'). Additionally, the only explicit command-line example uses Azure CLI, which is cross-platform, and there are no PowerShell-only or Windows-specific tools referenced. However, in the Backup and Recovery section, Azure Site Recovery is noted as 'Yes (via PowerShell)' for Flexible orchestration, which may imply a Windows-centric approach, but this is a feature limitation rather than a documentation bias.
Recommendations
  • Where OS support is discussed, alternate the order (e.g., 'Linux and Windows' vs 'Windows and Linux') or clarify parity.
  • If Azure Site Recovery is available via CLI or REST for Linux, mention those options; if not, clarify the limitation.
  • Consider adding explicit Linux/macOS usage notes or examples where relevant, especially for extension installation or application health monitoring.
  • Ensure that future command-line examples include both Azure CLI and PowerShell (if applicable), and clarify cross-platform compatibility.
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-18 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 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 ARM template methods. There is no explicit Linux shell example (e.g., Bash), and PowerShell is a Windows-centric tool, although it is now cross-platform. The documentation does mention Linux in the ARM template section, but does not provide Linux-specific command-line examples or highlight Linux workflows.
Recommendations
  • Add explicit Bash or Linux shell examples alongside Azure CLI, especially for update operations.
  • Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell examples, as CLI is more commonly used on Linux/macOS.
  • Add notes or links to Linux-specific quickstart guides where relevant.
  • Ensure parity in example coverage for Linux users, including troubleshooting or known issues sections.
GitHub Create Pull Request
← Previous Page 7 of 11 Next →