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 401-425 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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. While it claims to apply to both Windows and Linux VMs, several examples and templates (especially the ARM template) are Windows-centric, with Windows images and parameters shown by default. PowerShell is given equal prominence to Azure CLI, but PowerShell is a Windows-first tool. The ARM template only demonstrates Windows VM creation, with no Linux image or configuration example. Password complexity requirements are described in Windows terms. In most sections, Windows tools and patterns (PowerShell, Windows images) are shown before or instead of Linux equivalents.
Recommendations
  • Add explicit Linux VM ARM template examples, including imageReference for popular Linux distributions (e.g., Ubuntu, CentOS).
  • In ARM template parameters, include both Windows and Linux OS options, with clear instructions for each.
  • Clarify password requirements for Linux VMs (e.g., SSH keys) and provide guidance for Linux administrator account setup.
  • In PowerShell sections, note that PowerShell is cross-platform but most users on Linux/macOS will prefer Azure CLI or REST API.
  • Where examples use Windows-centric terminology (e.g., RDP port 3389), add Linux-relevant alternatives (e.g., SSH port 22).
  • Ensure that Linux is represented equally in example code, screenshots, and step-by-step instructions.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine scale set with Uniform Orchestration to a capacity reservation group. ...pacity-reservation-associate-virtual-machine-scale-set.md
Medium 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 exhibits a moderate Windows bias. PowerShell examples are provided for every scenario, and ARM template parameters and variables are heavily focused on Windows (e.g., Windows OS versions, PowerShell DSC, Windows-specific images). There is no equivalent Linux-focused ARM template example, and Windows terminology/tools (PowerShell DSC, WebDeploy) are referenced without Linux alternatives. While Azure CLI examples use Ubuntu images, the ARM template and scripting guidance are Windows-centric, and PowerShell is given equal or greater prominence than CLI. Linux/macOS users may find it less intuitive to adapt the ARM template or automation examples for their environments.
Recommendations
  • Add Linux-focused ARM template examples (e.g., using Ubuntu or other Linux images, removing PowerShell DSC and Windows-specific parameters).
  • Include Bash shell scripting examples alongside PowerShell for automation tasks.
  • Balance the documentation by referencing Linux tools and deployment patterns (e.g., cloud-init, Linux admin username conventions) where appropriate.
  • Clarify that Azure CLI commands work cross-platform and highlight any OS-specific considerations.
  • Provide links or notes for adapting Windows-centric steps (like DSC or WebDeploy) to Linux equivalents (e.g., cloud-init, custom script extensions).
GitHub Create Pull Request
Virtual Machines Share a Capacity Reservation Group in Azure ...s/virtual-machines/capacity-reservation-group-share.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides cross-platform guidance using REST API, Azure CLI, PowerShell, and ARM templates. However, there is a notable bias toward Windows tooling: PowerShell examples are present in every tabbed section, and references to PowerShell commands are frequent. The documentation refers to 'PowerShell' and 'PowerShell-interactive' in example blocks, which are Windows-centric, even though Azure PowerShell is available on Linux/macOS. Additionally, PowerShell examples are consistently shown alongside CLI, sometimes with more detail. There are no explicit Linux/macOS shell examples (e.g., bash scripts), and the CLI examples do not clarify platform differences. The documentation references 'Azure PowerShell' before CLI in some 'Learn more' links, and the overall pattern prioritizes Windows-native tooling.
Recommendations
  • Add explicit bash/sh examples for Linux/macOS users, especially for common tasks.
  • Clarify that Azure PowerShell is cross-platform, and provide installation/use guidance for Linux/macOS.
  • Ensure CLI examples are shown first or in parallel with PowerShell, and highlight CLI as the recommended cross-platform tool.
  • Where PowerShell is referenced, add notes or links for Linux/macOS installation and usage.
  • Consider adding troubleshooting or environment setup notes for Linux/macOS users, especially where PowerShell is involved.
GitHub Create Pull Request
Virtual Machines Configure VM watch ...b/main/articles/virtual-machines/configure-vm-watch.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents PowerShell as a primary method for configuring VM watch, with explicit PowerShell examples and references. While both CLI and ARM template methods are shown, the PowerShell example is given equal prominence, and there is no mention of Linux-specific shell commands (e.g., Bash) or guidance for Linux/macOS users beyond the Azure CLI. The instructions for finding the ARM template code segment reference Visual Studio Code, which is cross-platform but often associated with Windows. The documentation does clarify that the extension type differs for Windows and Linux, but does not provide Linux/macOS-specific command-line examples or troubleshooting tips.
Recommendations
  • Add explicit Bash or shell examples for Linux/macOS users alongside PowerShell.
  • Clarify that Azure CLI works cross-platform and highlight its use for Linux/macOS.
  • Reorder examples to present CLI (cross-platform) before PowerShell.
  • Include troubleshooting or environment notes for Linux/macOS users where relevant.
  • Mention Linux-native editors (e.g., nano, vim) as alternatives to Visual Studio Code.
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-12 00:00
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 PowerShell-specific cmdlets are referenced and linked, which may indicate a bias toward Windows tooling. The CLI examples use Azure CLI, which is cross-platform, but PowerShell is a Windows-centric tool (though available on Linux, it's less commonly used there). The documentation references PowerShell commands and links to their docs, but does not mention Bash, shell scripting, or Linux-native alternatives. In several places, PowerShell examples and references appear before or alongside CLI, but never after Linux-specific examples, and no Linux-specific tools or patterns are discussed.
Recommendations
  • Add Bash or shell scripting examples for Linux users, especially for tasks that can be performed with REST API or Azure CLI.
  • Clarify that Azure CLI is cross-platform and recommend it as the primary automation tool for Linux/macOS users.
  • Reduce emphasis on PowerShell by moving PowerShell sections after CLI, or by explicitly noting PowerShell's cross-platform availability.
  • Include notes or links to Linux/macOS-specific documentation or troubleshooting guides.
  • Where PowerShell cmdlets are referenced, also provide equivalent CLI or REST API references.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides parity between Azure Portal, CLI, PowerShell, and REST API for managing VM deletion options. However, there is a notable Windows bias: PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. REST API examples use Windows-specific images and OS types, and the FAQ and example sections reference Windows terminology and tools before Linux equivalents. The CLI examples are cross-platform, but Linux-specific scenarios are not highlighted, and Linux terminology is largely absent.
Recommendations
  • Add explicit Linux/macOS shell examples (e.g., bash) where appropriate, especially for CLI usage.
  • In REST API examples, use both Windows and Linux images and OS types to demonstrate parity.
  • In FAQ and example sections, mention Linux scenarios and terminology alongside Windows.
  • Clarify that PowerShell is primarily for Windows users and recommend CLI for Linux/macOS users.
  • Provide links to Linux-focused documentation sections within the main content, not just in 'Next steps'.
GitHub Create Pull Request
Virtual Machines Create Virtual Machine restore points ...ain/articles/virtual-machines/create-restore-points.md
Medium 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 demonstrates a moderate Windows bias. Windows and PowerShell are mentioned before Linux and CLI alternatives, with PowerShell links and references given more prominence. There is no example or explicit guidance for Linux users (e.g., Bash, Azure CLI), and Windows-specific terminology (application consistency) is explained in more detail than Linux equivalents (file system consistency). The page lacks parity in examples and tool recommendations for Linux/macOS users.
Recommendations
  • Add explicit Azure CLI and Bash examples alongside PowerShell for all API operations.
  • Mention Linux/macOS tools and workflows equally, and provide direct links to CLI documentation before or alongside PowerShell.
  • Clarify consistency modes for both Windows and Linux, and provide examples for each.
  • Reorder references so that CLI and PowerShell are presented together, or CLI first if targeting cross-platform users.
  • Include a section or tip specifically for Linux/macOS users outlining recommended tools and steps.
GitHub Create Pull Request
Virtual Machines Migrate from Azure Disk Encryption to encryption at host ...n/articles/virtual-machines/disk-encryption-migrate.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, manage-bde) and examples are often presented first or in greater detail, while Linux instructions are sometimes less explicit or relegated to comments. PowerShell is used heavily for both general and Linux scenarios, and Windows domain join/removal steps are more detailed than Linux equivalents. Some Linux migration steps (especially for encrypted OS disks) rely on external links or generic file transfer methods, rather than providing step-by-step parity with Windows. Windows-centric terminology and tools (e.g., manage-bde, Remove-Computer) are emphasized, and Linux alternatives are not always equally described.
Recommendations
  • Present Linux and Windows examples side-by-side, with equal detail and prominence.
  • Provide explicit Linux command-line examples (bash, CLI) for all major steps, not just PowerShell or comments.
  • Expand Linux domain join/removal instructions with concrete commands and troubleshooting tips.
  • Avoid presenting Windows steps or tools first; alternate or group by OS.
  • Include more Linux-specific troubleshooting and verification steps (e.g., checking dm-crypt status, SELinux/AppArmor considerations).
  • Ensure all PowerShell examples for Linux are matched with native Linux shell alternatives.
GitHub Create Pull Request
Virtual Machines Server-side encryption of Azure managed disks ...blob/main/articles/virtual-machines/disk-encryption.md
Medium 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 Minor Windows Reference
Summary
The documentation generally maintains parity between Windows and Linux, referencing both Azure PowerShell and Azure CLI for most tasks. However, there are several instances of Windows bias: Windows/PowerShell links and examples are consistently listed before Linux/CLI equivalents, and references to Windows-specific technologies (e.g., BitLocker, Cryptography API: Next Generation) appear without equal prominence for Linux alternatives. Some sections link only to Windows-specific articles for key tasks (e.g., automatic key rotation), and PowerShell is mentioned before CLI in revoking access instructions.
Recommendations
  • Alternate the order of Windows and Linux examples/links to avoid consistently listing Windows first.
  • Ensure all critical tasks (such as enabling automatic key rotation) have direct Linux/CLI documentation links, not just Windows/PowerShell.
  • When referencing Windows technologies (e.g., BitLocker, CNG), also mention Linux equivalents (e.g., dm-crypt, cryptsetup) with equal detail.
  • Where possible, provide cross-platform code samples or clarify that both PowerShell and CLI are supported for all operations.
  • Review and update references to ensure Linux users are not directed to Windows-specific articles for core workflows.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is heavily used in Resource Manager Template and prerequisite sections, with no Bash or cross-platform alternatives. Windows-centric tools and patterns (e.g., ConvertTo-SecureString, PSCredential, Windows image references) are present throughout PowerShell and ARM template examples. In the PowerShell sections, only Windows VM creation is shown, with no Linux VM examples. The ARM template and feature registration steps use PowerShell exclusively, omitting Azure CLI or REST API equivalents. While Azure CLI examples use Linux images, the PowerShell and ARM template tabs are Windows-focused and shown before any Linux alternatives.
Recommendations
  • Add Bash and Azure CLI equivalents for feature registration and ARM template deployment steps.
  • Include Linux VM creation examples in PowerShell and ARM template sections.
  • Provide REST API examples for feature registration and disk creation.
  • Ensure examples for both Windows and Linux are present and balanced in all tabs.
  • Explicitly note cross-platform alternatives where PowerShell is used.
  • Reorder examples so that Linux and Windows are presented with equal prominence.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently provides examples using Windows images (Win2016Datacenter) in CLI and PowerShell commands, and references Windows-specific quickstarts for portal deployment. There are no explicit Linux VM examples or instructions for deploying Ultra Disks with Linux images, nor are there links to Linux-specific quickstarts. This creates friction for Linux users, who must infer how to adapt the instructions for their platforms.
Recommendations
  • Add Linux VM examples alongside Windows examples in CLI and PowerShell sections (e.g., use Ubuntu or RHEL images).
  • Include links to Linux VM quickstart documentation in the portal deployment instructions.
  • Explicitly mention any differences or considerations for Linux VMs when deploying or managing Ultra Disks.
  • Ensure parity in screenshots and walkthroughs for both Windows and Linux VM creation flows.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for creating instant access snapshots, but does not include explicit Linux/macOS shell examples or mention Linux-specific considerations. The PowerShell example is given equal prominence to Azure CLI, and no bash-specific or Linux-native instructions are provided. There is no mention of Linux tools or patterns, and the CLI examples use syntax compatible with bash but do not clarify Linux/macOS usage or differences.
Recommendations
  • Add explicit bash/Linux/macOS shell examples for CLI commands, including variable declaration and command usage in those environments.
  • Clarify that Azure CLI commands are cross-platform and provide any necessary notes for Linux/macOS users (e.g., environment variable syntax differences, authentication methods).
  • Include troubleshooting or usage notes for Linux users, such as file permissions, shell compatibility, or installation instructions for Azure CLI on Linux/macOS.
  • Consider adding a table or section comparing Azure CLI and PowerShell usage on different platforms.
  • Ensure that Linux/macOS users are addressed in introductory sections to reinforce parity.
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-12 00:00
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 Windows bias in several ways: VM creation examples consistently use Windows images (e.g., 'Win2016Datacenter'), variable names and credential handling are tailored to Windows conventions, and PowerShell is given equal prominence to Azure CLI throughout. There are no explicit Linux VM creation examples, nor are Linux-specific considerations (such as SSH authentication or Linux images) discussed. This may cause friction for Linux/macOS users, who must adapt Windows-centric instructions to their platforms.
Recommendations
  • Add explicit Linux VM creation examples using common Linux images (e.g., UbuntuLTS) in Azure CLI and PowerShell sections.
  • Include authentication examples using SSH keys for Linux VMs, rather than only password-based authentication.
  • Clarify cross-platform usage of Azure CLI, emphasizing that it works natively on Linux/macOS.
  • Balance PowerShell and CLI coverage, noting that PowerShell is primarily a Windows tool, while CLI is cross-platform.
  • Adjust variable names and credential handling to be platform-neutral or provide both Windows and Linux variants.
GitHub Create Pull Request
Virtual Machines Enable shared disks for Azure managed disks .../main/articles/virtual-machines/disks-shared-enable.md
Medium 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 both Azure CLI and PowerShell examples for all disk types and operations, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections (such as 'Share an existing disk' and 'Using Azure shared disks with your VMs'), PowerShell examples are shown before CLI. There are no Linux-specific shell examples (e.g., Bash), nor are there any Linux/macOS-specific notes or guidance. The documentation assumes parity between CLI and PowerShell, but PowerShell is a Windows-first tool, and its prominence may create friction for Linux/macOS users.
Recommendations
  • Always present Azure CLI examples before PowerShell, as CLI is cross-platform and native to Linux/macOS.
  • Add explicit Bash shell examples where appropriate, especially for mounting disks to Linux VMs.
  • Include notes or links for Linux/macOS users on how to install and use Azure CLI.
  • Provide guidance or examples for disk attachment and SCSI PR commands using Linux tools (e.g., sg_persist, multipath).
  • Clarify that PowerShell is optional and not required for Linux/macOS users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation shows moderate Windows bias. Windows clustering (WSFC) and related tools are described first and in greater detail, with explicit links to Windows-specific guides and templates. Linux support is mentioned, but Linux examples are less detailed, and there are no step-by-step Linux configuration examples. The 'Examples' section provides detailed Windows (WSFC) scenarios before Linux, and Linux examples lack equivalent depth. Windows tools and patterns (e.g., WSFC, CSV) are referenced more prominently than Linux equivalents (e.g., Pacemaker, Corosync).
Recommendations
  • Add step-by-step Linux configuration examples, similar to those provided for Windows (e.g., setting up Pacemaker/Corosync with shared disks).
  • Provide Linux-first or parallel examples in the 'Examples' section to balance the order and depth of coverage.
  • Include links to official Linux HA cluster documentation and templates, as is done for Windows.
  • Explicitly mention and provide guidance for Linux-specific tools (e.g., sg_persist, fence_scsi) in the context of Azure shared disks.
  • Ensure parity in the level of detail for both Windows and Linux sections, especially for common workloads and deployment scenarios.
GitHub Create Pull Request
Virtual Machines What's new in Azure Disk Storage ...blob/main/articles/virtual-machines/disks-whats-new.md
Medium 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 page is primarily a feature update summary and does not provide detailed code examples. However, there is evidence of Windows bias in the form of Windows documentation links being presented before Linux equivalents, references to Windows-specific tools (PowerShell), and some update links pointing only to Windows guides. Linux/macOS parity is not always clear, and in some cases, Linux documentation is referenced after Windows, or not at all.
Recommendations
  • Ensure that all feature documentation and how-to guides are linked for both Windows and Linux/macOS users, ideally side-by-side.
  • Avoid listing Windows documentation links before Linux equivalents; use a neutral or alphabetical order.
  • Where PowerShell or Windows tools are mentioned, also mention Linux/macOS equivalents (e.g., Bash, Azure CLI) and provide links.
  • Audit all referenced documentation to ensure Linux/macOS users can complete tasks without friction.
  • Add explicit statements about cross-platform support for new features where relevant.
GitHub Create Pull Request
Virtual Machines Deploy Ephemeral OS disks ...articles/virtual-machines/ephemeral-os-disks-deploy.md
Medium 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 provides both Windows and Linux support in principle, but several sections show Windows bias. PowerShell examples are given in detail, while no Linux-specific shell examples (e.g., Bash) are provided. Template examples use Windows images by default, and admin credentials are shown as username/password rather than SSH keys. Windows tools (PowerShell) are covered in a dedicated section, while Linux equivalents (e.g., Bash scripting, cloud-init) are missing. The CLI section is neutral, but overall, Windows patterns and tools are prioritized.
Recommendations
  • Add explicit Linux VM template examples using popular Linux images (e.g., Ubuntu, CentOS) and SSH key authentication.
  • Provide Bash or shell scripting equivalents for PowerShell commands, especially for VM and scale set deployments.
  • Include Linux-specific guidance for admin credential setup (e.g., using --generate-ssh-keys in CLI, cloud-init for customization).
  • Balance the order of examples so that Linux and Windows are equally represented, or alternate which comes first.
  • Add notes or links to Linux admin tooling and best practices for ephemeral OS disk deployments.
GitHub Create Pull Request
Virtual Machines Use Azure Storage Explorer to manage Azure managed disks ...l-machines/disks-use-storage-explorer-managed-disks.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page describes using Azure Storage Explorer, a cross-platform GUI tool, to manage Azure managed disks. While the main instructions are platform-neutral, the 'Next steps' section exclusively links to Windows VM scenarios and does not provide Linux equivalents. There are no Linux-specific examples or guidance, and Windows is implicitly prioritized in follow-up tasks.
Recommendations
  • Add 'Next steps' links for Linux VM scenarios, such as creating a VM from a VHD or attaching a managed disk to a Linux VM.
  • Ensure parity in example tasks and follow-up documentation for both Windows and Linux users.
  • Explicitly mention that Azure Storage Explorer is available on Linux/macOS and provide installation instructions for those platforms if not already present.
  • Where relevant, include screenshots or notes for Linux/macOS versions of the tool to reassure non-Windows users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
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). PowerShell is featured exclusively and prominently, creating friction for non-Windows users. The mention of CLI is generic and lacks concrete examples.
Recommendations
  • Add equivalent Azure CLI (bash) examples/scripts for checking VM SKU support for ephemeral OS disks.
  • Present CLI and PowerShell examples side-by-side or in parallel sections to ensure parity.
  • Explicitly mention cross-platform alternatives and clarify which commands/tools work on Linux/macOS.
  • Consider providing downloadable scripts in both PowerShell and Bash formats.
GitHub Create Pull Request
Virtual Machines Export Azure resource groups that contain VM extensions ...ticles/virtual-machines/extensions/export-templates.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows tools and patterns first and most prominently. The sample deployment scripts generated by the export process are described as 'PowerShell and Azure CLI scripts', with PowerShell mentioned first and no explicit mention of Bash or Linux shell scripts. The ms.collection metadata is set to 'windows', and the list of supported extensions names Windows versions before Linux equivalents. There are no explicit Linux/macOS-specific instructions or examples, and no screenshots or walkthroughs for Linux users.
Recommendations
  • Mention Bash or Linux shell script samples alongside PowerShell and Azure CLI, and provide explicit examples for Linux/macOS users.
  • Ensure extension lists alternate or group Windows and Linux versions equally, rather than listing Windows first.
  • Add screenshots or step-by-step instructions for Linux/macOS users where UI or CLI differences exist.
  • Update metadata (ms.collection) to include Linux if the content is cross-platform.
  • Clarify that Azure CLI is cross-platform and provide examples of its use on Linux/macOS.
GitHub Create Pull Request
Virtual Machines Azure support for Generation 2 VMs ...cs/blob/main/articles/virtual-machines/generation-2.md
Medium 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 displays moderate Windows bias. Windows examples and PowerShell commands are presented before Linux equivalents, and some critical steps (such as uploading and creating managed disks from .vhd files) are only shown using Windows/PowerShell tooling, with no Linux CLI or cross-platform alternatives. References to Hyper-V and Windows-centric features appear more frequently and are linked before Linux resources. While Linux support is mentioned and some CLI examples are provided, Linux users may encounter friction due to missing or less prominent Linux-specific guidance.
Recommendations
  • Provide equivalent Linux examples for all PowerShell commands, especially for tasks like creating managed disks from .vhd files (e.g., using Azure CLI or REST API).
  • Ensure Linux and Windows examples are presented with equal prominence, ideally side-by-side or in parallel sections.
  • Include references to Linux-specific documentation and tools where appropriate, not just Windows/Hyper-V.
  • When listing supported images or features, alternate the order or group by OS type to avoid Windows-first presentation.
  • Add explicit instructions for Linux users in sections where only Windows/PowerShell guidance is given.
GitHub Create Pull Request
Virtual Machines Tenable One-Click Nessus Extension for Azure VMs ...b/main/articles/virtual-machines/extensions/tenable.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only PowerShell command-line examples for deploying the Nessus Agent extension, which is primarily a Windows-centric tool. No Linux-native CLI examples (such as Azure CLI or Bash) are provided, and the command-line section is introduced as 'PowerShell' without mentioning alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Bash/Azure CLI. Additionally, the command-line instructions and parameter descriptions are presented from a Windows/PowerShell perspective.
Recommendations
  • Add equivalent Azure CLI (az vm extension set) examples for Linux/macOS users.
  • Explicitly mention that PowerShell is available cross-platform, but provide Bash/Azure CLI alternatives for users who prefer native Linux tools.
  • Reorder or parallelize examples so that Linux and Windows approaches are presented with equal prominence.
  • Clarify any platform-specific requirements or limitations in the deployment process.
GitHub Create Pull Request
Virtual Machines Azure FPGA Attestation Service ...machines/field-programmable-gate-arrays-attestation.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both PowerShell and Bash script examples for attestation, but PowerShell is presented first and in greater detail (including monitoring and validation steps). The Bash example is less complete, lacking explicit instructions for monitoring attestation status. There is a notable emphasis on PowerShell tooling and scripts, with some post-validation steps and monitoring only described for PowerShell, leaving Linux/macOS users without equivalent guidance.
Recommendations
  • Provide Bash/Linux equivalents for all PowerShell scripts, especially for monitoring attestation status (e.g., a Bash script or curl command for polling status).
  • Present Bash and PowerShell examples side-by-side, or alternate which is shown first, to avoid implicit prioritization of Windows.
  • Explicitly mention how Linux/macOS users can perform all steps, including post-validation and error checking.
  • Clarify that all scripts and tools are cross-platform, and highlight any platform-specific limitations.
  • Add troubleshooting and support instructions for Linux/macOS users.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. The PowerShell method is presented first and in greatest detail, with multiple example scripts and cmdlet explanations. The REST API section requires installing armclient via Chocolatey, a Windows-only package manager, with instructions only for Windows (cmd.exe/PowerShell). There are no Linux/macOS installation alternatives for armclient. While Azure CLI and portal methods are included and are cross-platform, the CLI section is brief and lacks step-by-step examples compared to PowerShell. Windows disk management tools are mentioned before Linux equivalents in planning guidance.
Recommendations
  • Provide Linux/macOS installation instructions for armclient, or recommend a cross-platform REST client (e.g., curl, httpie) with example commands.
  • Expand Azure CLI examples to match the detail and scenarios covered in the PowerShell section, including step-by-step scripts.
  • When listing disk/volume managers, alternate or balance the order between Windows and Linux tools.
  • Explicitly note cross-platform compatibility for all tooling and commands.
  • Consider adding Bash or shell script examples for Linux users where appropriate.
GitHub Create Pull Request
Virtual Machines Create an image definition and image version ...s/blob/main/articles/virtual-machines/image-version.md
Medium 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 provides parity between Windows and Linux in most CLI and REST examples, but PowerShell examples are Windows-centric, and Windows terminology (Sysprep, PowerShell cmdlets) is mentioned before Linux equivalents. The PowerShell tab focuses on Windows scenarios, with Linux only briefly referenced. Windows tools and patterns (Sysprep, PowerShell) are mentioned before Linux equivalents (waagent).
Recommendations
  • Provide explicit Linux-focused PowerShell examples (e.g., using -OsType Linux and Linux-specific preparation steps).
  • Ensure Linux preparation steps (waagent) are mentioned alongside or before Windows (Sysprep) in all relevant sections.
  • Balance example order so Linux and Windows are presented equally, or alternate which is shown first.
  • Add notes or links for Linux users in PowerShell sections, clarifying how to adapt commands for Linux images.
  • Where Windows tools (Sysprep, PowerShell) are referenced, ensure Linux alternatives are equally described and linked.
GitHub Create Pull Request
← Previous Page 17 of 33 Next →