Scan Details - Linux-first Docs for Azure

Virtual Machines Enable Trusted launch on existing Gen2 VMs ...rticles/virtual-machines/trusted-launch-existing-vm.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides parity for both Linux and Windows VMs in terms of feature applicability and mentions both RDP (Windows) and SSH (Linux) for VM access. However, there is a notable bias in the scripting and automation sections: PowerShell is given a dedicated tab alongside Azure CLI, and ARM templates, and is used for both Windows and cross-platform scenarios. The PowerShell tab is presented with equal prominence as the CLI, but PowerShell is a Windows-native tool, and the template deployment steps also use PowerShell commands (e.g., New-AzResourceGroupDeployment, Stop-AzVM) rather than cross-platform CLI equivalents. Additionally, the PowerShell tab appears before the Template tab, and PowerShell is used for ARM template deployment, which could create friction for Linux/macOS users. There are no Linux shell (bash) or macOS-specific examples for template deployment, and the documentation assumes familiarity with PowerShell cmdlets for automation.

Recommendations

Add bash (Azure CLI) examples for ARM template deployment, showing how to deploy templates using az deployment group create.
Clarify that PowerShell is optional and provide equivalent CLI commands for all automation steps.
Where PowerShell is used for template deployment, provide a CLI alternative or explicitly note that PowerShell is not required.
Consider reordering tabs so that cross-platform tools (CLI, Template) appear before PowerShell.
In the prerequisites and best practices, briefly mention that all steps can be performed from Linux/macOS using Azure CLI or Cloud Shell.

Create Pull Request

Service Fabric Configure or modify a Service Fabric managed cluster node type ...vice-fabric/how-to-managed-cluster-modify-node-type.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides step-by-step instructions for configuring and modifying Service Fabric managed cluster node types using the Azure portal, ARM templates, and PowerShell. However, all command-line examples are exclusively in PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS shell equivalents. PowerShell is presented as the only scripting option for automation, which may create friction for Linux/macOS users who do not use PowerShell. The documentation does not clarify whether PowerShell Core (cross-platform) is supported, nor does it offer alternative command-line approaches.

Recommendations

Add Azure CLI examples for all operations currently shown only in PowerShell, such as adding, removing, scaling, and modifying node types.
Explicitly mention whether PowerShell Core (pwsh) is supported on Linux/macOS, or clarify if only Windows PowerShell is required.
Provide guidance or links for Linux/macOS users on how to perform these tasks using their preferred environments.
Consider listing Azure CLI or cross-platform options before or alongside PowerShell examples to avoid Windows-first bias.

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 →

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.

Create Pull Request

Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-specialized-image-version.md

Medium Priority View Details →

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 creating VMs from specialized images, but the PowerShell examples are significantly more detailed, including full network setup and VM configuration, while the CLI examples are minimal. PowerShell is a Windows-centric tool, and the lack of parity in example depth creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before CLI in some sections, and there are no Bash or Linux shell-specific examples for tasks like network setup, which could be performed using Azure CLI on Linux/macOS.

Recommendations

Expand Azure CLI examples to include full VM creation workflows, including network resources and configuration, matching the detail of PowerShell examples.
Add explicit Bash/Linux shell examples for Azure CLI commands, demonstrating usage on Linux/macOS platforms.
Ensure CLI examples are presented before or alongside PowerShell examples to avoid Windows-first perception.
Clarify that Azure CLI is cross-platform and recommend it for Linux/macOS users.

Create Pull Request

Virtual Machines Create a VM from a generalized image in a gallery ...icles/virtual-machines/vm-generalized-image-version.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides both Azure CLI (cross-platform) and PowerShell examples for creating VMs from generalized images in a gallery. However, the PowerShell examples are heavily Windows-centric, with parameters and configuration steps (e.g., Set-AzVMOperatingSystem -Windows) defaulting to Windows VM creation. There are no equivalent PowerShell examples for Linux VM creation, and the full parameter set for PowerShell only demonstrates Windows VM configuration. Additionally, in PowerShell examples, Windows VM creation is shown first and exclusively, while Linux VM creation is only covered in CLI and REST examples.

Recommendations

Add PowerShell examples for creating Linux VMs from generalized images, including the use of Set-AzVMOperatingSystem -Linux and SSH key configuration.
In PowerShell sections, clarify how to adapt the examples for Linux VMs, including differences in credential handling and network security rules (e.g., SSH port 22 instead of RDP port 3389).
Ensure that both Windows and Linux VM creation are equally represented in all code samples and explanations, especially in PowerShell sections.
Consider presenting Linux and Windows examples side-by-side or clearly labeling them to improve parity and reduce friction for Linux users.

Create Pull Request

Virtual Machine Scale Sets Spot Placement Score ...les/virtual-machine-scale-sets/spot-placement-score.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides usage instructions for Spot Placement Score via Azure Portal, REST API, Azure CLI, and Azure PowerShell. The PowerShell example is given its own section, and Windows/PowerShell is mentioned after CLI, but both are presented as equal options. No Linux-specific tools or shell examples are missing, as Azure CLI is cross-platform. However, PowerShell is highlighted, which may be less familiar to Linux/macOS users. The ordering of examples (CLI before PowerShell) is appropriate, but the PowerShell section may create minor friction for non-Windows users.

Recommendations

Clarify that Azure CLI is fully supported on Linux/macOS and provide explicit instructions for installing and using it on those platforms.
Note that PowerShell Core is available cross-platform, and provide a brief link or note for Linux/macOS users on how to install and use PowerShell if desired.
Consider including a Bash shell example for REST API calls using curl, which is common for Linux/macOS users.
Explicitly state that all features and APIs described are available regardless of OS, and that CLI and REST API are recommended for Linux/macOS users.

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 →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides a balanced overview of migrating to Virtual Machine Scale Sets in Flexible orchestration, but there is mild Windows bias in the 'Create scalable network connectivity' section, where Windows-specific scenarios (Windows VM activation, Windows updates) are mentioned before Linux equivalents (Linux package managers). There are no explicit Linux-focused examples or commands, and no PowerShell-specific instructions, but Windows use cases are listed first and in more detail.

Recommendations

Add explicit Linux migration scenarios, such as guidance for Linux VM activation or common Linux update/package manager connectivity requirements.
Ensure Linux-specific outbound connectivity needs (e.g., apt/yum repositories, SSH access) are mentioned alongside Windows scenarios.
Provide example commands for Linux environments where relevant (e.g., Azure CLI usage from Bash, Linux VM extension installation).
List Windows and Linux scenarios in parallel or alternate order to avoid Windows-first presentation.

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 →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and Azure PowerShell examples for all major operations (attach, detach, update VMSS membership), but consistently lists PowerShell examples after CLI and before any Linux-specific notes. The PowerShell examples use Windows-style syntax (backticks, parameter casing) and reference Windows-specific networking ports (e.g., 3389 for RDP). There are no explicit Linux shell examples (e.g., Bash), but the Azure CLI commands are cross-platform and use a Linux-friendly example image (Ubuntu2204). However, the PowerShell examples may create a perception of Windows bias, especially for users unfamiliar with PowerShell or working on Linux/macOS.

Recommendations

Clarify that Azure CLI commands work on Windows, Linux, and macOS, and are the recommended cross-platform approach.
Consider adding explicit Bash examples or notes for Linux/macOS users, especially for scripting or automation.
In PowerShell examples, avoid referencing Windows-specific ports (like 3389) unless relevant to the scenario.
Add a short note at the top of the page indicating that both CLI and PowerShell are supported on all platforms, but PowerShell syntax shown is for Windows.
If possible, alternate the order of CLI and PowerShell examples, or group them under a 'Cross-platform' heading.

Create Pull Request

Virtual Machine Scale Sets Rolling upgrades with MaxSurge for Virtual Machine Scale Sets ...hine-scale-sets/virtual-machine-scale-sets-maxsurge.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides configuration instructions for rolling upgrades with MaxSurge on Azure Virtual Machine Scale Sets. While the CLI example (az CLI) is cross-platform and shown before PowerShell, the PowerShell example is included and detailed, which may be seen as a mild Windows bias. However, there are no exclusive Windows tools or patterns, and Linux users can fully complete the task using the CLI or ARM template methods. The order of examples (CLI before PowerShell) and the inclusion of ARM templates help mitigate bias.

Recommendations

Explicitly mention that the Azure CLI commands work on Linux, macOS, and Windows.
Add a note clarifying that PowerShell examples are for Windows and PowerShell Core users, while CLI is recommended for Linux/macOS.
Consider including a Bash script example for Linux users, if relevant.
Ensure screenshots and UI references do not assume Windows-only environments.

Create Pull Request

Virtual Machine Scale Sets Configure rolling upgrades on Virtual Machine Scale Sets ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machine-scale-sets/virtual-machine-scale-sets-configure-rolling-upgrades.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides example commands for Azure CLI, PowerShell, Portal, and ARM templates. While the Azure CLI is cross-platform and suitable for Linux/macOS users, PowerShell examples are given equal prominence and detail, and in some sections, PowerShell appears before ARM templates. There is a slight 'windows_first' bias in the ordering and presentation of examples, with PowerShell (traditionally Windows-centric) featured alongside CLI, and no explicit mention of Bash or Linux-specific scripting. However, all critical tasks can be completed using the Azure CLI, which is fully supported on Linux/macOS.

Recommendations

Explicitly state that Azure CLI commands work on Linux/macOS and Windows.
Consider listing Azure CLI examples before PowerShell to reinforce cross-platform parity.
Add a brief note for Linux/macOS users clarifying that PowerShell Core is available cross-platform, but CLI is the native choice.
Where possible, include Bash script snippets or references for Linux users.
Avoid implying PowerShell is the default or preferred automation tool unless the task is Windows-specific.

Create Pull Request

Virtual Machine Scale Sets Custom metrics for rolling upgrades on Virtual Machine Scale Sets ...tual-machine-scale-sets-rolling-upgrade-custom-metrics.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation provides both Linux and Windows examples for configuring custom metrics and the application health extension on Azure Virtual Machine Scale Sets. However, there is a mild Windows bias: PowerShell examples are given equal prominence to Bash, and Windows-specific extension types (ApplicationHealthWindows) are shown first or exclusively in some code blocks. Additionally, PowerShell scripting is detailed alongside Bash, and Windows extension names/types are sometimes used as defaults in examples. REST API examples also use ApplicationHealthWindows as the type, even when ApplicationHealthLinux is equally valid.

Recommendations

Ensure that both ApplicationHealthLinux and ApplicationHealthWindows extension types are shown in REST and JSON examples, or clarify when to use each.
Alternate the order of Bash and PowerShell tabs so Linux is not always second.
Where possible, provide explicit Linux and Windows variants in code samples, especially for extension type and settings.
Clarify in text and tables that all functionality applies equally to Linux and Windows VMSS, and highlight any differences.
In REST/JSON examples, use ApplicationHealthLinux as the default type when the example is not Windows-specific.

Create Pull Request

Virtual Machines Time sync for Linux VMs in Azure ...blob/main/articles/virtual-machines/linux/time-sync.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation page is focused on time synchronization for Linux VMs in Azure and provides comprehensive Linux-specific guidance, examples, and tooling. However, the introductory section discusses Windows Server 2016 time sync improvements and links to Windows documentation before delving into Linux-specific content. No PowerShell or Windows-only tools are used in the main configuration or troubleshooting sections, except for a single PowerShell example for base64 encoding cloud-init (which is relevant for Azure ARM templates, but could be supplemented with Linux alternatives). All configuration and troubleshooting steps are Linux-centric.

Recommendations

Move or minimize the Windows Server 2016 time sync discussion in the introduction, or clarify its relevance to Linux VMs (e.g., as the underlying Azure host).
Provide a Linux shell alternative for the PowerShell base64 encoding example (e.g., `base64 ./cloud-config.txt`).
Ensure that Linux documentation links are presented before or alongside Windows links in the 'Next steps' section.
Add a brief note explaining why Windows time sync is mentioned (i.e., Azure hosts run Windows Server 2016, which impacts Linux VM time sync).

Create Pull Request

Virtual Machine Scale Sets Create an Azure scale set that uses Availability Zones ...s/virtual-machine-scale-sets-use-availability-zones.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and Azure PowerShell examples for creating and updating scale sets with Availability Zones. However, PowerShell examples are given equal prominence to CLI examples, and in some sections (such as updating scale sets), the PowerShell example is shown before the REST API example. There is a slight 'windows_first' bias in the ordering of example tabs and the inclusion of PowerShell, which is primarily a Windows tool, but Linux parity is generally maintained through CLI and ARM template instructions.

Recommendations

Ensure that Azure CLI examples are shown before PowerShell examples, as CLI is cross-platform and more commonly used on Linux/macOS.
Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, while PowerShell is primarily for Windows (with limited cross-platform support).
Consider adding bash shell script examples for common operations, or clarify that Azure CLI is the recommended approach for Linux/macOS users.
Where PowerShell is used, offer a note about Linux alternatives or cross-platform PowerShell Core usage.

Create Pull Request

Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell example is given equal prominence and detail as the CLI example. The CLI example is cross-platform (Linux, macOS, Windows), while PowerShell is primarily Windows-focused (though PowerShell Core is available on Linux/macOS, most Azure users associate it with Windows). The tabs present CLI first, but the PowerShell section is not clearly marked as Windows-specific, which may create confusion or friction for Linux/macOS users.

Recommendations

Explicitly note that PowerShell examples are primarily for Windows users, and clarify PowerShell Core compatibility for Linux/macOS.
Highlight Azure CLI as the recommended cross-platform method for quota checks.
Consider providing bash or shell script examples for Linux users, if relevant.
Add a note at the top of the examples section indicating which commands are cross-platform and which are Windows-specific.

Create Pull Request

Scan Information

Problematic Pages