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 676-700 of 818 flagged pages
Virtual Machines Remove a virtual machine scale set association from a capacity reservation group ...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/capacity-reservation-remove-virtual-machine-scale-set.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides API, Azure CLI, PowerShell, and Portal instructions for removing a VM scale set association from a capacity reservation group. PowerShell examples are given equal prominence to CLI, and explicit references to Azure PowerShell cmdlets are included. PowerShell is a Windows-centric tool, and its inclusion as a primary method (with detailed examples and links) reflects a Windows bias. Additionally, the CLI examples use Azure CLI, which is cross-platform, but PowerShell is mentioned before Portal in the tab order, and the documentation links to PowerShell modules without similar links for Bash or Linux shell scripting. There are no Bash or Linux shell script examples, nor are there references to Linux-specific tools or workflows.
Recommendations
  • Add Bash or Linux shell script examples where appropriate, especially for users who prefer scripting outside Azure CLI.
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS equally.
  • Provide links to Azure CLI documentation similar to the PowerShell links.
  • Consider reordering tabs so that CLI appears before PowerShell, or alternate tab order based on detected platform.
  • Explicitly mention Linux/macOS compatibility in the CLI sections.
GitHub Create Pull Request
Virtual Machines Remove a virtual machine association from a capacity reservation group ...les/virtual-machines/capacity-reservation-remove-vm.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 provides parity between Azure CLI and PowerShell examples, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, and is referenced with additional command links. There is a slight bias toward Windows tooling, as PowerShell is not natively available on Linux/macOS and is traditionally associated with Windows environments. The documentation also references Azure PowerShell commands in 'Learn more' sections, but does not offer equivalent Bash or shell scripting resources for Linux/macOS users. The ordering of tabs (API, Portal, CLI, PowerShell) puts PowerShell before Bash or Linux-specific examples, which may subtly prioritize Windows workflows.
Recommendations
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and recommend it as the default for non-Windows users.
  • Add explicit Bash or shell scripting examples for Linux/macOS users, especially for automation scenarios.
  • In 'Learn more' sections, provide links to Azure CLI documentation alongside PowerShell references.
  • Consider reordering tabs so CLI appears before PowerShell, or add a note about platform compatibility.
  • Mention that PowerShell Core is available on Linux/macOS, but CLI is often more familiar for Linux users.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. Windows-specific recommendations (e.g., 'Use at least B2 for Windows machines', Azure Hybrid Benefit for Windows Server) are mentioned without equivalent Linux guidance. Windows licensing optimization is discussed, but no Linux licensing or cost-saving features are highlighted. In some cases, Windows is mentioned before Linux (e.g., VM size pricing links), and Linux-specific examples or parity are missing for automation and cost-saving strategies.
Recommendations
  • Include Linux-specific cost optimization tips, such as leveraging reserved instances, optimizing OS licensing, or using open-source automation tools.
  • When mentioning VM sizes or pricing, present Windows and Linux options together or alternate which is listed first.
  • Discuss Linux equivalents for Azure Hybrid Benefit, or clarify if none exist.
  • Provide automation examples relevant to Linux environments (e.g., using cron jobs, cloud-init, or Ansible for VM scheduling/shutdown).
  • Ensure parity in recommendations for both Windows and Linux, especially in sections about licensing, automation, and VM selection.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. References to PowerShell and Windows tools are present before Linux equivalents, and links to configuration instructions list PowerShell before CLI or ARM templates. Examples for configuring VM watch are platform-neutral (JSON), but troubleshooting/logging instructions are split by OS only at the end. There are no explicit Linux/macOS command-line examples, and the overall flow assumes familiarity with Windows patterns.
Recommendations
  • Ensure that Azure CLI and ARM template instructions are listed before or alongside PowerShell, not after.
  • Provide explicit Linux/macOS command-line examples (e.g., using Azure CLI on Linux, bash environment variable settings) where relevant.
  • Where screenshots or tool references are given, include both Windows and Linux/macOS equivalents (e.g., Azure CLI output on Linux terminal).
  • In troubleshooting sections, provide parity in log file locations and diagnostic steps for both platforms, and consider including sample commands for viewing logs (e.g., 'cat' for Linux, 'type' for Windows).
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-13 06:17
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, PowerShell, and REST API. However, PowerShell is included as a top-level example for creating a gallery, while there is no equivalent example for Bash scripting or Linux-native tools. The order of examples also places PowerShell before REST, and the CLI examples use generic syntax but do not explicitly mention Linux/macOS compatibility. This subtly prioritizes Windows/PowerShell users and may create friction for Linux/macOS users.
Recommendations
  • Add explicit Bash shell scripting examples alongside PowerShell, especially for resource creation tasks.
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and provide OS-specific notes or examples where relevant.
  • Reorder example tabs so that CLI (cross-platform) appears before PowerShell, or group PowerShell and Bash together as scripting options.
  • Where PowerShell is shown, offer a Bash/Linux shell alternative for parity.
  • Explicitly mention that REST API calls are OS-agnostic and can be used from any platform.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by referencing PowerShell and Windows-specific installation instructions before Linux alternatives. The PowerShell section links only to Windows installation instructions, and PowerShell is presented before Azure CLI in some places. However, Azure CLI examples are provided, and no critical steps are Windows-only.
Recommendations
  • Add explicit instructions or links for installing Azure PowerShell on Linux/macOS.
  • Ensure parity in example ordering: present Azure CLI and PowerShell examples side-by-side or alternate which comes first.
  • Clarify that both Azure CLI and PowerShell work cross-platform, and provide troubleshooting tips for Linux/macOS users.
  • Where possible, avoid language like 'Install Azure PowerShell on Windows' and use 'Install Azure PowerShell' with platform-specific links.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation mentions both Windows and Linux VMs are supported, but introduces DiskSpd (Windows) before FIO (Linux) and links to DiskSpd first. The description of benchmarking tools starts with the Windows tool, and the overall tone and ordering slightly favor Windows. However, both platforms are acknowledged and tools for each are named and linked.
Recommendations
  • Present Linux and Windows tools in parallel, e.g., 'We have used common benchmarking tools: FIO for Linux and DiskSpd for Windows.'
  • Alternate the order of tool presentation or use a table to show parity.
  • Provide explicit example commands for both FIO (Linux) and DiskSpd (Windows) in the main documentation, not just in linked includes.
  • Ensure that any referenced steps or linked articles also provide Linux-specific guidance.
  • Add a note clarifying that both platforms are equally supported and that examples for both are available.
GitHub Create Pull Request
Virtual Machines Server-side encryption of Azure managed disks ...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page provides both Windows (PowerShell) and Linux (CLI) references for enabling encryption features, but there is a consistent pattern of listing Windows/PowerShell examples and links before Linux/CLI equivalents. Some references, such as to the Cryptography API: Next Generation, are Windows-specific. The main walkthroughs and 'Next steps' sections repeatedly mention PowerShell before CLI, and some deep links for advanced features (e.g., automatic key rotation) point to Windows/PowerShell guides first. There is no outright omission of Linux instructions, but the ordering and tool emphasis suggest a Windows-centric approach.
Recommendations
  • Alternate the order of Windows and Linux examples and links throughout the documentation, or present them side-by-side.
  • Provide equal prominence and detail for both Azure PowerShell and Azure CLI instructions, ensuring Linux users do not need to scroll past Windows content to find relevant guidance.
  • Where referencing platform-specific cryptography APIs (e.g., CNG for Windows), also mention Linux equivalents (e.g., dm-crypt, cryptsetup) or clarify their relevance.
  • Ensure that deep links for advanced features (e.g., automatic key rotation) are available for both PowerShell and CLI, and referenced equally.
  • Consider adding explicit callouts or sections for Linux/macOS users where workflows or tooling differ.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for listing affected disks, but the PowerShell example is presented first, and the command syntax is more detailed for PowerShell. The use of 'Disk Storage Center' (a portal tool) is platform-agnostic, but the overall pattern prioritizes Windows-centric tools and examples before Linux equivalents. There is no explicit Linux shell example (e.g., Bash), and the CLI example is less prominent.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Include explicit Bash shell examples for Linux users, showing how to use Azure CLI in a Linux terminal.
  • Clarify that both CLI and PowerShell are available on all platforms, and link to installation guides for Linux/macOS users.
  • Add a note or section specifically addressing Linux/macOS users, highlighting any differences or considerations.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for all tasks, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented before the Azure portal steps. There is a slight 'windows_first' bias in the order and prominence of PowerShell, and the use of PowerShell-specific instructions may be less familiar to Linux/macOS users. However, Azure CLI examples are present and fully functional for Linux/macOS users. No critical steps are Windows-only, and Linux is explicitly supported.
Recommendations
  • Consider listing Azure CLI examples before PowerShell in each section, as CLI is cross-platform and more natural for Linux/macOS users.
  • Add explicit notes clarifying that Azure CLI commands work natively on Linux/macOS, while PowerShell may require installation.
  • Where possible, provide bash-specific tips or troubleshooting for Linux users (e.g., environment variable usage, shell differences).
  • Ensure screenshots and portal instructions do not use Windows-specific terminology or UI elements.
  • Highlight Linux parity in the introduction, reassuring users that all steps are cross-platform.
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.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 Tools Missing Linux Example
Summary
The documentation page is mostly a feature and update summary, but there are several instances of Windows bias. Windows links and examples are sometimes listed before Linux equivalents (e.g., expanding disks without downtime), and some references point to Windows-specific documentation or tools (such as PowerShell and Windows disk management articles) without equal Linux coverage. In some cases, Linux examples are missing or referenced only as secondary options.
Recommendations
  • Ensure that all feature documentation links reference both Windows and Linux guides equally, ideally side-by-side.
  • Avoid listing Windows examples or documentation before Linux equivalents; use neutral ordering or group by OS.
  • Where Windows tools (e.g., PowerShell) are mentioned, also mention Linux tools (e.g., Bash, CLI) and provide equivalent instructions.
  • Audit linked articles to confirm Linux parity and update this summary page to clarify when features or instructions differ by OS.
GitHub Create Pull Request
Virtual Machines Deploy Ephemeral OS disks ...articles/virtual-machines/ephemeral-os-disks-deploy.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Minor Windows Example
Summary
The documentation provides a balanced overview of deploying ephemeral OS disks using multiple methods (Portal, ARM template, CLI, REST, PowerShell). However, there is a mild Windows bias: PowerShell (a Windows-centric tool) is given its own section with detailed examples, while Linux-native scripting tools (like Bash) are not. In the ARM template example for VMs, the image reference is for Windows Server by default, and no explicit Linux image example is shown. The CLI section is platform-neutral, but PowerShell is highlighted separately. No Linux-specific tools or workflows are mentioned.
Recommendations
  • Add explicit Linux image references in ARM template examples (e.g., Ubuntu or CentOS) alongside the Windows example.
  • Include Bash scripting examples for Linux users where PowerShell is shown.
  • Clarify that the Azure CLI commands work cross-platform and are recommended for Linux/macOS users.
  • If PowerShell is given a dedicated section, consider adding a Bash or shell scripting section for parity.
  • Mention that Azure PowerShell is available cross-platform, but CLI is often preferred on Linux/macOS.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows Reference
Summary
The documentation is overwhelmingly Linux-focused, as expected for the Azure Linux VM Agent. However, there is a minor Windows bias in the section describing SSH key types, where *putty.exe* (a Windows SSH client) is mentioned as not supporting ecdsa keys, and users are advised to use rsa or dsa if connecting from Windows. Additionally, in the Ubuntu Cloud Images section, a link to a Windows VM deployment tutorial is included alongside Linux resources, which may be confusing or unnecessary for Linux users.
Recommendations
  • Move or rephrase the mention of *putty.exe* so that Windows-specific advice is in a dedicated interoperability section, not in the main Linux configuration documentation.
  • Remove or clarify the link to the Windows VM deployment tutorial in the Ubuntu Cloud Images section. If the link is relevant for cross-platform automation, explain its purpose; otherwise, replace it with a Linux-specific resource.
  • When discussing SSH key types, provide parity by mentioning popular Linux SSH clients and their supported key types.
  • Ensure that all examples and references are Linux-centric unless explicitly discussing cross-platform scenarios.
GitHub Create Pull Request
Virtual Machines Azure Compute - Linux diagnostic extension 4.0 ...icles/virtual-machines/extensions/diagnostics-linux.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation is primarily focused on Linux, but there are several instances of Windows bias. PowerShell examples are given alongside Azure CLI, sometimes with more detail. Windows terminology and links (such as 'Configure managed identities' pointing to Windows VM docs) appear before or instead of Linux equivalents. Windows tools like Visual Studio Server Explorer are mentioned before cross-platform alternatives. However, Linux users can complete all tasks, and Linux-specific instructions are present.
Recommendations
  • Ensure Linux examples (Azure CLI, bash) are presented before or at least equally with PowerShell, especially in installation and configuration sections.
  • Replace or supplement Windows-centric links (e.g., 'Configure managed identities' for Windows VM) with Linux-specific documentation.
  • Mention cross-platform tools (e.g., Azure Storage Explorer) before Windows-only tools like Visual Studio Server Explorer.
  • Clarify when instructions or screenshots apply to Linux VMs, and avoid referencing Windows VM docs unless strictly necessary.
  • Review all sample code and ensure parity in detail and explanation between CLI and PowerShell examples.
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-13 06:17
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 Azure CLI and ARM template examples, but PowerShell is featured prominently for deployment and troubleshooting. PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows-first workflow, even though the extension is for Linux. However, Linux-native tools (Azure CLI, bash log paths) are also covered, and no critical steps are Windows-only.
Recommendations
  • Move Azure CLI examples before PowerShell examples to prioritize Linux-native workflows.
  • Explicitly mention that PowerShell can be used on Linux/macOS, or provide Bash/Cloud Shell alternatives for all PowerShell commands.
  • Add more context for Linux users about using Azure CLI and bash scripting for automation.
  • Clarify that the extension is not installable via native Linux package managers (apt, yum) to avoid confusion.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally maintains parity between Windows and Linux, but there are subtle signs of Windows bias. Windows tools (PowerShell) are mentioned before Linux equivalents (Azure CLI), and troubleshooting guidance for Windows VM extensions is called out before Linux. In some sections, Windows examples or terminology appear first, which may create a perception of Windows being the primary platform.
Recommendations
  • Alternate the order of Windows and Linux references throughout the documentation, or present Linux examples first in some sections.
  • Explicitly mention Linux management tools (e.g., Azure CLI, SSH) before or alongside PowerShell when listing extension management options.
  • Provide direct troubleshooting links for Linux VM extensions in the same way as for Windows.
  • Ensure that all extension examples and lifecycle instructions include both Linux and Windows commands/scripts, or link to them equally.
  • Review and balance the order of 'Next steps' links so Linux and Windows are treated equally.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally presents Windows examples and links before Linux equivalents, and highlights PowerShell as a deployment tool for both Windows and Linux, which may not be the most natural or common tool for Linux users. However, Linux deployment methods are present and linked, and alternative Linux-native tools (like Ansible) are mentioned.
Recommendations
  • Alternate the order of Windows and Linux examples/links to avoid always listing Windows first.
  • When describing PowerShell as a deployment method for Linux, clarify that native Linux shell options (bash, sh) are also supported if applicable, or provide equivalent bash/CLI examples.
  • Explicitly mention and link to Linux-native deployment methods (e.g., bash scripts, cloud-init) alongside PowerShell.
  • Where possible, provide side-by-side code snippets for both Windows (PowerShell) and Linux (bash) in the main documentation body, not just via external links.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation frequently presents Windows-based examples first, especially in REST API and PowerShell sections, with explicit references to 'ApplicationHealthWindows' and Windows VM scenarios. PowerShell (a Windows-centric tool) is given its own section with detailed examples, while Linux examples are only provided in Azure CLI sections and are not as prominent. The troubleshooting/logging section lists Windows log paths before Linux equivalents. Overall, there is a subtle but consistent prioritization of Windows tools and patterns throughout the page.
Recommendations
  • Alternate the order of Windows and Linux examples so that Linux is shown first in some sections.
  • Provide parity in example detail for both Windows and Linux, including explicit Linux VM scenarios in REST API and PowerShell sections (where possible).
  • Add Bash scripting examples for Linux users alongside PowerShell, or clarify that PowerShell Core can be used cross-platform.
  • List Linux log paths before or alongside Windows paths in troubleshooting sections.
  • Explicitly mention macOS compatibility or usage where relevant, especially for CLI tools.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Recommended Windows Missing Macos Example
Summary
The documentation generally maintains cross-platform neutrality, with explicit applicability to both Linux and Windows VMs. However, there is a subtle Windows bias: Windows Server is listed first and is the only OS called out in the 'Recommended OS for Performance' row, and the only explicit recommendation for performance is Windows Server 2019+. Linux distributions are listed for SRIOV RDMA support, but no Linux distribution is recommended for performance. There are no macOS examples or mentions. All command-line topology examples use Linux tools (lstopo), not Windows or PowerShell, which is positive for Linux parity.
Recommendations
  • Add a recommended Linux distribution for performance, or clarify if Windows Server 2019+ is uniquely recommended.
  • List Linux distributions first or equally in tables and recommendations.
  • If possible, provide equivalent Windows tooling or commands for topology inspection, or clarify that lstopo is available on Windows via WSL or other means.
  • Explicitly mention macOS support status if relevant, or clarify that macOS is not supported.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Windows Baseline Reference Powershell Heavy Minor Windows Tools
Summary
The documentation generally maintains OS parity, but there are subtle signs of Windows bias: Windows security baseline is referenced explicitly while Linux equivalents are not; PowerShell is often mentioned first in command examples and permissions configuration; and some references to Windows-specific tools (Sysprep) and features appear before Linux alternatives. However, Linux is supported throughout, and CLI examples are provided alongside PowerShell.
Recommendations
  • Explicitly mention Linux security baseline options or reference equivalent Linux hardening templates.
  • Alternate the order of PowerShell and CLI examples, or present CLI first to reflect cross-platform usage.
  • Provide Linux-specific configuration and customization examples where Windows-specific tools (like Sysprep) are mentioned.
  • Ensure that documentation links and references for Linux image building are as prominent as those for Windows.
  • Add references to Linux configuration management tools (e.g., cloud-init, Ansible) alongside Windows tools.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both PowerShell and Azure CLI examples, but PowerShell (a Windows-centric tool) is listed before CLI in both role assignment and disk update instructions. This ordering subtly prioritizes Windows workflows. There are no explicit Linux/macOS examples or notes, and no mention of platform-specific considerations for CLI usage on non-Windows systems.
Recommendations
  • Alternate the order of PowerShell and CLI examples, or present CLI examples first to better support Linux/macOS users.
  • Explicitly mention that Azure CLI works cross-platform and provide installation/use links for Linux/macOS.
  • Add notes or examples for Linux/macOS environments where relevant, such as shell syntax or authentication differences.
  • Consider including Bash or other Linux-native scripting examples if applicable.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud storage administrator, I want to adjust the expiration settings of Shared Access Signatures for disks and snapshots, so that I can ensure compliance with the upcoming 60-day limit and maintain uninterrupted access for my users. ...articles/virtual-machines/includes/disks-sas-change.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation consistently lists Azure PowerShell as a primary tool alongside REST API and Azure CLI, and refers to the Azure PowerShell module by name and link in every example. This creates a subtle Windows bias, as PowerShell is traditionally a Windows-centric tool, even though cross-platform support exists. The PowerShell option is always mentioned, sometimes before or alongside CLI, but never after a Linux-specific tool. No Linux/macOS-specific examples or shell scripts are provided.
Recommendations
  • Explicitly note that Azure CLI is fully cross-platform and provide Bash or shell script examples for Linux/macOS users.
  • Clarify that PowerShell Core is available on Linux/macOS, or link to installation instructions for non-Windows platforms.
  • Consider listing Azure CLI before PowerShell in examples, or alternate the order to avoid implicit prioritization.
  • Add a note or section for Linux/macOS users, highlighting any differences or best practices.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents Windows (DISKSPD) benchmarking examples and explanations before Linux (FIO) equivalents. Both platforms are covered with detailed, parity examples, but Windows is introduced first and in greater detail initially, which may create a perception of Windows prioritization.
Recommendations
  • Present Linux and Windows benchmarking tools in parallel, or alternate which platform is introduced first.
  • Add a short comparison table at the top showing both DISKSPD and FIO, their platforms, and installation commands.
  • Ensure equal detail and prominence for both sets of examples, including introductory context and explanations.
  • Explicitly state that both Windows and Linux are supported and provide links to further resources for each.
GitHub Create Pull Request
Virtual Machines Connect to a Linux VM ...lob/main/articles/virtual-machines/linux-vm-connect.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy
Summary
The documentation provides parity between Linux/macOS and Windows users by offering separate tabs for each platform, with clear instructions and examples. However, in the Windows section, the host fingerprint validation step uses a PowerShell/Azure PowerShell command (Invoke-AzVMRunCommand), while the Linux/macOS section uses a direct SSH command. This introduces a slight bias towards Windows tools and PowerShell, as Linux users may not be shown an equivalent Azure CLI method for host fingerprint retrieval. Additionally, the Windows section references PowerShell and cmd.exe, but does not mention third-party SSH clients for Windows.
Recommendations
  • Provide an Azure CLI example for host fingerprint retrieval in the Linux/macOS section, similar to the PowerShell example in the Windows section.
  • Mention third-party SSH clients for Windows (e.g., PuTTY, MobaXterm) for users who prefer alternatives to cmd.exe/PowerShell.
  • Ensure troubleshooting steps and advanced scenarios (e.g., Bastion, file transfer) include both Azure CLI and PowerShell options for all platforms.
  • Consider listing Linux/macOS instructions before Windows instructions in general documentation, unless usage statistics justify otherwise.
GitHub Create Pull Request
Virtual Machines Azure Instance Metadata Service for virtual machines ...articles/virtual-machines/instance-metadata-service.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux examples for all core operations, but consistently lists Windows (PowerShell) examples before Linux (bash/curl) ones. In troubleshooting and routing sections, Windows tools (route print, ipconfig, PowerShell CLI) are described in greater detail and appear first, with Linux equivalents following. Some advanced PowerShell scripting is shown for Windows, while Linux examples are simpler. The documentation does not omit Linux examples, but the ordering and depth of Windows coverage indicate a mild Windows bias.
Recommendations
  • Alternate the order of Windows and Linux examples so Linux is shown first in some sections.
  • Provide equally detailed troubleshooting steps for Linux, including advanced commands and scripting where appropriate.
  • Ensure Linux tools (e.g., netstat, ip, ifconfig, nmcli) are referenced with the same depth as Windows tools.
  • Where PowerShell scripting is shown, consider providing equivalent bash or Python scripting for Linux.
  • Explicitly mention macOS compatibility and provide examples where Linux commands would work on macOS.
GitHub Create Pull Request
← Previous Page 28 of 33 Next →