Virtual Machines
1080
Total Pages
1005
Linux-Friendly Pages
75
Pages with Bias
6.9%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
815 issues found
Showing 801-815 of 815 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell example is given equal prominence and detail as the CLI example. The CLI example is cross-platform (Linux, macOS, Windows), while PowerShell is primarily Windows-focused (though PowerShell Core is available on Linux/macOS, most Azure users associate it with Windows). The tabs present CLI first, but the PowerShell section is not clearly marked as Windows-specific, which may create confusion or friction for Linux/macOS users.
Recommendations
- Explicitly note that PowerShell examples are primarily for Windows users, and clarify PowerShell Core compatibility for Linux/macOS.
- Highlight Azure CLI as the recommended cross-platform method for quota checks.
- Consider providing bash or shell script examples for Linux users, if relevant.
- Add a note at the top of the examples section indicating which commands are cross-platform and which are Windows-specific.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but PowerShell (a Windows-centric tool) is given equal prominence and a dedicated tab. The CLI example is shown first, which is positive for Linux parity, but the presence of PowerShell examples may suggest a slight Windows bias, especially since no Linux-specific shell (e.g., Bash) or macOS-specific notes are included.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows equally.
- Add a note for Linux/macOS users confirming that Azure CLI is the recommended cross-platform tool.
- Consider mentioning Bash scripting or providing example output from a Linux terminal to reinforce parity.
- If possible, include a brief section on installing Azure CLI 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 when enabling Trusted launch, with clear statements that the feature applies to both. However, there is mild Windows bias in the ordering and tooling: PowerShell examples are provided and referenced before Linux alternatives, and PowerShell is used for ARM template deployment and VM deallocation, even though Linux users would likely prefer Bash or Azure CLI. The verification step mentions RDP (Windows) before SSH (Linux) throughout. There are no missing Linux examples, and the CLI instructions are cross-platform.
Recommendations
- Provide Bash shell examples for ARM template deployment and VM deallocation alongside PowerShell, or clarify that PowerShell commands can be run on Linux/macOS using PowerShell Core.
- Alternate the order of RDP/SSH mentions, or mention SSH first in Linux-specific contexts.
- Explicitly state that all CLI and template steps are cross-platform and can be performed from Linux/macOS.
- For template deployment, offer Azure CLI examples in addition to PowerShell.
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 shown in parity with CLI, but there is a subtle Windows bias: PowerShell is a Windows-centric tool and is presented alongside CLI, and in the first major section ('Create a private gallery'), the PowerShell example is shown before REST. Additionally, the ordering of examples is Portal > CLI > PowerShell > REST, which places Windows tools before REST, and PowerShell is not available natively on Linux/macOS (though PowerShell Core exists, it's less common for Azure tasks). No Linux-specific tools (e.g., Bash scripts) or explicit Linux/macOS guidance is provided.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- Consider mentioning PowerShell Core compatibility for non-Windows users if PowerShell is shown.
- Ensure example ordering does not imply preference for Windows tools (e.g., CLI before PowerShell).
- Optionally, add a note that Bash or shell scripting can be used with Azure CLI on Linux/macOS.
- Explicitly state platform compatibility for each method.
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 the CLI example is not explicitly labeled as Linux/macOS-friendly. The tab order presents CLI first, but the PowerShell section is detailed and assumes familiarity with Windows tooling. There is no explicit mention of Linux-specific tools or shell environments, nor are there notes clarifying cross-platform compatibility for the CLI commands.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and are the recommended cross-platform approach.
- Add a note clarifying that PowerShell examples are primarily for Windows users, while Azure CLI is suitable for Linux/macOS.
- Consider providing bash or shell script examples for Linux users, or at least mention that the CLI commands can be run in bash/zsh.
- If possible, reorder tabs or add a 'Recommended for Linux/macOS' label to the CLI section.
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 of connection instructions (RDP for Windows is mentioned before SSH for Linux), and PowerShell is used for ARM template deployment and VM deallocation/start examples, which may be less familiar or accessible to Linux/macOS users. The CLI examples are cross-platform, but PowerShell is referenced in several places without alternative Bash or shell scripting examples.
Recommendations
- When showing connection instructions, alternate the order or explicitly show Linux-first examples in some sections (e.g., 'Verify that you can sign in to the VM by using SSH (for Linux VMs) or RDP (for Windows VMs)').
- For ARM template deployment and VM management, provide equivalent Bash/Azure CLI scripts for Linux/macOS users alongside PowerShell examples.
- Where PowerShell is used for deallocation/start, add Bash/Azure CLI alternatives, especially in the 'Template' tab.
- Clarify that PowerShell examples are for users on Windows, and link to cross-platform CLI alternatives where possible.
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 before REST, and the PowerShell section is Windows-centric. The ordering of examples places PowerShell before REST, which may subtly prioritize Windows tooling. However, Linux/macOS users can fully complete all tasks using the CLI or REST, and no critical functionality is missing for non-Windows platforms.
Recommendations
- Explicitly note that PowerShell examples are for Windows users, and that Azure CLI and REST are cross-platform.
- Consider placing CLI examples before PowerShell to emphasize cross-platform tooling.
- Add a brief statement at the top clarifying that all tasks can be completed on Linux/macOS using CLI or REST.
- Where possible, link to Azure CLI installation guides for Linux/macOS users.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for 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 may suggest Windows-first thinking. There are no Linux-specific command-line examples beyond Azure CLI, and PowerShell is highlighted as a primary method, which may create friction for Linux/macOS users.
Recommendations
- Make it clear that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Consider listing the CLI example first, or explicitly noting platform compatibility for each method.
- Add a brief note that PowerShell Core is available on Linux/macOS, but Azure CLI is typically preferred on those platforms.
- If possible, include example output from Linux/macOS terminals to reinforce parity.
Virtual Machines
Boot integrity monitoring overview
...virtual-machines/boot-integrity-monitoring-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows and Linux examples for deploying the Guest Attestation extension via ARM templates, and references both Windows and Linux publishers. However, in the template section, Windows is presented before Linux, and the troubleshooting example error references the Windows extension specifically. The CLI and PowerShell sections do not show OS-specific commands, but the PowerShell tab is present, which may be more familiar to Windows users. Overall, Linux parity is maintained, but minor ordering and example choices show a slight Windows-first bias.
Recommendations
- Present Linux and Windows examples in parallel or alternate their order to avoid implicit prioritization.
- In troubleshooting, mention that similar errors may occur for Linux VMs and reference the Linux extension explicitly.
- Where possible, clarify that CLI and template instructions apply equally to both OS types.
- Add Bash or Linux shell examples if relevant, especially in sections where PowerShell is highlighted.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for configuring VM watch using ARM templates, Azure CLI, and PowerShell. While the introductory section notes that the code segment is identical for both Windows and Linux except for the extension type, the PowerShell example is included as a primary method alongside CLI and ARM template. There is a slight Windows-first bias in listing PowerShell as a top-level method, and the documentation does not provide explicit Linux shell (bash) examples or guidance for Linux users beyond the CLI. The use of Visual Studio Code as the recommended IDE is platform-neutral, but may be perceived as Windows-centric by some users.
Recommendations
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide explicit bash shell examples where relevant.
- Consider adding a note or example for Linux users showing how to use the CLI in a Linux shell environment.
- If PowerShell is mentioned, clarify that PowerShell Core is cross-platform, or provide alternative bash examples for Linux/macOS users.
- Explicitly state that all configuration methods (ARM template, CLI, PowerShell) are supported on both Windows and Linux, and highlight any platform-specific considerations.
Virtual Machines
Delete a VM and attached resources
...ute-docs/blob/main/articles/virtual-machines/delete.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides examples for Azure Portal, CLI, PowerShell, and REST API. However, PowerShell is given equal prominence to CLI, despite being Windows-centric. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell examples may not be directly usable on non-Windows platforms. The CLI examples are cross-platform, but the absence of Linux/macOS-specific shell scripting or explicit mention of Linux usage creates mild friction for non-Windows users.
Recommendations
- Clarify that PowerShell examples are primarily for Windows users and recommend CLI for Linux/macOS users.
- Add explicit Bash shell examples for common tasks, especially in sections where PowerShell is shown.
- Where possible, note platform compatibility for each example (e.g., 'CLI: works on Windows, Linux, macOS; PowerShell: Windows only').
- Consider reordering examples to show CLI before PowerShell, emphasizing cross-platform tools.
- Add links or references to Linux/macOS-specific documentation where relevant.
Virtual Machines
Copy a snapshot to a new region
...ines/disks-copy-incremental-snapshot-across-regions.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for copying incremental snapshots, but the PowerShell section is more detailed and assumes use of Windows/PowerShell. The CLI examples use Bash syntax, but there is no explicit mention of Linux/macOS environments or shell differences. The PowerShell example is given equal prominence to CLI, and the CLI example uses Bash variables, which may not be familiar to Windows users. There are no Linux-specific troubleshooting tips, nor is there mention of Linux-native tools or considerations. The portal and ARM template instructions are platform-neutral.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and clarify shell differences if needed.
- Add a note or section for Linux/macOS users, confirming that Bash syntax is for Unix-like shells and provide equivalent Windows CMD syntax if desired.
- Provide troubleshooting tips for Linux/macOS environments (e.g., permissions, environment variables).
- Ensure parity in detail between CLI and PowerShell sections, and avoid assuming PowerShell is the default for scripting unless the audience is Windows-specific.
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
Minor Windows Tools
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for enabling encryption at host, but PowerShell examples are consistently listed first. The 'Next steps' section links only to PowerShell-based template samples, which may favor Windows users. However, the main instructions are Azure portal-based and explicitly state applicability to both Linux and Windows VMs. There are no critical omissions of Linux-specific instructions or tools.
Recommendations
- Alternate the order of PowerShell and CLI examples, or present CLI examples first to balance visibility for Linux/macOS users.
- Include links to Azure CLI-based Resource Manager template samples in the 'Next steps' section.
- Explicitly mention that all CLI commands work on Linux/macOS and Windows, and clarify any platform-specific nuances if present.
- Ensure screenshots and UI instructions are platform-neutral, as the Azure portal is web-based.
Virtual Machines
Instantly access managed disk snapshots
...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for creating instant access snapshots, but lists PowerShell examples immediately after CLI and before Resource Manager templates. No Linux/macOS-specific tools or shell patterns are mentioned, but the CLI examples use Bash syntax, which is suitable for Linux/macOS. There is a slight ordering bias toward Windows/PowerShell, but all critical operations are covered with CLI examples, so Linux/macOS users are not blocked.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and show Bash and PowerShell syntax side-by-side for variable declarations if relevant.
- Consider listing CLI examples before PowerShell and clarify platform compatibility for each example.
- Add a note that Azure PowerShell is primarily for Windows, while Azure CLI is cross-platform.
- If possible, provide example commands using native Linux tools (e.g., curl for SAS URI download) where relevant.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely neutral, focusing on VM specifications and features. However, there is mild Windows bias in the 'Feature support' section, where 'Nested Virtualization' links to a Windows-specific guide, and in the 'Bandwidth/Throughput testing (NTTTCP)' reference, which is a Windows-centric tool. No Linux-specific examples or tools are mentioned, and Windows references appear before Linux equivalents (if any).
Recommendations
- Include links to Linux-specific nested virtualization documentation or clarify Linux support status.
- Mention Linux-compatible bandwidth/throughput testing tools (e.g., iperf, ntttcp-for-linux) alongside NTTTCP.
- Where features/tools are OS-specific, explicitly state Linux/macOS alternatives or limitations.
- Ensure parity in documentation references for both Windows and Linux environments.