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 501-525 of 815 flagged pages
Virtual Machines
Create a Gallery for Sharing Resources
.../blob/main/articles/virtual-machines/create-gallery.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides examples for creating an Azure Compute Gallery using Portal, Azure CLI, PowerShell, and REST API. The PowerShell example is presented as a dedicated tab alongside CLI and REST, and is not Windows-specific in its content. However, PowerShell is a Windows-centric tool, and its inclusion as a primary example (with its own tab) may signal a mild Windows bias. The CLI examples use Azure CLI, which is cross-platform, and REST API examples are platform-agnostic. The ordering of examples (Portal, CLI, PowerShell, REST) places PowerShell before REST, but after CLI, which is acceptable. No Windows-only tools or patterns are mentioned, and Linux parity is generally maintained.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider adding a note that PowerShell examples are primarily for Windows users, and that Azure CLI is recommended for Linux/macOS.
- Ensure that CLI examples are always present and up-to-date.
- If possible, provide Bash shell scripting examples for Linux users (though Azure CLI is sufficient).
Create Pull Request
Virtual Machines
Secure Azure Managed Disk Downloads and Uploads
...icles/virtual-machines/disks-secure-upload-download.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for key operations, but PowerShell is often presented before CLI. Portal, PowerShell, and CLI are all covered, but PowerShell (a Windows-centric tool) is given prominence in several sections. However, Linux parity is generally maintained, and CLI examples are present. The 'Next steps' section lists both Linux and Windows guides, with Linux listed first.
Recommendations
- Where possible, alternate the order of PowerShell and CLI examples to avoid implicit prioritization of Windows tools.
- Explicitly note that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Add brief notes or links for Bash scripting or Linux-native tools if relevant.
- Ensure screenshots and portal instructions are not Windows-specific (they appear generic here).
Virtual Machines
Enable shared disks for Azure Managed Disks
.../main/articles/virtual-machines/disks-shared-enable.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all disk types, but PowerShell examples are consistently present and often shown alongside or immediately after CLI examples. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. However, Azure CLI examples are always present and are cross-platform. There are no Windows-only tools or missing Linux examples, but PowerShell usage is emphasized and sometimes appears before CLI in section ordering.
Recommendations
- Consider listing Azure CLI examples before PowerShell in each section, as CLI is cross-platform and more familiar to Linux/macOS users.
- Explicitly note that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows (with some support on Linux/macOS).
- Where possible, add bash shell scripting examples for disk operations, especially in sections where PowerShell scripting is shown.
- Clarify that all disk operations shown via CLI are fully supported on Linux and macOS.
- Review section ordering to ensure CLI is not secondary to PowerShell, reducing perceived Windows bias.
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is focused on Linux VM extensions, but consistently presents Azure PowerShell examples alongside Azure CLI, and often lists PowerShell examples immediately after CLI. While both CLI and PowerShell are cross-platform, PowerShell is more commonly associated with Windows. The documentation does not provide Linux-native command-line examples (such as Bash scripting or direct REST API usage), and sometimes references PowerShell before CLI in explanations. However, all examples are functional for Linux users and do not require Windows-specific tools.
Recommendations
- Consider emphasizing Azure CLI as the primary example, since it is more commonly used on Linux and macOS.
- Where PowerShell is shown, clarify that Azure PowerShell is cross-platform, and provide links to installation instructions for Linux/macOS.
- Add Bash or shell script examples for common extension management tasks, especially where Azure CLI is used.
- Ensure that CLI examples are always listed before PowerShell, or group them together with clear labeling.
- Explicitly note that all shown tools (CLI, PowerShell) are available on Linux/macOS, to avoid confusion.
Virtual Machines
NVIDIA GPU Driver Extension - Azure Linux VMs
...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is focused on Azure Linux VMs and the NVIDIA GPU Driver Extension for Linux, with nearly all examples and instructions tailored for Linux environments. However, PowerShell examples are provided alongside Azure CLI and ARM template examples, and PowerShell is presented before Azure CLI in the deployment section. There is a brief mention of a Windows extension, but it is clearly separated and not the focus. No Windows-specific tools or patterns are prioritized, and Linux commands and troubleshooting steps are comprehensive. The inclusion of PowerShell is likely for cross-platform Azure management, but its placement before CLI may create minor friction for Linux users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more native to Linux environments.
- Clarify that PowerShell examples are for users managing Azure from non-Linux platforms, and highlight CLI as the primary method for Linux users.
- Consider adding Bash script examples for common tasks, as Bash is the default shell for most Linux distributions.
- Ensure screenshots and instructions in the Azure portal section are explicitly labeled as Linux-specific where relevant.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is focused on Linux, as indicated by the title and content. However, in several sections, Windows-oriented tools and patterns (specifically Azure PowerShell) are presented before their Linux-native equivalents (Azure CLI). PowerShell deployment instructions and troubleshooting commands are shown first, which may create friction for Linux users who typically use Azure CLI or shell scripting. There are also warnings about PowerShell-specific issues, but no equivalent Linux-specific troubleshooting advice. All actual extension configuration, certificate paths, and operational details are Linux-centric.
Recommendations
- Present Azure CLI examples before Azure PowerShell examples, as CLI is cross-platform and native to Linux.
- Add Linux-specific troubleshooting tips (e.g., using journalctl, systemd, or bash scripting) alongside PowerShell troubleshooting.
- Clarify that PowerShell is optional and not required for Linux deployments.
- Consider grouping CLI and PowerShell instructions under clearly labeled sections for each platform.
- Ensure that all example commands use Linux shell syntax (e.g., $VAR, --options) where appropriate.
Virtual Machines
Deprovision or generalize a VM before creating an image
...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows instructions for deprovisioning/generalizing VMs before imaging. However, the Windows section presents Windows-specific tools and PowerShell examples first in the 'Generalize a Windows VM' step, and the Windows prerequisites are more detailed. The Linux section is clear and includes links to distro-specific guides, but Windows examples (such as Set-AzVm) are shown in PowerShell, while Linux uses Azure CLI. The order of sections is Linux first, but Windows tools are emphasized in their section.
Recommendations
- Ensure parity in detail between Linux and Windows prerequisites and steps.
- Provide Azure CLI equivalents for Windows VM generalization (if available), not just PowerShell.
- Consider adding a summary table comparing Linux and Windows steps/tools for clarity.
- Balance the depth of instructions for both OS types, especially regarding prerequisites and troubleshooting.
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows guidance, but in several places Windows/PowerShell examples are presented before Linux/CLI equivalents. PowerShell examples are detailed and prominent, and Windows terminology (e.g., Sysprep) is mentioned before Linux-specific steps. However, Linux is well-represented overall, and CLI examples are provided for both OS types.
Recommendations
- Alternate the order of CLI and PowerShell examples, or present CLI (cross-platform) examples first.
- Ensure Linux-specific terminology and examples are given equal prominence and detail as Windows/PowerShell.
- Consider adding explicit Linux PowerShell (pwsh) examples if relevant, or clarify that PowerShell examples are Windows-centric.
- Where possible, clarify that CLI commands work on Linux/macOS as well as Windows.
- Review for subtle language that assumes Windows as the default (e.g., mentioning Sysprep before waagent -deprovision).
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is focused on Azure Disk Encryption for Linux VMs and provides both Azure CLI and Azure PowerShell examples throughout. However, PowerShell cmdlets and scripts are often mentioned first, and some critical instructions (such as backup requirements and encryption prerequisites) reference PowerShell cmdlets before their CLI equivalents. There is also frequent use of PowerShell-specific terminology and patterns, which may create friction for Linux users who typically prefer CLI or shell scripting. Nevertheless, CLI examples are present for all major operations, and the documentation is not Windows-exclusive.
Recommendations
- Ensure Azure CLI examples are presented before or alongside PowerShell examples, especially in critical sections.
- Clarify that PowerShell can be used cross-platform, but highlight that Azure CLI is the native tool for Linux environments.
- Reduce PowerShell-specific terminology in general Linux-focused documentation, or provide equivalent Bash/shell scripting guidance.
- Add explicit notes or guidance for Linux users on how to use Azure CLI in native shells, not just in PowerShell sessions.
- Where possible, provide Bash script examples for common automation scenarios.
Virtual Machines
Enable Azure Disk Encryption for Linux VMs
...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is focused on Linux VMs and provides Linux-specific instructions and examples. However, it mentions Azure PowerShell and PowerShell scripts alongside Azure CLI, and references PowerShell cmdlets in the terminology section. In the 'Next steps' section, PowerShell resources are listed immediately after CLI resources, rather than prioritizing Linux-native tools. There is minor bias in the inclusion and ordering of Windows-centric tools (PowerShell), but Linux parity is largely maintained.
Recommendations
- Clarify that Azure PowerShell is cross-platform and can be used on Linux/macOS, or prioritize Azure CLI as the primary tool for Linux users.
- In 'Next steps', list Azure CLI resources before PowerShell resources, and explicitly note that PowerShell is optional for Linux users.
- In the terminology section, explain that PowerShell cmdlets are available on Linux and macOS, or remove if not relevant to Linux VM management.
- Where PowerShell is referenced, provide context about its cross-platform support to avoid confusion for Linux users.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Low 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 before Azure CLI examples, and the PowerShell section is more detailed and extensive. This creates a mild Windows bias, as PowerShell is less commonly used on Linux, and Linux users typically prefer Azure CLI or Bash. The OS-level section uses Bash commands, which is appropriate for Linux, but the prominence and depth of PowerShell coverage may create friction for Linux users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is more native to Linux environments.
- Ensure Azure CLI coverage is as detailed as PowerShell, including all scenarios (single pass, dual pass, unattached disks, managed/unmanaged disks).
- Clarify that PowerShell examples are optional for Linux users and highlight Azure CLI as the primary cross-platform tool.
- Consider removing or minimizing PowerShell examples unless there is a strong use case for PowerShell on Linux.
- Add Bash scripting examples for interacting with Azure CLI, especially for common automation scenarios.
Virtual Machines
Create and upload a Red Hat Enterprise Linux VHD for use in Azure
...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation covers multiple hypervisors (Hyper-V, KVM, VMware, Kickstart) for preparing a Red Hat Enterprise Linux VHD for Azure. However, in several sections, Windows/Hyper-V instructions are presented first, and references to Windows tools (such as Hyper-V Manager and PowerShell convert-vhd cmdlet) appear before Linux alternatives. Linux/KVM/VMware instructions are comprehensive and present, but Windows/Hyper-V is prioritized in ordering and introductory notes.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, rather than always after.
- When mentioning disk conversion tools, list Linux tools (qemu-img, guestfish) before or alongside Windows tools (Hyper-V Manager, convert-vhd).
- In introductory notes, avoid phrasing that implies Windows/Hyper-V is the default or primary method; instead, clarify that multiple platforms are equally supported.
- Ensure that all references to disk conversion or VM preparation include both Windows and Linux options in parallel, not sequentially.
- Consider adding a summary table or matrix at the top to help users quickly identify instructions relevant to their platform.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is focused on Linux VM time sync in Azure and provides extensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific content, which may create a perception of Windows-first bias. All technical examples, tools, and instructions are Linux-centric and relevant to the page's purpose.
Recommendations
- Move or minimize Windows Server 2016 discussion to a background or context section, clarifying its relevance to Linux VM time sync.
- Ensure Linux-specific guidance is presented first in the overview and configuration sections.
- Add a brief summary explaining why Windows host time sync is relevant for Linux VMs, to avoid confusion.
- Consider linking to Linux time sync concepts before referencing Windows documentation in the 'Next steps' section.
Virtual Machines
Migrate Standard HDD OS disks by September 08, 2028
...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation covers both Linux and Windows VMs, and provides example commands for both Azure CLI and Azure PowerShell. However, the PowerShell example is listed first, which may indicate a minor 'windows_first' bias. All tools and instructions are cross-platform, and no Windows-specific tools or patterns are mentioned exclusively.
Recommendations
- Present Azure CLI and Azure PowerShell examples in parallel or alternate their order to avoid implicit Windows-first bias.
- Explicitly state that both CLI and PowerShell commands work for Linux and Windows VMs.
- Consider adding sample scripts for both Linux and Windows environments if relevant.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Low 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 more step-by-step breakdowns and screenshots. Azure CLI examples are present and thorough, but PowerShell is given prominence, which may create friction for Linux users who typically use Bash and Azure CLI. There are no missing Linux examples, and the OS-level validation uses standard Linux tools (lsblk, cryptsetup, dmsetup).
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more native to Linux environments.
- Ensure parity in detail and screenshots between Azure CLI and PowerShell sections.
- Explicitly note that PowerShell examples are for cross-platform use, but Azure CLI is recommended for Linux users.
- Consider adding Bash scripting examples for common tasks, where relevant.
- Clarify that PowerShell can be used on Linux, but Azure CLI is the default for Linux administrators.
Virtual Machines
Enable Azure Disk Encryption for Linux VMs
...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is focused on Linux VMs and provides Linux-specific instructions and examples. However, in several places, Azure PowerShell is mentioned alongside Azure CLI, and PowerShell examples/scripts are referenced equally with CLI ones. In the 'Next steps' section, PowerShell is listed after CLI, but both are given parity. The terminology table includes 'PowerShell cmdlets' as a term, even though this is not a Linux-native tool. Overall, there is minor bias in mentioning PowerShell for Linux management, but Linux-native tools and examples are prioritized.
Recommendations
- Clarify that Azure PowerShell can be used cross-platform, but CLI is the native Linux tool.
- Consider removing 'PowerShell cmdlets' from the terminology table unless specifically relevant to Linux users.
- Ensure that CLI examples and scripts are always presented before PowerShell, and that PowerShell is described as optional for Linux users.
- Add a note explaining the cross-platform nature of Azure PowerShell, and recommend CLI as the default for Linux users.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is focused on Linux VM time sync in Azure and provides thorough Linux-specific guidance, commands, and configuration examples. However, the introduction and overview sections discuss Windows Server 2016 and its time sync improvements before describing Linux mechanisms. There are references and links to Windows time service documentation, but all technical instructions, tools, and examples are Linux-centric. The only minor bias is the Windows context being presented first in the background, which could be confusing or distracting for Linux users.
Recommendations
- Move Windows Server 2016 context to a separate 'Background' or 'Azure host infrastructure' section, clarifying its relevance to Linux VM time sync.
- Add a brief statement at the start explaining that Azure hosts run Windows Server, but this page is focused solely on Linux VM configuration.
- Ensure Linux-specific information is presented before or independently of Windows references.
- Consider reducing or relocating Windows documentation links to a 'See also' section if not directly relevant to Linux VM configuration.
Virtual Machines
Overview of Azure Disk Storage
...in/articles/virtual-machines/managed-disks-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Minor Windows Reference
Summary
The documentation provides a generally balanced overview of Azure Managed Disks for both Linux and Windows VMs. However, there are a few instances where Windows terminology, tools, or references are presented first or more prominently, such as in partitioning guidance and some linked articles. Linux equivalents are present but sometimes appear after Windows references or are less detailed.
Recommendations
- When discussing partitioning (MBR/GPT), include Linux partitioning tools and documentation (e.g., 'fdisk', 'parted', or relevant Linux docs) alongside Windows links.
- In sections referencing drive letters (e.g., OS disk as C:, data disk as D:), provide Linux device path equivalents (e.g., /dev/sda, /dev/sdb) with equal prominence.
- For all how-to links (such as uploading VHDs), ensure Linux and Windows options are presented together and with equal visibility.
- Where possible, avoid Windows-centric language (like 'Sysprep') without mentioning the Linux equivalent (such as 'waagent -deprovision+user').
- Review linked articles to ensure Linux parity in depth and clarity.
Virtual Machines
Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents."
...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Linux and Windows coverage, but there is a mild Windows bias in the ordering and tool references. Windows-specific backup tools (like Volume Shadow Service) are mentioned before Linux equivalents (fsfreeze), and Windows examples (SQL Server, Always On Availability Groups) are discussed first in database scenarios. However, Linux is acknowledged and included, and most solutions are platform-agnostic.
Recommendations
- When mentioning backup coordination tools, list Linux options (e.g., fsfreeze) alongside Windows tools (e.g., VSS), and clarify their limitations and use cases.
- In scenario examples, alternate between Windows and Linux workloads or explicitly mention Linux-first scenarios (e.g., PostgreSQL, Cassandra, MongoDB) with relevant backup strategies.
- Provide links to Linux-specific documentation or third-party tools for application-consistent backups.
- Ensure tables and comparison sections highlight Linux and Windows parity, especially for features like application/file system consistency.
- Consider adding a brief section summarizing Linux-specific considerations for backup and disaster recovery.
Virtual Machines
Support matrix for VM restore points
...n/articles/virtual-machines/concepts-restore-points.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows operating system support before Linux in the 'Operating system support for application consistency' section. However, both Windows and Linux are covered with parity, and no Windows-specific tools or examples are prioritized elsewhere. The 'Next steps' section lists CLI, Portal, and PowerShell equally, without bias.
Recommendations
- Consider listing Linux operating system support before Windows, or presenting both together in a single table or section to avoid implicit prioritization.
- Ensure future updates provide equal detail for both Windows and Linux, especially in example-driven sections.
Virtual Machines
Best practices for virtual machine cost optimization
...s/virtual-machines/cost-optimization-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and neutral, but there is a minor bias in the VM recommendations section, where Windows machines are mentioned first and given specific guidance (e.g., 'Use at least B2 for Windows machines') without equivalent Linux-specific advice. All other recommendations and links are inclusive of both Windows and Linux, and Windows-only features are appropriately flagged.
Recommendations
- Provide equivalent Linux-specific guidance where Windows-specific advice is given (e.g., recommend minimum B-Series sizes for Linux VMs if applicable).
- Ensure examples and recommendations are balanced, mentioning Linux and Windows equally and in parallel.
- Where possible, add Linux-specific cost optimization tips (e.g., OS-level shutdown automation, licensing considerations).
Virtual Machines
Server-side encryption of Azure Managed Disks
...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers server-side encryption for Azure Managed Disks and is intended for both Linux and Windows VMs. However, there is a recurring pattern where Windows/PowerShell examples and links are presented before their Linux/Azure CLI equivalents. References to PowerShell are slightly more prominent, especially in sections about revoking access and enabling automatic key rotation, where PowerShell is mentioned first or exclusively in some cases. Linux parity is generally maintained, but Windows tools are prioritized in ordering and some references.
Recommendations
- Present Azure CLI (Linux/macOS) and PowerShell (Windows) examples and links side-by-side, or alternate their ordering to avoid Windows-first bias.
- Where PowerShell is mentioned for tasks (e.g., revoking access), ensure Azure CLI is equally referenced and linked.
- In 'Next steps' and throughout the article, list Azure CLI and PowerShell options together, or in alphabetical order, rather than consistently listing PowerShell first.
- Where possible, provide sample commands for both platforms inline, not just as links.
- Review for any subtle language that implies Windows tools are preferred or default.
Virtual Machines
Enable on-demand disk bursting
...ain/articles/virtual-machines/disks-enable-bursting.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Minor Windows Tools
Summary
The documentation provides examples for enabling on-demand disk bursting using the Azure Portal, PowerShell, Azure CLI, and Resource Manager templates. PowerShell examples are prominent and appear before Azure CLI examples, which may suggest a Windows-first bias. The PowerShell section is detailed and uses Windows-specific terminology (cmdlets), but Azure CLI examples are also provided, supporting Linux/macOS users. No Linux-specific tools or shell examples (e.g., Bash scripting) are included, but the CLI coverage is sufficient for cross-platform parity. The Azure Portal instructions are platform-neutral.
Recommendations
- Consider presenting Azure CLI examples before PowerShell examples, as CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Add brief Bash scripting examples for advanced Linux users, if relevant.
- Clarify that Azure PowerShell is available in Azure Cloud Shell, which is accessible from any OS.
Virtual Machines
Enable end-to-end encryption using encryption at host - Azure portal - managed disks
...-machines/disks-enable-host-based-encryption-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for subscription and feature registration tasks, but PowerShell examples are consistently shown first. The 'Next steps' section links to a PowerShell-focused sample repository, and there is a slight emphasis on PowerShell usage, which is more common on Windows. However, Linux parity is maintained via Azure CLI examples and explicit applicability to both Linux and Windows VMs.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or show Azure CLI examples first in some sections to avoid implicit Windows prioritization.
- Include links to Azure CLI sample repositories in the 'Next steps' section, not just PowerShell.
- Clarify that both PowerShell and CLI can be used from Cloud Shell, which is available on all platforms.
- Explicitly mention that all steps are applicable to both Linux and Windows VMs, as already indicated, but reinforce this in the 'Next steps' and sample links.
Virtual Machines
Secure Azure Managed Disk Downloads and Uploads
...icles/virtual-machines/disks-secure-upload-download.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell examples are often presented before CLI, which may subtly prioritize Windows users. The 'Next steps' section lists CLI (Linux) guides first, but throughout the main content, PowerShell is frequently mentioned before CLI, and portal instructions are also Windows-centric. However, Linux parity is generally maintained, and CLI examples are present.
Recommendations
- Ensure Azure CLI (Linux/macOS) examples are given equal prominence and are not consistently listed after PowerShell.
- Where possible, alternate the order of PowerShell and CLI examples, or present them side-by-side.
- Clarify that Azure CLI works on Windows, Linux, and macOS to avoid implicit platform bias.
- Add explicit notes or links for Linux/macOS users where relevant, especially in sections referencing PowerShell.
- Consider including Bash or shell script snippets for common tasks, if applicable.