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 176-200 of 818 flagged pages
Virtual Machines
Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment.
.../includes/virtual-machines-disks-shared-limitations.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation repeatedly references Windows Server Failover Cluster as the only clustering solution discussed, with multiple links to Windows-specific documentation. There is no mention of Linux clustering solutions (such as Pacemaker or Corosync), nor any examples or guidance for Linux users. This creates a bias toward Windows environments and may leave Linux users without clear guidance for implementing shared disks in their scenarios.
Recommendations
- Include references to Linux clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
- Add examples or links to documentation for configuring shared disks in Linux-based clusters.
- Clarify whether the listed limitations apply only to Windows environments or also to Linux, and provide parity in guidance.
- Ensure that both Windows and Linux scenarios are addressed in all relevant sections.
Create Pull Request
Virtual Machines
Use infrastructure automation tools
...articles/virtual-machines/infrastructure-automation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation generally covers both Linux and Windows automation tools, but there are several instances of Windows bias: Windows examples and tools (e.g., PowerShell DSC, Chef on Windows, Puppet on Windows) are sometimes mentioned first or exclusively, while Linux equivalents are missing or less emphasized. Some sections provide only Windows-focused links or examples, and Windows-specific tooling (PowerShell, Windows templates) is highlighted before Linux alternatives.
Recommendations
- Ensure every Windows example or link has a Linux equivalent, especially in sections like Chef and Puppet where only Windows instructions are provided.
- Present Linux and Windows examples side-by-side or alternate which is shown first to avoid 'windows_first' bias.
- Expand the Chef section to include Linux installation and VM creation guides, not just Windows.
- For Puppet, include links to Linux installation and usage, not just Windows.
- Where PowerShell is referenced, also mention Bash/CLI alternatives for Linux users.
- Review all 'Learn how to' lists to ensure parity between Linux and Windows instructions.
Virtual Machines
Prepare Linux for imaging
...ticles/virtual-machines/linux/create-upload-generic.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is focused on Linux preparation for Azure imaging, but it exhibits some Windows bias in the sections discussing VHD conversion and resizing. Windows tools (Hyper-V Manager, PowerShell cmdlets like Convert-VHD and Resize-VHD) are mentioned first and in detail, while Linux alternatives (qemu-img, vbox-manage) are referenced secondarily or as workarounds. The initial guidance for disk conversion and resizing assumes access to Windows environments before suggesting Linux tools. However, the majority of the technical instructions and examples are Linux-centric.
Recommendations
- Present Linux tools (qemu-img, vbox-manage) alongside or before Windows tools when discussing VHD conversion and resizing.
- Provide explicit, step-by-step Linux examples for all disk operations, not just as alternatives.
- Clarify that all required steps can be completed on Linux without needing Windows or Hyper-V.
- Add troubleshooting notes for Linux tools (e.g., qemu-img bugs, compatibility issues) in parity with Windows tool notes.
- Consider a dedicated section for Linux-only workflows to reinforce parity.
Virtual Machines
Create and upload a CentOS-based Linux VHD
...rticles/virtual-machines/linux/create-upload-centos.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily by referencing Hyper-V (a Windows virtualization tool) as the main method for creating and managing CentOS VHDs. Instructions for VM management (such as shutting down or connecting to the VM) are given using Hyper-V Manager, with no equivalent guidance for Linux-native virtualization platforms like KVM, QEMU, or VirtualBox. The conversion of disk formats is described using Hyper-V Manager or Windows PowerShell (`convert-vhd`), while Linux alternatives (e.g., qemu-img) are not mentioned. This creates friction for Linux/macOS users who may not have access to Hyper-V or Windows tools.
Recommendations
- Provide parallel instructions for common Linux virtualization platforms (KVM, QEMU, VirtualBox), including how to create, manage, and shut down VMs.
- Include Linux-native commands for converting disk formats (e.g., using `qemu-img` to convert raw to fixed VHD).
- Mention macOS-compatible tools and workflows where relevant.
- Present Windows and Linux options side-by-side, or clearly indicate alternatives for non-Windows users.
- Clarify that Hyper-V is one option among several, and link to resources for Linux-based virtualization.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page for creating and uploading an Ubuntu Linux VHD in Azure exhibits a moderate Windows bias. Hyper-V (a Windows-only virtualization solution) is presented as the primary example for creating VHDs, with links to Windows documentation and PowerShell cmdlets (Convert-VHD) for disk conversion. There are no equivalent instructions or references for Linux-based tools (such as qemu-img, VirtualBox, or KVM) for creating or converting VHDs, nor are Linux workflows described for these steps. Windows tools and procedures are mentioned first and exclusively in critical steps, which may create friction for Linux/macOS users.
Recommendations
- Include instructions and examples for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, KVM).
- Provide links to Linux documentation for virtualization and disk conversion.
- Present Linux and Windows options side-by-side, or prioritize Linux tools given the Ubuntu/Linux focus of the guide.
- Clarify that Hyper-V is just one option and explicitly mention alternatives for non-Windows users.
Virtual Machines
Creating and configuring a key vault for Azure Disk Encryption
...es/virtual-machines/linux/disk-encryption-key-vault.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples and resources, but PowerShell (a Windows-centric tool) is featured equally alongside CLI, despite the article's Linux focus. PowerShell scripts and quickstarts are referenced as primary resources, and PowerShell authentication is described in detail. The CLI and PowerShell scripts are listed together, but PowerShell is not deprioritized or marked as Windows-only, which may confuse Linux users. There is no explicit omission of Linux examples, but the parity between CLI and PowerShell may create friction for Linux users unfamiliar with PowerShell.
Recommendations
- Prioritize Azure CLI examples and quickstarts for Linux-focused documentation, listing CLI before PowerShell.
- Clearly indicate that PowerShell is primarily a Windows tool and may require additional setup on Linux.
- Add explicit notes or sections for Linux users, recommending Azure CLI as the preferred tool.
- Where PowerShell scripts are referenced, provide equivalent Bash/CLI scripts or clarify their platform compatibility.
- Review and update links to ensure Linux users are directed to CLI resources first.
Virtual Machines
Azure Disk Encryption with Microsoft Entra App Linux IaaS VMs (previous release)
...es/virtual-machines/linux/disk-encryption-linux-aad.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides extensive PowerShell examples and references to Windows-centric tools (such as PowerShell cmdlets and Windows-specific flags), even in sections focused on Linux VMs. PowerShell is presented as a primary method for disk encryption tasks, sometimes before or alongside Azure CLI and ARM templates. There are references to Windows-specific options (e.g., '-Windows' flag in Set-AzVMOSDisk), and some steps (such as disabling encryption) mention Windows VMs in Linux contexts. Linux-native command-line examples (bash, shell scripts) are minimal or absent, and the use of PowerShell for Linux VM management may not be natural for Linux administrators.
Recommendations
- Provide bash/shell script examples for Linux VM management tasks alongside PowerShell and CLI.
- Remove or clarify Windows-specific flags and references in Linux-focused sections.
- Ensure Linux-native tooling (e.g., bash, cloud-init, Linux utilities) is covered where appropriate.
- Present Azure CLI and ARM template methods before PowerShell in Linux documentation, as CLI is more cross-platform.
- Review and correct any references to Windows VMs in Linux-specific instructions.
- Highlight that PowerShell Core is cross-platform, but also offer alternatives for users who prefer native Linux tools.
Virtual Machines
Azure Disk Encryption with Microsoft Entra app prerequisites (previous release)
...virtual-machines/linux/disk-encryption-overview-aad.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page, while focused on Azure Disk Encryption for Linux VMs, contains notable Windows bias. Windows-specific tools (BitLocker, registry edits, Group Policy) are described in detail, including example registry changes and policy settings, but there are no equivalent Linux-specific examples or troubleshooting steps. Windows instructions are presented first and in more depth, while Linux-specific prerequisites and configuration details are largely omitted or deferred to other linked articles.
Recommendations
- Add Linux-specific troubleshooting steps and configuration examples, such as SELinux/AppArmor considerations, disk encryption tools (e.g., dm-crypt/LUKS), and relevant system settings.
- Provide Linux command-line examples for network configuration and key vault connectivity (e.g., using curl, iptables, or firewall-cmd).
- Include parity for Linux in the 'Group Policy' section by discussing relevant Linux access control or security policy mechanisms.
- Ensure that Linux instructions are presented with equal prominence and detail as Windows instructions, especially in sections about prerequisites and common issues.
- Where Windows registry or Group Policy changes are shown, provide analogous Linux configuration steps or explicitly state when they are not applicable.
Virtual Machines
Azure Disk Encryption sample scripts
...rtual-machines/linux/disk-encryption-sample-scripts.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is for Azure Disk Encryption on Linux VMs, but almost all automation and scripting examples use PowerShell cmdlets and scripts, which are Windows-centric. Key operations such as listing encrypted VMs, uploading VHDs, and managing secrets in Key Vault are only shown with PowerShell, with no Bash, Azure CLI, or Linux-native alternatives. Even when Linux VM configuration is described, the upload and management steps revert to PowerShell. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell examples, especially for listing encrypted VMs, uploading VHDs, and managing Key Vault secrets.
- Include Bash script examples for common tasks, such as preparing and uploading encrypted VHDs.
- Mention and demonstrate cross-platform tools (e.g., azcopy for VHD uploads) where possible.
- Order examples so that Linux-native methods (CLI/Bash) are shown before or alongside PowerShell.
- Clarify which steps require PowerShell and suggest alternatives for Linux/macOS users.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs, but PowerShell instructions are given before Azure CLI, despite CLI being more native to Linux. The PowerShell section is more extensive, with detailed examples and screenshots, while the CLI section, though comprehensive, comes after. There is no evidence of exclusive use of Windows tools, and Linux OS-level commands are included at the end. However, the ordering and emphasis may create friction for Linux users who are less likely to use PowerShell.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more commonly used on Linux.
- Clearly indicate that PowerShell commands are optional and primarily for users who have installed PowerShell on Linux.
- Expand Linux OS-level command examples (e.g., lsblk, cryptsetup) to match the detail given to PowerShell/CLI sections.
- Add a summary table comparing all methods, highlighting which are native to Linux.
- Consider removing or de-emphasizing PowerShell for Linux-specific documentation unless there is a strong use case.
Virtual Machines
How to Connect to the Azure Image Builder build VM
...al-machines/linux/image-builder-connect-to-build-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools and terminology (RDP, WinRM, Reset Password blade) are mentioned first or exclusively in several sections. Examples and links for connecting to Windows VMs are often given before Linux equivalents, and some instructions (such as password reset) reference Windows-centric UI without clarifying Linux differences. Linux-specific connection methods and troubleshooting steps are less detailed or referenced after Windows options.
Recommendations
- Provide explicit Linux examples and instructions alongside Windows ones, especially for credential management and connection steps.
- Clarify differences in the Azure portal UI for Linux VMs (e.g., password reset process, SSH key management).
- Ensure that links to Linux documentation are presented with equal prominence and order as Windows links.
- Include Linux-specific troubleshooting tips (e.g., SSH connectivity, cloud-init logs) where relevant.
- Avoid using Windows terminology (e.g., RDP, WinRM) as the default; always mention SSH for Linux first or equally.
Virtual Machines
Azure VM Image Builder service DevOps task (preview)
...es/virtual-machines/linux/image-builder-devops-task.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (PowerShell) and terminology are frequently mentioned, often before or more prominently than Linux equivalents. Windows examples (e.g., PowerShell commands, directory paths) are shown first in several sections, and some customization features (like Windows Update) are described only for Windows. Linux examples are present but sometimes less detailed or appear after Windows instructions. There are also references to Windows-only limitations (e.g., lack of support for Windows Restart), but Linux workarounds are not always equally emphasized.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which comes first to avoid Windows-first ordering.
- Expand Linux-specific instructions and examples to match the detail given for Windows, especially in customization and artifact handling.
- Clearly indicate when features are Windows-only and provide Linux alternatives or workarounds where possible.
- Include more bash or shell script examples for Linux users, especially in sections where PowerShell is heavily featured.
- Avoid using Windows terminology (e.g., 'C:\buildArtifacts') without immediately providing the Linux equivalent.
Virtual Machines
Troubleshoot Azure VM Image Builder
...s/virtual-machines/linux/image-builder-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools (PowerShell, WinRM, Sysprep) are frequently mentioned, often with detailed examples and troubleshooting steps. PowerShell commands are shown alongside Azure CLI, but Windows-specific patterns (e.g., Sysprep, Windows Update, restart customizers) receive more attention and troubleshooting coverage. Linux equivalents (waagent, SSH, shell scripting) are present but less detailed, and sometimes appear after Windows instructions. Some troubleshooting sections and examples are Windows-centric, with Linux guidance either brief or missing.
Recommendations
- Ensure Linux troubleshooting steps are as detailed as Windows ones, especially for common errors and customizations.
- Provide Linux-first or parallel examples for all CLI and scripting instructions, not just PowerShell.
- Expand Linux-specific error messages and solutions (e.g., waagent failures, SSH connectivity, Linux file permissions) to match the coverage of Windows topics.
- Balance the order of presentation so Linux and Windows instructions appear together or alternate, rather than Windows-first.
- Include more Linux shell script samples and troubleshooting logs, especially for customization and deprovisioning steps.
- Reference Linux-specific documentation and support resources as prominently as Windows ones.
Virtual Machines
Run scripts in a Linux VM in Azure using managed Run Commands
...articles/virtual-machines/linux/run-command-managed.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page, while focused on Linux VMs, contains several instances of Windows bias. PowerShell examples and tooling are heavily featured, with many advanced scenarios (such as output streaming, parameter passing, and SAS token generation) described only with PowerShell cmdlets and Windows-centric tools. REST and ARM template examples use PowerShell scripts as sample payloads, and some notes reference Windows-specific behaviors before Linux equivalents. There are missing Linux CLI or bash-native examples for advanced features, and PowerShell is often presented before or instead of Linux alternatives.
Recommendations
- Provide equivalent Azure CLI or bash script examples for all advanced scenarios currently shown only in PowerShell (e.g., output streaming, parameter passing, SAS token generation).
- Where REST or ARM template payloads use PowerShell scripts, also show examples with bash scripts.
- Clarify when instructions or notes are Windows-specific and provide Linux-specific guidance in parallel.
- Ensure Linux tools and patterns (e.g., az CLI, bash scripting) are presented before or alongside Windows/PowerShell examples, especially in Linux-focused documentation.
- Add instructions for generating SAS tokens using Azure CLI or portal for Linux users.
Virtual Machines
Create and upload a Red Hat Enterprise Linux VHD for use in Azure
...les/virtual-machines/linux/redhat-create-upload-vhd.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. The prerequisites and initial instructions reference Hyper-V Manager and link to Windows documentation first, with Hyper-V-specific steps appearing before KVM, VMware, and Kickstart. Windows/Hyper-V tools and patterns (e.g., Hyper-V Manager, convert-vhd cmdlet) are mentioned before Linux alternatives (qemu-img). However, the page does provide detailed Linux-centric instructions for KVM, VMware, and Kickstart, and includes Linux tooling for image conversion and configuration.
Recommendations
- In the prerequisites, mention KVM, VMware, and Kickstart options alongside Hyper-V, with links to their respective documentation.
- Provide Linux-first instructions or parallel instructions for common tasks (e.g., converting disk formats) rather than referencing Windows/Hyper-V tools first.
- Where possible, avoid assuming Hyper-V as the default workflow; present all supported hypervisors equally.
- Add explicit guidance for Linux/macOS users in sections that currently reference Windows tools or documentation.
- Ensure that all steps (including image conversion and VM creation) have clear Linux/macOS equivalents and links.
Virtual Machines
Run scripts in an Azure Linux VM
...n/articles/virtual-machines/linux/run-scripts-in-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page is focused on Linux VMs but repeatedly references Windows tools and patterns, such as PowerShell and Windows-specific installation instructions. Examples and descriptions often mention PowerShell scripts and Windows capabilities before or alongside Linux equivalents, but do not provide Linux-specific examples or highlight Linux-native tools. The Hybrid Runbook Worker section is especially Windows-centric, referencing PowerShell and requiring a manual installation link that points to Windows instructions, with no Linux installation guidance.
Recommendations
- Provide explicit Linux script examples (e.g., Bash, Python) for each feature, especially for Hybrid Runbook Worker.
- Ensure installation instructions for Hybrid Runbook Worker include Linux steps and links.
- List Linux-native tools and patterns first in sections focused on Linux VMs.
- Clarify which features are Linux-compatible and provide parity in documentation structure and detail.
- Reduce emphasis on PowerShell in Linux contexts; highlight Bash and other Linux scripting languages.
Virtual Machines
Create shared Azure Linux VM images using the portal
...rticles/virtual-machines/linux/shared-images-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is focused on Linux VM images and uses the Azure Portal for all steps, which is cross-platform. However, in the 'Before you begin' section, it references a PowerShell-based tutorial for creating a managed image and links to a snapshot guide under a Windows directory, without mentioning or linking to equivalent Linux CLI or Bash instructions. No Linux-specific command-line examples are provided, and Windows/PowerShell resources are referenced first and exclusively.
Recommendations
- Add links to Linux-specific guides for creating managed images and snapshots, such as those using the Azure CLI or Bash.
- Reference Linux CLI examples alongside or before PowerShell/Windows examples when discussing prerequisites.
- Ensure that all referenced tutorials and guides have Linux equivalents and are clearly labeled.
- Consider including a short section on how to perform prerequisite steps using Linux tools (e.g., Azure CLI) directly in the documentation.
Virtual Machines
Advanced Configuration for MSP
...s/metadata-security-protocol/advanced-configuration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides a Windows-specific example for process identity matching (WinPA) with Windows paths and process names, but does not offer a Linux equivalent. Windows process metadata (exePath, processName, userName) is shown in detail, while Linux examples are limited to a single earlier snippet and not referenced in the main schema expansion. Windows tools and conventions (e.g., C:\Windows paths, SYSTEM user) are mentioned exclusively in the WireServer example, and Windows examples are presented before or instead of Linux ones.
Recommendations
- Add equivalent Linux/macOS examples for process identity matching, such as using /usr/bin/nginx, processName: nginx, userName: root or www-data.
- Ensure schema expansions include both Windows and Linux/macOS scenarios side-by-side.
- Explicitly mention how to obtain process metadata on Linux/macOS (e.g., using ps, /proc, or systemd conventions).
- Avoid using Windows paths and usernames exclusively; provide cross-platform context.
- If Windows-specific tools or patterns are referenced, provide Linux/macOS alternatives.
Virtual Machines
Maintenance Configurations for Azure Virtual Machines using Bicep
...s/virtual-machines/maintenance-configurations-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides only a Windows/Powershell example for Bicep template deployment, using Windows-style paths (e.g., .\ds.bicep) and does not mention or show Linux/macOS CLI equivalents. There is no explicit Linux/macOS example for running the az deployment command, nor any notes about cross-platform usage. The documentation implicitly assumes a Windows environment for command execution, which may cause confusion or friction for Linux/macOS users.
Recommendations
- Provide both Windows and Linux/macOS CLI examples for az deployment group create, using appropriate path separators (e.g., ./ds.bicep for Linux/macOS).
- Add a note clarifying that the Azure CLI works cross-platform and that path syntax differs between Windows (\) and Linux/macOS (/).
- Consider listing Linux/macOS examples first or side-by-side with Windows examples to reinforce parity.
- Explicitly mention that all Bicep templates and Azure CLI commands are platform-agnostic, and provide troubleshooting tips for common Linux/macOS issues (e.g., file permissions, shell differences).
Virtual Machines
Manage Virtual Machine restore points
...ain/articles/virtual-machines/manage-restore-points.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation exclusively provides Azure PowerShell examples for all command-line operations, with no mention of Linux/macOS alternatives such as Azure CLI, Bash, or REST API usage. Windows-centric tools and syntax are used throughout, and no Linux-specific guidance or parity is offered. This creates friction for users on non-Windows platforms who may not have PowerShell installed or prefer native Linux tools.
Recommendations
- Add equivalent Azure CLI examples for each PowerShell command.
- Include Bash scripting examples where appropriate.
- Explicitly mention that PowerShell is cross-platform, but clarify installation steps for Linux/macOS users.
- Provide REST API request examples for advanced users.
- Ensure that Linux/macOS users are not required to install PowerShell unless necessary.
Virtual Machines
Overview of Azure Disk Storage
...in/articles/virtual-machines/managed-disks-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page generally covers Azure managed disks for both Linux and Windows VMs, but there are several instances of Windows bias. Windows terminology, tools, and links are often presented first or exclusively, such as references to Sysprep, MBR/GPT partitioning with Windows links, and PowerShell articles. Some sections, like image creation and partitioning, link only to Windows-specific resources or mention Windows tools before Linux equivalents. Linux examples and links are present but sometimes secondary or missing.
Recommendations
- Ensure all example links (e.g., image creation, partitioning) include both Windows and Linux equivalents, or provide a neutral overview page.
- When mentioning tools or procedures (e.g., Sysprep, MBR/GPT), include Linux alternatives (e.g., cloud-init, parted, gdisk) and link to relevant Linux documentation.
- Present Linux and Windows examples side-by-side or in parallel, rather than listing Windows first or exclusively.
- Review all cross-references to ensure Linux parity, especially in deep links and how-to guides.
- Clarify terminology to be OS-neutral where possible (e.g., avoid drive letter references without Linux device path equivalents).
Virtual Machines
Frequently Asked Questions About MSP
...les/virtual-machines/metadata-security-protocol/faq.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation displays a Windows-first bias in its explanation of provisioning and agent installation. It references the Windows philosophy as the default model and does not provide Linux-specific examples or guidance for checking MSP status or installing the Guest Proxy Agent (GPA). Windows tools and patterns are mentioned as the baseline, while Linux alternatives are discussed only in terms of limitations. There are no Linux command-line examples or instructions, and the guidance for Linux users is limited to stating what is not possible.
Recommendations
- Provide explicit Linux command-line examples (e.g., using curl, jq, or Azure CLI) for checking MSP status and component health.
- Offer step-by-step instructions for installing and enabling GPA on Linux VMs, including supported distributions and package managers.
- Discuss Linux-specific patterns for VM provisioning and agent management, and clarify any differences from Windows workflows.
- Ensure that Linux guidance is presented alongside Windows guidance, not only as an exception or limitation.
- Include troubleshooting steps and common issues for Linux users.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows troubleshooting steps and service names are often presented first, and Windows-specific tools (such as 'sc query' and service names like 'eBPFCore', 'NetEbpfExt') are described in detail. In some sections, Linux instructions are less detailed or missing, and Windows command examples are shown without Linux equivalents. Linux users may need to infer or search for analogous commands and troubleshooting steps.
Recommendations
- Provide Linux command equivalents for all Windows commands (e.g., replace 'sc query' with 'systemctl status' or 'lsmod' for Linux).
- Present Linux and Windows troubleshooting steps in parallel, or alternate which OS is shown first.
- Expand Linux troubleshooting sections to match the detail provided for Windows, including explicit error messages, log file locations, and service management commands.
- Include Linux-specific examples for checking service status, kernel modules, and log analysis.
- Clarify any OS-specific prerequisites and installation steps, and provide links to relevant Linux documentation.
Virtual Machines
Monitoring data reference for Azure Virtual Machines
...main/articles/virtual-machines/monitor-vm-reference.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows moderate Windows bias. Several log tables and data collection methods are Windows-specific (e.g., Windows Event Log, IIS logs, Windows DNS servers, Windows Security Events, Windows Firewall), and these are described before or without equivalent Linux examples. While Linux is mentioned (e.g., Syslog, Linux Daemons), Windows tools and terminology appear more frequently and are often listed first. Some data collection methods and log tables are exclusively for Windows, with no Linux alternatives or examples provided.
Recommendations
- Add equivalent Linux examples and references for each Windows-specific log table and data collection method (e.g., provide examples for collecting Linux audit logs, firewall logs, and DNS events).
- Ensure Linux and macOS terminology and tools are mentioned alongside Windows tools, not just as secondary notes.
- Where possible, reorder tables and examples so that Linux and Windows are presented with equal prominence.
- Include explicit guidance for Linux/macOS users in sections that currently only mention Windows tools or workflows.
Virtual Machines
Convert Audit Logs to an Allowlist
...ecurity-protocol/other-examples/audit-logs-to-rules.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. Windows-specific tools (PowerShell, .exe utilities) are featured prominently and in greater detail than Linux equivalents. Windows examples and terminology (e.g., PowerShell commands, .exe files, Windows paths) are presented first and in more depth, while Linux instructions are less detailed or absent (e.g., no Bash or shell scripting examples for Linux users, no mention of Linux-native automation tools). The allowlist generator tool is only available as a Windows executable, with no Linux alternative provided. Sample identities and rules are overwhelmingly Windows-centric, with little coverage of Linux processes or users.
Recommendations
- Provide Linux-native examples for all major steps, including shell (Bash) or Python scripts for resource creation and management.
- Offer a cross-platform or Linux-compatible version of the allowlist generator tool, or document manual log parsing methods for Linux.
- Balance sample identities and rules to include Linux processes and users, not just Windows executables.
- Present CLI and ARM template methods before or alongside PowerShell, emphasizing cross-platform parity.
- Explicitly note any limitations or workarounds for Linux users where Windows-only tooling is referenced.