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 551-575 of 818 flagged pages
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/general-purpose/dcadsv5-series.md
...rtual-machines/sizes/general-purpose/dcadsv5-series.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias, most notably in the 'Feature support' section where 'Nested Virtualization' links exclusively to a Windows/Hyper-V guide, and in the 'Network' section where bandwidth testing references NTTTCP, a Microsoft/Windows-centric tool, without mentioning Linux alternatives. There are no explicit Linux examples or equivalent Linux tooling references, and Windows tools/patterns are mentioned first or exclusively in relevant contexts.
Recommendations
- Include Linux equivalents or alternatives when referencing Windows-specific features or tools (e.g., mention KVM/QEMU for nested virtualization, and iperf or netperf for network bandwidth testing).
- Provide links to Linux documentation or guides alongside Windows/Hyper-V links, especially in feature support sections.
- Add explicit Linux usage examples or notes where relevant, ensuring parity in guidance for both platforms.
- Review referenced tools and resources to ensure cross-platform applicability, or clearly indicate platform-specific limitations.
Create Pull Request
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/memory-optimized/eadsv7-series.md
...rtual-machines/sizes/memory-optimized/eadsv7-series.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page generally maintains OS neutrality, but there are subtle signs of Windows bias. Specifically, the 'Nested Virtualization' feature links only to a Windows/Hyper-V guide, and the bandwidth/throughput testing resource references NTTTCP, a tool with a Windows-centric history (though now cross-platform). In the network section, Windows is mentioned before Linux in the context of performance optimization, and no Linux-specific tools or examples are provided. There are no explicit Linux command examples, and Linux parity is not highlighted.
Recommendations
- Provide equivalent Linux documentation links for features like Nested Virtualization (e.g., KVM/QEMU on Linux).
- When referencing tools like NTTTCP, clarify their cross-platform availability and consider mentioning Linux-native alternatives (e.g., iperf, netperf) for network testing.
- When discussing OS-specific requirements or optimizations, list Linux and Windows in parallel or alphabetically, rather than putting Windows first.
- Add explicit Linux examples or links where relevant, especially in sections discussing performance tuning, disk encryption, or network testing.
- Review all feature support and resource links to ensure Linux parity and visibility.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/memory-optimized/ebdsv6-series.md
...rtual-machines/sizes/memory-optimized/ebdsv6-series.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias. In the 'Feature support' section, nested virtualization links to a Windows-specific guide ('hyper-v-on-windows'), and the network performance testing resource references NTTTCP, a Microsoft/Windows tool, without mentioning Linux alternatives. Additionally, Windows terminology and resources (e.g., 'Generation 1/2 VMs', 'Azure Disk Encryption for Windows VMs') are mentioned before or alongside Linux equivalents, but Linux-specific examples or tools are not provided.
Recommendations
- Include Linux-specific examples and links for features such as nested virtualization (e.g., KVM/QEMU guides for Linux).
- Mention and link to Linux-compatible network performance testing tools (e.g., iperf, netperf) alongside NTTTCP.
- Ensure parity in documentation by providing both Windows and Linux references for VM features and management tasks.
- Where possible, alternate the order of Windows and Linux mentions, or group them together to avoid implicit prioritization.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/memory-optimized/m-series.md
...es/virtual-machines/sizes/memory-optimized/m-series.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page shows mild Windows bias. In the VM Basics section, Windows Server is listed first among supported guest OS versions for large vCPU counts, ahead of Linux distributions. In the Feature Support section, nested virtualization links specifically to a Windows/Hyper-V guide, with no mention of Linux alternatives. In the Networking section, bandwidth testing references NTTTCP, a Windows-centric tool, without mentioning Linux equivalents like iperf.
Recommendations
- List supported guest OS versions in alphabetical order or alternate the order to avoid Windows-first bias.
- Provide links to nested virtualization documentation for both Windows (Hyper-V) and Linux (KVM/QEMU) environments.
- Mention Linux-compatible network testing tools (e.g., iperf, netperf) alongside NTTTCP in the networking resources.
- Ensure that examples, guides, and references are provided for both Windows and Linux wherever relevant.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/using-managed-disks-template-deployments.md
...l-machines/using-managed-disks-template-deployments.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation consistently uses Windows-based examples and references, such as the 'vm-simple-windows' template and 'MicrosoftWindowsServer' images, throughout all code samples and explanations. Linux equivalents are not provided in the main body, and Linux-specific image references or templates are only mentioned in the 'Next steps' section, not in the core instructional content.
Recommendations
- Provide parallel Linux examples alongside Windows examples in all code snippets, using Linux image references (e.g., 'publisher': 'Canonical', 'offer': 'UbuntuServer').
- Reference both Windows and Linux quickstart templates in the main instructional sections, not just in 'Next steps'.
- Explicitly show how parameters (such as 'windowsOSVersion') would differ for Linux deployments.
- Clarify any OS-specific differences in disk deployment or template structure, if applicable.
- Ensure that introductory and example sections do not default to Windows-only resources or naming conventions.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/understand-vm-reboots.md
...ain/articles/virtual-machines/understand-vm-reboots.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation claims applicability to both Linux and Windows VMs, but there is a subtle Windows-first bias. In the 'Reduce downtime' section, the link to 'scheduled events for Linux' is listed after 'scheduled events for Windows', and there are no explicit Linux-specific examples or tools mentioned elsewhere. No PowerShell or Windows-only commands are present, but Linux parity is not fully achieved due to lack of Linux-specific guidance or examples.
Recommendations
- List Linux and Windows resources in parallel or alternate the order to avoid Windows-first bias.
- Include Linux-specific examples, such as using cloud-init, waagent, or relevant Linux commands for handling maintenance events.
- Explicitly mention any Linux-specific considerations or tools where applicable, similar to how Windows tools would be referenced.
- Ensure that links to Linux and Windows documentation are given equal prominence and detail.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/virtual-machines-create-restore-points-portal.md
...hines/virtual-machines-create-restore-points-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on using the Azure portal for creating and restoring VM restore points, with references to alternative methods via Azure CLI and PowerShell. However, when linking to further instructions on restoring a VM from a disk, it directs users to Windows-specific guides ('./windows/create-vm-specialized-portal.md' and './windows/attach-managed-disk-portal.yml'), without mentioning or linking to Linux equivalents. There are no Linux-specific examples or instructions, and the restoration workflow appears Windows-centric.
Recommendations
- Include links to Linux-specific documentation for creating VMs from disks and attaching managed disks, such as './linux/create-vm-specialized-portal.md' and './linux/attach-managed-disk-portal.yml'.
- Add explicit instructions or examples for restoring Linux VMs from restore points, ensuring parity with the Windows workflow.
- Where alternative methods (CLI, PowerShell) are mentioned, clarify which commands or scripts are suitable for Linux environments.
- Review all referenced guides and ensure both Windows and Linux paths are presented side-by-side, or at least both are mentioned.
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 (bash-style) and Azure PowerShell examples for creating instant access snapshots, but the PowerShell example is given equal prominence and appears immediately after the CLI example. There is no explicit Linux/macOS bias, but the ordering and inclusion of PowerShell (a Windows-centric tool) may suggest a slight Windows-first approach. No Windows-specific tools or patterns are mentioned exclusively, and all instructions are cross-platform except PowerShell, which is primarily used on Windows. No Linux-specific examples (e.g., Bash scripting, references to Linux tools) are provided, but the CLI example is applicable to Linux/macOS users.
Recommendations
- Consider explicitly stating that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Add a brief note clarifying that PowerShell is primarily for Windows users, while Azure CLI works on Linux/macOS.
- If possible, provide a Bash shell script example for Linux users, or highlight CLI usage as the default for non-Windows environments.
- Ensure that CLI examples are always shown first and labeled as the recommended approach for Linux/macOS.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides both Azure CLI and Azure PowerShell deployment instructions. However, PowerShell examples and troubleshooting commands are presented before their Azure CLI equivalents, and PowerShell-specific warnings are highlighted. There is a slight bias toward PowerShell/Windows tooling, even though the extension is Linux-specific. All technical instructions and examples are applicable to Linux, but the ordering and emphasis may create friction for Linux/macOS users who typically use Azure CLI or shell scripting.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is more commonly used on Linux/macOS.
- Add explicit notes clarifying that Azure PowerShell is cross-platform, but Azure CLI is the default for Linux users.
- Highlight Linux-native troubleshooting tools (e.g., journalctl, systemctl) for extension diagnostics in addition to Azure CLI/PowerShell.
- Remove or minimize PowerShell-specific warnings unless they are critical for Linux users.
- Ensure all example commands use Linux shell syntax (e.g., avoid PowerShell backticks in CLI examples).
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 covers both Linux and Windows VM generalization, but the Windows section presents Windows-specific tools (Sysprep, PowerShell) and registry commands before their Linux equivalents. Windows examples (PowerShell, Command Prompt) are shown in detail, and the Windows section includes more granular prerequisites and troubleshooting steps. However, Linux instructions are present and clearly separated, with links to distro-specific guides.
Recommendations
- Ensure Linux and Windows sections are equally detailed, including troubleshooting and prerequisites for Linux (e.g., common waagent issues, disk encryption, supported distros).
- Present Linux and Windows sections in parallel structure, possibly with a summary table comparing steps for both OSes.
- Add Linux-specific command-line examples for marking a VM as generalized (currently only Azure CLI is shown, but PowerShell is used for Windows).
- Include links to Linux troubleshooting or waagent logs, similar to the Windows Panther directory step.
- Consider alternating the order of Linux and Windows sections or presenting them side-by-side to avoid 'windows_first' bias.
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 the PowerShell example, Windows is shown first and Linux is mentioned as an alternative. The CLI example shows Linux first, but the PowerShell section is more detailed and prominent, which may favor Windows users. There are no missing Linux examples, and both platforms are covered, but Windows terminology and tools (Sysprep, PowerShell) are referenced before their Linux equivalents in some sections.
Recommendations
- Ensure that Linux and Windows examples are presented with equal prominence and detail in all sections.
- In PowerShell sections, show Linux examples first or alternate the order to avoid Windows-first bias.
- Where Windows-specific tools (e.g., Sysprep) are mentioned, ensure Linux equivalents (e.g., waagent -deprovision) are referenced with equal clarity.
- Consider adding Bash or shell script examples for Linux users alongside PowerShell examples.
- Review the language to avoid defaulting to Windows terminology when both platforms are supported.
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 Windows and Linux VM images, but there is a mild bias toward Windows in example ordering and tooling. PowerShell examples are provided alongside Azure CLI, but PowerShell is a Windows-centric tool. In several places, Windows-specific links and terminology are mentioned before Linux equivalents. However, Linux support is clearly stated and Linux-specific tools (waagent) are referenced where relevant.
Recommendations
- Ensure Linux and Windows examples are presented in parallel, with equal prominence.
- Where PowerShell is used, always provide a CLI or Bash equivalent for Linux/macOS users.
- When linking to upload instructions or specialized image guides, list Linux and Windows links together or alternate their order.
- Explicitly mention cross-platform support for Azure CLI and encourage its use for Linux/macOS users.
- Review FAQ and example sections to ensure Linux scenarios are not secondary to Windows.
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 section is presented second and is focused on the Windows-specific PowerShell tool. There is a slight bias in that PowerShell (a Windows-centric tool) is given its own section, and the CLI example is presented first, which is more cross-platform. No Linux-specific commands or tools are missing, but the PowerShell section may be less relevant for Linux/macOS users.
Recommendations
- Clarify that PowerShell examples are primarily for Windows users, and note that Azure CLI is recommended for Linux/macOS.
- Consider adding a note that Azure CLI works natively on Linux/macOS and is the preferred cross-platform tool.
- If relevant, mention that PowerShell Core is available on Linux/macOS, but most users on those platforms use Azure CLI.
- Ensure that CLI examples remain prominent and up-to-date for Linux parity.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell section is given equal prominence despite being Windows-centric. The CLI example is cross-platform, but PowerShell is Windows-first and may not be available or commonly used on Linux/macOS. The page does not provide Linux/macOS-specific shell examples (e.g., Bash), but the CLI example is sufficient for those platforms.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a note clarifying that PowerShell examples are primarily for Windows users, and that Azure CLI works on all platforms.
- Consider listing the CLI example first to emphasize cross-platform compatibility.
- Optionally, provide Bash scripting examples for advanced Linux users.
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 PowerShell (a Windows-centric tool) is given equal prominence and a dedicated tab. The CLI example is shown first, but the PowerShell section may imply parity between Windows and Linux tooling, even though PowerShell is less commonly used on Linux/macOS. No Linux/macOS-specific shell examples (e.g., Bash) are provided, but the Azure CLI is cross-platform.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a note indicating PowerShell is primarily for Windows users, though available on Linux/macOS.
- Consider including Bash script examples for Linux users, or explicitly state that Azure CLI commands work in Bash/zsh/fish shells.
- Ensure that CLI instructions are clearly marked as the recommended approach for non-Windows platforms.
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
While the documentation is focused on Azure Disk Encryption for Linux VMs and provides both Azure CLI and PowerShell examples, there is a notable tendency to mention PowerShell cmdlets and workflows first or more prominently in several sections. PowerShell is a Windows-centric tool, and its usage is emphasized alongside CLI, sometimes with more detailed scripts and explanations. In some places, PowerShell is referenced before CLI, and backup/restore instructions often cite PowerShell cmdlets before CLI equivalents. However, Linux users are not blocked from completing any tasks, as CLI examples are present for all major operations.
Recommendations
- Ensure CLI examples are presented before or alongside PowerShell examples, especially in introductory and critical workflow sections.
- Where PowerShell scripts are shown in detail, provide equally detailed CLI command sequences and context.
- Clarify that PowerShell can be run cross-platform (including on Linux/macOS), but highlight CLI as the native choice for Linux users.
- Review backup/restore and prerequisite instructions to ensure CLI commands are not omitted or relegated to secondary status.
- Add explicit guidance for Linux users on choosing between CLI and PowerShell, mentioning that CLI is typically pre-installed or easier to set up on Linux.
Virtual Machines
Migrate Managed image to Compute gallery
...igration/migration-managed-image-to-compute-gallery.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides migration steps for both Linux and Windows VMs, and offers examples for Portal, Azure CLI, and PowerShell. However, PowerShell examples are included alongside CLI, and the CLI example uses backticks (`) for line continuation, which is a Windows shell convention. The PowerShell section is given equal prominence, and the CLI example does not clarify Linux/macOS usage (e.g., line continuation, authentication differences). There is a slight Windows-first bias in example formatting and tool choice, but Linux users can complete the task using the CLI.
Recommendations
- Clarify CLI example line continuation for Linux/macOS (use '\' instead of '`').
- Add explicit notes or examples for Linux/macOS shell usage in CLI section.
- Consider mentioning Bash or Cloud Shell as alternatives for Linux/macOS users.
- Ensure CLI examples are cross-platform and avoid Windows-specific syntax.
- Add a note that PowerShell is available cross-platform, but clarify usage differences if any.
Virtual Machines
Quickstart - Create a Linux VM in the Azure portal
...articles/virtual-machines/linux/quick-create-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides instructions for connecting to the VM via SSH, mentioning Windows/PowerShell users before Linux/macOS users. However, it does include explicit steps for both platforms and offers Linux-specific package installation instructions. There are no Windows-only tools or missing Linux examples.
Recommendations
- Present Linux/macOS instructions before Windows/PowerShell, or group them equally.
- Consider explicitly mentioning macOS alongside Linux when referring to Bash prompts.
- Ensure screenshots and UI references are platform-neutral or include notes for platform-specific differences if any.
Virtual Machines
MSP Feature Configuration
...l-machines/metadata-security-protocol/configuration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation displays mild Windows bias, notably by referencing Windows in key configuration details before Linux, and by using Windows-centric naming in examples (e.g., 'GPAWinVM'). The automatic GPA installation/uninstallation is described only for Windows, and the VM examples use Windows naming conventions. However, Linux is supported throughout, with audit log paths and security behaviors described for both OS families.
Recommendations
- Clarify that GPA installation/uninstallation is supported for Linux VMs, or explicitly state any differences.
- Use neutral example names (e.g., 'GPA-VM') instead of 'GPAWinVM' to avoid implying Windows exclusivity.
- When describing configuration properties, mention Linux and Windows behaviors equally, or note any OS-specific differences.
- Provide explicit Linux CLI or scripting examples (e.g., Azure CLI, Bash) alongside PowerShell or Windows-centric instructions if referenced elsewhere.
- Ensure that any automation or troubleshooting steps are described for both Linux and Windows.
Virtual Machines
Move a maintenance configuration to another Azure region
...tual-machines/move-region-maintenance-configuration.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for creating, assigning, and deleting maintenance configurations, but PowerShell is mentioned first in each step. This ordering subtly prioritizes Windows tooling and may imply PowerShell is the primary or preferred method, which can create friction for Linux/macOS users who typically use Azure CLI or shell scripting. No Linux-specific examples or shell scripts are provided, but CLI coverage is present.
Recommendations
- Present Azure CLI instructions before PowerShell, or list both together without implied priority.
- Explicitly mention that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Add bash/shell script examples for common tasks to further support Linux users.
- Clarify that all steps can be completed using Azure CLI on Linux/macOS.
Virtual Machines
InfiniBand driver extension - Azure Linux VMs
...al-machines/extensions/hpc-compute-infiniband-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation is focused on Linux VMs and provides Linux-centric information and examples. However, there is a notable presence of PowerShell examples for deployment and management tasks, which are traditionally Windows tools. While Azure PowerShell is cross-platform, its prominence may create friction for Linux users who typically prefer Bash or native Azure CLI. The documentation does mention an extension for Windows VMs, but does not prioritize Windows content or omit Linux examples.
Recommendations
- Provide Bash script examples for extension deployment and management, in addition to PowerShell and Azure CLI.
- Clarify that Azure PowerShell can be used on Linux/macOS, or recommend Azure CLI/Bash as the primary method for Linux users.
- Consider reordering examples to show Azure CLI or Bash first, as these are more native to Linux workflows.
- Explicitly mention cross-platform compatibility of PowerShell if it is to be used.
Virtual Machines
Project Flash - Advancing Azure Virtual Machine availability monitoring
.../blob/main/articles/virtual-machines/flash-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. References to scheduled events link specifically to the Windows documentation, and several cross-platform Azure features are described without explicit Linux or macOS examples or links. Activity log and resource graph references mention PowerShell and Azure CLI tabs, but do not provide Linux-specific guidance or highlight parity. There are no examples or guidance tailored for Linux VM monitoring scenarios, nor are Linux-specific troubleshooting or automation tools mentioned.
Recommendations
- Include links to both Windows and Linux scheduled events documentation when discussing early warning features.
- Add explicit examples or references for monitoring Linux VMs, such as using Bash, Azure CLI, or Linux-native tools.
- Ensure all referenced Azure features (Resource Graph, Activity Logs, Monitor) provide parity in example commands for Linux/macOS environments.
- Where PowerShell is mentioned, also provide equivalent Bash/Azure CLI commands for Linux users.
- Highlight any differences or considerations for Linux VM availability monitoring, such as OS-specific failure modes or integration points.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides parity for both Windows and Linux in terms of CLI and ARM template instructions. However, there is a mild Windows bias: PowerShell examples are included (which are Windows-centric), and in several places, Windows screenshots and links are presented before Linux equivalents. PowerShell is given as a primary scripting option, while Bash or Linux shell alternatives are not mentioned. The quickstart links list Windows before Linux. Screenshots for Windows installations are shown before Linux ones.
Recommendations
- Add Bash or shell script examples alongside PowerShell for Linux users.
- Alternate the order of Windows and Linux examples/screenshots to avoid implicit prioritization.
- Explicitly mention that PowerShell Core is cross-platform, or provide Linux-native scripting alternatives.
- Where possible, provide Linux-specific troubleshooting or validation steps, not just generic or Windows-first instructions.
Virtual Machines
Quickstart: Create a Linux VM cluster in Azure using Terraform
...rtual-machines/linux/quick-cluster-create-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented immediately after the CLI example, which is cross-platform. There are no explicit Linux shell examples (e.g., Bash), nor is there any mention of Linux-specific tooling or commands for verification. The rest of the documentation is neutral and focused on Terraform, which is cross-platform.
Recommendations
- Prioritize Azure CLI examples, as it is cross-platform and preferred for Linux/macOS users.
- Clearly indicate that Azure PowerShell is primarily for Windows users, and suggest Azure CLI for Linux/macOS.
- Add explicit Bash shell examples for verification steps, if relevant.
- Consider reordering the tabs to show Azure CLI first, and PowerShell second, with a note about platform compatibility.
Virtual Machines
Configure Event Hubs for VM watch
...ticles/virtual-machines/configure-eventhub-vm-watch.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. References to PowerShell and Windows tools are present before Linux equivalents, and examples or instructions for configuring VM watch often mention PowerShell and Windows paths first or exclusively. Linux-specific instructions are limited, and Linux users may need to infer steps or adapt Windows-centric instructions.
Recommendations
- Provide explicit Linux and macOS examples alongside Windows/PowerShell examples, especially for configuration and troubleshooting steps.
- List Linux and Windows instructions in parallel tabs or sections, ensuring equal prominence.
- Include CLI/bash commands for Linux users where PowerShell is referenced.
- Expand troubleshooting and log location guidance for Linux and macOS, not just Windows.
- Ensure screenshots and UI references are platform-neutral or include Linux-specific visuals where relevant.