Virtual Machines
1073
Total Pages
1027
Linux-Friendly Pages
46
Pages with Bias
4.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
284 issues found
Showing 26-50 of 284 flagged pages
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page, while focused on creating and uploading an Ubuntu Linux VHD to Azure, exhibits notable Windows bias. Hyper-V (a Windows-only virtualization tool) is referenced as the primary example for creating VHDs, and Windows-specific instructions (such as using PowerShell's Convert-VHD cmdlet) are provided without Linux alternatives. Steps involving Hyper-V Manager and PowerShell are described in detail, but equivalent Linux tools (like qemu-img or VirtualBox) are not mentioned or explained. This creates friction for Linux/macOS users, who may not have access to Hyper-V or PowerShell.
Recommendations
- Add instructions and examples for creating VHDs using Linux-native tools such as qemu-img, KVM, or VirtualBox.
- Provide Linux/macOS alternatives for disk conversion (e.g., using qemu-img to convert raw images to fixed VHD format).
- Include guidance for deprovisioning and shutting down VMs using Linux tools and commands, not just Hyper-V Manager.
- Reorganize sections so Linux-native methods are presented first or alongside Windows methods, rather than Windows-first.
- Clarify which steps are Windows-specific and offer parity for Linux/macOS users wherever possible.
Create Pull Request
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation covers both Windows and Linux usage for Azure Image Builder, but there is a notable Windows bias in several areas. Windows/PowerShell examples and tools are often presented first, and PowerShell is frequently referenced for tasks like generating SHA256 checksums and running commands. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents are less prominent or missing (e.g., no Linux restart customizer). Windows tools (PowerShell cmdlets) are mentioned for checksum generation, with Linux alternatives referenced but less emphasized. However, Linux support is present throughout, and Linux-specific instructions are included, especially for shell customizers and validations.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which is shown first.
- For checksum generation, mention Linux/Mac commands (sha256sum) before or alongside PowerShell Get-FileHash.
- Clarify limitations (e.g., no Linux restart customizer) and suggest Linux workarounds (such as using shell scripts with 'reboot' and validation logic).
- Expand Linux-specific guidance for common tasks (e.g., file downloads, validation, customization) to match Windows detail.
- Ensure all CLI instructions are equally applicable to Linux/macOS users and highlight cross-platform compatibility.
- Add links to Linux troubleshooting and scripting resources where Windows links are provided.
Virtual Machines
Run scripts in a Linux VM in Azure using managed Run Commands
...articles/virtual-machines/linux/run-command-managed.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page, while focused on Linux VMs, includes significant PowerShell usage and references to Windows-centric tools and patterns. PowerShell examples are provided extensively alongside Azure CLI, but some examples and notes reference Windows-specific behaviors or tools (e.g., 'ipconfig', 'Write-Host', SAS token generation with PowerShell). REST API and ARM template examples use Windows-style scripts (.ps1) and 'Write-Host', and PowerShell is presented with equal or greater prominence than Azure CLI. Some explanations and examples lack explicit Linux shell script equivalents, and Windows terminology is used in parameter explanations.
Recommendations
- Ensure all script examples in REST API and ARM template sections use Linux shell scripts (e.g., 'echo Hello World!', '.sh' files) when the context is Linux VMs.
- Replace or supplement PowerShell-centric instructions (e.g., SAS token generation, 'Write-Host') with Azure CLI or Linux-native alternatives.
- Clarify when a command or parameter is Windows-specific versus Linux-specific, especially in sections describing parameter passing and script execution.
- Present Azure CLI examples before PowerShell, as CLI is more native to Linux environments.
- Add explicit Linux shell script examples for all major scenarios, including REST API and ARM template deployments.
- Avoid referencing Windows tools (e.g., 'ipconfig') in Linux contexts; use Linux equivalents like 'ifconfig' or 'ip'.
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is intended for both Windows and Linux virtual machines, as stated at the top. Most command-line examples (Azure CLI, API, PowerShell) are generic and applicable to both OS types. However, the ARM template section only provides a Windows VM example, with no Linux equivalent. Additionally, the ARM template parameters and image references are exclusively for Windows Server, and the Windows image options are listed without mention of Linux images. This creates a subtle Windows bias, especially for users seeking ARM template guidance for Linux VMs.
Recommendations
- Add an ARM template example for a Linux VM (e.g., Ubuntu or CentOS), including relevant parameters and image references.
- In the ARM template section, clarify how to modify the template for Linux VMs, such as changing the publisher, offer, and SKU.
- Consider listing both Windows and Linux image options in the ARM template parameters.
- Ensure that instructions and examples consistently mention both Windows and Linux where applicable.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux, repeatedly references Windows-specific tools and workflows (notably Hyper-V and Convert-VHD PowerShell cmdlet) for creating and converting VHDs. Windows/Hyper-V is mentioned first and most prominently as the example virtualization solution, and Linux-native alternatives (such as qemu-img, VirtualBox, or KVM) are not provided. The instructions for extracting the VHD tarball on Windows recommend using WSL, but do not provide guidance for Linux/macOS users. Critical steps like VHD conversion are only described with Windows/PowerShell tooling, leaving gaps for Linux users.
Recommendations
- Add Linux-native instructions for creating and converting VHDs (e.g., using qemu-img or VBoxManage).
- Mention Linux/macOS virtualization solutions (such as KVM, VirtualBox, or QEMU) alongside Hyper-V.
- Provide explicit examples for extracting the VHD tarball on Linux/macOS (e.g., using tar in a terminal).
- Include guidance for converting VHDX to fixed VHD on Linux (e.g., qemu-img convert -O vpc).
- Reorder examples so Linux-native tools are presented first or in parallel with Windows tools.
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Minor Windows Example Priority
Summary
The documentation covers both Windows and Linux VM image creation with Azure Image Builder, and provides parity for most features. However, there is a notable Windows bias in several areas: PowerShell is frequently used for examples (e.g., generating SHA256 checksums, Sysprep commands, image build/cancel operations), Windows customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in more detail and often before Linux equivalents, and Windows-specific tools (Get-FileHash, shutdown, Sysprep) are referenced. Linux examples are present and explained, but Windows tools and patterns are sometimes mentioned first or exclusively (e.g., no Linux restart customizer, PowerShell validator details shown before Shell validator details).
Recommendations
- Provide Linux/macOS equivalents for all PowerShell commands (e.g., show sha256sum before or alongside Get-FileHash).
- Ensure Linux examples are given equal prominence and detail, especially in sections where Windows tools are described.
- Where Windows customizers (e.g., WindowsRestart, WindowsUpdate) are described, clarify Linux alternatives or explicitly state their absence.
- In validation and customization sections, alternate the order of Windows and Linux examples, or present them side-by-side.
- Add explicit notes or links for Linux/macOS users where only Windows tools are referenced (e.g., Sysprep, PowerShell).
Virtual Machines
Run scripts in a Linux VM in Azure using managed Run Commands
...articles/virtual-machines/linux/run-command-managed.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
While the documentation is focused on Linux VMs and provides extensive Azure CLI examples (which are cross-platform), there is a notable bias toward Windows tooling and PowerShell. PowerShell examples are provided in great detail, often with Windows-centric terminology and tools (e.g., 'New-AzStorageBlobSASToken', 'ipconfig' as a commandId, 'myscript.ps1' in examples). REST API and ARM template examples frequently use Windows-style scripts (PowerShell, .ps1) rather than Linux shell scripts (.sh). Some explanations and notes reference Windows-specific behaviors or tools before Linux equivalents, and certain advanced scenarios (e.g., streaming output to blobs) are only illustrated with PowerShell. There are also missing Linux-specific examples for some advanced features.
Recommendations
- Provide Linux shell script (.sh) examples alongside PowerShell (.ps1) in REST API and ARM template sections.
- Clarify when PowerShell tools (e.g., New-AzStorageBlobSASToken) are Windows-only and offer Linux alternatives (e.g., Azure CLI or Python SDK for SAS token generation).
- Ensure commandId examples use Linux-relevant commands (e.g., 'ifconfig', 'ls', 'bash') instead of Windows commands like 'ipconfig'.
- Add advanced Azure CLI examples for features currently only shown in PowerShell (e.g., streaming output to blobs, parameter passing).
- Review notes and explanations to avoid referencing Windows behaviors before Linux, or to clearly distinguish OS-specific instructions.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation is primarily focused on Ubuntu Linux, but it exhibits Windows bias in several areas. Hyper-V (a Windows-only virtualization tool) is mentioned as the main example for creating VHDs, and instructions reference Hyper-V Manager and PowerShell's Convert-VHD cmdlet without providing equivalent Linux tooling or workflows. Windows extraction instructions are given (via WSL), but native Linux extraction is not explicitly described. Linux-native tools for VHD creation and conversion (such as qemu-img or VBoxManage) are missing, and the workflow assumes Windows/Hyper-V as the default environment.
Recommendations
- Add instructions and examples for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, dd).
- Provide steps for extracting the .tar.gz image natively on Linux (not just via WSL on Windows).
- Mention Linux virtualization solutions (e.g., KVM, VirtualBox) alongside Hyper-V, and link to relevant guides.
- Include PowerShell/Hyper-V steps as an alternative, not the default, and ensure Linux-first parity in examples.
- Clarify that Hyper-V is just one option, and highlight Linux-native workflows for users on Linux/macOS.
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Windows and Linux coverage, but there are several areas where Windows/PowerShell tools and patterns are emphasized or presented first. PowerShell is frequently used for checksum generation and command examples, sometimes without Linux equivalents. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents are less prominent or missing (e.g., no Linux restart customizer). In some sections, Windows tools (PowerShell cmdlets) are referenced before Linux tools, and Windows examples are shown first.
Recommendations
- Where PowerShell is used for tasks like checksum generation, always provide the equivalent Linux/macOS command (e.g., sha256sum) alongside.
- For customizer types, clarify Linux limitations (e.g., no restart customizer) and suggest workarounds for Linux users.
- Ensure that Linux examples (e.g., shell scripts, CLI commands) are presented with equal prominence and, where possible, shown before or alongside Windows examples.
- For validation and customization, explicitly state Linux support and provide Linux-specific examples where only Windows examples are given.
- Where Windows tools or patterns are mentioned (such as Get-FileHash), add Linux/macOS alternatives (such as sha256sum) in the same context.
Virtual Machines
Run scripts in a Linux VM in Azure using managed Run Commands
...articles/virtual-machines/linux/run-command-managed.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
Although the documentation is focused on Linux VMs, there is notable Windows bias in several areas. PowerShell examples and tooling (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand) are heavily featured, sometimes before or in greater detail than Azure CLI examples. Windows-specific tools and patterns (such as PowerShell cmdlets and SAS token generation via New-AzStorageBlobSASToken) are referenced throughout. REST API and ARM template examples use Windows-centric script examples (e.g., Write-Host, .ps1 files) instead of Linux shell scripts (.sh). Some explanations and notes reference Windows behaviors or requirements, and Linux-specific guidance is less prominent or missing in places.
Recommendations
- Ensure all examples and explanations are Linux-centric, using bash/shell scripts (.sh) instead of PowerShell (.ps1) where appropriate.
- Provide Azure CLI examples before PowerShell, as CLI is more cross-platform and native for Linux users.
- Where PowerShell cmdlets are referenced, add equivalent Azure CLI commands and highlight their use for Linux environments.
- In REST API and ARM template samples, use Linux shell script examples (e.g., 'echo Hello World!' or .sh files) rather than Windows PowerShell scripts.
- Clarify SAS token generation for Linux users, referencing Azure CLI commands instead of only PowerShell.
- Remove or minimize Windows-specific notes unless they are relevant to Linux VM scenarios.
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
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux guidance for upgrading Gen1 VMs to Trusted launch, but Windows-specific instructions, tools (MBR2GPT.exe, Defrag, PowerShell), and troubleshooting are more detailed and appear first. Linux instructions are present but less extensive, and CLI/ARM template examples are cross-platform. Windows tools and patterns are mentioned before Linux equivalents, and troubleshooting sections are heavily Windows-focused.
Recommendations
- Expand Linux troubleshooting guidance to match Windows detail, including common errors and recovery steps.
- Provide Linux-specific disk conversion instructions for cases where GPT/EFI is not already present, including recommended tools and commands.
- Add Linux examples for ARM template deployment and validation where relevant.
- Ensure parity in best practices, such as disk preparation and backup, for Linux VMs.
- Consider listing Linux instructions/examples before or alongside Windows to avoid 'windows_first' bias.
Virtual Machines
Deploy a Trusted Launch VM
...ain/articles/virtual-machines/trusted-launch-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows VM deployment with Trusted Launch, and provides parity in Azure CLI and ARM template examples. However, PowerShell examples are Windows-centric and shown in detail, with Windows-specific parameters and image references. In several PowerShell sections, only Windows examples are provided, while CLI examples use Linux images. The order of examples sometimes puts Windows/PowerShell before Linux/CLI, and PowerShell sections do not offer Linux-specific guidance or parameters.
Recommendations
- Add Linux-specific PowerShell examples, including Linux image references and parameters (e.g., Set-AzVMOperatingSystem -Linux).
- Ensure PowerShell snippets for Linux are included wherever Windows PowerShell examples are shown.
- Where possible, alternate the order of Windows and Linux examples, or group them clearly to avoid implicit Windows-first bias.
- Clarify in PowerShell sections whether the example is Windows-only, and provide Linux alternatives if supported.
- Review screenshots and UI instructions to ensure Linux options are visible or explained.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for resizing Azure VMs, including scripts for both single VMs and VMs in availability sets. PowerShell is a Windows-centric tool, and these examples are more numerous and detailed than the Azure CLI examples, which are cross-platform. The Terraform section references both Linux and Windows resources but links only to a Windows quickstart. There are no explicit Linux-specific examples or guidance, and the PowerShell examples are presented before CLI and Terraform, reinforcing a Windows-first pattern.
Recommendations
- Add Bash shell examples for resizing VMs using Azure CLI, highlighting Linux/macOS usage.
- Provide parity in example detail between PowerShell and Azure CLI, including scripts for availability sets and error handling.
- Include links to both Linux and Windows Terraform quickstarts, or provide a Linux-focused Terraform snippet.
- Consider mentioning cross-platform tools (e.g., Bash, Python SDK) alongside PowerShell for scripting.
- Ensure that Linux VM scenarios are explicitly referenced in code samples and explanations.
Virtual Machines
Create a VM from a specialized image version
...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images. However, PowerShell examples are significantly more verbose and detailed, including full network setup and VM configuration, while CLI examples are concise and focus only on the core VM creation steps. PowerShell is a Windows-centric tool, and its prominence and detail may create friction for Linux/macOS users. Additionally, PowerShell examples are often presented immediately after CLI, suggesting a Windows-first approach. No Linux-specific tools (e.g., Bash scripts) or macOS guidance are provided, but Azure CLI is cross-platform.
Recommendations
- Provide equally detailed Azure CLI examples, including network setup and VM configuration, to match the depth of PowerShell examples.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Consider including Bash shell script examples for Linux users, especially for more complex scenarios.
- Clarify that PowerShell examples are primarily for Windows users, and encourage Linux/macOS users to use Azure CLI.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux, frequently references Windows tools (Hyper-V, Convert-VHD PowerShell cmdlet) and provides Windows-centric instructions for VHD creation and conversion. Linux-native alternatives for creating and converting VHDs are not mentioned or are referenced after Windows tools. This creates friction for Linux/macOS users who may not have access to Hyper-V or PowerShell.
Recommendations
- Add instructions and examples for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, dd).
- Mention Linux/macOS alternatives for extracting and manipulating VHD files, such as using tar, qemu-img, or other open-source utilities.
- Present Linux-native workflows before or alongside Windows/Hyper-V instructions, especially in sections where Windows tools are currently referenced first.
- Clarify which steps are Windows-specific and provide equivalent Linux/macOS guidance where possible.
Virtual Machines
Run scripts in a Linux VM in Azure using managed Run Commands
...articles/virtual-machines/linux/run-command-managed.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation is focused on Linux VMs and provides extensive Azure CLI and PowerShell examples for managing Run Commands. However, PowerShell examples are given equal or greater prominence than Azure CLI, despite PowerShell being a Windows-centric tool. Several notes and examples reference Windows-specific tools (e.g., New-AzStorageBlobSASToken, PowerShell script URIs, Windows parameter handling), and in some cases, Windows terminology or patterns are described before their Linux equivalents. REST API and ARM template examples use PowerShell script syntax (Write-Host, .ps1) even in Linux contexts, and some explanations default to Windows behaviors before clarifying Linux differences.
Recommendations
- Prioritize Azure CLI examples and explanations, as CLI is more native to Linux environments.
- Where PowerShell is used, clarify its cross-platform support and provide Bash or shell script alternatives.
- In REST and ARM template examples, use Linux shell script syntax (e.g., 'echo Hello World!' or '.sh' files) instead of PowerShell (.ps1) for Linux VM scenarios.
- When discussing parameter handling, describe Linux behaviors first, then Windows, or clearly separate the two.
- Reduce references to Windows-specific tools (e.g., New-AzStorageBlobSASToken) or provide Linux-native alternatives (such as Azure CLI commands for generating SAS tokens).
- Ensure all examples and notes are tailored for Linux users, especially in sections where Windows terminology or tools are used.
Virtual Machines
Create and upload a Red Hat Enterprise Linux VHD for use in Azure
...les/virtual-machines/linux/redhat-create-upload-vhd.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides step-by-step instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, throughout the guide, Windows-centric tools and workflows (notably Hyper-V Manager) are consistently presented first and in greater detail. References to Windows tools (e.g., Hyper-V Manager, PowerShell convert-vhd cmdlet) appear before Linux equivalents, and the VM creation workflow often assumes Hyper-V as the starting point, even for Linux VMs. Linux-native hypervisors (KVM, VMware) are covered, but their sections are secondary and sometimes reference steps from the Hyper-V workflow, reinforcing Windows as the default environment.
Recommendations
- Reorder sections so Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, reflecting the primary audience for RHEL.
- Provide Linux-native disk conversion instructions (e.g., qemu-img) before Windows/Hyper-V tools.
- Avoid referencing Hyper-V Manager as the default VM creation tool for Linux VMs; instead, highlight virt-manager, virsh, or VMware Workstation/ESXi.
- Clarify that PowerShell and Hyper-V tools are optional for users on Windows, and provide equivalent Linux/macOS commands wherever possible.
- Ensure that all steps referenced from Hyper-V sections are fully explained in Linux-native hypervisor sections, rather than requiring cross-referencing.
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Windows and Linux coverage for Azure Compute Gallery, but there is a notable Windows bias in several areas. PowerShell examples and references are frequent and often appear before or alongside CLI examples, with some links and examples specifically referencing Windows workflows (e.g., Sysprep, Windows VHD upload). Windows tools and terminology (such as Sysprep, PowerShell, Windows-specific upload instructions) are mentioned more prominently or before Linux equivalents. While Linux is supported and referenced, the documentation tends to default to Windows-first patterns and tools.
Recommendations
- Ensure Linux CLI examples are presented before or equally alongside PowerShell examples.
- Provide explicit Bash/Linux shell examples for all PowerShell commands.
- Where Windows tools (e.g., Sysprep) are mentioned, ensure Linux equivalents (e.g., waagent) are described with equal prominence and detail.
- Add links to Linux-specific workflows and troubleshooting guides where Windows-specific links are provided.
- Review FAQ and scenario sections to ensure Linux scenarios are described with the same depth as Windows scenarios.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides multiple PowerShell examples for resizing VMs, including detailed scripts for both standalone VMs and VMs in availability sets. PowerShell is a Windows-centric tool, and its examples are more extensive and appear before Azure CLI examples. The Terraform section references a Windows VM quickstart and highlights Windows-specific code. While Azure CLI examples are present and cross-platform, the prominence and depth of PowerShell content, along with references to Windows tools and examples, indicate a Windows-first bias. Linux-specific examples or parity in scripting depth are missing.
Recommendations
- Expand CLI examples to match the depth and scenarios covered in PowerShell (e.g., availability sets, error handling).
- Add explicit Bash shell examples for Linux users, including how to run Azure CLI commands in Bash.
- Provide Terraform examples for azurerm_linux_virtual_machine alongside Windows examples.
- Ensure that Linux VM scenarios are referenced equally in code samples and explanations.
- Consider reordering sections so that cross-platform tools (Azure CLI, Terraform) are presented before Windows-specific tools (PowerShell).
Virtual Machines
Create a VM from a generalized image in a gallery
...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Linux and Windows examples in CLI and REST sections, but PowerShell sections are heavily Windows-centric, with all PowerShell VM creation examples defaulting to Windows VMs (using Set-AzVMOperatingSystem -Windows). Windows-specific constructs (e.g., RDP port, Windows credential prompts) are used in PowerShell examples, and Linux VM creation in PowerShell is not shown. In several places, Windows terminology and tools (PowerShell, Windows credential prompts) are presented before or instead of Linux equivalents. However, CLI and REST examples are generally neutral or Linux-first.
Recommendations
- Add PowerShell examples for creating Linux VMs (using Set-AzVMOperatingSystem -Linux) alongside Windows examples.
- Clarify in PowerShell sections that both Linux and Windows VMs can be created, and provide parameter variations for Linux.
- Where possible, avoid defaulting to Windows-specific constructs (e.g., RDP port, Windows credential prompts) in generic VM creation examples.
- Ensure parity in example coverage for both Linux and Windows across all scripting tabs (CLI, PowerShell, REST).
Virtual Machines
Deploy a Trusted Launch VM
...ain/articles/virtual-machines/trusted-launch-portal.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides parity for both Linux and Windows in most areas, especially in Azure CLI and ARM template examples. However, there is a notable bias in the PowerShell sections, where only Windows-based examples are provided (e.g., using Windows images, Windows-specific parameters, and RDP security rules). Additionally, in some PowerShell code, the Windows scenario is shown first or exclusively, and Windows-centric tools and patterns (like RDP port rules) are used without Linux equivalents. The overall structure tends to present Windows/PowerShell before Linux in some places.
Recommendations
- Add PowerShell examples for Linux VMs, including using Linux images and Linux-specific configuration (e.g., SSH port rules instead of RDP).
- Where PowerShell is shown, provide both Windows and Linux variants, or clearly indicate which OS the example applies to.
- In PowerShell network security group examples, include SSH (port 22) rules for Linux, not just RDP (port 3389) for Windows.
- When listing deployment methods or examples, alternate the order or present Linux and Windows equally, rather than defaulting to Windows/PowerShell first.
- Review all code snippets and ensure that Linux users can follow along without needing to translate Windows-specific steps.
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
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux guidance for upgrading Gen1 VMs to Trusted launch, but Windows-specific tools (MBR2GPT.exe, Defrag, PowerShell) are mentioned first and in greater detail. The PowerShell upgrade example is shown before the CLI example, and ARM template deployment steps use PowerShell. Windows disk conversion and troubleshooting are much more detailed, while Linux instructions are brief and mostly validation steps. Windows tools and commands (MBR2GPT.exe, Defrag, reagentc) are referenced exclusively for disk conversion and troubleshooting, with no Linux disk conversion guidance provided.
Recommendations
- Add Linux disk conversion guidance for cases where Gen1 Linux VMs do not have GPT/EFI (e.g., using gdisk, parted, or other tools).
- Provide Linux-specific troubleshooting steps for disk layout and EFI partition issues.
- Include ARM template deployment steps using Azure CLI, not just PowerShell.
- Ensure Linux instructions are as detailed as Windows, especially for disk conversion and upgrade validation.
- Consider showing CLI examples before PowerShell, or presenting them side-by-side.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides detailed PowerShell examples for resizing Azure VMs, including advanced scenarios (e.g., availability sets), while the Azure CLI section is less emphasized and lacks parity in depth and explanation. PowerShell is presented before CLI, and the Terraform example references a Windows-specific quickstart. There are no explicit Linux/macOS shell examples (e.g., Bash), and the Terraform code sample is Windows-focused. This creates friction for Linux/macOS users, who may prefer CLI or Bash-based workflows.
Recommendations
- Provide Bash shell examples using Azure CLI for resizing VMs, with explanations matching the PowerShell section.
- Ensure CLI examples cover advanced scenarios (e.g., availability sets) with the same level of detail as PowerShell.
- Add a Linux-focused Terraform example or reference, or clarify that the steps are identical for Linux VMs.
- Present CLI examples before PowerShell, or clarify that both are equally supported.
- Avoid referencing only Windows-specific Terraform quickstarts; include or link to Linux quickstarts as well.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The FAQ for Trusted Launch covers both Windows and Linux VM scenarios, but there is a notable pattern where Windows/PowerShell examples and terminology are presented first or more prominently. CLI and PowerShell examples are given for most tasks, but Linux-specific CLI/bash examples are sometimes secondary or omitted. Windows terminology and links (e.g., Secure Boot, Hyper-V) appear before Linux equivalents, even when both are supported. However, Linux-specific guidance (e.g., SBInfo tool installation) is included, and the documentation does not exclude Linux users from completing tasks.
Recommendations
- Ensure that Linux CLI/bash examples are presented alongside or before PowerShell/Windows examples where applicable.
- Where possible, provide parity in example output for both Windows and Linux images (e.g., show both Windows and Linux sample JSON outputs).
- Explicitly mention Linux tools and workflows in introductory sections, not just in troubleshooting.
- Review the order of examples and links to avoid consistently prioritizing Windows/PowerShell.
- Add more Linux-focused troubleshooting and validation steps where relevant.
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 is generally cross-platform and explicitly states Trusted Launch applies to both Linux and Windows VMs. However, there are several subtle signs of Windows bias: Windows examples and references (such as ARM templates for Windows VMs) are listed first, links to Secure Boot and vTPM documentation point to Windows-focused resources, and virtualization-based security (VBS) and HVCI sections are Windows-only without clarifying their lack of Linux applicability. The only explicit example templates are for Windows VMs, with no Linux equivalents shown.
Recommendations
- Add ARM template deployment examples for Linux VMs alongside Windows examples.
- Include links to Linux-specific documentation for Secure Boot and vTPM, or clarify when referenced resources are Windows-only.
- In sections describing features like VBS and HVCI, explicitly state that these are Windows-only and note Linux alternatives or limitations.
- Ensure parity in example code, deployment walkthroughs, and troubleshooting steps for both Linux and Windows users.