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 76-100 of 815 flagged pages
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 examples use a Windows VM image (Win2016Datacenter) and Windows-style admin credentials. There are no explicit Linux VM deployment examples, and the PowerShell examples are inherently Windows-centric. This may cause confusion or extra work for Linux users, who must adapt the instructions to deploy Linux VMs.
Recommendations
- Add explicit Linux VM deployment examples in the Azure CLI sections, using a popular Linux image (e.g., UbuntuLTS) and Linux-style admin credential setup.
- Clarify in each CLI example that the VM image and authentication method can be changed for Linux VMs, and provide sample variable values for Linux scenarios.
- Consider adding a short section or note explaining how to adapt the instructions for Linux VMs, including differences in admin username, password/SSH key authentication, and image selection.
- Ensure that the 'Next steps' links to Linux-specific guides are more prominent or referenced earlier in the workflow.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides extensive Azure PowerShell examples and scripts, which are strongly associated with Windows environments. The REST API section recommends installing 'armclient' via Chocolatey, a Windows-only package manager, and provides installation instructions using cmd.exe and PowerShell. While Azure CLI examples are included, the PowerShell section is much more detailed and appears first. There are no explicit Linux shell (bash) examples or instructions for Linux-native package managers or tools. However, the feature itself is cross-platform and the documentation does mention Linux VMs and Linux disk managers (LVM, MDADM).
Recommendations
- Add bash shell examples for Azure CLI usage, showing how to enable Write Accelerator from a Linux/macOS terminal.
- Provide instructions for installing 'armclient' or equivalent REST API tooling on Linux/macOS, such as via pip, npm, or manual download, instead of only Chocolatey.
- Reorder sections so Azure CLI examples appear before PowerShell, or provide parity in detail between PowerShell and CLI.
- Explicitly mention that all PowerShell commands can be run on Linux/macOS via Azure PowerShell (if true), or clarify any OS limitations.
- Include troubleshooting or configuration notes specific to Linux environments, such as SELinux, udev, or disk naming conventions.
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 to Windows-specific clustering requirements. There are no equivalent mentions or links for Linux clustering solutions (such as Pacemaker, Corosync, or other Linux HA tools). The proximity placement groups section links to a Windows-specific URL, even though PPGs are not exclusive to Windows. The clustering limitations are always described in terms of Windows tools, with no Linux parity or examples.
Recommendations
- Add information about Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
- Provide links to Linux clustering documentation or Azure guidance for Linux HA scenarios.
- Clarify if limitations apply to both Windows and Linux, or only Windows, and add Linux-specific notes where relevant.
- Update proximity placement group links to reference a cross-platform or generic Azure documentation page, not a Windows-specific one.
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 the Convert-VHD PowerShell cmdlet) as the primary or sole method for creating and converting VHDs. Linux-native alternatives for VHD creation and conversion are not provided, and Hyper-V/PowerShell steps are described before or instead of Linux equivalents. This creates friction for Linux users who may not have access to Windows tools.
Recommendations
- Provide Linux-native instructions for creating and converting VHDs (e.g., using qemu-img or VBoxManage).
- List Linux and Windows tools side-by-side, or present Linux-first examples given the Ubuntu/Linux focus.
- Clarify that Hyper-V/PowerShell are optional and not required if using Linux-native tooling.
- Link to or include instructions for extracting and manipulating VHDs on Linux systems.
- Explicitly mention cross-platform alternatives wherever a Windows-only tool is referenced.
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, and does not provide equivalent Linux image examples or instructions. This creates friction for Linux users, who must infer the correct Linux image and adapt the commands themselves. Additionally, references to Windows quickstart documentation are given first, and Linux-specific guidance is missing.
Recommendations
- Provide Linux VM image examples (e.g., UbuntuLTS, CentOS) alongside Windows examples in all CLI and PowerShell code snippets.
- Add links to Linux VM quickstart documentation where Windows quickstart links are provided.
- Explicitly state that the instructions apply to both Linux and Windows, and clarify any OS-specific steps if needed.
- Where variables are set for VM image, recommend both Windows and Linux values.
- Ensure screenshots and portal instructions mention Linux VM deployment as well.
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
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 disks, but consistently uses Windows-centric values (e.g., 'Win2016Datacenter' as the VM image) in all CLI and PowerShell scripts. PowerShell (a Windows-first tool) is given equal prominence to Azure CLI, and there are no explicit Linux-specific examples or guidance for deploying Linux VMs or using Linux admin credentials. The documentation does not show how to use Linux images, nor does it clarify how Linux users should adapt the examples. This creates friction for Linux/macOS users, who may be unfamiliar with Windows defaults or PowerShell.
Recommendations
- Add explicit Linux VM deployment examples in the Azure CLI sections (e.g., use 'UbuntuLTS' or another Linux image for the --image parameter, and show SSH key authentication).
- Clarify in the variable initialization sections how to set up admin credentials for Linux VMs (e.g., using --authentication-type ssh and --ssh-key-values).
- Where PowerShell is presented, consider also referencing Bash scripting for parity, or clarify that PowerShell is primarily for Windows users.
- In the 'Next steps' section, ensure Linux links/examples are as prominent as Windows ones.
- Consider reordering examples to show Azure CLI (cross-platform) before PowerShell, and ensure Linux VM deployment is not an afterthought.
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 examples for Azure Portal, Azure CLI, Azure PowerShell, and Resource Manager templates. While Azure CLI examples use Linux-friendly commands and Ubuntu images, PowerShell is heavily featured, and Resource Manager template examples are shown exclusively with PowerShell commands. Windows-specific tools (PowerShell) and Windows VM images are used in PowerShell and ARM template sections, and Windows is prioritized in some example flows. There are no Linux-specific ARM template or bash examples, and PowerShell is used for feature registration and deployment, potentially creating friction for Linux/macOS users.
Recommendations
- Add bash or shell script equivalents for ARM template deployment and feature registration, using Azure CLI.
- Provide ARM template deployment examples using Azure CLI (az deployment group create) instead of only PowerShell.
- Ensure that Linux VM images are used in at least some PowerShell and ARM template examples, or clarify that Windows images are optional.
- Where PowerShell is used for feature registration, add Azure CLI equivalents.
- In sections where Windows tools are mentioned first, alternate the order or clarify cross-platform options.
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 provides links and examples for both Azure PowerShell and Azure CLI, but the custom RBAC role section links only to a PowerShell-based guide. Additionally, PowerShell is mentioned before CLI in the NetworkAccessPolicy configuration section, and the custom role link uses '/custom-roles-powershell', suggesting a Windows-first approach. Linux users may need to search for CLI or ARM template equivalents.
Recommendations
- Add links to custom RBAC role creation using Azure CLI and/or ARM templates, not just PowerShell.
- Ensure CLI and PowerShell examples are presented together or with CLI first, as CLI is cross-platform.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI.
- Where possible, provide direct CLI commands or scripts for key actions.
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 referenced for installing armclient, with no mention of Linux/macOS alternatives. PowerShell instructions are presented before Azure CLI, and the REST API section assumes Windows environments for installation. While the feature is cross-platform and Linux is referenced in planning and REST API examples, Linux/macOS users may encounter friction due to missing parity in scripting and tool installation guidance.
Recommendations
- Provide Bash or shell script examples for Azure CLI usage, especially for Linux/macOS users.
- Include instructions for installing armclient on Linux/macOS (e.g., via npm, direct download, or other package managers).
- Mention cross-platform alternatives to Chocolatey for package installation.
- Present Azure CLI examples before or alongside PowerShell examples to emphasize platform neutrality.
- Clarify that all PowerShell/Chocolatey steps are Windows-specific and offer Linux/macOS equivalents where possible.
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 is generally cross-platform and includes both Linux and Windows support. However, there is a notable bias in the 'Recommended OS for Performance' row, which lists only Windows Server 2019+ and does not mention any Linux distributions. Additionally, in the software specifications, Windows is sometimes mentioned first, and there is no explicit Linux example or recommendation for optimal performance, despite Linux being widely used in HPC. The lstopo example is Linux-specific, but there are no equivalent Windows tools or guidance for topology inspection on Windows.
Recommendations
- Add recommended Linux distributions for performance (e.g., RHEL, Ubuntu, SLES) alongside Windows Server 2019+ in the 'Recommended OS for Performance' row.
- Where possible, provide parity in examples or guidance for both Linux and Windows users (e.g., suggest a Windows tool for inspecting NUMA topology, or clarify if such inspection is not relevant on Windows).
- List Linux and Windows support in a consistent order or clarify that both are equally supported.
- If Windows is recommended for specific workloads, explain why, and provide Linux tuning guidance for parity.
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-centric tools and workflows (notably Hyper-V and PowerShell's Convert-VHD) as the primary or sole example for creating and converting VHDs. Linux-native alternatives for creating and converting VHDs are not provided, and instructions for Linux users are minimal or absent in these areas. This creates friction for Linux/macOS users who may not have access to Hyper-V or PowerShell.
Recommendations
- Provide Linux-native instructions for creating and converting VHD files, such as using qemu-img or VBoxManage.
- Mention Linux virtualization solutions (e.g., KVM, VirtualBox, QEMU) alongside Hyper-V, and link to relevant guides.
- Include example commands for extracting and converting VHDs on Linux/macOS, not just Windows.
- Reorder sections or add parallel instructions so that Linux-native workflows are presented before or alongside Windows/Hyper-V ones.
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 offer a Linux/macOS equivalent. The AzCopy command is shown only in Windows syntax, and the file path example is Windows-specific. While the rest of the CLI commands are cross-platform, the upload step is Windows-centric, potentially creating friction for Linux/macOS users.
Recommendations
- Add a Linux/macOS AzCopy example, e.g., '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 file paths and command syntax differ between Windows and Linux/macOS.
- Consider showing both Windows and Linux/macOS AzCopy examples side by side.
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 to Windows-specific clustering requirements. There is no mention of Linux clustering solutions (such as Pacemaker, Corosync, or other Linux HA tools), nor are Linux-specific limitations or guidance provided. Windows clustering is discussed as a primary use case for shared disks, suggesting a Windows-centric perspective.
Recommendations
- Add information about Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
- Include links to Linux HA documentation and clarify if shared disks are supported for Linux clusters, and under what conditions.
- Explicitly state if certain limitations only apply to Windows clusters, and provide equivalent Linux guidance where possible.
- Balance references to Windows Failover Cluster with Linux alternatives, or clarify if shared disks are not intended for Linux clustering scenarios.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs, but PowerShell examples are presented first and in greater detail. This may create friction for Linux users, as PowerShell is not the default or most common scripting environment on Linux. The Azure CLI examples are present and comprehensive, but the ordering and emphasis suggest a Windows/PowerShell bias.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is more native to Linux environments.
- Clearly indicate that PowerShell examples are optional and primarily for users who have PowerShell Core installed on Linux, or for cross-platform administrators.
- Add brief notes about the availability and installation of PowerShell on Linux, if PowerShell examples are retained.
- Ensure that all PowerShell commands are matched with equivalent Azure CLI commands, and vice versa.
- Consider grouping examples by platform (e.g., 'Azure CLI (Linux/macOS)', 'PowerShell (Windows/Linux)') rather than by tool.
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 examples for Azure Image Builder, but there are several areas where Windows tools and patterns are emphasized or presented first. PowerShell is frequently referenced for checksum generation and image build operations, sometimes without equal prominence for Linux equivalents. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux customizers (Shell) are covered but with less depth. Windows tools (Get-FileHash, PowerShell commands) are often mentioned before Linux tools (sha256sum, bash), and some example sections (e.g., validation) show Windows examples first.
Recommendations
- Ensure Linux commands (e.g., sha256sum) are always mentioned alongside Windows commands (e.g., Get-FileHash), and vice versa.
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Provide equal detail and troubleshooting guidance for Linux customizers and validators as is given for Windows.
- Where PowerShell is referenced for operations (e.g., build, cancel), highlight Azure CLI as the primary cross-platform tool, and clarify that PowerShell is optional.
- Add explicit Linux troubleshooting sections or links, similar to Windows-focused troubleshooting.
- Where Windows customizers (WindowsRestart, WindowsUpdate) are described, clarify Linux alternatives or limitations.
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 primarily focused on Linux VMs, but several sections introduce Windows-centric tools and patterns. PowerShell examples are given equal prominence to Azure CLI, and Windows-specific terminology (such as PowerShell cmdlets, SAS token generation via PowerShell, and references to Windows VM behaviors) appear throughout. REST API and ARM template examples use PowerShell script syntax (Write-Host, .ps1) even in Linux contexts, and some notes reference Windows VM-specific requirements. The PowerShell section is extensive, and PowerShell is presented as a main management tool for Linux VMs, which may not align with typical Linux admin workflows.
Recommendations
- Where REST API and ARM template examples are given, use Linux shell script syntax (e.g., bash, sh) instead of PowerShell (e.g., Write-Host, .ps1) for Linux VM scenarios.
- Clarify when PowerShell examples are for Windows VMs only, and provide bash or shell script equivalents for Linux VMs.
- Move Azure CLI examples before PowerShell examples, as CLI is more native to Linux workflows.
- When referencing SAS token generation, provide az CLI equivalents (e.g., az storage blob generate-sas) alongside PowerShell commands.
- Remove or clearly separate Windows-specific notes (such as 'Secondary Logon' service) from Linux instructions.
- Expand troubleshooting and scripting examples to show Linux-native commands and patterns (e.g., using bash, sh, or Python).
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 and for feature registration. Windows/PowerShell commands are shown before or alongside CLI, and some feature registration steps are only shown with PowerShell. Additionally, Resource Manager template deployment examples use PowerShell syntax, which is not cross-platform. There are no explicit Linux/macOS-specific instructions or parity for feature registration or template deployment.
Recommendations
- Add Bash/Linux/macOS equivalents for feature registration (e.g., using Azure CLI instead of PowerShell).
- Provide cross-platform instructions for deploying Resource Manager templates (e.g., using Azure CLI's 'az deployment group create' command).
- Ensure that any PowerShell-only steps are accompanied by CLI alternatives.
- Clarify that PowerShell steps can be run in Azure Cloud Shell (which supports Bash and PowerShell) to reduce friction for non-Windows 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') and does not offer an equivalent Linux/macOS command. The AzCopy invocation uses Windows paths and executable naming, and the Linux/macOS usage (with azcopy or ./azcopy and UNIX-style paths) is missing. While the rest of the CLI examples are cross-platform, the critical upload step is Windows-centric, potentially creating friction for Linux/macOS users.
Recommendations
- Add a Linux/macOS AzCopy example, e.g., './azcopy copy "/home/user/mydisk.vhd" "sas-URI" --blob-type PageBlob'.
- Mention that AzCopy is available for Linux/macOS and provide download/install links for those platforms.
- Clarify path conventions and executable naming for different OSes (AzCopy.exe vs azcopy or ./azcopy).
- Consider showing both Windows and Linux/macOS examples side-by-side for key steps.
Virtual Machines
Benchmark your application on Azure Disk Storage
...lob/main/articles/virtual-machines/disks-benchmarks.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page introduces benchmarking tools for both Windows (DiskSpd) and Linux (FIO), but Windows tools and patterns are mentioned first and more prominently. The examples and setup instructions reference Windows terminology (e.g., host caching, volume names) without providing equivalent Linux commands or examples. There is no explicit Linux example or guidance, creating friction for Linux users.
Recommendations
- Provide explicit Linux examples alongside Windows examples, including FIO command lines and Linux-specific setup instructions.
- Ensure Linux tools (FIO) are mentioned equally and not after Windows tools.
- Clarify any differences in disk configuration steps for Linux VMs (e.g., how to stripe disks and configure caching in Linux).
- Add sample scripts or command lines for Linux users to replicate the benchmarking process.
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 provides both Azure CLI and PowerShell examples for deploying and managing Ultra Disks, but consistently uses Windows VM images (e.g., Win2016Datacenter) in all CLI and PowerShell code samples. There are no Linux VM image examples or explicit instructions for Linux VMs, despite the article stating applicability to both Linux and Windows VMs. Additionally, the 'Quickstart' link in the portal section references creating a Windows VM, and Windows terminology is used by default in several places.
Recommendations
- Add Linux VM image examples (e.g., UbuntuLTS) alongside Windows examples in all CLI and PowerShell code blocks.
- Explicitly mention that the steps are identical for Linux VMs, or highlight any differences (such as disk partitioning/formatting commands) for Linux.
- Provide a 'Quickstart: Create a Linux virtual machine in the Azure portal' link alongside the Windows quickstart.
- Ensure variable names and instructions are OS-neutral (e.g., avoid using only Windows usernames/passwords).
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 templates) are presented first and in greater detail. Windows-specific clustering patterns and terminology (WSFC, CSV) are described before Linux equivalents, and Windows workloads are listed before Linux workloads. Linux examples are present but less detailed, and Linux-specific utilities (sg_persist, fence_scsi) are mentioned only briefly. The performance throttling examples also start with Windows scenarios before Linux.
Recommendations
- Present Linux and Windows examples in parallel or alternate order, rather than always Windows first.
- Expand Linux workload examples to match the detail and variety of Windows workloads.
- Provide more detailed Linux-specific guidance, including step-by-step examples for Pacemaker, Corosync, and clustered filesystems.
- Include Linux-specific templates or links, similar to the Windows SoFS and SAP templates.
- Ensure Linux tools/utilities (sg_persist, fence_scsi) are described with usage examples, not just mentioned.
- Balance performance throttling examples so Linux scenarios are as prominent as Windows scenarios.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides extensive Azure PowerShell examples and scripts, which are primarily Windows-centric. The REST API section recommends installing 'armclient' via Chocolatey, a Windows-only package manager, and gives installation instructions using cmd.exe and PowerShell. While Azure CLI examples are included (which are cross-platform), PowerShell is presented first and in greater detail. There are no explicit Linux shell (bash) or macOS-specific instructions for REST API tooling, and the reliance on Chocolatey for 'armclient' excludes Linux/macOS users from easy installation.
Recommendations
- Add bash/Linux/macOS installation instructions for 'armclient' or recommend cross-platform alternatives (such as using curl or az CLI for REST calls).
- Provide parity in scripting examples for Linux users, such as using bash scripts or az CLI for all scenarios shown in PowerShell.
- Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
- Clarify that 'armclient' can be installed via .NET Core or provide a Docker image for Linux/macOS users if Chocolatey is not available.
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 to Windows-specific clustering requirements as a limitation for shared disks across all disk types. There is no mention of Linux clustering solutions (such as Pacemaker or Corosync), nor any guidance or limitations for Linux-based shared disk scenarios. Additionally, proximity placement group documentation is linked to a Windows-specific page, even though PPGs are not exclusive to Windows VMs.
Recommendations
- Add information about shared disk limitations and supported clustering solutions for Linux (e.g., Pacemaker, Corosync, or other Linux HA stacks).
- Include links to Linux clustering documentation and clarify whether shared disks are supported with Linux-based clusters.
- Update proximity placement group links to reference both Windows and Linux VM documentation, or use a generic PPG page.
- Explicitly state if certain limitations only apply to Windows Server Failover Cluster, and provide Linux equivalents or note their absence.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs. However, PowerShell examples are presented first and in greater detail, with multiple code blocks and screenshots, while Azure CLI examples (more natural for Linux users) are shown after. There is no explicit mention of Linux-native tools for interacting with Azure resources (e.g., Python SDK, REST API), and the PowerShell section may create friction for Linux users unfamiliar with PowerShell on Linux.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is more commonly used on Linux.
- Add a brief note clarifying that PowerShell commands can be run on Linux, but Azure CLI is the default for Linux environments.
- Expand Azure CLI examples to match the detail and coverage of the PowerShell section.
- Consider including REST API or Python SDK examples for advanced Linux users.
- Explicitly mention that all PowerShell commands can be run on Linux, but CLI is recommended for Linux users.
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 parity for both Linux and Windows VM image creation with Azure Image Builder, including Bicep and ARM template examples. However, there are several areas where Windows-specific tools (PowerShell, WindowsRestart, WindowsUpdate customizers) and instructions are emphasized, sometimes before Linux equivalents. SHA256 checksum generation is shown with PowerShell first, and Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux customizers (Shell) are less prominent. Some sections (e.g., restart customizer) note the absence of Linux equivalents. PowerShell commands and tools are referenced more frequently, and sometimes before Linux/CLI alternatives.
Recommendations
- Ensure Linux and macOS examples (e.g., shell commands, checksum generation) are shown alongside or before Windows/PowerShell examples.
- Provide more detailed Linux customizer examples, including advanced shell scripting and error handling.
- Where Windows-only customizers exist (e.g., WindowsRestart), clarify Linux alternatives or explicitly state limitations.
- Balance the order of examples so Linux and Windows are treated equally, or alternate which is shown first.
- Reference Linux tools (e.g., sha256sum, wget, curl) equally with Windows tools (PowerShell, Invoke-WebRequest).