Virtual Machines
1073
Total Pages
1027
Linux-Friendly Pages
46
Pages with Bias
4.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
284 issues found
Showing 101-125 of 284 flagged pages
Virtual Machines
Create a VM from a specialized image version
...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority
View Details →
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 and complex, including full network setup, while CLI examples are minimal. PowerShell is a Windows-centric tool, and there are no equivalent Linux shell (bash) or cross-platform scripting examples for the detailed VM/network configuration steps. In several sections, PowerShell examples are presented immediately after CLI, and the CLI examples are much shorter. There are no explicit Linux-specific command-line examples beyond Azure CLI, nor any mention of Linux-native tools or scripting patterns.
Recommendations
- Provide detailed bash (Linux shell) scripting examples for VM and network resource creation, matching the depth of the PowerShell examples.
- Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS, and offer sample scripts for those environments.
- Where PowerShell is used for complex resource setup, offer equivalent Azure CLI commands or bash scripts to ensure Linux users can follow along without needing PowerShell.
- Add notes or links to Linux/macOS-specific guidance for users who do not use PowerShell.
Create Pull Request
Virtual Machines
Create and upload a CentOS-based Linux VHD
...rticles/virtual-machines/linux/create-upload-centos.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation for creating and uploading a CentOS-based Linux VHD to Azure exhibits a moderate Windows bias. Hyper-V (a Windows-only virtualization tool) is mentioned first and most prominently as the example for creating VHDs, with detailed steps referencing Hyper-V Manager for VM operations (connect, shut down). There is minimal mention of Linux-native alternatives (e.g., KVM, VirtualBox, VMware), and no step-by-step instructions for those platforms. Conversion to VHD format is described using Hyper-V Manager or PowerShell's convert-vhd cmdlet, with only a brief note about VirtualBox. This may create friction for Linux/macOS users who do not have access to Hyper-V or Windows tools.
Recommendations
- Provide equivalent step-by-step instructions for creating and managing VHDs using Linux-native tools such as KVM, QEMU, or VirtualBox.
- Include commands for converting disk formats using Linux utilities (e.g., qemu-img) alongside or before Windows/Hyper-V examples.
- Add instructions for shutting down and managing VMs using Linux tools (e.g., virsh for KVM, VBoxManage for VirtualBox) instead of only referencing Hyper-V Manager.
- Reorder examples so that Linux-native tools are presented first or in parallel with Windows tools.
- Clarify that Hyper-V is only one option and not a requirement for Linux users.
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.
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 page exhibits moderate Windows bias. Windows-specific examples (PowerShell, CLI) are presented before Linux equivalents, and Windows tooling (PowerShell cmdlets, registry keys, WSUS) is referenced more frequently and in greater detail. Linux-specific examples are present but sometimes less detailed or appear after Windows instructions. Some sections (e.g., patch orchestration modes) provide more options and explanations for Windows than Linux. The 'Next steps' link is Windows-focused.
Recommendations
- Present Linux and Windows examples side-by-side or alternate their order to avoid Windows-first bias.
- Expand Linux-specific instructions and examples, especially for CLI and PowerShell usage.
- Add parity for Linux in sections where only Windows options are described (e.g., patch orchestration modes, disabling automatic updates).
- Include Linux-focused 'Next steps' links, such as guides for managing Linux VMs.
- Where Windows registry keys or services are mentioned, provide equivalent Linux configuration details (e.g., for disabling automatic updates).
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 omits explicit Linux/macOS shell examples and does not mention platform-specific nuances. PowerShell instructions are given equal prominence to CLI, and there are no bash-specific or Linux/macOS workflow notes. The order of examples sometimes places PowerShell before or alongside CLI, and there is no mention of Linux tools or troubleshooting. No Linux/macOS-specific issues or guidance are discussed.
Recommendations
- Add explicit bash/Linux/macOS shell examples, clarifying that Azure CLI commands work natively on these platforms.
- Include notes about installing and using Azure CLI on Linux/macOS, and clarify that PowerShell is Windows-centric (though cross-platform PowerShell exists).
- Highlight any platform-specific differences in disk attachment or hydration processes, if applicable.
- Provide troubleshooting tips for Linux/macOS users, e.g., permissions, environment variables, or shell compatibility.
- Consider listing Azure CLI (cross-platform) examples before PowerShell to reduce perceived Windows bias.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides extensive Linux-specific guidance, examples, and tooling. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details. There are no PowerShell or Windows-only tools used for Linux configuration, except for a single PowerShell command for base64 encoding cloud-init data, which is contextually appropriate for Azure ARM templates and not for VM time sync itself.
Recommendations
- Move the Windows Server 2016 discussion and links to a background or context section, making clear it is for Azure host infrastructure and not directly relevant to Linux VM configuration.
- Add a brief summary at the start clarifying that all configuration steps and examples are Linux-specific.
- If referencing Windows documentation, ensure Linux documentation is referenced with equal prominence and in the same section.
- For the PowerShell base64 example, consider providing a Linux equivalent (e.g., `base64 cloud-config.txt`) for users preparing ARM templates from Linux/macOS environments.
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
Summary
The documentation provides examples for Azure portal, Azure CLI, PowerShell, and REST API. PowerShell is presented as a distinct example, but it is not prioritized above CLI or REST. However, in the 'Create a private gallery' section, the PowerShell example is shown after the CLI example, and both are given equal prominence. The CLI examples use Bash syntax and variables, which are cross-platform and friendly for Linux/macOS users. There are no Windows-only tools or patterns, and no critical steps are Windows-exclusive. The only minor bias is the inclusion of PowerShell as a separate example, which could be interpreted as slightly favoring Windows users, but this is mitigated by the presence of CLI and REST examples. No Linux/macOS examples are missing, and the CLI is presented before PowerShell.
Recommendations
- Consider explicitly noting that Azure CLI commands work on Linux, macOS, and Windows.
- If possible, add a note clarifying that PowerShell examples are for Windows users, while CLI examples are cross-platform.
- Ensure screenshots and portal instructions do not reference Windows-specific UI elements.
- Maintain the current order (CLI before PowerShell) to minimize perceived Windows bias.
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.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 major tasks, but consistently presents PowerShell examples immediately after CLI, and sometimes with more detailed output formatting. There is minor bias in mentioning PowerShell as a primary tool alongside Azure CLI, despite the Linux focus. However, all examples and instructions are fully applicable to Linux users, and no Windows-specific tools or patterns are prioritized or required.
Recommendations
- Consider presenting Azure CLI examples first in all sections, as CLI is the native cross-platform tool and more relevant for Linux users.
- Where possible, clarify that PowerShell examples are optional for Linux users, and highlight that Azure CLI is the default for Linux environments.
- Ensure that output examples and troubleshooting steps are equally detailed for CLI and PowerShell.
- Add explicit notes that Azure PowerShell can be run on Linux, but Azure CLI is typically preferred for Linux workflows.
Virtual Machines
Qualys Cloud Agent Extension for Azure VMs
...ob/main/articles/virtual-machines/extensions/qualys.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation generally provides parity between Windows and Linux deployment methods, but there is a subtle bias in the prominence of PowerShell (a Windows-centric tool) as a primary automation method, and in some sections, Windows is mentioned before Linux. However, Linux-specific tools (like Ansible) are also referenced, and Linux deployment links are provided alongside Windows equivalents.
Recommendations
- When listing deployment methods or examples, alternate the order of Windows and Linux, or present them together to avoid 'Windows first' bias.
- Clarify that PowerShell Core is cross-platform if recommending it for Linux, or provide Bash/Azure CLI examples for Linux users.
- Expand on Linux-native automation tools (e.g., Bash scripts, Azure CLI, cloud-init) in addition to PowerShell, especially in sections focused on command-line deployment.
- Ensure that all external links for deployment steps are equally available and visible for both Windows and Linux.
- Explicitly mention when a method is equally applicable to both OSes, or provide OS-specific instructions where necessary.
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 and Azure PowerShell examples for creating instant access snapshots, but the PowerShell example is given equal prominence and appears before the portal example. There is no explicit Linux/macOS bias, but Windows tools (PowerShell) are featured alongside cross-platform CLI. No Linux-specific shell or tooling is referenced, and the CLI examples use Bash syntax, which is cross-platform but most common on Linux/macOS. The ordering of examples (CLI, PowerShell, Portal, ARM template) is neutral, but PowerShell is still a Windows-centric tool.
Recommendations
- Clearly indicate that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
- Consider providing example CLI commands using both Bash and PowerShell syntax, or clarify that Bash is the default for CLI.
- Add a note that Azure PowerShell is available on Linux/macOS, but CLI is recommended for cross-platform use.
- Ensure that CLI examples are shown first and are complete, which is already the case.
- Optionally, add a section for Linux/macOS users highlighting any OS-specific considerations (none appear necessary here).
Virtual Machines
What's new in Azure Disk Storage
...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is primarily a changelog and summary of new features for Azure Disk Storage, which is a cross-platform service. Most content is neutral, but there are minor instances of Windows bias: Windows documentation links are sometimes listed before Linux equivalents, and references to Azure PowerShell are made without equal mention of Linux tools. However, Linux links and parity are generally present, and no critical features are Windows-only.
Recommendations
- When linking to both Windows and Linux documentation, list Linux links first or side-by-side with Windows links to avoid subtle ordering bias.
- Where Azure PowerShell is mentioned, also reference Azure CLI (which is cross-platform) to ensure Linux/macOS users are equally supported.
- Review linked documentation to ensure Linux/macOS parity in examples and instructions.
- Explicitly state cross-platform support in feature descriptions where relevant.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is focused on Linux, but in several sections (e.g., upgrading, troubleshooting, deployment), Windows/PowerShell examples are presented before their Linux/Azure CLI equivalents. The PowerShell deployment section is more detailed and appears before the Azure CLI section, which may create friction for Linux users. Additionally, troubleshooting commands are shown with PowerShell first, even though Azure CLI is more common on Linux.
Recommendations
- Present Azure CLI examples before PowerShell examples in all sections, as CLI is the default for Linux users.
- Ensure troubleshooting commands are shown with Azure CLI first, or provide parity in detail between CLI and PowerShell.
- Clarify that PowerShell is optional and not required for Linux deployments.
- Add explicit notes or guidance for Linux users about which tools are recommended (e.g., Azure CLI).
Virtual Machines
NVIDIA GPU Driver Extension - Azure Linux VMs
...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is focused on Linux VM GPU driver installation, but includes PowerShell examples alongside Azure CLI and ARM templates. The PowerShell example is presented before the Azure CLI example, which is more relevant for Linux users. There is also mention of a Windows extension, but it is clearly separated and not the main focus. No Windows-specific tools or patterns are prioritized, and Linux-specific commands and troubleshooting are well covered.
Recommendations
- Move the Azure CLI example before the PowerShell example, as Azure CLI is more commonly used on Linux.
- Clarify that PowerShell is optional and primarily for users on Windows or those who prefer it.
- Consider adding Bash scripting examples for deployment, as Bash is native to Linux.
- Ensure all troubleshooting and operational examples use Linux-native tools and commands where possible.
Virtual Machines
HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs
...main/articles/virtual-machines/hbv3-series-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Recommended Windows
Minor Linux Example
Summary
The documentation covers both Linux and Windows, but there is a subtle bias towards Windows in the 'Recommended OS for Performance' row, which lists Windows Server 2019+ as recommended without mentioning a Linux equivalent. Additionally, the order of OS support in some tables lists Windows after Linux, but the explicit recommendation is Windows. Linux-specific tools (e.g., lstopo) are used for topology, but no Windows equivalents or guidance are provided. Overall, Linux is well-represented, but the performance recommendation and lack of Windows-specific examples/tools create minor friction.
Recommendations
- If Windows Server 2019+ is truly the only recommended OS for performance, clarify why and provide Linux performance guidance or caveats.
- If Linux is also recommended for performance, add the relevant Linux distributions (e.g., RHEL, Ubuntu, SLES) to the 'Recommended OS for Performance' row.
- Consider providing Windows equivalents for Linux-specific tools (like lstopo), or note if no equivalent exists.
- Ensure that both Linux and Windows users are equally guided for performance tuning and topology inspection.
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Windows and Linux examples and covers both OSes in detail. However, there is a noticeable Windows bias: PowerShell examples and references are often presented first, Windows-specific tools (e.g., Get-FileHash, PowerShell customizer, WindowsRestart, WindowsUpdate) are described in more detail, and Windows terminology and commands are frequently referenced before Linux equivalents. Some instructions for generating checksums and managing identities use Windows/PowerShell tools as the primary example, with Linux alternatives mentioned but less emphasized. There are also Windows-only customizers (WindowsRestart, WindowsUpdate) without Linux equivalents, but this is explicitly documented.
Recommendations
- Present Linux and Windows examples in parallel or alternate which is shown first.
- When referencing tools for tasks (e.g., generating SHA256 checksums), provide Linux/macOS commands (sha256sum) before or alongside Windows/PowerShell commands.
- Expand Linux-specific guidance (e.g., shell customizer, file paths, troubleshooting) to match the detail provided for Windows.
- Where Windows-only customizers exist, clearly state Linux alternatives or limitations.
- Ensure that validation and customization examples for Linux are as detailed as Windows examples.
- Add links to Linux/macOS documentation for relevant Azure CLI and scripting tasks.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, the PowerShell example is presented as a separate tab, and the CLI example (which is cross-platform) is shown first. There is minor bias in that PowerShell is included, but no Linux-specific shell examples (e.g., Bash scripting) are provided. The CLI example is sufficient for Linux/macOS users, and no Windows-only tools or patterns are prioritized.
Recommendations
- Consider clarifying that Azure CLI is fully cross-platform and works on Linux/macOS as well as Windows.
- Optionally, include a brief Bash shell scripting example for automating quota checks on Linux/macOS.
- Ensure that any references to PowerShell note that it is available cross-platform, not only on Windows.
Virtual Machines
Create and upload a Red Hat Enterprise Linux VHD for use in Azure
...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, in most sections, Windows/Hyper-V tools and workflows are presented first, and Windows-centric terminology (e.g., Hyper-V Manager, VHD format, PowerShell cmdlets) is referenced before Linux alternatives. Linux/KVM/VMware instructions are present and detailed, but the ordering and some tool mentions (e.g., 'convert-vhd' cmdlet, Hyper-V Manager) prioritize Windows approaches.
Recommendations
- Reorder sections so that Linux/KVM/VMware instructions are presented before or alongside Hyper-V/Windows instructions, especially in introductory or summary areas.
- When referencing disk conversion tools, mention Linux-native tools (e.g., qemu-img) before or alongside Windows tools (e.g., Hyper-V Manager, convert-vhd).
- Clarify that Hyper-V/Windows tools are optional and provide parity for Linux users by highlighting Linux-native workflows.
- Consider adding a summary table or navigation that allows users to quickly jump to their preferred hypervisor/platform.
- Where possible, avoid referencing Windows/PowerShell tools as the default unless the task is inherently Windows-specific.
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation covers both Windows and Linux VM images, but there are several signs of Windows bias. PowerShell examples are consistently provided alongside Azure CLI, sometimes referenced first. Windows-specific tools (Sysprep) are mentioned before Linux equivalents (waagent). Some links and examples reference Windows paths or documentation before Linux. However, Linux is explicitly supported and mentioned throughout, and most tasks can be completed by Linux users.
Recommendations
- Ensure CLI and PowerShell examples are presented in parallel, with equal prominence and ordering.
- When referencing tools for generalizing VMs, mention Linux (waagent) and Windows (Sysprep) in the same sentence or with equal visibility.
- Provide links to Linux documentation alongside Windows documentation, not after or as a secondary reference.
- Review FAQ and scenario sections to ensure Linux-specific workflows and links are equally represented.
- Where possible, add Bash or Linux shell examples in addition to PowerShell, especially for scripting tasks.