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 126-150 of 284 flagged pages
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 extensive Linux-specific guidance and examples. However, the introductory sections discuss Windows Server 2016 improvements and Windows time sync features before Linux-specific details, and Windows documentation is referenced multiple times. All configuration and command examples are Linux-centric, with only a minor PowerShell snippet shown for base64 encoding a cloud-init file (which is relevant for Azure ARM template usage, not time sync itself). There are no missing Linux examples or Windows-only tools presented for the main task.
Recommendations
- Move Windows Server 2016 discussion to a background or infrastructure section, clarifying its relevance to Linux VM time sync.
- Add a Linux shell example for base64 encoding cloud-init files (e.g., 'base64 cloud-config.txt') alongside the PowerShell snippet.
- Ensure Linux-specific links and resources are presented before or alongside Windows references.
- Clarify that Windows references are for context about Azure host infrastructure, not for user configuration.
Create Pull Request
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 separate example, and appears after CLI, but there is no evidence of exclusive Windows tools or patterns. The CLI examples are cross-platform, and REST API is platform-neutral. However, PowerShell is included as a distinct example, which may be seen as a minor Windows-first bias, since there is no equivalent Linux shell example (e.g., Bash scripting) provided. The CLI examples are suitable for Linux/macOS users.
Recommendations
- Clarify that Azure CLI examples are cross-platform and suitable for Linux/macOS users.
- Consider providing Bash shell scripting examples for Linux users, or explicitly state that PowerShell is optional and not required for Linux/macOS.
- Ensure that PowerShell examples are not presented as the primary or only scripting option.
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 and is presented immediately after the CLI example, which may subtly reinforce Windows/PowerShell as a primary option. There is no explicit Linux bias, but the PowerShell section is unnecessary for Linux users, and no mention is made of Bash or other Linux-native tools. The CLI example is cross-platform, but the documentation could clarify this for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Consider labeling the PowerShell section as 'Windows/PowerShell' and the CLI section as 'Linux/macOS/CLI' to clarify audience.
- Add a note that PowerShell Core is available on Linux/macOS, but Azure CLI is typically preferred in those environments.
- If possible, provide Bash or shell script examples for Linux users, or clarify that Azure CLI commands work natively in Bash.
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 operations (discover, run, check, remove extensions), but consistently presents PowerShell examples immediately after CLI and sometimes with more detail. There is no evidence of Windows-only tools or missing Linux examples, but PowerShell is not a native Linux tool and its prominence may create friction for Linux users. The documentation does not use Windows-specific tools or patterns, and all examples are Linux-appropriate. However, PowerShell is featured almost as prominently as CLI, which is more natural for Linux users.
Recommendations
- Prioritize Azure CLI examples before PowerShell throughout the documentation, as CLI is more native to Linux environments.
- Clearly indicate that PowerShell is optional and not required for Linux users.
- Consider grouping CLI and PowerShell examples under separate tabs or sections, with CLI as the default for Linux-focused docs.
- Add brief notes on how to install and use Azure CLI on Linux, and clarify that PowerShell is available but not necessary.
Virtual Machines
Support matrix for VM restore points
...n/articles/virtual-machines/concepts-restore-points.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows operating system support details before Linux, but provides parity in listing both OS types and their requirements. No Windows-specific tools, examples, or patterns are prioritized elsewhere. The 'Next steps' section references CLI, Portal, and PowerShell equally, without favoring Windows tools.
Recommendations
- Consider listing Linux operating system support before or alongside Windows to avoid 'windows_first' ordering bias.
- Ensure that future examples and walkthroughs (linked from 'Next steps') provide both Windows and Linux command-line instructions.
- Explicitly mention that CLI and PowerShell instructions are available for both platforms, if applicable.
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 and Azure PowerShell examples for creating instant access snapshots, but the PowerShell example is presented immediately after the CLI example and before the portal and ARM template examples. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, although it is available on Linux and macOS. There are no Linux-specific shell examples (e.g., Bash), and no explicit mention of Linux/macOS compatibility for PowerShell commands. The documentation does not reference Windows-only tools, but the ordering and emphasis may subtly favor Windows users.
Recommendations
- Explicitly note that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
- Consider providing Bash shell examples or clarifying that CLI commands are intended for Bash/zsh environments.
- Add a note that Azure PowerShell is available on Linux/macOS, or link to installation instructions for those platforms.
- Alternate the order of CLI and PowerShell examples to avoid implicit Windows-first bias.
- If possible, include sample scripts for Linux users (e.g., Bash) for common tasks.
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 commands are presented before Azure CLI equivalents, which may create friction for Linux users. However, Linux-specific instructions, troubleshooting, and examples are comprehensive and prioritized.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is more commonly used on Linux.
- Clearly indicate that PowerShell examples are primarily for users on Windows or those who prefer PowerShell, and provide equivalent Bash/CLI instructions for all tasks.
- Consider removing or de-emphasizing PowerShell examples unless they are necessary for cross-platform parity.
- Add Bash script examples where relevant, especially for troubleshooting or manual driver installation.
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, separate instructions for both Linux and Windows VM generalization. However, in the Windows section, PowerShell/Command Prompt examples are given, and the Windows steps include a PowerShell command to mark the VM as generalized, while the Linux section uses Azure CLI. The Windows section also appears after the Linux section, so 'windows_first' bias is minimal. Both OSes are covered, but Windows-specific tooling (PowerShell) is used for Windows, and Linux-specific tooling (waagent, SSH, Azure CLI) is used for Linux.
Recommendations
- Consider adding Azure CLI equivalents for Windows VM generalization steps, so Windows users can use CLI if preferred.
- Ensure parity in the depth of examples and explanations for both OSes.
- Mention that Azure CLI can be used for both Linux and Windows VMs to mark them as generalized, if applicable.
- If possible, provide cross-platform commands for marking VMs as generalized (e.g., Azure CLI for both).
Virtual Machines
HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs
...main/articles/virtual-machines/hbv3-series-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and provides information relevant to both Linux and Windows users. However, in the 'Software specifications' table, 'Recommended OS for Performance' lists 'Windows Server 2019+' without mentioning any Linux distributions, which may imply a preference for Windows. Additionally, Windows is mentioned first in some OS support lists, though Linux support is clearly stated elsewhere. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present.
Recommendations
- In the 'Recommended OS for Performance' row, include recommended Linux distributions (e.g., 'RHEL 8+, Ubuntu 20.04+, SLES 15 SP4+') if applicable, or clarify if Windows Server 2019+ is recommended only for Windows workloads.
- When listing supported OSes, alternate or group Linux and Windows examples to avoid the appearance of prioritizing Windows.
- If performance recommendations are genuinely Windows-specific, explicitly state so to avoid confusion for Linux users.
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 Linux, but deployment and troubleshooting sections present Azure PowerShell examples before Azure CLI, and some warnings are PowerShell-specific. While Azure CLI is covered, PowerShell is emphasized and shown first, which may create friction for Linux users who typically prefer CLI tools. No Windows-only tools or patterns are used, and all technical instructions are Linux-centric.
Recommendations
- Present Azure CLI examples before Azure PowerShell in deployment and troubleshooting sections, as CLI is more native to Linux environments.
- Add explicit notes clarifying that Azure PowerShell is optional and not required for Linux users.
- Highlight Linux-native troubleshooting tools (such as journalctl or systemd commands) for extension status, in addition to Azure CLI.
- Ensure all JSON and code snippets use Linux path conventions and shell syntax where appropriate.
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 the ordering and example emphasis. PowerShell examples are presented with Windows as the default, and Windows terminology (Sysprep) is mentioned before Linux equivalents. CLI and REST examples are neutral, but PowerShell sections use Windows as the primary example and Linux as a secondary note.
Recommendations
- Alternate the order of Linux and Windows examples in PowerShell and CLI sections, or provide parallel examples for both.
- Explicitly show Linux-focused PowerShell examples (e.g., using -OsType Linux) alongside Windows examples.
- Ensure that Linux terminology (waagent -deprovision) is mentioned equally with Windows terminology (Sysprep) in introductory sections.
- Consider starting example blocks with Linux scenarios, or at least alternating which OS is shown first.
- Add notes clarifying parity between Linux and Windows wherever relevant.
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 and uploading a Red Hat Enterprise Linux VHD for Azure using multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). While Linux-centric throughout, the structure and ordering of sections consistently place Hyper-V (a Windows-centric hypervisor) first, with detailed step-by-step instructions. Linux-native hypervisors (KVM, VMware, Kickstart) are covered in depth and parity, but their sections are always listed after Hyper-V. There are references to using Hyper-V Manager and Windows tools for disk conversion, but Linux alternatives (qemu-img, guestfish) are also provided. No critical Linux examples are missing, and Linux users can fully complete the task.
Recommendations
- Reorder the hypervisor sections so that Linux-native options (KVM, VMware, Kickstart) are presented before Hyper-V, or at least alternate the order to avoid implicit Windows primacy.
- Add a brief note at the top clarifying that all hypervisor options are equally supported and that users should select the section relevant to their environment.
- Where disk conversion is discussed, ensure Linux tools (qemu-img, guestfish) are mentioned alongside Windows tools, not only as secondary options.
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
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation covers both Linux and Windows VM image creation with Azure Image Builder, providing parity in most areas. However, there are several instances where Windows-specific tools (PowerShell, Windows commands) are mentioned first or exclusively, and PowerShell is used for checksum generation and other tasks, while Linux equivalents are sometimes only mentioned later or in passing. Windows examples and customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in more detail, and PowerShell commands are often shown before Azure CLI or Linux shell equivalents.
Recommendations
- Ensure Linux shell commands (e.g., for checksum generation) are always provided alongside PowerShell equivalents, and shown with equal prominence.
- Where PowerShell is referenced for validation or customization, provide clear Bash/shell alternatives for Linux users.
- In sections listing customizer types, avoid listing Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) before Linux equivalents (Shell), or alternate the order.
- For commands to register features or manage resources, show Azure CLI examples first or equally with PowerShell.
- Expand Linux-specific troubleshooting and guidance to match the detail provided for Windows (e.g., logs, error messages, customization advice).
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 Windows and Linux VM images, but there are signs of Windows bias. PowerShell examples are provided alongside Azure CLI, but PowerShell is a Windows-centric tool. In several places, Windows-related links and examples are listed before Linux equivalents (e.g., uploading VHDs, specialized image creation). References to Azure PowerShell are frequent and sometimes prioritized over CLI. However, Linux-specific information (such as waagent for generalization) is included, and Azure CLI examples are present, which mitigates the bias.
Recommendations
- Ensure Linux and Azure CLI examples are always provided alongside PowerShell, and shown first or equally.
- Where possible, use cross-platform tools (Azure CLI, REST API) as the primary example, with PowerShell as an alternative.
- Explicitly mention that Azure PowerShell is Windows-centric, and recommend Azure CLI for Linux/macOS users.
- Review all linked pages to ensure Linux parity in walkthroughs and examples.
- Add more Linux-specific troubleshooting tips and links where relevant.
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Arm Template Windows Only
Summary
The documentation covers both Windows and Linux VMs, but exhibits mild Windows bias in several areas. PowerShell examples are provided throughout, and the ARM template section only demonstrates Windows VM deployment. Windows-specific parameters (e.g., OSVersion) are prominent in the ARM template, and Windows images are used by default. In some sections, Windows terminology and tools (PowerShell, Windows image references) appear before or more prominently than Linux equivalents, despite the CLI examples using Ubuntu images.
Recommendations
- Add a Linux-focused ARM template example, or clarify how to modify the template for Linux VM deployment (e.g., show publisher/offer/sku for Ubuntu or other distributions).
- Balance PowerShell and CLI coverage by ensuring both are equally prominent and by mentioning Bash or shell scripting where relevant.
- In ARM template parameters, include both Windows and Linux image options, or add guidance for Linux users.
- Where Windows terminology appears first (e.g., administrator account password requirements, OSVersion), clarify applicability to Linux or provide Linux-specific guidance.
- Consider alternating CLI and PowerShell order, or explicitly state that both Windows and Linux are supported for all command-line examples.
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 mild Windows bias in example ordering and PowerShell usage. In the PowerShell section, Windows is shown first in the example, with Linux mentioned as an alternative. PowerShell is also presented as a primary scripting option, which is more native to Windows. However, CLI and REST examples are provided and are OS-neutral, and Linux-specific guidance is linked in the 'Before you begin' section.
Recommendations
- In PowerShell examples, show Linux as the primary example or provide parallel Linux and Windows examples.
- Explicitly state that PowerShell can be used on Linux/macOS, or recommend Azure CLI for cross-platform users.
- Ensure that Linux and Windows are treated equally in example ordering and explanations.
- Add notes or links about using PowerShell Core on Linux/macOS where PowerShell is referenced.
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 highlighted as a primary method alongside CLI, and its inclusion may create friction for Linux/macOS users, as PowerShell is traditionally Windows-centric (though now cross-platform). The CLI example is shown first, which is positive, but the PowerShell section is equally prominent and may imply parity between CLI and PowerShell usage, despite CLI being more native to Linux/macOS environments.
Recommendations
- Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
- Add a note that PowerShell is available cross-platform, but CLI is more commonly used on Linux/macOS.
- Consider providing Bash script examples or highlighting CLI usage for automation on Linux.
- Ensure that CLI instructions are comprehensive and cover all relevant use cases.
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
Missing Linux Example
Summary
The documentation provides both Azure CLI (bash-style) and Azure PowerShell examples for creating instant access snapshots, but does not include explicit Linux/macOS-specific instructions or examples (e.g., Bash shell, Python SDK, or REST API). PowerShell is presented as a primary scripting option alongside Azure CLI, and Windows-centric tools (PowerShell, Portal) are given equal or greater prominence. There are no Linux-specific troubleshooting tips or parity notes. The CLI examples use Bash syntax, but there is no explicit mention of Linux/macOS compatibility or alternative shells.
Recommendations
- Add explicit Bash shell examples and clarify that Azure CLI commands are cross-platform (Linux/macOS/Windows).
- Include REST API or Python SDK examples for snapshot creation and state monitoring, which are platform-neutral.
- Mention any OS-specific considerations (e.g., file path handling, authentication) for Linux/macOS users.
- Ensure that CLI examples are tested and work on Linux/macOS, and note any differences if present.
- Consider adding troubleshooting or tips for Linux environments (e.g., environment variable handling, az CLI installation).
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 extensive Linux-specific details. However, in deployment and troubleshooting sections, Azure PowerShell examples are given first and in greater detail, with CLI examples following. There are warnings and troubleshooting steps that reference PowerShell-specific issues, and PowerShell is used as the primary deployment method before CLI, which is more cross-platform. There are no missing Linux examples, and all file paths, certificate handling, and operational details are Linux-centric.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and native for Linux users.
- Add explicit notes clarifying that PowerShell is optional and not required for Linux users.
- Expand troubleshooting steps to include CLI commands and not just PowerShell.
- Where PowerShell-specific warnings are given, provide equivalent CLI guidance for Linux users.
- Consider removing or minimizing PowerShell deployment instructions, or move them to a separate section for Windows administrators.
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, separate 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 Linux equivalents in some sections. The Windows example for marking a VM as generalized uses PowerShell, while the Linux example uses Azure CLI, potentially causing friction for cross-platform users. Overall, Linux instructions are present and functional, but Windows receives slightly more attention and detail.
Recommendations
- Ensure Linux and Windows sections have parity in detail and troubleshooting guidance.
- Provide Azure CLI examples for Windows VM generalization, not just PowerShell.
- Consider presenting Linux and Windows instructions in parallel or with equal prominence.
- Add troubleshooting tips for Linux deprovisioning similar to those given for Windows Sysprep.
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell examples are always given alongside CLI and never omitted. However, PowerShell is featured equally and sometimes before CLI, despite the Linux focus. The documentation references Azure PowerShell as a primary tool for managing Linux VM extensions, which is more commonly used on Windows. There are no missing Linux examples, and all sample scripts and ARM templates are Linux-centric. The severity of bias is low, as Linux users can complete all tasks using CLI, ARM templates, or portal, but the prominence of PowerShell may cause minor confusion or friction.
Recommendations
- Feature Azure CLI examples before Azure PowerShell examples, as CLI is the cross-platform default for Linux users.
- Clarify that Azure PowerShell is optional and primarily for users who prefer it, not required for Linux VM management.
- Consider grouping CLI and PowerShell examples under clear tabs, with CLI as the default/first tab.
- Add explicit notes that Azure CLI is recommended for Linux/macOS environments.
- Review and minimize references to PowerShell unless necessary for parity.
Virtual Machines
NVIDIA GPU Driver Extension - Azure Linux VMs
...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is clearly focused on Linux VMs, with extensive Linux-specific instructions and examples. However, PowerShell examples are provided alongside Azure CLI and ARM template examples, and PowerShell is mentioned before Azure CLI in the deployment section. There are no missing Linux examples or Windows-only tools, but the ordering and inclusion of PowerShell (a Windows-centric tool) may create minor friction for Linux users.
Recommendations
- Move Azure CLI examples before PowerShell examples, as Azure CLI is more commonly used on Linux.
- Clarify that PowerShell examples are optional and primarily for users on Windows or cross-platform PowerShell Core.
- Consider providing Bash script examples for common deployment scenarios.
- Explicitly note that Azure CLI is the recommended tool for Linux users.
Virtual Machines
HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs
...main/articles/virtual-machines/hbv3-series-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is largely cross-platform and includes both Linux and Windows support. However, there is a subtle Windows-first bias: the 'Recommended OS for Performance' is listed as 'Windows Server 2019+' without a Linux equivalent, and the temporary storage section uses the term 'page file' (a Windows concept) without mentioning the Linux swap partition. While Linux tools (like lstopo) are shown, there are no Windows equivalents or instructions for Windows users to inspect NUMA topology, which could be a minor omission for parity.
Recommendations
- In the 'Recommended OS for Performance' row, also recommend a specific Linux distribution/version for optimal performance (e.g., RHEL 8.x, Ubuntu 20.04+).
- In the temporary storage section, clarify the equivalent Linux concept (e.g., swap partition) alongside 'page file'.
- If possible, provide Windows-native tooling or instructions (e.g., using 'coreinfo' or Windows System Information) for inspecting NUMA topology, or explicitly state that such tools are not available if that's the case.
- Ensure that examples and recommendations are balanced for both Linux and Windows, especially in sections where performance tuning or system inspection is discussed.
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 Reference
Powershell Example
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides Linux-centric guidance, commands, and examples. However, it references Windows Server 2016 improvements and links to Windows documentation in the introduction and conclusion. Additionally, a PowerShell example is provided for base64 encoding a cloud-init file, which is a Windows-centric tool, even though the rest of the guidance is Linux-focused.
Recommendations
- Move Windows references to a background section or footnote, clarifying their relevance to Linux VM time sync.
- Provide a Linux equivalent for the PowerShell base64 encoding example, such as using 'base64' or 'openssl' on Linux.
- Ensure that all examples and tooling instructions are available for Linux users, especially for tasks like preparing cloud-init files.
- Clarify that the PowerShell example is optional and provide context for users on non-Windows platforms.
Virtual Machines
Create a Gallery for Sharing Resources
.../blob/main/articles/virtual-machines/create-gallery.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides examples for creating an Azure Compute Gallery using the Azure Portal, Azure CLI, PowerShell, and REST API. While all major cross-platform tools are covered, the PowerShell example is given equal prominence alongside CLI and REST, and the ordering of examples sometimes places PowerShell before REST. However, the CLI examples (which are cross-platform) are present and complete. There is no evidence of exclusive Windows tooling or missing Linux/macOS examples, but PowerShell is included as a first-class option, which may be unnecessary for Linux/macOS users.
Recommendations
- Consider listing Azure CLI examples before PowerShell examples, as CLI is cross-platform and more relevant for Linux/macOS users.
- Explicitly note that PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Ensure that all CLI examples are as detailed as PowerShell examples.
- If possible, add Bash scripting examples for Linux users, or clarify that Azure CLI commands can be run in Bash.