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 476-500 of 818 flagged pages
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation generally covers both Windows and Linux VMs, but several sections show Windows bias. Windows tools (PowerShell) are mentioned before Linux equivalents (Azure CLI), and some examples or links are Windows-first. The Antimalware section is Windows-centric, with no Linux alternative discussed. In the Key Vault section, PowerShell is recommended for Windows and CLI for Linux, but the ordering and emphasis favor Windows. Some cross-linking (e.g., SSH from Windows to Linux) is present, but Linux usage patterns are less detailed.
Recommendations
- Provide Linux alternatives or equivalents for Windows-only features (e.g., Antimalware).
- Present examples and tool recommendations for both platforms side-by-side, or alternate which comes first.
- Expand Linux-specific guidance, especially for security tooling and automation.
- Ensure parity in depth and clarity of instructions for Linux and Windows users.
- Explicitly state when features are Windows-only and suggest Linux alternatives if available.
Create Pull Request
Virtual Machines
Azure premium storage: Design for high performance
...ticles/virtual-machines/premium-storage-performance.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Sql Server Bias
Missing Linux Example
Summary
The documentation page demonstrates moderate Windows bias. Windows tools (PerfMon, Storage Spaces, PowerShell) are mentioned before or more prominently than their Linux equivalents (iostat, MDADM). SQL Server (a Windows-centric workload) is used as the primary example throughout, with Linux alternatives or examples rarely provided. Disk striping instructions are more detailed for Windows (including PowerShell and Server Manager UI), while Linux is referenced briefly with a link. Some benchmarking and performance measurement sections mention Windows tools first or in more detail. Linux parity is present in some areas (e.g., iostat, MDADM, Linux benchmarking links), but Windows-centric patterns and examples dominate.
Recommendations
- Provide Linux examples and instructions with equal detail and prominence as Windows, especially for disk striping, benchmarking, and performance measurement.
- Use a mix of application examples (e.g., PostgreSQL, MySQL, Oracle) alongside SQL Server to illustrate scenarios for Linux users.
- List Linux tools (e.g., iostat, vmstat, MDADM) before or alongside Windows tools, not after.
- Expand Linux-specific configuration guidance (e.g., file system tuning, RAID setup) to match the depth given to Windows.
- Add step-by-step Linux command examples where PowerShell or Windows UI steps are shown.
- Balance references to Windows and Linux in tables, diagrams, and summary sections.
Virtual Machines
Set up Azure HPC or AI VMs
.../blob/main/articles/virtual-machines/set-up-hpc-vms.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally maintains parity between Windows and Linux, referencing both platforms for VM creation, disk attachment, SSH connection, and GPU driver installation. However, in the GPU driver installation section, only Windows instructions are provided for AMD GPUs, with no Linux equivalent. Additionally, Windows examples (e.g., AMD GPU drivers) are listed before Linux ones, and some links (e.g., SSH from Windows) are referenced after Linux/macOS, but the order is inconsistent.
Recommendations
- Add instructions or links for installing AMD GPU drivers on Linux VMs, if supported.
- Ensure that Linux and Windows examples are presented in parallel or grouped by OS for clarity.
- Review the order of examples and links to avoid subtle prioritization of Windows over Linux/macOS.
- Explicitly state if certain features (e.g., AMD GPU drivers) are not available on Linux, to avoid confusion.
Virtual Machines
Share Gallery Images Across Tenants by Using an App Registration
...icles/virtual-machines/share-using-app-registration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for sharing gallery images across tenants. However, the PowerShell section is significantly more detailed, including full networking and VM configuration steps, while the CLI section is much shorter and omits these details. The PowerShell examples use Windows-centric tools and patterns (e.g., RDP rules, Windows OS configuration), and the networking setup is only shown for PowerShell. This creates friction for Linux/macOS users who may prefer CLI or need Linux-specific guidance.
Recommendations
- Expand the Azure CLI section to include full VM creation steps, including networking setup, similar to the PowerShell example.
- Provide Linux-specific VM creation examples (e.g., using --os-type Linux, SSH configuration, Linux-friendly networking rules).
- Ensure parity in detail and completeness between CLI and PowerShell sections.
- Avoid Windows-centric configuration in generic examples; offer both Windows and Linux VM creation scenarios.
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 (e.g., Hyper-V nested virtualization) and tools (NTTTCP for bandwidth testing) without mentioning Linux equivalents or alternatives. Windows features and resources are sometimes referenced first or exclusively, while Linux-specific guidance is minimal or absent.
Recommendations
- When mentioning nested virtualization, include links or notes about Linux support and relevant technologies (e.g., KVM, nested virtualization on Linux).
- For bandwidth testing, mention Linux tools (e.g., iperf, netperf) alongside NTTTCP, and provide links to their usage in Azure.
- Ensure feature support and optimization notes explicitly address both Windows and Linux, with links to Linux documentation where available.
- Review all resource links and examples to ensure Linux parity, adding Linux-specific documentation where missing.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is given extensive coverage with multiple detailed scripts, including scenarios for availability sets and local execution. The CLI section is present and cross-platform, but is less detailed than PowerShell. The Terraform example references a Windows VM quickstart, and the code sample is for a Windows VM. There are no explicit Linux-specific examples, and Windows tools/patterns (PowerShell, Windows VM resource blocks) are mentioned first or exclusively in several places.
Recommendations
- Add explicit Linux VM examples in the Terraform section, referencing azurerm_linux_virtual_machine and providing sample code.
- Balance PowerShell and CLI coverage by expanding CLI examples to cover all scenarios shown for PowerShell, including availability sets and local execution.
- Reference Linux quickstart documentation alongside Windows quickstart in the Terraform section.
- Ensure that examples and code samples alternate or equally represent both Windows and Linux VMs.
- Add notes clarifying that Azure CLI commands work identically on Linux, macOS, and Windows, and provide shell script examples where appropriate.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented as the primary scripting example, and the CLI authentication example uses PowerShell syntax rather than Bash. There are no explicit Linux/macOS shell examples (e.g., Bash), and Windows-centric tools (PowerShell, Azure portal) are mentioned before cross-platform alternatives. This may create friction for Linux/macOS users who expect Bash or shell examples and parity in migration instructions.
Recommendations
- Provide Bash shell examples for Azure CLI commands, using standard Bash variable syntax and command chaining.
- Clarify that Azure CLI commands are cross-platform and show both Windows (PowerShell) and Linux/macOS (Bash) usage patterns.
- Include explicit instructions for Linux/macOS users, such as opening a terminal and using Bash, especially in the Azure CLI section.
- Where PowerShell is used, offer equivalent Bash commands for Linux/macOS users.
- Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., referencing Windows-only features or UI elements).
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation provides detailed instructions for resizing VMs using the Azure portal and Azure PowerShell, but does not include equivalent examples for Azure CLI, which is more commonly used on Linux/macOS. PowerShell is Windows-centric, and its exclusive use in code samples creates friction for Linux/macOS users. The ordering also presents Windows/PowerShell methods before mentioning CLI, and no CLI example is shown.
Recommendations
- Add step-by-step instructions and code samples for resizing VMs using Azure CLI, which works cross-platform.
- Present CLI and PowerShell examples side-by-side or in parallel sections, rather than PowerShell-only.
- Explicitly mention that Azure CLI is available and suitable for Linux/macOS users, and link to relevant CLI documentation.
- Consider including Bash or shell script examples for common tasks.
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 (a Windows-centric tool) is given its own section with detailed examples, and references to Windows-specific VM creation are provided before Linux equivalents. The 'Next steps' section links to Windows instructions first for both Portal and PowerShell, while the CLI section links to Linux instructions. There is no explicit Linux PowerShell example, and the CLI examples, while cross-platform, are not highlighted as the primary method for Linux users.
Recommendations
- Ensure that Linux-specific instructions are provided and linked equally in all tool sections, especially in 'Next steps'.
- Present CLI examples before or alongside PowerShell examples, as CLI is more universally applicable across platforms.
- Add explicit notes or examples for Linux users in the PowerShell section, or clarify PowerShell's cross-platform capabilities.
- Balance references to Windows and Linux VMs throughout, ensuring neither is prioritized in example ordering or linking.
- Where possible, provide bash script examples for Linux users alongside PowerShell for Windows users.
Virtual Machines
Create SSH keys with the Azure CLI
...b/main/articles/virtual-machines/ssh-keys-azure-cli.md
Medium Priority
View Details →
Detected Bias Types
Linux First
Missing Windows Example
Summary
The documentation is strongly oriented toward Linux workflows: all command examples use Linux-style paths, Bash commands, and Linux file permission patterns (chmod). There are no PowerShell or Windows Command Prompt examples, nor any mention of Windows-specific SSH key storage locations or usage patterns. While the page claims applicability to both Linux and Windows VMs, it does not provide guidance for Windows users on generating, storing, or using SSH keys with Azure CLI.
Recommendations
- Add equivalent examples for Windows users, including PowerShell and Command Prompt commands.
- Document typical Windows SSH key storage paths (e.g., C:\Users\<username>\.ssh\).
- Explain how to set file permissions for private keys on Windows, or note differences in security practices.
- Clarify any differences in Azure CLI usage or SSH key handling between Linux/macOS and Windows platforms.
- Consider alternating or parallel presentation of Linux and Windows examples to improve parity.
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 Windows bias primarily in the 'Connect to the VM' section, where only a PowerShell prompt is mentioned for running the SSH command, with no reference to Linux or macOS terminals. Additionally, the example assumes a Windows file path format and does not provide Linux/macOS equivalents. The page also links to a guide for using SSH from Windows when discussing Linux VMs, further reinforcing the Windows-centric approach.
Recommendations
- Include explicit instructions for connecting to the VM from Linux and macOS terminals, such as using the Terminal app and appropriate file paths (e.g., ~/.ssh/mySSHKey.pem).
- Provide example SSH commands for Linux/macOS alongside the PowerShell example.
- Avoid referencing only Windows tools or guides when discussing Linux VM management; link to platform-neutral or Linux/macOS-specific documentation as well.
- Clarify that the SSH command works on all platforms and note any platform-specific considerations (e.g., file permissions on private keys in Linux/macOS).
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 exhibits a Windows bias by consistently using Windows-centric examples in JSON templates (e.g., 'osType': 'Windows', 'windowsConfiguration', Windows-specific image references), mentioning Windows configuration options, and omitting explicit Linux-focused examples or templates. Linux users are referenced only indirectly, with no direct example of Linux VM creation or configuration. The only Linux-specific guidance is a link to another page for IMDS sample code, but the main documentation lacks parity in examples and patterns.
Recommendations
- Provide explicit Linux VM examples in all JSON templates (e.g., 'osType': 'Linux', Linux image references, and Linux-specific configuration options).
- Include Linux-specific sections or notes alongside Windows ones, such as 'linuxConfiguration' in the VMSS example.
- Ensure that Linux examples are shown with equal prominence and order as Windows examples.
- Add sample user data scripts relevant to Linux (e.g., bash scripts) in addition to or instead of generic base64 strings.
- Clarify any differences in user data handling between Windows and Linux VMs.
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 demonstrates 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 or generic statements. Windows examples and tools are frequently presented first or exclusively, while Linux alternatives are less emphasized or missing.
Recommendations
- Provide equally detailed Linux upgrade instructions, including steps for converting MBR to GPT and adding EFI partitions for non-endorsed distros.
- Include Linux-specific troubleshooting sections analogous to the Windows troubleshooting (e.g., handling partition issues, EFI setup failures).
- Present Linux and Windows examples side-by-side or in parallel, rather than Windows-first.
- Reference Linux disk management and partitioning tools (e.g., gdisk, parted) where appropriate.
- Offer guidance for BitLocker equivalents on Linux (e.g., LUKS) if relevant.
- Clarify and expand support for custom Linux images, including manual steps if Azure Marketplace images are not used.
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 both Linux and Windows guidance for deploying Trusted Launch VMs, but there is a notable Windows bias in several areas. PowerShell examples are extensive and exclusively use Windows images and parameters, while Linux equivalents are either missing or less detailed. In multi-step PowerShell workflows, only Windows VM creation is shown, and Windows-specific tools and patterns (like RDP rules, Bitlocker notes) are referenced without Linux parity. In some sections, Windows examples or terminology appear first or are more prominent.
Recommendations
- Add equivalent PowerShell examples for Linux VM deployment, including Linux-specific parameters and OS disk handling.
- Ensure that multi-step PowerShell workflows (such as network configuration and VM creation from gallery images) include Linux variants.
- Balance the order of examples so that Linux and Windows are presented with equal prominence, or alternate which comes first.
- Where Windows-specific tools or concepts are mentioned (e.g., Bitlocker, RDP), include Linux equivalents (e.g., LUKS, SSH) or clarify applicability.
- Review screenshots and UI instructions to ensure Linux scenarios are visually represented alongside Windows.
- Expand notes and tips to address Linux-specific concerns (e.g., secure boot implications for unsigned drivers, SSH key management).
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
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation page exhibits several signs of Windows bias. Examples and code snippets consistently use Windows-centric images (e.g., 'MicrosoftWindowsServer'), and the ARM template quickstart links to a Windows-specific template. PowerShell instructions are detailed and prominent, while Linux-specific examples (such as using Ubuntu or other Linux images) are absent from all code samples. The extension publisher table mentions Linux, but no Linux image or command-line examples are provided. The documentation assumes familiarity with Windows tooling and patterns, and Windows is prioritized in examples and references.
Recommendations
- Add explicit Linux examples (e.g., using Ubuntu or Red Hat images) in ARM template, CLI, and PowerShell sections.
- Provide sample code snippets for Linux image references alongside Windows examples.
- Link to both Windows and Linux quickstart ARM templates.
- Clarify any differences or requirements for Linux Trusted launch enablement (e.g., Secure Boot, vTPM support).
- Ensure extension publisher examples show both Windows and Linux usage.
- Balance PowerShell and CLI instructions, and mention cross-platform alternatives where possible.
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 signs of Windows bias. Windows terminology and features (e.g., Hotpatching for Windows Server Azure Edition) are described in detail, while equivalent Linux features are not mentioned or are less prominent. References to scheduled events and maintenance notifications link to Windows documentation first, and PowerShell is mentioned as a deployment tool before Azure CLI. Some features (like Hotpatch) are Windows-only, and examples or links for Linux are sometimes secondary or missing.
Recommendations
- Ensure that Linux examples and documentation links are presented alongside or before Windows equivalents, especially in sections like scheduled events and maintenance notifications.
- Highlight Linux-specific features or limitations where Windows-only features (e.g., Hotpatch) are discussed, and provide alternative solutions for Linux users.
- When listing deployment tools, mention Azure CLI and Linux-native tools before or alongside PowerShell, and provide example commands for both platforms.
- Add more explicit Linux usage examples and workflows throughout the documentation to ensure parity.
- Clearly indicate when a feature is Windows-only and suggest Linux alternatives or workarounds.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits several forms of Windows bias: Windows concepts and links (e.g., Secure Boot, Hyper-V Shielded VM) are introduced first and referenced more frequently than Linux equivalents. Command examples are often provided for both Azure CLI and PowerShell, but PowerShell (a Windows-centric tool) is given equal or greater prominence, and Linux-specific shell examples are less common or absent in some sections. Troubleshooting and validation workflows reference Windows tools and documentation before Linux alternatives. Some sections lack Linux-specific examples or troubleshooting steps, and Windows terminology is used as the default.
Recommendations
- Ensure Linux shell (bash) examples are provided alongside PowerShell for all CLI commands, especially in troubleshooting and validation sections.
- When referencing Secure Boot and other security features, include links to Linux documentation (e.g., UEFI Secure Boot on Linux, Linux kernel documentation) in addition to Windows resources.
- Present Linux and Windows examples in parallel tabs or sections, with equal prominence and ordering.
- Expand troubleshooting steps to include Linux-specific workflows and tools, not just Windows-centric approaches.
- Avoid using Windows terminology as the default; clarify when instructions apply to both platforms or provide platform-specific guidance.
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 step-by-step instructions for deploying Premium SSD v2 disks with VMs in an availability set using Azure CLI, PowerShell, and the Azure Portal. However, the VM creation examples in both CLI and PowerShell use Windows images (e.g., Win2016Datacenter), and there are no explicit Linux VM examples or references. PowerShell instructions are given equal prominence to CLI, but PowerShell is a Windows-centric tool. There is no mention of Linux-specific considerations, nor are there examples for Linux VM images or SSH credential handling. The documentation implicitly prioritizes Windows by example and tooling, which may create friction for Linux/macOS users.
Recommendations
- Include explicit Linux VM creation examples in both Azure CLI and PowerShell sections (e.g., use UbuntuLTS or CentOS images).
- Add notes or examples for SSH credential setup for Linux VMs.
- Clarify that Azure CLI is cross-platform and provide guidance for Linux/macOS users where relevant.
- Mention Linux-specific considerations (e.g., disk formatting, mounting) if applicable.
- Balance the order and prominence of Windows and Linux examples to avoid implicit prioritization.
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 consistently uses Windows-centric examples and references, such as the 'vm-simple-windows' template and Windows image parameters, without providing equivalent Linux-focused examples or parameters. All JSON code samples use Windows images, and the only referenced quickstart template in the walkthrough is for Windows. Linux is only mentioned in the 'Next steps' section as a link, not in the main instructional content.
Recommendations
- Provide parallel Linux VM examples throughout the document, including JSON snippets referencing Linux images and parameters.
- Reference both Windows and Linux quickstart templates when illustrating template changes and comparisons.
- Include explanations of any Linux-specific considerations (e.g., osType, imageReference) in the template sections.
- Alternate or balance the order of Windows and Linux examples to avoid implicit prioritization.
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, when referencing further steps for creating a VM from a disk and attaching restored disks, the links provided point only to Windows-specific guides. There are no Linux-specific instructions or examples, and Linux parity is not addressed in these critical steps.
Recommendations
- Include links to equivalent Linux documentation for creating a VM from a disk and attaching managed disks.
- Add notes or examples for Linux users, clarifying any differences in the process.
- Ensure that referenced guides cover both Windows and Linux scenarios, or provide parallel instructions.
- Explicitly mention that the process applies to both Windows and Linux VMs, or highlight any OS-specific considerations.
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 mild Windows bias. Application consistency is described in detail for Windows (using VSS writers), while Linux is mentioned only as supporting file system consistency and requiring pre- and post-scripts, with no further guidance or examples. Windows terminology (VSS) is introduced first and explained, whereas Linux alternatives are referenced generically. No Linux-specific examples, tools, or scripts are provided, and troubleshooting guidance is not differentiated by OS.
Recommendations
- Provide explicit Linux examples for application-consistent restore points, including sample pre- and post-scripts.
- List common Linux tools or patterns (e.g., fsfreeze, custom shell scripts) for achieving application consistency.
- Balance the explanation order: describe Linux and Windows approaches equally, rather than focusing on Windows first.
- Add troubleshooting steps specific to Linux VM agent and extension issues.
- Clarify any differences in restore point behavior or limitations between Windows and Linux VMs.
Virtual Machines
Overview of VM Applications in the Azure Compute Gallery
...blob/main/articles/virtual-machines/vm-applications.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. Windows tools (PowerShell, cmd.exe, msiexec) are mentioned frequently and sometimes before Linux equivalents. Troubleshooting and extension status examples are given only in PowerShell, with no Linux CLI or Bash alternatives. File renaming and installer examples for Windows are more detailed and precede Linux sections. Some Linux troubleshooting and operational examples are missing or less emphasized.
Recommendations
- Provide equivalent Linux CLI (az CLI, Bash) commands for troubleshooting and extension status checks, alongside PowerShell examples.
- Ensure Linux examples (e.g., install/remove scripts, file renaming) are presented with equal detail and prominence as Windows examples.
- When discussing command interpreters, mention Bash and Linux scripting patterns before or alongside Windows tools.
- Add Linux/macOS-specific troubleshooting steps and operational guidance where only Windows/PowerShell is currently shown.
- Balance the order of presentation so Linux and Windows are treated equally (e.g., alternate which OS is described first in sections).
Virtual Machines
Create and deploy VM Application on Azure
...in/articles/virtual-machines/vm-applications-how-to.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Many code samples and automation pipeline templates (GitHub Actions, Azure DevOps, Jenkins, GitLab) default to Windows-centric filenames (e.g., app.exe, app-config.json) and explicitly set --os-type Windows when creating VM Application definitions, even though Linux is supported. PowerShell examples are abundant and sometimes more detailed than their Bash/Linux equivalents. Windows tools (msiexec, powershell.exe, .exe installers) are featured prominently, often before or instead of Linux alternatives. While Linux/Bash examples are present for packaging and install scripts, the automation and CI/CD sections lack parity for Linux-first scenarios and do not provide clear guidance for deploying Linux applications in pipelines.
Recommendations
- In all pipeline and automation examples (GitHub Actions, Azure DevOps, Jenkins, GitLab), provide parallel Linux-focused samples (e.g., using app.sh, app.deb, app.rpm, app-config.yaml, and --os-type Linux).
- When showing code for creating VM Application definitions, alternate or equally present --os-type Linux and --os-type Windows, or clarify that both are supported.
- In install script tabs, ensure Linux formats (.sh, .deb, .rpm, .tar.gz) are shown first or equally with Windows formats (.exe, .msi, .ps1).
- Avoid defaulting to Windows filenames (app.exe, app-config.json) in generic templates; use neutral or alternate with Linux equivalents.
- Add explicit guidance for Linux/macOS users in CI/CD pipeline sections, including how to package, upload, and deploy Linux applications.
- Balance PowerShell and Bash examples in all sections, ensuring Linux users have clear, complete instructions.
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 Azure CLI and PowerShell examples for most scenarios, but the PowerShell sections are significantly more detailed, with full resource creation flows and advanced configuration. The PowerShell examples are inherently Windows-centric, and the VM creation steps in PowerShell default to Windows VMs (using Set-AzVMOperatingSystem -Windows), with no equivalent Linux PowerShell example. Network security rules in PowerShell focus on RDP (port 3389), which is Windows-specific, and the password requirements link points to a Windows FAQ. In REST examples, both Linux and Windows VM creation are shown, but the PowerShell bias remains strong throughout. The CLI examples do show Linux VM creation with SSH keys, but the PowerShell sections are more comprehensive and default to Windows patterns.
Recommendations
- Add PowerShell examples for Linux VM creation, including Set-AzVMOperatingSystem -Linux and SSH key authentication.
- Balance the detail level between CLI and PowerShell sections, ensuring Linux scenarios are equally covered in PowerShell.
- When showing network security rules, include examples for SSH (port 22) alongside RDP (port 3389) in PowerShell.
- Reference Linux password/SSH requirements, not just Windows password complexity.
- Where possible, avoid defaulting to Windows-centric resource names, patterns, or tools in examples.
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 Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images. However, the PowerShell examples are extensive, using Windows-centric cmdlets and patterns, while the CLI examples are much shorter and less detailed. The PowerShell sections include full networking setup and resource creation, whereas the CLI sections only show basic VM creation. The PowerShell examples use Windows-specific tools and terminology, and are presented alongside CLI, but with much more detail. There is a subtle Windows bias in the depth and completeness of examples, and in the use of PowerShell as the primary scripting language for advanced scenarios.
Recommendations
- Expand Azure CLI examples to include full networking setup and resource creation, matching the detail of PowerShell examples.
- Add Bash shell scripting examples for Linux users, especially for multi-step workflows.
- Clarify that PowerShell examples are cross-platform (if true), or provide equivalent Bash/Cloud Shell scripts.
- Avoid using Windows-specific terminology (e.g., RDP rules) without also mentioning Linux equivalents (e.g., SSH).
- Ensure that advanced scenarios (e.g., RBAC, cross-tenant, networking) have parity between CLI and PowerShell, and are not PowerShell-only.