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 201-225 of 284 flagged pages
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, with explicit statements that the feature applies to both. CLI and ARM template instructions are platform-neutral. However, PowerShell instructions are given equal prominence as CLI, and PowerShell is primarily a Windows tool (though available on Linux, it's less commonly used there). Additionally, in some sections (e.g., Portal and PowerShell tabs), Windows terminology (RDP) is mentioned before Linux (SSH), and PowerShell is listed before ARM template, which may subtly prioritize Windows patterns.
Recommendations
- Clarify that PowerShell instructions are applicable on both Windows and Linux, or provide Bash/Cloud Shell alternatives where relevant.
- Consider listing CLI instructions before PowerShell, as CLI is more universally used across platforms.
- When mentioning remote access, list SSH (Linux) and RDP (Windows) together, or alternate their order to avoid subtle Windows-first bias.
- Add explicit notes or links for Linux users regarding PowerShell usage, or suggest Azure Cloud Shell as a cross-platform option.
- Ensure screenshots and terminology are neutral or include both Linux and Windows examples where possible.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for most operations, but PowerShell (a Windows-centric tool) is consistently presented alongside or immediately after CLI. In some cases, Windows-specific image examples are shown first, and PowerShell is given equal prominence to CLI, which may create a subtle Windows-first impression. However, Linux-specific instructions and tools (such as SBInfo for Secure Boot validation) are included where relevant, and Linux images are referenced in CLI/PowerShell commands. There are no critical omissions for Linux users.
Recommendations
- Where possible, lead with Azure CLI examples (which are cross-platform) before PowerShell, especially in sections not inherently Windows-specific.
- When demonstrating image queries, alternate or balance the use of Windows and Linux images as examples.
- Continue to provide explicit Linux troubleshooting and validation steps, as done with the SBInfo tool.
- Consider adding Bash scripting examples for common automation scenarios, where appropriate.
- Clarify in introductory sections that both Linux and Windows are fully supported, and that all examples apply to both unless otherwise noted.
Virtual Machines
Trusted Launch for Azure VMs
.../blob/main/articles/virtual-machines/trusted-launch.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation covers Trusted Launch for both Linux and Windows VMs, but there are several subtle signs of Windows bias. Windows examples and references (such as ARM templates for Windows VMs) are presented first in example lists. Windows-specific tools and features (like Windows Defender Credential Guard, HVCI, and Secure Boot references) are discussed in detail, with less depth for Linux equivalents. Some links and explanations (e.g., Secure Boot, vTPM, VBS) reference Windows documentation or features before Linux, and Windows driver installation is described as 'not requiring extra steps', while Linux installation is described as requiring workarounds.
Recommendations
- Provide Linux-focused deployment examples alongside or before Windows examples, especially in sections listing ARM templates.
- Expand explanations of Linux equivalents for security features (e.g., Secure Boot, attestation, kernel module validation) to match the depth given to Windows features.
- Balance references to Windows tools with Linux tools (e.g., mention Linux attestation and boot integrity solutions).
- Ensure that Linux-specific guidance (such as driver installation steps) is as clear and prominent as Windows guidance.
- Where possible, link to Linux documentation or community resources for features like Secure Boot and vTPM.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization. However, the PowerShell section is presented immediately after the CLI section, and the PowerShell example is detailed and uses Windows-centric terminology (e.g., PowerShell SDK objects). The CLI example uses a Linux image (Ubuntu2204), but there is no explicit Linux/macOS shell example or mention of Bash scripting. The documentation refers to SQL Server as a licensing example, which is Windows-centric, but this is not flagged as bias since SQL Server is also available on Linux. Overall, the documentation is slightly Windows-biased in its ordering and tooling focus, but Linux users can complete all tasks using the CLI and ARM templates.
Recommendations
- Add explicit Bash or Linux/macOS shell examples for Azure CLI usage, clarifying that CLI commands work cross-platform.
- Consider mentioning that PowerShell is available on Linux/macOS, or provide a Bash equivalent for any PowerShell-specific steps.
- Ensure that CLI examples are shown first or equally with PowerShell, and clarify that both methods are supported on all OSes.
- Add a note that ARM templates and Azure CLI are fully cross-platform and suitable for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for VM vCore customization, but the PowerShell section is presented immediately after the CLI section and is detailed, which may suggest a slight Windows-first bias. However, the CLI example uses an Ubuntu image and is clearly cross-platform. There are no missing Linux examples, and no exclusive mention of Windows tools or patterns. The ARM template section is platform-neutral. The overall bias is minor and does not significantly impact Linux/macOS users.
Recommendations
- Consider explicitly stating that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Add a brief note in the PowerShell section clarifying its Windows-centric nature.
- Ensure parity in example detail between CLI and PowerShell sections.
- Optionally, provide Bash shell scripting examples for Linux users, though Azure CLI already covers this.
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. However, the PowerShell example is given equal prominence as the CLI, and the CLI example is not explicitly labeled as Linux/macOS-friendly. The PowerShell section may imply a Windows-centric approach, and the CLI example is shown first, but overall, Linux users can fully complete the task using the CLI instructions.
Recommendations
- Explicitly state that Azure CLI works on Linux, macOS, and Windows, and is the recommended cross-platform tool.
- Add a note clarifying that PowerShell examples are primarily for Windows users, while CLI is for all platforms.
- Consider mentioning Bash or shell scripting for advanced quota checks, if relevant.
- Ensure future examples do not assume PowerShell as the default unless the topic is Windows-specific.
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
Windows Tools
Summary
The documentation covers both Windows and Linux VM images, but there are several signs of Windows bias. PowerShell examples and references are frequent and often shown alongside or before CLI equivalents. Windows-specific tools (Sysprep) are mentioned before Linux equivalents (waagent), and links to Windows upload instructions are listed before Linux. Some references and examples default to Windows terminology or patterns, even though the feature is cross-platform.
Recommendations
- Ensure that Linux examples (Azure CLI, waagent, Linux upload instructions) are presented with equal prominence and order as Windows/PowerShell examples.
- Where PowerShell and CLI examples are shown, alternate their order or group them together to avoid always showing Windows first.
- Add explicit Linux-focused sections or examples where only Windows/PowerShell is currently referenced.
- Review links and references to ensure Linux documentation is as accessible as Windows documentation.
- Where possible, use neutral language and avoid defaulting to Windows terminology when the feature is cross-platform.
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 cross-platform examples for creating an Azure Compute Gallery, including Azure CLI, REST API, Portal, and PowerShell. However, PowerShell examples are presented alongside CLI and REST, and the PowerShell section is given equal prominence. The CLI examples use Bash-style syntax and variables, which are Linux/macOS-friendly. The only minor bias is that PowerShell is included as a primary example, which may be unnecessary for Linux/macOS users, but there are no missing Linux examples or Windows-only tools.
Recommendations
- Clarify in the PowerShell section that PowerShell is primarily for Windows users, and suggest Azure CLI as the preferred cross-platform tool.
- Consider listing Azure CLI examples before PowerShell to reinforce Linux/macOS parity.
- Explicitly state that Azure CLI works on Windows, Linux, and macOS, making it the recommended option for non-Windows environments.
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, there is a mild Windows bias in the ordering and prominence of deployment examples: Azure PowerShell instructions and examples are presented before Azure CLI, even though Linux users are more likely to use Azure CLI. Additionally, troubleshooting instructions reference Azure PowerShell before Azure CLI. There are no Windows-only tools or missing Linux examples; all technical steps and paths are Linux-specific.
Recommendations
- Present Azure CLI deployment instructions before Azure PowerShell, as CLI is the primary tool for Linux users.
- Highlight Azure CLI as the recommended method for Linux deployments.
- Ensure troubleshooting sections reference Azure CLI first, followed by PowerShell.
- Consider adding a note clarifying that PowerShell is optional and primarily for cross-platform or Windows users.
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 clear, parallel instructions for both Linux and Windows VM generalization. However, the Windows section includes more detailed prerequisites and troubleshooting steps, and Windows PowerShell/Command Prompt examples are shown before their Linux equivalents in some places. The Linux section is concise and relies heavily on waagent, while the Windows section uses multiple Windows-specific tools and registry edits. Both OSes are covered, but Windows examples and tools are somewhat more prominent.
Recommendations
- Ensure Linux prerequisites are as detailed as Windows prerequisites, including troubleshooting tips and common pitfalls.
- Provide Linux CLI alternatives for all Azure CLI and PowerShell commands (e.g., show az CLI usage for both OSes, not just in Linux section).
- Consider presenting Linux and Windows sections in parallel structure, or alternate which OS is shown first in examples.
- Expand Linux section to include more context about potential issues, similar to the Windows section.
- Where possible, avoid using Windows-specific terminology (e.g., 'Command Prompt') without Linux equivalents (e.g., 'Terminal').
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. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details. All configuration examples, tools, and commands are Linux-centric, with only a single PowerShell command shown for base64 encoding cloud-init (which is relevant for Azure ARM templates, not VM configuration). There are no missing Linux examples or Windows tools used for core tasks.
Recommendations
- Move or minimize the Windows Server 2016 discussion in the introduction, emphasizing Linux relevance first.
- Add a brief explanation for the PowerShell base64 example, noting that Linux users can use 'base64' command instead.
- Consider linking to Linux time sync concepts/documentation before Windows references in the intro and 'Next steps'.
Virtual Machines
Deploy a Trusted Launch VM
...ain/articles/virtual-machines/trusted-launch-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows VM deployment with Trusted Launch, but PowerShell examples are Windows-centric and Windows examples are often presented first. Linux parity is generally good, especially in CLI and template sections, but PowerShell sections focus on Windows images and configurations, and Windows terminology appears before Linux in some places.
Recommendations
- Provide PowerShell examples for Linux VM deployment, including using Set-AzVMOperatingSystem with -Linux and Linux image parameters.
- When listing examples, alternate or parallelize Windows and Linux instructions, rather than defaulting to Windows first.
- Clarify in PowerShell sections that Linux VMs can also be deployed and provide sample scripts for Linux.
- Ensure that terminology and screenshots are inclusive of both OS types, or explicitly state when a step is OS-specific.
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, but there is a mild Windows bias in the ordering and tooling. PowerShell examples are given equal prominence to Azure CLI, but PowerShell is a Windows-centric tool. In the ARM template section, PowerShell is used for deployment commands rather than CLI or cross-platform alternatives. Windows terminology (RDP) is mentioned before Linux (SSH) in verification steps. However, Linux-specific guidance (such as SBInfo for Secure Boot validation) is included, and all procedures are applicable to both OS types.
Recommendations
- In ARM template deployment steps, provide Azure CLI examples alongside PowerShell to ensure cross-platform usability.
- Where possible, mention SSH (Linux) and RDP (Windows) together or alternate their order to avoid Windows-first bias.
- Consider clarifying that PowerShell commands can be run on Linux/macOS via PowerShell Core, or provide CLI alternatives.
- Continue to highlight Linux-specific tools and validation steps as done with SBInfo.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization. The CLI example uses Ubuntu as the image, showing Linux parity, but the PowerShell section is more detailed and appears before ARM template automation. The PowerShell example uses Windows-centric SDK objects and terminology. The ordering of sections (CLI, then PowerShell) is reasonable, but the PowerShell example is more verbose and technical. No Linux-specific tools (like Bash scripts or cloud-init) are mentioned, but the CLI example covers Linux use cases. There is minor bias in the depth and detail of Windows/PowerShell instructions.
Recommendations
- Add Bash or shell script examples for Linux users, especially for automation scenarios.
- Clarify that Azure CLI works equally well for both Linux and Windows, and provide explicit Linux/macOS usage notes.
- Balance the detail between PowerShell and CLI sections, ensuring CLI instructions are as comprehensive as PowerShell.
- Mention Linux-specific automation tools (e.g., cloud-init) if relevant.
- Consider adding a table or summary comparing CLI, PowerShell, and ARM template approaches for both OS types.
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 (cross-platform) and Azure PowerShell (Windows-centric) examples for creating instant access snapshots, with CLI examples shown first. There are no Linux-specific tools or shell scripts, but the CLI coverage is sufficient for Linux/macOS users. No Windows-only tools or patterns are mentioned, and the PowerShell example is not prioritized over CLI. The presence of PowerShell is expected for Azure, but the lack of explicit Linux shell scripting or troubleshooting is a minor bias.
Recommendations
- Consider adding explicit Bash shell script examples for common Linux automation scenarios (e.g., using az CLI in bash loops or with jq for JSON parsing).
- Clarify in the introduction that all CLI examples are cross-platform and suitable for Linux/macOS users.
- If there are any troubleshooting steps or advanced usage, provide Linux/macOS-specific notes if behavior differs.
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 primarily Linux-focused, as indicated by the title and content. However, there are some minor Windows bias patterns: PowerShell deployment instructions are presented before Azure CLI instructions, and troubleshooting examples use PowerShell first. The CLI and JSON examples are present and correct for Linux, but the ordering and emphasis on PowerShell may create friction for Linux users who typically use Bash or Azure CLI.
Recommendations
- Present Azure CLI deployment instructions before PowerShell, as CLI is more commonly used on Linux.
- Ensure troubleshooting sections show Azure CLI commands first or equally alongside PowerShell.
- Clarify that PowerShell is optional and primarily for Windows users, while Azure CLI is recommended for Linux.
- Consider adding Bash script examples for common Linux automation scenarios.
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 Linux and Windows in most sections, especially in CLI and REST examples, but there is a subtle Windows bias in the PowerShell examples and ordering. PowerShell examples are Windows-centric by default, and Windows is mentioned first in some places. Linux is well-covered, but Windows examples and terminology sometimes appear before Linux equivalents.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence and ordering, especially in PowerShell and CLI sections.
- In PowerShell examples, provide explicit Linux-focused examples (e.g., using -OsType Linux) alongside Windows ones.
- Where possible, alternate the order of Linux and Windows examples to avoid implicit prioritization.
- Add clarifying notes that PowerShell can be used for Linux images as well, and show Linux-specific PowerShell commands.
Virtual Machines
Azure Instance Metadata Service for virtual machines
...articles/virtual-machines/instance-metadata-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides both Windows (PowerShell) and Linux (bash/curl) examples for all major usage scenarios, with clear tab separation. However, Windows/PowerShell examples are consistently presented first in each sample, and some troubleshooting and advanced routing instructions are more verbose for Windows (including PowerShell CLI examples even in Linux troubleshooting). Windows-specific tools (PowerShell, route print, ipconfig) are referenced before their Linux equivalents, but Linux coverage is strong and parity is maintained throughout.
Recommendations
- Alternate the order of Windows and Linux examples, or present Linux first in some sections to avoid implicit prioritization.
- Ensure troubleshooting steps for Linux are as detailed as those for Windows, and avoid including PowerShell CLI examples in Linux troubleshooting unless a direct Linux CLI equivalent is also provided.
- Where possible, reference Linux tools (e.g., netstat, ip, ifconfig) alongside Windows tools in general guidance sections.
- Consider adding a short note at the start stating that both Linux and Windows are equally supported, and that example order does not imply priority.
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 is a mild Windows bias in several areas. PowerShell examples are provided alongside Azure CLI, but PowerShell is mentioned first or more prominently in some sections. References to Windows tools (e.g., Sysprep) are given equal footing to Linux tools (waagent), but links to Windows-specific pages (e.g., upload VHD for Windows) are sometimes listed before Linux equivalents. In the FAQ, PowerShell is mentioned before CLI for cross-tenant sharing. Overall, Linux users can complete all tasks, but Windows tools and patterns are sometimes prioritized.
Recommendations
- Ensure that CLI and PowerShell examples are presented in parallel, with equal prominence and ordering.
- When referencing upload or creation guides, list Linux and Windows links together, or alternate their order to avoid Windows-first bias.
- Where possible, provide Bash or shell script examples alongside PowerShell for automation.
- In cross-tenant sharing sections, mention CLI and PowerShell equally, or provide a combined example for both platforms.
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, with explicit statements that the feature applies to both. However, PowerShell examples are used for ARM template deployment and rollback, which may create friction for Linux/macOS users. In several sections, PowerShell is presented before CLI, and installation instructions for Azure PowerShell reference Windows. The CLI examples are cross-platform, but PowerShell is emphasized, suggesting a mild Windows bias.
Recommendations
- Provide Bash or cross-platform shell examples for ARM template deployment and rollback, especially for Linux/macOS users.
- Clarify that Azure PowerShell can be used on Linux/macOS and provide installation links for those platforms.
- Where PowerShell is used, offer equivalent Bash/CLI commands or note that CLI is preferred for Linux/macOS.
- Consider listing CLI examples before PowerShell in tab order, as CLI is more universally available.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization. While the CLI example uses a Linux image (Ubuntu), the PowerShell section is given equal prominence and is described in detail. The ordering of sections places PowerShell immediately after CLI, and both are referenced as valid tools. There is a slight 'windows_first' bias in the ordering and prominence of PowerShell, but Linux users are not blocked from completing the task, as CLI and ARM template examples are provided. No Windows-only tools or patterns are mentioned exclusively, and Linux parity is generally maintained.
Recommendations
- Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Consider providing Bash shell script examples or referencing Bash usage for Linux users.
- Clarify that PowerShell is available cross-platform, but highlight CLI as the default for Linux/macOS.
- Ensure that CLI examples are shown first, or that the ordering does not imply Windows preference.
- Add a note that all features are available regardless of OS, and that the CLI is the recommended tool for Linux/macOS.
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/shell) and Azure PowerShell examples for creating instant access snapshots, but PowerShell is presented as a primary option alongside CLI, and Windows-specific tooling (PowerShell) is given equal prominence. There are no Linux-specific notes or examples beyond Azure CLI, and the CLI examples use bash syntax, which is cross-platform but not explicitly labeled as Linux/macOS. The documentation does not mention Linux tools or patterns (e.g., shell scripting, automation with cron, etc.), nor does it provide troubleshooting or guidance for Linux users. PowerShell is presented before the Azure Portal and Resource Manager Template sections, which may subtly reinforce Windows-centric workflows.
Recommendations
- Explicitly state that Azure CLI examples are cross-platform and suitable for Linux/macOS users.
- Add a note clarifying that PowerShell examples are primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
- Consider providing Linux/macOS-specific tips, such as using shell scripts for automation or integrating with cron.
- Ensure that CLI examples use generic shell syntax and avoid Windows-specific environment variable patterns.
- If possible, add troubleshooting or guidance for Linux users (e.g., common issues with az CLI on Linux).
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 primarily focused on Linux, as expected given the page title. However, there are several sections where Windows-oriented tools (PowerShell) are presented before their Linux equivalents (Azure CLI), and troubleshooting instructions reference Azure PowerShell before Azure CLI. PowerShell deployment examples are given first, despite Linux users typically preferring Azure CLI or shell scripting. There are no missing Linux examples, but the ordering and tool emphasis may create minor friction for Linux users.
Recommendations
- Present Azure CLI examples before PowerShell examples in all deployment and troubleshooting sections, as CLI is the default for Linux users.
- Explicitly note that PowerShell is optional and primarily for Windows users, while Azure CLI is cross-platform and recommended for Linux.
- Add bash shell script examples for common deployment scenarios, if relevant.
- In troubleshooting, show Azure CLI commands first, and clarify that PowerShell is an alternative for Windows users.
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 for both Linux and Windows throughout most sections, including CLI, REST, and portal instructions. However, there is mild Windows bias in the PowerShell examples, which default to Windows as the OS type, and in some cases, Windows is mentioned before Linux (e.g., in the PowerShell section). Additionally, PowerShell is a Windows-centric tool, and its examples are presented alongside CLI, but not prioritized over CLI. The CLI and REST examples default to Linux, balancing the bias. No critical Linux examples are missing, and all workflows are cross-platform.
Recommendations
- In PowerShell examples, show Linux as the default OS type or provide both Linux and Windows variants equally.
- Where possible, clarify that PowerShell can be used on Linux/macOS as well, or suggest cross-platform alternatives.
- Ensure that OS-specific guidance and examples are presented in parallel (e.g., 'To create a Linux image, use ...; to create a Windows image, use ...') rather than defaulting to Windows.
- Consider adding a note about PowerShell Core's cross-platform support for Linux/macOS 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 synchronization in Azure and provides comprehensive Linux-specific guidance, including tools, commands, and configuration examples for ntpd, chronyd, systemd-timesyncd, and cloud-init. However, the introductory sections discuss Windows Server 2016 time sync improvements and reference Windows documentation before Linux-specific content, which may create a perception of Windows-first bias. All practical examples and instructions are Linux-centric, with only a minor PowerShell snippet for base64 encoding cloud-init (which is relevant for Azure ARM template usage, not VM configuration).
Recommendations
- Move or minimize Windows Server 2016 discussion in the introduction; focus on Linux host infrastructure and its impact on Linux VM time sync.
- Provide a Linux shell alternative for the PowerShell base64 encoding example (e.g., `base64 cloud-config.txt`).
- Ensure Linux-specific resources and links are presented before or alongside any Windows references.