Virtual Machine Scale Sets

95
Total Pages
82
Linux-Friendly Pages
13
Pages with Bias
13.7%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

136 issues found
Showing 26-50 of 136 flagged pages
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
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-17 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 major operations (attach, detach, move), but consistently lists Azure PowerShell examples after Azure CLI and before any Linux-specific guidance. There are no explicit Linux/macOS shell examples beyond Azure CLI, and PowerShell is presented as a primary scripting option, which is more relevant to Windows users. However, Azure CLI is cross-platform and the examples use Ubuntu images, so Linux users are not blocked.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and are recommended for cross-platform use.
  • Consider providing Bash shell script examples for common operations, or clarify that Azure CLI is the preferred tool for Linux/macOS.
  • Mention that PowerShell Core is available cross-platform, but highlight Azure CLI as the default for Linux/macOS users.
  • Ensure that CLI examples do not assume Windows-specific conventions (e.g., backslashes for line continuation).
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-17 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 examples are consistently presented after Azure CLI, and not before. However, in the PowerShell examples, the Application Health extension is shown using the Windows extension type ('ApplicationHealthWindows'), while the CLI example uses 'ApplicationHealthLinux'. This could cause confusion for Linux users following the PowerShell path. There are no Linux/macOS-specific command-line gaps, and all features are accessible via cross-platform tools (Azure CLI, REST API, Portal).
Recommendations
  • In PowerShell examples, clarify when to use 'ApplicationHealthWindows' vs. 'ApplicationHealthLinux' for the extension type, or provide both variants.
  • Add a note that Azure PowerShell is cross-platform, but that the extension type should match the VM OS.
  • Consider mentioning that Azure CLI is available on Windows, Linux, and macOS, and is recommended for Linux/macOS users.
  • Ensure that Linux-specific extension types are shown in PowerShell examples when the VM image is Linux.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows examples for configuring the application health extension and custom metrics, but there is a mild Windows bias in several areas. In the 'Install the application health extension' section, PowerShell (Windows) and Azure CLI (cross-platform) are both shown, but REST and PowerShell examples use 'ApplicationHealthWindows' as the extension type, while CLI uses 'ApplicationHealthLinux'. In the sample application section, both Bash (Linux) and PowerShell (Windows) scripts are given, but the PowerShell example is more elaborate and prominent. Throughout, Windows tools (PowerShell) are consistently presented alongside cross-platform tools, sometimes before Linux alternatives. However, Linux parity is generally maintained, and the documentation is not Windows-only.
Recommendations
  • Ensure that all examples for extension installation and configuration explicitly show both 'ApplicationHealthLinux' and 'ApplicationHealthWindows' types, with clear guidance for each OS.
  • Where PowerShell and Bash examples are given, ensure both are equally detailed and prominent.
  • In REST API examples, provide sample payloads for both Linux and Windows extension types.
  • Where possible, present CLI (cross-platform) examples before PowerShell (Windows-only) examples.
  • Add clarifying notes about OS-specific extension types and commands to help users select the correct option.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Minor Windows Tools
Summary
The documentation provides migration guidance for Azure Virtual Machine Scale Sets in Flexible orchestration. While the content is generally platform-neutral, there are a few minor instances of Windows bias: Windows/PowerShell is mentioned alongside Azure CLI and ARM templates, and Windows-specific scenarios (such as Windows VM activation and Windows updates) are listed before Linux equivalents. However, Linux scenarios (e.g., access to Linux package managers) are also mentioned, and most examples use Azure CLI, which is cross-platform.
Recommendations
  • Ensure Linux-specific migration scenarios (such as package manager access) are given equal prominence and detail as Windows scenarios.
  • Where PowerShell is referenced, provide Bash/Linux shell equivalents or clarify that Azure CLI is recommended for cross-platform users.
  • When listing common outbound connectivity scenarios, alternate the order or group Windows and Linux examples together to avoid 'windows_first' bias.
  • Consider including explicit Linux migration examples or references to Linux documentation 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-17 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 a way that may imply parity. However, PowerShell is a Windows-centric tool, and no explicit Linux/macOS shell examples (e.g., Bash, shell scripting) are given. The CLI examples are cross-platform, but PowerShell is given its own section and is not clearly marked as Windows-only. Additionally, in some sections, PowerShell appears immediately after CLI, which may subtly prioritize Windows tools.
Recommendations
  • Clarify that PowerShell examples are intended for Windows users, and Azure CLI is cross-platform.
  • Consider adding explicit Bash or shell script examples where relevant, or note that Azure CLI commands can be run in Bash, Zsh, or other Linux/macOS shells.
  • In tabbed sections, consider labeling PowerShell as '(Windows)' and CLI as '(cross-platform)' to reduce ambiguity.
  • If possible, add notes for Linux/macOS users about installing and using Azure CLI, and link to relevant documentation.
  • Ensure that CLI examples are always shown first, or at least clarify their cross-platform nature.
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-17 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 greater detail. Portal instructions are also included, but there is no explicit Linux/macOS shell example or mention of Bash scripting, and PowerShell is referenced as a primary scripting method. However, Azure CLI (cross-platform) is present throughout, and ARM templates are used for platform-neutral configuration.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash shell scripting examples where relevant, especially for tasks like querying public IPs.
  • Where PowerShell is used, clarify that Azure CLI is the recommended tool for Linux/macOS users.
  • Ensure parity in detail between PowerShell and CLI examples (e.g., if PowerShell shows multiple query methods, show equivalent CLI methods).
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-17 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and describes orchestration modes for Azure Virtual Machine Scale Sets, which support both Linux and Windows VMs. However, there is a minor bias in the example command for assigning a fault domain during VM creation, which uses Azure CLI syntax but does not explicitly show Linux shell or PowerShell alternatives. Additionally, some links reference Windows-specific managed identity configuration, but the overall guidance applies to both Linux and Windows. Windows is mentioned first in some mixed OS contexts, but Linux parity is maintained.
Recommendations
  • Provide explicit Linux shell and PowerShell examples for Azure CLI commands where relevant.
  • Clarify that Azure CLI commands work on both Linux and Windows platforms.
  • When referencing managed identity documentation, include links for both Linux and Windows VMSS setup.
  • Ensure that mixed OS examples alternate the order (e.g., 'Linux and Windows' vs. 'Windows and Linux') to avoid subtle ordering bias.
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-17 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'), PowerShell is presented before Linux-specific guidance. Additionally, the CLI examples use --generate-ssh-keys, which is Linux-centric, but there is no explicit mention of Linux/macOS compatibility or shell-specific instructions. The Resource Manager template section references both Linux and Windows getting started articles, but the PowerShell section could be perceived as Windows-centric due to its prominence and detail.
Recommendations
  • Ensure that Azure CLI examples are presented before PowerShell, as CLI is cross-platform and more relevant for Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide shell-specific notes if needed.
  • Add bash/zsh shell example blocks where appropriate, especially for update operations.
  • Clarify that PowerShell is primarily for Windows users, and recommend CLI for Linux/macOS.
  • Consider adding a short section or note about Linux/macOS compatibility for each method.
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-16 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 PowerShell examples are always present and shown alongside CLI. PowerShell is a Windows-centric tool, and its inclusion in every section, with detailed parameters, creates a mild Windows bias. Additionally, PowerShell examples are sometimes more detailed than their CLI counterparts. However, the Azure CLI is cross-platform and is included throughout, ensuring Linux/macOS users can complete all tasks. There are no Windows-only tools or patterns, and no critical steps are Windows-exclusive.
Recommendations
  • Ensure Azure CLI examples are as detailed as PowerShell examples, including all relevant parameters.
  • Consider listing Azure CLI examples before PowerShell examples, or clarifying that Azure CLI is recommended for cross-platform use.
  • Add a brief note explaining that Azure CLI works on Linux/macOS/Windows, while PowerShell is primarily for Windows users.
  • If possible, provide Bash script examples for advanced scenarios, or link to Azure CLI scripting guides for Linux users.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parity between Azure CLI and PowerShell for all command-line examples, but PowerShell examples are consistently shown alongside CLI and portal, and are often detailed. While Azure CLI is cross-platform, PowerShell is primarily used on Windows, and its inclusion may signal a Windows bias. However, Linux/macOS users can fully use the Azure CLI and ARM templates, and no critical functionality is Windows-only. The ordering sometimes puts PowerShell after CLI, but both are always present.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
  • Consider adding brief notes for Linux/macOS users, e.g., 'Azure CLI commands can be run on Linux, macOS, and Windows.'
  • If possible, include Bash shell script examples for common tasks, or link to Azure CLI Bash usage guides.
  • Ensure that PowerShell is not presented as the default or primary method, but as an alternative for Windows users.
  • Explicitly mention that all features are available via CLI and ARM templates, regardless of OS.
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-16 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 consistently presented alongside or immediately after CLI examples, and in some cases, the PowerShell extension used is 'ApplicationHealthWindows', which may be confusing for Linux users. The documentation does not provide Linux shell-specific examples (e.g., Bash scripts), but since Azure CLI is cross-platform, Linux users are not blocked. There is a slight bias in the ordering and in the PowerShell-centric explanations, but Linux parity is largely maintained.
Recommendations
  • Clarify in PowerShell examples when the extension is for Windows VMs and provide the correct extension name for Linux VMs if different.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI for cross-platform usage.
  • Consider providing a Bash script example for end-to-end automation on Linux.
  • In PowerShell examples, mention that PowerShell Core is available cross-platform, or clarify if examples require Windows PowerShell.
  • Ensure that the Application Health extension example in PowerShell uses 'ApplicationHealthLinux' when the VM image is Linux, to avoid confusion.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides Azure CLI and Resource Graph examples, but does not explicitly show Linux-specific commands or mention Linux tools. The only CLI example uses Azure CLI, which is cross-platform, but the documentation does not clarify that it works on Linux/macOS. The mention of Azure Site Recovery 'via PowerShell' in the backup table could imply a Windows bias, as PowerShell is traditionally Windows-centric, though PowerShell Core is cross-platform. There are no explicit Linux/macOS examples or references, and Windows is mentioned first in some contexts (e.g., 'Mix operating systems | Yes, Linux and Windows can reside...').
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows.
  • Add explicit Linux/macOS command examples where relevant (e.g., bash syntax, shell environment setup).
  • For features like Azure Site Recovery, specify if PowerShell Core is supported on Linux/macOS, or provide equivalent Azure CLI examples.
  • Ensure parity in mentioning operating systems (e.g., 'Linux and Windows' instead of 'Windows and Linux').
  • Where VM extensions or health monitoring are discussed, note any OS-specific requirements or differences.
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-16 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 presented immediately after CLI and before REST API. The CLI examples are cross-platform, but PowerShell is Windows-centric. There are no explicit Linux/macOS shell examples (e.g., Bash), and the documentation does not mention Linux-specific tools or patterns. The ARM template section references both Linux and Windows getting started articles, but does not provide explicit Linux shell commands.
Recommendations
  • Add Bash shell examples alongside PowerShell, especially for update operations.
  • Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider reordering examples to show CLI first, then PowerShell, to reinforce cross-platform parity.
  • Add clarifying notes for Linux/macOS users where PowerShell is referenced, suggesting CLI as the alternative.
GitHub Create Pull Request
← Previous Page 2 of 6 Next →