Virtual Machines
2112
Total Pages
1865
Linux-Friendly Pages
247
Pages with Bias
11.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
818 issues found
Showing 576-600 of 818 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation is largely platform-neutral, but there is a subtle Windows bias in the networking section, where the recommended bandwidth/throughput testing tool (NTTTCP) is a Windows-specific utility. No Linux equivalent is mentioned, and the link provided is for a Windows-focused guide. No other Windows-specific examples, tools, or ordering are present.
Recommendations
- Mention Linux-compatible network testing tools (e.g., iperf, netperf) alongside NTTTCP.
- Provide links to Linux-focused bandwidth/throughput testing guides.
- Clarify in the documentation that NTTTCP is Windows-specific and suggest alternatives for Linux/macOS users.
Create Pull Request
Virtual Machines
Dldsv6 size series (Preview)
...irtual-machines/sizes/general-purpose/dldsv6-series.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is largely platform-neutral, focusing on VM specifications and features. However, there is mild Windows bias in the 'Feature support' section, where 'Nested Virtualization' links only to a Windows/Hyper-V guide, and in the 'Network' section, where bandwidth testing references NTTTCP, a Microsoft tool primarily associated with Windows. There are no Linux-specific examples or equivalent Linux tool references for these features.
Recommendations
- Add references to Linux/KVM nested virtualization documentation alongside the Windows/Hyper-V link.
- Mention Linux-compatible network bandwidth testing tools (e.g., iperf, netperf) in the networking section.
- Where tools or features are platform-specific, clarify applicability and provide parity guidance for Linux/macOS users.
Virtual Machines
NC_RTXPRO6000BSE_v6 size series
...s/sizes/gpu-accelerated/nc-rtxpro6000-bse-v6-series.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation is largely neutral and platform-agnostic, focusing on VM sizes, specs, and features. However, there is a minor Windows bias in the networking section, where the recommended bandwidth/throughput testing tool (NTTTCP) is a Windows-native utility. No Linux equivalent is mentioned, and no Linux/macOS-specific examples or tools are provided.
Recommendations
- Include Linux/macOS equivalents for any recommended tools, such as mentioning iperf3 or netperf for bandwidth testing alongside NTTTCP.
- Explicitly state that performance optimization and testing guidance applies to both Linux and Windows, and provide links to Linux-specific documentation where relevant.
- If referencing Windows-specific tools, add notes or alternatives for Linux/macOS users to ensure parity.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely neutral and platform-agnostic, focusing on VM specs and features. However, there are minor signs of Windows bias: the 'Nested Virtualization' feature links to a Windows/Hyper-V guide, and the bandwidth/throughput testing resource references NTTTCP, a tool traditionally associated with Windows. These references appear before or without Linux equivalents, which may create minor friction for Linux users seeking parity.
Recommendations
- Include links to Linux-specific nested virtualization documentation (e.g., KVM/QEMU on Azure).
- Mention and link to Linux-compatible bandwidth testing tools (e.g., iperf, netperf) alongside NTTTCP.
- Where possible, clarify platform applicability for referenced tools and features.
- Ensure that feature support lists and resource links are balanced between Windows and Linux, especially for advanced scenarios.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is mostly platform-neutral, but there is a subtle Windows bias in the 'Feature support' section, where Nested Virtualization is linked to a Windows/Hyper-V guide, and in the 'Network' section, where bandwidth/throughput testing references NTTTCP, a tool primarily associated with Windows. No Linux-specific examples, tools, or guidance are provided, and Windows resources are mentioned first or exclusively where relevant.
Recommendations
- Include equivalent Linux documentation links for features like Nested Virtualization (e.g., KVM/QEMU guides for Linux VMs).
- Mention Linux-compatible tools for bandwidth/throughput testing (such as iperf or netperf) alongside NTTTCP.
- Where feature support is described, clarify if/how features work on Linux and provide relevant links.
- Ensure that examples and references are balanced between Windows and Linux, or explicitly state platform applicability.
Virtual Machines
Azure virtual machine extensions and features
.../main/articles/virtual-machines/extensions/overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page presents both Linux and Windows information, but there is a subtle Windows bias. Windows tools (PowerShell) are mentioned before Linux equivalents, and Windows troubleshooting steps are referenced first. The troubleshooting table lists Windows extensions and tools prominently, including PowerShell DSC, while Linux equivalents are present but not highlighted. Windows examples and links are often shown before Linux ones, and some extension namespaces (e.g., powershell.dsc) are Windows-specific.
Recommendations
- Ensure Linux and Windows examples/tools are presented in parallel, with equal prominence.
- When listing management options (CLI, PowerShell, ARM templates), clarify which are cross-platform and provide Linux-specific command examples alongside PowerShell.
- In troubleshooting sections, alternate the order of Windows and Linux entries or group them by OS for clarity.
- Highlight Linux tools and workflows (e.g., Bash, Azure CLI) as much as PowerShell.
- Add explicit Linux command examples where only Windows/PowerShell is mentioned.
Virtual Machines
Mdsv3 Very High Memory size series
...al-machines/sizes/memory-optimized/mdsv3-vhm-series.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists compatible OS images for the VM series, mentioning Windows Server first, followed by Linux distributions. No command-line examples, tooling, or configuration steps are provided for either platform, and no Windows-specific tools or PowerShell examples are present. The only minor bias is the ordering of Windows before Linux in the compatibility list.
Recommendations
- List Linux distributions before or alongside Windows Server in the compatible images section to avoid implicit prioritization.
- If future documentation includes examples or tooling, ensure both Windows and Linux instructions are provided and presented with parity.
Virtual Machines
Best practices for virtual machine cost optimization
...s/virtual-machines/cost-optimization-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page shows mild Windows bias. Windows-specific recommendations (e.g., 'Use at least B2 for Windows machines', 'Azure Hybrid Benefit for Windows Server') are given without equivalent Linux guidance. Windows licensing cost optimization is discussed, but not Linux licensing. In several places, Windows is mentioned before Linux (e.g., VM pricing links). There are no Linux-specific cost-saving tips, and automation examples/tools are generic (Logic Apps, Azure Automation) but lack platform-specific scripts or examples.
Recommendations
- Add Linux-specific cost optimization tips, such as recommendations for Linux VM series, disk types, and licensing options (e.g., mention that Linux VMs do not incur OS licensing costs).
- Provide parity in recommendations, e.g., if Azure Hybrid Benefit for Windows Server is mentioned, clarify that Linux does not require similar licensing.
- When linking to pricing or VM size pages, present Linux and Windows options equally (not Windows first).
- Include Linux-specific automation examples or scripts where relevant.
- Explicitly state when recommendations apply to both platforms, or call out differences.
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
Missing Mac Example
Summary
The documentation is generally cross-platform and provides Linux-centric tooling examples (e.g., lstopo). However, there is a subtle Windows bias: Windows is listed first in OS support and recommendations, and the 'Recommended OS for Performance' is Windows Server 2019+, with no equivalent Linux recommendation. There are no macOS-specific examples or recommendations, and no PowerShell or Windows-only tooling is shown.
Recommendations
- Provide recommended Linux distributions and versions for optimal performance, similar to the Windows recommendation.
- List Linux and Windows OS support in alphabetical or neutral order, or explicitly state parity.
- Include macOS notes if relevant, or clarify its support status.
- If recommending Windows for performance, explain why and whether Linux can achieve similar results.
- Add Linux-specific performance tuning tips if available.
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. While CLI and REST are cross-platform, PowerShell is Windows-centric and is presented as a primary tab for creating galleries. The order of examples consistently lists PowerShell before REST, and the CLI examples use Bash-style syntax (which is cross-platform but may be less familiar to Windows users). There are no explicit Linux/macOS-specific instructions or troubleshooting notes, but the presence and prominence of PowerShell examples may signal a slight Windows bias.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide example shell environments if needed.
- Consider listing CLI examples before PowerShell to emphasize cross-platform support.
- Add notes or links for Linux/macOS users about installing and using Azure CLI.
- If PowerShell is shown, mention that PowerShell Core is available for Linux/macOS, or provide equivalent Bash scripts for resource creation.
- Ensure troubleshooting and environment setup instructions are not Windows-centric.
Virtual Machines
Best Practices for Azure VM Image Builder
...icles/virtual-machines/image-builder-best-practices.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation references both Shell and PowerShell scripts as customizer artifacts, but does not provide explicit Linux shell examples or mention Linux tools. The examples and guidance are generic, but PowerShell is mentioned alongside Shell, which may imply a Windows-first approach. No Linux-specific patterns or tools are discussed, and no Linux/macOS command examples are given.
Recommendations
- Provide explicit examples for both Linux shell scripts (e.g., Bash) and Windows PowerShell scripts in customizer/validator sections.
- Mention Linux-specific tools or patterns where relevant, such as using Bash, sh, or cloud-init for Linux VMs.
- Ensure that any references to scripts or artifacts clarify which OS they apply to, and offer parity in guidance for both platforms.
- Include links to Linux documentation or best practices for image customization.
Virtual Machines
Azure CLI - Enable customer-managed keys with SSE - managed disks
...chines/linux/disks-enable-customer-managed-keys-cli.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is primarily Linux-friendly, using Azure CLI and Bash-style scripting throughout, which is cross-platform. However, there is some Windows bias in the 'Next steps' section, where PowerShell-based disaster recovery guides for VMware and Hyper-V are highlighted, and Windows-centric scenarios are mentioned before Linux equivalents. There are no explicit PowerShell examples in the main body, but the linked resources and some terminology (e.g., 'PowerShell' and 'Hyper-V') are Windows-specific.
Recommendations
- Add equivalent Linux/macOS instructions or links for disaster recovery scenarios currently covered only with PowerShell.
- Where PowerShell is referenced, clarify that Azure CLI or Bash alternatives exist, and provide those alternatives.
- Ensure that Linux and macOS users are not required to use Windows-only tools for any critical workflows.
- Balance the order of presenting Windows and Linux scenarios in 'Next steps' and throughout the documentation.
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation is strongly Linux-focused throughout, with all main examples and instructions using Linux commands, tools, and distributions. However, there is a single section at the end ('Expand without downtime classic VM SKU support') that provides only a PowerShell script for determining classic VM SKU support, without any Bash/Azure CLI/Linux equivalent. This creates a minor bias for users on Linux/macOS who may not have access to PowerShell.
Recommendations
- Provide an equivalent Bash/Azure CLI script or command to check classic VM SKU support for expanding disks without downtime.
- Where PowerShell is used, offer cross-platform alternatives or clarify if the operation is only possible via PowerShell.
- Explicitly state platform requirements for any Windows-specific tooling or scripts.
Virtual Machines
VM Snapshot extension using VM restore points
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/virtual-machines-restore-points-vm-snapshot-extension.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific technologies (VSS) first and in more detail, and mentioning Windows extension and log paths before their Linux equivalents. Troubleshooting guidance is focused on VSS writer issues, which are Windows-specific, with no equivalent Linux troubleshooting example or detail.
Recommendations
- Present Linux and Windows information in parallel, rather than Windows-first.
- Expand troubleshooting guidance to include common Linux-specific issues and their resolution steps.
- Provide equal detail for Linux mechanisms (pre-/postscripts) as is given for VSS on Windows.
- Ensure log file locations and extension names for both platforms are presented together or in a neutral order.
Virtual Machines
Create Virtual Machine restore points
...ain/articles/virtual-machines/create-restore-points.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates mild Windows bias by referencing PowerShell and Windows-specific features before Linux equivalents. PowerShell is mentioned as a primary tool for interacting with restore points, while Linux CLI options are only referenced later and less prominently. The documentation also highlights application consistency for Windows VMs and file system consistency for Linux VMs, suggesting more robust support for Windows. No Linux-specific command-line examples or tools are provided, and Windows terminology (PowerShell) appears before CLI or REST API options.
Recommendations
- Provide Linux-specific CLI examples (e.g., Azure CLI commands) alongside or before PowerShell examples.
- Include explicit instructions or links for Linux users, such as Bash shell usage and relevant tools.
- Balance the discussion of consistency models by clarifying support levels for both Windows and Linux.
- Ensure that REST API usage is presented as the primary, cross-platform method, with platform-specific tools as secondary options.
Virtual Machines
Enable shared disks for Azure managed disks
.../main/articles/virtual-machines/disks-shared-enable.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all disk types and operations, but PowerShell examples are given equal prominence and detail as CLI, and in some cases, PowerShell is listed first (e.g., in 'Share an existing disk' and 'Using Azure shared disks with your VMs'). PowerShell is a Windows-centric tool, and its heavy usage and occasional ordering before CLI may create friction for Linux/macOS users. However, Azure CLI examples are present for all operations, and no critical steps are Windows-only.
Recommendations
- Ensure Azure CLI examples are always listed before PowerShell, as CLI is cross-platform.
- Explicitly state that all CLI commands work on Linux/macOS and Windows.
- Add bash scripting examples for common Linux automation scenarios.
- Where PowerShell is used for VM operations, provide equivalent Azure CLI or ARM template examples.
- Clarify in the prerequisites that PowerShell is optional and not required for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Minor Windows Example
Summary
The documentation is generally cross-platform and includes both Linux and Windows information. However, there are minor instances of Windows bias: Windows examples or references are sometimes presented before Linux equivalents, and Windows-specific tools (e.g., PowerShell) are mentioned before Linux tools (CLI). There are also a few sections where Windows-specific details are highlighted without a Linux counterpart, such as page file placement.
Recommendations
- Ensure that Linux and Windows examples are always presented together or alternate which comes first.
- Where Windows-specific details are given (e.g., page file placement), provide equivalent Linux information or explicitly state if not applicable.
- In sections referencing tools (e.g., PowerShell, CLI), always mention both platforms' tools together and provide parallel links/examples.
- Review tables and feature lists to ensure Linux-specific behaviors or caveats are equally documented.
Virtual Machines
Azure Linux VM Agent Overview
...in/articles/virtual-machines/extensions/agent-linux.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows Reference
Summary
The documentation is strongly Linux-focused and does not provide Windows/Powershell examples or prioritize Windows tools. However, there is a notable mention of Windows-specific tooling (putty.exe) and a reference to a Windows VM deployment tutorial in the Ubuntu Cloud Images section. These inclusions may distract Linux users or create minor confusion, but do not prevent Linux users from completing tasks.
Recommendations
- Remove or clarify the reference to putty.exe in the SSH key section, or provide equivalent Linux SSH client guidance.
- Replace or supplement the Windows VM deployment tutorial link in the Ubuntu Cloud Images section with a Linux-focused deployment tutorial.
- Ensure all external links and examples are relevant to Linux users, especially in sections explicitly about Linux VM management.
Virtual Machines
Availability options for Azure Virtual Machines
...cs/blob/main/articles/virtual-machines/availability.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally cross-platform, but there is mild Windows bias in the Load Balancer section, where PowerShell is mentioned as an example tool alongside CLI, and the PowerShell example link is listed after the CLI link. No Linux-specific tools (e.g., Bash, shell scripts) are mentioned, and there is no explicit parity in example coverage for Linux/macOS users. However, the overall content applies to both Linux and Windows VMs, and most links and next steps reference Linux-focused guides.
Recommendations
- Explicitly mention Linux/macOS tools (e.g., Bash, Azure CLI in Bash) where PowerShell is referenced.
- Ensure example links for both CLI and PowerShell are provided for all major tasks, and clarify which are cross-platform.
- Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples to reduce perceived bias.
- Add a note clarifying that Azure CLI works on Linux/macOS and Windows, and provide links to installation guides for all platforms.
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 demonstrates mild Windows bias: Windows examples and terminology (such as PowerShell and Windows extension publisher names) are presented before Linux equivalents. The PowerShell section is included as a top-level tab, while there is no equivalent Bash or shell scripting tab for Linux. The troubleshooting section references Windows extension names in error messages, and screenshots consistently show Windows-centric UI elements. However, Linux template examples are provided, and CLI instructions are generally cross-platform.
Recommendations
- Present Linux and Windows examples side-by-side, or alternate which is shown first.
- Add a Bash or shell scripting tab alongside PowerShell for parity.
- In troubleshooting, mention both Windows and Linux extension names in error messages.
- Include screenshots or instructions that reflect Linux environments where relevant.
- Clarify that CLI instructions apply to both Windows and Linux, and note any platform-specific differences.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is primarily focused on Linux, but in the section about creating a Network Security Group rule for Remote Desktop traffic, both Azure CLI and Azure PowerShell examples are provided. The PowerShell example is given equal prominence, which may be unnecessary for Linux users. Additionally, references to using SSH from Windows are present before Linux equivalents, and links to Windows-specific documentation are included. However, the core instructions for installing and configuring xrdp are Linux-centric and do not rely on Windows-only tools.
Recommendations
- Move Linux/Azure CLI examples before PowerShell examples, or clearly mark PowerShell as optional for Windows users.
- Add explicit notes clarifying that PowerShell is primarily for Windows administrators, and that Linux users should use Azure CLI.
- Ensure that links to SSH documentation for Linux/macOS are provided before or alongside Windows links.
- Consider removing or de-emphasizing Windows-specific tooling in Linux-focused documentation unless strictly necessary.
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, but the PowerShell example is given equal prominence despite being primarily a Windows tool. There is no explicit Linux bias, but the presence of PowerShell examples may suggest a Windows-centric approach, especially since PowerShell is traditionally associated with Windows environments, even though it is now cross-platform. The CLI example is shown first, which is positive for Linux parity.
Recommendations
- Clarify that PowerShell is available cross-platform, or note its installation on Linux/macOS if relevant.
- Consider adding Bash shell scripting examples for Linux users, especially for automation.
- Explicitly mention that Azure CLI works natively on Linux/macOS and Windows.
- If possible, provide example outputs from Linux/macOS terminals to reinforce cross-platform support.
Virtual Machines
Proximity placement groups
...ocs/blob/main/articles/virtual-machines/co-location.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. In sections discussing how to check colocation status, PowerShell is mentioned before CLI, and the PowerShell cmdlet is described in more detail. In the best practices section, the Windows accelerated networking guide is listed after the Linux guide, but both are present. References to PowerShell and CLI are present throughout, but there are no Linux shell script examples or explicit parity for Linux-specific tooling. The next steps section links to both Linux (CLI) and Windows (PowerShell) guides, but the page does not provide in-page command examples for either platform.
Recommendations
- When listing tools or commands, alternate the order (e.g., CLI before PowerShell in some sections) or present them together.
- Include explicit Linux shell (bash) examples where relevant, not just CLI references.
- Ensure that Linux and macOS users are addressed in all command-line instructions, not just via CLI.
- Add a note clarifying parity between Windows and Linux workflows, especially for tasks that can be completed using either CLI or PowerShell.
- Consider adding a table summarizing commands for both platforms side-by-side.
Virtual Machines
Support matrix for VM restore points
...n/articles/virtual-machines/concepts-restore-points.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows operating system support details before Linux, listing specific Windows versions and then referencing Linux distributions. No command-line examples or tooling are provided in this page, but the ordering prioritizes Windows information. There is no evidence of exclusive Windows tools, PowerShell-heavy examples, or missing Linux equivalents in this page.
Recommendations
- Present Windows and Linux operating system support in parallel or alphabetical order to avoid perceived prioritization.
- Ensure that any referenced 'Next steps' documentation (CLI, Portal, PowerShell) includes Linux-friendly examples and tools, such as Bash/CLI commands.
- Explicitly mention Linux-specific considerations or features where relevant, to provide parity in detail.
Virtual Machines
Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents."
...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias in several areas. Windows tools and patterns (e.g., Volume Shadow Service, SQL Server Always On) are mentioned before or in more detail than their Linux equivalents. Application-consistent backup for Windows (VSS) is described with more specificity, while Linux alternatives (fsfreeze) are mentioned briefly and with less clarity. SQL Server (Windows-centric) is referenced repeatedly, with less coverage of Linux database backup strategies. There are no explicit PowerShell examples, but the overall framing and tool references favor Windows environments.
Recommendations
- Provide equal detail for Linux backup tools (e.g., describe how to use fsfreeze, LVM snapshots, or other Linux-native mechanisms for application-consistent backups).
- Include examples and references for Linux database backup strategies (e.g., PostgreSQL, MySQL, MongoDB), not just SQL Server and Oracle.
- When discussing coordinated backup, offer step-by-step Linux procedures alongside Windows VSS explanations.
- Add links to Linux-specific documentation for backup and disaster recovery on Azure.
- Ensure that both Windows and Linux scenarios are presented with parity in detail and guidance.