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 726-750 of 818 flagged pages
Virtual Machines Edsv6 size series ...irtual-machines/sizes/memory-optimized/edsv6-series.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation is largely neutral and platform-agnostic, focusing on VM specifications and features. However, there is a minor Windows bias in the 'Feature support' section, where nested virtualization is linked only to a Windows-specific (Hyper-V) guide, and in the 'Network' section, bandwidth testing references NTTTCP, a tool that originated on Windows. No Linux/macOS-specific examples, tools, or guides are provided in these contexts.
Recommendations
  • In the 'Feature support' section, add references to nested virtualization guides for Linux (such as KVM/QEMU) if supported, or clarify platform limitations.
  • In the 'Network' section, mention Linux-native bandwidth testing tools (e.g., iperf3) alongside NTTTCP, and provide links to relevant Linux documentation.
  • Where platform-specific features are discussed, explicitly state support or limitations for Linux/macOS and provide parity in documentation links.
GitHub Create Pull Request
Virtual Machines Troubleshoot problems with shared images in Azure ...cles/virtual-machines/troubleshooting-shared-images.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page references both Azure CLI and PowerShell for troubleshooting, but explicitly calls out PowerShell's '-Debug' switch alongside Azure CLI's '--debug'. This gives prominence to Windows/PowerShell tooling, and the mention of PowerShell occurs before any Linux-specific shell or tool. No Linux/macOS-specific troubleshooting commands or examples are provided, and there is no mention of Bash, shell scripting, or Linux-native tools. All error messages and mitigations are generic and do not show platform-specific examples, but the initial troubleshooting guidance is slightly Windows-biased.
Recommendations
  • Explicitly mention Bash or Linux shell equivalents for troubleshooting, such as using Azure CLI in Bash or Zsh.
  • Provide example commands for both PowerShell and Bash (Linux/macOS) when discussing troubleshooting steps.
  • Clarify that Azure CLI works cross-platform and provide links or notes for installing and using it on Linux/macOS.
  • If PowerShell is referenced, also mention PowerShell Core (pwsh) for Linux/macOS, or clarify platform compatibility.
  • Consider listing Azure CLI (cross-platform) before PowerShell in troubleshooting steps to avoid Windows-first perception.
GitHub Create Pull Request
Virtual Machines Understand VM reboots ...ain/articles/virtual-machines/understand-vm-reboots.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation generally presents information in a platform-neutral way, but there is a subtle bias in the ordering and linking of resources: Windows and Linux scheduled events are mentioned together, but the Windows link is listed second. There are no command-line examples or tooling references for either platform, and no explicit examples for Linux or Windows. However, the lack of Linux-specific troubleshooting or operational examples (such as how to check for downtime or maintenance events on Linux VMs) may leave Linux users with less actionable guidance compared to what could be provided.
Recommendations
  • Provide explicit examples or references for both Linux and Windows users, such as commands to check system logs for reboots or maintenance events.
  • Ensure parity in documentation depth for both platforms, including troubleshooting steps and operational guidance.
  • If mentioning scheduled events, briefly summarize the differences or considerations for Linux and Windows, rather than only linking out.
  • Consider listing Linux and Windows resources in alternating order or together to avoid perceived prioritization.
GitHub Create Pull Request
Virtual Machines We're retiring Azure unmanaged disks by March 31, 2026 ...ticles/virtual-machines/unmanaged-disks-deprecation.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by listing Windows migration resources and examples before Linux equivalents and referencing PowerShell as a primary tool for querying affected VMs. Linux migration is mentioned, but Windows is consistently presented first, and no Linux-specific CLI or scripting examples are provided.
Recommendations
  • Present Linux and Windows migration resources in parallel or alternate their order to avoid 'Windows first' bias.
  • Include examples for querying affected VMs using Azure CLI or Bash scripts, which are more common for Linux users.
  • Explicitly mention Linux-friendly tools and workflows alongside PowerShell, such as Azure CLI commands.
  • Ensure links to migration guides for both Windows and Linux are equally prominent and described.
GitHub Create Pull Request
Virtual Machines Understanding Azure virtual machine usage ...e-docs/blob/main/articles/virtual-machines/vm-usage.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Windows Examples Windows Terms
Summary
The documentation references both Linux and Windows VMs, but Windows-related terms and examples appear more frequently and are often listed before Linux equivalents. For example, image types and usage examples mention Windows Server and SQL Server on Windows before Linux distributions. Tagging instructions link to both CLI and PowerShell, but the PowerShell link is labeled as 'tag-portal', which may suggest a Windows-centric approach. There are no explicit Linux-only examples, and Windows terminology (BYOL, Hybrid Benefit) is explained in detail, while Linux licensing or usage is not.
Recommendations
  • Ensure Linux distributions and usage scenarios are given equal prominence in examples and explanations.
  • Provide explicit Linux CLI examples and links alongside PowerShell instructions, not just as an afterthought.
  • Balance the order of Windows and Linux references in lists and tables (e.g., image types, usage scenarios).
  • Include details about Linux licensing, cost management, and marketplace images similar to the Windows explanations.
  • Clarify that tagging and other features work equally for Linux and Windows VMs, and provide parallel instructions.
GitHub Create Pull Request
Virtual Machines Boot integrity monitoring overview ...virtual-machines/boot-integrity-monitoring-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 demonstrates a mild Windows bias. Windows examples and terminology (e.g., PowerShell, WindowsAttestation publisher) are presented before Linux equivalents in several sections. The PowerShell tab is present, but there is no Bash or Linux shell scripting tab. Troubleshooting and configuration steps reference Windows-centric extension names and tools, and screenshots are from the Azure portal, which is platform-neutral but often reflects Windows conventions. However, Linux template examples are provided, and CLI instructions are generally cross-platform.
Recommendations
  • Add a Bash or Linux shell scripting tab alongside PowerShell for parity.
  • Ensure Linux examples are presented alongside or before Windows examples in all sections.
  • Clarify that Azure portal and CLI instructions apply equally to Linux and Windows VMs.
  • Include troubleshooting examples and error messages for Linux (e.g., referencing Microsoft.Azure.Security.LinuxAttestation.GuestAttestation failures).
  • Balance screenshots to show Linux VM context where possible.
GitHub Create Pull Request
Virtual Machines Support matrix for VM restore points ...n/articles/virtual-machines/concepts-restore-points.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents Windows operating system support details before Linux, listing specific Windows versions and only referencing Linux distributions in a general way. No PowerShell or Windows-specific tooling is used in examples, and Linux support is described, but Windows is given more detailed attention and is listed first.
Recommendations
  • Present Windows and Linux operating system support in parallel, or list Linux first in some sections to balance presentation.
  • Provide a more detailed list of supported Linux distributions (or link more prominently to the endorsed distros page).
  • Ensure examples and guidance for creating restore points (referenced in 'Next steps') include both Linux and Windows scenarios equally.
GitHub Create Pull Request
Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.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 examples for Azure Portal, Azure CLI, PowerShell, and REST API. PowerShell is included as a dedicated example tab alongside CLI, which is cross-platform. However, PowerShell is primarily a Windows tool, and there is no mention of Linux/macOS-specific shell commands (e.g., Bash, shell scripts) or guidance for Linux users. In the ordering of examples, PowerShell is given equal prominence to CLI, and in some sections, it appears before REST, which may reinforce Windows-centric workflows. No explicit Linux tools or patterns are mentioned.
Recommendations
  • Clarify that Azure CLI examples work on Linux/macOS as well as Windows.
  • Add Bash or shell script examples where relevant, especially for automation scenarios.
  • Note PowerShell's cross-platform availability, but avoid implying it is required for Linux/macOS users.
  • Consider ordering CLI examples before PowerShell to emphasize cross-platform support.
  • Explicitly mention that all tasks can be completed on Linux/macOS using CLI and REST.
GitHub Create Pull Request
Virtual Machines Azure VM Extensions and Features for Linux ...articles/virtual-machines/extensions/features-linux.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 is focused on Linux VM extensions, but consistently presents both Azure CLI and Azure PowerShell examples for all operations. PowerShell examples are given equal prominence to CLI, despite PowerShell being a Windows-centric tool (even though it is available on Linux, CLI is more common for Linux users). References to ARM templates link to Windows documentation first, and some terminology (such as 'PowerShell') may be confusing for Linux users. However, all examples and screenshots are Linux-specific, and Linux tools (Azure CLI, waagent, Bash) are well represented.
Recommendations
  • Prioritize Azure CLI examples and place them before PowerShell examples, as CLI is more widely used on Linux.
  • Clarify that PowerShell is available on Linux, but Azure CLI is the recommended tool for Linux users.
  • Link to ARM template documentation that is Linux-specific, or provide parity in links for both Windows and Linux.
  • Where possible, use Bash and Linux-native commands in examples and troubleshooting sections.
  • Consider omitting PowerShell examples or moving them to a separate tab or appendix for Linux-focused documentation.
GitHub Create Pull Request
Virtual Machines Dedicated hosts include file ...es/virtual-machines/includes/dedicated-hosts-resize.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 examples for Azure Portal, Azure CLI, and PowerShell, with PowerShell (a Windows-centric tool) given a dedicated section and detailed command syntax. The CLI section uses Azure CLI, which is cross-platform, but PowerShell is highlighted separately, and no mention is made of Bash or Linux-specific workflows. The ordering places PowerShell after CLI, but the PowerShell section is more verbose and links to further Windows-specific resources.
Recommendations
  • Add explicit Bash examples for Linux/macOS users, especially for scripting resize operations.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • Include a note or section for Linux/macOS users, mentioning alternative shell environments and any OS-specific considerations.
  • Balance the detail level between PowerShell and CLI sections, ensuring Linux users have equally comprehensive guidance.
GitHub Create Pull Request
Virtual Machines Prepare a Debian Linux VHD ...les/virtual-machines/linux/debian-create-upload-vhd.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 page is focused on preparing Debian Linux VHDs for Azure and is generally Linux-centric. However, there is evidence of Windows bias in the 'Prerequisites' and 'Installation notes' sections, where Windows tools (Hyper-V, convert-vhd cmdlet) are mentioned first and in more detail than Linux alternatives. Linux tools for VHD creation (e.g., qemu-img) are covered later, but Windows options are introduced before Linux equivalents, and links to Windows-specific instructions are provided.
Recommendations
  • Mention Linux-native VHD creation tools (e.g., qemu-img, VBoxManage) alongside or before Windows tools in the prerequisites section.
  • Provide links to Linux-specific guides for creating and converting VHD files.
  • Clarify that Hyper-V is only one of several options and highlight Linux alternatives equally.
  • If referencing Windows tools, also give equivalent Linux command-line examples and documentation links.
  • Ensure that Linux users can complete all steps without needing Windows or Windows-only tools.
GitHub Create Pull Request
Virtual Machines Azure VM Image Builder networking options ...les/virtual-machines/linux/image-builder-networking.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 Windows-related examples and tools (PowerShell) before their Linux equivalents (Azure CLI) in several places. For example, in the 'Checklist for using your virtual network' section, PowerShell examples are consistently listed after Azure CLI, but the links for Windows and PowerShell are present throughout. Additionally, the 'Required permissions' section lists both CLI and PowerShell, but PowerShell is called out specifically for Windows users. There is also an 'IMPORTANT' note that is Windows-specific (WinRM configuration), while no equivalent Linux-specific caveat is provided.
Recommendations
  • Ensure Linux/Azure CLI examples are presented first or equally alongside Windows/PowerShell examples.
  • Add Linux-specific notes or caveats where Windows-specific ones are present (e.g., SSH configuration impacts).
  • Where possible, clarify that PowerShell is available cross-platform, or provide Bash examples for Linux/macOS users.
  • Review linked example pages to ensure Linux and Windows parity in depth and clarity.
GitHub Create Pull Request
Virtual Machines Use a template to deploy Azure Spot Virtual Machines .../main/articles/virtual-machines/linux/spot-template.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 mentions Azure PowerShell (Windows-centric) before Azure CLI in the 'Next steps' section, and links to a Windows-specific PowerShell guide. No Linux-specific tools or examples are provided, although the template itself is OS-agnostic and uses Ubuntu as the VM image.
Recommendations
  • List Azure CLI before Azure PowerShell in 'Next steps', as CLI is cross-platform.
  • Provide explicit Linux/macOS usage examples, such as deploying the template via Azure CLI on Linux.
  • Include links to Linux-specific guides or troubleshooting resources.
  • Clarify that the template can be used from any OS and provide instructions for both Windows and Linux users.
GitHub Create Pull Request
Virtual Machines MSP Feature Configuration ...l-machines/metadata-security-protocol/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 🔧 Windows Tools
Summary
The documentation shows mild Windows bias. Windows is mentioned first in several places (e.g., 'automatic GPA installation (when true) or uninstallation (when false) on a Windows VM'), and example resource names use 'GPAWinVM'. However, Linux is supported and audit log locations are documented for both OSes. No PowerShell-only examples or Windows-exclusive instructions are present, but Windows terminology and ordering are favored.
Recommendations
  • Use neutral example resource names (e.g., 'GPAExampleVM' instead of 'GPAWinVM').
  • When describing behaviors, mention both Windows and Linux equally (e.g., 'automatic GPA installation/uninstallation on Windows or Linux VMs').
  • Ensure that any OS-specific instructions or behaviors are documented for both Windows and Linux, with equal prominence.
  • Alternate the order in which Windows and Linux are listed/described, or use OS-neutral phrasing.
  • Add explicit Linux configuration examples if any OS-specific steps exist.
GitHub Create Pull Request
Virtual Machines We're retiring Azure unmanaged disks by March 31, 2026 ...ticles/virtual-machines/unmanaged-disks-deprecation.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 page exhibits minor Windows bias by listing Windows migration resources before Linux equivalents and referencing PowerShell as a primary tool for querying affected VMs, with no mention of Linux CLI alternatives (e.g., Azure CLI, Bash). However, both Windows and Linux migration guides are linked, and the overall instructions are platform-neutral.
Recommendations
  • Present Linux and Windows migration links together or alternate their order to avoid Windows-first bias.
  • Include Linux-friendly command-line examples (e.g., Azure CLI, Bash scripts) alongside PowerShell for querying affected VMs.
  • Explicitly mention Linux tools and workflows in sections discussing VM discovery and migration.
  • Add a note clarifying that all steps can be performed on Linux/macOS using Azure CLI or portal, not just PowerShell.
GitHub Create Pull Request
Virtual Machines Availability options for Azure Virtual Machines ...cs/blob/main/articles/virtual-machines/availability.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 page is mostly platform-neutral, but in the 'Load balancer' section, PowerShell is mentioned before CLI as an example for quickstarts, and both links are provided. This ordering may subtly prioritize Windows users. There are no Linux-specific examples in the main body, but the 'Next steps' section does link to Linux-focused tutorials. No Windows-only tools or patterns are exclusively referenced, but PowerShell is given equal prominence to CLI, which is more cross-platform.
Recommendations
  • Present CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
  • Explicitly mention that both CLI and PowerShell are supported, and clarify which is recommended for Linux/macOS users.
  • Add Linux/macOS-specific notes or examples in relevant sections to further improve parity.
  • Ensure that all referenced quickstarts and tutorials have Linux/macOS equivalents and are clearly labeled.
GitHub Create Pull Request
Virtual Machines Azure boot diagnostics ...lob/main/articles/virtual-machines/boot-diagnostics.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 Windows and Linux applicability, but there is a mild bias toward Windows in the ordering and tooling. PowerShell is mentioned as a primary method for enabling boot diagnostics, with CLI and ARM Template alternatives. The link for configuring the storage firewall for Azure Serial Console points to a Windows-specific troubleshooting page, even though Linux VMs are supported. Windows screenshots/examples are presented alongside Linux, but Windows tools (PowerShell) are given a dedicated section before ARM templates.
Recommendations
  • Ensure that Linux-specific tools (such as Bash scripts or Linux shell commands) are given equal prominence to PowerShell, with example commands for enabling boot diagnostics on Linux VMs.
  • When referencing troubleshooting guides or configuration steps, provide both Windows and Linux links, or clarify applicability for both OS types.
  • Alternate the order of examples so that Linux and Windows are presented with parity, or group them together when possible.
  • Explicitly mention cross-platform support in CLI and ARM Template sections, and provide sample commands for both Linux and Windows environments.
GitHub Create Pull Request
Virtual Machines Best practices for virtual machine cost optimization ...s/virtual-machines/cost-optimization-best-practices.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 demonstrates mild Windows bias. Windows-specific recommendations (e.g., 'Use at least B2 for Windows machines', 'Azure Hybrid Benefit for Windows Server') are given without equivalent Linux guidance. Windows pricing and licensing options are mentioned before Linux, and some cost-saving tips are Windows-only. There are no Linux-specific cost optimization examples or tools highlighted, and Linux is generally referenced second or as an afterthought.
Recommendations
  • Add Linux-specific cost optimization tips, such as recommendations for Linux VM series, licensing, and storage.
  • Provide parity in examples: if mentioning Azure Hybrid Benefit for Windows, clarify Linux licensing options (e.g., bring-your-own subscription for RHEL/SUSE).
  • When listing pricing pages or VM sizes, alternate or parallelize Windows and Linux references.
  • Include automation and shutdown examples relevant to Linux (e.g., using cron, Azure Automation for Linux VMs).
  • Ensure that recommendations for VM sizing, disk types, and policies explicitly address both Windows and Linux use cases.
GitHub Create Pull Request
Virtual Machines Create a capacity reservation in Azure ...ticles/virtual-machines/capacity-reservation-create.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 examples for Azure Portal, Azure CLI, and Azure PowerShell in parallel tabbed sections. However, PowerShell is given equal prominence to CLI, despite being primarily a Windows tool. In some sections, PowerShell examples are shown immediately after CLI, and PowerShell-specific commands are referenced directly. There are no Linux-specific shell examples (e.g., Bash), and no mention of platform differences or considerations for Linux/macOS users. The CLI examples are cross-platform, but the presence and prominence of PowerShell may create a perception of Windows bias.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows equally, and consider providing explicit Bash examples or notes for Linux/macOS users.
  • Add a brief note explaining that PowerShell examples are primarily for Windows users, and that Linux/macOS users should use Azure CLI or Bash.
  • Consider reordering tabs so that CLI (cross-platform) appears before PowerShell, or add a 'Bash' tab for Linux/macOS users if there are platform-specific nuances.
  • Reference platform parity in introductory sections, reassuring users that all major steps can be completed on Linux/macOS using CLI.
GitHub Create Pull Request
Virtual Machines Modify a capacity reservation in Azure ...ticles/virtual-machines/capacity-reservation-modify.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 Azure CLI and PowerShell examples, but PowerShell is always presented as a first-class option alongside CLI, and is shown in every tabbed section. There is a subtle Windows bias in that PowerShell is a Windows-centric tool (even though it is now cross-platform, many users still associate it with Windows), and the ordering of tabs is API, Portal, CLI, then PowerShell—placing PowerShell last but always present. There are no explicit Linux-only examples, and no mention of Linux-specific tools or shell patterns (e.g., bash scripting). However, the CLI examples are cross-platform and suitable for Linux/macOS users, and the documentation states applicability to both Linux and Windows VMs.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide sample bash/zsh usage where relevant.
  • Clarify that PowerShell is available cross-platform, but highlight CLI as the default for Linux/macOS users.
  • Consider reordering tabs so CLI appears before PowerShell, or add a note for Linux users recommending CLI.
  • Add troubleshooting tips or links for Linux/macOS users if there are known issues with PowerShell or CLI on those platforms.
GitHub Create Pull Request
Virtual Machines Proximity placement groups ...ocs/blob/main/articles/virtual-machines/co-location.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 Minor Windows Tools
Summary
The documentation generally maintains cross-platform parity, explicitly stating applicability to both Linux and Windows VMs. However, there are minor signs of Windows bias: PowerShell is mentioned before CLI in several places, and Windows terminology/tools (PowerShell, Availability Set Overview page) are referenced slightly more prominently than their Linux equivalents. Examples and links for both platforms are provided, but Windows tools are sometimes listed first.
Recommendations
  • Alternate the order of CLI and PowerShell references so Linux tools are not always second.
  • Where possible, provide equal detail for both CLI and PowerShell commands, or combine instructions for cross-platform tools.
  • Mention Linux-specific management interfaces (e.g., Azure CLI in Cloud Shell, Linux VM portals) where relevant.
  • Ensure screenshots and UI references are platform-neutral or provide both Linux and Windows examples.
GitHub Create Pull Request
Virtual Machines Configure Event Hubs for VM watch ...ticles/virtual-machines/configure-eventhub-vm-watch.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 page exhibits mild Windows bias. References to PowerShell and Windows tools are present before Linux equivalents, and links to configuration instructions mention PowerShell alongside ARM templates and CLI. The log file troubleshooting section does provide both Linux and Windows paths, but there are no explicit Linux/macOS command-line examples (e.g., using Bash or Linux-native tools) for configuring or viewing Event Hubs data. Windows terminology and patterns (e.g., C:/WindowsAzure paths, PowerShell) are mentioned first or exclusively in some places.
Recommendations
  • Provide Linux/macOS command-line examples (e.g., Bash, Azure CLI) alongside or before Windows/PowerShell examples.
  • Ensure links to configuration instructions highlight Linux/macOS methods equally (not just PowerShell).
  • When mentioning log file paths or troubleshooting, present Linux and Windows paths in parallel, not sequentially.
  • Add screenshots or instructions for viewing Event Hubs data using Linux/macOS tools (e.g., az CLI, curl, jq) if possible.
  • Review terminology to avoid Windows-centric language (e.g., use 'file system path' instead of 'C:/...').
GitHub Create Pull Request
Virtual Machines Deploy Azure dedicated hosts ...in/articles/virtual-machines/dedicated-hosts-how-to.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 Azure Portal, Azure CLI, and PowerShell for all major operations. However, there is a mild Windows bias: PowerShell examples are given equal weight to CLI, and in some sections (e.g., 'Reassign an existing VM', 'Move a VM from dedicated host to multitenant infrastructure'), PowerShell is presented after CLI but with detailed variable usage and scripting, which is more familiar to Windows users. The CLI examples are cross-platform, but PowerShell is inherently Windows-centric (though available on Linux, it's less commonly used there). There are no explicit Linux-only examples (e.g., bash scripts), and the documentation does not mention Linux-specific tools or patterns. The Portal instructions are neutral.
Recommendations
  • Add explicit bash script examples for common tasks to demonstrate Linux-native workflows.
  • Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
  • Consider mentioning that PowerShell is available on Linux/macOS, but CLI is more typical for those platforms.
  • Where relevant, note any differences in experience or prerequisites for Linux/macOS users (e.g., SSH keys, shell environment).
  • If possible, add troubleshooting or tips sections for Linux users (e.g., dealing with az CLI installation, permissions, etc.).
GitHub Create Pull Request
Virtual Machines Use a disk encryption set across Microsoft Entra tenants ...l-machines/disks-cross-tenant-customer-managed-keys.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 page exhibits mild Windows bias by referencing PowerShell and Windows-specific installation instructions before Linux alternatives. The PowerShell section links to 'Install Azure PowerShell on Windows with PowerShellGet', and PowerShell is presented before Azure CLI in several places. However, Azure CLI examples are provided, and no critical steps are Windows-only.
Recommendations
  • Provide installation instructions for Azure PowerShell on Linux/macOS alongside Windows.
  • Avoid referencing Windows-specific installation methods (e.g., PowerShellGet) without mentioning cross-platform alternatives.
  • Alternate the order of PowerShell and CLI examples, or present CLI first to better reflect cross-platform usage.
  • Explicitly state that both PowerShell and CLI are cross-platform, and provide links to installation guides for all OSes.
GitHub Create Pull Request
Virtual Machines Benchmark your application on Azure Disk Storage ...lob/main/articles/virtual-machines/disks-benchmarks.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 introduces Windows benchmarking tools (DiskSpd) before Linux equivalents (FIO), and mentions DiskSpd as the primary example for Windows. The order and phrasing subtly prioritize Windows tools and patterns, though Linux is acknowledged and FIO is referenced. No explicit Linux example is missing, but the Windows tool is listed first and its link precedes the Linux tool.
Recommendations
  • Present Linux and Windows tools in parallel, or alternate which is mentioned first.
  • Provide equal detail and prominence to both DiskSpd and FIO, including links and example usage.
  • Consider adding explicit command-line examples for both platforms in the main documentation, not just in includes.
  • Clarify that both Linux and Windows are fully supported and provide parity in instructions.
GitHub Create Pull Request
← Previous Page 30 of 33 Next →