Virtual Machine Scale Sets

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

Bias Trend Over Time

Pages with Bias Issues

129 issues found
Showing 1-25 of 129 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 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
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-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides conceptual information about orchestration modes for Azure Virtual Machine Scale Sets and includes some command-line examples (e.g., az vm create) without specifying OS-specific instructions. However, in the 'Backup and recovery' section, Azure Site Recovery is noted as supported only 'via PowerShell' for Flexible orchestration, without mentioning Linux/CLI alternatives. Additionally, the documentation sometimes references Windows and Linux together (e.g., mixing OSes in scale sets), but Windows-specific tooling (PowerShell) is mentioned where Linux parity is unclear.
Recommendations
  • Clarify whether Azure Site Recovery for Flexible orchestration mode can be used with Azure CLI or REST API, and provide Linux/macOS-compatible instructions if possible.
  • Where PowerShell is mentioned, add equivalent Azure CLI or REST API examples for Linux/macOS users.
  • Ensure all command-line examples (such as az vm create) are shown with correct syntax for both Windows and Linux shells, avoiding Windows-specific formatting.
  • Explicitly state OS compatibility for features and tools, and provide links or references for Linux/macOS users 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-14 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 deployment, but does not provide explicit Linux/bash examples or mention Linux tools. Azure PowerShell is listed alongside Azure CLI, but there are no bash or shell script examples. Windows-specific scenarios (activation, updates) are mentioned before Linux equivalents, and Windows examples (such as activation and updates) are listed first in outbound connectivity requirements. The only command example is Azure CLI, which is cross-platform, but there are no explicit Linux/macOS shell examples or guidance.
Recommendations
  • Add explicit Linux/bash shell script examples for key migration steps, especially where Azure CLI is used.
  • Ensure Linux-specific scenarios (such as package manager access) are given equal prominence to Windows scenarios in outbound connectivity requirements.
  • Mention Azure CLI as the primary cross-platform tool, and clarify that PowerShell is Windows-centric, with alternatives for Linux/macOS users.
  • Provide links or references to Linux/macOS documentation for relevant Azure VM operations.
  • Where PowerShell is referenced, add equivalent bash/CLI examples for Linux/macOS users.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for enabling Automatic Zone Balance on Virtual Machine Scale Sets. However, PowerShell (a Windows-centric tool) is given equal prominence to CLI, and there are several examples using PowerShell. The Application Health extension example in PowerShell uses 'ApplicationHealthWindows' as the extension type, while the CLI example uses 'ApplicationHealthLinux', which may cause confusion or friction for Linux users. Additionally, PowerShell examples are presented in all major sections, and the tab order sometimes places PowerShell before CLI, indicating a mild Windows-first bias.
Recommendations
  • Ensure that Linux-focused examples (Azure CLI) are always presented before PowerShell in tab order and narrative.
  • Clarify when to use 'ApplicationHealthLinux' vs 'ApplicationHealthWindows' extension types, and provide both examples in PowerShell and CLI sections.
  • Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add a note or section for macOS users if any steps differ.
  • Review tab ordering to ensure CLI is first, followed by PowerShell, to reduce Windows-first bias.
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-13 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 Template as migration tools, 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 before CLI in some places. There are no explicit Linux/macOS-focused migration steps or examples, and the CLI example is minimal and not clearly cross-platform.
Recommendations
  • Provide explicit bash/Linux/macOS examples alongside PowerShell, especially for migration steps.
  • Ensure Azure CLI examples are clearly cross-platform and not just shown as an alternative to PowerShell.
  • Mention Linux package manager connectivity needs before or alongside Windows activation/update scenarios.
  • Clarify that all steps can be performed from Linux/macOS using Azure CLI or ARM templates.
  • Add links or references to Linux/macOS-specific documentation 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-10 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. Azure PowerShell is mentioned alongside Azure CLI, but CLI examples are not shown. Windows-specific scenarios (activation, updates) are listed before Linux (package managers) in outbound connectivity requirements. No explicit Linux/macOS guidance or parity is provided, and PowerShell is referenced as a primary scripting option.
Recommendations
  • Add explicit bash/Linux shell examples for key operations (e.g., az CLI commands for VM creation, migration, querying, etc.).
  • Mention Linux/macOS compatibility for Azure CLI and ARM templates, and clarify that PowerShell is optional for Windows users.
  • Provide Linux-specific migration considerations, such as package manager connectivity, and list Linux scenarios alongside Windows ones.
  • Ensure that Linux tools and workflows (e.g., bash scripts, cloud-init) are referenced where relevant.
  • Consider alternating the order of Windows and Linux scenarios/examples to avoid 'windows_first' bias.
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-08 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. Azure PowerShell is mentioned alongside Azure CLI, but PowerShell is a Windows-centric tool. Windows-specific scenarios (Windows VM activation, Windows updates) are listed before Linux equivalents (Linux package managers) in the networking section. No explicit Linux/macOS command examples or parity guidance is provided.
Recommendations
  • Provide explicit bash/Linux command examples alongside Azure PowerShell, especially for VM creation and migration steps.
  • Mention Azure CLI as the primary cross-platform tool, and clarify PowerShell is optional for Windows users.
  • List Linux scenarios (e.g., package manager access) before or alongside Windows scenarios in relevant sections.
  • Add references or links to Linux-specific migration considerations or troubleshooting guides.
  • Ensure all example commands are shown in both Azure CLI and PowerShell formats, or clarify which are 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
Medium 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 references both Azure CLI and Azure PowerShell for creating and managing Virtual Machine Scale Sets, but does not provide explicit Linux/macOS shell examples or parity in command-line instructions. PowerShell is mentioned alongside Azure CLI, but no bash or Linux-native scripting examples are given. Windows-specific scenarios (activation, updates) are listed before Linux equivalents, and some network connectivity examples highlight Windows needs first.
Recommendations
  • Provide explicit bash/Linux shell examples for key Azure CLI commands, especially for VM creation and migration steps.
  • Include Linux-specific migration considerations (e.g., package manager connectivity, Linux VM extension installation).
  • Balance example order: list Linux and Windows scenarios together, or alternate which is mentioned first.
  • Reference Linux-native tools or scripting patterns where appropriate, not just PowerShell.
  • Clarify that Azure CLI commands are cross-platform and provide sample commands in bash syntax.
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-02 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 is shown for querying public IPs, with CLI mentioned but not exemplified. There are also cases where Windows tools (PowerShell) are referenced more heavily than Linux/macOS equivalents, and some example queries (e.g., for public IPs) lack explicit Linux/macOS CLI parity.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
  • Ensure every PowerShell example has an equivalent Azure CLI example, especially for querying and managing resources.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide bash syntax where appropriate.
  • Where possible, add Linux/macOS-specific notes or troubleshooting tips if there are platform differences.
  • Review tab ordering so that CLI is not deprioritized after PowerShell.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation occasionally references Windows-specific scenarios (e.g., Windows VM activation, Windows updates) before Linux equivalents and does not provide Linux-specific examples or parity in some sections. While Linux is mentioned (e.g., access to Linux package managers), examples and troubleshooting links are more detailed for Windows. There are no CLI or script examples that demonstrate Linux-specific migration or configuration patterns, and PowerShell is mentioned alongside Azure CLI, but no Bash or Linux shell examples are provided.
Recommendations
  • Provide Linux-specific migration examples, such as using Bash scripts or Linux CLI workflows.
  • Include troubleshooting links for common Linux scenarios (e.g., SSH connectivity, package manager access) similar to the Windows VM activation troubleshooting link.
  • Ensure that references to OS-specific requirements (e.g., updates, activation) mention both Windows and Linux in equal detail.
  • Add explicit Linux-focused guidance for outbound connectivity (e.g., apt/yum updates, SSH key management).
  • Where PowerShell is referenced, also provide equivalent Bash or shell script examples for Linux/macOS users.
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-02-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and ARM templates. While the CLI and ARM template sections are cross-platform, PowerShell examples are given equal prominence and detail, and in some cases, appear before Linux-specific guidance. The ARM template section references both Linux and Windows getting started articles, but the CLI and PowerShell sections do not clarify OS context. No explicit Linux shell (bash) examples are provided, and PowerShell (Windows-centric) is presented as a primary method alongside CLI.
Recommendations
  • Add explicit bash shell examples for Linux/macOS users, especially for Azure CLI commands.
  • Clarify that Azure CLI commands are cross-platform and can be run from Linux/macOS terminals.
  • Where PowerShell is shown, provide equivalent bash commands or note that PowerShell Core is available cross-platform.
  • In step-by-step sections, alternate or parallelize examples for Linux and Windows, rather than presenting PowerShell as a default.
  • Ensure that links to 'getting started' articles for Linux and Windows are equally visible and not Windows-first.
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-02-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides Azure CLI, PowerShell, and ARM template examples for creating scale sets with Availability Zones. While the CLI and ARM template examples are cross-platform, PowerShell (Windows-only) is given equal prominence and detailed examples. The ARM template section links to both Linux and Windows quickstart guides, but the main walkthroughs and update instructions do not provide explicit Linux shell (bash) or macOS examples. Windows/PowerShell tooling is mentioned before Linux equivalents in some sections, and Linux-specific considerations (such as SSH keys or Linux admin users) are not highlighted outside the CLI example.
Recommendations
  • Add explicit bash shell examples for Linux/macOS users, especially for update operations and scale set management.
  • Clarify in each section which commands are cross-platform and which are Windows-only.
  • Ensure Linux and Windows quickstart links are presented together and with equal prominence.
  • Consider adding notes or callouts for Linux-specific configuration steps (e.g., SSH keys, admin username conventions).
  • Where PowerShell is used, provide equivalent bash/CLI commands for Linux/macOS users.
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-01 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) examples are often presented before CLI (Linux/macOS compatible) examples. In several sections, only PowerShell is shown for certain operations, or CLI examples are less detailed. Some verification steps use PowerShell exclusively, and there are places where Linux-specific guidance is missing or less emphasized.
Recommendations
  • Ensure that CLI examples are always present and as detailed as PowerShell examples for every operation.
  • Present CLI (cross-platform) examples before PowerShell examples to avoid implicit Windows prioritization.
  • Where PowerShell is used for querying or updating resources, provide equivalent CLI commands and highlight their parity.
  • Explicitly note that CLI commands work on Linux/macOS and Windows, and encourage their use for cross-platform scenarios.
  • Review all verification and troubleshooting steps to ensure Linux users are not left out or forced to use Windows tools.
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-01-31 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 there is a tendency to present PowerShell (Windows) examples before CLI (cross-platform) ones, and some sections (such as querying public IPs) offer more detailed PowerShell examples than CLI. In some cases, PowerShell examples are given without explicit Linux/macOS CLI equivalents, and there are no bash scripting examples for advanced tasks. The documentation does not mention Linux-specific tools or patterns, and the order of examples sometimes favors Windows/PowerShell first.
Recommendations
  • Ensure CLI (az) examples are always present and as detailed as PowerShell examples, especially for querying and updating resources.
  • Present CLI examples before PowerShell examples to emphasize cross-platform parity.
  • Add bash scripting examples for advanced tasks where PowerShell scripts are shown.
  • Explicitly mention that CLI commands work on Linux/macOS and Windows, and clarify any platform-specific limitations.
  • Where REST API or ARM template examples are given, provide CLI commands to perform equivalent operations if possible.
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-01-31 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides example commands for both Azure CLI and Azure PowerShell, but in several sections, PowerShell (a Windows-centric tool) is given equal prominence to CLI, and sometimes appears before Linux-specific details. The Azure Resource Manager template section references both Linux and Windows getting started articles, but the PowerShell examples are detailed and prominent, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Ensure that Azure CLI examples are shown first, as CLI is cross-platform and preferred for Linux/macOS users.
  • Where PowerShell examples are given, explicitly note that PowerShell is primarily for Windows users, and suggest Azure CLI for Linux/macOS.
  • Add Bash shell script examples where appropriate, especially for scale set management tasks.
  • In update/expansion sections, provide full Azure CLI command sequences alongside PowerShell, not just a single command.
  • Consider a tabbed format for CLI, PowerShell, and REST API, with CLI as the default tab.
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-01-27 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 related to Azure Virtual Machine Scale Sets, but PowerShell (a Windows-centric tool) is often presented before CLI, and some sections (such as querying public IPs) give more detailed PowerShell examples than CLI. There are also places where only PowerShell is shown for a task, or where CLI examples are less complete. While ARM templates and REST API examples are cross-platform, the documentation leans toward Windows/PowerShell in example ordering and detail.
Recommendations
  • Ensure CLI examples are provided for every PowerShell example, with equal detail and clarity.
  • Present CLI examples before PowerShell examples, or at least alternate their ordering to avoid Windows-first bias.
  • Where PowerShell is used for querying or updating resources, provide equivalent Bash/CLI commands.
  • Explicitly note that CLI commands work on Linux/macOS and Windows, and clarify any platform-specific caveats.
  • Review all example sections to ensure Linux/macOS users can complete all tasks without needing PowerShell.
GitHub Create Pull Request
Virtual Machine Scale Sets Maintenance notifications for Virtual Machine Scale Sets in Azure ...tps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-maintenance-notifications.md
Medium Priority View Details →
Scanned: 2026-01-22 01:38
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for managing maintenance notifications and actions on Virtual Machine Scale Sets. However, PowerShell examples are presented first and in greater detail, with CLI examples following. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is a Windows-centric tool, although it is available cross-platform. The documentation does not mention Linux/macOS-specific considerations or tools, and scheduled events are linked only to Windows documentation.
Recommendations
  • Present Azure CLI (cross-platform) examples before or alongside PowerShell examples to avoid Windows-first bias.
  • Include Bash shell examples for common queries and actions using Azure CLI to improve accessibility for Linux/macOS users.
  • Link to both Windows and Linux versions of scheduled events documentation, or clarify that scheduled events are available for Linux VMs as well.
  • Explicitly state that PowerShell and CLI commands work on Linux/macOS where applicable.
  • Add notes or sections highlighting any Linux/macOS-specific considerations or limitations.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a Virtual Machine Scale Set with instance mix ...cles/virtual-machine-scale-sets/instance-mix-create.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples for Azure Portal, Azure CLI, Azure PowerShell, and REST API. While CLI and REST API are cross-platform, the PowerShell section is extensive and detailed, with multiple example scenarios and configuration objects, whereas the CLI section is brief and limited to basic usage. The prerequisites mention PowerShell and its module version before CLI, and PowerShell examples are given equal or greater prominence than CLI, which may indicate a Windows bias. There are no Linux-specific tools or shell examples (e.g., Bash scripts), and PowerShell is a Windows-centric tool, despite its cross-platform availability.
Recommendations
  • Expand the Azure CLI section to include advanced scenarios, such as using configuration objects and allocation strategies, matching the depth of PowerShell examples.
  • Add Bash script examples for Linux users, especially for tasks like parameter substitution and automation.
  • In prerequisites, mention CLI and PowerShell together, or list CLI first to avoid Windows-first perception.
  • Clarify that PowerShell is available cross-platform, but highlight Linux-native tools where possible.
  • Consider adding a section or tips for Linux/macOS users, such as SSH key management or environment setup.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a Virtual Machine Scale Set with instance mix ...cles/virtual-machine-scale-sets/instance-mix-create.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Azure CLI and PowerShell examples side-by-side, but PowerShell (a Windows-centric tool) receives more detailed and advanced coverage, including configuration object usage. The prerequisites mention both CLI and PowerShell, but PowerShell is listed second. There are no explicit Linux shell (bash) examples, and PowerShell commands are more numerous and complex than CLI examples, suggesting a bias toward Windows tooling and workflows.
Recommendations
  • Add bash-specific examples for Linux users, especially for advanced scenarios currently covered only in PowerShell.
  • Ensure parity in example complexity and coverage between CLI and PowerShell sections.
  • Explicitly mention Linux environments and workflows in prerequisites and examples.
  • Consider listing CLI (cross-platform) before PowerShell in prerequisites and example sections.
  • Add troubleshooting or tips relevant to Linux environments, such as SSH key management, file permissions, and shell scripting.
GitHub Create Pull Request
Virtual Machine Scale Sets Enable Automatic Zone Balance on Virtual Machine Scale Sets (Preview) ...virtual-machine-scale-sets/auto-zone-balance-enable.md
Low Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for enabling Automatic Zone Balance on Virtual Machine Scale Sets. However, PowerShell examples (which are Windows-centric) are consistently presented alongside or after CLI examples, and the PowerShell extension configuration uses 'ApplicationHealthWindows' as the type, even in contexts where Linux is clearly supported. Portal instructions are platform-neutral, but PowerShell is a Windows tool and its prominence, as well as the lack of explicit Linux/macOS PowerShell guidance, creates a mild Windows bias. The CLI examples use Ubuntu images and 'ApplicationHealthLinux', showing Linux support, but PowerShell examples do not clarify Linux usage.
Recommendations
  • Clarify that Azure PowerShell can be used cross-platform (Windows, Linux, macOS) and provide explicit instructions/examples for Linux/macOS users if relevant.
  • In PowerShell extension examples, show both 'ApplicationHealthWindows' and 'ApplicationHealthLinux' usage, or explain when to use each.
  • Consider presenting CLI (Linux-friendly) examples before PowerShell (Windows-centric) examples, or explicitly state parity.
  • Add a note that both Azure CLI and PowerShell are available on all major platforms, and link to installation guides for Linux/macOS.
  • Ensure that screenshots and portal instructions do not assume Windows-only environments.
GitHub Create Pull Request
Virtual Machine Scale Sets Migrate deployments and resources to Virtual Machine Scale Sets in Flexible orchestration ...lexible-virtual-machine-scale-sets-migration-resources.md
Low Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides a balanced overview of migrating to Flexible orchestration mode in Azure Virtual Machine Scale Sets. However, in the 'Create scalable network connectivity' section, Windows-specific scenarios (Windows VM activation, Windows updates) are mentioned before Linux equivalents (Linux package managers). There are no PowerShell-heavy examples, Windows tools, or missing Linux examples; the CLI and ARM Template are referenced alongside PowerShell, and all migration steps are generic to Azure VMs regardless of OS.
Recommendations
  • When listing common outbound connectivity scenarios, mention Linux package manager access before or alongside Windows activation and updates to avoid subtle Windows-first bias.
  • Ensure that any example commands or scripts (such as az vm create) are shown in both Azure CLI and PowerShell where relevant, and clarify OS-agnostic steps.
  • If referencing troubleshooting or update scenarios, provide links or notes for both Windows and Linux VM activation/update documentation.
GitHub Create Pull Request
Virtual Machine Scale Sets Attach or detach a virtual machine to or from a Virtual Machine Scale Set ...le-sets/virtual-machine-scale-sets-attach-detach-vm.md
Low Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all operations (attach, detach, move), but consistently presents PowerShell examples alongside CLI and portal instructions. PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias, especially since Linux/macOS users typically use Azure CLI or REST APIs. Additionally, PowerShell examples are sometimes more detailed than their CLI counterparts. However, Azure CLI examples are present and use Linux-friendly syntax (e.g., Ubuntu image), mitigating the bias.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows. Consider linking to instructions for installing Azure PowerShell on Linux/macOS.
  • Ensure that Azure CLI examples are as detailed as PowerShell examples, especially for networking and advanced options.
  • Consider adding REST API or ARM template examples for users who prefer those methods, especially on Linux/macOS.
  • Explicitly state that all operations can be performed from Linux/macOS using Azure CLI, and highlight any differences if present.
  • If possible, reorder examples to show Azure CLI before PowerShell, or alternate the order to avoid 'windows_first' bias.
GitHub Create Pull Request
← Previous Page 1 of 6 Next →