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 1-25 of 274 flagged pages
Virtual Machine Scale Sets Create a Virtual Machine Scale Set with instance mix ...cles/virtual-machine-scale-sets/instance-mix-create.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell examples after Azure CLI, providing detailed PowerShell commands, and referencing Windows-centric tools and patterns (such as PowerShell and credential objects). While the Azure CLI examples use Ubuntu images and SSH authentication, the PowerShell section is more extensive and uses Windows-style parameters and patterns. There is no explicit Linux shell scripting example (e.g., Bash), and PowerShell is presented as a primary automation method, which may disadvantage Linux users.
Recommendations
  • Add Bash shell script examples for Linux users, especially for automation scenarios.
  • Clarify that PowerShell is cross-platform, but provide examples using native Linux tools where appropriate.
  • Ensure parity in example depth and detail between CLI and PowerShell sections.
  • Avoid Windows-centric terminology (e.g., 'Credential objects') unless also explaining Linux equivalents.
  • Explicitly mention Linux prerequisites and patterns (e.g., SSH key management, environment variables) alongside Windows ones.
GitHub Create Pull Request
Virtual Machine Scale Sets Automatic OS image upgrades with Azure Virtual Machine Scale Sets ...e-sets/virtual-machine-scale-sets-automatic-upgrade.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers both Windows and Linux VM Scale Sets, but there is a notable Windows bias in example ordering, tool references, and template defaults. PowerShell examples are prominent and shown before Azure CLI, and ARM/Bicep template snippets default to Windows images. Linux-specific examples, troubleshooting, and considerations are less visible or missing.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or show CLI first for parity.
  • Provide ARM/Bicep template snippets with Linux image defaults (e.g., Ubuntu) alongside Windows examples.
  • Add explicit Linux troubleshooting notes where Windows-specific guidance is given (e.g., drive letter reassignment).
  • Ensure all example commands (PowerShell, CLI, REST) are shown for both Windows and Linux scenarios.
  • Clarify that all features and steps apply equally to Linux, and highlight any Linux-specific requirements or caveats.
  • Add links to Linux-specific documentation or best practices where 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
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows examples for configuring custom metrics and the application health extension on Azure Virtual Machine Scale Sets. However, there is evidence of Windows bias: PowerShell examples are often given equal or greater prominence than Bash/Linux examples, and Windows-specific extension types (e.g., ApplicationHealthWindows) are shown first or exclusively in some code snippets. PowerShell and Windows tools are referenced throughout, sometimes before their Linux equivalents. The REST API and Azure CLI examples are platform-neutral, but the PowerShell sections are detailed and prominent.
Recommendations
  • Ensure Linux and Bash examples are presented before or alongside Windows/PowerShell examples in each section.
  • Where extension types are shown (e.g., ApplicationHealthWindows vs ApplicationHealthLinux), clarify both options and show Linux as the default or first example when possible.
  • Expand Bash/Linux scripting examples to match the detail and completeness of PowerShell examples.
  • Add explicit notes or tables clarifying parity between Windows and Linux extension types and commands.
  • Review sample outputs and code snippets to ensure Linux is equally represented and not overshadowed by Windows-specific content.
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
Medium Priority View Details →
Scanned: 2026-03-09 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 examples or parity for PowerShell commands. Windows-specific scenarios (activation, updates) are mentioned before Linux equivalents, and PowerShell is referenced alongside Azure CLI without clear Linux guidance. Some example commands (e.g., az vm create) are shown without specifying shell context, potentially defaulting to Windows/PowerShell usage. Linux-specific migration steps, tools, or troubleshooting are not covered.
Recommendations
  • Add explicit bash/Linux shell examples alongside PowerShell for all CLI instructions.
  • Ensure Linux package manager update scenarios are described with equal detail as Windows update/activation.
  • Mention Azure CLI usage in Linux/macOS contexts, and clarify shell compatibility for example commands.
  • Provide troubleshooting guidance for Linux VM migration, including common issues and solutions.
  • Where PowerShell is referenced, add equivalent bash/CLI instructions and links to Linux documentation.
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
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for 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 ARM template examples. 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 not exclusively mention Windows tools, but the presence of PowerShell examples without explicit Linux shell alternatives may create friction for Linux/macOS users.
Recommendations
  • Add explicit Bash shell examples for Azure CLI commands, clarifying that CLI is cross-platform and works on Linux/macOS.
  • Where PowerShell is used, note its cross-platform availability, but also provide Bash alternatives for Linux users.
  • Ensure that CLI examples are shown before PowerShell examples, as CLI is the primary cross-platform tool.
  • Clarify in introductory sections that all methods (portal, CLI, PowerShell, ARM templates) are available to all OS users, and link to platform-specific getting started guides.
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
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both 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 Windows-specific PowerShell tooling is referenced throughout. The Application Health extension example in PowerShell uses 'ApplicationHealthWindows', while the CLI uses 'ApplicationHealthLinux', but there is no explicit guidance for Linux users in PowerShell. Portal instructions are platform-neutral, but the PowerShell sections are inherently Windows-centric, and PowerShell is presented as a primary automation option, which may create friction for Linux/macOS users.
Recommendations
  • Clarify that Azure PowerShell is cross-platform and can be used on Linux/macOS, or provide Bash scripting examples where appropriate.
  • Ensure that Application Health extension examples in PowerShell include both Windows and Linux variants, or explain how to use 'ApplicationHealthLinux' in PowerShell.
  • Consider presenting CLI (Bash) examples before PowerShell, or explicitly state that CLI is recommended for Linux/macOS users.
  • Add a note about PowerShell Core support on non-Windows platforms if PowerShell is required.
  • Where possible, provide Bash shell scripting examples for automation tasks.
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
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response, but there is a notable Windows bias in several areas. PowerShell examples are consistently present alongside CLI and REST, and in some sections (e.g., REST sample payloads), the extension type defaults to 'ApplicationHealthWindows' rather than 'ApplicationHealthLinux'. In the PowerShell section for installing the extension, only the Windows extension is shown, while the CLI example uses the Linux extension. There is no explicit parity table or clear guidance for Linux vs. Windows extension usage, and the PowerShell example is more detailed than the Bash example. Additionally, in some REST payloads, 'ApplicationHealthWindows' is used by default, which may confuse Linux users.
Recommendations
  • Ensure all sample code and REST payloads show both 'ApplicationHealthLinux' and 'ApplicationHealthWindows' values, or clarify when to use each.
  • Add explicit Linux (Bash) examples for installing the application health extension, not just for the response server.
  • Balance the detail level between Bash and PowerShell examples, ensuring Linux users have equally comprehensive guidance.
  • In REST and PowerShell sections, provide Linux-specific examples or note how to adapt for Linux VMSS.
  • Consider a parity table or section summarizing differences between Windows and Linux extension usage.
GitHub Create Pull Request
Virtual Machine Scale Sets Automatic OS image upgrades with Azure Virtual Machine Scale Sets ...e-sets/virtual-machine-scale-sets-automatic-upgrade.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux information, but there is a notable Windows bias in several areas. Windows-specific properties and configuration options are discussed first and in greater detail. PowerShell examples are presented before Azure CLI examples, and ARM/Bicep template snippets default to Windows images. Some explanations reference Windows tools and concepts (e.g., drive letters, Windows Update) without equivalent Linux context. However, Linux is supported and referenced throughout, and CLI examples are present.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI first for cross-platform parity.
  • Provide ARM/Bicep template snippets that default to a Linux image, or show both Windows and Linux examples.
  • When discussing OS-specific configuration (e.g., drive letters, Windows Update), add equivalent Linux context (e.g., mount points, package managers).
  • Clarify in requirements and configuration sections which steps are Windows-specific and which apply to Linux, to avoid confusion.
  • Ensure Linux-specific troubleshooting and error scenarios are covered alongside Windows examples.
GitHub Create Pull Request
Virtual Machine Scale Sets Orchestration modes for Virtual Machine Scale Sets in Azure ...sets/virtual-machine-scale-sets-orchestration-modes.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides examples and references that are either Windows-centric or lack explicit Linux parity. For instance, the Azure Site Recovery feature is noted as supported 'via PowerShell' for Flexible orchestration, but no Linux/CLI equivalent is mentioned. The only command-line example uses Azure CLI, which is cross-platform, but there are no explicit Linux-specific examples or notes. Additionally, in the Managed Identity section, the link references a Windows VMSS portal guide, which may confuse Linux users. Overall, the documentation assumes Windows familiarity in some areas and omits Linux-specific guidance.
Recommendations
  • Add explicit Linux/CLI equivalents for features currently described as 'via PowerShell', such as Azure Site Recovery.
  • Ensure that links and examples for Managed Identity and other features reference both Windows and Linux documentation or clarify applicability.
  • Include Linux-specific examples or notes where relevant, especially in sections referencing command-line tools or extensions.
  • Review feature tables and FAQs to ensure Linux parity is clearly stated for each feature.
GitHub Create Pull Request
Virtual Machine Scale Sets Automatic OS image upgrades with Azure Virtual Machine Scale Sets ...e-sets/virtual-machine-scale-sets-automatic-upgrade.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation covers automatic OS image upgrades for Azure Virtual Machine Scale Sets and is intended for both Windows and Linux workloads. However, there is evidence of Windows bias: Windows terminology and properties are often mentioned first or exclusively (e.g., 'enableAutomaticUpdates', 'Windows Update'), ARM template examples default to Windows images, and PowerShell examples are prominent. While Azure CLI examples are provided (which are cross-platform), there are no explicit Linux-specific configuration examples or notes about Linux-specific behaviors, and Windows-specific settings are discussed in detail without equivalent Linux guidance.
Recommendations
  • Add explicit Linux-focused examples in ARM templates and Bicep (e.g., default to Ubuntu or Mariner images, not WindowsServer).
  • Provide guidance or notes on Linux-specific configuration nuances (such as handling custom scripts, extension behaviors, or disk mounting differences).
  • Ensure Linux terminology and settings are mentioned alongside Windows settings, not after or omitted.
  • Balance PowerShell and CLI examples, and clarify that CLI is cross-platform.
  • Where Windows-specific properties are discussed (e.g., 'enableAutomaticUpdates'), add a note about their irrelevance or Linux equivalents for Linux images.
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
Medium Priority View Details →
Scanned: 2026-03-01 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 Virtual Machine Scale Sets, but does not provide explicit Linux/bash examples or mention Linux tools. PowerShell is mentioned alongside Azure CLI, but no Linux-specific guidance or parity is provided. Windows-specific scenarios (activation, updates) are listed before Linux package manager access in the networking section, and the only command-line example is in Azure CLI, but no bash or Linux shell context is given. The documentation assumes cross-platform usage but subtly prioritizes Windows tools and scenarios.
Recommendations
  • Add explicit Linux/bash examples for key operations, such as VM creation and migration.
  • Provide parity between Azure PowerShell and Azure CLI examples, clarifying which commands are cross-platform.
  • Mention Linux-specific migration considerations, such as package manager access and OS disk handling.
  • Ensure Linux scenarios (e.g., package manager updates) are given equal prominence to Windows scenarios.
  • Clarify which tools (Azure CLI, PowerShell) are recommended for Linux/macOS users and provide links to installation guides.
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
Medium Priority View Details →
Scanned: 2026-02-28 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 Virtual Machine Scale Sets, but does not provide explicit Linux/bash examples or parity for PowerShell commands. Azure PowerShell is mentioned alongside Azure CLI, but no Linux-specific guidance or bash scripting examples are given. Windows-specific scenarios (such as Windows VM activation and Windows updates) are mentioned before Linux equivalents, and Linux package manager access is only briefly referenced. The sample command for assigning fault domains uses Azure CLI, which is cross-platform, but there is no demonstration of Linux shell usage or explicit Linux/macOS considerations.
Recommendations
  • Add explicit bash/Linux shell examples alongside PowerShell and Azure CLI commands.
  • Provide Linux-specific migration considerations, such as handling SSH keys, package manager updates, and disk management.
  • Ensure Linux scenarios (e.g., package manager access, Linux VM extensions) are described with equal detail as Windows scenarios.
  • Mention cross-platform tools (e.g., Azure CLI) as primary options, and clarify PowerShell usage is optional.
  • Include links to Linux documentation for relevant Azure features (e.g., Linux VM activation, Linux troubleshooting).
GitHub Create Pull Request
Virtual Machine Scale Sets Automatic OS image upgrades with Azure Virtual Machine Scale Sets ...e-sets/virtual-machine-scale-sets-automatic-upgrade.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows (PowerShell) and cross-platform (Azure CLI, REST, ARM/Bicep) examples for configuring and managing automatic OS image upgrades in Azure Virtual Machine Scale Sets. However, in several sections, PowerShell (a Windows-centric tool) examples are presented before Azure CLI, and some ARM template snippets use Windows images as defaults. There are also multiple references to Windows-specific properties and behaviors, sometimes without equivalent Linux notes. While Linux is supported and examples are present, the ordering and emphasis can create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
  • When showing ARM or Bicep template snippets, use a Linux image as the default or provide both Windows and Linux examples.
  • Where Windows-specific properties (e.g., enableAutomaticUpdates) are discussed, add clarifying notes about Linux equivalents or state when not applicable.
  • Ensure that all sections referencing tools or commands provide parity between Windows and Linux (e.g., Bash scripts, cloud-init, etc.), or explicitly state when a feature is Windows-only.
  • Consider adding a table or section summarizing differences or additional steps for Linux 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
Medium Priority View Details →
Scanned: 2026-02-27 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 examples or mention Linux tools. PowerShell is mentioned alongside Azure CLI, but there are no bash or shell script examples. Windows-specific scenarios (activation, updates) are listed before Linux package manager access in the networking section. The only CLI example is Azure CLI, but there is no parity for Linux-specific workflows or troubleshooting.
Recommendations
  • Add explicit bash/shell script examples for Linux users alongside PowerShell examples.
  • Ensure Linux package manager scenarios are described with equal prominence as Windows activation and updates.
  • Provide links to Linux-specific migration guides or troubleshooting resources.
  • Mention Azure CLI as cross-platform and clarify that PowerShell is optional for Windows users.
  • Include sample ARM templates or CLI commands that demonstrate Linux VM migration.
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
Medium Priority View Details →
Scanned: 2026-02-25 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 scale sets, but does not provide explicit Linux/bash examples or parity for PowerShell commands. Windows-specific scenarios (activation, updates) are mentioned before Linux equivalents, and PowerShell is listed alongside CLI without clear Linux guidance. There are no explicit Linux/macOS command examples or references to Linux tools, creating friction for non-Windows users.
Recommendations
  • Provide explicit bash/Linux command examples alongside PowerShell, especially for Azure CLI usage.
  • Mention Linux package manager update scenarios before or alongside Windows update scenarios.
  • Clarify that Azure CLI is cross-platform and provide guidance for Linux/macOS users where PowerShell is referenced.
  • Ensure migration steps and tooling are equally described for Linux and Windows environments.
  • Add examples for Linux VM activation and troubleshooting, not just Windows.
  • Where PowerShell is referenced, add equivalent bash/CLI instructions.
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
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references both Azure CLI and Azure PowerShell for creating Virtual Machine Scale Sets, but PowerShell is mentioned alongside CLI and before ARM Template. There are no explicit Linux shell (bash) examples, and PowerShell is referenced without equivalent Linux-specific guidance. Windows-specific scenarios (activation, updates) are listed before Linux package manager access in the networking section. No Linux-specific migration examples or tools are provided.
Recommendations
  • Provide explicit bash/Linux shell examples alongside PowerShell and Azure CLI, especially for VM creation and migration steps.
  • Mention Azure CLI (which is cross-platform) before PowerShell, and clarify that CLI commands work on Linux/macOS.
  • Add Linux-specific migration considerations, such as handling SSH keys, package managers, and OS disk migration.
  • Ensure Linux package manager connectivity is discussed with equal prominence as Windows activation and updates.
  • Where PowerShell is referenced, add notes or links for Linux/macOS users to use Azure CLI or bash equivalents.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Medium 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 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 scripting language shown (e.g., querying public IPs), and CLI examples are not always as prominent. There are no Linux-specific shell examples (e.g., Bash), but the CLI is cross-platform. The documentation references both Windows and Linux for Accelerated Networking, but PowerShell is generally associated with Windows, and its prominence may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Ensure all PowerShell examples have equivalent Azure CLI examples.
  • Where possible, include Bash shell snippets for common tasks to further improve Linux parity.
  • Clarify that Azure CLI commands work on all platforms, and highlight this in introductory sections.
  • Add links to Linux/macOS-specific guidance where relevant.
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
Medium Priority View Details →
Scanned: 2026-02-21 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 scale sets, but does not provide explicit Linux/bash examples or parity for PowerShell commands. Azure PowerShell is mentioned alongside Azure CLI, but examples and links for PowerShell are provided without equivalent Linux/bash or cross-platform CLI examples. Windows-specific scenarios (activation, updates) are listed before Linux equivalents, and Windows tools are referenced more prominently. There are no explicit Linux-focused migration steps or examples.
Recommendations
  • Add explicit bash/Linux shell examples alongside PowerShell examples, especially for Azure CLI usage.
  • Ensure that CLI examples are shown first or equally with PowerShell, as Azure CLI is cross-platform.
  • Provide links to Linux-specific documentation or migration guides where relevant.
  • When listing scenarios (e.g., outbound connectivity requirements), alternate or balance Windows and Linux mentions.
  • Clarify that Azure CLI is cross-platform and suitable 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
Medium Priority View Details →
Scanned: 2026-02-20 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 Virtual Machine Scale Sets, but does not provide explicit Linux/bash examples or clarify parity between PowerShell and bash usage. Azure PowerShell is mentioned alongside Azure CLI, but no Linux-specific guidance or examples are given. Windows activation and Windows updates are mentioned before Linux package managers in network connectivity scenarios. No Linux-specific migration considerations or examples are provided.
Recommendations
  • Add explicit bash/Linux shell examples for key Azure CLI commands (e.g., az vm create) and clarify that Azure CLI works cross-platform.
  • Provide Linux-specific migration considerations, such as handling SSH keys, Linux VM extensions, and package manager updates.
  • When listing network connectivity scenarios, mention Linux package manager access before or alongside Windows activation and updates.
  • Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
  • Include links to Linux VM documentation and migration best practices.
GitHub Create Pull Request
Virtual Machine Scale Sets Networking for Azure Virtual Machine Scale Sets ...ne-scale-sets/virtual-machine-scale-sets-networking.md
Medium 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 generally provides parity between Azure CLI and PowerShell, but in some sections, PowerShell (Windows) examples are presented before CLI (cross-platform) equivalents, and some advanced operations are only shown in PowerShell. There are also a few places where PowerShell is mentioned or shown without an immediately adjacent CLI/Linux example, which may cause friction for Linux/macOS users.
Recommendations
  • Ensure that for every PowerShell example, an equivalent Azure CLI example is provided and shown with equal prominence.
  • When presenting tabbed examples, default to showing Azure CLI (cross-platform) first, or alternate the order to avoid Windows-first bias.
  • Where only PowerShell examples are given (e.g., querying public IPs), add equivalent Azure CLI commands.
  • Review all sections for any missing CLI examples, especially for advanced or update scenarios, and add them.
  • Explicitly note when a feature or command is only available in PowerShell, and provide workarounds or alternatives for Linux/macOS users if possible.
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
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows examples for configuring custom metrics and the application health extension on Azure Virtual Machine Scale Sets. However, there is evidence of Windows bias: PowerShell examples are consistently present and sometimes shown before Bash/Linux equivalents; Windows-specific extension types (ApplicationHealthWindows) are used in several code snippets; and Windows tools (PowerShell cmdlets) are featured prominently alongside Azure CLI and REST. The Bash/Linux example for the health endpoint is present, but the PowerShell example is more elaborate and appears first in some sections. REST API examples use Windows extension types by default, and the PowerShell section is detailed, potentially creating friction for Linux users.
Recommendations
  • Ensure Linux and Bash examples are given equal prominence and detail as PowerShell examples.
  • In code snippets and tables, use both ApplicationHealthLinux and ApplicationHealthWindows types, or clarify when each should be used.
  • Where PowerShell is used, provide equivalent Bash or Python scripts for Linux/macOS users.
  • In REST API examples, alternate between ApplicationHealthLinux and ApplicationHealthWindows, or explain the difference.
  • Consider listing Bash/Linux examples first in relevant sections to balance ordering.
  • Explicitly state that all features are supported on both Linux and Windows VMSS, and clarify any OS-specific requirements.
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
Medium 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 configuration examples for Azure Virtual Machine Scale Sets using MaxSurge via Portal, CLI, PowerShell, and ARM Template. The PowerShell example is included, which is Windows-specific, and is presented after the CLI example. The CLI example uses Azure CLI, which is cross-platform, but there is no explicit mention of Linux/macOS-specific tools or shell syntax. The documentation does not show Linux-specific commands (e.g., Bash scripts) or highlight Linux workflows. However, the PowerShell example is not shown first, and the CLI example is cross-platform, so the bias is moderate.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
  • Add explicit Bash shell examples for Linux users, especially for scripting or automation.
  • Mention that PowerShell is available cross-platform, but highlight Azure CLI as the primary tool for Linux/macOS users.
  • Consider including references to Linux/macOS documentation or guides for managing VM Scale Sets.
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
Medium Priority View Details →
Scanned: 2026-02-16 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 resources, but does not provide explicit Linux/bash examples or mention Linux tools. PowerShell is mentioned alongside Azure CLI, but no Linux-specific scripting guidance is given. Windows scenarios (activation, updates) are listed before Linux (package managers) in outbound connectivity requirements. There are no explicit Linux/macOS shell examples or parity guidance.
Recommendations
  • Add explicit bash/Linux shell examples alongside Azure CLI and PowerShell, especially for VM creation and migration steps.
  • Mention Linux-specific migration considerations (e.g., package manager updates, SSH configuration) in relevant sections.
  • Ensure Linux scenarios are given equal prominence in outbound connectivity requirements, not listed after Windows scenarios.
  • Clarify that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell) and Linux/macOS (bash).
  • Include links to Linux documentation or migration guides where appropriate.
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
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions Azure CLI, Azure PowerShell, and ARM Template as options for creating Virtual Machine Scale Sets, but does not provide explicit Linux/bash examples or clarify parity between PowerShell and CLI usage. Windows-specific scenarios (activation, updates) are listed before Linux equivalents, and PowerShell is referenced alongside CLI without clear Linux guidance. No Linux/macOS-specific migration steps or examples are provided.
Recommendations
  • Provide explicit bash/Azure CLI examples for key operations, such as creating scale sets and migrating VMs.
  • Clarify that Azure CLI is cross-platform and provide Linux/macOS usage guidance where PowerShell is mentioned.
  • List Linux scenarios (e.g., package manager access) alongside Windows scenarios, not after them.
  • Add sample migration scripts or commands for Linux users, including handling disks, NICs, and VM creation.
  • Ensure that references to tools (CLI, PowerShell) are balanced and that Linux/macOS users are not required to use Windows tools.
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
Medium Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for enabling Automatic Zone Balance on VM Scale Sets. However, PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and in some sections, PowerShell examples reference Windows-specific extension types (e.g., ApplicationHealthWindows), while CLI examples reference ApplicationHealthLinux. The PowerShell examples are not clearly marked as Windows-only, and PowerShell is presented as a first-class option, which may create friction for Linux/macOS users. Portal instructions are platform-neutral, but PowerShell is a Windows tool and is not available natively on most Linux/macOS systems.
Recommendations
  • Clearly indicate that Azure PowerShell is primarily for Windows users and recommend Azure CLI for Linux/macOS users.
  • Ensure that all extension examples (e.g., Application Health) are shown for both Linux and Windows, and clarify which is appropriate for each OS.
  • Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Add explicit notes or links for Linux/macOS users about how to install and use Azure CLI.
  • Where PowerShell is used, clarify if the example is Windows-specific or if PowerShell Core is supported on Linux/macOS.
GitHub Create Pull Request
← Previous Page 1 of 11 Next →