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 751-775 of 818 flagged pages
Virtual Machines Copy a snapshot to a new region ...ines/disks-copy-incremental-snapshot-across-regions.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for copying snapshots, but the PowerShell section is detailed and includes installation instructions, which may suggest a Windows-centric approach. The CLI examples use Bash syntax, which is cross-platform, but there are no explicit Linux/macOS-specific notes or troubleshooting tips. The manual copy section references .NET sample code, which is more common on Windows. There are no examples or guidance for Linux-specific tools or shell environments beyond Bash, nor any mention of macOS.
Recommendations
  • Add explicit Linux/macOS troubleshooting notes for Azure CLI usage (e.g., common permission issues, path differences).
  • Include example scripts using native Linux tools or environments (e.g., zsh, fish) if relevant.
  • Provide parity in installation instructions for Azure CLI and PowerShell on Linux/macOS.
  • Reference or provide sample code in languages popular on Linux/macOS (e.g., Python, Go) for manual copy operations.
  • Clarify that Bash examples work on Linux/macOS and Windows (WSL, Git Bash), and mention any platform-specific caveats.
GitHub Create Pull Request
Virtual Machines Enable on-demand disk bursting ...ain/articles/virtual-machines/disks-enable-bursting.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page presents both Azure PowerShell and Azure CLI examples, but PowerShell (a Windows-centric tool) is listed before CLI. The PowerShell section is more detailed, and references to 'cmdlets' and the Azure PowerShell module are prominent. There is no explicit mention of Linux/macOS-specific shell environments or considerations, and no Bash or shell script examples are provided. The Azure portal and Resource Manager template sections are neutral, but the command-line guidance leans toward Windows tools and patterns.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and more common for Linux/macOS users.
  • Add explicit Bash/shell script examples or notes for Linux/macOS users where relevant.
  • Clarify that Azure CLI and Cloud Shell are fully supported on Linux/macOS, and provide links or instructions for installation on those platforms.
  • Avoid referring to command-line examples as 'cmdlets' when discussing CLI, as this is a PowerShell-specific term.
  • Consider adding a section or note about using these commands in Linux/macOS environments, including any differences or prerequisites.
GitHub Create Pull Request
Virtual Machines Migrate Standard HDD OS disks by September 08, 2028 ...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation mentions both Linux and Windows VMs as affected, but when listing tools and examples for identifying affected disks, it references Azure PowerShell before Azure CLI and provides a PowerShell command first. The Disk Storage Center is a GUI tool that is most familiar to Windows users. There are no explicit Linux/macOS shell examples (e.g., Bash), and the CLI example is shown after PowerShell, suggesting a Windows-first approach.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell examples.
  • Include Bash shell script examples for Linux/macOS users.
  • Clarify that Disk Storage Center is accessible via browser on any OS, not just Windows.
  • Add explicit guidance for Linux/macOS users, such as using Azure CLI in Bash or Zsh.
  • Ensure parity in troubleshooting and migration steps for both platforms.
GitHub Create Pull Request
Virtual Machines Enable end-to-end encryption using encryption at host - Azure portal - managed disks ...-machines/disks-enable-host-based-encryption-portal.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias by listing Azure PowerShell examples before Azure CLI, referencing PowerShell in links and resource samples, and providing links to Windows-specific guides before Linux equivalents. However, both PowerShell and CLI commands are shown, and the Azure portal instructions are platform-neutral.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or show CLI first for parity.
  • Ensure that resource/sample links include Linux/CLI equivalents, not just PowerShell/Windows.
  • Explicitly mention that all portal steps apply equally to Linux and macOS users.
  • Add a 'See also' section with Linux/macOS-specific resources or troubleshooting tips.
GitHub Create Pull Request
Virtual Machines Increase performance of Premium SSDs and Standard SSD/HDDs .../articles/virtual-machines/disks-enable-performance.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all tasks, with Azure CLI (Linux/macOS friendly) presented first. However, the PowerShell section is extensive and uses Windows-centric scripting patterns, and the page metadata and custom tags (e.g., 'devx-track-azurepowershell') suggest a PowerShell/Windows bias. There are no explicit Linux/macOS shell examples (e.g., bash-only or zsh-only), nor are there any references to Linux-specific tools or workflows. The Azure CLI examples are generic and do not leverage Linux-specific features or discuss Linux nuances. The Azure portal instructions are platform-neutral.
Recommendations
  • Add explicit bash/zsh examples for Linux/macOS users, especially for scripting and automation.
  • Include notes on Linux-specific considerations (e.g., environment variables, shell differences, file permissions) when using Azure CLI.
  • Balance PowerShell and CLI coverage by highlighting CLI as the cross-platform default and referencing PowerShell as an alternative for Windows users.
  • Remove or balance metadata/tags that suggest PowerShell as the primary approach.
  • Add troubleshooting or tips for Linux/macOS users where workflows may differ.
GitHub Create Pull Request
Virtual Machines Create an incremental snapshot ...ticles/virtual-machines/disks-incremental-snapshots.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for all major tasks, but consistently lists PowerShell examples immediately after CLI and gives them equal prominence. There are no Linux-specific shell examples (e.g., Bash-only idioms), and no mention of Linux-native tools or patterns. The CLI examples are generic and work on both Linux and Windows, but the PowerShell examples are Windows-specific and more verbose, potentially giving the impression of Windows as a first-class platform. No explicit Linux bias or missing Linux examples, but the parity could be improved.
Recommendations
  • Add explicit Bash shell examples where appropriate, especially for scripting tasks, to demonstrate Linux-native usage.
  • Clarify in introductory sections that Azure CLI commands work identically on Linux, macOS, and Windows.
  • Consider listing CLI examples before PowerShell, and labeling PowerShell as Windows-centric.
  • If possible, mention Linux tools (e.g., jq for JSON parsing) or patterns that Linux users might use in conjunction with Azure CLI.
  • Add a note that PowerShell Core is available cross-platform, but most users on Linux will use Bash with Azure CLI.
GitHub Create Pull Request
Virtual Machines Convert a disk from LRS to ZRS ...ain/articles/virtual-machines/disks-migrate-lrs-zrs.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Azure Portal instructions first, which are platform-neutral, but then lists Azure PowerShell before Azure CLI in all code example sections. PowerShell is a Windows-centric tool, while Azure CLI is cross-platform. No Linux/macOS-specific tools or shell examples are provided, and PowerShell is given precedence over CLI, which may create friction for Linux/macOS users.
Recommendations
  • List Azure CLI examples before Azure PowerShell in each section, as CLI is cross-platform and more familiar to Linux/macOS users.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide shell-specific notes where relevant.
  • Consider including bash or shell script examples for common operations, especially in migration scenarios.
  • Add a brief note about PowerShell Core availability on Linux/macOS if PowerShell examples are retained.
  • Ensure links and references (such as 'Find and delete unattached disks') do not point only to Windows-specific pages.
GitHub Create Pull Request
Virtual Machines Change the performance of Azure managed disks ...n/articles/virtual-machines/disks-performance-tiers.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell, but PowerShell (a Windows-centric tool) is given equal prominence and detail as Azure CLI. The use of PowerShell and references to its installation may create friction for Linux/macOS users, as PowerShell is less commonly used or pre-installed on those platforms. The documentation does not show explicit Linux shell examples (e.g., bash), and the ordering of examples sometimes places PowerShell before CLI. There are no Linux-specific commands or troubleshooting notes, and the portal instructions are platform-neutral.
Recommendations
  • Clearly indicate that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
  • Provide bash-specific examples or notes for Linux users (e.g., variable syntax differences).
  • Add troubleshooting notes for common Linux/macOS issues (e.g., CLI installation, environment variables).
  • Consider listing Azure CLI examples before PowerShell, or grouping by platform relevance.
  • Explicitly mention that PowerShell is available on Linux/macOS, but may require installation.
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias. PowerShell and Windows-centric links are mentioned first in several sections, and references to custom RBAC roles point to PowerShell-based instructions. While CLI and Linux alternatives are present, they are often listed second or less prominently. The page also uses Windows/PowerShell terminology and links before Linux/CLI equivalents.
Recommendations
  • Present CLI/Linux examples and links alongside or before Windows/PowerShell ones.
  • Ensure references to custom roles include both PowerShell and CLI/ARM template methods, not just PowerShell.
  • Use neutral language when referring to tools (e.g., 'Azure CLI or PowerShell' instead of 'PowerShell').
  • Add explicit Linux/macOS instructions where only Windows/PowerShell is referenced.
  • Review linked articles to ensure Linux parity in step-by-step guides.
GitHub Create Pull Request
Virtual Machines Ephemeral OS disks ...b/main/articles/virtual-machines/ephemeral-os-disks.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates mild Windows bias in several areas. Windows-specific details (such as page file placement) are discussed more thoroughly and appear before Linux equivalents. PowerShell is mentioned explicitly for customer-managed keys, with Linux CLI only referenced secondarily. Examples and sizing guidance for Windows images are presented before Linux images, and some sections (like page file placement) only discuss Windows patterns. There is a lack of parity in example depth and tool coverage for Linux/macOS users.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail, ideally side-by-side.
  • Include explicit Linux/macOS command-line examples (e.g., Bash, Azure CLI) wherever PowerShell is referenced.
  • Discuss Linux-specific disk/file system patterns (e.g., swap file placement) in sections that currently only mention Windows details.
  • When mentioning tools or deployment methods (CLI, PowerShell, Portal), list Linux/macOS options first or equally.
  • Add more Linux image sizing examples and clarify any differences in deployment or management for Linux VMs.
GitHub Create Pull Request
Virtual Machines Azure Linux VM Agent Overview ...in/articles/virtual-machines/extensions/agent-linux.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows Reference Windows First
Summary
The documentation is overwhelmingly Linux-focused, as expected for the Azure Linux VM Agent. However, there are minor instances of Windows bias: Windows tools (putty.exe) are referenced when discussing SSH key compatibility, and a link to a Windows VM deployment tutorial is included in the Ubuntu Cloud Images section. These references may distract or confuse Linux users, but do not prevent Linux users from completing tasks.
Recommendations
  • Remove or de-emphasize references to Windows tools (e.g., putty.exe) unless strictly necessary for cross-platform scenarios.
  • Replace or supplement Windows VM deployment tutorial links with Linux equivalents when discussing Linux-specific configuration.
  • Ensure that all example links and resources in Linux documentation are Linux-centric unless cross-platform context is required.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption for Linux ...es/virtual-machines/extensions/azure-disk-enc-linux.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is focused on Azure Disk Encryption for Linux and provides Linux-centric schema and deployment examples. However, in the warning section, the PowerShell cmdlet (Get-AzVMDiskEncryptionStatus) is mentioned before the Azure CLI equivalent (az vm encryption show), which may indicate a subtle Windows-first bias. The troubleshooting and support sections do not reference any Windows-specific tools or patterns, and the examples are all Linux-oriented.
Recommendations
  • List the Azure CLI command before the PowerShell cmdlet when providing cross-platform instructions, as CLI is natively available on Linux/macOS.
  • Explicitly state that both CLI and PowerShell are supported, and clarify which is recommended for Linux users.
  • Consider providing Bash script examples for common operations, as Linux users are more likely to use Bash than PowerShell.
  • Review other documentation links to ensure Linux tools and patterns are prioritized or at least equally represented.
GitHub Create Pull Request
Virtual Machines Chef extension for Azure VMs ...blob/main/articles/virtual-machines/extensions/chef.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation covers both Linux and Windows, but exhibits subtle Windows bias. The publisher value ('Chef.Bootstrap.WindowsAzure') and extension type ('ChefClient' for Windows) are mentioned before Linux equivalents. There is no explicit Linux-specific deployment example (e.g., for Windows, a PowerShell path is shown, but for Linux, only a CLI example is given). Troubleshooting paths are shown for both OSes, but Windows is listed second. The documentation references Windows-specific naming conventions and tools (e.g., publisher name, extension type), and does not provide parity in example scripts or commands for Linux (e.g., no bash deployment example, only Azure CLI).
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which OS is shown first.
  • Provide explicit Linux deployment examples using bash scripts, not just Azure CLI.
  • Clarify publisher and extension type values for both Linux and Windows in a more balanced way.
  • Include Linux-specific troubleshooting steps and file paths before or alongside Windows equivalents.
  • Review for any missing Linux-specific options or settings and document them if available.
GitHub Create Pull Request
Virtual Machines Azure Machine Configuration (guest configuration) ...les/virtual-machines/extensions/guest-configuration.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parity between Windows and Linux for all extension installation methods (Azure Portal, CLI, ARM/Bicep/Terraform templates), but consistently lists Windows examples and terminology before Linux equivalents in several places. The PowerShell section is included as a primary method, which is Windows-centric, while no Linux-native shell (e.g., Bash) examples are given. There is minor bias in ordering and tool emphasis, but Linux users are not blocked from completing any tasks.
Recommendations
  • Alternate the order of Windows and Linux examples, or present Linux examples first in some sections.
  • Include Bash or shell script examples for Linux users alongside PowerShell, especially for automation scenarios.
  • Explicitly mention that PowerShell Core is cross-platform if recommending PowerShell for Linux users.
  • Clarify in the portal instructions that both Windows and Linux extensions are available, and show screenshots or steps for both OS types.
  • Add a section or note highlighting any Linux-specific considerations or troubleshooting tips.
GitHub Create Pull Request
Virtual Machines Use Application Health extension with Azure Virtual Machines ...ticles/virtual-machines/extensions/health-extension.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Windows Examples First
Summary
The documentation consistently presents Windows-based examples before Linux equivalents, especially in REST API and PowerShell sections. PowerShell commands (Windows-centric) are given more prominence and detail, while Linux examples (using Azure CLI) are provided but always after Windows ones. The extension type naming is clear for both OSes, and Linux is supported throughout, but the ordering and emphasis favor Windows users.
Recommendations
  • Alternate the order of examples so that Linux (Azure CLI) examples are shown first in some sections.
  • Provide Bash script examples for Linux users where PowerShell scripts are shown for Windows.
  • Add explicit notes clarifying parity and equivalence between Windows and Linux steps.
  • Ensure troubleshooting and log file sections highlight Linux paths and commands as prominently as Windows ones.
  • Consider grouping OS-specific instructions together or using tabs for OS selection to reduce perceived bias.
GitHub Create Pull Request
Virtual Machines Qualys Cloud Agent Extension for Azure VMs ...ob/main/articles/virtual-machines/extensions/qualys.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides deployment instructions for both Windows and Linux VMs, generally maintaining parity between the two platforms. However, there is a notable emphasis on PowerShell as a deployment method, which is natively a Windows tool, even though a Linux PowerShell option is mentioned. In several sections, Windows instructions or links are listed before Linux equivalents, subtly prioritizing Windows. There are no missing Linux examples or exclusive use of Windows-only tools, but the ordering and tool emphasis reflect a mild Windows bias.
Recommendations
  • Provide Bash or native Linux CLI examples alongside PowerShell for Linux deployments, as PowerShell is less common on Linux.
  • Alternate the order of Windows and Linux instructions/links to avoid consistently listing Windows first.
  • Explicitly mention and provide examples for Linux-native automation tools (e.g., Bash scripts, cloud-init) in addition to Ansible, Chef, and Puppet.
  • Clarify when PowerShell is required on Linux and offer guidance for users who prefer native Linux tools.
GitHub Create Pull Request
Virtual Machines Enable InfiniBand on HPC VMs - Azure Virtual Machines | Microsoft Docs ...icles/virtual-machines/extensions/enable-infiniband.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Linux and Windows instructions for enabling InfiniBand, but there is a slight Windows bias in the VM extension section, where Azure PowerShell is mentioned as the primary tool for adding extensions, and Windows-specific extension details are given before Linux equivalents. Manual installation instructions are more detailed for Linux, but Windows users are directed to a download link without step-by-step guidance. The overall structure and examples are reasonably balanced, but Windows tools and patterns are referenced first or exclusively in some sections.
Recommendations
  • Include Azure CLI and portal instructions for adding VM extensions, not just PowerShell.
  • Present Linux and Windows extension details in parallel or with equal prominence.
  • Provide step-by-step manual installation instructions for Windows, similar to the Linux example.
  • Ensure Linux examples and tools are mentioned first or side-by-side with Windows equivalents.
GitHub Create Pull Request
Virtual Machines InfiniBand driver extension - Azure Linux VMs ...al-machines/extensions/hpc-compute-infiniband-linux.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation is focused on Linux VMs and provides both Azure CLI and PowerShell examples for deploying the InfiniBand driver extension. However, PowerShell examples are given equal prominence to Azure CLI, despite PowerShell being a Windows-centric tool. There are multiple PowerShell examples (including for VMSS), but no Linux-native command-line examples (e.g., Bash, cloud-init, or ARM template deployment via Linux tools). Troubleshooting also references PowerShell first, and the support section mentions MSDN (Windows-centric) forums. There is a brief mention of a Windows extension, but no Windows-specific instructions are present.
Recommendations
  • Prioritize Azure CLI examples over PowerShell, as Azure CLI is cross-platform and native to Linux/macOS.
  • Add Bash or shell script examples for ARM template deployment from Linux environments.
  • Clarify that PowerShell examples are optional and primarily for Windows users.
  • Reference Linux-specific support channels or forums in addition to MSDN.
  • Ensure troubleshooting steps highlight Azure CLI and Linux-native tools before PowerShell.
GitHub Create Pull Request
Virtual Machines Azure virtual machine extensions and features .../main/articles/virtual-machines/extensions/overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents both Linux and Windows information, but there is a subtle Windows bias. Windows tools (PowerShell) are mentioned alongside Azure CLI, and Windows troubleshooting is referenced first. In some sections, Windows examples or links are listed before Linux equivalents. The troubleshooting table is balanced, but the overall flow and tool mentions favor Windows slightly.
Recommendations
  • Alternate the order of Linux and Windows references throughout the documentation to avoid consistently listing Windows first.
  • Explicitly mention Linux tools (e.g., Bash, shell scripting) alongside PowerShell when discussing extension management.
  • Provide example commands for both Linux and Windows environments in relevant sections, or link to parity examples.
  • Ensure troubleshooting guidance is equally detailed and easy to find for both platforms.
  • Consider a platform-neutral introduction before splitting into OS-specific details.
GitHub Create Pull Request
Virtual Machines Project Flash - Advancing Azure Virtual Machine availability monitoring .../blob/main/articles/virtual-machines/flash-overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows-specific documentation first (e.g., scheduled events link points to a Windows path), and by omitting explicit Linux/macOS examples or references. No PowerShell-heavy or Windows-only tools are presented, but the lack of Linux parity in examples and links may create friction for non-Windows users.
Recommendations
  • Provide parallel Linux/macOS documentation links where Windows-specific links are given (e.g., scheduled events for Linux VMs).
  • Include example workflows or references for Linux VM monitoring, especially in sections discussing scheduled events and health events.
  • Ensure that cross-platform tools (Azure CLI, REST API) are mentioned and exemplified alongside any Windows-centric tools.
  • Review all linked articles to verify Linux parity and update this overview to explicitly mention Linux support where applicable.
GitHub Create Pull Request
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Recommended Windows Missing Mac Example
Summary
The documentation is generally cross-platform and includes Linux and Windows support throughout. However, there is a subtle Windows bias: Windows is listed first in several places, and Windows Server 2019 is specifically recommended for performance, while no Linux distribution is similarly highlighted. There are no macOS-specific examples or recommendations. Linux examples (e.g., lstopo output) are present, but Windows tools for topology are not mentioned, nor are Linux distributions recommended for performance.
Recommendations
  • List Linux and Windows equally or alternate order in tables and recommendations.
  • Recommend specific Linux distributions for performance, similar to Windows Server 2019.
  • Include macOS notes or clarify its support status, if relevant.
  • If recommending OS for performance, provide rationale and equivalent Linux guidance.
  • Add Windows-specific topology tools (e.g., Coreinfo, Windows System Information) if lstopo is shown for Linux.
GitHub Create Pull Request
Virtual Machines Azure VM Image Builder overview ...in/articles/virtual-machines/image-builder-overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Low Linux Example
Summary
The documentation generally presents both Windows and Linux support, but there are several areas where Windows tools, terminology, or examples are given first or exclusively. PowerShell is often mentioned before Azure CLI, and Windows-specific tools (e.g., Sysprep, Windows security baseline) are referenced without Linux equivalents. Linux examples and tools are present but sometimes secondary. There are no critical missing Linux instructions, but the overall tone and ordering subtly favor Windows.
Recommendations
  • Ensure Linux and Windows examples are always presented in parallel, with equal prominence.
  • When referencing Windows-specific tools (e.g., Sysprep, Windows security baseline), also mention Linux equivalents (e.g., waagent for deprovisioning, CIS Linux baselines).
  • Alternate the order of Windows and Linux examples/tabs to avoid always listing Windows first.
  • Expand references to Linux-specific configuration management tools (e.g., cloud-init, Ansible) where appropriate.
  • Provide direct links to Linux baseline templates or best practices, similar to the Windows baseline template link.
GitHub Create Pull Request
Virtual Machines Customer intent: As a system administrator, I want to restrict uploads and downloads for Azure managed disks using identity verification, so that I can enforce security policies and ensure only authorized users can access sensitive data. ...ines/includes/disks-azure-ad-upload-download-portal.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents PowerShell examples before Azure CLI examples in several sections, and references PowerShell as a primary method for role assignment and disk configuration. While Azure CLI is included, the ordering and emphasis may subtly favor Windows users, as PowerShell is a Windows-centric tool. No explicit Linux/macOS exclusion is present, but the pattern may create friction for non-Windows users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide installation links.
  • Add Bash or shell script examples where relevant.
  • Clarify that all steps can be performed on Linux/macOS using Azure CLI.
  • Avoid implying PowerShell is the default or preferred method unless necessary.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to expand virtual machine disks efficiently, so that I can manage storage capacity without downtime and ensure optimal performance in my infrastructure. ...al-machines-disks-expand-without-downtime-restrictions.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation mentions both Azure CLI and Azure PowerShell as supported tools, but PowerShell (a Windows-centric tool) is listed before CLI, and Windows-specific instructions (such as the Windows rescan function) are referenced before Linux equivalents. The rescan instructions for Windows are slightly more detailed, and the link for Windows is to a Microsoft driver page, while the Linux link is to Azure documentation. There is a subtle prioritization of Windows tools and patterns.
Recommendations
  • List cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell) to avoid implicit prioritization.
  • Ensure Linux and Windows instructions are equally detailed and prominent.
  • Provide direct Linux command examples (e.g., using 'lsblk', 'partprobe', or 'echo 1 > /sys/block/sdX/device/rescan') alongside Windows examples.
  • Include parity in troubleshooting steps for both platforms.
  • Where possible, link to official Linux documentation or community resources for disk management.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines. ...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Windows benchmarking tool (DISKSPD) and its usage before introducing the Linux equivalent (FIO). The Windows tool is described in detail with command-line examples first, followed by the Linux tool. There is a clear separation between Windows and Linux sections, but Windows is prioritized in order and coverage. Both platforms have example commands and explanations, but Windows tools are mentioned and explained first.
Recommendations
  • Present Linux (FIO) and Windows (DISKSPD) tools in parallel, or alternate their order in examples.
  • Add a comparison table summarizing both tools, their installation, and usage for quick reference.
  • Explicitly state platform applicability at the start of each section.
  • Ensure equal depth of explanation and example coverage for both platforms.
  • Consider including macOS guidance if applicable.
GitHub Create Pull Request
← Previous Page 31 of 33 Next →