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 776-800 of 815 flagged pages
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
Windows Tools
Summary
The documentation provides clear, detailed instructions for both Linux and Windows VM generalization, but the Windows section includes more prerequisites, registry edits, and PowerShell-specific commands. The Windows example for marking the VM as generalized uses Azure PowerShell, while the Linux example uses Azure CLI. The Windows section appears after the Linux section, but the Windows-specific tooling (Sysprep, registry, PowerShell) is emphasized without mentioning Linux equivalents or cross-platform alternatives for some steps.
Recommendations
- Ensure parity in tooling: For marking a VM as generalized, provide both Azure CLI and Azure PowerShell examples for both Linux and Windows VMs.
- Clarify cross-platform options: Where Windows uses PowerShell, note that Azure CLI can be used on Windows as well, and show CLI syntax.
- Balance prerequisites: If possible, add more detail to Linux prerequisites, such as common pitfalls or distro-specific notes, to match the depth of the Windows section.
- Order examples consistently: Consider alternating the order of Linux and Windows examples or grouping cross-platform steps together.
- Reference cross-platform documentation: Link to Azure CLI and PowerShell docs for both OSes in the 'Related content' section.
Create Pull Request
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 sync in Azure and provides Linux-specific guidance and examples. However, the introduction and overview sections discuss Windows Server 2016 time sync improvements and Windows infrastructure before describing Linux mechanisms. All technical instructions, examples, and tools are Linux-centric, with no PowerShell or Windows-only commands given for time sync configuration. The only Windows-related content is background context and links to Windows documentation, which may be unnecessary for Linux users.
Recommendations
- Move Windows Server 2016 time sync background to a separate 'Azure infrastructure' or 'Background' section, or condense it to a brief note if relevant.
- Begin the page with Linux-specific time sync context and configuration options, reserving Windows infrastructure details for later or as a sidebar.
- Clarify that Windows documentation links are for background only and not required for Linux VM configuration.
- Ensure all examples and instructions remain Linux-focused, as currently provided.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is focused on Linux, as indicated by the title and content. However, in several sections, Windows-oriented tools and patterns (notably Azure PowerShell) are presented before Linux-native equivalents (Azure CLI). PowerShell deployment instructions and troubleshooting commands are shown first, even though Linux users are more likely to use Azure CLI. There are also warnings about PowerShell-specific issues, which may not be relevant for most Linux users. All configuration and operational details are Linux-centric, and no critical functionality is missing for Linux users.
Recommendations
- Present Azure CLI examples before PowerShell examples in all deployment and troubleshooting sections.
- Clearly mark PowerShell instructions as primarily for Windows users, and Azure CLI for Linux/macOS users.
- Add a short note at the start of deployment sections indicating that Azure CLI is recommended for Linux users.
- Move PowerShell-specific warnings to a dedicated troubleshooting subsection for Windows users.
- Review all example ordering to ensure Linux-first presentation.
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux and Windows guidance, but in several sections, Windows/PowerShell examples and terminology are presented before Linux equivalents. The PowerShell tab examples default to Windows, while the CLI tab defaults to Linux. There is a slight tendency to mention Windows/PowerShell first or more prominently, but Linux parity is generally maintained through CLI and REST examples.
Recommendations
- Ensure that Linux and Windows examples are presented with equal prominence and order in all code sample tabs (e.g., alternate which OS is shown first, or provide both in parallel).
- In PowerShell sections, explicitly show both Linux and Windows examples, or clarify that PowerShell can be used for Linux images as well.
- Where OS-specific preparation steps are referenced, ensure links and instructions for both Linux and Windows are equally visible and accessible.
- Review all examples to confirm that Linux users are not required to infer steps from Windows-centric instructions.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and PowerShell examples for checking vCPU quotas, but 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 inclusion of PowerShell may imply a Windows-centric workflow. No Linux-specific shell examples (e.g., Bash scripting) are provided, though the CLI is cross-platform.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows equally.
- Explicitly mention that PowerShell is primarily for Windows users, while CLI is recommended for Linux/macOS.
- Consider adding a short Bash script example for Linux users, or a note about using CLI in Bash/zsh.
- Reiterate cross-platform compatibility in the introduction to reduce perceived Windows bias.
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 provides examples and instructions for both Linux and Windows VMs throughout, including CLI, portal, template, and PowerShell methods. However, in several sections, Windows/PowerShell examples are presented first or in more detail, and PowerShell examples are exclusively for Windows VMs, with no Linux PowerShell equivalents. Some PowerShell snippets default to Windows images and configurations, while Linux examples are primarily shown in CLI and template sections.
Recommendations
- Ensure parity in PowerShell examples by including Linux VM deployment snippets where possible, or clearly state PowerShell is Windows-only if that's the case.
- Alternate the order of Windows and Linux examples so Linux is sometimes shown first, or group examples by OS for clarity.
- In PowerShell sections, explicitly mention that Linux VMs should be deployed using CLI or ARM templates if PowerShell support is limited.
- Add clarifying notes where a method (e.g., PowerShell) is Windows-specific, to avoid confusion for Linux users.
Virtual Machines
Enable Trusted launch on existing Gen2 VMs
...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides parity for both Linux and Windows VMs, explicitly stating applicability to both. However, there is a mild Windows bias in the ordering and tooling: PowerShell examples are included and shown before Linux-native alternatives, and some steps (such as VM deallocation in the ARM template section) use PowerShell syntax exclusively, even though Linux users would use Bash or Azure CLI. The verification step mentions RDP (Windows) before SSH (Linux) throughout. All CLI examples use Azure CLI, which is cross-platform, but PowerShell is given equal prominence, which may be less relevant for Linux/macOS users.
Recommendations
- Where PowerShell is used for generic Azure operations (e.g., deallocating VMs), provide equivalent Azure CLI or Bash examples, especially in sections like ARM template deployment.
- When listing verification steps, alternate or parallelize RDP/SSH references, or mention SSH first in Linux-focused contexts.
- Consider clarifying that PowerShell examples are primarily for Windows users, and recommend Azure CLI/Bash for Linux/macOS users.
- Ensure screenshots and UI references are not Windows-centric if possible.
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, but PowerShell (a Windows-centric tool) is given its own section and detailed example. The CLI example uses Ubuntu as the image, showing Linux applicability, but the PowerShell section appears before ARM template automation and is presented as a primary method. There is a slight Windows-first ordering in the examples and tool references, but Linux users can fully complete the tasks using CLI, ARM templates, and the portal.
Recommendations
- Add explicit Bash or shell scripting examples for Linux users, especially for automation scenarios.
- Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and highlight this in the CLI section.
- Consider reordering sections so that cross-platform tools (CLI, ARM templates) appear before Windows-specific tools (PowerShell).
- Add a note in the PowerShell section indicating its Windows-centric nature and suggest CLI 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 detailed, Linux-specific guidance and examples. However, the introductory section and overview spend several paragraphs describing Windows Server 2016 time sync improvements and Windows infrastructure before discussing Linux-specific mechanisms. All technical instructions, examples, and configuration steps are Linux-centric, with no PowerShell or Windows tool bias in the practical guidance.
Recommendations
- Move the Windows Server 2016 time sync discussion to a background or reference section, or summarize it more briefly before focusing on Linux-specific details.
- Begin the page with Linux VM time sync concepts and Azure-specific mechanisms, referencing Windows infrastructure only as necessary for context.
- Ensure that Linux instructions and examples are always presented first and most prominently on Linux-focused documentation pages.
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 generally Linux-focused, as expected for the Key Vault VM Extension for Linux. However, there are several instances where Windows-centric tools and patterns (notably Azure PowerShell) are presented prominently or before Linux-native alternatives. PowerShell deployment instructions are detailed and appear before Azure CLI examples, and troubleshooting guidance references Azure PowerShell before Azure CLI. There is also a reference to a Windows VM access policy guide in the template deployment section, which may confuse Linux users.
Recommendations
- Present Azure CLI examples before Azure PowerShell, as CLI is cross-platform and native to Linux/macOS.
- Clarify that Azure PowerShell is optional and primarily for Windows users; highlight CLI as the recommended approach for Linux.
- In troubleshooting sections, show Azure CLI commands first, and add Bash scripting examples where appropriate.
- Remove or clarify references to Windows-specific documentation (e.g., access policy guides for Windows VMs) and link to Linux-relevant guides.
- Add explicit notes about tool compatibility (e.g., Azure PowerShell on Linux) if PowerShell instructions are retained.
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 despite PowerShell being primarily a Windows tool. The CLI example (cross-platform) is shown first, which is positive, but the inclusion of PowerShell may create a slight Windows-centric impression. No Linux-specific tools or shell examples are provided, but the CLI is sufficient for Linux/macOS users.
Recommendations
- Clarify that Azure CLI works on Windows, Linux, and macOS.
- Consider adding a brief Bash shell example for parsing CLI output, if relevant.
- Explicitly state that PowerShell is primarily for Windows users, and CLI is recommended for cross-platform usage.
- Ensure that future documentation does not assume PowerShell as the default for automation unless the audience is Windows-focused.
Virtual Machines
Enable Trusted launch on existing Gen2 VMs
...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides parity for both Linux and Windows VMs, explicitly stating applicability to both. However, there is a mild Windows bias in the ordering and example tooling: PowerShell examples are given alongside CLI and ARM template, but PowerShell is a Windows-centric tool and is presented before Linux-native alternatives. Additionally, in the portal instructions, RDP (Windows) is mentioned before SSH (Linux) when verifying VM access. There are no missing Linux examples, and Linux-specific validation (SBInfo tool) is called out in best practices.
Recommendations
- Present SSH (Linux) and RDP (Windows) access instructions in parallel or with equal prominence.
- Clarify that PowerShell can be used cross-platform, or provide Bash scripting examples for Linux users where appropriate.
- Consider listing CLI and template methods before PowerShell, as these are more platform-neutral.
- Continue to highlight Linux-specific validation steps, as done with SBInfo.
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 detail, despite PowerShell being primarily a Windows tool. The CLI example is shown first, which is positive, but the presence of a dedicated PowerShell tab and example may signal a slight Windows bias, especially since Linux users are less likely to use PowerShell.
Recommendations
- Clarify that PowerShell is primarily for Windows users, and recommend Azure CLI for cross-platform usage.
- Add a note that Azure CLI works natively on Linux/macOS, while PowerShell requires installation and configuration on those platforms.
- Consider including Bash or shell scripting examples for Linux users, if relevant.
- Explicitly state platform compatibility for each tool in the documentation.
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
While the documentation is focused on a Linux-specific Azure VM extension, it provides both Azure PowerShell and Azure CLI deployment instructions. However, PowerShell examples and troubleshooting commands are presented before CLI equivalents, and PowerShell-specific warnings are included. This ordering and emphasis may create friction for Linux users, who are more likely to use Azure CLI or native Linux tools.
Recommendations
- Present Azure CLI examples before PowerShell examples in all sections, as CLI is more commonly used on Linux.
- Add explicit notes clarifying that PowerShell is optional and primarily for users on Windows or those who prefer it.
- Where troubleshooting commands are shown, list Azure CLI commands first and ensure parity in troubleshooting guidance.
- Consider removing PowerShell-specific warnings from the main flow, or move them to a dedicated section for Windows users.
- Highlight Linux-native workflows and tools (e.g., bash scripting, systemd integration) where 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 time synchronization for Linux VMs in Azure and provides comprehensive Linux-specific guidance and examples. However, the introduction and overview sections discuss Windows Server 2016 time sync improvements and link to Windows documentation before fully addressing Linux-specific mechanisms. All configuration, troubleshooting, and example commands are Linux-centric, with only a single PowerShell snippet shown for base64 encoding cloud-init data (which is relevant for Azure ARM template usage, not time sync itself). No Linux examples are missing, and no Windows tools are recommended for Linux VM management.
Recommendations
- Move or minimize Windows Server 2016 time sync discussion to a background or context section, making it clear that the rest of the page is Linux-focused.
- Add a brief note explaining why Windows time sync improvements are relevant to Linux VM users (e.g., because Azure hosts run Windows Server and this affects host time accuracy).
- Consider providing a Linux shell command alternative for base64 encoding cloud-init data, since the PowerShell example may not be directly usable by Linux/macOS users.
- Ensure that all actionable steps and examples remain Linux-centric and that any Windows references are clearly contextual/background.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit Linux shell (bash) example. The CLI example uses an Ubuntu image, but does not show Linux-specific shell usage or mention Linux tooling. The PowerShell section is detailed and uses Windows-centric SDK objects, while Linux users are expected to use the CLI or ARM templates without further guidance. The order of presentation (CLI, then PowerShell) is neutral, but the lack of explicit Linux shell examples and the presence of detailed PowerShell instructions indicate a mild Windows bias.
Recommendations
- Add explicit bash shell examples for Linux/macOS users, showing how to use az vm create and az vm list-skus in a Linux terminal.
- Clarify that Azure CLI commands work on all platforms and provide notes or examples for Linux/macOS environments.
- Reduce reliance on PowerShell SDK object manipulation, or provide equivalent scripting examples for Linux (e.g., using Azure CLI with jq or other Linux tools).
- Consider presenting CLI and ARM template examples before PowerShell, or grouping them by platform.
Virtual Machines
Enable Trusted launch on existing Gen2 VMs
...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides parity for both Linux and Windows VMs in terms of feature applicability and CLI/PowerShell/Portal/ARM template instructions. However, there is a mild Windows bias: PowerShell examples are given equal prominence to Azure CLI, and PowerShell is a Windows-centric tool. In some sections, RDP (Windows) is mentioned before SSH (Linux) when verifying VM access. Additionally, the template deployment steps use PowerShell for ARM template deployment, without mentioning Bash or cross-platform alternatives. The documentation does mention Linux-specific validation (SBInfo tool), but overall, Windows tools and patterns are slightly prioritized.
Recommendations
- In ARM template deployment sections, provide Bash/az CLI examples for deploying templates, not just PowerShell.
- When listing access methods, alternate or list SSH (Linux) before RDP (Windows) in some places.
- Explicitly mention that all CLI and template steps work on Linux/macOS, and provide sample commands for Bash where PowerShell is shown.
- Clarify that Azure CLI is cross-platform and recommend it as the default 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 page is focused on Linux VM time sync in Azure and provides comprehensive Linux-specific guidance. However, the introductory section discusses Windows Server 2016 time sync improvements and links to Windows documentation before delving into Linux-specific mechanisms. No Windows-only tools or examples are given, and all configuration and troubleshooting steps are Linux-centric.
Recommendations
- Move the Windows Server 2016 time sync discussion to a background or infrastructure section, making it clear it's context for Azure hosts, not actionable for Linux VM admins.
- Begin the page with Linux-specific time sync concepts and configuration options.
- Ensure that 'Next steps' and reference links prioritize Linux resources over Windows ones, unless specifically relevant to Azure host infrastructure.
Virtual Machines
Enable Trusted launch on existing Gen2 VMs
...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides parity for both Linux and Windows VMs, explicitly stating applicability to both. However, there is a mild Windows bias in the ordering and tooling: PowerShell examples are given equal prominence as CLI, and in some sections (e.g., ARM template deployment and VM deallocation), PowerShell is used as the default scripting language, which is more native to Windows. Additionally, in step-by-step instructions, RDP (Windows) is mentioned before SSH (Linux), and screenshots are Windows-centric. There are no missing Linux examples, and Linux-specific considerations (such as Secure Boot validation with SBInfo) are included.
Recommendations
- Where scripting is required (e.g., deallocation, template deployment), provide both PowerShell and Bash/Azure CLI examples, or clarify that PowerShell can be used cross-platform.
- Alternate the order of RDP/SSH mentions, or mention SSH first when discussing Linux VMs.
- Include screenshots from both Windows and Linux VM contexts, or use more generic images.
- Explicitly state that PowerShell can be used on Linux/macOS, or recommend Bash/CLI alternatives for Linux users.
- Where possible, clarify that all steps apply equally to Linux and Windows VMs, and highlight any OS-specific caveats.
Virtual Machines
Enable Trusted launch on existing Gen2 VMs
...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides parity for both Linux and Windows VMs when enabling Trusted launch, with clear notes and instructions applicable to both platforms. However, there is a mild Windows bias in the ordering and example tooling: PowerShell examples are shown alongside CLI and template methods, and PowerShell is referenced for ARM template deployment and VM deallocation, which is more common on Windows. Additionally, in several places, RDP (Windows) is mentioned before SSH (Linux) when verifying VM access.
Recommendations
- Where PowerShell is used for generic Azure VM operations (deallocation, deployment), provide equivalent Bash or Azure CLI examples for Linux/macOS users.
- When listing access methods (RDP/SSH), alternate or list SSH first in Linux-specific contexts.
- Clarify that PowerShell commands can be run cross-platform (Windows, Linux, macOS) if true, or provide Bash/CLI alternatives.
- Consider including Bash scripts for ARM template deployment and VM deallocation to improve Linux parity.
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
Powershell Heavy
Summary
The documentation provides examples for creating an Azure Compute Gallery using the Portal, Azure CLI, PowerShell, and REST API. While the CLI and REST examples are cross-platform, PowerShell is Windows-centric and is presented as a primary method alongside CLI and Portal. The PowerShell example is given equal prominence to CLI, but there is no mention of Linux/macOS equivalents for scripting (e.g., Bash), and PowerShell is not explicitly marked as Windows-only. Additionally, the ordering of examples sometimes places PowerShell before REST, which may subtly reinforce Windows-centric workflows.
Recommendations
- Clearly indicate that PowerShell examples are intended for Windows users, and suggest CLI or REST for Linux/macOS users.
- Consider providing Bash script examples for Linux/macOS users where appropriate, or clarify that Azure CLI is the recommended cross-platform tool.
- Reorder example tabs so that CLI (cross-platform) appears before PowerShell, or group Windows-specific tooling separately.
- Add a note at the start of the examples section explaining which tools are cross-platform and which are Windows-specific.
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 time synchronization for Linux VMs in Azure and provides comprehensive Linux-specific guidance and examples. However, the introduction and overview sections discuss Windows Server 2016 time sync improvements and Windows Time Service before explaining Linux mechanisms. All technical instructions, configuration steps, and examples are Linux-centric, with only one minor PowerShell snippet shown for base64 encoding a cloud-init file (which is an Azure ARM template pattern, not a time sync operation). No Windows tools or PowerShell-heavy bias is present in the core guidance.
Recommendations
- Move or condense the Windows Server 2016 time sync discussion to a background or context section, making it clear that the focus is on Linux VM configuration.
- Consider providing a Linux-native command for base64 encoding the cloud-init file (e.g., `base64 cloud-config.txt`) alongside the PowerShell example for ARM template users on Linux/macOS.
- Ensure that links and references in the 'Next steps' section prioritize Linux resources over Windows ones, or clearly separate them.
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 generally Linux-focused, as expected for the Azure Key Vault VM Extension for Linux. However, there are several instances where Windows-oriented tools (PowerShell) are presented before or alongside Linux-native alternatives, and PowerShell deployment examples are given equal or greater prominence than Azure CLI (which is more common on Linux). The troubleshooting section also lists PowerShell before CLI. There are no missing Linux examples, and all technical details are Linux-specific.
Recommendations
- Present Azure CLI examples before PowerShell examples in all deployment and troubleshooting sections, as CLI is more native to Linux environments.
- Explicitly note that PowerShell examples are optional for Linux users and primarily for those who prefer PowerShell cross-platform.
- Add brief instructions for running Azure CLI commands on Linux (e.g., bash syntax, file path conventions) to reinforce Linux parity.
- In troubleshooting, list CLI commands first and clarify that PowerShell is available for users who have it installed on Linux.
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 detail as the CLI example, despite PowerShell being primarily a Windows tool. The CLI example is suitable for Linux/macOS, but PowerShell is listed as a main tab, which may imply parity or preference for Windows users. There is no explicit Linux/macOS bias, but the presence and prominence of PowerShell may create minor friction for non-Windows users.
Recommendations
- Clarify that PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Consider listing the CLI example first, as it is cross-platform.
- Add a note explaining platform compatibility for each tool.
- If possible, provide Bash or shell script examples for Linux users, or clarify that Azure CLI is the recommended approach for Linux/macOS.
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 time synchronization for Linux VMs in Azure and provides comprehensive Linux-specific guidance, examples, and tooling. However, the introductory section discusses Windows Server 2016 time sync improvements and links to Windows documentation before delving into Linux-specific content. No PowerShell or Windows-only tools are used in the main configuration or troubleshooting sections, except for a single PowerShell example for base64 encoding cloud-init (which is relevant for Azure ARM templates, but could be supplemented with Linux alternatives). All configuration and troubleshooting steps are Linux-centric.
Recommendations
- Move or minimize the Windows Server 2016 time sync discussion in the introduction, or clarify its relevance to Linux VMs (e.g., as the underlying Azure host).
- Provide a Linux shell alternative for the PowerShell base64 encoding example (e.g., `base64 ./cloud-config.txt`).
- Ensure that Linux documentation links are presented before or alongside Windows links in the 'Next steps' section.
- Add a brief note explaining why Windows time sync is mentioned (i.e., Azure hosts run Windows Server 2016, which impacts Linux VM time sync).