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 1-25 of 143 flagged pages
Virtual Machine Scale Sets Using Desired State Configuration With Virtual Machine Scale Sets ...l-machine-scale-sets/virtual-machine-scale-sets-dsc.md
High Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows and PowerShell Desired State Configuration (DSC). All code examples reference the Microsoft.Powershell.DSC extension and use PowerShell scripts (.ps1), with no mention of Linux equivalents or support for Linux VM extensions. References and links are exclusively for Windows/PowerShell DSC, and there are no Linux-specific instructions or examples.
Recommendations
  • Add sections or notes on using Linux VM extensions for configuration management, such as the Custom Script Extension or Azure Machine Configuration for Linux.
  • Provide equivalent ARM template snippets for configuring Linux VMs or scale sets, using supported Linux extensions.
  • Include references and links to documentation for Linux VM extensions and configuration management tools (e.g., cloud-init, Chef, Puppet, or Ansible on Linux).
  • Clarify in the introduction or notes whether the DSC extension is Windows-only, and guide Linux users to appropriate alternatives.
GitHub Create Pull Request
Virtual Machine Scale Sets Using Desired State Configuration With Virtual Machine Scale Sets ...l-machine-scale-sets/virtual-machine-scale-sets-dsc.md
High Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows and PowerShell Desired State Configuration (DSC). All examples use the Microsoft.Powershell.DSC extension, reference PowerShell scripts (.ps1), and mention Windows Management Framework (WMF) requirements. There is no mention of Linux support, Linux equivalents, or cross-platform DSC options. Linux users are not provided with guidance or examples, making the documentation Windows-centric.
Recommendations
  • Add a section describing DSC support for Linux, including any limitations or prerequisites.
  • Provide ARM template examples for Linux VM Scale Sets using the Linux DSC extension (OmsAgentForLinux or equivalent).
  • Include links to Linux DSC documentation and examples.
  • Clarify in the introduction that the page currently covers only Windows VMs, if Linux is not supported.
  • If Linux is supported, show Linux examples alongside Windows examples, not just after.
  • Mention Linux configuration management alternatives if DSC is not supported for Linux VMSS.
GitHub Create Pull Request
Virtual Machine Scale Sets Tutorial - Install applications in a scale set with Azure PowerShell ...machine-scale-sets/tutorial-install-apps-powershell.md
High Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell. All examples use Azure PowerShell cmdlets and focus on deploying IIS (a Windows-only web server) via PowerShell scripts. There are no Linux or Bash examples, nor any mention of deploying Linux applications or using Linux-native tools. The tutorial assumes Windows as the default platform for both scripting and application deployment.
Recommendations
  • Add parallel examples using Azure CLI and Bash for Linux users.
  • Provide a Linux-focused scenario, such as installing Apache or Nginx on Ubuntu VMSS instances.
  • Include links to the Custom Script Extension documentation for Linux.
  • Explicitly mention that the tutorial is Windows-specific and provide guidance or links for Linux users.
  • Show how to use shell scripts (.sh) with the Custom Script Extension on Linux VMSS.
GitHub Create Pull Request
Virtual Machine Scale Sets Tutorial - Install applications in a scale set with Azure PowerShell ...machine-scale-sets/tutorial-install-apps-powershell.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The tutorial exclusively uses Azure PowerShell and Windows-centric tools, with all examples focused on deploying IIS (a Windows web server) using PowerShell scripts. There are no Linux or Bash examples, nor any mention of Linux application deployment, making the documentation strongly biased toward Windows environments.
Recommendations
  • Add equivalent examples for deploying applications to Linux VM Scale Sets, such as installing Apache or Nginx using Bash scripts.
  • Include sample Custom Script Extension configurations for Linux, demonstrating use of shell scripts and Linux package managers (e.g., apt, yum).
  • Provide Azure CLI commands alongside PowerShell examples for cross-platform parity.
  • Reference both Windows and Linux documentation in the 'Custom Script Extension overview' section.
  • Clarify in the introduction that the tutorial is Windows-specific, or split into separate Windows and Linux guides.
GitHub Create Pull Request
Virtual Machine Scale Sets Using Desired State Configuration With Virtual Machine Scale Sets ...l-machine-scale-sets/virtual-machine-scale-sets-dsc.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows and PowerShell Desired State Configuration (DSC), with all examples and references using Windows-centric tooling (Microsoft.Powershell.DSC, WMF, .ps1 scripts). There is no mention of Linux equivalents, nor examples for configuring Linux VMs or using cross-platform DSC solutions. All links and next steps point to Windows/PowerShell documentation.
Recommendations
  • Add explicit guidance and examples for configuring Linux VM Scale Sets, including supported extensions and configuration management tools (e.g., Azure Custom Script Extension for Linux, Azure Machine Configuration for Linux, or third-party tools like Ansible, Chef, or Puppet).
  • Clarify whether DSC extension is supported for Linux VMs, and if not, provide alternative solutions for Linux users.
  • Include Linux-specific ARM template snippets and walkthroughs alongside Windows examples.
  • Balance references and links to include Linux documentation and cross-platform configuration management resources.
GitHub Create Pull Request
Virtual Machine Scale Sets Creating and configuring a key vault for Azure Disk Encryption ...irtual-machine-scale-sets/disk-encryption-key-vault.md
Medium Priority View Details →
Scanned: 2026-01-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation mentions both Azure CLI and Azure PowerShell as supported tools, but PowerShell is listed before CLI in several places, and the 'Next steps' section gives PowerShell examples equal prominence to CLI. There is no explicit Linux/macOS example or guidance, and PowerShell is a Windows-centric tool, potentially creating friction for Linux/macOS users.
Recommendations
  • List Azure CLI before PowerShell in tool recommendations and examples, as CLI is cross-platform.
  • Explicitly state that Azure CLI works on Linux/macOS and provide links or notes for installation on those platforms.
  • Ensure examples and walkthroughs are available for both Azure CLI and PowerShell, with clear labeling for platform compatibility.
  • Add a brief section or note for Linux/macOS users, confirming parity and pointing to relevant CLI documentation.
GitHub Create Pull Request
Virtual Machine Scale Sets Use Azure Log Analytics to monitor standby pool events ...achine-scale-sets/standby-pools-monitor-pool-events.md
Medium Priority View Details →
Scanned: 2026-01-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring diagnostic settings, but PowerShell is given equal prominence despite being Windows-centric. There is no explicit Linux shell (bash) example, and PowerShell is listed as a primary method alongside CLI and REST. The guidance does not mention Linux-specific considerations or alternative Linux-native tools, and PowerShell is presented as a recommended SDK for non-portal configuration, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit bash shell examples for configuring diagnostic settings using Azure CLI, demonstrating usage on Linux/macOS.
  • Clarify that PowerShell examples are for Windows users, and recommend Azure CLI for cross-platform usage.
  • Reorder examples to present CLI (cross-platform) before PowerShell, and explicitly state CLI is recommended for Linux/macOS.
  • Include a note about installing and using Azure CLI on Linux/macOS.
  • If PowerShell is required for any advanced scenario, explain how to use PowerShell Core on Linux/macOS.
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 00:00
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 for checking and initiating maintenance on Virtual Machine Scale Sets, with CLI equivalents included. However, PowerShell is featured first and in more detail, and there are no explicit Bash or Linux shell script examples. References to 'scheduled events' link to Windows-specific documentation, and there is no mention of Linux-specific guidance or parity for those features.
Recommendations
  • Add explicit Bash or shell script examples for common Linux environments, especially for querying maintenance status and initiating maintenance using the Azure CLI.
  • When referencing 'scheduled events', include or link to Linux/macOS documentation (e.g., scheduled events for Linux VMs) alongside or before Windows links.
  • Present CLI examples before PowerShell, or at least in parallel, to avoid the impression that PowerShell is the primary or preferred method.
  • Clarify that all CLI commands work cross-platform (Windows, Linux, macOS), and provide any Linux/macOS-specific notes if needed.
GitHub Create Pull Request
Virtual Machine Scale Sets Encrypt disks for Azure scale sets with Azure CLI ...cles/virtual-machine-scale-sets/disk-encryption-cli.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Heavy Minor Linux Example
Summary
The documentation is titled and described as focused on Windows Virtual Machine Scale Sets, but the main CLI examples use Linux images and extensions. However, the overall framing, references, and some links (e.g., PowerShell, batch file) are Windows-centric, and Linux parity is not emphasized or clearly separated. Linux is supported, but not highlighted or explained in depth.
Recommendations
  • Clarify in the title and introduction that both Windows and Linux VMSS are supported, or provide separate guides for each.
  • Provide explicit Linux and Windows example sections, with clear instructions for both OS types.
  • Add more Linux-specific context, such as common troubleshooting steps, differences in encryption support, and links to Linux documentation.
  • Avoid referring to batch files for Linux (should use shell scripts), and ensure Linux examples use native Linux tooling and terminology.
  • List Linux examples before or alongside Windows examples to avoid Windows-first bias.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page presents extension sequencing for Azure Disk Encryption but features Windows-centric examples: both JSON template samples use PowerShell scripts or Windows-specific extensions (FormatMBRDisk.ps1, VMDiagnosticsSettings for Windows VMs). Linux scenarios are only referenced via a link, with no in-page Linux shell script example or explicit Linux extension sequencing shown. Windows tools and patterns are mentioned and demonstrated before Linux equivalents.
Recommendations
  • Add an in-page example showing extension sequencing with a Linux VM, using a shell script (e.g., Bash) in CustomScriptExtension.
  • Provide a sample template where Azure Disk Encryption is sequenced after a Linux disk preparation step.
  • Include explicit mention and demonstration of Linux diagnostics extensions if relevant.
  • Ensure Linux examples are presented with equal prominence and detail as Windows examples.
  • Consider showing Linux and Windows examples side-by-side for direct comparison.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by highlighting Windows disk encryption support (OS and data volumes) while Linux support is limited to data volumes only. Tutorial links are presented for both Azure CLI and PowerShell, but PowerShell (a Windows-centric tool) is emphasized alongside CLI. There is no explicit Linux-specific example or guidance, and the limitations for Linux (no OS disk encryption) are mentioned without alternative solutions or parity.
Recommendations
  • Provide explicit Linux-focused examples and tutorials, especially for Azure CLI (which is cross-platform).
  • Clarify limitations for Linux users and suggest alternative security approaches where OS disk encryption is not supported.
  • Ensure Linux documentation is presented with equal prominence to Windows, including example commands and workflows.
  • Add a section addressing Linux-specific considerations and future roadmap for parity.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references deploying templates via the Azure Resource Manager documentation, specifically linking to a PowerShell-based deployment guide. There is no mention of Linux-native tools (such as Azure CLI or bash) for deployment, nor are Linux/macOS workflows or examples provided. The first and only deployment method referenced is PowerShell, which is primarily a Windows tool, creating a Windows-first impression and missing Linux parity.
Recommendations
  • Include links to Azure CLI and bash-based deployment guides alongside the PowerShell reference.
  • Explicitly mention cross-platform options for template deployment, such as Azure CLI, which works on Linux and macOS.
  • Add examples or references for Linux/macOS users to ensure they can follow the documentation without friction.
  • Reorder or balance examples so that Windows and Linux/macOS methods are presented equally.
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-14 01:31
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 advanced usage, whereas Linux/macOS-specific shell examples (e.g., Bash) are absent. The prerequisites mention PowerShell before CLI, and PowerShell commands are given equal or greater prominence than CLI, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Add Bash or shell script examples for Linux/macOS users, especially for advanced scenarios currently only covered in PowerShell.
  • In prerequisites, mention CLI before PowerShell or clarify platform applicability for each tool.
  • Balance example depth: provide equally detailed CLI (or Bash) examples as PowerShell, including advanced configuration scenarios.
  • Explicitly state platform compatibility for each tool and example.
  • Consider adding a table summarizing which tools are recommended for each OS.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is featured first and in greater detail than Azure CLI, with explicit PowerShell cmdlets and examples provided before CLI equivalents. There are no Linux/macOS-specific shell examples (e.g., Bash), nor are there references to Linux tooling or patterns. The FAQ and 'Next steps' sections link to Windows-specific documentation for scheduled events, omitting Linux guidance. This may create friction for Linux/macOS users, though CLI commands are present as alternatives.
Recommendations
  • Provide Bash or shell script examples alongside PowerShell for maintenance operations.
  • Ensure CLI examples are given equal prominence and detail as PowerShell, possibly presenting CLI first or side-by-side.
  • Add links to Linux/macOS scheduled events documentation in 'Next steps' and FAQ sections.
  • Explicitly mention cross-platform compatibility for CLI commands and clarify any OS-specific limitations.
  • Where PowerShell is referenced, note that Azure PowerShell is available on Linux/macOS and provide installation guidance if relevant.
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-14 01:31
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, with extensive use of Windows-centric tools and patterns. The PowerShell section is significantly longer and more detailed than the CLI section, which is more cross-platform. The networking and load balancer setup is only shown in PowerShell, with no equivalent Bash or Linux-native scripting example. The order of examples also places PowerShell after CLI, but the depth of PowerShell coverage suggests a Windows bias. There are no explicit Linux/macOS-specific instructions or troubleshooting notes.
Recommendations
  • Add equivalent Bash shell scripts for all PowerShell examples, especially for networking and load balancer setup.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide OS-specific notes where relevant.
  • Include troubleshooting tips for Linux/macOS users (e.g., file path formats, environment variable usage).
  • Balance example depth: ensure CLI/Bash examples are as comprehensive as PowerShell ones.
  • Reference Linux-native tools or patterns where appropriate (e.g., using SSH instead of RDP for VM access).
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-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. However, PowerShell (a Windows-centric tool) is given its own dedicated section with detailed, multi-step examples, while no equivalent is provided for Bash or shell scripting on Linux/macOS. In each major section, PowerShell is presented before REST API, and the CLI examples are generic but do not mention Linux-specific nuances. There are no explicit Linux/macOS shell scripting examples, nor is there guidance for Linux users who may prefer Bash or other native tools.
Recommendations
  • Add Bash shell scripting examples for Linux/macOS users, especially for multi-step operations currently shown only in PowerShell.
  • Clarify that Azure CLI commands work equally on Linux, macOS, and Windows, and note any OS-specific considerations.
  • Consider reordering sections so that cross-platform tools (CLI, REST API) are presented before Windows-specific tools (PowerShell).
  • Explicitly mention Linux/macOS compatibility and provide troubleshooting tips for those platforms.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page is heavily focused on Windows and PowerShell, with all code examples and step-by-step instructions using Azure PowerShell cmdlets. Linux/Azure CLI equivalents are only mentioned in passing, and no CLI/bash examples are provided. The page title and description specifically reference Windows, and Windows tools (PowerShell) are used exclusively for all practical guidance, leaving Linux/macOS users with minimal actionable information.
Recommendations
  • Add equivalent Azure CLI/bash examples for all PowerShell code snippets, especially for creating, listing, and managing proximity placement groups and VM scale sets.
  • Update the title and description to remove Windows-specific language, making it clear the guidance applies to both Windows and Linux VM Scale Sets.
  • Present CLI and PowerShell examples side-by-side or in separate tabs, ensuring Linux/macOS users have clear, actionable instructions.
  • Reference both Linux and Windows documentation equally in best practices and next steps sections.
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-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 moderate Windows bias. Windows tools (Azure PowerShell) are frequently mentioned and examples are provided for PowerShell before Linux-friendly alternatives. The CLI example is present, but PowerShell is consistently listed first in several sections, and the 'Next steps' and management links focus on PowerShell. There are no explicit Linux/macOS shell examples (e.g., Bash), and no mention of platform-specific nuances for Linux/macOS users. The diagnostics extension section does link to both Linux and Windows instructions, but overall, Windows-centric tools and patterns are prioritized.
Recommendations
  • Ensure that CLI examples (az CLI) are listed before or alongside PowerShell examples.
  • Add explicit Bash or Linux/macOS shell examples where appropriate.
  • Include links to Linux/macOS management documentation in 'Next steps' and management sections.
  • Balance references to Azure PowerShell with Azure CLI throughout the page.
  • Highlight any platform-specific considerations for Linux/macOS users.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides extensive PowerShell examples, which are primarily relevant for Windows users. The PowerShell section is significantly longer and more detailed than the CLI section, including advanced networking and load balancer configuration. Windows-specific tools (PowerShell cmdlets) are featured, and the PowerShell tab appears after CLI but before Linux-native scripting options (none are given). There are no Bash or Linux shell script equivalents for the advanced scenarios, and the CLI examples use generic Azure CLI commands but do not provide parity for the advanced PowerShell scenarios.
Recommendations
  • Add Bash/Linux shell script examples for advanced scenarios currently covered only by PowerShell (e.g., networking, load balancer, and full VMSS configuration).
  • Explicitly mention Linux/macOS compatibility for CLI commands and provide troubleshooting tips for non-Windows environments.
  • Reorder examples to present CLI (cross-platform) before PowerShell, and clarify that PowerShell is Windows-centric.
  • Where PowerShell cmdlets are used for resource creation, provide equivalent Azure CLI or ARM template examples.
  • Highlight SSH key usage and Linux admin practices in examples, not just generic admin/password prompts.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references the Azure portal UI for role assignment and troubleshooting, which is platform-agnostic but most commonly associated with Windows environments. There are no command-line examples (such as Azure CLI or PowerShell) for role assignment, and when SDKs are mentioned, PowerShell is listed before CLI, suggesting a Windows-first approach. No Linux/macOS-specific guidance or parity is provided for key tasks.
Recommendations
  • Add Azure CLI examples for role assignment and troubleshooting alongside or before PowerShell references.
  • Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI or REST API.
  • Provide links to cross-platform command-line documentation for RBAC and Log Analytics tasks.
  • When listing SDKs, mention CLI before PowerShell or present them together to avoid Windows-first bias.
GitHub Create Pull Request
Virtual Machine Scale Sets Use Azure Log Analytics to monitor standby pool events ...achine-scale-sets/standby-pools-monitor-pool-events.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides PowerShell and Azure CLI examples for configuring diagnostic settings, but omits explicit Linux shell (bash) or macOS terminal examples. PowerShell is a Windows-centric tool, and its inclusion without parity for Linux-native tools or examples creates friction for non-Windows users. The instructions for creating resources and configuring alerts rely on the Azure portal, which is cross-platform, but the scripting guidance is Windows-biased.
Recommendations
  • Add explicit bash shell examples for Linux/macOS users alongside PowerShell and CLI sections.
  • Clarify that Azure CLI commands work on Linux/macOS and provide installation/setup guidance for these platforms.
  • Include notes or links for Linux/macOS users on how to authenticate and run Azure CLI commands in their environment.
  • Avoid presenting PowerShell examples without Linux equivalents, or present CLI/bash examples first.
GitHub Create Pull Request
Virtual Machine Scale Sets Spot Placement Score ...les/virtual-machine-scale-sets/spot-placement-score.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 platform-specific instructions for accessing the Spot Placement Score via Azure CLI, REST API, and Azure PowerShell. The PowerShell example is given its own dedicated section and command, and the Azure CLI example is presented as a separate tab. However, there is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there examples for scripting with Bash or other common Linux tools. The PowerShell example is presented after the CLI example, but both are given equal prominence, and there is no explicit prioritization of Linux workflows. The documentation does not mention any Linux-specific considerations or tools, and the troubleshooting and examples sections are platform-neutral.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users, showing how to invoke the REST API using curl or similar tools.
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS, and provide example commands run in Bash.
  • Include notes or sections on Linux/macOS environment setup for Azure CLI and REST API usage.
  • Ensure parity by mentioning Linux/macOS usage wherever PowerShell is referenced, and avoid implying PowerShell is the default or only scripting option.
  • Consider listing CLI/Bash examples before PowerShell to signal Linux parity.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for creating a standby pool, but PowerShell is given equal prominence as CLI, and PowerShell-specific deployment commands are referenced in ARM and Bicep sections alongside CLI. There is a slight Windows bias due to the explicit inclusion of PowerShell examples and deployment instructions, while Linux/macOS alternatives (such as Bash scripting or shell-specific notes) are not mentioned. The CLI examples are cross-platform, but the repeated mention of PowerShell and its deployment commands may create friction for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI commands work on Linux/macOS and provide shell-specific notes if needed.
  • In ARM and Bicep sections, mention that 'az deployment group create' is cross-platform and provide examples for Bash or other shells.
  • Consider adding a note for Linux/macOS users that PowerShell is optional and CLI is fully supported.
  • If PowerShell is required for any functionality, explicitly state whether it is available on Linux/macOS via PowerShell Core.
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-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 provides both Linux and Windows guidance, but Windows/PowerShell examples and tooling are often presented first or in greater detail. Windows-specific tools (PowerShell DSC) receive a full code example, while the Linux equivalent (cloud-init) is described but lacks a direct example file. References to PowerShell management are prominent, and some links or sections prioritize Windows approaches before Linux ones.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail, ideally side-by-side.
  • Provide a direct cloud-init example file in the documentation, similar to the PowerShell DSC example.
  • Include links to Linux management guides (e.g., using Azure CLI or SSH) alongside PowerShell management references.
  • Avoid listing Windows/PowerShell tutorials before Linux/CLI ones unless contextually justified.
  • Clarify parity in features and workflows between Windows and Linux, especially for advanced scenarios.
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-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a moderate Windows bias. In multi-platform code tabs, Windows/PowerShell examples are consistently presented first, and REST API examples use Windows-based scale sets by default. PowerShell (a Windows-centric tool) is given prominent coverage, with Linux/CLI examples appearing later. REST and PowerShell examples default to 'ApplicationHealthWindows' and Windows resource names, while Linux examples are only provided under Azure CLI sections. Troubleshooting commands are PowerShell-focused, and Windows log file paths are listed before Linux equivalents.
Recommendations
  • Present Linux and Windows examples with equal prominence, alternating which appears first or grouping by OS rather than tool.
  • In REST API and JSON schema examples, provide both 'ApplicationHealthLinux' and 'ApplicationHealthWindows' variants, or use a neutral placeholder.
  • Include Azure CLI and PowerShell examples for both Linux and Windows scale sets in all relevant sections.
  • In troubleshooting, provide equivalent Linux commands (e.g., using Azure CLI or Bash) alongside PowerShell.
  • List Linux and Windows log file paths together or alternate their order.
  • Use neutral resource names (e.g., 'myVMScaleSet' instead of 'myVMScaleSet' for Windows and 'myLinuxVMScaleSet' for Linux) in examples.
GitHub Create Pull Request
← Previous Page 1 of 6 Next →