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 76-100 of 274 flagged pages
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-03-06 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 referenced in every section. PowerShell is a Windows-centric tool, and its inclusion may create friction for Linux/macOS users, especially since Azure CLI is cross-platform. In some sections, PowerShell is listed after CLI, but its presence throughout the page is notable. No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, but the CLI examples are sufficient for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider adding Bash shell script examples for common operations, or explicitly mention that Azure CLI commands work on Linux/macOS.
  • If PowerShell is included, note that it is available cross-platform (PowerShell Core), but most Linux users will prefer Azure CLI.
  • Ensure that CLI examples are always shown first, or provide a clear parity statement.
  • Add a brief section or note for Linux/macOS users about tool choice and compatibility.
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-03-06 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell examples are often presented before CLI examples, and some sections (such as querying public IPs) give more detailed PowerShell guidance. There is a slight preference for Windows/PowerShell tools, but Linux parity is generally maintained via CLI and ARM template examples.
Recommendations
  • Present CLI and PowerShell examples side-by-side or in a consistent order (e.g., CLI first, then PowerShell) to avoid perceived Windows-first bias.
  • Ensure all PowerShell examples have equivalent CLI examples, especially for querying and managing resources.
  • Explicitly mention that Azure CLI commands work cross-platform (Linux, macOS, Windows) to reinforce parity.
  • Where possible, add Bash shell script examples for advanced scenarios to further support Linux users.
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
Low Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation covers automatic OS image upgrades for Azure Virtual Machine Scale Sets and is intended for both Windows and Linux users. It provides examples for REST API, Azure PowerShell, Azure CLI, ARM templates, and Bicep. However, PowerShell examples are presented before CLI examples throughout, and ARM template snippets default to Windows images. Some minor references to Windows-specific properties (e.g., enableAutomaticUpdates) are necessary for Windows VMs but are not flagged as bias. Overall, Linux parity is maintained, but Windows tools and patterns are shown first, which may create minor friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
  • In ARM template and Bicep snippets, use a Linux image as the default example or provide parallel examples for both Windows and Linux.
  • Explicitly state that all examples (PowerShell, CLI, ARM, Bicep) work for both Windows and Linux scale sets unless otherwise noted.
  • Where referencing Windows-specific properties, clarify their relevance and provide equivalent Linux guidance if applicable.
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-03-06 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 before REST API and after CLI. There is a slight 'windows_first' bias in listing PowerShell as a primary method alongside CLI, and the PowerShell example uses Windows-specific syntax. The Resource Manager template section references both Linux and Windows getting started articles, but overall, Linux-specific shell examples (e.g., Bash) are not provided, nor are there explicit notes about Linux/macOS compatibility for CLI commands.
Recommendations
  • Explicitly state that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Add Bash shell examples or clarify that CLI commands can be run in Bash, zsh, or other Linux shells.
  • Consider listing CLI examples before PowerShell in all sections to reinforce Linux parity.
  • Add notes about PowerShell being Windows-centric and recommend CLI for Linux/macOS users.
  • Ensure that any screenshots or UI references are not Windows-specific.
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-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 Azure CLI and PowerShell examples for enabling Automatic Zone Balance, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI and REST, and sometimes before CLI. Portal instructions are platform-neutral, but PowerShell examples use Windows-specific extension types (e.g., ApplicationHealthWindows), while CLI uses ApplicationHealthLinux. The PowerShell section is more verbose and detailed, suggesting a Windows-centric audience. However, Linux parity is generally maintained via CLI and REST examples, and the feature itself is not Windows-specific.
Recommendations
  • Ensure that PowerShell and CLI examples are presented in parallel, with CLI (Linux/macOS-friendly) examples shown first where possible.
  • Clarify in PowerShell examples when Windows-specific extensions are used, and provide Linux equivalents if applicable.
  • Add explicit notes about cross-platform support for Azure CLI and REST API, highlighting their suitability for Linux/macOS users.
  • Consider including Bash shell script examples for Linux users, especially for automation.
  • Review the ordering of tabs and sections to avoid subtle prioritization of Windows tools.
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-03-05 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 tasks, but PowerShell is featured equally alongside CLI and is presented as a primary automation method. PowerShell is a Windows-centric tool, and its inclusion as a main example (rather than Bash or Linux-native scripting) may create friction for Linux/macOS users. However, the Azure CLI examples are present and complete, and the tasks can be accomplished on Linux/macOS using the CLI. There are no Windows-only tools or patterns, and no critical sections are Windows-exclusive.
Recommendations
  • Consider adding Bash shell scripting examples for Linux/macOS users, especially for automation scenarios.
  • Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users, while PowerShell is primarily for Windows (unless using PowerShell Core).
  • If possible, provide links or notes about using PowerShell Core on Linux/macOS for parity.
  • Ensure that CLI examples are always shown before PowerShell, or explicitly note that CLI is recommended for non-Windows platforms.
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-03-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for most operations, but PowerShell examples are often presented before CLI examples, and some sections (e.g., querying public IPs) show PowerShell commands first or exclusively. 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 all PowerShell examples have equivalent CLI examples, especially for querying and managing resources.
  • Highlight that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Where possible, add Bash scripting examples for advanced scenarios.
  • Review sections where PowerShell is shown exclusively and add CLI equivalents if missing.
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-03-05 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 CLI examples are generic and suitable for Linux/macOS, but the documentation does not explicitly highlight Linux-specific workflows or tools. The 'getting started' ARM template section does link to both Linux and Windows quick-starts, which is positive. Overall, the bias is minor and mostly in the ordering and prominence of PowerShell.
Recommendations
  • Ensure Azure CLI examples are always shown before PowerShell, as CLI is the primary cross-platform tool.
  • Add explicit Bash shell examples where relevant, especially for Linux/macOS users.
  • Clarify that PowerShell examples are also valid for Linux/macOS, or provide notes about cross-platform compatibility.
  • Where possible, provide links to Linux/macOS-specific quick-starts or troubleshooting guides.
  • Consider adding a section or note about using Bash or other shells for Linux users.
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-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 Linux (Bash/Python) and Windows (PowerShell) examples for configuring the application health extension response, but Windows/PowerShell examples are often presented alongside or immediately after Linux examples. In the extension installation section, the PowerShell example uses 'ApplicationHealthWindows' as the extension type, while the CLI example uses 'ApplicationHealthLinux', but neither is clearly explained or prioritized. PowerShell is given equal prominence to Bash, and Windows-specific extension types and tools (PowerShell cmdlets) are referenced. However, Linux parity is generally maintained, and CLI/Bash examples are present throughout.
Recommendations
  • Clarify when to use 'ApplicationHealthLinux' vs 'ApplicationHealthWindows' extension types, and explicitly mention OS-specific requirements.
  • Ensure Linux/Bash examples are presented first, or at least equally, in all sections.
  • Add explicit notes about cross-platform support for Azure CLI and REST API, emphasizing their availability on Linux/macOS.
  • Where PowerShell examples are given, ensure equivalent Bash or CLI examples are always present and clearly labeled.
  • Consider adding a table summarizing which commands/tools are available for each OS.
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-03-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 most tasks, but PowerShell examples are often presented before CLI examples, and some sections (such as querying public IPs) show PowerShell commands first or in greater detail. Portal instructions are also included, but there is a slight tendency to present Windows-centric tools (PowerShell) before cross-platform CLI equivalents. No critical features are Windows-only, and Linux parity is generally maintained.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell examples in each section.
  • Ensure all PowerShell examples have equivalent Azure CLI examples, and vice versa.
  • Where possible, clarify that Azure CLI works on Linux/macOS/Windows, and PowerShell is primarily Windows-focused.
  • Add explicit notes or links for Linux/macOS users if any step differs or requires additional setup.
  • Review for any minor omissions of CLI examples and add them for completeness.
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
Low Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation covers both Windows and Linux VM Scale Sets, but there is a mild Windows bias in example ordering and tooling. Windows/PowerShell examples are often presented before Linux/Azure CLI equivalents, and ARM/Bicep template snippets default to Windows images. However, Linux support is clearly described, and CLI examples are provided throughout. No critical Linux gaps are present.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples so Linux users see their preferred tooling first in some sections.
  • Provide ARM/Bicep template snippets that default to a Linux image (e.g., Ubuntu) alongside the Windows example.
  • Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Where possible, clarify that all features and examples apply equally to Linux and Windows unless otherwise noted.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for enabling Automatic Zone Balance on Virtual Machine Scale Sets. However, PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and in some sections, PowerShell examples are shown before or with equal prominence to CLI. The Application Health extension examples use 'ApplicationHealthWindows' in PowerShell, while CLI uses 'ApplicationHealthLinux', but there is no explicit explanation or parity guidance for Linux/macOS users regarding PowerShell alternatives or cross-platform scripting. Additionally, the portal instructions reference screenshots and steps that may be more familiar to Windows users, but do not exclude Linux/macOS users.
Recommendations
  • Clarify that Azure PowerShell is cross-platform, but provide explicit guidance for Linux/macOS users (e.g., installation links, usage notes).
  • Ensure that CLI examples are presented before PowerShell, as Azure CLI is natively cross-platform.
  • Add notes or links for Linux/macOS users on how to use Azure CLI and PowerShell in their environments.
  • Where extensions differ (e.g., ApplicationHealthWindows vs ApplicationHealthLinux), explain the distinction and provide both examples in each scripting section.
  • Consider including Bash shell scripting examples for common automation scenarios.
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-03-04 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), but PowerShell examples are always present and shown alongside CLI. Azure PowerShell is a Windows-centric tool, and its inclusion in every section, with detailed parameters, may signal a Windows bias. Additionally, PowerShell examples are sometimes more elaborate than their CLI counterparts. However, Azure CLI is cross-platform and is included throughout, mitigating the bias. No Windows-only tools or patterns are mentioned, and Linux users can complete all tasks using Azure CLI.
Recommendations
  • Consider clarifying that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
  • If possible, provide Bash shell scripting examples for common scenarios (e.g., chaining CLI commands, error handling) to further support Linux users.
  • Review the order of examples: consider listing Azure CLI before PowerShell to emphasize cross-platform parity.
  • Explicitly state that Azure PowerShell is primarily for Windows users, and that Azure CLI is suitable for all platforms.
GitHub Create Pull Request
Virtual Machine Scale Sets Azure Virtual Machine Scale Sets Attached Data Disks ...cale-sets/virtual-machine-scale-sets-attached-disks.md
Low Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux examples for preparing attached data disks in Azure Virtual Machine Scale Sets, but the Windows example is presented first. Both Azure CLI and PowerShell tutorials are linked, and the custom script extension examples are given for both OS types. There are no missing Linux examples or exclusive mention of Windows tools.
Recommendations
  • Present Windows and Linux examples side-by-side or alternate their order to avoid implicit prioritization.
  • Explicitly mention that both Windows and Linux are supported in the introductory sections.
  • Ensure parity in detail and clarity between Windows and Linux instructions.
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-03-04 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 major tasks (setting, updating, monitoring, canceling, and restarting rolling upgrades). However, PowerShell examples are consistently included alongside CLI, and in some sections, PowerShell is presented immediately after CLI, which may subtly reinforce Windows-centric workflows. There are no Linux-specific examples, but the Azure CLI is cross-platform and is presented first in most cases. No Windows-only tools or patterns are mentioned, and all features described are platform-agnostic.
Recommendations
  • Explicitly note that Azure CLI commands work equally on Linux, macOS, and Windows.
  • Consider adding brief Bash shell scripting examples for common automation scenarios, highlighting Linux/macOS workflows.
  • Clarify that PowerShell examples are for Windows and PowerShell Core users, while CLI is recommended for cross-platform use.
  • If possible, add a section or note about using Azure CLI in Bash or zsh shells, and reference installation instructions for Linux/macOS.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux (Bash/Python) and Windows (PowerShell) examples for configuring custom metrics and the application health extension. However, there are several instances where Windows/PowerShell examples are presented first or in greater detail. Windows-specific extension types (ApplicationHealthWindows) are used in some code snippets and REST examples, sometimes without clear Linux alternatives. PowerShell scripts are more elaborate and detailed than Bash examples, and Windows tools (PowerShell cmdlets) are featured prominently alongside Azure CLI and REST. Linux examples are present but sometimes less detailed or not shown first.
Recommendations
  • Ensure Linux examples (using ApplicationHealthLinux) are shown alongside or before Windows examples in all relevant code snippets and REST payloads.
  • Provide equally detailed Bash/Python scripts for Linux as are provided for PowerShell/Windows.
  • Clarify in REST and extension configuration sections that both ApplicationHealthLinux and ApplicationHealthWindows are supported, and show both in sample payloads.
  • Where possible, avoid presenting Windows/PowerShell examples first unless there is a clear reason (e.g., user base data).
  • Expand troubleshooting and verification sections to include Linux-specific commands and scenarios.
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-03-03 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) show PowerShell commands first or exclusively. There is a slight preference for Windows/PowerShell tooling, but Linux parity is generally maintained via CLI and ARM template examples.
Recommendations
  • Ensure CLI examples are always presented alongside PowerShell, and consider showing CLI examples first to avoid implicit Windows-first bias.
  • Where possible, add Bash shell examples for common Linux workflows, especially for querying resources.
  • Explicitly note that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Review all sections to ensure no critical task is only documented with PowerShell.
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-03-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides orchestration mode concepts for Azure Virtual Machine Scale Sets and is intended to be platform-neutral, supporting both Linux and Windows VMs. However, there are subtle signs of Windows bias: the only explicit command-line example uses Azure CLI but does not show Linux shell syntax (e.g., bash), and the mention of Azure Site Recovery is qualified as 'via PowerShell' without mentioning Linux alternatives or parity. Additionally, the documentation sometimes refers to Windows and Linux together, but Windows is often mentioned first or more prominently.
Recommendations
  • Provide explicit Linux shell (bash) examples alongside Azure CLI and PowerShell examples, especially for critical operations.
  • Clarify Azure Site Recovery support for Linux VMs and document any Linux-specific steps or limitations.
  • Ensure parity in mentioning both Windows and Linux in feature tables and descriptions, avoiding Windows-first ordering unless justified.
  • Where extensions or tooling are referenced (e.g., Application Health Extension), note any Linux-specific considerations or installation steps.
GitHub Create Pull Request
Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority View Details →
Scanned: 2026-03-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 Azure CLI and PowerShell examples for enabling Automatic Zone Balance, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI and REST, and in some sections, PowerShell examples reference Windows-specific extension names (e.g., ApplicationHealthWindows). In the PowerShell example for adding the Application Health extension, only the Windows extension is shown, while the CLI example uses the Linux extension. The ordering of tabs sometimes puts PowerShell before CLI, and the PowerShell section assumes familiarity with Windows tooling. There are no explicit Linux/macOS gaps, but the documentation could be clearer about cross-platform parity and extension types.
Recommendations
  • Clarify in PowerShell examples how to use Application Health extensions for both Windows and Linux VMSS (e.g., show ApplicationHealthLinux as well as ApplicationHealthWindows).
  • Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users, and consider listing CLI before PowerShell in tab order.
  • Add a note explaining that PowerShell is available cross-platform, but Windows users may be more familiar with it.
  • Where extension types differ (ApplicationHealthWindows vs ApplicationHealthLinux), provide both examples or guidance for each OS.
  • Ensure all screenshots and portal steps are OS-agnostic or clarify if any are Windows-specific.
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-03-03 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 signal Windows bias, especially since Linux users typically use Bash/CLI. Additionally, PowerShell examples are shown immediately after CLI, rather than being separated or clearly marked as Windows-only. However, Azure CLI examples are present and use Linux-friendly syntax (e.g., Ubuntu image), and no critical steps are Windows-only.
Recommendations
  • Clearly label PowerShell examples as 'Windows only' or 'for Windows users', and Azure CLI examples as 'for Linux/macOS users'.
  • Consider providing Bash script examples where appropriate, or clarify that Azure CLI is cross-platform and preferred for Linux/macOS.
  • If possible, reorder examples so Azure CLI is shown before PowerShell, or group PowerShell examples in a separate section for Windows users.
  • Add a note explaining that Azure PowerShell is primarily for Windows environments, while Azure CLI is cross-platform.
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
Low Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation provides both Windows and Linux parity in terms of supported OS images and configuration methods for automatic OS image upgrades in Azure Virtual Machine Scale Sets. However, there is a mild Windows bias in some areas: Windows-specific properties are mentioned first in requirements, PowerShell examples (which are Windows-centric) are presented before Azure CLI (cross-platform) examples, and ARM template snippets default to Windows images. There are no missing Linux examples, and Linux support is clearly documented, but Windows patterns and tools are sometimes prioritized.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
  • In ARM template and Bicep snippets, provide both Windows and Linux image examples, or use a Linux image as the default.
  • Where Windows-specific properties are discussed (e.g., enableAutomaticUpdates), clarify Linux equivalents or explicitly state when they are not applicable.
  • Ensure all sections referencing tools or commands include Linux-friendly options or clarify platform neutrality.
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-03-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 all tasks, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI and sometimes after CLI. There are no Linux-specific examples (e.g., Bash scripting), but Azure CLI is cross-platform and is shown first in most cases. The PowerShell sections are prominent, but do not prevent Linux/macOS users from completing any task, as all operations can be performed via Azure CLI or ARM templates.
Recommendations
  • Explicitly note that Azure CLI commands work on Linux, macOS, and Windows, and are the recommended cross-platform option.
  • Consider adding Bash shell scripting examples for common automation scenarios, or clarifying that Azure CLI commands can be used in Bash scripts.
  • If PowerShell is shown, clarify that Azure PowerShell is available cross-platform (via PowerShell Core), but CLI is generally preferred for Linux/macOS users.
  • Ensure that CLI examples are always shown before PowerShell, and that the documentation does not imply PowerShell is required.
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-03-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 and Windows examples for configuring custom metrics in rolling upgrades on Virtual Machine Scale Sets. 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 scripts and Azure PowerShell cmdlets are given equal prominence to Bash and Azure CLI, but Windows tools and patterns (e.g., PowerShell HTTP server, Windows extension type) are sometimes mentioned first or exclusively in certain code blocks. REST API examples also default to Windows extension types. Overall, Linux parity is present but not always prioritized.
Recommendations
  • Ensure Linux/Bash examples are presented before or alongside Windows/PowerShell examples in all code tabs and sections.
  • Use ApplicationHealthLinux as the default extension type in generic sample code and REST API payloads, or provide both Linux and Windows variants.
  • Clarify in each section that both Linux and Windows are supported, and highlight any differences explicitly.
  • Add troubleshooting steps and sample output for both Linux and Windows, not just Windows.
  • Review REST API and PowerShell sample payloads to ensure Linux examples are included and not overshadowed by Windows defaults.
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-03-02 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 rolling upgrades on Virtual Machine Scale Sets. However, PowerShell examples are consistently presented alongside CLI, and in some sections, PowerShell is shown immediately after CLI. There are no Linux-specific examples (e.g., Bash scripting), but since Azure CLI is cross-platform and the documentation does not reference Windows-only tools or patterns, the bias is minor. The documentation does not mention Linux or macOS users explicitly, nor does it provide parity guidance for those environments.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash shell scripting examples or clarify that CLI commands can be run in Bash on Linux/macOS.
  • Consider including a note for Linux/macOS users about installing Azure CLI and using it in their preferred shell.
  • Ensure PowerShell examples are not presented before CLI, as CLI is more cross-platform.
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-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides some Windows-specific scenarios (e.g., Windows VM activation, Windows updates) before mentioning Linux equivalents (e.g., Linux package manager access). There are no explicit Linux-focused migration examples, commands, or troubleshooting links. Azure CLI is referenced, but no Linux-specific shell or command examples are given. The overall guidance is generic, but Windows scenarios are mentioned first and more prominently.
Recommendations
  • Add explicit Linux migration scenarios and troubleshooting links (e.g., guidance for Linux VM updates, package manager outbound connectivity).
  • Provide Linux-specific command examples or references (e.g., Bash shell, Linux CLI usage).
  • Ensure Linux scenarios (such as package manager access) are mentioned alongside or before Windows scenarios where relevant.
  • Include links to Linux documentation for Azure VM activation, updates, and outbound connectivity.
  • Balance the order and prominence of Windows and Linux scenarios in outbound connectivity and migration sections.
GitHub Create Pull Request
← Previous Page 4 of 11 Next →