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 151-175 of 818 flagged pages
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation claims to apply to both Windows and Linux VMs, and provides Azure CLI, API, Portal, ARM template, and PowerShell instructions for associating VMs with capacity reservation groups. However, there is a notable Windows bias: the ARM template example is exclusively for Windows Server (no Linux image or parameters shown), and password requirements are described in Windows-centric terms. PowerShell examples (a Windows-centric tool) are given equal prominence as CLI, but no bash or Linux shell examples are provided. Windows terminology and tools (e.g., PowerShell, Windows images) are referenced before or instead of Linux equivalents. There are no explicit Linux-focused examples or ARM template snippets for Linux VMs.
Recommendations
  • Add ARM template examples for Linux VM images (e.g., Ubuntu, CentOS) alongside the Windows example.
  • Clarify password requirements for Linux VMs (e.g., SSH key usage) and provide Linux-specific administrator account guidance.
  • Include bash or Linux shell examples for common tasks, especially for users who do not use PowerShell.
  • Ensure that examples and parameter lists are balanced between Windows and Linux, or provide tabs for each OS where relevant.
  • Mention Linux-specific considerations (e.g., SSH authentication, cloud-init) where appropriate.
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for API, Azure CLI, PowerShell, and Portal. PowerShell is included as a dedicated tab, which is primarily a Windows tool, and is referenced with links and detailed usage. While Azure CLI is cross-platform and shown before PowerShell, the presence of PowerShell as a first-class example and the explicit references to PowerShell commands indicate a moderate Windows bias. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux/macOS-specific considerations. However, the CLI examples are sufficient for Linux/macOS users to complete the tasks.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands work on Linux/macOS as well as Windows.
  • Consider including Bash or shell script examples for Linux users, especially for automation scenarios.
  • If PowerShell is shown, mention that PowerShell Core is available cross-platform, or clarify any Windows-specific limitations.
  • Ensure that CLI examples are as detailed as PowerShell ones, including links to relevant CLI documentation.
  • Avoid presenting PowerShell as the default or preferred method unless necessary.
GitHub Create Pull Request
Virtual Machines Delete a VM and attached resources ...ute-docs/blob/main/articles/virtual-machines/delete.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides examples for Azure Portal, CLI, PowerShell, and REST API. PowerShell is featured as a primary scripting option alongside CLI, but there is no mention of Linux shell scripting (e.g., Bash) or Linux-specific patterns. The CLI examples are cross-platform, but PowerShell is Windows-centric and presented as an equal alternative. REST API examples use Windows-centric resource names and images, and the FAQ and backup management instructions reference the portal with Windows-style navigation. There are no explicit Linux/macOS shell examples, and Windows tools (PowerShell) are given equal prominence to CLI, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit Bash shell examples for common operations, especially for updating and deleting VMs and resources.
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS terminals.
  • In REST API examples, use neutral or Linux-centric image references and OS types where appropriate.
  • In PowerShell sections, add notes for Linux users about alternatives (e.g., Azure CLI, Bash scripting).
  • In FAQ and portal navigation, clarify that the portal is OS-agnostic and accessible from any browser.
  • Consider reordering examples to present CLI (cross-platform) before PowerShell (Windows-centric).
GitHub Create Pull Request
Virtual Machines Copy a snapshot to a new region ...ines/disks-copy-incremental-snapshot-across-regions.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides detailed examples for Azure CLI (which is cross-platform) and Azure PowerShell (primarily Windows-focused), with PowerShell examples given equal prominence as CLI. However, there are no explicit Linux/macOS shell examples (e.g., bash), nor are Linux-specific considerations or troubleshooting tips mentioned. The CLI examples use bash syntax, but this is not explicitly stated or explained for Linux users. The manual copy section refers only to .NET sample code, with no mention of Linux-native tooling or languages.
Recommendations
  • Explicitly state that Azure CLI examples use bash syntax and are suitable for Linux/macOS terminals.
  • Add Linux/macOS-specific notes or troubleshooting tips, especially for manual copy scenarios.
  • Provide sample code or references for manual copy using Linux-native tools (e.g., Python, shell scripts) in addition to .NET.
  • Clarify cross-platform compatibility for each method, especially for PowerShell (which is available on Linux but less commonly used).
  • Consider listing CLI (bash) examples before PowerShell to reduce perceived Windows-first bias.
GitHub Create Pull Request
Virtual Machines Deploy a ZRS managed disk ...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. While Azure CLI examples (which are cross-platform) are provided and shown before PowerShell, the PowerShell sections are extensive and all examples use Windows-centric patterns (e.g., Windows images, Windows admin credentials, Windows-specific VM configuration). Resource Manager template examples are also presented using PowerShell commands and Windows images. There is no explicit Linux/macOS example in PowerShell or ARM template sections, and Windows tooling (PowerShell) is assumed for feature registration and deployment steps.
Recommendations
  • Add PowerShell examples that use Linux images and Linux-style credential setup.
  • Provide bash or shell script equivalents for ARM template deployment and feature registration, or clarify that Azure CLI can be used for these steps.
  • Explicitly mention cross-platform alternatives for all PowerShell commands, especially for feature registration and template deployment.
  • Balance the examples by including Linux/macOS-specific instructions or notes in sections currently focused on Windows.
  • Clarify that Azure CLI is fully supported on Linux/macOS and highlight its parity with PowerShell for these tasks.
GitHub Create Pull Request
Virtual Machines Ultra disks for VMs - Azure managed disks ...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways. In command examples for deploying Ultra Disks using Azure CLI and PowerShell, the VM image used is always 'Win2016Datacenter', with no Linux equivalent shown. The portal instructions link only to the Windows VM quickstart, omitting the Linux VM counterpart. There are no examples or guidance for deploying Ultra Disks with Linux images, nor any Linux-specific configuration or validation steps. This may cause confusion or extra effort for Linux users seeking parity.
Recommendations
  • Provide Linux VM deployment examples alongside Windows, e.g., using Ubuntu or CentOS images in CLI and PowerShell commands.
  • Add links to both Windows and Linux VM quickstart guides in the portal section.
  • Clarify that Ultra Disks are supported for Linux VMs and provide any Linux-specific considerations (e.g., partitioning, formatting, or driver requirements).
  • Ensure screenshots and walkthroughs are not Windows-centric, or provide Linux alternatives where relevant.
GitHub Create Pull Request
Virtual Machines Migrate Standard HDD OS disks by September 08, 2028 ...n/articles/virtual-machines/disks-hdd-os-retirement.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page mentions both Linux and Windows VMs as affected, but when providing examples for listing affected disks, it references Azure PowerShell before Azure CLI, and the PowerShell example is given first. PowerShell is primarily a Windows tool, while Azure CLI is cross-platform. The Disk Storage Center is also a GUI tool that is most familiar to Windows users. There are no Linux-specific command-line examples or shell scripts, and no mention of Linux-native tooling or patterns.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Include bash shell script examples for listing affected disks, demonstrating usage on Linux/macOS.
  • Explicitly mention that Azure CLI works natively on Linux/macOS and provide installation links.
  • Clarify that Disk Storage Center is accessible via browser on any OS, not just Windows.
  • Add a note about using automation tools (e.g., bash, Python) for Linux users to script migrations.
GitHub Create Pull Request
Virtual Machines Deploy a Premium SSD v2 managed disk ...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. VM creation examples consistently use Windows images (e.g., 'Win2016Datacenter') and Windows-style authentication (username/password), with no mention of Linux images or SSH authentication. PowerShell is given equal prominence to Azure CLI, but CLI examples are tailored to Windows VM deployment. There are no explicit Linux-specific examples or guidance for deploying Premium SSD v2 disks with Linux VMs, nor are Linux authentication patterns (SSH keys) covered.
Recommendations
  • Add explicit Linux VM deployment examples using Azure CLI and PowerShell, including common Linux images (e.g., UbuntuLTS, CentOS).
  • Show how to use SSH key authentication for Linux VMs in CLI and PowerShell examples.
  • In variable initialization, provide both Windows and Linux image options, and clarify which parameters are OS-specific.
  • When presenting examples, alternate or parallel Windows and Linux scenarios, or provide a table of common images.
  • Clarify that Azure CLI and PowerShell are cross-platform, and provide notes on usage from Linux/macOS terminals.
  • Ensure portal screenshots and instructions mention Linux VM options where relevant.
GitHub Create Pull Request
Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 (cross-platform) and Azure PowerShell (Windows-centric) examples for creating instant access snapshots, but does not include explicit Linux shell (bash) or macOS-specific examples. The PowerShell example is given equal prominence to the CLI, and the CLI example uses bash syntax but does not clarify Linux/macOS compatibility or provide troubleshooting for those platforms. There are no references to Linux-specific tools or workflows, and the order of examples sometimes places PowerShell before Resource Manager templates, which are platform-neutral. The documentation does not mention any Linux-specific considerations or alternatives for monitoring or scripting.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and provide troubleshooting tips for common platform-specific issues (e.g., quoting, environment variables).
  • Add a dedicated Linux/macOS shell example, clarifying any differences in syntax or prerequisites.
  • Include notes or links for Linux users regarding installation of Azure CLI and authentication methods.
  • Balance example order by listing CLI (cross-platform) first, followed by PowerShell (Windows), and clearly label platform compatibility for each.
  • Mention any Linux-specific tools (e.g., jq for JSON parsing) where relevant.
GitHub Create Pull Request
Virtual Machines Convert a disk from LRS to ZRS ...ain/articles/virtual-machines/disks-migrate-lrs-zrs.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation presents Azure Portal (a GUI often associated with Windows) and Azure PowerShell examples before Azure CLI examples in every major section. PowerShell, a Windows-centric tool, is given equal or greater prominence than Azure CLI, which is more common on Linux/macOS. There are no explicit Linux/macOS-specific instructions, nor are Linux shell patterns (e.g., bash, sh) used in examples. The only mention of Linux is in the final VM creation CLI example, which sets --os-type linux, but this is not explained or highlighted for parity.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is more cross-platform and preferred by Linux/macOS users.
  • Add explicit notes or sections for Linux/macOS users, clarifying that all CLI commands work natively on those platforms.
  • Include bash/sh shell variable syntax in CLI examples (e.g., export, $VAR) instead of PowerShell variable syntax ($var), which may confuse Linux users.
  • Where Portal instructions are given, clarify that the Portal is OS-agnostic and accessible from any browser.
  • Add troubleshooting notes for Linux/macOS users if any step differs from Windows.
  • Consider a dedicated 'Linux/macOS' tab or section if there are platform-specific nuances.
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell and Windows-centric links are referenced first or exclusively in several sections (e.g., custom RBAC role creation, secure uploads with Azure AD). Windows tools and terminology (PowerShell, portal) are mentioned before their Linux equivalents, and some links point to Windows-specific guides before CLI/Linux alternatives. However, Linux/CLI options are generally present, and critical tasks can be completed on Linux/macOS.
Recommendations
  • Provide both PowerShell and CLI examples side-by-side in all relevant sections.
  • Link to Linux/CLI documentation before or alongside Windows/PowerShell documentation.
  • Ensure terminology is platform-neutral (e.g., 'Azure CLI or PowerShell' instead of 'PowerShell').
  • Add explicit Linux/macOS instructions for custom RBAC role creation and other tasks currently referencing only PowerShell.
  • Review all links to ensure parity in depth and clarity between Windows and Linux/macOS guides.
GitHub Create Pull Request
Virtual Machines Share an Azure managed disk across VMs ...cs/blob/main/articles/virtual-machines/disks-shared.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows clustering tools (WSFC, CSV, Scale-Out File Server) are described first and in greater detail, with multiple application examples and links to Windows-specific templates. Linux equivalents (Pacemaker, Corosync, ocfs2, gfs2) are mentioned, but with less depth and fewer practical examples. The 'Sample workloads' section lists several Windows scenarios before Linux, and the 'Examples' section provides more detailed Windows cluster configurations. There are no explicit command-line examples for either platform, but Windows tools and patterns are referenced more prominently.
Recommendations
  • Add Linux-first examples and templates, such as step-by-step guides for configuring Pacemaker/Corosync clusters with Azure shared disks.
  • Provide parity in application scenarios for Linux (e.g., clustered file servers, SAP, database failover) with links to relevant templates or walkthroughs.
  • Include practical Linux command-line examples (e.g., using sg_persist, fence_scsi) for disk reservation and failover operations.
  • Ensure that Linux tools and patterns are described with equal detail and prominence as Windows equivalents.
  • Alternate the order of Windows and Linux sections, or present them side-by-side for direct comparison.
GitHub Create Pull Request
Virtual Machines FAQ Ephemeral OS disks ...in/articles/virtual-machines/ephemeral-os-disks-faq.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed PowerShell script for determining VM support for ephemeral OS disks, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI). This creates friction for non-Windows users, who must translate the script or seek alternative methods. The documentation also references PowerShell and ARM templates before CLI, and does not mention Linux-specific tools or workflows.
Recommendations
  • Provide equivalent Azure CLI and/or Bash script examples for checking VM SKU support for ephemeral OS disks.
  • List cross-platform tools (CLI, REST, Templates) before or alongside PowerShell in all relevant sections.
  • Explicitly mention Linux/macOS compatibility and provide guidance for those platforms.
  • Where scripts are provided, offer both PowerShell and Bash/CLI versions side-by-side.
GitHub Create Pull Request
Virtual Machines Use Application Health extension with Azure Virtual Machines ...ticles/virtual-machines/extensions/health-extension.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation frequently presents Windows-based examples first, especially in REST API and PowerShell sections, and provides more detailed PowerShell instructions for Windows than for Linux. While Azure CLI examples are given for Linux, there is a lack of parity in scripting examples (e.g., no Bash or shell script equivalents for Linux users). The troubleshooting and log location sections do mention Linux, but overall, Windows tools and patterns are prioritized or more thoroughly documented.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which comes first in each section.
  • Provide Bash or shell script examples for Linux users, especially where PowerShell is used for Windows.
  • Expand Linux-specific guidance, such as troubleshooting steps and log analysis, to match the detail given for Windows.
  • Explicitly mention Linux/macOS compatibility and any platform-specific caveats in each relevant section.
  • Ensure that all REST API and Azure CLI examples clearly indicate how to use them for both Linux and Windows VMs, including the correct 'type' property.
GitHub Create Pull Request
Virtual Machines Azure Key Vault VM Extension for Linux ...rticles/virtual-machines/extensions/key-vault-linux.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
While the documentation is focused on the Linux Key Vault VM extension, there are several instances of Windows bias. PowerShell examples are presented before Azure CLI examples in deployment and troubleshooting sections, and PowerShell-specific warnings and patterns are included. References to Windows-centric tools (PowerShell) and links to Windows VM guides appear before or alongside Linux instructions, even though the extension is Linux-specific. This ordering and emphasis may create friction for Linux users who expect bash or CLI-first guidance.
Recommendations
  • Present Azure CLI examples before PowerShell in all deployment and troubleshooting sections, as CLI is cross-platform and native to Linux.
  • Minimize or move PowerShell-specific warnings and notes to a dedicated 'Windows deployment' section or an appendix.
  • Ensure all references to VM identity and Key Vault access policy configuration link to Linux-specific guides or provide Linux CLI instructions.
  • Add explicit bash script examples for common deployment and troubleshooting tasks.
  • Remove or rephrase any references that imply PowerShell is the default or preferred method for Linux VM extension deployment.
GitHub Create Pull Request
Virtual Machines Qualys Cloud Agent Extension for Azure VMs ...ob/main/articles/virtual-machines/extensions/qualys.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 in several sections, and includes a dedicated 'Deploy Cloud Agent via PowerShell' section, which is a Windows-centric tool (even though a Linux PowerShell link is provided). There are no explicit Linux shell or native command-line examples, and the ordering and tool emphasis may create friction for Linux users.
Recommendations
  • Alternate the order of Windows and Linux examples/links in each section, or group them together under neutral headings.
  • Provide native Linux shell (bash) command examples or links, not just PowerShell, for Linux deployments.
  • Clarify in the 'PowerShell' section that PowerShell Core is cross-platform, and provide bash/CLI alternatives where appropriate.
  • Ensure that automation tool examples (e.g., Ansible, Chef, Puppet) include both Windows and Linux usage scenarios.
GitHub Create Pull Request
Virtual Machines Azure FPGA Attestation Service ...machines/field-programmable-gate-arrays-attestation.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides both PowerShell and Bash examples for running attestation scripts, but PowerShell is presented first and in more detail (including monitoring status). The monitoring example is only shown for PowerShell, with no Bash or Linux equivalent. There is a slight emphasis on PowerShell and Windows tools, and some steps (like monitoring) lack Linux/Bash parity.
Recommendations
  • Add Bash/Linux examples for monitoring attestation status, similar to the PowerShell Monitor-Validation.ps1 example.
  • Present Bash and PowerShell examples side-by-side or alternate which is shown first to avoid Windows-first ordering.
  • Clarify that all scripts and commands (including monitoring) are available and supported on Linux/macOS, or provide alternative Bash scripts if not.
  • Explicitly mention Linux/macOS compatibility for all steps, not just initial prerequisites.
  • If PowerShell scripts are required for some steps, provide guidance for installing and using PowerShell on Linux/macOS.
GitHub Create Pull Request
Virtual Machines Azure Write Accelerator ...es/virtual-machines/how-to-enable-write-accelerator.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is the primary scripting example, with detailed, step-by-step scripts provided only for PowerShell. Windows-specific tools (Chocolatey, cmd.exe, PowerShell) are referenced exclusively for installing armclient, with no mention of Linux/macOS alternatives. The PowerShell section precedes Azure CLI and REST API instructions, and the CLI section is brief by comparison. There are no Linux shell (bash) or macOS-specific examples for scripting or tool installation.
Recommendations
  • Provide equivalent bash shell scripts for enabling Write Accelerator using Azure CLI, including disk attachment and update operations.
  • Include instructions for installing armclient on Linux/macOS (e.g., via dotnet, npm, or manual download), not just via Chocolatey.
  • Mention Linux-native package managers (apt, yum, Homebrew) when discussing tool installation, or provide cross-platform installation guidance.
  • Balance the order and depth of examples: present Azure CLI and REST API usage before or alongside PowerShell, and offer parity in example detail.
  • Explicitly call out any OS-specific limitations or differences in the feature, if present.
GitHub Create Pull Request
Virtual Machines Azure VM Image Builder overview ...in/articles/virtual-machines/image-builder-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page generally presents Azure VM Image Builder as supporting both Windows and Linux, but there are several subtle signs of Windows bias. Windows-specific tools (Sysprep, WinRM) and security baselines are mentioned before or more prominently than their Linux equivalents. PowerShell is frequently referenced, sometimes before or in place of Linux-native tools. Some examples and links (e.g., security baseline templates) are Windows-centric, and there are references to Windows-specific features (Azure Hybrid Benefit) without Linux equivalents. Linux examples and tools are present but often secondary.
Recommendations
  • Ensure Linux-specific tools and patterns (e.g., cloud-init, SSH, Linux security baselines) are mentioned with equal prominence and detail as Windows equivalents.
  • Provide Linux-first or parallel examples where Windows examples are given, especially for security, configuration, and registration tasks.
  • Include links to Linux baseline templates and best practices, not only Windows ones.
  • When referencing PowerShell, always provide equivalent Bash/Azure CLI examples and make clear which platforms each applies to.
  • Avoid mentioning Windows tools (Sysprep, WinRM) without also mentioning or explaining the Linux equivalents (cloud-init, SSH).
  • Review the order of examples and tool mentions to avoid consistently listing Windows first.
GitHub Create Pull Request
Virtual Machines Customer intent: As a cloud security administrator, I want to configure Azure Key Vault and Disk Encryption Set so that I can securely manage encryption keys for our managed disks across multiple subscriptions in compliance with security policies. ...-machines-disks-encryption-create-key-vault-powershell.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell cmdlets for all examples and instructions, with no mention of Azure CLI, Bash, or cross-platform alternatives. This creates a strong bias towards Windows environments and users familiar with PowerShell, making it difficult for Linux/macOS users to follow the guide without translating commands themselves.
Recommendations
  • Add equivalent Azure CLI examples for each step, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux/macOS, or link to installation guides for non-Windows platforms.
  • Provide Bash script examples where appropriate, especially for automation scenarios.
  • Reorder examples or provide tabs for PowerShell and CLI, so Linux/macOS users do not feel secondary.
GitHub Create Pull Request
Virtual Machines Create an encrypted image version with customer-managed keys .../articles/virtual-machines/image-version-encryption.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are presented first and in greater detail, with explicit references to Windows tools and APIs (such as Cryptography API: Next Generation). While Azure CLI examples are provided and are cross-platform, the prominence and depth of PowerShell instructions, as well as the use of Windows-centric terminology and links, may create friction for Linux/macOS users. There are no explicit Linux shell (bash) examples, and Windows tools are referenced before their Linux equivalents (if any).
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Add bash shell script examples for common tasks, demonstrating parity with PowerShell workflows.
  • Replace or supplement Windows-specific references (e.g., Cryptography API: Next Generation) with platform-neutral or Linux-relevant cryptographic documentation.
  • Clarify that all CLI commands work on Linux/macOS, and provide troubleshooting tips for non-Windows environments.
  • Where possible, avoid language that assumes a Windows environment (e.g., avoid referencing PowerShell as the default).
GitHub Create Pull Request
Virtual Machines Customer intent: "As an IT administrator managing virtual machines, I want to aggregate OS update statuses and availability states across my machines, so that I can efficiently monitor and ensure the health of my infrastructure." ...es/virtual-machines/includes/azure-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for each query, with PowerShell (a Windows-centric tool) always present and often listed immediately after CLI. There are dedicated sections for Windows Server OS update installation, but Linux-specific queries are less frequent and appear later in the document. There is no mention of Linux-native tools or shell scripting alternatives, and PowerShell is treated as a first-class option throughout, which may create friction for Linux/macOS users who do not use PowerShell. The documentation does not provide bash or shell script equivalents, nor does it discuss Linux-specific patterns outside of a single Linux OS update query.
Recommendations
  • Add bash/shell script examples for each query, especially for Linux/macOS users who may not use PowerShell.
  • Present CLI and PowerShell examples in parallel, or alternate their order to avoid implicit prioritization.
  • Explicitly mention Linux-native tools or alternatives where relevant.
  • Ensure Linux-specific queries (such as OS update installation) are given equal prominence and detail as Windows equivalents.
  • Clarify that Azure CLI is fully cross-platform and highlight its parity for Linux/macOS users.
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
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation lists Azure PowerShell as a primary tool for managing SAS on disks and snapshots, alongside REST API and Azure CLI. PowerShell is a Windows-centric tool, and its mention in every step (checking, revoking, creating SAS) may signal a Windows bias. Additionally, PowerShell is listed before Linux-native alternatives (e.g., Bash scripting with Azure CLI), and no explicit Linux/macOS examples or guidance are provided.
Recommendations
  • Provide explicit Linux/macOS examples using Azure CLI and Bash.
  • Clarify that Azure CLI is cross-platform and highlight its usage for non-Windows users.
  • Reorder tool listings to avoid suggesting Windows tools first, or group them by platform.
  • Add notes or links for installing and using Azure CLI on Linux/macOS.
  • Consider including sample commands for both PowerShell and Bash.
GitHub Create Pull Request
Virtual Machines Customer intent: As a system administrator, I want to hibernate and manage virtual machines using various tools, so that I can optimize resource usage and maintain system performance effectively. ...nes/includes/hibernate-resume-platform-instructions.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided for every operation, often with more detailed output and interaction (e.g., confirmation prompts), while Linux/macOS-specific shell examples are not present. The CLI examples use Azure CLI, which is cross-platform, but there are no bash or shell script examples, nor any mention of Linux-specific considerations. Windows-specific notes (e.g., page file location on C:) are present, but there are no equivalent Linux guest OS configuration notes. PowerShell is given equal or greater prominence than CLI, and Windows terminology/tools are referenced without Linux parity.
Recommendations
  • Add bash or shell script examples for common Linux/macOS workflows, especially for tasks like viewing VM state and managing hibernation.
  • Include Linux guest OS configuration notes for hibernation, similar to the Windows page file note.
  • Ensure that CLI examples explicitly mention their cross-platform nature and provide sample outputs for Linux/macOS terminals.
  • Balance PowerShell and CLI coverage, and avoid giving PowerShell more detailed or interactive examples unless parity is provided for Linux users.
  • Add troubleshooting or configuration tips for Linux-based VMs where relevant.
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
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation lists Azure PowerShell as a primary tool alongside Azure CLI and the portal, but does not provide Linux-specific command examples or mention Linux-native tools. Windows-specific instructions (such as the Windows rescan function) are referenced with direct links, while the Linux equivalent is mentioned but not detailed. The order of presentation often places Windows before Linux, and there is a lack of parity in example depth.
Recommendations
  • Provide explicit Linux command-line examples (e.g., using Azure CLI on Linux, or native disk management commands like 'lsblk', 'fdisk', or 'partprobe').
  • Include step-by-step instructions for Linux disk rescanning, not just a link.
  • Ensure that Linux tools and workflows are described with equal detail and prominence as Windows/PowerShell.
  • Alternate or parallelize the order of Windows and Linux instructions to avoid Windows-first bias.
GitHub Create Pull Request
← Previous Page 7 of 33 Next →