107
Pages Scanned
18
Pages Flagged
107
Changed Pages
16.8%
% Pages Flagged
Scan Information
Started At: 2026-01-14 00:00:33
Finished At: 2026-01-14 05:22:17
Status: completed
Target Repo: Azure Compute
Current Phase: discovery
Files Queued: 107
Files Completed: 107
Problematic Pages
18 issues found
Container Instances
Standby pools for Azure Container Instances
...instances/container-instances-standby-pool-overview.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation page for 'Standby pools for Azure Container Instances' shows a moderate Windows bias. The provider registration step exclusively uses Azure PowerShell, with no Azure CLI or REST example. In the 'Availability zones' section, PowerShell is presented before CLI and REST, and both CLI and PowerShell examples are given, but the initial registration step is PowerShell-only. There are no Linux-specific tools or patterns mentioned, but the ordering and example selection favor Windows/PowerShell users.
Recommendations
- Add Azure CLI and REST examples for provider registration, not just PowerShell.
- Ensure CLI examples are presented before or alongside PowerShell examples in all sections.
- Explicitly mention that all commands (PowerShell, CLI, REST) can be run from Linux/macOS environments, and provide guidance for non-Windows users where relevant.
- Consider including bash script snippets or notes for Linux users where appropriate.
Create Pull Request
Virtual Machines
Automatic Extension Upgrade for VMs and scale sets in Azure
...ticles/virtual-machines/automatic-extension-upgrade.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Windows and Linux extension support and mentions compatibility for both OS types. However, in critical example sections (REST API, PowerShell, ARM template), the extension type used is 'DependencyAgentWindows', and PowerShell examples are Windows-centric. Linux equivalents (e.g., 'DependencyAgentLinux') are only shown in CLI examples, and not in PowerShell or ARM template samples. The ordering of examples and extension types generally favors Windows first, which may create friction for Linux users seeking parity.
Recommendations
- For each example (REST API, PowerShell, ARM template), provide both Windows and Linux extension type samples side-by-side or clearly indicate how to adapt for Linux (e.g., use 'DependencyAgentLinux').
- In PowerShell sections, include Linux extension examples or clarify that PowerShell can be used for Linux VMs with the appropriate extension type.
- In ARM template samples, show both 'DependencyAgentWindows' and 'DependencyAgentLinux' or add a note on how to switch between them.
- Consider alternating the order of Windows and Linux examples, or grouping them together for clarity.
- Explicitly state that all shown operations are equally applicable to Linux VMs/VMSS when the extension type is changed.
Virtual Machines
Attach an existing OS disk to a VM
.../blob/main/articles/virtual-machines/attach-os-disk.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation page focuses exclusively on creating a new Windows VM by attaching an existing OS disk, with all command-line examples provided only in PowerShell. There are no Bash, Azure CLI, or Linux/macOS shell examples, nor is there any mention of Linux VM scenarios. The portal instructions are generic, but the command-line workflow is Windows-centric and omits Linux parity.
Recommendations
- Add equivalent Azure CLI or Bash examples for attaching an OS disk to a Linux VM.
- Clarify in the introduction whether the process is applicable to Linux VMs, or explicitly state if it is Windows-only.
- If the process is supported for Linux VMs, provide Linux-specific notes (e.g., SSH access, disk attachment flags, OS type selection).
- Ensure references to VM creation, disk attachment, and networking cover both Windows and Linux scenarios.
Virtual Machines
Automatic Guest Patching for Azure Virtual Machines and Scale Sets
...ticles/virtual-machines/automatic-vm-guest-patching.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation covers both Windows and Linux VMs for automatic guest patching, but there is a notable Windows bias in example ordering, tooling, and detail. PowerShell and Windows CLI examples are more detailed and appear first, while Linux-specific CLI and PowerShell examples are less prominent or missing. Windows tools and registry keys are discussed in detail, whereas Linux equivalents (such as disabling automatic updates) are mentioned briefly and without parity in example depth.
Recommendations
- Provide Linux-specific PowerShell and CLI examples with equal detail and visibility as Windows examples.
- Ensure that Linux examples (e.g., REST API, CLI, PowerShell) are presented alongside Windows examples, not after them.
- Expand Linux tooling documentation, such as showing how to verify patching status, disable automatic updates, and manage patch modes using Linux-native tools.
- Add parity in troubleshooting and operational guidance for Linux VMs, matching the depth given to Windows.
- Consider alternating example order or grouping by OS to avoid Windows-first presentation.
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority
View Details →
Detected Bias Types
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides parity for both Windows and Linux virtual machines in terms of supported features and CLI/API usage. However, there is a notable Windows bias in the ARM template section, which only demonstrates Windows VM image deployment and omits any Linux image example or parameter. Additionally, the PowerShell examples (a Windows-centric tool) are given equal prominence as CLI, but CLI examples do use Linux images. The order of examples sometimes places PowerShell before ARM template, and the ARM template itself is Windows-only, which may create friction for Linux users seeking infrastructure-as-code guidance.
Recommendations
- Add a Linux VM ARM template example or include parameters for both Windows and Linux images in the ARM template section.
- Clarify in the ARM template section that the example is for Windows and provide a link or guidance for Linux VM ARM template usage.
- Consider alternating the order of CLI and PowerShell examples, or explicitly state that both are supported on Windows, macOS, and Linux (where applicable).
- Ensure that infrastructure-as-code examples (ARM templates, Bicep, Terraform) demonstrate both Windows and Linux VM scenarios.
Virtual Machines
Associate a virtual machine scale set with Uniform Orchestration to a capacity reservation group.
...pacity-reservation-associate-virtual-machine-scale-set.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation provides cross-platform instructions for associating a VM scale set with a capacity reservation group, including API, CLI, PowerShell, ARM template, and Portal methods. However, several sections—especially the ARM template example—are strongly Windows-centric, with parameters and variables focused exclusively on Windows Server images and PowerShell DSC/IIS deployment. There is no equivalent Linux-focused ARM template example, and Windows-specific deployment artifacts (PowerShell DSC, IIS) are referenced. PowerShell is given equal prominence to CLI, but CLI examples do use Ubuntu images, showing some Linux consideration. The ARM template and supporting text, however, assume Windows workloads by default.
Recommendations
- Add a Linux-focused ARM template example, using a popular Linux image (e.g., Ubuntu) and removing Windows-specific parameters, variables, and deployment artifacts.
- Provide guidance or links for deploying Linux workloads (e.g., using cloud-init or custom script extensions) in ARM templates.
- Balance PowerShell and CLI coverage, ensuring CLI examples are not just present but also highlighted as the primary cross-platform method.
- Clarify in the ARM template section that the example is for Windows workloads and offer a parallel Linux example.
- Remove or generalize references to Windows-only deployment artifacts (PowerShell DSC, IIS, WebDeploy) in generic capacity reservation documentation.
Virtual Machines
Deploy a Premium SSD v2 managed disk
...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 managed disks, but all CLI and PowerShell code samples use Windows VM images (e.g., 'Win2016Datacenter') and Windows-centric authentication (username/password), with no Linux VM image or SSH authentication examples. This creates a subtle Windows bias, as Linux users must adapt the examples themselves. Additionally, the VM creation examples consistently use Windows images first, and do not mention Linux-specific considerations or provide parity for Linux VM deployment.
Recommendations
- Include Linux VM deployment examples alongside Windows examples in CLI and PowerShell sections (e.g., use 'UbuntuLTS' or other Linux images, and demonstrate SSH key authentication).
- Explicitly mention that the CLI and PowerShell commands work for both Windows and Linux VMs, and highlight any differences in disk attachment or sector size compatibility.
- Alternate or parallel example blocks for Windows and Linux VM creation, making it clear how to adapt for either OS.
- Add notes or links to Linux-specific documentation where relevant (e.g., disk formatting, mounting, sector size compatibility).
Virtual Machines
Deploy a ZRS managed disk
...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides parity between Azure CLI (Linux/macOS friendly) and Azure PowerShell (Windows-centric) examples for deploying ZRS managed disks. However, PowerShell examples are extensive and use Windows-specific VM images and patterns, while Linux examples (via Azure CLI) are present but less detailed. Resource Manager template instructions and next steps reference PowerShell and Windows images first, and registration commands are only shown in PowerShell. There is a subtle Windows-first bias in example ordering and depth, but Linux users can complete all tasks using the CLI examples provided.
Recommendations
- Add equivalent Bash or Azure CLI commands for feature registration (currently only PowerShell is shown).
- Ensure Resource Manager template deployment examples include CLI/Bash alternatives, not just PowerShell.
- Balance example depth and detail between CLI (Linux/macOS) and PowerShell (Windows) sections.
- When showing VM creation, alternate between Linux and Windows images, or provide both in each example.
- In 'Next steps', link to both PowerShell and CLI sample repositories if available.
Virtual Machines
Ultra disks for VMs - Azure managed disks
...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority
View Details →
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying and managing Ultra Disks, but all VM creation and disk attachment examples use Windows VM images (e.g., Win2016Datacenter) and do not show Linux VM image equivalents. The portal instructions link only to the Windows VM quickstart, and there are no explicit Linux VM creation or disk attachment examples, despite Ultra Disks supporting Linux VMs.
Recommendations
- Add Linux VM creation examples in Azure CLI and PowerShell sections (e.g., using Ubuntu or CentOS images).
- In portal instructions, link to both Windows and Linux VM quickstarts, or clarify that the process is identical for Linux VMs.
- Show example commands for attaching Ultra Disks to existing Linux VMs, including any OS-specific considerations (e.g., partitioning and formatting disks on Linux).
- Ensure that documentation language and examples are balanced between Windows and Linux, reflecting the stated support for both.
Container Instances
Quickstart - create a container instance - Bicep
...iner-instances/container-instances-quickstart-bicep.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment, management, and cleanup steps. However, PowerShell examples are given equal prominence and are presented immediately alongside CLI examples, which may create a slight Windows-first impression. There are no Linux/macOS-specific shell examples (e.g., Bash), but the use of Azure CLI is cross-platform and sufficient for non-Windows users. No Windows-only tools or patterns are mentioned, and the documentation does not omit Linux/macOS equivalents.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform usage.
- Consider listing Azure CLI examples first, as CLI is the default for cross-platform scenarios.
- Optionally, add a note that PowerShell examples are primarily for Windows users, while CLI is recommended for Linux/macOS.
- Ensure that screenshots or UI references (if any) do not assume Windows environments.
Container Instances
Get prediction results for standby pools for Azure Container Instances (Preview)
...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pool-prediction-results.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for retrieving prediction results, but PowerShell is given a dedicated tab and example, which is primarily a Windows tool. The PowerShell example appears before the REST API example, and there is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor any explicit Linux/macOS instructions. However, the Azure CLI example is cross-platform and shown first, mitigating the bias somewhat.
Recommendations
- Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
- Consider adding a Bash shell example or explicitly stating that the CLI commands work on Linux/macOS.
- If PowerShell is shown, note that PowerShell Core is available on Linux/macOS, or provide equivalent Bash examples.
- Ensure that examples and instructions do not imply PowerShell is required unless there is a Windows-only feature.
Container Instances
Understand the health state of your standby pool for Azure Container Instances
...ances/container-instances-standby-pool-health-state.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. PowerShell is given a dedicated example tab, and is listed before REST API. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, and no Linux/macOS-specific shell examples (such as Bash/cURL for REST) are provided. The ordering of examples (CLI, then PowerShell, then REST) may subtly prioritize Windows users, and the lack of explicit Linux/macOS shell examples creates minor friction for non-Windows users.
Recommendations
- Add a Bash/cURL example for querying the REST API, demonstrating how Linux/macOS users can retrieve the health state.
- Clarify that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
- Consider listing REST API and CLI examples before PowerShell, or grouping all examples equally to avoid implicit prioritization.
- Explicitly mention that PowerShell Core is available on Linux/macOS if relevant.
Virtual Machines
Boot integrity monitoring overview
...virtual-machines/boot-integrity-monitoring-overview.md
Low Priority
View Details →
Detected Bias Types
windows_first
Summary
The documentation provides both Windows and Linux examples for deploying the Guest Attestation extension via ARM templates, and references both Windows and Linux publishers. However, in the template section, Windows is presented before Linux, and the troubleshooting example error references the Windows extension specifically. The CLI and PowerShell sections do not show OS-specific commands, but the PowerShell tab is present, which may be more familiar to Windows users. Overall, Linux parity is maintained, but minor ordering and example choices show a slight Windows-first bias.
Recommendations
- Present Linux and Windows examples in parallel or alternate their order to avoid implicit prioritization.
- In troubleshooting, mention that similar errors may occur for Linux VMs and reference the Linux extension explicitly.
- Where possible, clarify that CLI and template instructions apply equally to both OS types.
- Add Bash or Linux shell examples if relevant, especially in sections where PowerShell is highlighted.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides examples for configuring VM watch using ARM templates, Azure CLI, and PowerShell. While the introductory section notes that the code segment is identical for both Windows and Linux except for the extension type, the PowerShell example is included as a primary method alongside CLI and ARM template. There is a slight Windows-first bias in listing PowerShell as a top-level method, and the documentation does not provide explicit Linux shell (bash) examples or guidance for Linux users beyond the CLI. The use of Visual Studio Code as the recommended IDE is platform-neutral, but may be perceived as Windows-centric by some users.
Recommendations
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide explicit bash shell examples where relevant.
- Consider adding a note or example for Linux users showing how to use the CLI in a Linux shell environment.
- If PowerShell is mentioned, clarify that PowerShell Core is cross-platform, or provide alternative bash examples for Linux/macOS users.
- Explicitly state that all configuration methods (ARM template, CLI, PowerShell) are supported on both Windows and Linux, and highlight any platform-specific considerations.
Virtual Machines
Delete a VM and attached resources
...ute-docs/blob/main/articles/virtual-machines/delete.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides examples for Azure Portal, CLI, PowerShell, and REST API. However, PowerShell is given equal prominence to CLI, despite being Windows-centric. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell examples may not be directly usable on non-Windows platforms. The CLI examples are cross-platform, but the absence of Linux/macOS-specific shell scripting or explicit mention of Linux usage creates mild friction for non-Windows users.
Recommendations
- Clarify that PowerShell examples are primarily for Windows users and recommend CLI for Linux/macOS users.
- Add explicit Bash shell examples for common tasks, especially in sections where PowerShell is shown.
- Where possible, note platform compatibility for each example (e.g., 'CLI: works on Windows, Linux, macOS; PowerShell: Windows only').
- Consider reordering examples to show CLI before PowerShell, emphasizing cross-platform tools.
- Add links or references to Linux/macOS-specific documentation where relevant.
Virtual Machines
Copy a snapshot to a new region
...ines/disks-copy-incremental-snapshot-across-regions.md
Low Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for copying incremental snapshots, but the PowerShell section is more detailed and assumes use of Windows/PowerShell. The CLI examples use Bash syntax, but there is no explicit mention of Linux/macOS environments or shell differences. The PowerShell example is given equal prominence to CLI, and the CLI example uses Bash variables, which may not be familiar to Windows users. There are no Linux-specific troubleshooting tips, nor is there mention of Linux-native tools or considerations. The portal and ARM template instructions are platform-neutral.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and clarify shell differences if needed.
- Add a note or section for Linux/macOS users, confirming that Bash syntax is for Unix-like shells and provide equivalent Windows CMD syntax if desired.
- Provide troubleshooting tips for Linux/macOS environments (e.g., permissions, environment variables).
- Ensure parity in detail between CLI and PowerShell sections, and avoid assuming PowerShell is the default for scripting unless the audience is Windows-specific.
Virtual Machines
Enable end-to-end encryption using encryption at host - Azure portal - managed disks
...-machines/disks-enable-host-based-encryption-portal.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
minor_windows_tools
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for enabling encryption at host, but PowerShell examples are consistently listed first. The 'Next steps' section links only to PowerShell-based template samples, which may favor Windows users. However, the main instructions are Azure portal-based and explicitly state applicability to both Linux and Windows VMs. There are no critical omissions of Linux-specific instructions or tools.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to balance visibility for Linux/macOS users.
- Include links to Azure CLI-based Resource Manager template samples in the 'Next steps' section.
- Explicitly mention that all CLI commands work on Linux/macOS and Windows, and clarify any platform-specific nuances if present.
- Ensure screenshots and UI instructions are platform-neutral, as the Azure portal is web-based.
Virtual Machines
Instantly access managed disk snapshots
...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for creating instant access snapshots, but lists PowerShell examples immediately after CLI and before Resource Manager templates. No Linux/macOS-specific tools or shell patterns are mentioned, but the CLI examples use Bash syntax, which is suitable for Linux/macOS. There is a slight ordering bias toward Windows/PowerShell, but all critical operations are covered with CLI examples, so Linux/macOS users are not blocked.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and show Bash and PowerShell syntax side-by-side for variable declarations if relevant.
- Consider listing CLI examples before PowerShell and clarify platform compatibility for each example.
- Add a note that Azure PowerShell is primarily for Windows, while Azure CLI is cross-platform.
- If possible, provide example commands using native Linux tools (e.g., curl for SAS URI download) where relevant.