35
Pages Scanned
18
Pages Flagged
35
Changed Pages
51.4%
% Pages Flagged
Scan Information
Started At: 2026-01-14 00:01:08
Finished At: 2026-01-14 00:02:10
Status: completed
Target Repo: Azure Compute
Current Phase: discovery
Files Queued: 35
Files Completed: 35
Problematic Pages
18 issues found
Virtual Machines
Attach an existing OS disk to a VM
.../blob/main/articles/virtual-machines/attach-os-disk.md
High Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
windows_tools
Summary
The documentation is heavily biased towards Windows, with all command-line examples using PowerShell and Windows-specific parameters. There are no CLI or Linux/macOS shell examples, and the workflow is described for Windows VMs only. Windows tools and patterns (e.g., RDP, PowerShell modules) are mentioned exclusively, with no parity for Linux users.
Recommendations
- Add Azure CLI and/or Bash examples for attaching an OS disk to a VM, covering Linux VM scenarios.
- Include instructions for creating and attaching disks to Linux VMs, including SSH access setup instead of RDP.
- Clearly indicate which steps apply to Windows, Linux, or both, and provide equivalent Linux-focused guidance.
- Mention Linux-specific considerations (e.g., cloud-init, hostname changes, SSH keys) when reusing disks.
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
windows_tools
Summary
The documentation exhibits a Windows bias in several ways: Windows extension types are consistently used in code examples (REST, PowerShell, ARM templates), with 'DependencyAgentWindows' shown as the default even when Linux equivalents exist. PowerShell examples are prominent and use Windows-centric extension types. Linux examples are present only in CLI tabs, and Linux extension types are not shown in REST, PowerShell, or ARM template samples. Windows extension types are listed first in supported extensions and examples, and Windows tools (PowerShell) are emphasized over Linux-native alternatives.
Recommendations
- Provide parallel examples for both Windows and Linux extension types in all code samples (REST, PowerShell, ARM template), not just CLI.
- Alternate the order of Windows and Linux extension types in tables and examples, or group them together to avoid Windows-first presentation.
- Include Bash or shell scripting examples for Linux users where PowerShell is used.
- Explicitly mention Linux support and provide guidance for Linux-specific scenarios in enabling automatic extension upgrades.
- Clarify that CLI commands work cross-platform and highlight Linux usage where relevant.
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides examples for ARM templates, Azure CLI, and PowerShell, with PowerShell (a Windows-centric tool) given its own section and example. The CLI example is generic, but PowerShell is highlighted as a distinct method, which may suggest a Windows-first approach. There is no explicit Linux shell example (e.g., Bash), nor is there parity for Linux-specific command-line tools. The documentation mentions Visual Studio Code as an IDE, which is cross-platform, but does not suggest Linux-native editors. The only Linux-specific guidance is in a note about the extension type parameter, not in the main workflow or examples.
Recommendations
- Add explicit Bash or Linux shell command examples alongside PowerShell, especially for tasks like viewing or configuring extensions.
- Clarify that Azure CLI commands work identically on Linux/macOS and Windows, and provide platform-specific notes if there are differences.
- Include Linux-native editor suggestions (e.g., Vim, Nano) when recommending IDEs for editing JSON.
- Ensure that Linux-specific extension types and configuration steps are shown in examples, not just mentioned in notes.
- Consider reordering examples so that cross-platform tools (ARM template, CLI) appear before Windows-specific tools (PowerShell).
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
Summary
The documentation displays a moderate Windows bias, particularly in the ARM template section, which is heavily oriented toward Windows VM deployment and configuration. Windows-specific parameters, images, and PowerShell DSC are emphasized, while Linux equivalents are not mentioned. PowerShell examples are provided alongside CLI, but Windows tooling and terminology (e.g., DSC, WebDeploy) are referenced without Linux alternatives. However, Azure CLI examples do use Ubuntu images, and the overall workflow is cross-platform, so Linux users can complete the tasks but may need to adapt Windows-centric instructions.
Recommendations
- Add ARM template parameters and examples for Linux VM images (e.g., Ubuntu, CentOS) alongside Windows options.
- Include Linux configuration options (e.g., cloud-init, shell scripts) in the ARM template instead of only PowerShell DSC.
- Provide explicit Linux/macOS command-line examples where PowerShell is referenced, or clarify cross-platform compatibility.
- Balance references to Windows-specific tooling (DSC, WebDeploy) with Linux equivalents (cloud-init, custom script extension).
- Ensure documentation language and examples do not assume a Windows-first environment.
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
powershell_heavy
missing_linux_example
Summary
The documentation, while claiming applicability to both Windows and Linux VMs, demonstrates a moderate Windows bias. Windows tools (PowerShell) are given equal or greater prominence than Linux-native approaches, and ARM template examples are exclusively for Windows images. Password requirements and example parameters are tailored for Windows VMs, with no Linux-specific ARM template or parameterization. CLI examples use Ubuntu images but do not provide parity in ARM template or configuration details for Linux VMs.
Recommendations
- Add ARM template examples for Linux VMs, including Linux image references and SSH key authentication.
- Include Linux-specific configuration parameters and guidance (e.g., SSH, cloud-init) in ARM templates.
- Ensure password/account requirements are described for both Windows and Linux, or clarify differences.
- Balance PowerShell and CLI coverage, and consider Bash or other Linux-native scripting examples where appropriate.
- Present examples for both Windows and Linux side-by-side, especially in critical sections like VM creation and configuration.
Virtual Machines
Deploy a ZRS managed disk
...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are provided for all advanced scenarios, with Windows-centric tools and patterns (e.g., ConvertTo-SecureString, PSCredential, Windows images) used throughout. Resource Manager Template instructions and examples are exclusively shown using PowerShell, with no Linux shell or cross-platform alternatives. In PowerShell sections, only Windows VM images are used, while Azure CLI examples use Ubuntu images. The feature registration step for ARM templates is only shown in PowerShell, with no az CLI equivalent. The 'Next steps' section links only to PowerShell-based samples.
Recommendations
- Add bash/az CLI equivalents for all PowerShell-only steps, especially for ARM template feature registration and deployments.
- Show Linux VM image examples in PowerShell sections, or clarify how to deploy Linux VMs with ZRS disks using PowerShell.
- Include links to cross-platform or bash-based ARM template samples in the 'Next steps' section.
- Where possible, use generic terminology and avoid Windows-specific constructs (e.g., ConvertTo-SecureString) in examples, or provide Linux/macOS alternatives.
- Ensure that both Windows and Linux workflows are covered equally in all tabs and examples.
Virtual Machines
Delete a VM and attached resources
...ute-docs/blob/main/articles/virtual-machines/delete.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
missing_linux_example
Summary
The documentation provides parity between Azure Portal, CLI, PowerShell, and REST API for VM deletion options. However, there is a notable Windows bias: PowerShell examples are given equal prominence to CLI, and REST examples use Windows-centric values (e.g., Windows images, osType: Windows). There are no explicit Linux-specific examples (e.g., using a Linux image, osType: Linux, or Linux-specific adminUsername patterns). The FAQ and walkthroughs do not mention Linux-specific considerations, and PowerShell (a Windows-first tool) is featured as a primary automation method, which may not be available or preferred on Linux/macOS. The only Linux reference is in the 'Next steps' link, which is not integrated into the main content.
Recommendations
- Add explicit Linux examples in CLI and REST sections, such as using a Linux image (e.g., Ubuntu) and osType: Linux.
- In REST examples, alternate between Windows and Linux VM configurations to show parity.
- Clarify that PowerShell is cross-platform, but recommend CLI for Linux/macOS users and provide Bash shell examples where appropriate.
- In the FAQ, add notes about Linux VM deletion behaviors, if any differences exist.
- Ensure that Linux and Windows examples are presented with equal prominence, alternating or grouping by OS where possible.
Virtual Machines
Copy a snapshot to a new region
...ines/disks-copy-incremental-snapshot-across-regions.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides step-by-step instructions for copying incremental snapshots using Azure CLI, Azure PowerShell, Azure Portal, and ARM templates. While Azure CLI is cross-platform, the PowerShell example is Windows-centric and given equal prominence. There are no explicit Linux/macOS shell examples (e.g., Bash), nor are there notes about platform-specific differences. The CLI example uses Bash syntax, but this is not clarified, and no Linux-specific considerations (such as authentication, environment setup, or troubleshooting) are mentioned. The manual copy section references .NET sample code, which is more common on Windows, and does not mention Linux alternatives.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and provide Bash and PowerShell variants where syntax differs.
- Add Linux/macOS-specific notes for authentication, environment setup, and troubleshooting.
- Include sample scripts or references for manual copy using Linux tools (e.g., curl, azcopy, Bash).
- Offer parity in programming language samples (e.g., Python or Bash for manual copy, not just .NET).
- Clarify when examples are Windows-specific and provide Linux/macOS equivalents where relevant.
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
windows_tools
powershell_heavy
missing_linux_example
Summary
The documentation exhibits several signs of Windows bias. VM creation examples consistently use Windows images (e.g., 'Win2016Datacenter') in both Azure CLI and PowerShell scripts, with no Linux equivalents shown. The variable names and authentication methods (password-based, not SSH keys) are tailored to Windows scenarios. PowerShell is given equal prominence to Azure CLI, despite being Windows-centric. There are no explicit Linux VM creation examples, nor are there instructions or code samples for Linux-specific deployment patterns (e.g., using SSH keys, specifying a Linux image, or Linux admin username conventions).
Recommendations
- Add Linux VM creation examples alongside Windows ones in all CLI and PowerShell sections (e.g., use Ubuntu or CentOS images, SSH authentication).
- Show how to specify SSH keys for Linux VMs in CLI and PowerShell scripts.
- Include Linux-specific variable naming and admin username conventions.
- Explicitly mention that Azure CLI works cross-platform and provide Linux/macOS installation guidance.
- Where PowerShell is referenced, clarify its availability on Linux/macOS, or suggest Bash alternatives.
- In portal instructions, show screenshots or steps for Linux VM creation and disk attachment.
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
windows_tools
powershell_heavy
Summary
The documentation exhibits a notable Windows bias. Windows-specific examples (e.g., Win2016Datacenter image) are given exclusively in CLI and PowerShell sections, with no Linux VM deployment examples. References and links to Windows VM quickstarts are present, while Linux equivalents are omitted. All scripting examples use Windows-centric tools (PowerShell), and the CLI examples also default to Windows images. There is no guidance for Linux disk partitioning/formatting, nor any mention of Linux-specific considerations.
Recommendations
- Add Linux VM deployment examples alongside Windows (e.g., use Ubuntu or CentOS images in CLI/PowerShell snippets).
- Provide links to both Windows and Linux VM quickstart guides.
- Include Linux-specific instructions for partitioning and formatting Ultra Disks after attachment.
- Ensure CLI and PowerShell examples alternate or show both Windows and Linux usage.
- Mention any Linux-specific limitations, requirements, or troubleshooting steps for Ultra Disks.
Virtual Machines
Instantly access managed disk snapshots
...les/virtual-machines/disks-instant-access-snapshots.md
Medium Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
missing_linux_example
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for creating instant access snapshots, but does not offer explicit Linux shell (bash) or macOS-specific guidance. PowerShell examples are given equal prominence to CLI, and no Linux/macOS-specific nuances or troubleshooting are mentioned. There is a slight Windows-first bias in the ordering and tool selection, and Linux users may need to infer usage from CLI examples without tailored advice.
Recommendations
- Add explicit bash examples for Linux/macOS users, including variable declaration and command usage.
- Clarify that Azure CLI commands work on Linux/macOS and provide troubleshooting tips for common platform-specific issues (e.g., authentication, environment variables).
- Mention installation steps for Azure CLI on Linux/macOS, or link to relevant documentation.
- If PowerShell is mentioned, note that PowerShell Core is available cross-platform, but provide bash alternatives for Linux/macOS.
- Ensure that any screenshots or portal instructions are not Windows-centric (e.g., avoid showing Windows-only UI elements).
Virtual Machines
Enable double encryption at rest for managed disks
...hines/disks-enable-double-encryption-at-rest-portal.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation provides parity between Azure CLI and Azure PowerShell, but PowerShell examples and references are consistently presented after CLI, and there is a notable emphasis on PowerShell in the 'Next steps' section. The 'Next steps' links prioritize PowerShell/Windows content, with Linux/CLI content listed last. There are no Linux-specific shell examples (e.g., bash), but the CLI examples are cross-platform. No critical steps are Windows-only, but the documentation leans toward Windows/PowerShell tools and patterns.
Recommendations
- Ensure that Linux/CLI examples are given equal prominence in 'Next steps' and cross-links, not just at the end.
- Add explicit bash/zsh shell examples where relevant, especially for Linux users, to demonstrate parity.
- Consider alternating the order of CLI and PowerShell sections or providing a clear statement that CLI commands are cross-platform.
- Add a note clarifying that Azure CLI is fully supported on Linux/macOS and is recommended for cross-platform automation.
- Include more Linux/macOS-specific troubleshooting tips or environment notes if applicable.
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
windows_tools
Summary
The documentation page demonstrates mild Windows bias. In sections describing how to find supported VM sizes, the Windows/PowerShell method is listed before the Linux/Azure CLI method. Throughout the prerequisites, PowerShell examples are presented before Azure CLI, and the 'Next steps' link points to a PowerShell-focused sample repository. While Azure CLI examples are provided for Linux users, the ordering and emphasis favor Windows/PowerShell tools and patterns.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI first in Linux-focused documentation.
- Provide direct links to both PowerShell and CLI sample repositories in the 'Next steps' section.
- Explicitly state parity between Windows and Linux throughout, and ensure screenshots and instructions are not Windows-centric.
- Consider adding a note that all steps are equally applicable to Linux/macOS users when using Azure CLI.
- Where possible, include Linux/macOS-specific tips or troubleshooting notes.
Virtual Machines
Boot integrity monitoring overview
...virtual-machines/boot-integrity-monitoring-overview.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation displays mild Windows bias. Windows examples and terminology (such as PowerShell and Windows-specific extension publishers) are presented before Linux equivalents in the template section. The PowerShell tab is included, but there is no Bash or Linux shell scripting equivalent. Troubleshooting and configuration steps use generic Azure portal and CLI instructions, but screenshots and error messages reference Windows extension names. Linux parity is present in the template section, but less emphasized elsewhere.
Recommendations
- Add a Bash or Linux shell scripting tab alongside PowerShell for command-line examples.
- Ensure Linux extension error messages and troubleshooting steps are equally represented, including screenshots and sample error outputs for Linux.
- Present Windows and Linux examples side-by-side or alternate their order to avoid Windows-first bias.
- Clarify when instructions or extension names differ between Windows and Linux, especially in troubleshooting sections.
Virtual Machines
Configure Event Hubs for VM watch
...ticles/virtual-machines/configure-eventhub-vm-watch.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation page demonstrates mild Windows bias. References to PowerShell and Windows tools are present before Linux equivalents, and instructions for accessing vmWatchSettings mention PowerShell before CLI or ARM templates. Examples for viewing logs are provided for both Linux and Windows, but guidance for examining events in Event Hubs focuses on the Azure portal, which is platform-agnostic but often more familiar to Windows users. No explicit Linux command-line examples (e.g., az CLI, bash) are provided for key tasks such as configuring or troubleshooting Event Hubs output.
Recommendations
- Provide Linux/macOS-specific command-line examples using Azure CLI and bash for configuring Event Hubs output.
- Ensure that instructions for accessing vmWatchSettings mention CLI and ARM templates before PowerShell, or present all options equally.
- Include troubleshooting steps using Linux-native tools (e.g., tail, grep) for log analysis.
- Add explicit guidance for Linux users on viewing Event Hubs data using CLI or SDKs, not just the Azure portal.
- Review screenshots and examples to ensure they are not Windows-centric.
Virtual Machines
Create a Gallery for Sharing Resources
.../blob/main/articles/virtual-machines/create-gallery.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. However, PowerShell examples are given equal prominence as CLI, despite PowerShell being primarily a Windows technology. There is no explicit mention of Linux/macOS-specific tools or shell environments (e.g., Bash), and PowerShell is presented as a main option rather than as a Windows-specific alternative. The ordering of examples sometimes places PowerShell before REST, and the CLI examples use generic variable syntax that is compatible with Bash, but this is not clarified. No Linux/macOS-specific guidance or troubleshooting is provided.
Recommendations
- Clearly label PowerShell examples as Windows-specific and recommend CLI for cross-platform use.
- Add explicit Bash shell examples where variable syntax or command differences exist.
- Provide notes or troubleshooting tips for Linux/macOS users, especially regarding environment setup.
- Consider reordering examples to present CLI (cross-platform) before PowerShell.
- Mention that Azure CLI is the recommended tool for Linux/macOS users.
Virtual Machines
Remove a virtual machine scale set association from a capacity reservation group
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/capacity-reservation-remove-virtual-machine-scale-set.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides examples for API, Azure CLI, PowerShell, and Portal. PowerShell is featured as a first-class method alongside CLI, and PowerShell-specific commands are referenced and linked. While Azure CLI is cross-platform and examples are present, PowerShell is a Windows-centric tool and is given equal prominence. In some sections, PowerShell examples and links are provided before CLI equivalents. No Linux/macOS-specific shell examples (e.g., Bash scripts) are included, and there is no mention of Linux-specific considerations.
Recommendations
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Add Bash script examples for common Linux workflows, especially for automation.
- Reorder CLI examples before PowerShell to emphasize cross-platform support.
- Explicitly state PowerShell Core compatibility for non-Windows platforms if relevant.
- Add a note or section addressing Linux/macOS users and their preferred tools.
Virtual Machines
Convert a disk from LRS to ZRS
...ain/articles/virtual-machines/disks-migrate-lrs-zrs.md
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
windows_tools
Summary
The documentation consistently presents Azure Portal and Azure PowerShell instructions before Azure CLI examples. PowerShell, a Windows-centric tool, is given equal prominence to Azure CLI, and all examples use Azure Portal (a graphical tool familiar to Windows users) first. There is no explicit mention of Linux/macOS-specific considerations, and no Bash or shell script examples are provided. However, Azure CLI is cross-platform and shown for all tasks, so Linux users are not blocked from completing any steps.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
- Add explicit notes or examples for Linux/macOS users, such as using Bash variables and shell scripting patterns.
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide links to installation instructions for non-Windows platforms.
- Consider including a section or tab for Bash scripting for advanced automation scenarios.
- Avoid referring to Windows-specific tools (such as PowerShell) as the default or primary method.