Virtual Machines
1080
Total Pages
1005
Linux-Friendly Pages
75
Pages with Bias
6.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
815 issues found
Showing 726-750 of 815 flagged pages
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 extension management tasks, but consistently lists PowerShell examples immediately after CLI, and sometimes with more detailed output. There is a slight 'Windows-first' ordering in some sections, and PowerShell is given parity with CLI despite Linux users overwhelmingly preferring CLI. No Linux-specific tools (e.g., Bash scripts, cloud-init) are referenced for extension management, and troubleshooting/log paths are Linux-appropriate. No critical Windows-only tools or patterns are present, and all examples are valid for Linux VMs.
Recommendations
- Consider listing Azure CLI examples before PowerShell in all sections, as CLI is the primary cross-platform tool for Linux users.
- Explicitly state that Azure PowerShell is available on Linux, but CLI is recommended for Linux VM management.
- Add a short Bash script example for extension management using the Azure CLI to reinforce Linux-native workflows.
- Where possible, reference Linux-native automation tools (e.g., cloud-init, Bash scripting) in the context of VM extension management.
Create Pull Request
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows guidance, but there is a subtle Windows bias in some areas. PowerShell examples are shown with Windows as the default OS type, and Windows terminology (Sysprep) is mentioned before Linux equivalents. In the PowerShell section, Windows is the primary example, while Linux is only referenced as an alternative. However, CLI and REST examples default to Linux, and Linux-specific guidance is linked early in the 'Before you begin' section. Overall, Linux users can complete all tasks, but Windows is sometimes prioritized in examples and terminology.
Recommendations
- In PowerShell examples, show Linux as the default OS type or provide parallel Linux and Windows examples.
- When referencing OS-specific steps, mention Linux and Windows equally, rather than defaulting to Windows terminology.
- Ensure that CLI and PowerShell sections consistently show both Linux and Windows examples, or alternate which OS is shown first.
- Add explicit notes clarifying parity between Linux and Windows where relevant.
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 Tools
Windows First
Summary
The documentation provides both Windows and Linux examples and covers both OSes in detail. However, there are several areas where Windows tools and PowerShell are mentioned first or exclusively, such as using PowerShell for checksum generation, validator examples, and generalization commands. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents are less prominent. Some sections use Windows tools or patterns before Linux equivalents, and PowerShell is often referenced for tasks that could be done with cross-platform tools.
Recommendations
- When describing tasks like generating SHA256 checksums, mention Linux/macOS commands (e.g., 'sha256sum') alongside or before PowerShell equivalents.
- Ensure Linux validator examples are as prominent and detailed as Windows examples, including shell script usage and inline commands.
- Where possible, use cross-platform tools (e.g., Azure CLI) in examples before platform-specific tools (e.g., PowerShell).
- For sections like generalization, provide Linux command examples with equal detail and visibility as Windows Sysprep examples.
- Consider alternating the order of Windows and Linux examples to avoid always presenting Windows first.
- Clarify when a feature is Windows-only (e.g., WindowsRestart customizer), and provide Linux alternatives or explicitly state the lack thereof.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, the PowerShell example is given equal prominence, despite PowerShell being primarily a Windows tool. The CLI example is shown first, which is positive, but the presence of a PowerShell section may create friction for Linux/macOS users, as PowerShell is not natively installed on those platforms. No Linux-specific tools or commands (such as Bash scripting or references to native Linux utilities) are mentioned, but the Azure CLI is cross-platform and sufficient for Linux users.
Recommendations
- Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
- Optionally, add a note that PowerShell is available on Linux/macOS, but Azure CLI is more commonly used.
- Ensure that CLI examples are always shown first and are comprehensive.
- Consider adding Bash script examples for automation, if relevant.
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 page is focused on Linux VM time synchronization in Azure and provides comprehensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before fully explaining Linux-specific mechanisms. No Windows/PowerShell examples are given except for a single PowerShell command for base64 encoding cloud-init, which is contextually relevant for Azure users but lacks a Linux equivalent. All technical guidance, tools, and examples are Linux-centric.
Recommendations
- Move Windows Server 2016 discussion to a background or context section, or clarify its relevance to Linux VM time sync.
- Provide a Linux shell equivalent for the PowerShell base64 encoding example (e.g., 'base64 cloud-config.txt') for parity.
- Ensure that Linux-specific guidance is presented before or independently of Windows references.
- Consider minimizing Windows documentation links unless directly relevant to Linux VM time sync.
Virtual Machines
Upgrade Gen1 VMs to Trusted launch
...s/virtual-machines/trusted-launch-existing-vm-gen-1.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Windows and Linux guidance for upgrading Gen1 VMs to Trusted launch. However, Windows-specific tools (MBR2GPT.exe, Defrag, PowerShell) are described in detail and appear first, with Linux instructions following. Windows disk conversion and troubleshooting steps are more extensive, while Linux disk conversion is not covered (because most Marketplace Linux images already meet requirements). Azure CLI and ARM template examples are cross-platform, but PowerShell is shown first and used for template deployment. Overall, Linux users can complete the task, but Windows tools and patterns are emphasized.
Recommendations
- Present Linux and Windows instructions in parallel or with equal prominence, rather than Windows-first.
- For ARM template deployment, provide Azure CLI examples alongside PowerShell.
- Expand Linux troubleshooting guidance for disk layout issues, even if rare, to match Windows detail.
- Clarify that Azure CLI and ARM templates are fully cross-platform and recommend them for Linux users.
- Consider adding links or references to Linux disk conversion tools (e.g., gdisk, parted) for custom images.
Virtual Machines
Enable Trusted launch on existing Gen2 VMs
...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity for both Linux and Windows VMs, with explicit statements that the feature applies to both. CLI and ARM template instructions are platform-neutral. However, PowerShell instructions are given equal prominence as CLI, and PowerShell is primarily a Windows tool (though available on Linux, it's less commonly used there). Additionally, in some sections (e.g., Portal and PowerShell tabs), Windows terminology (RDP) is mentioned before Linux (SSH), and PowerShell is listed before ARM template, which may subtly prioritize Windows patterns.
Recommendations
- Clarify that PowerShell instructions are applicable on both Windows and Linux, or provide Bash/Cloud Shell alternatives where relevant.
- Consider listing CLI instructions before PowerShell, as CLI is more universally used across platforms.
- When mentioning remote access, list SSH (Linux) and RDP (Windows) together, or alternate their order to avoid subtle Windows-first bias.
- Add explicit notes or links for Linux users regarding PowerShell usage, or suggest Azure Cloud Shell as a cross-platform option.
- Ensure screenshots and terminology are neutral or include both Linux and Windows examples where possible.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most operations, but PowerShell (a Windows-centric tool) is consistently presented alongside or immediately after CLI. In some cases, Windows-specific image examples are shown first, and PowerShell is given equal prominence to CLI, which may create a subtle Windows-first impression. However, Linux-specific instructions and tools (such as SBInfo for Secure Boot validation) are included where relevant, and Linux images are referenced in CLI/PowerShell commands. There are no critical omissions for Linux users.
Recommendations
- Where possible, lead with Azure CLI examples (which are cross-platform) before PowerShell, especially in sections not inherently Windows-specific.
- When demonstrating image queries, alternate or balance the use of Windows and Linux images as examples.
- Continue to provide explicit Linux troubleshooting and validation steps, as done with the SBInfo tool.
- Consider adding Bash scripting examples for common automation scenarios, where appropriate.
- Clarify in introductory sections that both Linux and Windows are fully supported, and that all examples apply to both unless otherwise noted.
Virtual Machines
Trusted Launch for Azure VMs
.../blob/main/articles/virtual-machines/trusted-launch.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation covers Trusted Launch for both Linux and Windows VMs, but there are several subtle signs of Windows bias. Windows examples and references (such as ARM templates for Windows VMs) are presented first in example lists. Windows-specific tools and features (like Windows Defender Credential Guard, HVCI, and Secure Boot references) are discussed in detail, with less depth for Linux equivalents. Some links and explanations (e.g., Secure Boot, vTPM, VBS) reference Windows documentation or features before Linux, and Windows driver installation is described as 'not requiring extra steps', while Linux installation is described as requiring workarounds.
Recommendations
- Provide Linux-focused deployment examples alongside or before Windows examples, especially in sections listing ARM templates.
- Expand explanations of Linux equivalents for security features (e.g., Secure Boot, attestation, kernel module validation) to match the depth given to Windows features.
- Balance references to Windows tools with Linux tools (e.g., mention Linux attestation and boot integrity solutions).
- Ensure that Linux-specific guidance (such as driver installation steps) is as clear and prominent as Windows guidance.
- Where possible, link to Linux documentation or community resources for features like Secure Boot and vTPM.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization. However, the PowerShell section is presented immediately after the CLI section, and the PowerShell example is detailed and uses Windows-centric terminology (e.g., PowerShell SDK objects). The CLI example uses a Linux image (Ubuntu2204), but there is no explicit Linux/macOS shell example or mention of Bash scripting. The documentation refers to SQL Server as a licensing example, which is Windows-centric, but this is not flagged as bias since SQL Server is also available on Linux. Overall, the documentation is slightly Windows-biased in its ordering and tooling focus, but Linux users can complete all tasks using the CLI and ARM templates.
Recommendations
- Add explicit Bash or Linux/macOS shell examples for Azure CLI usage, clarifying that CLI commands work cross-platform.
- Consider mentioning that PowerShell is available on Linux/macOS, or provide a Bash equivalent for any PowerShell-specific steps.
- Ensure that CLI examples are shown first or equally with PowerShell, and clarify that both methods are supported on all OSes.
- Add a note that ARM templates and Azure CLI are fully cross-platform and suitable for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for VM vCore customization, but the PowerShell section is presented immediately after the CLI section and is detailed, which may suggest a slight Windows-first bias. However, the CLI example uses an Ubuntu image and is clearly cross-platform. There are no missing Linux examples, and no exclusive mention of Windows tools or patterns. The ARM template section is platform-neutral. The overall bias is minor and does not significantly impact Linux/macOS users.
Recommendations
- Consider explicitly stating that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Add a brief note in the PowerShell section clarifying its Windows-centric nature.
- Ensure parity in example detail between CLI and PowerShell sections.
- Optionally, provide Bash shell scripting examples for Linux users, though Azure CLI already covers this.
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 given equal prominence as the CLI, and the CLI example is not explicitly labeled as Linux/macOS-friendly. The PowerShell section may imply a Windows-centric approach, and the CLI example is shown first, but overall, Linux users can fully complete the task using the CLI instructions.
Recommendations
- Explicitly state that Azure CLI works on Linux, macOS, and Windows, and is the recommended cross-platform tool.
- Add a note clarifying that PowerShell examples are primarily for Windows users, while CLI is for all platforms.
- Consider mentioning Bash or shell scripting for advanced quota checks, if relevant.
- Ensure future examples do not assume PowerShell as the default unless the topic is 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 and references are frequent and often shown alongside or before CLI equivalents. Windows-specific tools (Sysprep) are mentioned before Linux equivalents (waagent), and links to Windows upload instructions are listed before Linux. Some references and examples default to Windows terminology or patterns, even though the feature is cross-platform.
Recommendations
- Ensure that Linux examples (Azure CLI, waagent, Linux upload instructions) are presented with equal prominence and order as Windows/PowerShell examples.
- Where PowerShell and CLI examples are shown, alternate their order or group them together to avoid always showing Windows first.
- Add explicit Linux-focused sections or examples where only Windows/PowerShell is currently referenced.
- Review links and references to ensure Linux documentation is as accessible as Windows documentation.
- Where possible, use neutral language and avoid defaulting to Windows terminology when the feature is cross-platform.
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 cross-platform examples for creating an Azure Compute Gallery, including Azure CLI, REST API, Portal, and PowerShell. However, PowerShell examples are presented alongside CLI and REST, and the PowerShell section is given equal prominence. The CLI examples use Bash-style syntax and variables, which are Linux/macOS-friendly. The only minor bias is that PowerShell is included as a primary example, which may be unnecessary for Linux/macOS users, but there are no missing Linux examples or Windows-only tools.
Recommendations
- Clarify in the PowerShell section that PowerShell is primarily for Windows users, and suggest Azure CLI as the preferred cross-platform tool.
- Consider listing Azure CLI examples before PowerShell to reinforce Linux/macOS parity.
- Explicitly state that Azure CLI works on Windows, Linux, and macOS, making it the recommended option for non-Windows environments.
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, as indicated by the title and content. However, there is a mild Windows bias in the ordering and prominence of deployment examples: Azure PowerShell instructions and examples are presented before Azure CLI, even though Linux users are more likely to use Azure CLI. Additionally, troubleshooting instructions reference Azure PowerShell before Azure CLI. There are no Windows-only tools or missing Linux examples; all technical steps and paths are Linux-specific.
Recommendations
- Present Azure CLI deployment instructions before Azure PowerShell, as CLI is the primary tool for Linux users.
- Highlight Azure CLI as the recommended method for Linux deployments.
- Ensure troubleshooting sections reference Azure CLI first, followed by PowerShell.
- Consider adding a note clarifying that PowerShell is optional and primarily for cross-platform or Windows users.
Virtual Machines
Deprovision or generalize a VM before creating an image
...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides clear, parallel instructions for both Linux and Windows VM generalization. However, the Windows section includes more detailed prerequisites and troubleshooting steps, and Windows PowerShell/Command Prompt examples are shown before their Linux equivalents in some places. The Linux section is concise and relies heavily on waagent, while the Windows section uses multiple Windows-specific tools and registry edits. Both OSes are covered, but Windows examples and tools are somewhat more prominent.
Recommendations
- Ensure Linux prerequisites are as detailed as Windows prerequisites, including troubleshooting tips and common pitfalls.
- Provide Linux CLI alternatives for all Azure CLI and PowerShell commands (e.g., show az CLI usage for both OSes, not just in Linux section).
- Consider presenting Linux and Windows sections in parallel structure, or alternate which OS is shown first in examples.
- Expand Linux section to include more context about potential issues, similar to the Windows section.
- Where possible, avoid using Windows-specific terminology (e.g., 'Command Prompt') without Linux equivalents (e.g., 'Terminal').
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 comprehensive Linux-specific guidance. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details. All configuration examples, tools, and commands are Linux-centric, with only a single PowerShell command shown for base64 encoding cloud-init (which is relevant for Azure ARM templates, not VM configuration). There are no missing Linux examples or Windows tools used for core tasks.
Recommendations
- Move or minimize the Windows Server 2016 discussion in the introduction, emphasizing Linux relevance first.
- Add a brief explanation for the PowerShell base64 example, noting that Linux users can use 'base64' command instead.
- Consider linking to Linux time sync concepts/documentation before Windows references in the intro and 'Next steps'.
Virtual Machines
Deploy a Trusted Launch VM
...ain/articles/virtual-machines/trusted-launch-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows VM deployment with Trusted Launch, but PowerShell examples are Windows-centric and Windows examples are often presented first. Linux parity is generally good, especially in CLI and template sections, but PowerShell sections focus on Windows images and configurations, and Windows terminology appears before Linux in some places.
Recommendations
- Provide PowerShell examples for Linux VM deployment, including using Set-AzVMOperatingSystem with -Linux and Linux image parameters.
- When listing examples, alternate or parallelize Windows and Linux instructions, rather than defaulting to Windows first.
- Clarify in PowerShell sections that Linux VMs can also be deployed and provide sample scripts for Linux.
- Ensure that terminology and screenshots are inclusive of both OS types, or explicitly state when a step is OS-specific.
Virtual Machines
Enable Trusted launch on existing Gen2 VMs
...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity for both Linux and Windows VMs, but there is a mild Windows bias in the ordering and tooling. PowerShell examples are given equal prominence to Azure CLI, but PowerShell is a Windows-centric tool. In the ARM template section, PowerShell is used for deployment commands rather than CLI or cross-platform alternatives. Windows terminology (RDP) is mentioned before Linux (SSH) in verification steps. However, Linux-specific guidance (such as SBInfo for Secure Boot validation) is included, and all procedures are applicable to both OS types.
Recommendations
- In ARM template deployment steps, provide Azure CLI examples alongside PowerShell to ensure cross-platform usability.
- Where possible, mention SSH (Linux) and RDP (Windows) together or alternate their order to avoid Windows-first bias.
- Consider clarifying that PowerShell commands can be run on Linux/macOS via PowerShell Core, or provide CLI alternatives.
- Continue to highlight Linux-specific tools and validation steps as done with SBInfo.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization. The CLI example uses Ubuntu as the image, showing Linux parity, but the PowerShell section is more detailed and appears before ARM template automation. The PowerShell example uses Windows-centric SDK objects and terminology. The ordering of sections (CLI, then PowerShell) is reasonable, but the PowerShell example is more verbose and technical. No Linux-specific tools (like Bash scripts or cloud-init) are mentioned, but the CLI example covers Linux use cases. There is minor bias in the depth and detail of Windows/PowerShell instructions.
Recommendations
- Add Bash or shell script examples for Linux users, especially for automation scenarios.
- Clarify that Azure CLI works equally well for both Linux and Windows, and provide explicit Linux/macOS usage notes.
- Balance the detail between PowerShell and CLI sections, ensuring CLI instructions are as comprehensive as PowerShell.
- Mention Linux-specific automation tools (e.g., cloud-init) if relevant.
- Consider adding a table or summary comparing CLI, PowerShell, and ARM template approaches for both OS types.
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, with CLI examples shown first. There are no Linux-specific tools or shell scripts, but the CLI coverage is sufficient for Linux/macOS users. No Windows-only tools or patterns are mentioned, and the PowerShell example is not prioritized over CLI. The presence of PowerShell is expected for Azure, but the lack of explicit Linux shell scripting or troubleshooting is a minor bias.
Recommendations
- Consider adding explicit Bash shell script examples for common Linux automation scenarios (e.g., using az CLI in bash loops or with jq for JSON parsing).
- Clarify in the introduction that all CLI examples are cross-platform and suitable for Linux/macOS users.
- If there are any troubleshooting steps or advanced usage, provide Linux/macOS-specific notes if behavior differs.
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 primarily Linux-focused, as indicated by the title and content. However, there are some minor Windows bias patterns: PowerShell deployment instructions are presented before Azure CLI instructions, and troubleshooting examples use PowerShell first. The CLI and JSON examples are present and correct for Linux, but the ordering and emphasis on PowerShell may create friction for Linux users who typically use Bash or Azure CLI.
Recommendations
- Present Azure CLI deployment instructions before PowerShell, as CLI is more commonly used on Linux.
- Ensure troubleshooting sections show Azure CLI commands first or equally alongside PowerShell.
- Clarify that PowerShell is optional and primarily for Windows users, while Azure CLI is recommended for Linux.
- Consider adding Bash script examples for common Linux automation scenarios.
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides parity between Linux and Windows in most sections, especially in CLI and REST examples, but there is a subtle Windows bias in the PowerShell examples and ordering. PowerShell examples are Windows-centric by default, and Windows is mentioned first in some places. Linux is well-covered, but Windows examples and terminology sometimes appear before Linux equivalents.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence and ordering, especially in PowerShell and CLI sections.
- In PowerShell examples, provide explicit Linux-focused examples (e.g., using -OsType Linux) alongside Windows ones.
- Where possible, alternate the order of Linux and Windows examples to avoid implicit prioritization.
- Add clarifying notes that PowerShell can be used for Linux images as well, and show Linux-specific PowerShell commands.
Virtual Machines
Azure Instance Metadata Service for virtual machines
...articles/virtual-machines/instance-metadata-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides both Windows (PowerShell) and Linux (bash/curl) examples for all major usage scenarios, with clear tab separation. However, Windows/PowerShell examples are consistently presented first in each sample, and some troubleshooting and advanced routing instructions are more verbose for Windows (including PowerShell CLI examples even in Linux troubleshooting). Windows-specific tools (PowerShell, route print, ipconfig) are referenced before their Linux equivalents, but Linux coverage is strong and parity is maintained throughout.
Recommendations
- Alternate the order of Windows and Linux examples, or present Linux first in some sections to avoid implicit prioritization.
- Ensure troubleshooting steps for Linux are as detailed as those for Windows, and avoid including PowerShell CLI examples in Linux troubleshooting unless a direct Linux CLI equivalent is also provided.
- Where possible, reference Linux tools (e.g., netstat, ip, ifconfig) alongside Windows tools in general guidance sections.
- Consider adding a short note at the start stating that both Linux and Windows are equally supported, and that example order does not imply priority.
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
Summary
The documentation covers both Linux and Windows VM images, but there is a mild Windows bias in several areas. PowerShell examples are provided alongside Azure CLI, but PowerShell is mentioned first or more prominently in some sections. References to Windows tools (e.g., Sysprep) are given equal footing to Linux tools (waagent), but links to Windows-specific pages (e.g., upload VHD for Windows) are sometimes listed before Linux equivalents. In the FAQ, PowerShell is mentioned before CLI for cross-tenant sharing. Overall, Linux users can complete all tasks, but Windows tools and patterns are sometimes prioritized.
Recommendations
- Ensure that CLI and PowerShell examples are presented in parallel, with equal prominence and ordering.
- When referencing upload or creation guides, list Linux and Windows links together, or alternate their order to avoid Windows-first bias.
- Where possible, provide Bash or shell script examples alongside PowerShell for automation.
- In cross-tenant sharing sections, mention CLI and PowerShell equally, or provide a combined example for both platforms.