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 801-818 of 818 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page 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 the recommended bandwidth/throughput testing tool (NTTTCP) is a Windows-centric utility. Linux equivalents or guidance are not provided, and Windows terminology/tools are mentioned first or exclusively in these contexts.
Recommendations
- For 'Nested Virtualization', add or link to Linux/KVM nested virtualization documentation if supported, or clarify platform limitations.
- In the 'Network' section, mention Linux-compatible bandwidth testing tools (e.g., iperf, netperf) alongside NTTTCP, and provide links to relevant Linux usage guides.
- Where features/tools are Windows-only, explicitly state platform restrictions and suggest Linux alternatives or workarounds.
- Review all feature support links to ensure Linux parity and add Linux-specific documentation where missing.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely neutral and platform-agnostic, but there are subtle signs of Windows bias. The only tool mentioned for bandwidth/throughput testing is NTTTCP, which is a Windows-centric tool (though it has a Linux port, it's less commonly referenced in Linux documentation). Additionally, the link for nested virtualization support points to a Windows-specific guide, and the order of mentioning Azure Disk Encryption lists Linux after Windows. However, all VM features and specifications are presented equally for both Linux and Windows, and most resources are generic.
Recommendations
- Include Linux-native tools for bandwidth/throughput testing (e.g., iperf3, netperf) alongside NTTTCP, with links to relevant guides.
- When referencing nested virtualization, provide links to both Windows and Linux documentation (if available), or clarify platform support.
- Ensure parity in listing feature support and restrictions for both Linux and Windows, and avoid listing Windows features first unless justified.
- Add explicit examples or troubleshooting steps for both Linux and Windows where OS-specific requirements (e.g., NVMe driver support) are mentioned.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page 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 to a Windows-specific Hyper-V guide, and in the 'Network' section, where bandwidth testing references NTTTCP—a Windows-centric tool—without mentioning Linux alternatives. Windows terminology/tools are mentioned before Linux equivalents, and Linux-specific guidance is minimal.
Recommendations
- Provide equivalent Linux documentation links for nested virtualization (e.g., KVM/QEMU guides).
- Mention and link to Linux-compatible network bandwidth testing tools (e.g., iperf, netperf) alongside NTTTCP.
- Ensure that feature support and troubleshooting notes reference both Windows and Linux resources where applicable.
- Clarify in notes or tables when features/tools are Windows-only and suggest Linux alternatives.
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 the link for Nested Virtualization points to a Windows/Hyper-V guide, and in the 'Network' section, where bandwidth testing references NTTTCP, a tool originally Windows-centric. Windows and Linux disk encryption support are listed together, but the nested virtualization and network testing resources favor Windows first.
Recommendations
- Include links to Linux/KVM nested virtualization documentation if relevant for Azure VMs.
- Mention Linux equivalents for network bandwidth testing (e.g., iperf, netperf) alongside NTTTCP.
- Where possible, provide parity in external documentation links for both Windows and Linux.
- Clarify that features/tools apply to both platforms, or note any platform-specific limitations.
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 Mdsv3-VHM-series with Windows Server mentioned first, followed by Linux distributions. No command-line examples, tooling, or operational instructions are provided, so there is no evidence of Powershell-heavy or Windows-tools bias. The only minor bias is the ordering of Windows before Linux in the compatibility list.
Recommendations
- List Linux distributions before or alongside Windows in compatibility sections to avoid implying Windows primacy.
- Explicitly state that all features and instructions apply equally to Linux and Windows unless there are OS-specific caveats.
- If future documentation adds operational examples, ensure parity by providing both Linux (bash/CLI) and Windows (PowerShell) instructions.
Virtual Machines
Troubleshoot problems with shared images in Azure
...cles/virtual-machines/troubleshooting-shared-images.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation references both Azure CLI and PowerShell for troubleshooting, but explicitly mentions the PowerShell '-Debug' switch alongside the CLI '--debug' switch. PowerShell is a Windows-centric tool, and its mention may imply a Windows-first approach. No Linux/macOS-specific troubleshooting tools or shell examples are provided, and PowerShell is listed before any Linux shell alternatives. There are no explicit Linux/macOS command examples, nor is Bash or other Unix shell troubleshooting discussed.
Recommendations
- Add explicit Bash or shell examples for Linux/macOS users, such as using Azure CLI in Bash with '--debug'.
- Clarify that PowerShell is optional and provide parity for Linux/macOS troubleshooting workflows.
- Mention cross-platform alternatives to PowerShell, such as Bash or zsh, and provide equivalent troubleshooting steps.
- Ensure that references to tools are ordered neutrally or with cross-platform tools first (e.g., Azure CLI before PowerShell).
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
Windows Heavy References
Summary
The documentation page for Trusted Launch for Azure VMs is generally cross-platform, but exhibits mild Windows bias. Windows examples and references (such as ARM templates for Windows VMs) are listed before Linux equivalents, and links to Windows-specific documentation (e.g., Secure Boot, TPM, VBS, Credential Guard) are more prevalent. Some sections, such as Virtualization-based Security and vTPM, reference Windows features and tools without mentioning Linux equivalents or alternatives. However, Linux support is clearly indicated, and Linux-specific notes (e.g., Secure Boot and driver installation) are present.
Recommendations
- Provide Linux-focused deployment examples (e.g., ARM templates for Linux VMs) alongside Windows examples.
- Include references to Linux documentation for Secure Boot, TPM, and attestation, not just Windows links.
- Mention Linux alternatives or equivalents for features like Virtualization-based Security and Credential Guard, or clarify their applicability.
- Ensure that examples and references are balanced between Windows and Linux, or alternate their order.
- Add more explicit guidance for Linux users in sections that currently focus on Windows tools or features.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias. Windows tools and terminology (such as PowerShell and Windows signature templates) are mentioned alongside or before Linux equivalents. In scenario 3, 'MicrosoftWindowsTemplate' is listed as a signature template, but there is no explicit mention of Linux-specific templates. The instructions for creating gallery and image definition resources list 'Azure portal, PowerShell, CLI, or REST API', with PowerShell (Windows-centric) mentioned before CLI (cross-platform). However, Linux verification commands (mokutil) and useful links for Linux distributions are provided, showing some effort toward Linux parity.
Recommendations
- List Azure CLI before PowerShell when describing cross-platform workflows.
- Explicitly mention Linux-specific signature templates if available, or clarify their absence.
- Provide example workflows using Linux tools (e.g., OpenSSL) for certificate/key creation.
- Include Linux/macOS-specific instructions for gallery/image resource creation, if they differ.
- Clarify that all steps can be performed on Linux/macOS where applicable.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally addresses both Linux and Windows VMs, but there is a subtle Windows bias: in the 'Reduce downtime' section, scheduled events for Linux are mentioned after Windows, and no concrete examples or commands are provided for either platform. There is also a lack of platform-specific guidance or parity in examples, which could leave Linux users seeking more actionable information.
Recommendations
- Present Linux and Windows examples side-by-side, or alternate which platform is mentioned first.
- Provide concrete examples or links for both Linux and Windows (e.g., sample scripts for handling scheduled events on each OS).
- Ensure that any platform-specific tools or procedures are described equally for both Linux and Windows.
- Explicitly mention any differences in handling reboots or downtime between Linux and Windows VMs.
Virtual Machines
Overview of Maintenance control for OS image upgrades on Azure Virtual Machine Scale Sets
...ines/virtual-machine-scale-sets-maintenance-control.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page shows a Windows bias by listing Azure PowerShell as the first management option and highlighting PowerShell in the 'Next steps' section, while Linux-friendly tools like Azure CLI are mentioned but not emphasized. No Linux/macOS-specific examples or guidance are provided.
Recommendations
- Provide equal prominence to Azure CLI in both the management options and next steps sections.
- Include direct links to CLI-based walkthroughs or examples for Linux/macOS users.
- Add a note clarifying that all features are available via CLI and portal, and mention platform compatibility.
- Rotate or randomize the order of management options to avoid implicit prioritization.
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 demonstrates a mild Windows bias by referencing Windows-specific technologies (VSS) and listing Windows examples and tools before their Linux equivalents. While Linux is mentioned and supported, Windows terminology and troubleshooting steps are more prominent.
Recommendations
- Present Windows and Linux information in parallel, rather than listing Windows first.
- Expand Linux-specific troubleshooting guidance, including common issues with pre-/post-scripts.
- Provide equal detail for both VMSnapshot Windows and Linux extensions, including links to Linux-specific documentation.
- Clarify the Linux restore point process, especially how application consistency is achieved.
- Include Linux-first or cross-platform examples where possible.
Virtual Machines
Copy VM restore points to another region
...achines/virtual-machines-copy-restore-points-how-to.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is largely platform-neutral in its API focus, but there is a subtle Windows bias in the ordering and detail of configuration examples. Windows-specific configuration fields (such as 'windowsConfiguration', 'winRM', 'additionalUnattendContent', and 'certificateStoreName on Windows') are described first and in greater detail than their Linux equivalents. Linux configuration is present but less detailed and always follows Windows fields. Some fields (e.g., 'certificateStore') are labeled as Windows-only, with no Linux alternative or explanation.
Recommendations
- Present Linux and Windows configuration examples with equal detail and in parallel, rather than listing Windows first.
- Clarify which fields are Windows-only and provide Linux alternatives or explicitly state when a feature is not available for Linux.
- Expand Linux configuration documentation to match the depth provided for Windows (e.g., provide examples for customData, SSH options, and disk restore points).
- Add explicit notes or tables comparing Windows and Linux restore point behaviors and supported features.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux, but there are subtle signs of Windows bias. Windows-specific details (such as page file placement and OS image sizing) are often mentioned first or exclusively, and PowerShell is referenced before CLI in some places. Windows tools and patterns (like PowerShell) are highlighted, sometimes before their Linux equivalents. However, Linux examples and references are present, and most features are described for both OS types.
Recommendations
- Ensure that Linux and Windows examples are presented side-by-side or in parallel, rather than Windows first.
- When referencing command-line tools, mention Azure CLI (cross-platform) before PowerShell, or provide both examples together.
- Include explicit Linux-specific details where Windows-specific details are given (e.g., page file placement for Linux).
- Avoid using Windows-centric terminology or examples in sections that apply equally to Linux.
- Where links to PowerShell instructions are provided, ensure equivalent Linux/CLI links are equally prominent.
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 overwhelmingly Linux-focused, as expected for the Azure Linux VM Agent. However, there is a minor Windows bias in the configuration section: the SSH key type recommendation references putty.exe on Windows, and one of the external links in the Ubuntu Cloud Images section points to a Windows VM deployment tutorial. These inclusions may distract Linux users or suggest Windows tooling as a default.
Recommendations
- Remove or rephrase the reference to putty.exe in the SSH key type section. If mentioning Windows SSH clients, also mention Linux/macOS equivalents for parity.
- Replace or supplement the Windows VM deployment tutorial link in the Ubuntu Cloud Images section with a Linux-focused tutorial or documentation.
- Ensure all external references and examples are relevant to Linux users, given the page's audience and intent.
Virtual Machines
Chef extension for Azure VMs
...blob/main/articles/virtual-machines/extensions/chef.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides examples and instructions for both Linux and Windows, but there is a subtle Windows bias. The publisher value is 'Chef.Bootstrap.WindowsAzure', which references Windows Azure branding. The extension type for Linux ('LinuxChefClient') is mentioned after the Windows type ('ChefClient'). File paths for logs are given for both OSes, but the Windows path is shown second. There are no PowerShell-heavy examples, and the Azure CLI is used throughout, which is cross-platform. However, there is a lack of explicit Linux-first examples and some terminology (e.g., publisher name) is Windows-centric.
Recommendations
- Present Linux and Windows extension types in parallel or with Linux first, especially in tables and examples.
- Clarify that 'Chef.Bootstrap.WindowsAzure' is used for both Linux and Windows extensions, and explain the naming convention.
- Add explicit Linux-specific examples where possible, such as troubleshooting steps or log file analysis.
- Consider updating terminology to be more OS-neutral (e.g., avoid 'WindowsAzure' in publisher name if possible).
Virtual Machines
Availability options for Azure Virtual Machines
...cs/blob/main/articles/virtual-machines/availability.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page is generally cross-platform, but there is a subtle Windows bias in the 'Load balancer' section, where PowerShell is mentioned and linked before the CLI, and both are presented as quickstart options. No Linux-specific tools or examples are highlighted, and PowerShell (primarily a Windows tool, though available on Linux) is given equal or slightly more prominence than CLI, which is more universal. The rest of the page is neutral and references both Linux and Windows VMs equally.
Recommendations
- Present CLI examples and links before PowerShell, as CLI is more universal and preferred on Linux/macOS.
- Explicitly mention that PowerShell is available on Linux/macOS if linking to PowerShell instructions.
- Add Bash or Linux-specific command examples where relevant, especially in sections discussing VM creation or management.
- Ensure that any referenced quickstarts or tutorials include both Linux and Windows instructions, or clarify platform applicability.
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-oriented in its Azure CLI examples, but there is mild Windows bias in the 'Next steps' section, where PowerShell-based disaster recovery guides for VMware and Hyper-V are highlighted before any Linux alternatives. Additionally, the page references Windows VMs alongside Linux VMs in applicability, but does not provide Windows-specific CLI or PowerShell examples, nor does it mention Linux tools or patterns in the 'Next steps'.
Recommendations
- Add equivalent Linux-based disaster recovery guides or CLI-based instructions in the 'Next steps' section.
- Ensure that Linux and Windows tools are mentioned with equal prominence, or group them by platform.
- Where PowerShell is referenced, provide a CLI or Bash alternative if possible.
- Explicitly state that the Azure CLI examples are cross-platform, and note any platform-specific considerations.
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
Windows Tools
Powershell Heavy
Summary
The documentation is overwhelmingly focused on Linux, with all main examples, commands, and procedures using Linux tools and conventions. However, the only mention of Windows tooling is in the final section, where a PowerShell script is provided to check classic VM SKU support for disk expansion without downtime. There is no equivalent Bash/Azure CLI script for Linux users in this section, and PowerShell is presented as the only option.
Recommendations
- Provide an equivalent Bash/Azure CLI script for Linux/macOS users to check classic VM SKU support for disk expansion without downtime.
- Clarify that the PowerShell script is only needed for users who manage Azure resources from Windows, and offer guidance for Linux users.
- Consider moving the PowerShell example to a separate section or tab labeled 'Windows' and add a 'Linux/macOS' tab with a CLI or REST API example.