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 351-375 of 818 flagged pages
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias: PowerShell examples and references are given equal or greater prominence than Azure CLI, with some links and examples (e.g., finding images in the Azure Marketplace, sharing images) referencing Windows-specific pages or PowerShell first. Windows tools and terminology (Sysprep, Hyper-V generation) are mentioned before or more thoroughly than their Linux equivalents. Linux-specific instructions (e.g., waagent for generalization, Linux upload VHD) are present but often referenced after Windows or in less detail. Some example links and troubleshooting guides default to Windows/PowerShell, and Linux CLI parity is not always explicit.
Recommendations
- Ensure all example commands are provided in both Azure CLI and PowerShell, with CLI (cross-platform) examples shown first.
- Where Windows-specific tools (Sysprep, Hyper-V) are mentioned, provide equivalent Linux instructions (waagent, etc.) with equal prominence and detail.
- Avoid linking primarily to Windows/PowerShell documentation; provide direct links to Linux/CLI documentation where available.
- Explicitly call out Linux/macOS compatibility and provide troubleshooting steps/examples for those platforms.
- Review and update references to ensure Linux and Windows are treated equally in all scenarios, including FAQs and advanced scenarios.
Create Pull Request
Virtual Machines
Share Resources in Azure Compute Gallery
...s/blob/main/articles/virtual-machines/share-gallery.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides three example tabs for sharing resources via RBAC: Portal, CLI, and PowerShell. The PowerShell example is Windows-centric and is presented as a first-class method alongside the cross-platform Azure CLI. There are no Linux/macOS-specific instructions or mentions of platform differences, and PowerShell is shown before any Linux shell scripting alternatives.
Recommendations
- Explicitly mention that Azure CLI works on Linux/macOS and provide bash/zsh shell examples where appropriate.
- Clarify that PowerShell examples are primarily for Windows users, and suggest alternatives for Linux/macOS users.
- Consider adding a note about platform compatibility for each method.
- If relevant, provide instructions for using Azure CLI in bash/zsh, and highlight any differences in authentication or environment setup for Linux/macOS.
- List CLI (cross-platform) examples before PowerShell (Windows-centric) to reduce perceived Windows-first bias.
Virtual Machines
Dlsv6 size series (Preview)
...virtual-machines/sizes/general-purpose/dlsv6-series.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Windows-specific technologies (such as Hyper-V nested virtualization) and tools (NTTTCP for bandwidth testing) without mentioning Linux equivalents or alternatives. In the networking section, Windows is mentioned before Linux when discussing optimization, and the bandwidth testing tool referenced is Windows-centric. No explicit Linux examples or tools are provided.
Recommendations
- Include Linux equivalents for referenced Windows tools, such as suggesting iperf or netperf for bandwidth testing alongside NTTTCP.
- Provide links to Linux-specific documentation for nested virtualization (e.g., KVM or QEMU guides) in addition to Hyper-V.
- When listing OSes, mention Linux/macOS first or equally with Windows to avoid ordering bias.
- Add explicit examples or optimization tips for Linux VMs where appropriate.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely platform-neutral, focusing on VM specifications and features. However, there is a subtle Windows bias in the 'Feature support' section, where Nested Virtualization links specifically to a Windows/Hyper-V guide, and in the 'Network' section, where bandwidth testing references NTTTCP (a Microsoft tool primarily associated with Windows). Linux equivalents or guidance are not mentioned, and Windows tools are referenced first or exclusively.
Recommendations
- Include links or references to Linux-specific nested virtualization documentation (e.g., KVM/QEMU guides for nested virtualization on Azure).
- In the bandwidth testing section, mention and link to Linux-compatible tools such as iperf or netperf, and provide guidance for Linux users.
- Where Windows-specific tools are referenced, add Linux alternatives and usage notes to ensure parity.
- Review all feature support links to ensure Linux documentation is equally represented where applicable.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. PowerShell is given extensive coverage with multiple detailed scripts, including both Cloud Shell and local usage, and special handling for availability sets. The CLI section is present and functional, but less detailed and lacks explicit Linux/macOS shell context (e.g., bash vs. PowerShell). The Terraform example references a Windows VM quickstart and does not provide a Linux VM example or parity. There are references to Windows-specific migration scenarios and links. Overall, Windows tools and patterns are mentioned first and in greater detail, while Linux-specific guidance is minimal or absent.
Recommendations
- Add explicit Linux/macOS shell examples in the CLI section, clarifying shell syntax and environment differences.
- Provide a Terraform example for resizing a Linux VM, not just referencing the Windows quickstart.
- Ensure migration workaround links and instructions cover both Windows and Linux VMs equally.
- Balance PowerShell and CLI coverage, possibly by offering bash scripts or Azure CLI examples with Linux context first or equally.
- Review and update references and quickstarts to include Linux VM scenarios and links.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Migration instructions are provided for the Azure portal (GUI), Azure PowerShell, and Azure CLI. The PowerShell example is detailed and presented before the CLI example. The CLI example is labeled as 'powershell' in the code block, and uses variable syntax ($var) that is typical for PowerShell, not Bash, which may confuse Linux/macOS users. No explicit Bash/Linux shell example is provided, and there is no mention of Linux-specific tools or patterns. The documentation assumes familiarity with PowerShell and Windows-centric workflows, potentially creating friction for Linux/macOS users.
Recommendations
- Provide explicit Bash/Linux shell examples for Azure CLI commands, using correct Bash variable syntax (e.g., $resourceGroup without curly braces, or using export).
- Ensure code blocks for CLI examples are labeled as 'bash' or 'sh' rather than 'powershell' when appropriate.
- Add notes clarifying that Azure CLI works cross-platform and provide any OS-specific instructions if needed.
- Consider presenting CLI (cross-platform) examples before PowerShell (Windows-centric) examples to reduce perceived bias.
- Mention Linux/macOS compatibility in migration steps and highlight any differences or prerequisites for those platforms.
Virtual Machines
Create SSH keys in the Azure portal
...blob/main/articles/virtual-machines/ssh-keys-portal.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. The only example for connecting to a VM uses PowerShell, with no mention of Linux/macOS terminals or their usage patterns. The instructions for using the SSH key after download are Windows-centric, and Linux/macOS users are not given explicit guidance or examples. References to further documentation also point to a page about connecting from Windows, reinforcing the bias.
Recommendations
- Add explicit Linux/macOS terminal examples for connecting to the VM using SSH, e.g., using the Terminal app or bash.
- Include notes on file permissions for the downloaded .pem file (e.g., chmod 600 on Linux/macOS).
- Provide parity in instructions for moving the .pem file on Linux/macOS systems.
- Reference documentation for connecting from Linux/macOS, not just Windows.
- When showing SSH commands, avoid specifying PowerShell unless necessary, or present both Windows and Linux/macOS options side by side.
Virtual Machines
Upgrade Gen1 VMs to Trusted launch
...s/virtual-machines/trusted-launch-existing-vm-gen-1.md
Medium 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-specific tools (MBR2GPT.exe, Defrag, BitLocker, PowerShell) are described in detail, with step-by-step instructions and troubleshooting. Linux instructions are present but less detailed, often limited to validation steps and lacking guidance for disk conversion or troubleshooting. Windows examples and tools are frequently mentioned first or exclusively, while Linux equivalents are referenced briefly or omitted.
Recommendations
- Provide detailed Linux disk conversion steps (e.g., using gdisk, parted, or other tools) for MBR to GPT and EFI partition creation, including troubleshooting.
- Include Linux-specific troubleshooting guidance for common upgrade issues.
- Balance example order: present Linux and Windows instructions with equal prominence, or alternate which comes first.
- Reference Linux-native tools for disk management and encryption, not just Windows tools.
- Expand Linux upgrade support beyond Marketplace images, or clarify the process for custom images.
- Where PowerShell is used for ARM template deployment, offer Bash/CLI alternatives for Linux/macOS users.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation provides detailed resizing instructions for the Azure portal and Azure PowerShell, but omits equivalent examples for the Azure CLI, which is more commonly used on Linux/macOS. The PowerShell example is given before any mention of CLI, and no bash or Linux-native commands are shown. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
- Add Azure CLI (bash) examples for resizing VMs, including listing available sizes and performing the resize.
- Present CLI and PowerShell examples side-by-side or in parallel sections, rather than PowerShell only.
- Explicitly mention that CLI is cross-platform and suitable for Linux/macOS users.
- Consider providing links to both PowerShell and CLI documentation in the main migration section.
Virtual Machines
Create an Azure snapshot of a virtual hard disk
...rticles/virtual-machines/snapshot-copy-managed-disk.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and references are prominent, and Windows-centric tools and patterns (e.g., PowerShell cmdlets, Windows VM creation links) are mentioned before or more extensively than Linux equivalents. The 'Next steps' section links to Windows-specific guides first, with the Linux CLI example only appearing last. There is no explicit Linux-specific PowerShell example, and the CLI example is generic, not tailored for Linux VMs.
Recommendations
- Ensure Linux examples are presented with equal prominence and detail as Windows examples, especially in the 'Next steps' section.
- Provide Linux-specific PowerShell examples if relevant, or clarify PowerShell usage on Linux.
- Alternate the order of Windows and Linux examples/links to avoid implicit prioritization.
- Include explicit Linux VM creation and recovery steps in both PowerShell and CLI sections.
- Add notes clarifying cross-platform compatibility for each tool and command.
Virtual Machines
Enable Trusted launch on existing Gen2 VMs
...rticles/virtual-machines/trusted-launch-existing-vm.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides parity for both Linux and Windows VMs in terms of Azure CLI, Portal, and ARM template instructions. However, PowerShell examples are given for all automation scenarios, which is a Windows-centric tool. Additionally, PowerShell is used for ARM template deployment and VM deallocation, with no mention of Bash or cross-platform alternatives. The documentation also references RDP (Windows) and SSH (Linux) equally, but PowerShell is the only scripting language shown for template deployment and roll-back, which may create friction for Linux/macOS users. The order of examples sometimes places PowerShell before CLI, and the template deployment steps use PowerShell commands exclusively.
Recommendations
- Provide Bash or cross-platform shell examples for ARM template deployment and VM deallocation/start, alongside PowerShell.
- Explicitly mention that Azure CLI and ARM templates can be used from Linux/macOS, and provide sample commands for those platforms.
- Where PowerShell is used, add equivalent Bash/CLI instructions to ensure Linux/macOS users can follow without needing PowerShell.
- Clarify that PowerShell is optional and not required for Linux/macOS users.
- Consider reordering examples so that CLI or cross-platform methods appear before PowerShell, or present them side-by-side.
Virtual Machines
Enable Trusted launch on existing Uniform scale set
...icles/virtual-machines/trusted-launch-existing-vmss.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a moderate Windows bias. Windows OS images are used as the primary example in ARM template, CLI, and PowerShell sections. All code snippets for enabling Trusted launch use Windows-centric SKUs (e.g., '2022-datacenter-azure-edition'), and there are no explicit Linux image examples or Linux-specific command variations. The Guest Attestation extension publisher for Linux is mentioned, but not demonstrated in any code. PowerShell is given a dedicated section, and Windows tools/patterns (e.g., Azure PowerShell, Windows image SKUs) are referenced before or instead of Linux equivalents.
Recommendations
- Include explicit Linux OS image examples (e.g., Ubuntu, Red Hat) in ARM template, CLI, and PowerShell sections.
- Demonstrate use of the Linux Guest Attestation extension publisher in code snippets.
- Add notes or sections clarifying any differences or additional steps for Linux scale sets.
- Alternate or parallelize Windows and Linux examples to ensure parity and visibility.
- Reference cross-platform installation instructions for CLI and PowerShell, not just Windows.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits several Windows biases: Windows concepts (Secure Boot, Hyper-V Shielded VM) are introduced first and referenced with Windows-centric links; PowerShell examples are consistently provided alongside CLI, sometimes before Linux-specific instructions; Windows tools and terminology (such as COM ports, Secure Boot links) are mentioned without Linux equivalents; and some troubleshooting and validation sections lack parity in Linux-specific guidance, especially for certificate inspection and VM image validation. Although Linux instructions are present for some tasks (e.g., SBInfo tool installation), Windows patterns and examples are more prominent and detailed.
Recommendations
- Ensure Linux examples are provided for every CLI and PowerShell example, especially for certificate inspection and VM image validation.
- Present Linux and Windows instructions in parallel, or alternate which is shown first, to avoid Windows-first ordering.
- Include Linux-specific troubleshooting steps and links where only Windows tools or documentation are referenced.
- Expand certificate inspection guidance to include Linux-native tools (e.g., openssl, certtool) and workflows.
- Reference Linux documentation for Secure Boot and UEFI concepts, not just Windows hardware links.
- Add more explicit Linux automation examples (e.g., Bash scripts, cloud-init) where PowerShell is used.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows tools and terminology (e.g., PowerShell, MicrosoftWindowsTemplate) are mentioned before or alongside Linux equivalents. While Linux is referenced in the 'Useful links' section and verification steps use Linux tools (mokutil), there are no explicit Linux command-line examples for creating or managing UEFI keys, and Windows-centric signature templates are highlighted. Instructions for creating certificates/keys refer users to external links for Linux, rather than providing direct examples, whereas Windows templates are named and described in the main scenarios.
Recommendations
- Add explicit Linux command-line examples for creating and managing UEFI keys (e.g., using openssl, sbsigntool).
- Provide step-by-step Linux instructions for certificate/key creation within the documentation, not just in external links.
- Describe Linux-specific signature templates or clarify cross-platform applicability of existing templates.
- Ensure Linux tools and patterns are mentioned alongside Windows ones, not only in 'Useful links'.
- Consider reordering examples so that Linux and Windows scenarios are presented with equal prominence.
Virtual Machines
Trusted Launch for Azure VMs
.../blob/main/articles/virtual-machines/trusted-launch.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page for Trusted Launch in Azure VMs generally covers both Windows and Linux platforms, but there are several signs of Windows bias. Windows examples and references (such as ARM templates for Windows VMs) are given before Linux equivalents, and links to Windows-specific documentation (e.g., Secure Boot, TPM, VBS, Credential Guard) are prevalent. The 'Secure Boot' and 'vTPM' sections reference Windows documentation and features almost exclusively, with Linux details being less prominent or relegated to notes. Example templates are Windows-focused, and there is a lack of Linux-specific deployment examples or tooling references (e.g., cloud-init, Linux CLI usage).
Recommendations
- Add Linux-focused deployment examples (e.g., ARM templates for Ubuntu or RHEL, cloud-init scripts).
- Provide links to Linux documentation for Secure Boot, TPM, and attestation, not just Windows/MS docs.
- Include Linux CLI and scripting examples alongside or before Windows/PowerShell examples.
- Balance references to Windows tools/features with equivalent Linux security features and workflows.
- Ensure that Linux-specific limitations and workarounds are documented with the same depth as Windows.
Virtual Machines
Guest updates and host maintenance overview
...icles/virtual-machines/updates-maintenance-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation generally covers both Windows and Linux VMs, but there are several instances of Windows bias. Windows examples and links are often mentioned first, and some features (like Hotpatch) are described as Windows-only without Linux equivalents or alternatives. Maintenance control via CLI and PowerShell is mentioned, but no explicit Linux shell examples are provided. References to 'PowerShell' and 'Windows Server' are more prominent, and some links (e.g., scheduled events) default to Windows documentation before Linux. Linux users may need to search for their relevant instructions, causing friction.
Recommendations
- Ensure that Linux and Windows examples/links are presented together or alternate which is shown first.
- Provide explicit Linux shell (bash/CLI) examples where PowerShell is mentioned.
- For Windows-only features (e.g., Hotpatch), clearly state the lack of Linux support and suggest Linux alternatives if available.
- Balance the mention of Windows and Linux tools and terminology throughout the documentation.
- Where links to both Windows and Linux documentation exist, present them side-by-side rather than defaulting to Windows first.
Virtual Machines
Use Premium SSD v2 with VMs in availability set
...l-machines/use-premium-ssd-v2-with-availability-set.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides command-line examples for Azure CLI and PowerShell, with the PowerShell examples being Windows-specific. VM creation examples use Windows images (Win2016Datacenter) by default, and there are no explicit Linux VM image examples or Linux-specific guidance. The PowerShell tab is present, but there is no Bash or Linux shell scripting equivalent. The Azure CLI examples are cross-platform, but the overall pattern and examples favor Windows and Windows tooling.
Recommendations
- Include explicit Linux VM image examples (e.g., UbuntuLTS, CentOS) alongside Windows VM examples in Azure CLI and PowerShell sections.
- Add a Bash/Linux shell scripting tab or section, especially for users who prefer Bash over PowerShell.
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide any platform-specific notes if needed.
- Ensure parity in examples and guidance for both Windows and Linux users, including troubleshooting and disk attachment scenarios.
- Avoid using only Windows-centric VM images in examples; alternate or show both OS types.
Virtual Machines
User data for Azure Virtual Machine
...-docs/blob/main/articles/virtual-machines/user-data.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page shows a notable Windows bias: JSON examples for VM creation and updates consistently use Windows OS images and Windows-centric fields (e.g., 'osType': 'Windows', 'windowsConfiguration', 'adminPassword'), with no Linux equivalents or examples. Linux-specific configuration fields (like 'linuxConfiguration') are absent, and the only reference to Linux is in a link to IMDS sample code, not in the main examples. This may cause confusion or extra effort for Linux users.
Recommendations
- Provide parallel JSON examples for Linux VMs, including 'osType': 'Linux', 'linuxConfiguration', and relevant image references.
- Include Linux-specific fields and remove unnecessary Windows-only fields in generic examples.
- Ensure example ordering is balanced or alternates between Windows and Linux.
- Clarify in text that user data applies equally to Linux and Windows, and link to both Linux and Windows sample code.
- Add a section explicitly showing how to retrieve and use user data on Linux VMs, not just via external links.
Virtual Machines
Deploying disks with Azure Resource Manager templates
...l-machines/using-managed-disks-template-deployments.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently using Windows VM examples and references throughout. All JSON template examples use Windows images (MicrosoftWindowsServer) and Windows-specific parameters, with no Linux equivalents shown. The main template referenced is 'vm-simple-windows', and even the SSD disk example specifies 'osType': 'Windows'. Linux VMs are mentioned only in the 'Applies to' section and in a single link at the end, but no Linux-specific template snippets or image references are provided.
Recommendations
- Provide parallel Linux VM template examples, using Linux image references (e.g., Ubuntu, CentOS) and Linux-specific parameters.
- Alternate or balance the use of Windows and Linux examples throughout the documentation, not just in links.
- Include explicit notes or sections for Linux users, highlighting any differences in template structure or parameters.
- Reference both Windows and Linux quickstart templates equally in the main text, not just in 'Next steps'.
Virtual Machines
Maintenance control for OS image upgrades on Azure Virtual Machine Scale Sets using Azure portal
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/virtual-machine-scale-sets-maintenance-control-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes how to use the Azure portal GUI for maintenance control, with screenshots and instructions that are platform-agnostic but implicitly Windows-centric due to the Azure portal's design and common usage patterns. There are no examples or references to command-line tools, such as Azure CLI or PowerShell, nor any mention of Linux/macOS workflows or tools. This creates a subtle bias by omitting Linux-friendly automation and scripting options.
Recommendations
- Add equivalent instructions for configuring maintenance control using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Include sample scripts or commands for both PowerShell and Bash, demonstrating automation of maintenance configuration and assignment.
- Explicitly mention that the Azure portal is accessible from any OS/browser, and link to CLI documentation for users preferring non-GUI workflows.
- Provide troubleshooting or tips for Linux/macOS users if there are any known differences or limitations.
Virtual Machines
Use virtual machine restore points
...ual-machines/virtual-machines-create-restore-points.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by describing application consistency primarily in terms of Windows (VSS writers) before mentioning Linux (pre- and postscripts). It references Windows-specific tooling (Volume Shadow Copy Service) and does not provide concrete Linux examples or guidance for implementing pre- and postscripts, leaving Linux users with less actionable information.
Recommendations
- Include explicit Linux examples for application-consistent restore points, such as sample pre- and postscripts.
- Provide links or references to best practices for Linux application consistency in Azure.
- Present Windows and Linux guidance in parallel, rather than Windows-first.
- Clarify any differences in restore point creation or troubleshooting for Linux VMs.
Virtual Machines
Manage, Update, and Delete VM Applications on Azure
...in/articles/virtual-machines/vm-applications-manage.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for all operations, but PowerShell (a Windows-centric tool) is given equal prominence and sometimes referenced for scripting even in CLI sections. Windows terminology and tools (PowerShell, Select-Object, ConvertTo-Json, etc.) are used throughout, and PowerShell scripting is shown for tasks that could be done with Bash or other Linux-native tools. There are no explicit Bash or Linux shell script examples, and PowerShell is referenced in CLI scripting notes, implying a Windows-first approach. However, the Azure CLI examples are cross-platform, and REST API usage is platform-neutral.
Recommendations
- Add Bash/Linux shell script equivalents alongside PowerShell examples, especially in scripting sections.
- When showing scripting with Azure CLI, use Bash syntax for loops and data extraction, not just PowerShell.
- Clarify that Azure CLI commands work on Linux/macOS and provide OS-specific notes where relevant.
- Avoid referencing PowerShell in CLI sections unless also providing a Linux shell alternative.
- Consider reordering examples so that cross-platform tools (CLI, REST) are shown before Windows-specific tools (PowerShell).
Virtual Machines
Overview of Maintenance control for OS image upgrades on Azure Virtual Machine Scale Sets
...ines/virtual-machine-scale-sets-maintenance-control.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page shows a notable Windows bias: PowerShell is mentioned first among management options, and the 'Next steps' section exclusively links to a PowerShell-based guide. There is no direct example or link for Linux/macOS users (e.g., Azure CLI or Bash), and Windows-centric tools/patterns are prioritized.
Recommendations
- Present Azure CLI and PowerShell options side-by-side, or alternate their order to avoid implicit prioritization.
- Include direct links to Azure CLI and portal guides in the 'Next steps' section, not just PowerShell.
- Add explicit examples or walkthroughs for Linux/macOS users using Azure CLI or Bash.
- Clarify that all management options are cross-platform where applicable.
Virtual Machines
Creating Virtual Machine Restore Points using Azure portal
...hines/virtual-machines-create-restore-points-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on using the Azure portal for creating and restoring VM restore points, which is cross-platform. However, in the 'Restore a VM from a restore point' section, the links provided for creating a new VM and attaching disks point to Windows-specific guides, with no mention or links to equivalent Linux VM documentation. There are no Linux-specific instructions or examples, and Windows documentation is referenced first and exclusively.
Recommendations
- Add links to Linux VM creation and disk attachment guides alongside the Windows links.
- Explicitly mention that the process applies to both Windows and Linux VMs, or provide platform-specific notes where relevant.
- Ensure parity by including examples or screenshots for both Windows and Linux VM scenarios, especially in restore workflows.
- Where PowerShell or CLI alternatives are mentioned, clarify their cross-platform support and provide Linux/macOS usage notes if needed.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization, but the PowerShell example is more detailed and uses Windows-centric SDK objects. The CLI example uses Ubuntu as the image, but does not provide any Linux-specific shell scripting or guidance. The PowerShell section is presented after CLI, but is more verbose and assumes familiarity with Windows tooling. There are no Bash or Linux shell script examples, nor is there mention of Linux-specific considerations beyond the image name in the CLI example.
Recommendations
- Add explicit Bash/Linux shell script examples for VM creation using Azure CLI.
- Provide guidance for Linux users on how to automate these settings (e.g., with shell scripts, cloud-init, etc.).
- Balance the detail level between PowerShell and CLI sections, ensuring Linux users have equally comprehensive instructions.
- Mention Linux-specific considerations (such as verifying vCPU count in Linux OS, e.g., using lscpu or /proc/cpuinfo).
- If possible, provide macOS-specific notes for CLI usage.