Virtual Machine Scale Sets

186
Total Pages
138
Linux-Friendly Pages
48
Pages with Bias
25.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

143 issues found
Showing 26-50 of 143 flagged pages
Virtual Machine Scale Sets Use extension sequencing with Azure Virtual Machine Scale Sets ...ets/virtual-machine-scale-sets-extension-sequencing.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples for extension sequencing use Windows-centric tools (PowerShell and Azure CLI) and reference Windows-based scale sets. The examples specifically mention and use Windows extensions (ApplicationHealthWindows, CustomScriptExtension for Windows), with no mention or example for Linux-based scale sets or Linux extensions. The PowerShell example is presented before the CLI example, and both are tailored to Windows environments. There are no Linux-specific instructions, examples, or references.
Recommendations
  • Add equivalent examples for Linux-based scale sets, using Linux extensions such as ApplicationHealthLinux and CustomScriptExtension for Linux.
  • Include sample Azure CLI and PowerShell commands for Linux VMSS extension sequencing.
  • Reference Linux extension documentation and provide links to Linux extension resources.
  • Clarify in the text that extension sequencing applies to both Windows and Linux scale sets, and highlight any OS-specific differences.
  • Present examples for both Windows and Linux side-by-side or alternate their order to avoid Windows-first bias.
GitHub Create Pull Request
Virtual Machine Scale Sets Terminate notification for Azure Virtual Machine Scale Set instances ...s/virtual-machine-scale-sets-terminate-notification.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows moderate Windows bias: Windows/Powershell examples and links are presented before Linux equivalents, with PowerShell-specific instructions and links to Windows documentation appearing more prominently. Linux-specific examples (e.g., bash scripts, Linux CLI patterns) are less detailed or referenced only via links. The REST API and Azure CLI sections are cross-platform, but the PowerShell section is Windows-centric, and some cross-references (e.g., Scheduled Events) link to Windows docs first.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate their order to avoid Windows-first bias.
  • Add explicit bash or shell script examples for querying/responding to Scheduled Events, not just PowerShell.
  • Ensure all cross-references to Scheduled Events and event properties link to both Windows and Linux documentation equally.
  • Include troubleshooting steps and tips that mention Linux-specific tooling or issues.
  • Highlight Azure CLI as a cross-platform tool and provide parity in example detail with PowerShell.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 is a notable Windows bias: PowerShell examples are consistently present and sometimes more detailed, Windows-specific extension types (ApplicationHealthWindows) are shown before Linux equivalents, and Windows tooling (PowerShell cmdlets) is given equal or greater prominence than Linux CLI/Bash workflows. In some places, Windows extension types are used as defaults in examples, and PowerShell scripts are more elaborate than Bash equivalents.
Recommendations
  • Ensure Linux and Windows extension types are shown side-by-side in all examples, not defaulting to Windows.
  • Provide equally detailed Bash/Python scripts for Linux as for PowerShell on Windows, including troubleshooting and server setup.
  • Where both CLI and PowerShell are shown, alternate which is presented first, or use neutral ordering.
  • Explicitly mention Linux/macOS compatibility and provide guidance for common Linux distributions.
  • Clarify when examples are OS-specific and provide parity for both platforms in every workflow.
GitHub Create Pull Request
Virtual Machine Scale Sets Update a Virtual Machine Scale Set with instance mix ...cles/virtual-machine-scale-sets/instance-mix-update.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides example commands for Azure CLI, PowerShell, and REST API. However, the PowerShell section is given equal prominence to CLI, despite PowerShell being primarily a Windows tool. The PowerShell examples are extensive and detailed, while there are no equivalent examples for Linux-native scripting (e.g., Bash). Additionally, PowerShell is listed before REST API, and there is no mention of Linux/macOS-specific considerations or alternative tools. The CLI examples are cross-platform, but the presence and depth of PowerShell examples indicate a moderate Windows bias.
Recommendations
  • Clarify that Azure CLI examples work on Linux, macOS, and Windows.
  • Add Bash shell scripting examples for Linux/macOS users, especially for more complex update scenarios.
  • Consider moving PowerShell examples after CLI and REST API, or grouping them in a 'Windows-specific' section.
  • Explicitly mention platform compatibility for each example (e.g., 'Works on Linux/macOS/Windows').
  • Provide troubleshooting tips for Linux/macOS users if there are known differences.
GitHub Create Pull Request
Virtual Machine Scale Sets Customer intent: As a cloud administrator, I want to deploy and customize Virtual Machine Scale Sets, so that I can efficiently manage workloads and optimize resource utilization in my existing infrastructure. ...virtual-machine-scale-sets/includes/mvss-next-steps.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page primarily references Azure Resource Manager deployment via PowerShell, which is a Windows-centric tool. There are no explicit Linux or cross-platform CLI examples, and the initial deployment instructions point to PowerShell documentation. While there is a mention of deploying a Linux scale set, the overall guidance and examples favor Windows tools and patterns.
Recommendations
  • Include Azure CLI examples alongside PowerShell for deployment steps, as Azure CLI is cross-platform.
  • Reference Bash or shell scripting options for Linux/macOS users.
  • Add links to Linux/macOS-specific documentation for deploying and managing scale sets.
  • Ensure that examples and instructions are presented in a platform-neutral order or explicitly note alternatives for non-Windows users.
GitHub Create Pull Request
Virtual Machine Scale Sets Get standby pool and instance details ...irtual-machine-scale-sets/standby-pools-get-details.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 (a Windows-centric tool) is given equal prominence as CLI, and is presented immediately after CLI in every section. There are no Linux-specific shell examples (e.g., Bash, curl), nor are there notes about running PowerShell on Linux/macOS. The examples and instructions do not mention Linux/macOS environments or tools, and PowerShell is implicitly assumed to be available.
Recommendations
  • Add explicit Bash/curl examples for REST API calls to demonstrate Linux/macOS usage.
  • Clarify that PowerShell examples can be run on Linux/macOS using PowerShell Core, or provide instructions for installing PowerShell on non-Windows platforms.
  • Consider listing CLI (cross-platform) examples before PowerShell, and add notes about CLI being available on all platforms.
  • Include troubleshooting or environment setup notes for Linux/macOS users where relevant.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a scale set that uses Azure Spot Virtual Machines ...b/main/articles/virtual-machine-scale-sets/use-spot.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Azure Spot Virtual Machines in scale sets, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented with a full example. There is no explicit Linux shell (bash) example, and the PowerShell section references a Windows-specific getting started article. The simulated eviction section links only to a Windows/PowerShell article for further information, omitting Linux guidance. The ARM template section references both Linux and Windows, but the example is generic. Overall, Windows tools and patterns are featured as primary or equal options, with Linux-specific instructions and examples underrepresented.
Recommendations
  • Add explicit bash/Linux shell examples for key tasks, especially for simulating eviction and deploying scale sets.
  • Provide links to Linux-specific documentation for simulated eviction and other advanced tasks, not just Windows/PowerShell articles.
  • Ensure that Azure CLI (cross-platform) examples are presented before PowerShell, or clarify CLI as the recommended cross-platform approach.
  • Where PowerShell is referenced, include a note about its availability on Linux/macOS, or provide alternative Linux-native instructions.
  • Balance references to getting started articles so both Linux and Windows users are equally supported.
GitHub Create Pull Request
Virtual Machine Scale Sets Use Application Health extension with Azure Virtual Machine Scale Sets ...le-sets/virtual-machine-scale-sets-health-extension.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation shows a notable Windows bias in deployment examples and tooling. In multi-tabbed deployment sections, Windows/PowerShell examples are consistently presented first, with Linux/Azure CLI examples following. PowerShell is the only scripting language shown for imperative scripting, and all PowerShell examples target Windows-based scale sets. REST API examples also default to Windows. Linux-specific examples are only present in the Azure CLI sections, and there are no Linux PowerShell or Bash scripting examples. Troubleshooting commands are PowerShell-centric, and Windows log paths are listed before Linux equivalents. This ordering and tooling focus create friction for Linux/macOS users.
Recommendations
  • Present Linux and Windows examples in parallel, or alternate which is shown first to avoid implicit prioritization.
  • Provide imperative scripting examples for Linux users (e.g., Bash scripts using Azure CLI, or cross-platform PowerShell with ApplicationHealthLinux).
  • Ensure REST API examples alternate or include both ApplicationHealthLinux and ApplicationHealthWindows in the 'type' property.
  • In troubleshooting, show Linux log paths before or alongside Windows paths, and provide Azure CLI commands for health state retrieval.
  • Explicitly state that all extension operations are supported on both Linux and Windows, and clarify any differences in behavior or support.
GitHub Create Pull Request
Virtual Machine Scale Sets Terminate notification for Azure Virtual Machine Scale Set instances ...s/virtual-machine-scale-sets-terminate-notification.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows and PowerShell examples are presented before Linux/Azure CLI equivalents, and Windows-specific links and terminology (e.g., referencing Windows scheduled events documentation first) are used throughout. PowerShell is given a dedicated section with detailed examples, while Linux-specific scripting (such as Bash or Python) is only briefly referenced, with no explicit Bash example for querying/responding to scheduled events. The REST API and Azure CLI sections are platform-neutral, but the overall structure and example ordering favor Windows users.
Recommendations
  • Present Linux/Azure CLI examples before or alongside Windows/PowerShell examples to ensure parity.
  • Include explicit Bash or Python examples for querying and responding to scheduled events, not just links.
  • Reference both Windows and Linux scheduled events documentation equally in all relevant sections.
  • Add troubleshooting steps specific to Linux environments (e.g., curl/jq usage, common errors).
  • Clarify that Azure CLI commands work cross-platform and highlight any OS-specific considerations.
GitHub Create Pull Request
Virtual Machine Scale Sets Azure Disk Encryption and Azure Virtual Machine Scale Sets extension sequencing ...ine-scale-sets/disk-encryption-extension-sequencing.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page presents Windows-centric examples, such as PowerShell scripts and Windows disk formatting, in the main template samples. Linux-specific guidance is relegated to a single external link, and no Linux shell script example is shown inline. Windows tools and extensions are referenced first and exclusively in the main body, creating friction for Linux users.
Recommendations
  • Include an inline example of extension sequencing using a Linux shell script (e.g., bash) for disk formatting, not just as an external link.
  • Present both Windows and Linux scenarios side-by-side or in parallel sections to ensure equal visibility.
  • Reference Linux tools and patterns (e.g., bash scripts, Linux disk utilities) in the main template samples.
  • Clarify which examples apply to Windows and which to Linux in the text, to avoid confusion.
  • Ensure that Linux-specific extensions and workflows are documented with the same level of detail as Windows.
GitHub Create Pull Request
Virtual Machine Scale Sets Enable Azure Disk Encryption for Virtual Machine Scale Sets ...virtual-machine-scale-sets/disk-encryption-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While it mentions both Windows and Linux support, it highlights Windows capabilities (OS and data disk encryption) before Linux (data disks only, with OS disk encryption explicitly unsupported). The tutorials referenced include both Azure CLI (cross-platform) and PowerShell (Windows-centric), but do not explicitly mention Linux-specific guidance or examples. There is no direct Linux command-line example or parity in instructions, and the limitations for Linux are stated after Windows features.
Recommendations
  • Add explicit Linux command-line examples (e.g., Bash, Azure CLI on Linux) and clarify Linux-specific steps.
  • Present Linux and Windows capabilities side-by-side, rather than listing Windows features first.
  • Include a section or link for Linux troubleshooting and workarounds for unsupported features (e.g., OS disk encryption).
  • Ensure tutorial links specify which platforms they target, and provide equivalent Linux-focused tutorials where possible.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific scenarios (such as VM activation and Windows updates) are mentioned before Linux equivalents, and troubleshooting links are provided only for Windows. There are no explicit Linux-focused migration or troubleshooting examples, and Linux package manager access is mentioned only briefly and after Windows scenarios. Command-line examples use Azure CLI, which is cross-platform, but PowerShell is referenced as an alternative without Linux shell equivalents. There are no Linux/macOS-specific instructions or considerations.
Recommendations
  • Add explicit Linux migration scenarios and troubleshooting links (e.g., for Linux VM activation, package manager connectivity).
  • Provide Linux/macOS command-line examples (e.g., bash scripts) alongside Azure CLI and PowerShell.
  • Mention Linux-specific tools or patterns where relevant, such as cloud-init or SSH key management.
  • Ensure Linux scenarios (e.g., updates, connectivity) are described with equal detail and priority as Windows scenarios.
  • Reference Linux documentation for common tasks (e.g., troubleshooting, updates) in the same way as Windows.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a scale set from a generalized image ...chine-scale-sets/instance-generalized-image-version.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed PowerShell examples for creating scale sets, including both simplified and extended parameter sets, which are specific to Windows environments. The CLI examples are present and generally cross-platform, but the PowerShell section is much more extensive, with advanced networking and load balancer configuration shown only in PowerShell. There is no mention of Linux shell scripting or equivalent advanced automation for Linux/macOS users. Additionally, the PowerShell tab is placed after CLI and Portal, but the depth of PowerShell coverage and the use of Windows-centric tools (e.g., Get-Credential, New-AzResourceGroup) indicate a bias toward Windows users.
Recommendations
  • Add equivalent advanced examples using Bash shell scripting and Azure CLI for Linux/macOS users, covering networking and load balancer configuration.
  • Explicitly mention that PowerShell examples are for Windows and provide links or guidance for Linux/macOS automation.
  • Ensure that all advanced scenarios shown in PowerShell are also available in CLI or ARM template examples.
  • Consider adding a section on using Azure CLI in Bash scripts for automation, including credential management and resource configuration.
GitHub Create Pull Request
Virtual Machine Scale Sets Configure role permissions for standby pools ...hine-scale-sets/standby-pools-configure-permissions.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by exclusively referencing the Azure portal (a web GUI most commonly used on Windows) for role assignment steps and troubleshooting, without providing equivalent CLI or automation examples (such as Azure CLI or Bash scripts) that are platform-agnostic and preferred by many Linux/macOS users. The only mention of SDKs includes 'PowerShell' before 'CLI', and no explicit Linux/macOS tooling or examples are given.
Recommendations
  • Add step-by-step instructions for assigning roles using Azure CLI and/or Azure PowerShell, with example commands.
  • Provide troubleshooting examples using Azure CLI (az monitor, az role assignment, etc.) alongside portal-based instructions.
  • Explicitly mention that all steps can be performed on Linux/macOS using CLI tools, and provide links to relevant cross-platform documentation.
  • List SDKs in a neutral order (e.g., 'CLI or PowerShell') or highlight cross-platform options first.
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 06:17
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 Azure CLI is cross-platform and shown before PowerShell, the PowerShell section is extensive and detailed, with multiple example scenarios and advanced usage. There is a slight bias toward Windows tooling, as PowerShell is a Windows-first tool and its coverage is more comprehensive than the CLI section. Additionally, prerequisites mention PowerShell before CLI, and the CLI examples use Ubuntu images but do not discuss Linux-specific considerations or parity with PowerShell features.
Recommendations
  • Expand Azure CLI examples to cover advanced scenarios currently only shown for PowerShell, such as using configuration objects.
  • Add notes or examples for Bash scripting and Linux shell environments, especially for tasks like credential management and network configuration.
  • Ensure that CLI and PowerShell sections have parity in terms of depth and complexity of examples.
  • Explicitly mention that Azure CLI is fully supported on Linux/macOS and highlight any differences or limitations compared to PowerShell.
  • In prerequisites, list CLI before PowerShell to signal platform neutrality.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a scale set from a specialized image version using the Azure CLI ...chine-scale-sets/instance-specialized-image-version.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides detailed PowerShell examples for creating a scale set from a specialized image, including extensive networking and load balancer configuration, while the CLI (cross-platform) examples are much simpler and lack equivalent depth. The PowerShell section uses Windows-centric tooling and patterns, and is presented before the CLI in the main specialized image scenario. There is no mention of Linux/macOS-specific considerations or parity in scripting depth.
Recommendations
  • Expand the Azure CLI section to include more comprehensive examples, matching the depth of the PowerShell walkthrough (e.g., networking, load balancer setup).
  • Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
  • Add notes or examples for Linux/macOS users where PowerShell is referenced, including alternative commands or scripts.
  • Consider presenting CLI examples before PowerShell, or side-by-side, to avoid Windows-first impression.
  • Highlight any OS-specific requirements or differences in resource creation, if applicable.
GitHub Create Pull Request
Virtual Machine Scale Sets Proximity placement groups for Virtual Machine Scale Sets ...rtual-machine-scale-sets/proximity-placement-groups.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias: all code examples use PowerShell cmdlets, with no Azure CLI or Linux/macOS shell equivalents provided inline. Windows tools and patterns (PowerShell, cmdlets) are mentioned and demonstrated exclusively and before any reference to Linux alternatives. The only mention of Azure CLI is in a 'Next steps' link, rather than integrated examples. This creates friction for Linux/macOS users, who must seek out separate documentation or translate PowerShell examples themselves.
Recommendations
  • Add inline Azure CLI examples alongside PowerShell for all key tasks (creating/listing proximity placement groups, creating scale sets, checking status).
  • Explicitly mention Linux/macOS support and provide bash shell snippets where appropriate.
  • Reorganize examples so that CLI and PowerShell approaches are presented together or in parallel sections.
  • Ensure references to Linux documentation are as prominent as Windows/PowerShell equivalents.
  • Clarify that all operations are cross-platform and not limited to Windows/PowerShell.
GitHub Create Pull Request
Virtual Machine Scale Sets Create a standby pool for Virtual Machine Scale Sets ...les/virtual-machine-scale-sets/standby-pools-create.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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, but PowerShell is given its own dedicated tab and is mentioned alongside deployment tools for ARM and Bicep templates. Windows-centric tools (PowerShell, New-AzResourceGroupDeployment) are referenced as primary deployment options, and PowerShell is presented before Linux-native alternatives in several places. There are no explicit Linux/macOS examples or notes about cross-platform usage for CLI commands.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • List CLI examples before PowerShell examples to reduce Windows-first impression.
  • For ARM and Bicep template deployment, highlight az deployment group create (CLI) as the primary method, and mention PowerShell as an alternative.
  • Add notes or links for Linux/macOS users, clarifying that all CLI commands work natively on those platforms.
  • Consider including bash script examples or references to shell usage for Linux/macOS users.
GitHub Create Pull Request
Virtual Machine Scale Sets Overview of autoscale with Azure Virtual Machine Scale Sets ...-sets/virtual-machine-scale-sets-autoscale-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows-centric tools (PowerShell) are frequently mentioned, often before cross-platform alternatives (Azure CLI). Examples for manual scaling are provided for Azure Portal, Azure CLI, and Azure PowerShell, but no explicit Linux shell or macOS terminal examples are given. References to management and next steps prioritize PowerShell, and links to PowerShell tutorials and management guides are listed before CLI or template options. There is a lack of parity in example ordering and tool coverage for Linux/macOS users.
Recommendations
  • Provide explicit Linux/macOS shell examples (e.g., Bash) alongside PowerShell, especially for common tasks.
  • Order cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) in examples and next steps.
  • Include links to Linux/macOS management guides and tutorials where available.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide platform-specific notes if needed.
  • Balance references to PowerShell and CLI throughout the documentation to ensure equal visibility.
GitHub Create Pull Request
Virtual Machine Scale Sets Use extension sequencing with Azure Virtual Machine Scale Sets ...ets/virtual-machine-scale-sets-extension-sequencing.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing examples and instructions primarily for Windows-based scale sets, referencing Windows-specific extensions (ApplicationHealthWindows, CustomScriptExtension for Windows), and using Windows-centric tools (PowerShell, Windows extension types) without showing equivalent Linux examples or mentioning Linux extension types. Both the Azure PowerShell and Azure CLI examples are explicitly for Windows-based scale sets, and there is no guidance for Linux-based scale sets or Linux extensions.
Recommendations
  • Add parallel examples for Linux-based scale sets, using Linux-specific extensions (e.g., ApplicationHealthLinux, CustomScriptExtension for Linux).
  • Explicitly mention the applicability of extension sequencing to Linux VMSS and provide sample ARM templates, REST API payloads, PowerShell, and CLI commands for Linux scenarios.
  • Ensure that documentation references both Windows and Linux extension types and links to their respective documentation.
  • Where possible, present examples for both platforms side by side or clarify platform-specific differences.
GitHub Create Pull Request
Virtual Machine Scale Sets Deploy an application to an Azure Virtual Machine Scale Set ...ne-scale-sets/virtual-machine-scale-sets-deploy-app.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Linux and Windows deployment options, but there is a notable Windows bias: Windows/PowerShell examples and tools (PowerShell DSC, PowerShell cmdlets) are described in greater detail and appear before Linux equivalents. The Windows section includes a full PowerShell script, while the Linux section refers users to external documentation for cloud-init and does not provide an inline example. Windows management tools (PowerShell DSC, Update-AzVmss, etc.) are highlighted, while Linux alternatives (such as Ansible or native Linux configuration management) are not mentioned. Some links and next steps also prioritize PowerShell/Windows management.
Recommendations
  • Provide inline, detailed cloud-init examples for Linux, similar to the PowerShell DSC example for Windows.
  • Mention and link to Linux-native configuration management tools (e.g., Ansible, Chef, Puppet) as alternatives to PowerShell DSC.
  • Ensure Linux examples are presented with equal prominence and detail as Windows examples.
  • Balance references to management tools (CLI, PowerShell) by including Linux-friendly options and workflows.
  • In 'Next steps', include links to Linux management guides, not just PowerShell/Windows guides.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed PowerShell examples and references, with CLI examples included but presented after PowerShell. There is a notable lack of explicit Linux/macOS shell examples or discussion of platform-specific considerations. The 'scheduled events' link and section reference Windows documentation, and there is no mention of Linux-specific tools or patterns. This creates friction for Linux/macOS users, though most tasks can be completed using the Azure CLI.
Recommendations
  • Provide Bash or shell script examples alongside PowerShell for all command-line instructions.
  • Reference both Windows and Linux/macOS scheduled events documentation, not just Windows.
  • Clarify that Azure CLI commands work cross-platform and highlight any platform-specific differences.
  • Add notes or examples for Linux users where PowerShell is mentioned, such as using Azure CLI or REST API.
  • Ensure links to scheduled events and other features point to both Windows and Linux 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
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 most networking tasks, but PowerShell (a Windows-centric tool) is often presented before CLI, and some sections (such as querying public IPs) give more detailed PowerShell examples. References to Windows-specific scenarios (e.g., Windows VM activation) are present, and PowerShell is used heavily in example scripts. Linux/macOS users may find parity, but Windows tools and patterns are often prioritized or more deeply covered.
Recommendations
  • Present CLI examples before PowerShell, as CLI is cross-platform.
  • Ensure all PowerShell examples have equivalent, fully detailed CLI examples.
  • Add Bash script examples where scripting is shown for PowerShell.
  • When referencing OS-specific scenarios (e.g., Windows VM activation), also mention Linux equivalents or clarify when not applicable.
  • Avoid referring to PowerShell as the default or primary automation tool; emphasize CLI for cross-platform parity.
GitHub Create Pull Request
Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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. However, there is a notable Windows bias: PowerShell examples are consistently present and detailed, sometimes appearing before or alongside Linux equivalents. Windows-specific extension types (ApplicationHealthWindows) are used in several code samples and REST payloads, often as the default or first shown. The PowerShell tab is always present and sometimes more verbose than the Bash/Linux tab. REST API examples also default to Windows extension types. While Linux users are not blocked from completing the task, Windows tools and patterns are emphasized, and Linux parity could be improved.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail, alternating which is shown first.
  • In REST API and JSON configuration samples, use ApplicationHealthLinux as the default or provide both Linux and Windows variants.
  • Expand Bash/Python/Linux examples to match the depth and clarity of PowerShell examples, including troubleshooting and verification steps.
  • Explicitly mention cross-platform compatibility and clarify when a step or tool is OS-specific.
  • Provide macOS-specific notes or examples where relevant, especially for scripting and endpoint configuration.
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-13 06:17
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 Azure PowerShell examples for creating and updating scale sets with Availability Zones, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is sometimes listed before or alongside CLI. There are no explicit Linux shell (bash) examples, nor are Linux-specific considerations or tools mentioned. The ARM template section references both Linux and Windows, but does not provide a Linux shell example for deployment. The overall pattern is to treat Windows/PowerShell as a first-class or default environment, with limited explicit Linux parity.
Recommendations
  • Add explicit bash shell examples for Linux/macOS users alongside Azure CLI and PowerShell sections.
  • Ensure CLI examples are shown before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Clarify that Azure CLI commands work natively on Linux/macOS and provide installation links or notes for those platforms.
  • Where PowerShell is mentioned, add a note that PowerShell Core is available cross-platform, but CLI is recommended for Linux/macOS.
  • Provide a sample ARM template deployment using Azure CLI on Linux/macOS, not just the template JSON.
GitHub Create Pull Request
← Previous Page 2 of 6 Next →