Virtual Machines
2112
Total Pages
1865
Linux-Friendly Pages
247
Pages with Bias
11.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
818 issues found
Showing 651-675 of 818 flagged pages
Virtual Machines
Boot integrity monitoring overview
...virtual-machines/boot-integrity-monitoring-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation displays mild Windows bias. Windows examples and terminology (such as PowerShell and Windows-specific extension publishers) are presented before Linux equivalents in the template section. The PowerShell tab is included, but there is no Bash or Linux shell scripting equivalent. Troubleshooting and configuration steps use generic Azure portal and CLI instructions, but screenshots and error messages reference Windows extension names. Linux parity is present in the template section, but less emphasized elsewhere.
Recommendations
- Add a Bash or Linux shell scripting tab alongside PowerShell for command-line examples.
- Ensure Linux extension error messages and troubleshooting steps are equally represented, including screenshots and sample error outputs for Linux.
- Present Windows and Linux examples side-by-side or alternate their order to avoid Windows-first bias.
- Clarify when instructions or extension names differ between Windows and Linux, especially in troubleshooting sections.
Create Pull Request
Virtual Machines
Configure Event Hubs for VM watch
...ticles/virtual-machines/configure-eventhub-vm-watch.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. References to PowerShell and Windows tools are present before Linux equivalents, and instructions for accessing vmWatchSettings mention PowerShell before CLI or ARM templates. Examples for viewing logs are provided for both Linux and Windows, but guidance for examining events in Event Hubs focuses on the Azure portal, which is platform-agnostic but often more familiar to Windows users. No explicit Linux command-line examples (e.g., az CLI, bash) are provided for key tasks such as configuring or troubleshooting Event Hubs output.
Recommendations
- Provide Linux/macOS-specific command-line examples using Azure CLI and bash for configuring Event Hubs output.
- Ensure that instructions for accessing vmWatchSettings mention CLI and ARM templates before PowerShell, or present all options equally.
- Include troubleshooting steps using Linux-native tools (e.g., tail, grep) for log analysis.
- Add explicit guidance for Linux users on viewing Event Hubs data using CLI or SDKs, not just the Azure portal.
- Review screenshots and examples to ensure they are not Windows-centric.
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 Azure Portal, Azure CLI, PowerShell, and REST API. However, PowerShell examples are given equal prominence as CLI, despite PowerShell being primarily a Windows technology. There is no explicit mention of Linux/macOS-specific tools or shell environments (e.g., Bash), and PowerShell is presented as a main option rather than as a Windows-specific alternative. The ordering of examples sometimes places PowerShell before REST, and the CLI examples use generic variable syntax that is compatible with Bash, but this is not clarified. No Linux/macOS-specific guidance or troubleshooting is provided.
Recommendations
- Clearly label PowerShell examples as Windows-specific and recommend CLI for cross-platform use.
- Add explicit Bash shell examples where variable syntax or command differences exist.
- Provide notes or troubleshooting tips for Linux/macOS users, especially regarding environment setup.
- Consider reordering examples to present CLI (cross-platform) before PowerShell.
- Mention that Azure CLI is the recommended tool for Linux/macOS users.
Virtual Machines
Remove a virtual machine scale set association from a capacity reservation group
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/capacity-reservation-remove-virtual-machine-scale-set.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for API, Azure CLI, PowerShell, and Portal. PowerShell is featured as a first-class method alongside CLI, and PowerShell-specific commands are referenced and linked. While Azure CLI is cross-platform and examples are present, PowerShell is a Windows-centric tool and is given equal prominence. In some sections, PowerShell examples and links are provided before CLI equivalents. No Linux/macOS-specific shell examples (e.g., Bash scripts) are included, and there is no mention of Linux-specific considerations.
Recommendations
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Add Bash script examples for common Linux workflows, especially for automation.
- Reorder CLI examples before PowerShell to emphasize cross-platform support.
- Explicitly state PowerShell Core compatibility for non-Windows platforms if relevant.
- Add a note or section addressing Linux/macOS users and their preferred tools.
Virtual Machines
Convert a disk from LRS to ZRS
...ain/articles/virtual-machines/disks-migrate-lrs-zrs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation consistently presents Azure Portal and Azure PowerShell instructions before Azure CLI examples. PowerShell, a Windows-centric tool, is given equal prominence to Azure CLI, and all examples use Azure Portal (a graphical tool familiar to Windows users) first. There is no explicit mention of Linux/macOS-specific considerations, and no Bash or shell script examples are provided. However, Azure CLI is cross-platform and shown for all tasks, so Linux users are not blocked from completing any steps.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred by many Linux/macOS users.
- Add explicit notes or examples for Linux/macOS users, such as using Bash variables and shell scripting patterns.
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide links to installation instructions for non-Windows platforms.
- Consider including a section or tab for Bash scripting for advanced automation scenarios.
- Avoid referring to Windows-specific tools (such as PowerShell) as the default or primary method.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely neutral and platform-agnostic, focusing on VM size specifications and features. However, there is mild Windows bias in the 'Feature support' section, where the link for Nested Virtualization points only to the Windows/Hyper-V guide, and in the 'Bandwidth/Throughput testing' resource, which references NTTTCP—a Microsoft tool primarily associated with Windows. Additionally, Windows and Linux disk encryption support are mentioned together, but the Windows link appears after the Linux one.
Recommendations
- Provide equivalent Linux documentation or links for Nested Virtualization (e.g., KVM/QEMU guides for Linux VMs).
- Mention and link to Linux-native network throughput testing tools (such as iperf3) alongside NTTTCP.
- Ensure that any feature support or tooling references include both Linux and Windows options, or clarify platform applicability.
- Where possible, present Linux and Windows resources in parallel, rather than referencing Windows tools first or exclusively.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely platform-neutral, focusing on VM specifications and features. However, there is mild Windows bias in the 'Feature support' section, where nested virtualization is linked only to a Windows/Hyper-V guide, and in the 'Network' section, where bandwidth testing references NTTTCP—a Windows-centric tool—without mentioning Linux alternatives. Windows and Windows tools are mentioned before or instead of Linux equivalents in these cases.
Recommendations
- Include links or references to Linux/KVM nested virtualization documentation alongside the Windows/Hyper-V guide.
- Mention Linux-compatible bandwidth testing tools (e.g., iperf, netperf) in the networking section and provide relevant links.
- Where features are supported or unsupported for both Windows and Linux, list both platforms together or in alphabetical order to avoid perceived prioritization.
- Ensure that examples and tooling references are provided for both Windows and Linux where applicable.
Virtual Machines
Modify a capacity reservation in Azure
...ticles/virtual-machines/capacity-reservation-modify.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for API, Portal, CLI, and PowerShell for all major operations. PowerShell is featured as a first-class automation option alongside Azure CLI, but PowerShell is a Windows-centric tool, and its examples are presented with equal prominence to the cross-platform CLI. In several places, PowerShell commands are shown after CLI, but the documentation does not show any Linux-specific shell scripting or mention Linux-native tools. There is no explicit Windows-only bias, but the parity between CLI and PowerShell may create a subtle bias toward Windows users, especially since PowerShell is not pre-installed on most Linux distributions.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users, while PowerShell is more common on Windows.
- Add example shell scripts (bash) for Linux users where appropriate, especially for automation scenarios.
- Explicitly mention installation requirements for PowerShell on Linux/macOS if users wish to use those examples.
- Consider listing CLI examples before PowerShell in each tabbed section to reinforce cross-platform parity.
- Add a note that all CLI commands work identically on Linux, macOS, and Windows.
Virtual Machines
Increase performance of Premium SSDs and Standard SSD/HDDs
.../articles/virtual-machines/disks-enable-performance.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 steps, but the PowerShell examples are given equal prominence and detail as the CLI, despite PowerShell being primarily a Windows-centric tool. The prerequisites mention Azure PowerShell before Azure CLI, and the custom metadata ('devx-track-azurepowershell') suggests a PowerShell focus. There are no Linux-specific shell examples (e.g., bash-only, or Linux-native tools), and PowerShell is not natively available on most Linux distributions. However, the Azure CLI examples are fully cross-platform and shown first in each section, mitigating the bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Add a note that PowerShell is available for Linux, but CLI is more commonly used on Linux/macOS.
- Consider including bash-only or Linux-native shell examples for scripting tasks, especially for disk management.
- Remove or balance metadata and authoring cues that suggest PowerShell is the primary method.
- Explicitly state that all CLI examples work on Linux/macOS, and link to installation guides for those platforms.
Virtual Machines
Enable end-to-end encryption using encryption at host - Azure portal - managed disks
...-machines/disks-enable-host-based-encryption-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates mild Windows bias: PowerShell examples and links are presented before Azure CLI/Linux equivalents, and the 'Next steps' section links to a PowerShell-focused sample repository. While both Windows and Linux are marked as supported and CLI examples are provided, the ordering and external resources favor Windows users.
Recommendations
- Present Azure CLI (Linux/macOS-friendly) examples before or alongside PowerShell examples.
- Include links to Linux/macOS-focused sample repositories in the 'Next steps' section.
- Ensure parity in screenshots and walkthroughs for Linux/macOS environments where relevant.
- Explicitly mention cross-platform compatibility in all command-line instructions.
Virtual Machines
Chef extension for Azure VMs
...blob/main/articles/virtual-machines/extensions/chef.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides examples and instructions for both Linux and Windows platforms, but there is a subtle bias toward Windows. The publisher value uses 'Chef.Bootstrap.WindowsAzure', which is Windows-centric branding. The extension type for Linux ('LinuxChefClient') is mentioned after the Windows type ('ChefClient'), and the directory paths for extension logs are listed with Windows first in the troubleshooting section. However, the Azure CLI example is Linux-focused, and there is a clear effort to address Linux users.
Recommendations
- List Linux and Windows examples side by side or in parallel sections, rather than mentioning Windows first.
- Provide explicit Linux and Windows deployment examples in Azure CLI and ARM templates.
- Use neutral publisher naming or clarify that 'Chef.Bootstrap.WindowsAzure' applies to both platforms.
- Ensure troubleshooting sections alternate or start with Linux examples if the documentation is intended for both audiences.
- Add a Linux-specific troubleshooting section (e.g., common issues, permissions, SELinux notes) to match Windows parity.
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
Windows Tools
Summary
The documentation is focused on Linux, but several sections exhibit Windows bias. PowerShell deployment instructions and troubleshooting commands are presented before or alongside Azure CLI equivalents, even though Linux users are more likely to use Azure CLI or shell scripts. References to Windows-specific tools and patterns (such as PowerShell and ARM template caveats referencing Windows VM configuration) appear in places where Linux alternatives could be emphasized or presented first.
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 as the recommended approach for Linux.
- Remove or move Windows-specific notes (such as ARM template caveats referencing Windows VM configuration) to a dedicated Windows section.
- Add bash/shell script examples for common operations (such as settings file manipulation, troubleshooting, etc.) where appropriate.
- Ensure all troubleshooting and operational guidance is Linux-centric, with Windows alternatives in a separate section.
Virtual Machines
Azure Disk Encryption for Linux
...es/virtual-machines/extensions/azure-disk-enc-linux.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is focused on Azure Disk Encryption for Linux and generally maintains Linux-centric content. However, in the warning section, Windows tooling (PowerShell cmdlet Get-AzVMDiskEncryptionStatus) is mentioned before the cross-platform Azure CLI command (az vm encryption show) for checking encryption status. This subtly prioritizes Windows/PowerShell tooling and may cause friction for Linux/macOS users who are less likely to use PowerShell.
Recommendations
- List the Azure CLI command before the PowerShell cmdlet when describing how to check encryption status, as Azure CLI is cross-platform and more relevant to Linux/macOS users.
- Explicitly state that Azure CLI is recommended for Linux/macOS environments.
- Consider providing bash script examples or direct Linux shell commands where appropriate.
- Review troubleshooting and support sections to ensure no implicit prioritization of Windows tools.
Virtual Machines
Dedicated hosts include file
...es/virtual-machines/includes/dedicated-hosts-resize.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents three usage tabs: Portal, CLI, and PowerShell. The PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily a Windows tool. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell is presented as a main method for automation, which may bias Windows users. However, the CLI examples use the Azure CLI, which is cross-platform and suitable for Linux/macOS users.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows.
- Add explicit Bash shell examples or notes for Linux/macOS users, such as how to install and use Azure CLI on those platforms.
- Consider adding a note that PowerShell Core is available cross-platform, but most Linux/macOS users will prefer Azure CLI.
- If possible, provide example scripts for Linux automation (e.g., Bash) alongside PowerShell scripts.
Virtual Machines
Customer intent: "As an IT administrator managing virtual machines, I want to aggregate OS update statuses and availability states across my machines, so that I can efficiently monitor and ensure the health of my infrastructure."
...es/virtual-machines/includes/azure-virtual-machines.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each query. Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) is standard in Azure docs. However, the documentation does not provide any Linux/macOS-specific shell examples (e.g., Bash scripts, shell pipelines), nor does it mention Linux-native tools or patterns. In sections about OS update installation, Windows Server and Linux are treated separately, but the Windows example appears after the Linux one. There is a slight bias toward Windows tools (PowerShell) and the lack of Linux-specific command-line patterns.
Recommendations
- Add explicit Bash/shell examples for Linux/macOS users, especially for common tasks like parsing or post-processing query results.
- Clarify that Azure CLI is fully cross-platform and highlight usage on Linux/macOS, possibly with screenshots or terminal output.
- Where PowerShell is mentioned, consider also referencing Linux-native scripting approaches (e.g., jq, grep, awk) for processing output.
- For OS update queries, ensure parity in detail and placement between Windows and Linux sections.
- Add notes or links to Linux/macOS installation and usage guides for Azure CLI and PowerShell Core.
Virtual Machines
MSP Feature Configuration
...l-machines/metadata-security-protocol/configuration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page exhibits mild Windows bias. Windows is mentioned first in several places (e.g., 'automatic GPA installation (when true) or uninstallation (when false) on a Windows VM'), and the example VM names use 'GPAWinVM', which implies a Windows-centric example. The configuration and audit log locations are provided for both Linux and Windows, but Windows is often referenced first or exclusively in explanatory text. No PowerShell-heavy examples or missing Linux instructions are present, and Linux audit log paths are documented.
Recommendations
- Use neutral VM names in examples (e.g., 'GPAExampleVM' instead of 'GPAWinVM').
- When describing agent installation/uninstallation, clarify Linux behavior explicitly and avoid mentioning Windows first.
- Ensure that all configuration steps and examples are equally applicable to Linux and Windows, and highlight any OS-specific differences.
- Alternate the order of OS references in tables and explanations to avoid implicit prioritization.
- Add explicit notes about GPA installation/uninstallation on Linux VMs where relevant.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is primarily focused on Linux, but in the section about creating a Network Security Group (NSG) rule for Remote Desktop traffic, both Azure CLI and Azure PowerShell examples are provided. The PowerShell example is shown after the CLI, but PowerShell is a Windows-centric tool. There is also a reference to using SSH from Windows before mentioning Linux SSH key creation in the prerequisites and next steps. No Linux-specific firewall tools (like ufw or firewalld) are mentioned for opening port 3389, and the NSG rule creation references a Windows documentation link for portal instructions.
Recommendations
- Add examples for configuring Linux firewalls (e.g., ufw, firewalld) to open port 3389, alongside the Azure NSG rule.
- Reference Linux SSH documentation before Windows SSH documentation, or present both equally.
- Clarify that Azure PowerShell is cross-platform, but highlight CLI and Linux-native tools for Linux users.
- Provide links to Linux-native RDP clients and troubleshooting steps for those clients.
- Ensure that documentation links for portal instructions do not point to Windows-specific pages.
Virtual Machines
Copy VM restore points to another region
...achines/virtual-machines-copy-restore-points-how-to.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is largely platform-neutral in its API focus, but there is a subtle Windows bias in the ordering and detail of OS-specific configuration examples. Windows configuration details (e.g., unattend XML, WinRM, certificateStore) are described first and in greater depth than Linux equivalents. The only certificate store example is for Windows, and the 'windowsConfiguration' section is more elaborate than 'linuxConfiguration'.
Recommendations
- Provide Linux configuration examples with equal detail, such as sample SSH configuration, cloud-init customData, and Linux-specific disk or boot diagnostics options.
- Include certificate store examples for Linux (e.g., location of PEM files, integration with Linux keyrings).
- Alternate the order of OS-specific configuration sections, or present them side-by-side for parity.
- Clarify any platform-specific limitations or behaviors for both Windows and Linux VMs.
Virtual Machines
List, update, and delete resources
...in/articles/virtual-machines/update-image-resources.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all major tasks, but PowerShell is given equal prominence as CLI, despite being a Windows-centric tool. In some sections, PowerShell examples are present where Linux/macOS users would not benefit. The CLI examples are cross-platform, but PowerShell is not, and its inclusion may create confusion or friction for non-Windows users. No Linux-specific tools or shell examples (e.g., bash scripting) are provided, and PowerShell is presented as a primary alternative to CLI, which may imply Windows bias.
Recommendations
- Clearly indicate that PowerShell examples are intended for Windows users and that Azure CLI is cross-platform.
- Consider providing bash or shell script examples for Linux/macOS users where scripting is relevant.
- Where PowerShell is used, add notes or links for Linux/macOS users to install PowerShell Core if needed, or recommend CLI as the preferred cross-platform tool.
- If possible, reorder examples so CLI appears before PowerShell, emphasizing its cross-platform nature.
- Explicitly mention that all CLI commands work on Linux/macOS and Windows.
Virtual Machines
VM Snapshot extension using VM restore points
...ps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/virtual-machines-restore-points-vm-snapshot-extension.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation demonstrates mild Windows bias by referencing Windows-specific technologies (VSS) and mentioning Windows patterns before Linux equivalents. While both Windows and Linux are acknowledged, Windows tooling (VSS) is described in more detail, and troubleshooting links focus on Windows scenarios. Linux is mentioned as using pre-/postscripts, but no further guidance or troubleshooting is provided for Linux-specific issues.
Recommendations
- Provide equal detail for Linux restore point mechanisms, including common issues and troubleshooting steps.
- Include links or sections for Linux-specific troubleshooting, analogous to the VSS writer troubleshooting for Windows.
- Present Windows and Linux examples side-by-side or in parallel, rather than listing Windows first.
- Expand on how pre-/postscripts work for Linux, with examples and best practices.
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 operating system support for application consistency with Windows listed first, followed by Linux. However, both platforms are covered with appropriate details and limitations. No examples, tools, or instructions are given in this page, so there is no evidence of PowerShell-heavy bias, missing Linux examples, or exclusive mention of Windows tools.
Recommendations
- Consider listing Linux and Windows operating system support in parallel or alphabetically to avoid perceived prioritization.
- Ensure that referenced 'Next steps' links (CLI, Portal, PowerShell) provide parity in instructions and examples for both Windows and Linux environments.
- Explicitly mention that CLI instructions are cross-platform and highlight any platform-specific caveats if present.
Virtual Machines
Boot integrity monitoring overview
...virtual-machines/boot-integrity-monitoring-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. Windows examples and terminology (such as 'WindowsAttestation' publisher, PowerShell tab, and Windows error messages) are presented before or more prominently than Linux equivalents. The troubleshooting section references Windows-specific extension names and error messages, and PowerShell is given its own tab, while Linux CLI examples are not as detailed. However, Linux parity is maintained in the template section, and CLI instructions are generally OS-neutral.
Recommendations
- Ensure Linux and macOS examples are presented with equal prominence and detail as Windows examples.
- In troubleshooting sections, include Linux-specific error messages and extension names (e.g., 'LinuxAttestation') where relevant.
- Provide Bash or shell script examples alongside PowerShell, especially in sections where PowerShell is highlighted.
- Avoid using Windows extension names or terminology exclusively in generic error messages; clarify when errors apply to both platforms.
- Explicitly mention macOS support or limitations if applicable.
Virtual Machines
Availability options for Azure Virtual Machines
...cs/blob/main/articles/virtual-machines/availability.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page is generally cross-platform, but in the Load Balancer section, PowerShell is mentioned before CLI, and both are linked as quickstart options. This ordering may subtly favor Windows users, as PowerShell is primarily a Windows tool, though it is available cross-platform. No Linux-specific tools (such as Bash or shell scripts) are mentioned, and examples are not shown for Linux commands. The rest of the page is neutral and covers both Linux and Windows VMs equally.
Recommendations
- List CLI examples before PowerShell to avoid implicit Windows-first bias.
- Explicitly mention Bash or shell script options for Linux users where relevant.
- Provide example commands for both Linux (Bash/CLI) and Windows (PowerShell) in sections involving VM management or load balancing.
- Clarify that PowerShell is available cross-platform, but CLI is often preferred on Linux.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux coverage, but there is a subtle Windows bias: PowerShell is given its own section for enabling boot diagnostics, while Linux users must infer that the CLI section applies to them. Additionally, references to troubleshooting with the Serial Console link to a Windows-specific page, and PowerShell is mentioned before ARM templates, which are platform-neutral. No Linux-specific tools or examples are provided.
Recommendations
- Add explicit Bash or Linux shell examples for enabling boot diagnostics, alongside PowerShell.
- Clarify that Azure CLI instructions apply to both Windows and Linux users.
- Provide links to Linux-specific troubleshooting guides for Serial Console and boot diagnostics.
- Ensure that references to platform-specific tools (e.g., PowerShell) are balanced with Linux alternatives.
Virtual Machines
Create a capacity reservation in Azure
...ticles/virtual-machines/capacity-reservation-create.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell for all major operations. However, PowerShell is given equal prominence to CLI, despite being primarily a Windows tool, and PowerShell examples are detailed and referenced with links to specific cmdlets. There is a slight Windows bias in the inclusion and emphasis of PowerShell, which is not natively available on Linux/macOS (though it can be installed). The CLI examples are cross-platform, but PowerShell is often presented as a first-class option, which may create friction for Linux/macOS users. No Linux/macOS-specific tools or shell examples (e.g., Bash scripts) are provided, and PowerShell is mentioned before CLI in some sections.
Recommendations
- Clarify that Azure CLI is the recommended cross-platform tool for scripting and automation, and mention that PowerShell is primarily for Windows users (with installation instructions for Linux/macOS if referenced).
- Ensure CLI examples are shown before PowerShell in tabbed sections to reinforce CLI as the default for non-Windows platforms.
- Add Bash script equivalents for common operations, or provide notes for Linux/macOS users on how to adapt CLI commands in shell scripts.
- Explicitly state the cross-platform nature of Azure CLI and ARM templates, and provide links to installation guides for Linux/macOS.
- Consider reducing the prominence of PowerShell unless there are Windows-specific steps.