Devtest Labs
188
Total Pages
144
Linux-Friendly Pages
44
Pages with Bias
23.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
113 issues found
Showing 101-113 of 113 flagged pages
Devtest Labs
Create a custom image from a lab VM
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-custom-image-from-vm-using-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions both Windows (sysprep) and Linux (deprovision) generalization steps, but lists Windows first and links to the Windows sysprep documentation before the Linux deprovision documentation. No command-line examples or tooling are provided, and the process is described as identical for both OSes via the Azure portal.
Recommendations
- List Linux (deprovision) and Windows (sysprep) steps in parallel, or alternate which is mentioned first.
- Provide direct links to both Windows and Linux generalization documentation with equal prominence.
- Include screenshots or examples for both Windows and Linux VMs if there are any OS-specific differences in the portal UI.
- Explicitly state that the process is identical for both Windows and Linux VMs unless there are differences.
Create Pull Request
Devtest Labs
Create and manage virtual machines in Azure DevTest Labs with Azure CLI
...s/blob/main/articles/devtest-labs/devtest-lab-vmcli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by presenting Windows VM creation examples first, referencing Windows images and tools (e.g., Remote Desktop), and giving PowerShell-specific command formatting before Bash. However, Linux examples and instructions are present, and most commands are cross-platform via Azure CLI.
Recommendations
- Alternate the order of Windows and Linux VM creation examples, or present Linux examples first in some sections.
- Provide equal emphasis and detail for Linux/macOS connection methods (e.g., SSH) alongside Windows methods (e.g., RDP).
- Include more Linux artifact examples in output samples, not just Windows ones.
- Clarify that all Azure CLI commands work on Linux/macOS, and link to platform-specific setup guides.
- Balance PowerShell and Bash command formatting guidance, possibly by combining into a single section.
Devtest Labs
Access, claim, and connect to lab VMs
.../main/articles/devtest-labs/tutorial-use-custom-lab.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents connection instructions for Windows VMs before Linux VMs, listing 'Connect via RDP' (Windows) prior to 'Connect via Azure CLI' or 'Connect via Native SSH' (Linux). However, both platforms are covered with links to dedicated instructions, and no Windows-only tools or patterns are used elsewhere.
Recommendations
- Present Windows and Linux connection options in parallel or alphabetical order, rather than listing Windows first.
- Explicitly mention that both Windows and Linux VMs are supported at the start of the connection section.
- Ensure screenshots and examples alternate between Windows and Linux VMs, or include both where relevant.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by using a Windows 11 Pro image as the example for VM creation and referencing a PowerShell script as the only method for copying existing Azure VMs into a lab. While alternative methods (Azure CLI, ARM template) are mentioned for VM creation, examples and scripts are Windows-centric, and Linux-specific instructions or examples are absent.
Recommendations
- Provide Linux-based VM creation examples alongside or before Windows examples (e.g., Ubuntu, CentOS).
- Include Linux/macOS-friendly scripts (e.g., Bash, Azure CLI) for tasks such as copying VMs into a lab.
- Ensure screenshots and walkthroughs are not exclusively Windows-focused; show parity for Linux images and workflows.
- Explicitly mention cross-platform compatibility for all steps and tools.
- Add links to Linux/macOS documentation or guides where PowerShell is referenced.
Devtest Labs
Create and manage virtual machines in Azure DevTest Labs with Azure CLI
...s/blob/main/articles/devtest-labs/devtest-lab-vmcli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Minor Windows Examples
Summary
The documentation page generally maintains cross-platform parity, but there is a subtle Windows bias. Windows-based VM creation is shown first, and Windows images are used as the initial example. There is a specific mention of PowerShell syntax for Cloud Shell before Bash, and the sample artifact output references a Windows artifact. However, Linux VM creation and artifact application are also covered, and Linux-specific examples are present.
Recommendations
- Alternate the order of Windows and Linux VM creation examples, or show Linux first.
- Provide equal emphasis and detail for both Bash and PowerShell in Cloud Shell sections.
- Include sample outputs for both Windows and Linux artifacts.
- Ensure that references and links for connecting to VMs (SSH and RDP) are equally prominent.
- Explicitly mention macOS where relevant (e.g., SSH instructions).
Devtest Labs
Access, claim, and connect to lab VMs
.../main/articles/devtest-labs/tutorial-use-custom-lab.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents connection instructions for Windows VMs before Linux VMs, listing 'Connect via RDP' (Windows) before 'Connect via Azure CLI' or 'Connect via Native SSH' (Linux). However, both platforms are covered with links to their respective guides, and no Windows-only tools or examples are present.
Recommendations
- Present connection options for Windows and Linux VMs in parallel or alphabetical order, rather than listing Windows first.
- Ensure screenshots and examples are balanced between Windows and Linux VM scenarios.
- Explicitly mention macOS where relevant, especially for SSH connections.
- Add a brief note clarifying that both Windows and Linux VMs are supported equally.
Devtest Labs
Troubleshoot VM deployment failures
...es/devtest-labs/troubleshoot-vm-deployment-failures.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page demonstrates a mild Windows bias by referencing PowerShell as the primary method for deploying VMs with ARM templates, without mentioning or providing equivalent examples for Linux/macOS users (such as Azure CLI, Bash, or other cross-platform tools). The only explicit tooling example is PowerShell, and it is mentioned before any alternatives. No Linux/macOS-specific instructions or examples are provided.
Recommendations
- Include Azure CLI or Bash examples alongside PowerShell for ARM template deployments.
- Explicitly state that deployment steps can be performed on Linux/macOS using Azure CLI or other cross-platform tools.
- Add links to cross-platform documentation for VM deployment and troubleshooting.
- Where PowerShell is referenced, clarify its availability on Linux/macOS or provide alternative commands.
Devtest Labs
Connect to your Linux virtual machines
...articles/devtest-labs/connect-linux-virtual-machine.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation page is focused on connecting to Linux VMs and provides a clear SSH command-line example. However, it mentions Putty—a Windows-centric SSH client—by name, without listing Linux-native alternatives or clarifying platform options. No Powershell or Windows-first patterns are present, and Linux examples are primary throughout.
Recommendations
- List Linux-native SSH clients (e.g., OpenSSH, GNOME Terminal, Konsole) alongside Putty.
- Clarify that Putty is primarily for Windows users and suggest alternatives for Linux/macOS.
- Add a note that most Linux/macOS systems have SSH clients pre-installed.
- Ensure tool recommendations are platform-neutral or grouped by OS.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits mild Windows bias. Windows is mentioned first and exclusively in key sections, such as the link to 'Windows virtual machines in Azure' without a corresponding Linux VM link. Example tools listed as artifacts (e.g., Visual Studio, Fiddler) are Windows-centric, and there are no explicit Linux or cross-platform examples or references. No PowerShell-specific bias is present, but Linux users may find the documentation less relatable due to the lack of parity in examples and references.
Recommendations
- Add references and links to Linux virtual machines in Azure alongside Windows VM links.
- Include Linux-specific or cross-platform tools and artifact examples (e.g., Git, VS Code, Apache, Nginx) in the artifacts section.
- Provide examples or scenarios relevant to Linux/macOS users, such as creating labs with Linux base images or using Linux-friendly artifacts.
- Ensure that documentation sections mentioning VM creation, management, and templates highlight both Windows and Linux options equally.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references PowerShell as a method for managing tags before mentioning Azure CLI, which may suggest a Windows-first approach. However, no actual command-line examples are provided, and the main instructions use the Azure portal, which is cross-platform. There are no explicit Windows-only tools or missing Linux/macOS examples, but the ordering of PowerShell before Azure CLI subtly prioritizes Windows patterns.
Recommendations
- When referencing command-line management, mention Azure CLI before or alongside PowerShell, as CLI is cross-platform.
- Provide explicit examples for both PowerShell and Azure CLI, ensuring parity for Linux/macOS users.
- Consider adding a note clarifying that all portal instructions are platform-agnostic.
- If scripting is discussed, include Bash or shell script examples where appropriate.
Devtest Labs
Create a custom image from a lab VM
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-custom-image-from-vm-using-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation mentions Windows-specific tooling (Sysprep) before Linux equivalents (deprovision) and links to Windows documentation first. The generalization step is described as '(Run sysprep)' for Windows and '(Run deprovision)' for Linux, with Sysprep referenced first. There are no command-line examples, but the pattern of mentioning Windows tools and terminology before Linux alternatives suggests a subtle Windows bias.
Recommendations
- Present Windows and Linux generalization options in parallel, giving equal prominence to both.
- Alternate the order of mentioning Windows and Linux tools, or use neutral phrasing such as 'Generalize this virtual machine (Windows: Sysprep, Linux: deprovision)'.
- Provide direct links to both Windows and Linux generalization documentation, ideally side-by-side.
- Include brief explanations of both Sysprep and deprovision processes, ensuring Linux users have clear guidance.
- If possible, add command-line examples for both Windows (PowerShell) and Linux (bash) for advanced users.
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions both Windows and Linux VM use cases, but provides examples and screenshots that are generic and do not show platform-specific instructions. However, Windows VM password use is mentioned first, and there are no explicit Linux/macOS command-line or SSH key management examples. There is a subtle bias toward Windows, as the primary secret example is a Windows VM password, and Linux scenarios (such as SSH key handling) are referenced only in passing.
Recommendations
- Provide explicit examples for storing and retrieving SSH keys for Linux VMs, including screenshots or code snippets.
- Include instructions or references for using secrets with Linux/macOS command-line tools (e.g., Azure CLI, bash scripts).
- Balance the order of examples so that Linux and Windows scenarios are equally represented.
- Add a section on how to use secrets in Linux VM provisioning workflows.
Devtest Labs
Create a network isolated lab
...s/blob/main/articles/devtest-labs/network-isolation.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing a PowerShell script as the only provided method for converting an existing lab to isolated network mode, without mentioning or providing equivalent Azure CLI, Bash, or Linux/macOS-friendly alternatives. Additionally, PowerShell is mentioned before any cross-platform automation options, and no Linux-specific examples or guidance are given.
Recommendations
- Provide equivalent Azure CLI commands or scripts for converting labs to isolated network mode, ensuring Linux/macOS users have a clear path.
- Explicitly mention that PowerShell Core is cross-platform, or clarify if the script is Windows-only.
- Add Bash or Azure CLI examples for automating the configuration steps (e.g., storage account and key vault endpoint setup).
- Ensure that automation and scripting guidance is not Windows-centric and covers Linux/macOS usage patterns.