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 226-250 of 274 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-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and 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 are no explicit Linux-specific command-line examples (e.g., Bash scripts), and the documentation does not mention Linux tools or patterns. The Resource Manager template section references both Linux and Windows getting started articles, but overall, there is a slight bias towards Windows/PowerShell in example prominence and ordering.
Recommendations
  • Ensure Azure CLI examples are always presented before PowerShell, as CLI is cross-platform.
  • Add explicit Bash shell script examples for Linux users where relevant.
  • Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Consider including a note or section highlighting Linux/macOS parity and recommending CLI for those platforms.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides Azure Portal, Azure CLI, and Azure PowerShell examples for all attach/detach operations. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric, and its inclusion in every section (with full code samples) demonstrates a mild Windows bias. Additionally, PowerShell examples are consistently presented immediately after CLI, which may reinforce a Windows-first impression. However, there are no critical tasks that are Windows-only, and CLI parity is maintained throughout. No Linux/macOS-specific tools or shell examples are missing, but Bash or shell script examples are not explicitly shown.
Recommendations
  • Add explicit Bash/shell script examples for common attach/detach operations, or clarify that Azure CLI commands work identically on Linux/macOS.
  • Consider alternating the order of CLI and PowerShell examples, or explicitly state that CLI is cross-platform and recommended for Linux/macOS users.
  • Where possible, mention that PowerShell Core is available cross-platform, or clarify when examples are Windows PowerShell-specific.
  • Add a short note at the start of the 'Azure CLI' sections indicating that these commands are suitable for Linux/macOS/Windows.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parity between Azure CLI and PowerShell for all command-line examples, but consistently presents PowerShell examples immediately after CLI and before ARM Template. Portal instructions are also present. However, PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. No Linux-specific tools or shell examples (e.g., Bash, shell scripting) are provided, but Azure CLI is cross-platform and covers most needs. The ordering of examples (CLI first, PowerShell second) is a minor bias, but no critical functionality is Windows-only.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider providing Bash shell scripting examples for common tasks, or clarify that Azure CLI commands are suitable for Linux/macOS.
  • If possible, add a short section or callout for Linux/macOS users, confirming that all tasks can be completed with Azure CLI.
  • Review the ordering of examples to ensure CLI and ARM Template are prioritized for cross-platform parity.
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-08 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, but CLI is shown before PowerShell. There is a slight bias toward Windows/PowerShell, as PowerShell is a Windows-centric tool, but the CLI example is cross-platform and appears first. No Windows-specific tools or patterns are mentioned exclusively, and Linux users can complete all tasks using Azure CLI or ARM templates.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider adding Bash shell scripting examples for CLI usage, or clarifying that CLI commands work on Linux/macOS.
  • If possible, mention that PowerShell Core is available cross-platform, but traditional PowerShell is Windows-only.
  • Ensure that CLI and ARM template examples are always present and shown before PowerShell in future documentation.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell examples are often presented before CLI examples, and some sections (e.g., querying public IPs) give more detailed PowerShell usage. There is a slight preference for Windows/PowerShell tooling, but Linux parity is generally maintained via CLI and ARM template examples.
Recommendations
  • Present CLI and PowerShell examples side-by-side or in parallel tabs, rather than consistently listing PowerShell first.
  • Ensure CLI examples are as detailed as PowerShell examples, especially for querying and updating resources.
  • Add explicit notes clarifying that Azure CLI works cross-platform (Linux/macOS/Windows), and PowerShell is available on Linux/macOS as well.
  • Where possible, provide Bash shell script examples for Linux users, especially in sections with only PowerShell code.
  • Review for any missing CLI equivalents and add them if absent.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring custom metrics and the application health extension on Azure Virtual Machine Scale Sets. However, there are several areas where Windows/PowerShell examples are presented first or in greater detail, and Windows-specific extension types (ApplicationHealthWindows) are used in some code snippets and REST payloads. The PowerShell section is more verbose and detailed than the Bash example, and Windows-specific extension names/types are used in several places. Linux parity is generally good, but Windows bias is evident in ordering and emphasis.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail. Alternate the order of examples or present them side-by-side.
  • Clarify when to use ApplicationHealthLinux vs ApplicationHealthWindows in all code snippets and REST payloads, and provide explicit Linux-focused examples.
  • Expand Bash/Python examples to match the detail and completeness of PowerShell examples, including troubleshooting and verification steps.
  • Where possible, use generic extension names/types in JSON and REST examples, or provide both Linux and Windows variants.
  • Review sample output and troubleshooting sections to ensure Linux commands and tools are as prominent as Windows/PowerShell equivalents.
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-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI, and the PowerShell section appears before the ARM template section. There is a slight 'windows_first' bias, as PowerShell is a Windows-centric tool, and its inclusion alongside CLI without mention of Bash or Linux-specific commands may create friction for Linux/macOS users. However, the CLI examples are present and fully functional for Linux/macOS users, and ARM templates are platform-agnostic.
Recommendations
  • Ensure Azure CLI examples are always shown before PowerShell, as CLI is cross-platform.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
  • Consider adding Bash shell script examples for Linux users, or clarifying that Azure CLI is the recommended tool for Linux/macOS.
  • In the 'Use Azure Resource Manager templates' section, clarify that both Linux and Windows images are supported, and link to both quick-create-template-linux.md and quick-create-template-windows.md equally.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides Azure CLI, Azure PowerShell, and portal instructions for attaching/detaching VMs to/from VM Scale Sets. While Azure CLI is cross-platform and examples use Ubuntu images, PowerShell examples are given equal prominence and are shown immediately after CLI, which may imply parity but can be seen as Windows-centric since PowerShell is most commonly used on Windows. There is a minor 'windows_first' bias in troubleshooting links, which reference Windows-specific documentation for disk conversion and proximity placement group operations, even though Linux equivalents exist.
Recommendations
  • Clarify that Azure PowerShell is available on macOS/Linux, or provide Bash examples where appropriate.
  • Ensure troubleshooting links reference both Windows and Linux documentation for disk conversion and proximity placement group operations.
  • Consider listing CLI examples before PowerShell, as CLI is more universally available across platforms.
  • Explicitly state that all shown commands (CLI/PowerShell) are cross-platform unless there are platform-specific caveats.
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-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 Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response, but there is a mild Windows bias in several areas. PowerShell examples are consistently present and sometimes shown before or alongside Linux equivalents. Windows-specific extension types (ApplicationHealthWindows) are used in code samples and REST payloads, sometimes before Linux equivalents. The REST and PowerShell sections use Windows extension types by default, and PowerShell is given equal or greater prominence than Bash. However, Linux parity is generally maintained, and CLI/Bash examples are present for all major workflows.
Recommendations
  • When showing extension type in JSON or REST samples, use ApplicationHealthLinux as the default or show both Linux and Windows variants.
  • In REST API examples, clarify that both ApplicationHealthLinux and ApplicationHealthWindows are valid, and provide explicit Linux-focused sample payloads.
  • Ensure Bash/Python examples are shown before or at least equally with PowerShell, especially in sections where Linux is the more common platform.
  • Add a note clarifying that all workflows are supported on both Linux and Windows VMSS, and highlight any platform-specific differences if present.
  • Consider adding more troubleshooting examples for Linux environments (e.g., systemd, firewall configuration) to match the PowerShell troubleshooting depth.
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-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides usage instructions for Azure portal, REST API, Azure CLI, and Azure PowerShell. While all major cross-platform interfaces are covered, the PowerShell example is given its own section and is presented after CLI, which is cross-platform. The documentation does not show Linux-specific tools or shell examples (e.g., Bash/curl for REST API), and the PowerShell section may imply a slight Windows bias by highlighting PowerShell usage, which is most common on Windows.
Recommendations
  • Add explicit Bash/curl examples for the REST API section to demonstrate usage from Linux/macOS.
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS/Windows.
  • Consider listing CLI and REST API examples before PowerShell, or grouping them together to avoid implying a Windows-first workflow.
  • Mention that PowerShell Core is available on Linux/macOS if relevant, or clarify when examples are Windows-only.
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-05 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, and in some sections (such as setting/updating the rolling upgrade policy), the PowerShell tab appears immediately after CLI, which may imply a slight Windows-first orientation. There are no Linux-specific tools or shell script examples, but the Azure CLI commands are fully cross-platform. No critical functionality is locked to Windows-only tools, and ARM template examples are also provided.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows equally.
  • Consider listing CLI examples before PowerShell in all sections, or explicitly note CLI is cross-platform.
  • Add a brief note for Linux/macOS users that PowerShell examples are optional and CLI is recommended for cross-platform automation.
  • If possible, provide Bash script snippets for common automation scenarios to further demonstrate Linux parity.
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-05 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 Azure CLI and PowerShell examples for most networking tasks with Azure Virtual Machine Scale Sets, but PowerShell (Windows-centric) examples are often presented before CLI (cross-platform) examples. In some sections, only PowerShell examples are given for querying resources, with CLI shown later or not at all. There are no Linux/macOS-specific shell examples (e.g., Bash scripts), and Windows tools/patterns (PowerShell) are sometimes prioritized. However, most tasks can be completed using the CLI, which is cross-platform.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred for Linux/macOS users.
  • Ensure every PowerShell example has a corresponding Azure CLI example.
  • Where possible, provide Bash script snippets for Linux/macOS users, especially for tasks involving scripting or automation.
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS to guide users.
  • Review sections where only PowerShell is shown (e.g., querying public IPs) and add CLI equivalents.
  • Avoid language that implies PowerShell is the default or preferred method unless the feature is Windows-only.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides usage instructions for Spot Placement Score via Azure portal, REST API, Azure CLI, and Azure PowerShell. The PowerShell example is given its own section and is presented after the CLI example, but both are included. There is a slight 'Windows-first' bias as PowerShell is highlighted as a primary method, and the Azure portal instructions implicitly assume a graphical interface typical of Windows environments. However, Linux parity is generally maintained via REST API and Azure CLI instructions.
Recommendations
  • Explicitly mention that Azure CLI and REST API are cross-platform and suitable for Linux/macOS users.
  • Consider listing CLI and REST API instructions before PowerShell to avoid implicit prioritization of Windows tooling.
  • Add a note clarifying that PowerShell Core is available on Linux/macOS, or link to cross-platform PowerShell documentation.
  • Where possible, include example shell commands (e.g., Bash/curl) for REST API usage to further support Linux/macOS users.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides Azure portal, Azure CLI, and Azure PowerShell instructions for attaching/detaching VMs to/from scale sets. In each code example section, PowerShell is presented as a primary option alongside CLI, and the PowerShell examples use Windows-centric syntax (backticks, cmdlets). The CLI examples are cross-platform, but PowerShell is Windows-first and not natively available on Linux/macOS. Additionally, in troubleshooting, links for disk migration and proximity placement group removal point to Windows VM documentation, even though the feature is not Windows-specific.
Recommendations
  • Clarify that Azure PowerShell can be used cross-platform via PowerShell Core, or provide Bash/shell script equivalents for Linux/macOS users.
  • Where links point to Windows-specific documentation for generic VM features (e.g., managed disk migration, proximity placement group removal), add or reference Linux VM documentation as well.
  • Consider listing CLI examples before PowerShell, as CLI is more universally available across platforms.
  • Explicitly state that all operations can be performed on both Windows and Linux VMs, and provide example commands for both where configuration or parameters differ.
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-04 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 Azure CLI and PowerShell examples for most networking tasks with Azure Virtual Machine Scale Sets, but PowerShell (Windows-centric) examples are often presented before CLI (cross-platform) ones. In some sections, PowerShell is the only example given for querying resources, or CLI examples are less detailed. There are no Linux/macOS-specific shell examples (e.g., Bash scripts), and some verification steps use PowerShell exclusively. However, the majority of configuration is done via Azure CLI, ARM templates, or REST API, which are cross-platform.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell examples to reduce Windows-first perception.
  • Ensure every PowerShell example has an equivalent Azure CLI example, especially for verification and querying tasks.
  • Where possible, include Bash script snippets for Linux/macOS users, especially for tasks that might involve scripting.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and encourage its use for cross-platform scenarios.
  • Review sections where only PowerShell is used for querying or updating resources and add CLI equivalents.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a balanced overview of migrating to Flexible orchestration in Virtual Machine Scale Sets, but there are subtle signs of Windows bias. Windows-specific scenarios (such as VM activation and Windows updates) are mentioned before Linux equivalents (e.g., Linux package manager access), and there are no explicit Linux-focused migration examples or CLI commands. All command-line examples use Azure CLI, which is cross-platform, but the documentation does not provide Linux-specific considerations or troubleshooting steps, nor does it mention Linux tools or patterns where relevant.
Recommendations
  • Add explicit Linux migration scenarios, such as handling SSH keys, cloud-init, or Linux-specific VM extensions.
  • When listing outbound connectivity requirements, mention Linux package manager access before or alongside Windows activation and updates.
  • Include troubleshooting steps or references for common Linux VM migration issues (e.g., hostname changes, network configuration, package updates).
  • Provide examples of Linux VM extension usage or configuration in Flexible orchestration mode.
  • Ensure that any references to PowerShell are accompanied by Bash/Azure CLI equivalents, if 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-04 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 tasks, but PowerShell examples are consistently presented after CLI and before ARM template examples. PowerShell is a Windows-centric tool, and its inclusion may suggest a slight Windows bias, especially since Linux/macOS users typically use Azure CLI or ARM templates. However, all CLI examples are cross-platform and presented first, and no Windows-only tools or patterns are used. There are no missing Linux examples, and all instructions are applicable to Linux/macOS users.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and that PowerShell is primarily for Windows users.
  • Consider adding Bash script examples for common automation scenarios to further demonstrate Linux parity.
  • Clarify in introductory sections that all features described are available regardless of VM OS, unless otherwise noted.
  • If possible, add a short note for each code tab indicating platform compatibility (e.g., 'Azure CLI: Windows, Linux, macOS; PowerShell: Windows').
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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response and installation. However, there are several instances where Windows/PowerShell examples are presented before or alongside Linux equivalents, and PowerShell is given equal prominence to Bash, which may create minor friction for Linux/macOS users. The extension installation and querying sections use both Azure CLI and PowerShell, but PowerShell is not relegated to a secondary position, and the REST API is presented last. There are no critical omissions of Linux instructions, and the documentation explicitly supports both ApplicationHealthLinux and ApplicationHealthWindows extension types.
Recommendations
  • Present Linux/Bash/Azure CLI examples before Windows/PowerShell examples in each tabbed section to reflect the majority usage on Azure and avoid implicit prioritization of Windows.
  • Clarify in introductory sections that all steps and features apply equally to both Linux and Windows VMSS instances.
  • Where possible, add explicit macOS notes or examples (e.g., for running the Python HTTP server) to further improve parity.
  • Ensure that REST API examples use ApplicationHealthLinux in at least one snippet to reinforce Linux support.
  • Consider grouping CLI and Bash examples together, and PowerShell separately, to make it easier for Linux/macOS users to follow.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides Azure portal, Azure CLI, and Azure PowerShell instructions for attaching and detaching VMs to/from scale sets. In each case, Azure PowerShell examples are given equal prominence to Azure CLI, and PowerShell is a Windows-centric tool. The CLI examples use Ubuntu images, showing Linux is supported, but PowerShell is always listed as a primary method, and examples are not explicitly labeled as Windows-only. The troubleshooting section links to some Windows-specific docs (e.g., converting unmanaged disks, proximity placement groups) without Linux equivalents or clarifying applicability.
Recommendations
  • Clearly label Azure PowerShell examples as Windows-only, and note that PowerShell is primarily for Windows users.
  • Provide Bash or shell script equivalents for Linux/macOS users where PowerShell is shown.
  • Ensure troubleshooting links and migration steps reference both Windows and Linux documentation where applicable (e.g., disk migration, proximity placement group removal).
  • Consider listing Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Add a brief note at the top clarifying that Azure CLI is recommended for Linux/macOS users, while PowerShell is for Windows.
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-03 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 creating and updating scale sets with Availability Zones, but PowerShell examples are given equal prominence to CLI, and are shown before REST/ARM template examples. While CLI is cross-platform, PowerShell is primarily a Windows tool (though available on Linux/macOS, it's less commonly used there). The documentation does not provide any Linux/macOS-specific shell examples (e.g., Bash), nor does it clarify CLI usage on Linux/macOS. The ARM template section does link to both Linux and Windows quickstart articles, but in the main walkthrough, Windows-centric tooling (PowerShell) is featured as a primary method.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS as well as Windows.
  • Consider providing Bash shell examples for Linux/macOS users, especially for common operations like az vmss create.
  • If PowerShell is shown, clarify its cross-platform availability, but note that CLI is the recommended tool for Linux/macOS.
  • Ensure that Linux/macOS users are not left to infer that PowerShell is required.
  • In the 'Use Azure Resource Manager templates' section, clarify parity between Linux and Windows deployments, and ensure links to both quickstart guides are equally visible.
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-03 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 for both Windows and Linux scenarios, but Windows-specific tasks (such as VM activation and Windows updates) are mentioned before Linux equivalents, and there are no explicit Linux/PowerShell/Bash command examples or Linux migration patterns shown. The CLI example is generic, but the narrative and troubleshooting links prioritize Windows use cases.
Recommendations
  • Include explicit Linux migration considerations and examples, such as package manager connectivity requirements (apt/yum) and troubleshooting steps for Linux VMs.
  • Provide CLI or script examples for Linux environments (e.g., Bash, cloud-init) alongside PowerShell or generic Azure CLI examples.
  • Balance the order of mention between Windows and Linux scenarios (e.g., discuss Linux package manager connectivity before or alongside Windows activation and updates).
  • Reference Linux-specific documentation for troubleshooting and best practices 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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides example commands for Azure CLI, PowerShell, Portal, and ARM templates. While Azure CLI is cross-platform, PowerShell examples are given equal prominence and detail, and are presented immediately after CLI in each section. There is a slight Windows-first bias in the ordering and inclusion of PowerShell examples, which are primarily relevant to Windows users. However, all critical tasks (configuring, monitoring, canceling, and restarting rolling upgrades) can be completed using the cross-platform Azure CLI, and no functionality is locked to Windows/PowerShell tools.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider listing CLI examples before PowerShell in each section to reinforce Linux parity.
  • Add a short note in each PowerShell section clarifying that PowerShell Core is available on Linux/macOS, or link to installation instructions for PowerShell on non-Windows platforms.
  • Where possible, clarify that all operations can be performed via CLI, and PowerShell is an alternative for those who prefer it.
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-03 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 Azure CLI and PowerShell examples for most networking tasks with Azure Virtual Machine Scale Sets, but PowerShell (Windows-centric) examples are often presented before CLI (cross-platform) equivalents. In some sections, only PowerShell is shown for querying resources, with CLI examples provided separately or later. There is a slight tendency to mention Windows tools or patterns first, and some examples (such as querying public IPs) are more detailed for PowerShell than CLI. No Linux-specific shell examples (e.g., bash scripts) are given, and the documentation does not reference Linux-native tools or patterns outside of Azure CLI.
Recommendations
  • Present Azure CLI (cross-platform) examples before or alongside PowerShell examples to avoid Windows-first bias.
  • Ensure all PowerShell examples have equivalent Azure CLI examples, especially for querying and managing resources.
  • Add explicit notes or examples for Linux/macOS users where CLI usage may differ (e.g., environment variables, shell syntax).
  • Consider including bash script snippets or references to Linux-native tools where relevant.
  • Clarify that Azure CLI is the recommended tool for cross-platform scenarios.
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-03 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, and covers Azure CLI, PowerShell, and REST API for extension installation and querying. However, in several places, Windows/PowerShell examples are presented before Linux/Bash equivalents, and PowerShell scripts are detailed and prominent. The extension installation section lists PowerShell after CLI, but the PowerShell example is more verbose and detailed. The extension type examples use both ApplicationHealthLinux and ApplicationHealthWindows, but the REST API and PowerShell samples default to Windows extension types. There is a slight preference for Windows tools and ordering, but Linux parity is generally maintained.
Recommendations
  • Ensure that Linux examples (Bash, Python) are presented before or alongside Windows/PowerShell examples, especially in sections where ordering implies priority.
  • In REST API examples, alternate between ApplicationHealthLinux and ApplicationHealthWindows for extension type, or explicitly show both.
  • Clarify in introductory sections that all examples are available for both Linux and Windows VMSS instances.
  • Where possible, balance the detail level between Bash and PowerShell scripts, so Linux users have equally comprehensive guidance.
  • Consider adding a table or note summarizing OS-specific extension types and usage patterns for clarity.
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-02 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 responses and installing the application health extension. However, there are several instances of Windows bias: PowerShell examples are often presented before or alongside Linux equivalents, Windows extension types (ApplicationHealthWindows) are shown first in some code blocks, and Windows-specific tools (PowerShell cmdlets) are given equal prominence to cross-platform CLI commands. The REST API and Azure CLI examples are cross-platform, but some sections (such as the PowerShell install and response server) are more detailed than their Linux counterparts.
Recommendations
  • Ensure Linux and Windows examples are presented with equal detail and prominence; consider alternating which is shown first.
  • In code samples where both ApplicationHealthLinux and ApplicationHealthWindows are referenced, clarify which to use for each OS and provide explicit examples for both.
  • Add more troubleshooting and verification steps for Linux environments, such as systemd service setup or firewall configuration.
  • Where PowerShell scripts are provided, ensure Bash/Linux equivalents are equally comprehensive.
  • Review sample outputs and ensure they do not default to Windows extension types unless contextually appropriate.
GitHub Create Pull Request
← Previous Page 10 of 11 Next →