Devtest Labs
99
Total Pages
40
Linux-Friendly Pages
59
Pages with Bias
59.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
334 issues found
Showing 326-334 of 334 flagged pages
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 and linked to dedicated instructions. No exclusive use of Windows tools or missing Linux examples is observed.
Recommendations
- Present connection options for Windows and Linux VMs 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 are balanced between Windows and Linux scenarios.
Create Pull Request
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 Windows (sysprep) and Linux (deprovision) generalization steps together, but lists Windows first and provides a direct link to the Windows sysprep documentation before the Linux deprovision link. There are no command-line examples or tool references for either platform, but the ordering and emphasis slightly favor Windows.
Recommendations
- Present Windows and Linux options in parallel, alternating which is listed first or using a neutral order.
- Provide equal detail and direct links for both Windows and Linux generalization processes.
- Include example commands for both sysprep (Windows) and waagent deprovision (Linux) to ensure parity.
- Add screenshots or step-by-step instructions for both Windows and Linux VMs where applicable.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-custom-image-from-vm-using-portal.md
...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 Windows (sysprep) and Linux (deprovision) generalization steps, but lists the Windows method first and provides a direct link to the Windows Sysprep documentation before the Linux deprovision link. No command-line examples (PowerShell, Bash) are given, and the portal instructions are platform-neutral. However, the ordering and linking suggest a slight Windows-first bias.
Recommendations
- List Windows and Linux generalization options in parallel or alternate the order to avoid implicit prioritization.
- Provide equal prominence and detail for both Windows (sysprep) and Linux (deprovision) steps, including links and explanations.
- Consider adding command-line examples for both platforms (PowerShell for Windows, Bash/CLI for Linux) if relevant.
- Explicitly state that the process applies equally to both Windows and Linux VMs to reinforce parity.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-custom-image-from-vm-using-portal.md
...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 and Linux generalization steps, but lists the Windows tool (Sysprep) before the Linux equivalent (deprovision). The explanation and links also present Sysprep first, which may subtly prioritize Windows workflows. No command-line examples (PowerShell, Bash) are given, and no platform-specific tools are highlighted beyond the generalization step.
Recommendations
- Present Windows and Linux options in parallel or alternate their order to avoid implicit prioritization.
- Provide explicit examples or links for both Windows (Sysprep) and Linux (deprovision) generalization steps, including command-line instructions.
- Add screenshots or instructions that show the process for both Windows and Linux VMs, if there are UI differences.
- Ensure that related content covers both Windows and Linux scenarios equally.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-gen2-vm.md
...blob/main/articles/devtest-labs/devtest-lab-gen2-vm.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides instructions for creating Generation 2 VMs in Azure DevTest Labs exclusively through the Azure portal UI, with no mention of OS-specific tools, commands, or examples. However, it omits any discussion or examples of connecting to or managing Linux-based VMs, such as SSH access, Linux username conventions, or Linux-specific post-deployment steps. The documentation is neutral in terms of not explicitly favoring Windows, but it lacks Linux parity in connection and usage guidance.
Recommendations
- Include explicit examples for connecting to both Windows (using RDP) and Linux (using SSH) VMs after deployment.
- Mention Linux username conventions and any differences in credential requirements.
- Provide guidance or links for post-deployment configuration steps for Linux VMs, such as installing packages or configuring SSH keys.
- Add screenshots or instructions that show Linux VM options and settings where they differ from Windows.
- Clarify that the process applies equally to both Windows and Linux images, and highlight any OS-specific considerations.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/create-alerts.md
...-docs/blob/main/articles/devtest-labs/create-alerts.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively describes how to create activity log alerts using the Azure Portal GUI, with no mention of command-line or scripting alternatives. There are no examples using PowerShell, Azure CLI, or any platform-specific tools. However, the lack of Azure CLI (cross-platform) or Linux-specific instructions means Linux users do not see parity with Windows users who may be more accustomed to GUI or PowerShell workflows.
Recommendations
- Add step-by-step instructions for creating activity log alerts using the Azure CLI, which is cross-platform and widely used on Linux.
- Include example scripts for automating alert creation, highlighting both PowerShell (for Windows) and Bash (for Linux/macOS) usage.
- Explicitly mention that the Azure Portal is accessible from any OS, but provide parity by showing how to accomplish the same tasks from the command line.
- Link to documentation on using Azure CLI and ARM templates for alert rule creation, to support automation and Linux-first workflows.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-custom-image-from-vm-using-portal.md
...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 the Windows generalization tool (Sysprep) before the Linux equivalent (deprovision), and the parenthetical note '(Run sysprep)' for Windows appears before '(Run deprovision)' for Linux. However, both platforms are mentioned and linked, and no platform-specific commands or tools are otherwise favored.
Recommendations
- Present Windows and Linux options in parallel or alternate the order to avoid always listing Windows first.
- Provide explicit step-by-step instructions or links for both Sysprep (Windows) and waagent deprovision (Linux), ensuring equal detail.
- Include screenshots or examples for both Windows and Linux generalization processes if applicable.
- Use neutral phrasing such as 'for Windows (Sysprep) or Linux (deprovision)' or 'for Linux (deprovision) or Windows (Sysprep)' to balance representation.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-attach-detach-data-disk.md
...es/devtest-labs/devtest-lab-attach-detach-data-disk.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation focuses exclusively on using the Azure portal UI to attach and detach data disks, without providing any OS-specific (Windows or Linux) command-line examples. However, it omits any mention of post-attachment steps required inside the VM, such as mounting and formatting disks, which differ between Windows and Linux. This omission can disadvantage Linux users, as the process for making a new disk usable is not covered for either OS, but is especially critical for Linux where manual mounting is common.
Recommendations
- Add a section describing post-attachment steps for both Windows and Linux VMs, such as initializing, partitioning, and mounting the disk (for Linux, using fdisk/lsblk/mkfs/mount; for Windows, using Disk Management or PowerShell).
- Provide example commands for both Linux (bash) and Windows (PowerShell) to guide users through making the new disk available inside the VM.
- Explicitly mention that after attaching a disk in the Azure portal, further steps are required inside the VM, and link to relevant documentation for both OSes.
- Ensure parity in instructions and examples for both Windows and Linux users throughout the documentation.
Devtest Labs
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-gen2-vm.md
...blob/main/articles/devtest-labs/devtest-lab-gen2-vm.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page describes how to create Generation 2 VMs in Azure DevTest Labs using the Azure portal, but does not provide any OS-specific examples or instructions. There is no explicit Windows bias in terms of mentioning Windows tools, PowerShell, or Windows-first patterns. However, the documentation omits any discussion or examples related to Linux-specific considerations, such as SSH access, Linux username conventions, or Linux image selection, which are relevant for cross-platform parity.
Recommendations
- Add explicit notes or examples for creating both Windows and Linux Generation 2 VMs, including any differences in image selection or configuration.
- Clarify how to set up authentication for Linux VMs (e.g., SSH keys vs. passwords) in the 'User name' and 'Password' sections.
- Include screenshots or descriptions that show both Windows and Linux images in the image selection step.
- Mention any Linux-specific Generation 2 VM limitations or requirements, if applicable.
- Provide guidance on connecting to Linux VMs (e.g., using SSH) in addition to the generic 'Connect' instructions.