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 426-450 of 815 flagged pages
Virtual Machines
Migrate from Amazon Elastic Compute Cloud (Amazon EC2) to Azure Virtual Machines
...ion/migrate-from-elastic-compute-cloud-architecture.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a migration guide from Amazon EC2 to Azure Virtual Machines, covering architecture, storage, networking, and image translation. While the guide is generally platform-neutral, there are subtle signs of Windows bias: Windows-specific tools (Sysprep) are mentioned before Linux equivalents, and some image preparation steps highlight Windows patterns first. There are no explicit PowerShell examples, but Windows-centric terminology and processes are referenced before Linux alternatives. Linux-specific migration steps (such as waagent installation) are mentioned, but often after Windows steps or with less detail.
Recommendations
- Ensure Linux and Windows migration steps are presented with equal prominence and detail.
- When describing image generalization, mention Linux steps (waagent installation) before or alongside Windows steps (Sysprep), rather than after.
- Provide explicit Linux migration examples or references (e.g., shell commands, Linux agent installation, troubleshooting).
- Include links to Linux-specific Azure documentation and migration tools.
- Avoid defaulting to Windows terminology (e.g., 'RDP' before 'SSH') in networking and access sections.
Create Pull Request
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 covers backup and disaster recovery for Azure Managed Disks on both Linux and Windows VMs. However, there is a mild bias toward Windows: Windows tools and mechanisms (like Volume Shadow Service and SQL Server Always On) are mentioned first or in greater detail, while Linux equivalents (such as fsfreeze) are referenced briefly and with less explanation. Some backup consistency concepts are explained primarily in Windows terms, and Windows-specific database examples (SQL Server) are more prominent than Linux alternatives.
Recommendations
- Provide equally detailed explanations and examples for Linux tools (e.g., expand on fsfreeze usage, mention other Linux backup consistency solutions).
- Include more Linux-centric database scenarios (e.g., MySQL, PostgreSQL) alongside SQL Server.
- When discussing application-consistent backups, clarify Linux approaches and limitations, and reference relevant documentation.
- Ensure parity in example ordering (e.g., mention Linux and Windows tools together, not Windows-first).
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell examples are always present even though the page is Linux-focused. In several sections, PowerShell examples are given equal prominence to CLI, and sometimes appear before or alongside CLI, despite PowerShell being less relevant for Linux users. There are no missing Linux examples, and all tooling is cross-platform, but the inclusion and prominence of PowerShell creates minor friction for Linux users.
Recommendations
- Prioritize Azure CLI examples and explanations, as CLI is the primary cross-platform tool for Linux users.
- Move PowerShell examples to secondary sections or appendices, or clearly label them as 'for Windows users or PowerShell users'.
- Consider removing PowerShell examples from the main flow unless there is a strong use case for PowerShell on Linux.
- Add explicit notes clarifying that Azure CLI is recommended for Linux and macOS users.
- Where possible, provide Bash shell script examples for local operations (e.g., checking agent version) and troubleshooting.
Virtual Machines
Create an encrypted image version with customer-managed keys
.../articles/virtual-machines/image-version-encryption.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for creating encrypted image versions with customer-managed keys, but PowerShell (a Windows-centric tool) is presented first and in greater detail. There is a slight Windows-first bias in the ordering and depth of examples, but Linux users can complete all tasks using the Azure CLI or Portal instructions.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is fully cross-platform and more familiar to Linux/macOS users.
- Ensure that CLI and PowerShell sections are equally detailed, with parallel explanations and example complexity.
- Explicitly state that all steps can be performed on Linux/macOS using the Azure CLI, and link to CLI installation instructions if not already present.
- Where possible, add Bash shell script snippets for common tasks, especially for VM creation, to further improve Linux parity.
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation is overwhelmingly Linux-focused and provides detailed, distribution-specific Linux instructions for expanding disks on Azure VMs. However, there is a single section at the end that introduces a PowerShell script for checking classic VM SKU support for disk expansion without downtime. This script is only provided in PowerShell, with no Azure CLI or Bash equivalent, which may create friction for Linux users who do not use PowerShell.
Recommendations
- Provide an Azure CLI or Bash equivalent for the PowerShell script that checks classic VM SKU support for disk expansion without downtime.
- If the check cannot be performed with Azure CLI, explicitly state this and provide guidance for Linux users on how to run the PowerShell script (e.g., via Azure Cloud Shell, which supports PowerShell regardless of OS).
- Consider moving the PowerShell-only section to an appendix or clearly mark it as optional/advanced for users who require classic VM SKU support.
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 is generally cross-platform and explicitly states applicability to both Linux and Windows VMs. However, there are minor instances of Windows bias: Windows tools and terminology are sometimes mentioned first (e.g., PowerShell and Windows-specific links), Windows partitioning concepts are referenced more heavily, and some links and examples are Windows-centric or listed before Linux equivalents. Linux tools and paths are included but sometimes after Windows references.
Recommendations
- Ensure that Linux and Windows examples/tools are presented together or in parallel, rather than Windows-first.
- Where partitioning or disk management is discussed, include Linux-specific references (e.g., parted, fdisk, GPT/MBR links for Linux).
- When linking to guides (e.g., uploading VHDs), list Linux and Windows options side-by-side, not Windows-first.
- Expand explanations of disk roles and partitioning to include Linux terminology and tools equally.
- Review all links and ensure Linux equivalents are provided and equally visible.
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Minor Windows Template Bias
Summary
The documentation provides both Windows and Linux parity in most command-line and portal instructions, but there are minor signs of Windows bias: PowerShell examples are always present and sometimes more detailed, and the ARM template example is Windows-centric (defaulting to Windows images and OS versions). However, the CLI examples use Ubuntu images and the documentation explicitly states it applies to both Windows and Linux VMs. No critical Linux gaps are present.
Recommendations
- In ARM template examples, include a Linux image option or show how to switch the image to a Linux distribution, or provide a Linux-focused template tab.
- When showing PowerShell examples, ensure Bash or CLI examples are equally detailed and shown first or in parallel.
- In the ARM template parameters, add Linux OS SKU options and clarify how to deploy a Linux VM.
- Consider alternating the order of CLI and PowerShell tabs or defaulting to CLI (which is cross-platform) to avoid subtle Windows-first bias.
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 details before Linux, but provides parity in information for both platforms. No Windows-specific tools or examples are given, and Linux support is clearly described. The 'Next steps' section references CLI, Portal, and PowerShell, but does not prioritize Windows tools or omit Linux equivalents.
Recommendations
- Consider presenting Linux and Windows operating system support in parallel or alphabetical order to avoid perceived prioritization.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users, if not already clear in linked pages.
- Ensure that linked 'PowerShell' and 'CLI' documentation provide Linux/macOS examples where relevant.
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, referencing both Windows and Linux VM options and pricing. However, there is a minor bias where Windows-specific recommendations (e.g., 'Use at least B2 for Windows machines') are mentioned before Linux equivalents, and Windows pricing links are listed before Linux pricing links. No critical sections are Windows-only, and Linux users can complete all tasks described.
Recommendations
- When mentioning VM sizing recommendations, provide equivalent guidance for Linux VMs (e.g., 'Use at least B2 for Linux machines' if applicable).
- When linking to pricing pages, list both Windows and Linux links together or alternate their order to avoid Windows-first bias.
- Ensure automation and scheduling examples reference cross-platform tools (e.g., Azure Automation, Logic Apps) without implying Windows-only usage.
- Review for any implicit assumptions about Windows usage and clarify when recommendations apply to both platforms.
Virtual Machines
Benchmark your application on Azure Disk Storage
...lob/main/articles/virtual-machines/disks-benchmarks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions both Windows and Linux VMs are supported and references both DiskSpd (Windows) and FIO (Linux) as benchmarking tools. However, DiskSpd (Windows) is mentioned first, and the overall tone and example setup (such as host caching configuration) may be more familiar to Windows users. The actual benchmarking examples are not shown in this excerpt, but the structure suggests Windows tools and patterns are prioritized.
Recommendations
- Ensure Linux benchmarking examples (using FIO) are provided alongside Windows examples, with equal detail and visibility.
- Alternate the order of tool presentation (sometimes mention FIO first) to avoid Windows-first bias.
- Clarify any differences in disk setup or caching configuration for Linux users, as terminology and tooling may differ.
- Explicitly state that both DiskSpd and FIO are equally supported and provide links to Linux-specific guidance where relevant.
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 Azure PowerShell and Azure CLI examples for key tasks, but PowerShell examples are often presented before CLI (which is more cross-platform). References to the Azure portal, PowerShell, and CLI are generally balanced, but PowerShell is sometimes prioritized. The 'Next steps' section lists Linux and Windows resources separately, but the PowerShell (Windows) example appears before the CLI (Linux) example in some places.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, and encourage its use for cross-platform scenarios.
- Where possible, add Bash or shell script examples alongside PowerShell, especially for disk operations.
- Ensure that links and instructions for Linux/macOS users are as prominent and accessible as those for Windows users.
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
Minor Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux, providing links to both PowerShell (Windows) and CLI (Linux) guides for most procedures. However, there are several instances where Windows/PowerShell links or references are listed before their Linux/CLI equivalents, and some cross-references (such as for automatic key rotation) point only to a Windows/PowerShell-specific article. There is also a slight emphasis on PowerShell for certain tasks, with CLI mentioned second or as an alternative.
Recommendations
- Ensure that all procedural links (such as enabling automatic key rotation) are provided for both Windows/PowerShell and Linux/CLI, or clarify if a feature is only available via one tool.
- When listing options (e.g., PowerShell and CLI), alternate the order or present them together (e.g., 'using PowerShell or CLI') to avoid a consistent Windows-first pattern.
- Where possible, provide direct Linux/CLI examples or links alongside PowerShell, especially for critical workflows.
- Review references to Windows-specific tools or documentation (such as Cryptography API: Next Generation) and, if relevant, add Linux equivalents or clarify their applicability.
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 (a Windows-centric tool) is given equal prominence and sometimes appears first in sections. There are no Linux-specific command-line examples (e.g., Bash, shell scripting), and no mention of Linux-native tools for disk management. However, Azure CLI is cross-platform and all steps can be completed on Linux/macOS. The documentation does not use Windows-only tools or patterns, but the heavy use of PowerShell and its parity with Azure CLI may create friction for Linux users.
Recommendations
- Consider showing Azure CLI examples before PowerShell, as Azure CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly note that Azure CLI commands can be run on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
- Add brief Bash shell scripting examples for disk operations where relevant, or clarify that Azure CLI is the recommended tool for Linux/macOS.
- Where PowerShell is used, clarify its platform support and recommend Azure CLI for Linux/macOS users.
Virtual Machines
What's new in Azure Disk Storage
...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is generally platform-neutral, focusing on Azure Disk Storage features and regional availability. However, there are minor instances of Windows bias: some links and references point to Windows-specific documentation first or exclusively (e.g., 'expand with Ultra Disks and Premium SSD v2' links to a Windows article, and 'find unattached disks' links to a Windows page). The mention of Azure PowerShell in the context of disk properties is not accompanied by explicit Linux CLI parity, though Azure CLI is referenced elsewhere. No critical features are described as Windows-only, and Linux equivalents are usually available or referenced, but sometimes after Windows.
Recommendations
- Ensure that all feature documentation links reference both Windows and Linux guides equally, or provide a platform-neutral landing page.
- When referencing tools (e.g., Azure PowerShell), also mention Azure CLI or other cross-platform tools, and provide examples for both.
- Where possible, avoid linking to Windows-specific documentation unless the feature is Windows-only; otherwise, include Linux/macOS links alongside.
- Review the order of examples and links to avoid consistently showing Windows first.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows VM scenarios for ephemeral OS disks and provides parity in technical explanations and examples. However, there is a mild Windows bias in the ordering of examples and references: Windows Server image sizing is discussed first in the 'Size requirements' section, and PowerShell is mentioned before CLI in the 'Customer Managed key' section. Both Linux and Windows tools are referenced, but Windows examples and tools tend to appear first.
Recommendations
- Alternate the order of Linux and Windows examples in sections where both are relevant, or present them side-by-side.
- In the 'Customer Managed key' section, mention Azure CLI and PowerShell together, or list CLI first for Linux parity.
- Ensure that Linux-specific considerations (such as image sizing, disk placement, and OS disk management) are given equal prominence and detail as Windows examples.
- Where possible, provide explicit Linux command examples alongside Windows/PowerShell examples.
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 Tools
Powershell Heavy
Windows First
Summary
The documentation is focused on Linux, but several sections (notably deployment and troubleshooting) present Windows-centric tools (Azure PowerShell) before Linux-native equivalents (Azure CLI). PowerShell examples are detailed and appear before CLI examples, and troubleshooting references Azure PowerShell first. There is also a reference to a Windows-specific Key Vault access policy guide in the template deployment section. However, Linux-specific instructions, paths, and concepts are well covered, and CLI parity is generally maintained.
Recommendations
- Present Azure CLI examples before Azure PowerShell examples, as CLI is cross-platform and native to Linux.
- Clarify that Azure PowerShell is optional and not required for Linux users.
- Remove or supplement references to Windows-specific guides (e.g., Key Vault access policy for Windows VM) with Linux equivalents.
- Expand troubleshooting to highlight CLI commands and Linux-native log analysis tools before PowerShell.
- Consider adding a short section explaining the difference between PowerShell and CLI for Linux users, emphasizing CLI as the preferred tool.
Virtual Machines
Share an Azure Managed Disk across VMs
...cs/blob/main/articles/virtual-machines/disks-shared.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides parity between Windows and Linux in terms of supported workloads, cluster managers, and disk features. However, in the 'Sample workloads' section, Windows examples are presented first and in greater detail, with more application scenarios and links than Linux. Linux examples are present and include supported distributions, cluster managers, and utilities, but are less extensive and detailed compared to Windows. The performance throttles and reservation flow sections are neutral and apply to both OSes.
Recommendations
- Expand the Linux sample workloads section to include more detailed application scenarios, similar to the Windows section (e.g., clustered databases, file servers, SAP workloads).
- Add links to Linux-specific templates or guides for deploying clustered file servers, SAP Central Services, or other common Linux workloads using shared disks.
- Ensure that Linux examples and tools are presented with equal detail and prominence as Windows examples.
- Consider alternating the order of Windows and Linux sections or presenting them side-by-side for parity.
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 primarily focused on Linux, as indicated by the title and content. However, in the deployment section, PowerShell examples are presented before Azure CLI examples, and PowerShell is a Windows-centric tool. There is also mention of an extension for Windows VMs, but this is appropriately referenced as a cross-link. The troubleshooting section also includes PowerShell commands before Azure CLI. All other examples, instructions, and screenshots are Linux-specific, and Linux tools and commands are used throughout.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more relevant for Linux users.
- Clearly label PowerShell sections as 'Windows only' or 'for Windows users', and Azure CLI as 'cross-platform'.
- Consider removing or minimizing PowerShell examples unless there is a strong use case for Linux administrators using PowerShell.
- Ensure troubleshooting commands prioritize Azure CLI and Linux-native tools.
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 generalizing/deprovisioning VMs before imaging. However, the Windows section presents PowerShell examples and Windows-specific registry/configuration steps, and the Windows example for marking a VM as generalized uses PowerShell, while the Linux example uses Azure CLI. The Windows section appears after the Linux section, but the PowerShell example is shown for Windows without an Azure CLI equivalent. There is minor bias in tool selection and example parity.
Recommendations
- Provide Azure CLI examples for Windows VM generalization alongside PowerShell examples, ensuring parity with Linux instructions.
- Mention that both Azure CLI and PowerShell can be used for marking VMs as generalized, and link to relevant documentation for both.
- Consider including a note that Linux users can use PowerShell Core if desired, and Windows users can use Azure CLI.
- Ensure that the documentation structure and tool recommendations are balanced between platforms.
Virtual Machines
What's New in Azure VM Image Builder
...ual-machines/image-builder-api-update-release-notes.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for HTTP, Azure CLI, and Azure PowerShell when demonstrating how to pin to an older API version. PowerShell is a Windows-centric tool, and its inclusion alongside cross-platform tools (CLI and HTTP) is common, but the PowerShell example is given equal prominence. Additionally, in sections describing validation support, PowerShell (Windows) is mentioned separately and with more detail than Shell (Linux), including options like 'run elevated' and 'run as system' that are Windows-specific. However, the overall documentation is balanced, with frequent references to Linux, and most features and examples are not Windows-exclusive.
Recommendations
- Ensure that Linux shell examples are as detailed as Windows PowerShell examples, especially regarding script execution options.
- Consider listing cross-platform tools (HTTP, Azure CLI) before Windows-specific tools (PowerShell) in example tabs.
- Where PowerShell-specific options are described, clarify their Linux equivalents or explicitly state if no equivalent exists.
- Add explicit Bash or shell script examples where PowerShell examples are given, to reinforce Linux parity.
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 parity between Windows and Linux in most sections, including CLI, REST, and portal instructions. However, PowerShell examples are shown with Windows as the default, and Windows is mentioned first in some contexts. The PowerShell section uses Windows as the primary example, with Linux only referenced as an alternative. Additionally, PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- In PowerShell examples, provide Linux-focused examples or clarify that PowerShell can be used cross-platform.
- Ensure that Linux and Windows examples are balanced in order and prominence, especially in scripting sections.
- Add explicit notes about using Azure CLI and REST for Linux/macOS users, and highlight their parity.
- Consider including Bash or shell script examples where appropriate, or link to Linux-specific guidance.
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, with all technical instructions, examples, and requirements tailored for Linux distributions. However, in several places, Azure PowerShell is mentioned alongside Azure CLI as a management tool for Linux VMs, and PowerShell examples/scripts are referenced equally with CLI ones. In the 'Next steps' section and introductory guidance, PowerShell is listed after CLI, but its inclusion may cause minor confusion for Linux users, since PowerShell is less commonly used on Linux compared to CLI/bash. No Windows-specific tools, patterns, or examples are prioritized or exclusively presented.
Recommendations
- Clarify that Azure PowerShell is cross-platform and can be used on Linux, but Azure CLI is generally preferred for Linux VM management.
- Consider providing guidance on installing and using PowerShell on Linux, or explicitly recommend Azure CLI as the default for Linux users.
- Ensure that PowerShell references are not presented as primary or default for Linux scenarios, and that CLI/bash examples are always shown first.
- If PowerShell scripts are referenced, add a note about their Linux compatibility and any prerequisites.
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 parity between Azure CLI and Azure PowerShell examples throughout. However, PowerShell cmdlets and patterns are often mentioned first, especially in critical backup and encryption steps, and some explanations reference PowerShell-specific behaviors (e.g., sequence version requirements) before CLI equivalents. There is also frequent use of PowerShell terminology and links, which may create friction for Linux users unfamiliar with PowerShell.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is more native to Linux environments.
- Clarify that PowerShell can be run cross-platform, but highlight CLI as the default for Linux users.
- Where PowerShell-specific requirements are discussed (e.g., sequence version), provide equivalent CLI explanations in parallel.
- Reduce references to PowerShell-specific backup patterns unless they are equally relevant for CLI users.
- Add explicit notes or guidance for Linux users who may not use PowerShell, including links to CLI documentation and troubleshooting.
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 comprehensive Linux-specific guidance, examples, and tools. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific content. No PowerShell or Windows-only tools are used for Linux configuration, except for a single PowerShell snippet for base64 encoding cloud-init (which is relevant for Azure users on Windows). All configuration and troubleshooting examples are Linux-centric.
Recommendations
- Move the Windows Server 2016 discussion and links to a background section or an appendix, emphasizing Linux-specific mechanisms first.
- Provide a Linux shell command alternative for base64 encoding cloud-init (e.g., `base64 cloud-config.txt`) alongside the PowerShell example.
- Clarify that the Windows references are for Azure host context, not VM configuration, to avoid confusion.
- Ensure Linux examples and tools are always presented first and Windows references are secondary or contextual.
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 Red Hat Enterprise Linux VHDs for Azure. However, in most sections, instructions for Hyper-V (a Windows-centric hypervisor) are presented first, and references to Windows tools (e.g., Hyper-V Manager) appear before Linux-native alternatives. All major Linux workflows (KVM, VMware, Kickstart) are thoroughly documented, but the ordering and some phrasing subtly prioritize Windows/Hyper-V environments.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, rather than always after.
- Explicitly state that all workflows are equally supported, and avoid implying Hyper-V is the default or preferred option.
- Where possible, provide parity in detail and clarity for Linux-native workflows, ensuring they are as comprehensive as Hyper-V instructions.
- Consider a summary table at the top listing all supported hypervisors with links to their respective sections, to avoid implicit prioritization.
- In introductory text, clarify that users can use any of the listed hypervisors and that the order does not imply preference.