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 26-50 of 818 flagged pages
Virtual Machines
AMD GPU Driver Extension - Azure Linux VMs
...irtual-machines/extensions/hpccompute-amd-gpu-linux.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page is focused on Linux VMs and AMD GPU drivers, but it presents Windows-centric tools (PowerShell) alongside Linux-native tools (Azure CLI) for extension deployment and troubleshooting. PowerShell examples are given equal prominence to Azure CLI, and PowerShell is mentioned before Azure CLI in several sections. There is no explicit Linux shell scripting example (e.g., Bash), and some troubleshooting steps reference PowerShell before CLI. The documentation does not exclusively use Windows tools, but the inclusion and ordering of PowerShell may signal a subtle Windows bias.
Recommendations
- Prioritize Azure CLI and Bash examples before PowerShell in all sections, as CLI is cross-platform and native to Linux.
- Add explicit Bash shell scripting examples for common tasks (e.g., checking extension status, parsing logs).
- Clarify that PowerShell is optional and primarily for users on Windows, while Azure CLI is recommended for Linux users.
- Ensure troubleshooting and deployment instructions are Linux-first, with Windows tools mentioned only as alternatives.
- Review and update screenshots and UI references to ensure they reflect Linux usage where possible.
Create Pull Request
Virtual Machines
Use Azure Policy to restrict VM extension installation (Windows)
...al-machines/extensions/extensions-rmpolicy-howto-ps.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, with all examples and instructions using Azure PowerShell and referencing Windows VM extensions. There are no Linux-specific examples, nor is there mention of using Azure CLI or Bash. The customer intent, article title, and collection metadata all reinforce a Windows-centric approach, and Linux VM extension management is not addressed.
Recommendations
- Add equivalent examples for Linux VMs, including how to restrict Linux-specific extensions.
- Provide Azure CLI and Bash examples alongside PowerShell to support cross-platform usage.
- Clarify which steps are universal and which are Windows-specific; consider splitting content into Windows and Linux sections.
- Update metadata and customer intent to reflect support for both Windows and Linux environments.
- Mention Linux troubleshooting tools and extension types where relevant.
Virtual Machines
Convert managed disks storage between different disk types
.../main/articles/virtual-machines/disks-convert-types.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell (a Windows-centric tool) is consistently presented before Azure CLI in code example tabs, and PowerShell scripts are shown in full detail. The use of PowerShell as a primary automation example can be intimidating or less relevant for Linux users, even though Azure CLI is cross-platform. References to converting unmanaged disks mention both CLI and PowerShell, but the PowerShell link is listed second in one place and first in another. There is no explicit Linux shell scripting (bash) example, and the overall structure and language tend to favor Windows tools and patterns.
Recommendations
- Alternate the order of PowerShell and CLI examples so that CLI is presented first in some sections, especially those relevant to Linux users.
- Add explicit bash scripting examples for common disk conversion tasks to improve accessibility for Linux administrators.
- Clarify that Azure CLI is cross-platform and suitable for both Windows and Linux environments.
- Where PowerShell is used, note its availability on Linux and macOS, but also provide native bash alternatives.
- Ensure that references to conversion guides (unmanaged to managed disks) mention Linux/CLI first or equally.
- Consider adding a short section or callout for Linux-specific considerations or best practices.
Virtual Machines
Create a Gallery for Sharing Resources
.../blob/main/articles/virtual-machines/create-gallery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. However, PowerShell is a Windows-centric tool and is presented as a primary automation option alongside CLI, without any mention of Linux shell scripting or native Linux tools. There are no explicit Linux/Bash examples (e.g., using Bash variables, scripting patterns, or references to Linux environments), and the PowerShell example is more detailed than the CLI example. This may give the impression of Windows preference and insufficient Linux parity.
Recommendations
- Add explicit Bash/Linux shell examples for each CLI scenario, using Bash variables and scripting patterns.
- Clarify that Azure CLI commands work cross-platform and provide sample Bash scripts for Linux users.
- Balance the detail level between PowerShell and CLI examples, ensuring CLI/Bash examples are as comprehensive as PowerShell ones.
- Mention Linux-native automation tools or scripting environments where relevant.
- Consider adding a note about cross-platform support for Azure CLI and REST API.
Virtual Machines
Create Virtual Machine restore points
...ain/articles/virtual-machines/create-restore-points.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-specific consistency features more prominently than Linux equivalents. PowerShell is mentioned as a primary tool for interacting with restore points, while Linux tools or CLI examples are less visible or absent. Application consistency is highlighted for Windows VMs, whereas Linux VMs are only mentioned in the context of file system consistency. There are no explicit Linux or cross-platform command-line examples provided, and Windows tools are referenced before Linux alternatives.
Recommendations
- Provide equivalent CLI (az CLI) examples alongside PowerShell for all operations, ensuring Linux users have clear guidance.
- Explicitly mention Linux support and parity in restore point features, including any limitations or differences.
- Add bash shell and REST API usage examples that can be run on Linux systems.
- Ensure documentation references Linux tools and workflows as frequently and prominently as Windows/PowerShell ones.
- Clarify any differences in consistency modes between Windows and Linux VMs, and provide guidance for both.
Virtual Machines
Delete a VM and attached resources
...ute-docs/blob/main/articles/virtual-machines/delete.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. However, PowerShell examples are given equal prominence to CLI, despite PowerShell being primarily a Windows tool. REST API examples often use Windows-centric values (e.g., Windows images, Windows admin settings) and do not show Linux-specific configurations. There are no explicit Linux shell (bash) examples, nor are Linux-specific patterns or considerations discussed. The FAQ and main content do not mention Linux-specific behaviors, and Windows terminology (e.g., 'MicrosoftWindowsServer', 'osType': 'Windows') appears in sample payloads before any Linux equivalent. The only reference to Linux is in the 'Next steps' section, which links to a Linux tutorial, but this is not integrated into the main instructional content.
Recommendations
- Add explicit Linux shell (bash) examples alongside PowerShell, especially for common VM management tasks.
- In REST API examples, alternate between Windows and Linux image references, or provide both in parallel.
- Include Linux-specific configuration details (e.g., 'osType': 'Linux', Linux admin settings) in sample payloads.
- Discuss any differences in delete behavior or resource management for Linux VMs, if applicable.
- Ensure that CLI examples use Linux-friendly patterns (e.g., bash syntax, environment variables) and clarify cross-platform usage.
- Balance the order of presentation so that Linux and Windows are treated equally (e.g., alternate which is shown first in examples or explanations).
Virtual Machines
Enable end-to-end encryption using encryption at host - Azure portal - managed disks
...-machines/disks-enable-host-based-encryption-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell (typically Windows-centric) examples before Azure CLI (cross-platform) in all command sections, referencing PowerShell modules and a 'managed-disks-powershell-getting-started' sample repository in 'Next steps', and mentioning Windows tools and patterns more prominently. While Linux is marked as supported, there are no Linux-specific examples, screenshots, or workflow notes, and the portal instructions do not differentiate between Windows and Linux VM deployment nuances.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to emphasize cross-platform parity.
- Include Linux-specific deployment notes or screenshots, especially where VM configuration may differ.
- Reference Linux-focused sample repositories or documentation in the 'Next steps' section.
- Explicitly mention any differences or considerations for Linux VMs in relevant sections.
- Ensure that all command-line instructions are clearly marked as cross-platform where applicable.
Virtual Machines
Migrate Standard HDD OS disks by September 08, 2028
...n/articles/virtual-machines/disks-hdd-os-retirement.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page mentions both Linux and Windows VMs as affected, but the example commands and tooling references prioritize Windows-centric tools and patterns. The Azure PowerShell module is mentioned before Azure CLI, and the PowerShell example is given in detail, while the CLI example is less prominent. The Disk Storage Center, a GUI tool familiar to Windows users, is referenced first for listing disks, with CLI and PowerShell as alternatives. There are no Linux-specific migration examples or guidance.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more familiar to Linux users.
- Include Linux-specific migration steps or considerations, such as scripting with Bash or using Linux-native tools.
- Explicitly mention that all commands can be run from Linux, macOS, or Windows, and provide sample Bash scripts for disk listing and migration.
- Balance references to GUI tools (Disk Storage Center) with command-line alternatives, and clarify their cross-platform availability.
- Add troubleshooting or migration tips relevant to Linux VMs, such as handling fstab updates or GRUB bootloader changes after disk migration.
Virtual Machines
Instantly access managed disk snapshots
...les/virtual-machines/disks-instant-access-snapshots.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, Portal, and Resource Manager templates, but does not include explicit Linux shell (bash) or cross-platform scripting examples. Azure PowerShell is featured prominently, which is traditionally associated with Windows environments. There are no references to Linux-specific tools, nor are there instructions or examples tailored for Linux users (e.g., bash scripts, Linux authentication patterns). The ordering of examples often places PowerShell before Portal or Resource Manager, and there is no mention of Linux-specific considerations or troubleshooting.
Recommendations
- Add explicit bash shell examples for Linux users, including variable declaration and command execution.
- Clarify that Azure CLI commands are cross-platform and provide sample usage in both Windows (cmd/PowerShell) and Linux (bash) environments.
- Include troubleshooting notes or tips for common Linux scenarios (e.g., authentication, file permissions, environment variables).
- Ensure example ordering alternates or starts with cross-platform tools (Azure CLI) before Windows-specific tools (PowerShell).
- Mention that Azure PowerShell is available on Linux, but provide guidance for native Linux shell users.
- Add notes about using the Azure CLI in Linux distributions and any differences in output formatting or environment setup.
Virtual Machines
Restrict managed disks from being imported or exported
...tual-machines/disks-restrict-import-export-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows-specific tools and links before their Linux/CLI equivalents. The custom RBAC role creation links directly to a PowerShell-based guide, and in several sections, PowerShell is mentioned before CLI or Linux alternatives. There is a general tendency to present Windows/PowerShell options first or exclusively, with less emphasis on Linux-native tools and workflows.
Recommendations
- Provide equal prominence to Linux/CLI examples and documentation links alongside PowerShell/Windows options.
- When referencing guides or articles, alternate the order (e.g., CLI before PowerShell) or list both together.
- Include explicit Linux shell examples for key operations, not just CLI references.
- Ensure that custom role creation and other administrative tasks have clear, step-by-step instructions for both PowerShell and CLI/bash environments.
- Audit linked articles to verify Linux parity and update them if necessary.
Virtual Machines
What's new in Azure Disk Storage
...blob/main/articles/virtual-machines/disks-whats-new.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Several feature explanations and links reference Windows-specific documentation before Linux equivalents, and some links point only to Windows or PowerShell-centric articles (e.g., expand disks, find unattached disks). In some cases, Linux examples or documentation are missing or referenced after Windows, and Windows tools like PowerShell are mentioned without equal mention of Linux alternatives.
Recommendations
- Ensure all feature explanations provide both Windows and Linux usage examples, with equal prominence.
- When linking to platform-specific guides (e.g., expanding disks, finding unattached disks), always include both Windows and Linux links side-by-side.
- Avoid referencing Windows tools (e.g., PowerShell) exclusively; mention Linux CLI equivalents (e.g., Bash, Azure CLI) in parallel.
- Audit all documentation links to ensure Linux parity, updating or adding Linux-focused articles where missing.
- Consider alternating the order of Windows and Linux references to avoid implicit prioritization.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides a detailed PowerShell script as the sole example for determining VM support for ephemeral OS disks, without offering equivalent examples for Linux users (e.g., Bash/CLI). PowerShell is a Windows-centric tool, and its exclusive use here prioritizes Windows workflows. Additionally, the mention of 'ARM template deployment/PowerShell/CLI' lists PowerShell before CLI, subtly reinforcing Windows-first patterns. There are no Linux/Bash examples or references to Linux-native tooling.
Recommendations
- Provide equivalent Bash/Azure CLI script examples for Linux users to determine VM support for ephemeral OS disks.
- When listing automation options, alternate or randomize the order (e.g., CLI, PowerShell, ARM template) to avoid Windows-first bias.
- Explicitly mention that all operations can be performed using Azure CLI/Bash on Linux, and link to relevant documentation.
- Add a note or section highlighting cross-platform support and parity for ephemeral OS disk management.
Virtual Machines
Share an Azure managed disk across VMs
...cs/blob/main/articles/virtual-machines/disks-shared.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows clustering tools (WSFC) and workloads are described first and in greater detail, with explicit references to Windows-specific features (CSV, Scale-Out File Server, RDS UPD, etc.) and links to Windows-centric guides. Linux support is mentioned, but Linux examples are less detailed, and there are no step-by-step Linux configuration examples or explicit Linux command-line instructions. Windows tools and patterns (WSFC, CSV) are referenced before their Linux equivalents (Pacemaker, Corosync, ocfs2, gfs2), and the examples section provides more concrete Windows scenarios than Linux ones.
Recommendations
- Provide step-by-step Linux configuration examples, including commands for setting up Pacemaker/Corosync clusters and using SCSI PR utilities (e.g., sg_persist, fence_scsi).
- Balance the sample workloads section by including more detailed Linux application scenarios (e.g., clustered file servers, SAP on Linux, machine learning clusters) with links to relevant guides.
- Ensure that Linux tools and patterns (Pacemaker, Corosync, ocfs2, gfs2) are described with equal prominence and detail as Windows equivalents.
- Add explicit Linux command-line examples for disk reservation and failover flows.
- Where possible, present Windows and Linux examples in parallel, rather than listing Windows first.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page generally maintains parity between Windows and Linux, but there are subtle signs of Windows bias. Windows-specific details (e.g., page file placement, cache sizing for Windows images) are presented before or in more detail than Linux equivalents. PowerShell is mentioned before CLI in the customer-managed key section, and the example for cache placement only references Windows Server images, while Linux (Ubuntu) is only mentioned for temp/NVMe placement. There are no explicit Linux command examples, and some technical details (like page file placement) are only described for Windows.
Recommendations
- Provide Linux-specific technical details where Windows details are given (e.g., swap file placement for Linux).
- Ensure Linux examples are presented alongside Windows examples, especially in sections discussing disk sizing and placement.
- Mention CLI and Linux tools before or alongside PowerShell, or provide equal prominence.
- Add explicit Linux command examples (e.g., Azure CLI commands for Linux VM configuration) where PowerShell is referenced.
- Clarify any differences in ephemeral disk behavior for Linux VMs, not just Windows.
Virtual Machines
Azure Linux VM Agent Overview
...in/articles/virtual-machines/extensions/agent-linux.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows Reference
Windows First
Summary
The documentation is generally Linux-focused, but there is evidence of Windows bias. Windows tools (putty.exe) are mentioned as a consideration for SSH key types, and a Windows tutorial is referenced before any Linux equivalent in the Ubuntu Cloud Images section. The mention of System Center Virtual Machine Manager deployments is also Windows-centric, though contextually relevant. No Linux command-line examples (e.g., installation commands) are provided, and the only external tutorial link is for Windows VM deployment.
Recommendations
- Add Linux-specific SSH client recommendations (e.g., OpenSSH, MobaXterm) alongside putty.exe, and clarify platform differences.
- Provide Linux command-line examples for installing, configuring, and managing waagent (e.g., apt, yum, systemctl usage).
- Replace or supplement the Windows VM deployment tutorial link with a Linux equivalent for automating deployment using the Custom Script extension.
- Ensure that all references to Windows tools or workflows are balanced with Linux alternatives, and present Linux-first where appropriate.
Virtual Machines
Azure Backup for SQL Server running in Azure VM
...extensions/backup-azure-sql-server-running-azure-vm.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a clear Windows bias. It exclusively discusses the AzureBackupWindowsWorkload extension, which is specific to Windows workloads, and provides only PowerShell-based deployment instructions. There are no examples or guidance for Linux-based SQL Server deployments, nor are Linux tools or command-line patterns mentioned. The documentation assumes the SQL Server is running on Windows, with no consideration for Linux VMs or cross-platform scenarios.
Recommendations
- Explicitly state whether Linux-based SQL Server VMs are supported or not. If not, clarify this early in the documentation.
- If Linux support exists, add equivalent instructions and examples for Linux VMs, including relevant extensions, deployment methods, and command-line tools (e.g., Bash, Azure CLI).
- Provide parity in tooling: alongside PowerShell, include Azure CLI or REST API examples for cross-platform compatibility.
- Mention any differences in backup process or extension names for Linux VMs, if applicable.
- Review and update the documentation collection metadata (e.g., ms.collection: windows) to reflect cross-platform support if/when Linux is included.
Virtual Machines
Add monitoring & diagnostics to an Azure virtual machine
...es/virtual-machines/extensions/diagnostics-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page is heavily focused on Windows virtual machines, with all examples, configuration snippets, and explanations tailored exclusively to Windows. There are no Linux-specific examples, configuration details, or references to Linux diagnostics extension usage. Windows tools and conventions (such as Windows event logs, performance counters, and Visual Studio) are mentioned exclusively, and the customer intent and sample templates are Windows-centric. While there is a brief mention of the Linux diagnostics extension (LAD) in the deprecation notice, no practical guidance or parity is provided for Linux users.
Recommendations
- Provide equivalent examples and configuration snippets for Linux VMs, including how to add monitoring and diagnostics using the Linux diagnostics extension (LAD) and/or Azure Monitor Agent.
- Include sample XML or JSON configuration for Linux diagnostics, such as syslog, performance counters, and log collection.
- Reference Linux-specific tools and conventions (e.g., system logs, Linux performance metrics) alongside Windows examples.
- Add links to Linux-focused quickstart templates and documentation.
- Ensure that deployment instructions cover both Azure PowerShell (Windows) and Azure CLI (cross-platform), with explicit Linux usage examples.
- Clarify in the introduction and customer intent that the guidance applies to both Windows and Linux, or provide a separate Linux-focused article.
Virtual Machines
Export Azure resource groups that contain VM extensions
...ticles/virtual-machines/extensions/export-templates.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell and Windows tools/scripts before mentioning Azure CLI, listing Windows extensions before Linux ones in several places, and lacking explicit Linux shell (bash) examples for template deployment. The 'ms.collection' metadata is set to 'windows', and the screenshot and workflow descriptions are tailored to the Azure portal, which is often used in Windows environments. There are no direct Linux command-line or automation examples, and the sample deployment scripts are described as 'PowerShell and Azure CLI', with PowerShell mentioned first.
Recommendations
- Add explicit bash/Linux shell examples for template deployment alongside PowerShell.
- List Linux and Windows extensions in alphabetical order or group them by OS for parity.
- Mention Azure CLI before or alongside PowerShell when describing sample deployment scripts.
- Update metadata to include both Windows and Linux collections if the content is cross-platform.
- Include screenshots or instructions for using the Azure portal from Linux environments (e.g., browser on Ubuntu).
- Clarify that all steps and exported templates are usable from both Windows and Linux environments.
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
Although the documentation is focused on Linux VM extensions, it consistently presents both Azure CLI and Azure PowerShell examples side-by-side, with PowerShell (a Windows-centric tool) given equal prominence. In some sections, references to ARM templates link to Windows documentation first. There is no mention of Linux-native automation tools (such as Bash scripts outside the Custom Script extension), nor are there examples using Linux-native configuration management tools (like Ansible or cloud-init) for extension management. The troubleshooting and operational guidance is generic, but the example commands and links sometimes prioritize Windows or PowerShell patterns, and there are no examples using Linux shell commands for interacting with Azure resources outside the CLI.
Recommendations
- Prioritize Azure CLI examples before PowerShell, as CLI is cross-platform and more native to Linux users.
- Add explicit Bash shell script examples for common extension management tasks, such as using curl, jq, or other Linux tools to interact with Azure REST APIs.
- Reference ARM template documentation for Linux VMs directly, rather than linking to Windows template docs.
- Include examples or mentions of Linux-native automation/configuration tools (e.g., Ansible, cloud-init) where relevant.
- Clarify that PowerShell is available on Linux, but most Linux users prefer CLI or Bash, and adjust examples accordingly.
- Ensure troubleshooting steps include Linux shell commands for log inspection and status checks, not just Azure CLI.
Virtual Machines
Use Application Health extension with Azure Virtual Machines
...ticles/virtual-machines/extensions/health-extension.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Examples First
Windows Tools
Summary
The documentation demonstrates a Windows bias in several areas: Windows-based examples (REST API and PowerShell) are presented before Linux equivalents (CLI), PowerShell is heavily featured, and Windows-specific extension types and log paths are mentioned first. Linux examples are present but generally follow Windows ones, and Linux-specific tools or commands are not highlighted or explained in parity with Windows/PowerShell. The documentation does not provide Linux-first or Linux-only scenarios, and the narrative often defaults to Windows VM usage.
Recommendations
- Alternate the order of examples so that Linux (CLI) examples are presented first in some sections, or provide both Windows and Linux examples side-by-side.
- Include Bash or shell script examples for Linux users where PowerShell is used for Windows.
- Explicitly mention Linux-specific extension types and log paths before or alongside Windows equivalents.
- Add troubleshooting and operational guidance for Linux environments, such as using systemd or journalctl for service health.
- Ensure that all instructions, screenshots, and sample configurations are equally applicable and clearly labeled for both Windows and Linux.
- Highlight any differences in extension behavior or configuration between Windows and Linux VMs, and provide guidance for both.
Virtual Machines
Azure FPGA Attestation Service
...machines/field-programmable-gate-arrays-attestation.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides both PowerShell and Bash examples for attestation, but PowerShell is presented first and in more detail (including monitoring scripts), which may signal a Windows-first bias. The monitoring example is only given for PowerShell, with no equivalent Bash or Linux-native example. References to PowerShell and its installation are prominent, and the documentation mentions using the Azure portal (a GUI tool more commonly used on Windows) for some steps, but not for attestation submission or monitoring. There is no mention of Linux-native tools (such as curl for HTTP requests or monitoring), and Bash examples are less detailed.
Recommendations
- Provide Bash or Linux-native examples for all steps, including monitoring attestation status (e.g., using curl or a Bash script to poll the HTTP endpoint).
- Alternate the order of PowerShell and Bash examples, or present them side-by-side to avoid Windows-first perception.
- Explicitly mention that all CLI commands and scripts are cross-platform, and clarify any platform-specific limitations.
- Include references to Linux-native tools (e.g., curl, jq) for HTTP requests and status monitoring.
- Ensure parity in detail and completeness between PowerShell and Bash examples throughout the documentation.
Virtual Machines
Azure virtual machine extensions and features
.../main/articles/virtual-machines/extensions/overview.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. Windows tools (PowerShell) are mentioned before Linux equivalents when discussing extension management. Troubleshooting guidance for Windows VM extensions is called out first, and PowerShell is listed as a primary management tool alongside Azure CLI, without highlighting Linux-native alternatives. Windows extension examples and links are often presented before Linux ones, and some extension namespaces (e.g., Desired State Configuration) are Windows-specific.
Recommendations
- Present Linux and Windows management tools (e.g., Azure CLI, Bash, PowerShell) in parallel, or highlight Azure CLI/Bash first for cross-platform parity.
- Ensure troubleshooting guidance for Linux VM extensions is equally prominent and not secondary to Windows.
- When listing extension examples or links, alternate the order or group by OS to avoid implicit prioritization.
- Include Linux-native automation patterns (e.g., cloud-init, shell scripts) alongside PowerShell examples.
- Clarify when extensions or features are Windows-only or Linux-only to avoid confusion.
- Add explicit Linux command-line examples (e.g., Bash, Azure CLI) where PowerShell is mentioned.
Virtual Machines
Azure support for Generation 2 VMs
...cs/blob/main/articles/virtual-machines/generation-2.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows examples, tools, and references (such as PowerShell and Hyper-V) are presented before or more extensively than Linux equivalents. PowerShell commands are given for key tasks (e.g., creating managed disks from .vhd files), while Linux CLI or shell examples are missing for similar operations. Windows-centric terminology and links (e.g., Hyper-V documentation) are referenced more frequently and earlier than Linux alternatives. Although Linux support is mentioned and some Linux images are listed, actionable Linux examples and parity in tooling are lacking.
Recommendations
- Provide equivalent Linux CLI or shell commands for all PowerShell examples, especially for tasks like creating managed disks from .vhd files.
- Include Linux-focused documentation links (e.g., KVM, QEMU, or other common Linux virtualization platforms) alongside or before Windows/Hyper-V references.
- Ensure that Linux examples (e.g., using Azure CLI or ARM templates for Linux VMs) are presented with equal prominence and detail as Windows examples.
- Add explicit instructions or code snippets for Linux users in all procedural sections (not just referencing that Linux is supported).
- Review and balance the order of presentation so that Linux and Windows are treated equally in examples, references, and guidance.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. Windows and PowerShell are mentioned explicitly and repeatedly as supported methods for triggering hibernation, while Linux equivalents (such as Bash or shell commands) are not mentioned. The phrase 'PowerShell' appears before 'CLI' in several lists, and there are no concrete examples or references to Linux-specific tools or commands. The troubleshooting and setup sections reference both Windows and Linux documentation, but the main page lacks parity in examples and tool mentions.
Recommendations
- Explicitly mention Linux command-line tools (e.g., Bash, shell scripts) alongside PowerShell when listing supported methods for triggering hibernation.
- Provide example commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) directly on the overview page, not just in linked documentation.
- When listing supported interfaces (portal, CLI, PowerShell, SDKs, APIs), alternate or randomize the order so Windows tools are not always listed first.
- Add a brief summary of Linux-specific hibernation steps or considerations on the overview page to match the Windows coverage.
- Ensure troubleshooting and FAQ sections include Linux-specific examples and not just links.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits several Windows biases. PowerShell is presented as the primary scripting method with detailed examples, while Linux-native CLI or scripting examples are minimal or absent. Windows disk management tools (Storage Spaces, SOFS) are mentioned before Linux equivalents (LVM, MDADM) in planning sections. The REST API section assumes use of Chocolatey (a Windows package manager) and PowerShell/cmd.exe for installation, with no mention of Linux installation methods. There are no bash or Linux shell script examples for enabling Write Accelerator, and the CLI section is brief and lacks parity with the PowerShell walkthrough.
Recommendations
- Provide bash/Linux shell script examples for enabling Write Accelerator, matching the detail of PowerShell examples.
- Mention Linux package managers (e.g., apt, yum, snap) for installing armclient, or provide cross-platform installation instructions.
- Present Linux disk management tools (LVM, MDADM) before or alongside Windows tools in planning and configuration sections.
- Expand Azure CLI examples to cover all scenarios shown in PowerShell, with explicit Linux usage notes.
- Add troubleshooting and operational notes specific to Linux environments.
- Clarify that all steps are cross-platform where applicable, and highlight any OS-specific differences.