Virtual Machines
1073
Total Pages
1027
Linux-Friendly Pages
46
Pages with Bias
4.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
284 issues found
Showing 176-200 of 284 flagged pages
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, PowerShell is featured as a primary method alongside CLI, and its inclusion may be seen as Windows-centric since PowerShell is most commonly used on Windows. The CLI example is cross-platform, but PowerShell is presented as an equal alternative, which may create friction for Linux/macOS users who rarely use PowerShell. Additionally, the PowerShell section follows the CLI section, so Windows tools are not shown first, but their presence is notable.
Recommendations
- Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
- Explicitly mention that PowerShell is primarily for Windows users, or note its availability on Linux/macOS if relevant.
- Consider adding Bash or shell script examples if applicable, or reinforce CLI as the main method.
- Add a short note about CLI's cross-platform compatibility to guide non-Windows users.
Create Pull Request
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 preparing Red Hat Enterprise Linux VHDs for Azure using multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, in most sections, the instructions for Hyper-V (a Windows-only hypervisor) are presented first, and references to Windows tools (Hyper-V Manager, convert-vhd cmdlet) appear before Linux alternatives. Linux hypervisors (KVM, VMware) are covered thoroughly and with parity, but Windows-centric tools and ordering are prioritized.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware) are presented before Hyper-V, or at least in parallel.
- When mentioning disk conversion tools, list Linux tools (qemu-img) before or alongside Windows tools (Hyper-V Manager, convert-vhd).
- Clarify that Hyper-V steps are only required for users on Windows, and highlight Linux-native workflows for Linux/macOS users.
- Consider a summary table at the top showing all supported hypervisors and their OS requirements, so Linux users can quickly find relevant instructions.
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 synchronization in Azure and provides comprehensive Linux-specific guidance, commands, and examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details. This could create a perception of Windows-first bias, but all technical guidance is Linux-centric.
Recommendations
- Move or minimize Windows Server 2016 discussion to a background or context section, emphasizing that it is relevant only as the Azure host OS.
- Begin the page with Linux-specific time sync concepts and configuration options, referencing Windows only as necessary for host context.
- Ensure that Linux documentation links and examples are presented before any Windows references.
- Clarify that all configuration steps and examples are for Linux, and that Windows references are for infrastructure context only.
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows VM images, but there are several subtle signs of Windows bias. PowerShell examples are provided alongside Azure CLI, but PowerShell is often shown second and referenced frequently. Some links and references (such as image finding and uploading) point to Windows-specific pages first or separately, and PowerShell is mentioned in feature examples and sharing scenarios. However, Linux equivalents are generally present, and the overall guidance is cross-platform.
Recommendations
- Ensure that Linux and Windows examples are presented with equal prominence, alternating their order or grouping them together.
- Where PowerShell is referenced, ensure Bash/CLI examples are equally detailed and linked.
- Review linked pages to ensure Linux-specific guidance is as accessible as Windows guidance.
- Explicitly state that all features and procedures apply equally to Linux and Windows, unless otherwise noted.
- Consider adding sample Bash scripts or Linux command-line workflows where PowerShell scripts are shown.
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 there are subtle signs of Windows bias. In the PowerShell section, Windows examples are shown first and in more detail, with Linux mentioned as an alternative. PowerShell is presented as a primary scripting option, which is more relevant to Windows users. However, CLI and REST examples are neutral or Linux-first, and the overall guidance covers both OS types.
Recommendations
- In PowerShell examples, show Linux usage first or provide parity in example detail for both OS types.
- Explicitly mention cross-platform PowerShell (pwsh) usage for Linux/macOS users, or clarify that PowerShell examples work on all platforms.
- Ensure all CLI and REST examples include both Linux and Windows variants where relevant.
- Review ordering of OS-specific guidance to avoid always listing Windows first.
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
Windows Reference
Summary
The documentation is focused on Linux VM time sync in Azure and provides extensive Linux-specific guidance and examples. However, the opening sections reference Windows Server 2016 and its time sync improvements, and link to Windows documentation before Linux-specific details. There are no PowerShell or Windows command examples except for a single PowerShell snippet used for base64 encoding cloud-init, which is contextually relevant for Azure users but could be supplemented with a Linux equivalent. All configuration, troubleshooting, and tool instructions are Linux-centric.
Recommendations
- Move or minimize Windows Server 2016 references to a background section or sidebar, emphasizing Linux-specific mechanisms first.
- Provide a Linux shell command equivalent for base64 encoding cloud-init (e.g., 'base64 cloud-config.txt') alongside the PowerShell example.
- Ensure that Linux documentation links are as prominent as Windows links in the 'Next steps' and introductory sections.
- Clarify that Windows references are for host infrastructure context, not for VM configuration.
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 Azure Portal, Azure CLI, PowerShell, and REST API. PowerShell is presented as a distinct example, but it is not prioritized over cross-platform tools. However, in the 'Create a private gallery' section, the PowerShell example is shown after CLI and Portal, which is a minor 'windows_first' bias, as PowerShell is a Windows-centric tool. All critical tasks are covered with cross-platform CLI and REST examples, ensuring Linux/macOS users can complete the tasks without friction.
Recommendations
- Consider clarifying that Azure CLI commands work on Windows, Linux, and macOS.
- Explicitly mention that PowerShell examples are primarily for Windows users, and that Azure CLI is recommended for cross-platform use.
- If possible, provide Bash shell scripting examples for Linux/macOS users, or note that Azure CLI commands can be used in Bash.
- Ensure that CLI examples are always shown before PowerShell, and that PowerShell is clearly labeled as Windows-specific.
Virtual Machines
Instantly access managed disk snapshots
...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI (bash/Linux/macOS) and Azure PowerShell (Windows) examples for creating instant access snapshots, but the PowerShell example is given equal prominence and detail. However, there is no explicit Linux/macOS bias or omission; all critical tasks can be performed using Azure CLI, which is cross-platform. The ordering of examples sometimes puts PowerShell before CLI, and PowerShell is referenced as a primary tool, which may create minor friction for Linux/macOS users.
Recommendations
- Ensure Azure CLI examples are always presented first, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux, macOS, and Windows, while PowerShell is primarily for Windows (though it can run cross-platform).
- Add a short note clarifying that all tasks can be completed on Linux/macOS using Azure CLI.
- Consider including sample bash scripts for automation, or referencing Linux/macOS shell usage where appropriate.
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 page is focused on Linux VM extensions, but consistently presents both Azure CLI and Azure PowerShell examples side-by-side throughout. In several sections, PowerShell examples are given equal prominence to CLI, despite PowerShell being a Windows-centric tool (even though it is cross-platform, its usage is far more common on Windows). Additionally, in the 'Discover VM extensions' section, the PowerShell example is shown after the CLI example, but both are given full code blocks and explanations. There is no evidence of missing Linux examples or exclusive mention of Windows tools, but the parity between CLI and PowerShell may create a subtle Windows-first impression.
Recommendations
- Consider emphasizing Azure CLI as the primary example for Linux-focused documentation, since CLI is natively available on Linux and macOS, while PowerShell is less commonly used in those environments.
- Where PowerShell is included, clarify its cross-platform availability and typical use cases for Linux users.
- If space or clarity is a concern, offer PowerShell examples in expandable sections or as supplementary material, rather than giving them equal prominence.
- Review the ordering of examples to ensure CLI is presented first in all cases for Linux documentation.
- Add explicit notes or links for Linux users on how to install and use PowerShell if they choose to use it.
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 Linux VM GPU driver installation, but includes PowerShell examples alongside Azure CLI and ARM template examples. In several sections, PowerShell is presented before Azure CLI, which is more native to Linux environments. There is also a mention of a Windows extension, but it is clearly separated and not the main topic. All troubleshooting and manual steps are Linux-centric, and Linux tools and commands are used throughout.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is the primary cross-platform tool and more relevant for Linux users.
- Clearly indicate that PowerShell is optional and primarily for users on Windows or those who prefer it, while Azure CLI is recommended for Linux/macOS.
- Consider adding Bash script examples for common deployment scenarios, since Bash is native to Linux.
- Review the order of example sections to ensure Linux-native tools are prioritized.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides thorough Linux-specific guidance. However, there is evidence of Windows bias in the deployment sections: PowerShell examples are given before Azure CLI examples, and troubleshooting commands are shown first in PowerShell. The PowerShell deployment section is more detailed and prominent, despite the extension being Linux-only. There are no missing Linux examples, and all configuration paths, logs, and certificate handling are Linux-centric.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more relevant for Linux users.
- Reduce the prominence of PowerShell deployment instructions or clarify that PowerShell is primarily for Windows users.
- Add explicit notes that Azure CLI is recommended for Linux environments.
- Ensure troubleshooting instructions highlight CLI commands first.
- Consider removing PowerShell deployment instructions unless there is a clear use case for Linux administrators using PowerShell.
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 provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, in several sections, Windows/Hyper-V tools and workflows are presented first or with more detail, such as disk conversion instructions referencing Hyper-V Manager and PowerShell cmdlets before Linux alternatives. Linux/KVM/VMware instructions are present and thorough, but Windows/Hyper-V is often prioritized in ordering and introductory notes.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware) are presented before Hyper-V/Windows tools, or group them equally.
- When mentioning disk conversion tools, list Linux-native tools (qemu-img, guestfish) alongside or before Windows/Hyper-V tools.
- Where possible, provide parity in detail and step-by-step instructions for Linux/KVM/VMware workflows, matching the clarity and completeness of Hyper-V sections.
- Add a summary table at the top outlining the supported hypervisors and tools for both Windows and Linux, making it clear that Linux workflows are fully supported.
- Avoid referencing Windows/PowerShell tools (e.g., convert-vhd cmdlet) before Linux equivalents unless contextually necessary.
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows VM images, but there are signs of Windows bias. PowerShell examples and references are given alongside CLI, but PowerShell is mentioned first in several places. Windows-specific tools (Sysprep) are referenced before Linux equivalents (waagent). Some links and examples are Windows-focused or presented before Linux alternatives. However, Linux support is acknowledged, and CLI examples are provided, so Linux users can complete the tasks.
Recommendations
- Ensure Linux and Windows examples are presented in parallel, alternating order or grouped by OS.
- Provide explicit Linux-focused examples and links wherever Windows examples are given (e.g., for uploading VHDs, generalizing images).
- Avoid mentioning PowerShell first; alternate with CLI or Bash examples.
- Where possible, use cross-platform tools (Azure CLI) as the primary example, and supplement with PowerShell only as needed.
- Review linked pages to ensure Linux parity in referenced content.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell example is given equal prominence, and the CLI example is not explicitly labeled as Linux/macOS-friendly. The tab order presents CLI first, but the PowerShell section is detailed and assumes familiarity with Windows tools. There is no explicit mention of Linux-specific considerations or alternative Linux-native tools.
Recommendations
- Clarify that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
- Explicitly mention that PowerShell examples are primarily for Windows users, while CLI is recommended for Linux/macOS.
- Consider adding a note or section for Linux users, confirming that all quota management tasks can be performed using Azure CLI.
- If relevant, provide example commands for Bash or other common Linux shells, or mention that Azure CLI can be installed natively on Linux.
Virtual Machines
Enable Trusted launch on existing Gen2 VMs
...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity for both Linux and Windows VMs, including explicit statements that the feature applies to both. However, there is a mild Windows bias in the ordering and tooling: PowerShell examples are provided alongside CLI and ARM template, but PowerShell is a Windows-centric tool and its installation instructions link to Windows-specific pages. Additionally, in some sections, PowerShell is listed before CLI, and screenshots reference RDP (Windows) before SSH (Linux). The documentation does mention Linux-specific validation (SBInfo tool), but overall, Windows tools and patterns are slightly prioritized.
Recommendations
- Add explicit instructions or links for installing Azure PowerShell on Linux/macOS, not just Windows.
- Where possible, clarify that PowerShell can be used cross-platform, or highlight CLI as the preferred cross-platform tool.
- Alternate the order of CLI and PowerShell sections, or list CLI first to emphasize cross-platform accessibility.
- Ensure screenshots and example text reference SSH (Linux) and RDP (Windows) equally, or alternate their order.
- Consider adding Bash shell script examples for Linux users, if relevant.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The FAQ for Trusted Launch covers both Windows and Linux VM scenarios. However, there is a mild Windows bias: PowerShell examples are consistently provided alongside CLI, and Windows-specific terminology and links (e.g., Secure Boot, Hyper-V) often appear first or are referenced before Linux equivalents. While Linux examples and troubleshooting are present (especially for Secure Boot validation and SBInfo tool usage), Windows examples and tools are sometimes prioritized or more detailed. The documentation does not omit Linux information, but Windows examples are often shown first and PowerShell is always included.
Recommendations
- Alternate the order of CLI and PowerShell examples so Linux CLI is not always second.
- Where possible, provide Bash shell examples for Linux users alongside PowerShell.
- Ensure Linux-specific troubleshooting and validation steps are as prominent and detailed as Windows equivalents.
- Add explicit notes clarifying parity between Windows and Linux for each feature or command.
- Consider including macOS-specific notes or examples where relevant (e.g., Azure CLI usage on macOS).
Virtual Machines
Qualys Cloud Agent Extension for Azure VMs
...ob/main/articles/virtual-machines/extensions/qualys.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation covers both Windows and Linux VM deployment methods for the Qualys Cloud Agent and provides parallel links for each OS where relevant. However, in several sections, Windows examples or links are listed before Linux equivalents, which may subtly reinforce a Windows-first perspective.
Recommendations
- Alternate the order of Windows and Linux examples/links in each section, or present them in alphabetical order (Linux, then Windows) for parity.
- Explicitly state that all deployment methods are supported on both Windows and Linux at the beginning of the relevant sections.
- Where possible, provide combined instructions or tables that show both Windows and Linux commands side-by-side.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides comprehensive Linux-specific guidance. However, in deployment and troubleshooting sections, PowerShell examples are presented first and in greater detail than Azure CLI equivalents, despite Linux users typically favoring Azure CLI or shell scripting. Additionally, troubleshooting instructions reference Azure PowerShell before Azure CLI, which may create friction for Linux users.
Recommendations
- Present Azure CLI examples before PowerShell examples in deployment and troubleshooting sections, as CLI is more relevant for Linux users.
- Expand Azure CLI troubleshooting guidance to match the detail provided for PowerShell.
- Clarify that PowerShell examples are primarily for Windows users, and highlight Azure CLI as the preferred method for Linux environments.
- Consider adding Bash scripting examples for common operations, if relevant.
Virtual Machines
Instantly access managed disk snapshots
...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI (bash-style) and Azure PowerShell examples for creating instant access snapshots, but PowerShell is presented as a primary example alongside CLI. The CLI example uses bash syntax, which is Linux/macOS-friendly, but PowerShell is listed second and is Windows-centric. There are no Linux-specific tools or commands (such as direct REST API calls or references to Linux-native scripting), but the CLI coverage is sufficient for Linux/macOS users. The documentation avoids Windows-only tools and does not mention Windows patterns or tools before Linux equivalents, but PowerShell is still prominent.
Recommendations
- Ensure Azure CLI examples are always listed first, as they are cross-platform.
- Consider adding explicit notes clarifying that Azure CLI commands work on Linux, macOS, and Windows.
- Optionally, provide REST API or Python SDK examples for advanced Linux/macOS users.
- Clarify that PowerShell is optional and primarily for Windows users.
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 provides both Azure CLI and Azure PowerShell examples for all major extension management tasks, but consistently lists PowerShell examples immediately after CLI, and sometimes with more detailed output. There is a slight 'Windows-first' ordering in some sections, and PowerShell is given parity with CLI despite Linux users overwhelmingly preferring CLI. No Linux-specific tools (e.g., Bash scripts, cloud-init) are referenced for extension management, and troubleshooting/log paths are Linux-appropriate. No critical Windows-only tools or patterns are present, and all examples are valid for Linux VMs.
Recommendations
- Consider listing Azure CLI examples before PowerShell in all sections, as CLI is the primary cross-platform tool for Linux users.
- Explicitly state that Azure PowerShell is available on Linux, but CLI is recommended for Linux VM management.
- Add a short Bash script example for extension management using the Azure CLI to reinforce Linux-native workflows.
- Where possible, reference Linux-native automation tools (e.g., cloud-init, Bash scripting) in the context of VM extension management.
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 there is a subtle Windows bias in some areas. PowerShell examples are shown with Windows as the default OS type, and Windows terminology (Sysprep) is mentioned before Linux equivalents. In the PowerShell section, Windows is the primary example, while Linux is only referenced as an alternative. However, CLI and REST examples default to Linux, and Linux-specific guidance is linked early in the 'Before you begin' section. Overall, Linux users can complete all tasks, but Windows is sometimes prioritized in examples and terminology.
Recommendations
- In PowerShell examples, show Linux as the default OS type or provide parallel Linux and Windows examples.
- When referencing OS-specific steps, mention Linux and Windows equally, rather than defaulting to Windows terminology.
- Ensure that CLI and PowerShell sections consistently show both Linux and Windows examples, or alternate which OS is shown first.
- Add explicit notes clarifying parity between Linux and Windows where relevant.
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Windows and Linux examples and covers both OSes in detail. However, there are several areas where Windows tools and PowerShell are mentioned first or exclusively, such as using PowerShell for checksum generation, validator examples, and generalization commands. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents are less prominent. Some sections use Windows tools or patterns before Linux equivalents, and PowerShell is often referenced for tasks that could be done with cross-platform tools.
Recommendations
- When describing tasks like generating SHA256 checksums, mention Linux/macOS commands (e.g., 'sha256sum') alongside or before PowerShell equivalents.
- Ensure Linux validator examples are as prominent and detailed as Windows examples, including shell script usage and inline commands.
- Where possible, use cross-platform tools (e.g., Azure CLI) in examples before platform-specific tools (e.g., PowerShell).
- For sections like generalization, provide Linux command examples with equal detail and visibility as Windows Sysprep examples.
- Consider alternating the order of Windows and Linux examples to avoid always presenting Windows first.
- Clarify when a feature is Windows-only (e.g., WindowsRestart customizer), and provide Linux alternatives or explicitly state the lack thereof.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, the PowerShell example is given equal prominence, despite PowerShell being primarily a Windows tool. The CLI example is shown first, which is positive, but the presence of a PowerShell section may create friction for Linux/macOS users, as PowerShell is not natively installed on those platforms. No Linux-specific tools or commands (such as Bash scripting or references to native Linux utilities) are mentioned, but the Azure CLI is cross-platform and sufficient for Linux users.
Recommendations
- Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
- Optionally, add a note that PowerShell is available on Linux/macOS, but Azure CLI is more commonly used.
- Ensure that CLI examples are always shown first and are comprehensive.
- Consider adding Bash script examples for automation, if relevant.
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 page is focused on Linux VM time synchronization in Azure and provides comprehensive Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before fully explaining Linux-specific mechanisms. No Windows/PowerShell examples are given except for a single PowerShell command for base64 encoding cloud-init, which is contextually relevant for Azure users but lacks a Linux equivalent. All technical guidance, tools, and examples are Linux-centric.
Recommendations
- Move Windows Server 2016 discussion to a background or context section, or clarify its relevance to Linux VM time sync.
- Provide a Linux shell equivalent for the PowerShell base64 encoding example (e.g., 'base64 cloud-config.txt') for parity.
- Ensure that Linux-specific guidance is presented before or independently of Windows references.
- Consider minimizing Windows documentation links unless directly relevant to Linux VM time sync.
Virtual Machines
Upgrade Gen1 VMs to Trusted launch
...s/virtual-machines/trusted-launch-existing-vm-gen-1.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Windows and Linux guidance for upgrading Gen1 VMs to Trusted launch. However, Windows-specific tools (MBR2GPT.exe, Defrag, PowerShell) are described in detail and appear first, with Linux instructions following. Windows disk conversion and troubleshooting steps are more extensive, while Linux disk conversion is not covered (because most Marketplace Linux images already meet requirements). Azure CLI and ARM template examples are cross-platform, but PowerShell is shown first and used for template deployment. Overall, Linux users can complete the task, but Windows tools and patterns are emphasized.
Recommendations
- Present Linux and Windows instructions in parallel or with equal prominence, rather than Windows-first.
- For ARM template deployment, provide Azure CLI examples alongside PowerShell.
- Expand Linux troubleshooting guidance for disk layout issues, even if rare, to match Windows detail.
- Clarify that Azure CLI and ARM templates are fully cross-platform and recommend them for Linux users.
- Consider adding links or references to Linux disk conversion tools (e.g., gdisk, parted) for custom images.