Virtual Machines
1080
Total Pages
1005
Linux-Friendly Pages
75
Pages with Bias
6.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
815 issues found
Showing 101-125 of 815 flagged pages
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, it frequently uses PowerShell cmdlets (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand) for examples and instructions, which are Windows-centric tools. PowerShell examples are provided in detail and often before or in greater depth than Azure CLI examples. REST API and ARM template examples also use Windows-style script syntax (e.g., Write-Host, .ps1 files) without Linux/bash equivalents. Some explanations reference Windows-specific behaviors (such as 'Secondary Logon' service), and there are missing Linux/bash script examples in several sections.
Recommendations
- Provide equivalent bash/Linux shell script examples for REST API and ARM template sections (e.g., use 'echo' or bash scripts instead of 'Write-Host' or .ps1).
- Expand Azure CLI examples to match the depth and breadth of PowerShell examples, including advanced scenarios like parameter passing, output streaming, and sequential execution.
- Clarify that PowerShell cmdlets can be used cross-platform, but also highlight native Linux tools (bash, sh) and Azure CLI as primary options for Linux users.
- Ensure that script examples and explanations use Linux conventions (e.g., .sh files, bash syntax) where appropriate, especially in sections about Linux VMs.
- Move Azure CLI examples before PowerShell examples to prioritize Linux-native tooling.
Create Pull Request
Virtual Machines
Share an Azure Managed Disk across VMs
...cs/blob/main/articles/virtual-machines/disks-shared.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux coverage, but Windows examples and tools (WSFC, CSV, Windows clustering, Windows-specific templates) are presented first and in greater detail. Windows clustering patterns and terminology (WSFC, CSV) are referenced before Linux equivalents, and Windows sample workloads are listed before Linux. Linux tools and cluster managers (Pacemaker, Corosync, sg_persist, fence_scsi) are mentioned, but with less depth and fewer practical examples. Performance throttling examples are Windows-first, with Linux scenarios appearing later.
Recommendations
- Present Linux and Windows examples in parallel or alternate order, rather than Windows-first.
- Expand Linux sample workloads with practical, step-by-step examples (e.g., Pacemaker configuration, clustered filesystem setup).
- Provide Linux-specific templates and links, similar to Windows (e.g., for clustered file servers or SAP workloads).
- Include Linux command-line examples for disk reservation and cluster setup, not just tool mentions.
- Ensure performance throttling examples include Linux scenarios with equal detail.
Virtual Machines
Deploy a ZRS managed disk
...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying ZRS managed disks, but there is notable bias towards Windows/PowerShell. PowerShell examples are extensive and use Windows-centric patterns (e.g., Windows VM images, Windows credentials, ConvertTo-SecureString), and PowerShell is presented before Linux-friendly alternatives in some sections. Resource Manager Template examples also use PowerShell commands for deployment, rather than cross-platform CLI or ARM template JSON. The Azure CLI examples use Ubuntu images, but PowerShell and ARM sections default to Windows images and Windows-specific configuration.
Recommendations
- Provide ARM template deployment examples using pure JSON and Azure CLI, not PowerShell.
- Add PowerShell examples for Linux VM images and credentials, or clarify how to adapt for Linux.
- Ensure Azure CLI and PowerShell examples are equally detailed and placed side-by-side, not with PowerShell first.
- Explicitly mention cross-platform compatibility and how Linux/macOS users can use Azure CLI or ARM templates.
- Where possible, avoid Windows-specific credential patterns (e.g., ConvertTo-SecureString) in generic deployment examples.
Virtual Machines
Deploy a Premium SSD v2 managed disk
...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 disks, but all CLI and PowerShell examples use Windows VM images (e.g., 'Win2016Datacenter') and Windows-style authentication (username/password). There are no explicit Linux VM deployment examples, and the instructions do not mention or illustrate how to deploy or attach Premium SSD v2 disks to Linux VMs. This may cause confusion or friction for Linux users, who must adapt the examples themselves.
Recommendations
- Add explicit Linux VM deployment examples in both Azure CLI and PowerShell sections, using a Linux image (e.g., 'UbuntuLTS') and SSH authentication.
- In variable initialization, show both Windows and Linux image options, or provide a note explaining how to select a Linux image.
- Include a brief section or note clarifying that Premium SSD v2 disks are fully supported on Linux VMs, and link to Linux-specific disk attachment documentation.
- Ensure that the 'Next steps' section links to both Linux and Windows disk attachment guides equally.
Virtual Machines
Ultra Disks for VMs - Azure Managed Disks
...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is intended for both Linux and Windows VMs, but consistently uses Windows VM images (e.g., Win2016Datacenter) in all CLI and PowerShell examples. There are no examples showing how to deploy Ultra Disks with a Linux VM image, nor any Linux-specific considerations or commands. Windows is always the default in code samples, and the only Quickstart link is for Windows VMs. This creates friction for Linux users, who must adapt the examples themselves.
Recommendations
- Add parallel examples for Linux VM images (e.g., Ubuntu, CentOS) in CLI and PowerShell sections.
- Include a Quickstart link for creating a Linux VM in the Azure portal.
- Explicitly mention that the steps are identical for Linux VMs, and provide sample values for Linux images.
- Where VM image is specified, show both Windows and Linux image options.
- Add notes or sections for Linux-specific disk partitioning and formatting guidance.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides extensive PowerShell examples and scripts for enabling Write Accelerator, with detailed step-by-step instructions. Windows-specific tools (Chocolatey, cmd.exe, PowerShell) are mentioned for installing the armclient, and Windows disk/volume managers are referenced before Linux equivalents. While Azure CLI and REST API methods are also documented, the PowerShell approach is given much more prominence and detail, and the installation instructions for armclient are Windows-centric.
Recommendations
- Provide equivalent Bash shell scripts for Linux users alongside PowerShell examples.
- Include instructions for installing armclient on Linux (e.g., via npm, direct download, or other package managers) instead of only Chocolatey.
- Mention Linux disk/volume managers (LVM, MDADM) before or equally with Windows tools in relevant sections.
- Ensure all CLI and REST API examples are shown with both Windows and Linux command syntax where differences exist.
Virtual Machines
Create an encrypted image version with customer-managed keys
.../articles/virtual-machines/image-version-encryption.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for creating encrypted image versions with customer-managed keys. However, PowerShell examples are presented first and in greater detail, including more complex scripting for regional encryption sets. The CLI section is present and functional, but PowerShell receives more prominence and depth. There are no Linux-specific command-line examples (e.g., Bash scripting), but the CLI commands are cross-platform. References to Windows tools (e.g., PowerShell) are more frequent, and links to Windows-specific articles appear in prerequisites, though the feature itself is not Windows-only.
Recommendations
- Present Azure CLI examples before PowerShell, or alternate their order to avoid Windows-first bias.
- Expand CLI examples to match the complexity and detail of PowerShell examples, including scripting for multiple regions and disks.
- Add Bash scripting examples for CLI usage to demonstrate Linux-native workflows.
- Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
- Review prerequisite links to ensure parity between PowerShell and CLI/portal guidance.
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, while focused on Ubuntu Linux VHDs, repeatedly references Windows-centric tools and workflows (Hyper-V, PowerShell's Convert-VHD) as primary methods for creating and converting VHDs. Windows/Hyper-V instructions and links are provided first and in detail, while Linux-native alternatives (such as qemu-img or KVM) are not mentioned. This creates friction for Linux/macOS users, who may not have access to Windows tools or environments.
Recommendations
- Add instructions and examples for creating and converting VHDs using Linux-native tools such as qemu-img, KVM, or VirtualBox.
- Provide links to Linux-specific guides for disk conversion and VM creation.
- Ensure that Linux workflows are presented before or alongside Windows/Hyper-V methods, not after.
- Clarify which steps are platform-agnostic and which are Windows-specific, to help users choose the right path.
Virtual Machines
Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment.
.../includes/virtual-machines-disks-shared-limitations.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation repeatedly references Windows Server Failover Cluster and links exclusively to Windows Server documentation for clustering requirements. There are no mentions of Linux clustering solutions (e.g., Pacemaker, Corosync), nor are Linux-specific limitations or guidance provided. The proximity placement group link is Windows-focused, and Windows clustering is discussed before any Linux alternatives.
Recommendations
- Add information about Linux-based clustering solutions (such as Pacemaker/Corosync) and their compatibility or limitations with Azure shared disks.
- Include links to relevant Linux documentation or Azure guidance for Linux clusters.
- Clarify if the 'basic disks' limitation applies to Linux clusters, or if it is Windows-specific.
- Provide parity in examples and guidance for both Windows and Linux users.
Virtual Machines
Upload a VHD to Azure or copy a disk across regions - Azure CLI
...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a Windows-centric example for uploading a VHD using AzCopy, specifically referencing 'AzCopy.exe' and a Windows file path ('c:\somewhere\mydisk.vhd'), without offering a Linux/macOS equivalent. While the rest of the CLI commands are cross-platform, the AzCopy upload step is presented only for Windows, which may confuse or hinder Linux/macOS users. Additionally, the Windows example appears before any mention of Linux usage, and there is no explicit guidance for Linux/macOS users regarding AzCopy usage or file paths.
Recommendations
- Add a Linux/macOS AzCopy example, using the typical command-line syntax (e.g., './azcopy' or 'azcopy') and a Linux-style file path (e.g., '/home/user/mydisk.vhd').
- Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
- Mention any OS-specific considerations for AzCopy usage, such as executable naming or permissions.
- Present both Windows and Linux/macOS examples side-by-side, or note that the command is identical except for path syntax.
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 covers both Linux and Windows VM image creation with Azure Image Builder, providing parity in most areas. However, there are several sections where Windows/PowerShell tools and examples are emphasized or shown first, such as checksum generation (PowerShell cmdlets), restart customizer (Windows only), and validation examples (PowerShell shown before Shell). Windows-specific tools and commands (e.g., PowerShell, Sysprep, shutdown.exe) are referenced more frequently and sometimes before Linux equivalents. Linux instructions are present but occasionally secondary.
Recommendations
- Where PowerShell is referenced for tasks like checksum generation, add Linux/macOS equivalents (e.g., sha256sum) alongside or before the Windows instructions.
- For customizer and validator examples, alternate the order so Linux/Shell examples are shown first or equally prominent.
- Explicitly note Linux limitations (e.g., no Linux restart customizer) and suggest workarounds or alternatives if possible.
- Ensure all CLI instructions are clearly cross-platform and avoid referencing Windows tools exclusively unless necessary.
- Where possible, provide links to Linux/macOS documentation for relevant tasks (e.g., file hash generation, script execution).
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
While the documentation is focused on Linux VMs and provides extensive Azure CLI examples (which are cross-platform), it exhibits Windows bias in several areas: PowerShell examples are given equal or greater prominence than Azure CLI, and PowerShell-specific tools (e.g., New-AzStorageBlobSASToken) are referenced for generating SAS tokens, with no Linux-native alternatives mentioned. REST API script examples use Windows PowerShell syntax (Write-Host, .ps1), and some example scripts reference Windows conventions (e.g., myscript.ps1) before Linux equivalents (.sh). Additionally, the PowerShell section is more detailed and appears before REST API, and some notes reference Windows-specific behaviors without Linux parity explanations.
Recommendations
- Provide Bash or Linux-native alternatives for generating SAS tokens (e.g., using Azure CLI or azcopy), not just PowerShell.
- In REST API and deployment template examples, use .sh scripts and Linux shell commands (e.g., echo) as the primary example, or at least alternate between Windows and Linux script types.
- Clarify when PowerShell tools are required and offer equivalent Azure CLI or Bash commands for Linux users.
- Ensure that Linux-specific behaviors (such as parameter passing to .sh scripts) are explained with equal detail as Windows behaviors.
- Consider placing Azure CLI examples before PowerShell, as CLI is more universally available on Linux/macOS.
Virtual Machines
Deploy a Premium SSD v2 managed disk
...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 managed disks, but all VM creation examples use Windows images (e.g., 'Win2016Datacenter') and Windows-centric parameters. There are no Linux VM image examples or explicit guidance for Linux users, even though Premium SSD v2 is suitable for Linux workloads. This creates friction for Linux users who must adapt the examples themselves.
Recommendations
- Add Linux VM image examples (e.g., Ubuntu, CentOS) alongside Windows examples in Azure CLI and PowerShell sections.
- Explicitly mention that the disk deployment steps are OS-agnostic, and provide guidance on selecting Linux images.
- In variable initialization, show both Windows and Linux image values, or provide a table of common image references.
- Ensure that authentication examples include SSH for Linux VMs, not just password authentication.
- Clarify any OS-specific considerations for disk attachment or performance tuning.
Virtual Machines
Overview of Azure Disk Storage
...in/articles/virtual-machines/managed-disks-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is generally cross-platform and explicitly states applicability to both Linux and Windows VMs. However, there are several instances where Windows terminology, tools, or documentation are mentioned first or exclusively, and some links and examples are Windows-centric. For example, partitioning and disk size limitations are explained with references to Windows MBR/GPT documentation, and the process for creating images links only to a Windows-specific guide. In the upload VHD section, both Azure CLI (Linux) and PowerShell (Windows) are linked, but the image creation section only references Windows. Some disk management concepts (like drive letters) are described in Windows terms before or instead of Linux equivalents.
Recommendations
- When discussing disk partitioning and size limits, include Linux-specific guidance and documentation (e.g., referencing Linux partitioning tools and GPT/MBR handling).
- For the 'Images' section, provide or link to Linux-specific instructions for creating managed images from generalized Linux VMs.
- When describing disk roles and mounting, ensure Linux device paths and conventions (e.g., /dev/sdX, mount points) are mentioned alongside or before Windows drive letters.
- In all sections where both Azure CLI and PowerShell are relevant, ensure both are always referenced and that Linux-first examples are included where appropriate.
- Review all links to ensure parity between Linux and Windows documentation, especially for critical VM lifecycle tasks.
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
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation is intended for both Windows and Linux VMs, as indicated at the top. However, there are several areas of Windows bias: (1) PowerShell examples are provided alongside CLI, but there are no bash or Linux shell script equivalents; (2) The ARM template example is Windows-centric, defaulting to Windows images and only listing Windows SKUs; (3) In some sections, Windows tools and patterns (like PowerShell) are given equal or more prominence than Linux-native approaches; (4) There are no explicit Linux-focused examples or instructions for Linux-specific configuration (e.g., SSH keys, Linux images in ARM templates).
Recommendations
- In ARM template examples, provide both Windows and Linux image options, or show how to select a Linux image (e.g., Ubuntu, CentOS) and configure SSH authentication.
- Include bash or Linux shell script examples where PowerShell is shown, especially for common tasks like deallocating or updating VMs.
- When listing allowed values for OSVersion or similar parameters, include popular Linux distributions.
- Instruct users on how to configure Linux-specific settings (e.g., SSH keys) in the portal and ARM templates.
- Where possible, alternate the order of CLI and PowerShell examples, or clarify that both are equally supported.
- Explicitly note any differences or additional steps required for Linux VMs, if applicable.
Virtual Machines
Deploy a ZRS managed disk
...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying ZRS managed disks, but PowerShell (a Windows-centric tool) is heavily featured, especially in the Resource Manager Template section. PowerShell examples are shown for ARM template deployment, and the prerequisite steps for ARM templates use PowerShell commands exclusively. Additionally, the PowerShell examples use Windows VM images and configurations, while Azure CLI examples use Ubuntu images. The documentation does not provide Bash or cross-platform scripting alternatives for ARM template deployment or feature registration, and PowerShell is presented before CLI in some sections.
Recommendations
- Add Bash or cross-platform shell examples for ARM template deployment and feature registration, using 'az' CLI where possible.
- Include Linux VM image examples in PowerShell sections, or clarify that PowerShell can be used on Linux/macOS (with Azure PowerShell Core).
- Provide parity in example ordering: show CLI and PowerShell examples side-by-side or alternate which comes first.
- Clarify that PowerShell commands can be run on Linux/macOS if using Azure PowerShell Core, or link to instructions for installing Azure PowerShell on non-Windows platforms.
Virtual Machines
Ultra Disks for VMs - Azure Managed Disks
...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is intended for both Linux and Windows VMs, but consistently uses Windows-specific VM images (e.g., Win2016Datacenter) in all CLI and PowerShell examples, and does not provide equivalent Linux image examples. The Quickstart link in the portal section references creating a Windows VM, and Linux VM creation is not mentioned. This creates friction for Linux users, as they must adapt the examples themselves.
Recommendations
- Provide Linux VM image examples (e.g., UbuntuLTS) alongside Windows examples in all CLI and PowerShell code blocks.
- Add a Quickstart link for creating a Linux VM in the portal section, or mention both Windows and Linux options.
- Explicitly state that the steps apply to both Linux and Windows VMs, and show how to select a Linux image where relevant.
- Where variables are set (e.g., $image), show both Windows and Linux values, or explain how to choose the appropriate image.
Virtual Machines
Restrict managed disks from being imported or exported
...tual-machines/disks-restrict-import-export-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation references both Azure CLI and Azure PowerShell for configuring disk restrictions, but PowerShell is mentioned first and is linked in the custom RBAC role section. The custom RBAC role creation link directs to a PowerShell-specific page, while Linux/CLI alternatives are not mentioned or linked. The CLI is referenced later for private links and network access policy, but PowerShell is given prominence.
Recommendations
- Provide links and examples for creating custom RBAC roles using Azure CLI or ARM templates, not just PowerShell.
- Ensure that CLI and PowerShell options are presented together or in parallel, rather than PowerShell first.
- Add explicit Linux/macOS instructions or links where only Windows/PowerShell options are given.
- Review the order of tool mentions to avoid Windows-first bias.
Virtual Machines
HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs
...main/articles/virtual-machines/hbv3-series-overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Recommended Windows
Missing Linux Example
Summary
The documentation covers both Linux and Windows VMs, but there are subtle biases: Windows is listed first in the 'Recommended OS for Performance' row, and only Windows is specifically recommended for performance. The only explicit OS recommendation is 'Windows Server 2019+'; no Linux distribution is recommended for best performance, despite Linux being widely used for HPC. Additionally, the 'lstopo' example is Linux-specific, but there are no equivalent Windows/PowerShell commands or guidance for viewing NUMA topology on Windows, which may leave Windows users at a disadvantage.
Recommendations
- Provide explicit Linux OS recommendations for best performance (e.g., RHEL 8.x, Ubuntu 20.04+), not just Windows.
- When listing 'Recommended OS for Performance', include both Linux and Windows options if both are supported.
- Add Windows/PowerShell equivalents for topology inspection (e.g., using 'Get-WmiObject', 'systeminfo', or third-party tools) alongside the 'lstopo' example.
- Where possible, alternate the order of OS mentions or clarify that both Linux and Windows are equally supported unless there is a technical reason to prefer one.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation provides extensive Azure PowerShell examples and scripts for enabling Write Accelerator, with detailed step-by-step instructions. The REST API section recommends installing 'armclient' via Chocolatey, a Windows-only package manager, and provides installation commands for cmd.exe and PowerShell. While Azure CLI and portal instructions are included, PowerShell is presented first and in greater detail. There are no Linux-specific shell examples or guidance for Linux-native package managers or tools, especially for REST API usage.
Recommendations
- Provide Bash or shell script examples for Linux users alongside PowerShell scripts.
- For REST API usage, recommend cross-platform tools (e.g., curl, httpie, az CLI) instead of or in addition to 'armclient', and explain how to use them on Linux/macOS.
- Clarify that Chocolatey and armclient installation steps are Windows-specific, and offer alternatives for Linux/macOS users.
- Balance the order and depth of PowerShell and CLI examples, ensuring CLI instructions are as detailed as PowerShell.
- Add explicit Linux/macOS guidance where relevant, especially for scripting and automation.
Virtual Machines
Create an encrypted image version with customer-managed keys
.../articles/virtual-machines/image-version-encryption.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page provides both PowerShell and Azure CLI examples, but PowerShell (a Windows-centric tool) is presented first and in greater detail. References to enabling customer-managed keys and double encryption in the prerequisites link to PowerShell guides before CLI or cross-platform alternatives. There are also references to Windows-specific cryptography documentation. While Azure CLI examples are present and sufficient for Linux/macOS users, the overall structure and example ordering show a Windows-first and PowerShell-heavy bias.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
- Ensure all prerequisite links include Azure CLI or REST API options where possible, not just PowerShell and Portal.
- Where Windows-specific cryptography documentation is referenced, also provide links to platform-agnostic or Linux-relevant Azure encryption documentation.
- Explicitly state that all steps can be performed from Linux/macOS using Azure CLI, and highlight any differences if they exist.
Virtual Machines
Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment.
.../includes/virtual-machines-disks-shared-limitations.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation repeatedly references Windows Server Failover Cluster and links exclusively to Windows-specific clustering requirements. There are no mentions of Linux clustering solutions (such as Pacemaker or Corosync), nor are Linux-specific limitations or guidance provided. Windows clustering is the only OS-level scenario discussed, and Windows links are given before any Linux equivalents (which are missing).
Recommendations
- Add information about Linux clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
- Include links to Linux documentation for clustering and shared disk support.
- Explicitly state whether shared disks are supported or unsupported for Linux-based clusters, and provide guidance for Linux users.
- If Windows Failover Cluster is the only supported scenario, clarify this explicitly to avoid confusion.
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, while focused on Ubuntu Linux, repeatedly references Windows-centric tools and workflows (notably Hyper-V and PowerShell's Convert-VHD) as the primary or sole method for creating and converting VHDs. Hyper-V instructions and UI steps are given, but equivalent Linux-native approaches (such as using qemu-img or KVM) are not provided. PowerShell's Convert-VHD is mentioned without Linux alternatives. Windows tools and steps are presented first and more prominently, creating friction for Linux users.
Recommendations
- Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, KVM, VirtualBox).
- Provide step-by-step examples for extracting and manipulating VHDs on Linux, not just Windows/WSL.
- Include Linux-specific guidance for deprovisioning and shutting down the VM, rather than referencing Hyper-V UI actions.
- Mention Linux alternatives alongside Windows tools, not after or instead of them.
- Clarify that Hyper-V and Convert-VHD are Windows-specific, and offer parity for Linux/macOS users.
Virtual Machines
Upload a VHD to Azure or copy a disk across regions - Azure CLI
...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a Windows-style AzCopy example ('AzCopy.exe copy "c:\somewhere\mydisk.vhd" "sas-URI" --blob-type PageBlob') but does not include a Linux/macOS equivalent. The AzCopy command is shown only in Windows syntax, and the explicit example uses Windows file paths and executable names. While the rest of the CLI commands are cross-platform, the critical upload step is Windows-centric. There is no mention of how to run AzCopy on Linux/macOS, nor are Linux file path examples provided.
Recommendations
- Add a Linux/macOS AzCopy example, such as 'azcopy copy "/home/user/mydisk.vhd" "sas-URI" --blob-type PageBlob'.
- Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
- Mention that the AzCopy executable may be 'azcopy' on Linux/macOS, not 'AzCopy.exe'.
- Provide both Windows and Linux/macOS file path examples for clarity.
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
Summary
The documentation is focused on Linux VMs, but exhibits Windows bias in several areas: PowerShell examples and tooling (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand) are given equal or greater prominence than Azure CLI, despite PowerShell being a Windows-centric tool for most users. Windows-specific terminology and tools (e.g., PowerShell script references, Windows VM mentions, SAS token generation via PowerShell) are used throughout, sometimes before or instead of Linux-native alternatives. REST API and ARM template examples use Windows-style scripts (Write-Host, .ps1) and do not consistently show Linux shell script equivalents. Some notes and examples reference Windows behaviors or requirements (e.g., 'Secondary Logon' service), even in Linux-focused sections.
Recommendations
- Prioritize Azure CLI and Bash examples for Linux scenarios, placing them before PowerShell in the documentation.
- Ensure REST API and ARM template examples use Linux shell scripts (e.g., 'echo Hello World!' or .sh files) rather than Windows PowerShell scripts (.ps1).
- Clarify when PowerShell examples are for cross-platform PowerShell Core, and provide Bash alternatives where possible.
- Remove or clearly separate Windows-specific notes (e.g., 'Secondary Logon' service) from Linux instructions.
- Add guidance for generating SAS tokens and managing blobs using Azure CLI or Bash, not just PowerShell.
- Where commandId examples are given, ensure Linux-relevant commands are shown (e.g., 'ifconfig', 'RunShellScript') and Windows commands are omitted or clearly marked as Windows-only.