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 226-250 of 284 flagged pages
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, PowerShell is presented as a primary option alongside CLI, despite PowerShell being more commonly used on Windows. The CLI example is shown first, which is positive, but the PowerShell section is equally prominent and detailed. There are no Linux-specific tools or shell examples (e.g., Bash scripting), and PowerShell is not flagged as Windows-only, which could cause confusion for Linux/macOS users who may not have PowerShell installed.
Recommendations
- Clarify that PowerShell examples are primarily for Windows users, and note that PowerShell Core is available cross-platform but may require installation.
- Add Bash shell scripting examples or note that Azure CLI is the recommended cross-platform tool.
- Explicitly state that Azure CLI works natively on Linux/macOS and is the preferred method for non-Windows environments.
- Consider adding a short section or note about PowerShell Core availability on Linux/macOS, with installation links.
Create Pull Request
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux coverage for Azure Compute Gallery, but there are several signs of Windows bias. PowerShell examples and references appear frequently and often before CLI equivalents. Windows-specific tools (e.g., Sysprep) are mentioned before Linux equivalents (waagent). Some links and examples reference Windows paths or documentation first. However, Linux is supported and referenced throughout, and most tasks can be completed by Linux/macOS users.
Recommendations
- Ensure that CLI and PowerShell examples are presented side-by-side or with equal prominence, rather than PowerShell first.
- Where Windows tools (e.g., Sysprep) are mentioned, ensure Linux equivalents (e.g., waagent) are given equal detail and placement.
- Review linked documentation to ensure Linux examples are as comprehensive as Windows examples.
- Consider adding Bash or cross-platform scripting examples where appropriate.
- Avoid referencing Windows documentation or tools first unless the feature is Windows-only.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for VM vCore customization, but the PowerShell section is presented immediately after the CLI section and is detailed, potentially implying Windows as a primary platform. The CLI example uses Ubuntu as the image, but there are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is emphasized as a separate section. The documentation does not mention Linux-specific tools or patterns, nor does it provide parity for Linux/macOS users in terms of native shell scripting.
Recommendations
- Add Bash shell examples for Linux/macOS users, especially for commands that can be run outside Azure CLI (e.g., using az commands in Bash scripts).
- Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Consider mentioning that PowerShell Core is available on Linux/macOS, but provide Bash examples as the default for non-Windows users.
- Ensure that examples and instructions are not presented in a Windows-first order; alternate or combine CLI and PowerShell sections, or explicitly state platform applicability.
Virtual Machines
Enable Trusted launch on existing Gen2 VMs
...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity for both Linux and Windows VMs, with clear indications that Trusted launch applies to both. However, there is a mild Windows bias in the tooling examples: PowerShell is given its own section and is used for ARM template deployment and VM deallocation, while Linux-native tools (such as Bash or shell scripting) are not referenced for these tasks. Additionally, PowerShell examples are shown alongside CLI and portal, but the PowerShell section is not explicitly labeled as Windows-only, despite PowerShell Core being cross-platform. In some cases, PowerShell is used for tasks where Azure CLI or Bash could be equally applicable, and PowerShell is referenced first for ARM template deployment. The documentation does mention SSH for Linux and RDP for Windows, and includes a Linux-specific best practice (SBInfo tool), but overall, Windows tooling is slightly favored.
Recommendations
- Add explicit Bash/shell scripting examples for ARM template deployment and VM deallocation/start, especially for Linux/macOS users.
- Clarify that PowerShell examples are compatible with PowerShell Core on Linux/macOS, or provide alternative Bash/CLI commands where possible.
- Ensure that CLI and Bash examples are presented before or alongside PowerShell, rather than PowerShell being the default for template deployment.
- Where PowerShell is used, note its cross-platform support, or link to documentation for using PowerShell on Linux/macOS.
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, with clear indications that Trusted launch applies to both. However, there is a mild Windows bias in the ordering and tooling: PowerShell examples are provided and referenced frequently, and PowerShell commands are used for ARM template deployment and VM deallocation, even though Linux users would typically use Bash or Azure CLI. In several sections, Windows-centric tools (PowerShell, RDP) are mentioned before their Linux equivalents (CLI, SSH), and PowerShell is used for template deployment without an explicit Bash alternative.
Recommendations
- Provide Bash shell equivalents for all PowerShell commands, especially for ARM template deployment and VM deallocation/start.
- Where possible, show CLI/Bash examples before or alongside PowerShell, or clarify which commands are cross-platform.
- Explicitly state that Azure CLI commands can be run from Bash on Linux/macOS, and provide sample Bash usage for template deployment.
- Ensure that references to remote access methods (RDP/SSH) are presented with Linux/SSH first or equally.
- Add a note clarifying that PowerShell is available cross-platform, but Bash/CLI is native to Linux/macOS.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides configuration instructions for VM vCore Customization using the Azure portal, Azure CLI, PowerShell, and ARM templates. While the CLI and ARM template examples are cross-platform, the PowerShell section is Windows-specific and is presented before any Linux/macOS shell alternatives (such as Bash or shell scripting). The CLI example uses Ubuntu as the image, but the PowerShell example is given equal prominence, which may create minor friction for Linux/macOS users. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is referenced as a primary automation tool, which is more common on Windows.
Recommendations
- Add Bash or shell script examples for Linux/macOS users alongside PowerShell, especially for automation scenarios.
- Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows.
- Consider reordering examples to present CLI and ARM template options before PowerShell, or group platform-specific tools clearly.
- Clarify in the PowerShell section that it is intended for Windows users, and suggest alternatives 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. However, the introductory section discusses Windows Server 2016 time sync improvements and Windows host algorithms before explaining Linux mechanisms, which may create a perception of 'windows_first' bias. All configuration examples, tools, and troubleshooting steps are Linux-centric, with no PowerShell or Windows-specific commands or tools used for Linux VM configuration.
Recommendations
- Move the Windows Server 2016 time sync discussion to a background or infrastructure section, clarifying its relevance to Linux VMs.
- Begin the overview with Linux-specific time sync mechanisms and Azure's support for Linux time sync, then mention host infrastructure details as context.
- Add a brief statement clarifying that while Azure hosts run Windows Server, all configuration and management for Linux VMs is performed using Linux-native tools.
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 examples are included and presented as a primary method alongside CLI, and the ordering of examples often places PowerShell before REST. There is a mild 'Windows-first' bias in the inclusion and ordering of PowerShell examples, which are only relevant to Windows users. However, Linux/macOS users are not blocked from completing any tasks, as CLI and REST examples are present and fully functional.
Recommendations
- Clearly indicate that PowerShell examples are Windows-only and suggest CLI/REST for Linux/macOS users.
- Consider placing CLI examples before PowerShell examples to emphasize cross-platform support.
- Add a note at the top of the example sections clarifying platform compatibility for each method.
- Ensure parity in example detail and completeness between CLI and PowerShell sections.
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 places, Windows/PowerShell examples are presented before Linux/CLI equivalents. The PowerShell tab examples use Windows as the default, while the CLI tab uses Linux. The introductory OS-specific guidance lists Linux first, but the PowerShell section defaults to Windows, and PowerShell is inherently a Windows-centric tool (though available on Linux, it's less common for Linux users). No critical Linux examples or tools are missing, but the ordering and example defaults show a mild Windows bias.
Recommendations
- Alternate the order of CLI and PowerShell examples so Linux/CLI is not always second.
- In PowerShell examples, default to Linux where appropriate or provide both Linux and Windows variants.
- Explicitly state that PowerShell commands can be run on Linux, but CLI is more common for Linux workflows.
- Ensure parity in example depth and clarity between CLI and PowerShell sections.
- Consider adding Bash script examples for Linux users where complex workflows are shown.
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
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for key tasks, but PowerShell examples are often shown alongside or before CLI, and some references (such as finding Marketplace images) link to Windows/PowerShell-specific pages first. In some cases, Linux equivalents are mentioned but not given equal prominence or example coverage. There are also references to Windows tools (Sysprep) before Linux equivalents (waagent), and some links for uploading VHDs are split into Windows and Linux, but the Windows link appears first. Overall, while the documentation is not exclusively Windows-focused, there is a mild bias toward Windows/PowerShell in example ordering and reference links.
Recommendations
- Ensure Azure CLI examples are presented before or alongside PowerShell, as CLI is cross-platform.
- When referencing external guides (e.g., uploading VHDs), present Linux and Windows links together or in parallel, not with Windows first.
- Provide explicit Linux-focused examples or references where only Windows/PowerShell examples are given.
- When mentioning tools (e.g., Sysprep vs waagent), present both with equal prominence and detail.
- Audit linked documentation to ensure Linux parity in referenced guides.
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, and the CLI example is not explicitly labeled as Linux/macOS-friendly. The tab order places CLI first, but PowerShell is presented as a full alternative, which may create a slight Windows bias. No Linux-specific tools or shell examples are provided, but the CLI example is cross-platform.
Recommendations
- Explicitly note that Azure CLI works on Linux, macOS, and Windows, and is the recommended cross-platform tool.
- Add a brief example of running the Azure CLI command in a Linux/macOS shell (e.g., bash), or clarify that the CLI example is suitable for Linux/macOS users.
- Consider mentioning that PowerShell Core is available on Linux/macOS if relevant, or clarify if the PowerShell example is Windows-only.
- If possible, add troubleshooting notes for common Linux/macOS issues (e.g., authentication, environment setup) when using Azure CLI.
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 thorough Linux-specific guidance and examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before delving into Linux-specific details. This may create a perception of Windows-first bias, but all configuration instructions, examples, and tools are Linux-centric.
Recommendations
- Move the Windows Server 2016 time sync discussion and references to a background section or an appendix, making it clear that the main content is Linux-focused.
- Begin the overview with Linux time sync concepts and Azure-specific Linux features, referencing Windows infrastructure only as necessary for context.
- Ensure that all example commands and configuration steps remain Linux-specific, as currently provided.
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. While CLI and REST are cross-platform, PowerShell is Windows-centric, and its inclusion as a primary example may signal a Windows bias. Additionally, PowerShell examples are presented before REST, and CLI examples are not explicitly labeled as Linux/macOS-friendly, though they are cross-platform. There is a slight 'windows_first' bias in the ordering of examples, with PowerShell given prominence alongside CLI and Portal, but no critical functionality is locked to Windows.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- Consider labeling PowerShell examples as 'Windows PowerShell' or 'PowerShell (Windows)' to make the distinction clear.
- If possible, provide Bash or shell script examples for Linux/macOS users, especially for automation scenarios.
- Reorder examples so that cross-platform tools (CLI, REST) are presented before Windows-specific tools (PowerShell).
- Add a note for Linux/macOS users confirming that all CLI and REST steps are fully supported on their platforms.
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 the Azure Key Vault VM Extension for Linux and provides comprehensive Linux-specific details. However, in several sections, Windows-oriented tools (Azure PowerShell) are presented before Linux-native tools (Azure CLI), and PowerShell examples are given more prominence or detail. This ordering may create friction for Linux users, as PowerShell is not the default or preferred automation tool on Linux. All technical instructions and examples are Linux-appropriate, and there is no use of Windows-only tools or patterns, but the documentation could better prioritize Linux-native workflows.
Recommendations
- Present Azure CLI examples before Azure PowerShell examples, as CLI is the primary cross-platform tool and preferred on Linux.
- Explicitly note that PowerShell examples are optional and primarily for users who prefer PowerShell on Linux.
- Add Bash script examples for common deployment and troubleshooting tasks, as Bash is the default shell on most Linux systems.
- Clarify in troubleshooting sections that Azure CLI commands are fully supported and provide parity with PowerShell.
- Where PowerShell-specific warnings are given (e.g., about escaping quotes), add equivalent notes for Azure CLI or Bash if relevant.
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 and examples for creating image definitions and versions in Azure Compute Gallery. However, in several places, Windows/PowerShell examples are presented before Linux/CLI equivalents, and PowerShell is given equal or greater prominence than CLI. The CLI and REST examples are Linux-first, but the PowerShell examples default to Windows, and the portal instructions do not show OS-specific steps. Overall, Linux users can complete all tasks, but minor friction exists due to ordering and example selection.
Recommendations
- Ensure that CLI and PowerShell examples alternate or are presented in parallel for both Linux and Windows, rather than defaulting to Windows in PowerShell and Linux in CLI.
- In PowerShell sections, provide Linux examples first or clarify that the cmdlets work for both OS types.
- In portal instructions, add explicit notes or screenshots for both Linux and Windows image creation flows if there are differences.
- Where examples are shown, alternate the OS type (e.g., show a Linux PowerShell example, or a Windows CLI example) to avoid implicit bias.
- Consider grouping OS-specific instructions together, or clearly labeling them as 'Linux' and 'Windows' for clarity.
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 being Windows-specific. The CLI example is cross-platform, but the tab order and structure do not clearly prioritize Linux/macOS parity. There is no explicit mention of Linux/macOS-specific considerations, and PowerShell (a Windows-centric tool) is presented as a primary method alongside CLI.
Recommendations
- Clearly indicate that Azure CLI is the recommended cross-platform method for Linux/macOS users.
- List the CLI example first, and explicitly note its cross-platform compatibility.
- Add a brief note clarifying that PowerShell is primarily for Windows users, and that Linux users should use Azure CLI.
- Consider adding a section or callout for Linux/macOS users to reinforce parity and avoid confusion.
Virtual Machines
Deploy a Trusted Launch VM
...ain/articles/virtual-machines/trusted-launch-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows Trusted Launch VM deployment, but there are some mild Windows biases. PowerShell examples are exclusively for Windows, and in several sections, Windows examples or terminology appear before Linux equivalents. For example, the PowerShell tab for VM creation only shows Windows VM creation, while CLI examples are Linux-focused. In template deployment, Linux and Windows are presented separately but equally. Overall, Linux users can complete all tasks, but Windows is sometimes prioritized in ordering and scripting.
Recommendations
- Add PowerShell examples for Linux VM deployment (using -Linux parameter and Linux images) alongside Windows examples.
- Where possible, present Linux and Windows examples in parallel, or alternate which is shown first.
- Clarify in PowerShell sections which commands are for Windows and which for Linux, and provide both where supported.
- Ensure terminology and screenshots do not assume Windows by default (e.g., mention SSH for Linux admin setup).
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 PowerShell is used for ARM template deployment and VM deallocation, which is less common for Linux/macOS users. The CLI examples are cross-platform, but PowerShell is presented as a primary automation tool, which may create friction for Linux/macOS users who prefer Bash or native shell scripting.
Recommendations
- Add Bash shell script examples for ARM template deployment and VM deallocation, or clarify that Azure CLI commands work natively on Linux/macOS.
- Explicitly mention that Azure PowerShell is available cross-platform, but provide Bash/CLI alternatives for common operations.
- Reorder examples so that CLI (cross-platform) instructions appear before PowerShell, or group them by OS preference.
- Where PowerShell is used for template deployment, add equivalent Azure CLI commands.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for configuring VM vCore customization, but the PowerShell section is given equal prominence to CLI, and the CLI example uses Ubuntu as the image. However, the PowerShell example is Windows-centric, and PowerShell is a Windows-first tool, though it is available cross-platform. The ordering of sections (CLI before PowerShell) is neutral, but the PowerShell example may imply a Windows bias for users who are not aware of PowerShell Core's cross-platform capabilities. No Linux-specific shell (e.g., bash) or Linux-native tools are mentioned, but the CLI example does use a Linux image.
Recommendations
- Clarify that PowerShell examples work cross-platform with PowerShell Core, or explicitly mention this.
- Consider adding bash or shell script examples for Linux/macOS users, especially for automation scenarios.
- Ensure that examples and instructions do not imply that PowerShell is required for Linux/macOS users.
- Highlight that Azure CLI is fully supported on Linux/macOS and is often the preferred tool for those platforms.
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.
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.