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 76-100 of 113 flagged pages
Devtest Labs Grant user permissions to specific lab policies ...st-lab-grant-user-permissions-to-specific-lab-policies.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell (specifically Azure PowerShell cmdlets) for all examples and instructions, with no mention of Linux/macOS alternatives such as Azure CLI or Bash. All code samples and setup steps assume a Windows/PowerShell environment, and there is no guidance for users on non-Windows platforms. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that Azure PowerShell can be installed and used on Linux/macOS, or provide links to installation instructions for those platforms.
  • Where possible, provide Bash script examples alongside PowerShell.
  • Clarify tool requirements at the start, and suggest alternatives for non-Windows users.
  • Reorder or balance examples so that Windows and Linux/macOS users are equally supported.
GitHub Create Pull Request
Devtest Labs Deploy Azure DevTest Labs (Enterprise Reference Architecture) ...les/devtest-labs/devtest-lab-reference-architecture.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, primarily through exclusive references to Windows-centric tools and patterns, such as Remote Desktop Gateway and RDP, without mentioning Linux/macOS equivalents (e.g., SSH, Linux jump hosts). Examples and guidance for scripting automation mention PowerShell first, with no Linux shell or macOS-specific examples. The lack of Linux/macOS alternatives for remote access and automation may create friction for non-Windows users.
Recommendations
  • Include guidance and examples for Linux/macOS remote access (e.g., SSH bastion hosts, Linux jump servers) alongside or before Windows RDP solutions.
  • Provide scripting automation examples using Bash, Azure CLI, and cross-platform SDKs, not just PowerShell.
  • Mention Linux/macOS-compatible tools for artifact repository access and VM management.
  • Clarify which features and recommendations are platform-agnostic and which require Windows-specific infrastructure.
GitHub Create Pull Request
Devtest Labs Troubleshoot Artifacts on Lab Virtual Machines ...vtest-labs/devtest-lab-troubleshoot-apply-artifacts.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. Troubleshooting steps and examples are primarily focused on Windows environments, with PowerShell commands and Windows file paths provided. Linux-specific instructions are either missing, referenced only via external links, or not given equal prominence. Windows tools and patterns (File Explorer, Command Prompt) are used throughout, while Linux equivalents are not described.
Recommendations
  • Provide equivalent Linux examples alongside Windows instructions, such as Bash/CLI commands for checking artifact status and inspecting logs.
  • Include Linux file paths and troubleshooting steps for CSE logs and script execution directly in the main documentation, not only via external links.
  • Use cross-platform language and tools where possible (e.g., Azure CLI instead of PowerShell, or show both).
  • Present Windows and Linux instructions in parallel sections or side-by-side, rather than Windows-first.
  • Reference Linux-specific troubleshooting resources with equal visibility.
GitHub Create Pull Request
Devtest Labs Azure DevTest Labs scenarios ...icles/devtest-labs/devtest-lab-guidance-get-started.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure DevTest Labs scenarios demonstrates a moderate Windows bias. Many example links and quickstarts reference Windows-specific resources (e.g., 'create-lab-windows-vm-bicep.md', 'create-lab-windows-vm-template.md', 'create-lab-windows-vm-terraform.md'), and PowerShell is frequently mentioned as the automation tool, with no mention of Bash, CLI, or Linux/macOS scripting alternatives. Windows tools (Visual Studio, Fiddler, Active Directory domain join) are listed as artifact examples, while Linux equivalents are absent. There are no explicit Linux/macOS examples or guidance, and Windows terminology and tooling are presented first or exclusively.
Recommendations
  • Add Linux/macOS-specific examples and quickstarts, such as creating labs and VMs using Bash scripts, Azure CLI, or Linux-based images.
  • Include references to Linux tools and artifacts (e.g., VS Code, open-source agents, Linux domain join) alongside Windows tools.
  • Balance PowerShell references with Azure CLI or Bash alternatives for automation tasks.
  • Update example links and file names to include Linux scenarios, not just Windows (e.g., 'create-lab-linux-vm-bicep.md').
  • Explicitly mention cross-platform support and provide parity in instructions for both Windows and Linux/macOS users.
GitHub Create Pull Request
Devtest Labs Hibernation for virtual machines ...main/articles/devtest-labs/devtest-lab-hibernate-vm.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by using Windows 11 Pro as the example OS for VM creation and referencing 'select your Windows VM' in screenshots and instructions. There are no examples or guidance provided for Linux-based VMs, nor is there mention of Linux-specific considerations or parity in the hibernation process.
Recommendations
  • Include explicit examples for creating and hibernating Linux-based VMs, such as Ubuntu or CentOS, alongside Windows examples.
  • Clarify whether hibernation is supported for Linux VMs and list any OS-specific limitations.
  • Update screenshots and instructions to show both Windows and Linux VM scenarios.
  • Mention Linux authentication options (e.g., SSH keys) in the VM creation steps.
  • Ensure terminology and instructions are inclusive of both Windows and Linux users.
GitHub Create Pull Request
Devtest Labs Create and deploy labs with Azure Resource Manager (ARM) templates ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-use-arm-and-powershell-for-lab-resources.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows/PowerShell examples and workflows are mentioned first and most frequently, especially in automation and quickstart sections. The quickstart template example is specifically for a Windows Server VM, with no Linux VM equivalent shown. Automation tasks are described primarily using Azure PowerShell, with only brief mention of Azure CLI and no Linux shell-specific guidance. Linked scripts and examples are PowerShell-centric, and there is no explicit mention of Linux/macOS usage patterns or troubleshooting.
Recommendations
  • Add Linux VM quickstart examples alongside Windows Server VM instructions.
  • Provide Bash/Azure CLI automation examples with step-by-step instructions, not just command references.
  • Include links to Linux/macOS-specific scripts or guidance in the GitHub repository.
  • Balance PowerShell and CLI coverage, ensuring Linux users can follow all tasks without switching to Windows tools.
  • Explicitly mention platform compatibility and any differences in workflow for Linux/macOS users.
GitHub Create Pull Request
Devtest Labs Move DevTest Labs to another region ...cs/blob/main/articles/devtest-labs/how-to-move-labs.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, especially in the disk migration section, where PowerShell commands and Windows-centric patterns are used exclusively. AzCopy is presented as the preferred tool, with instructions and code samples in PowerShell. The reference to swapping OS disks links to a Windows-specific article, and no Linux CLI or Bash examples are provided. While Linux VMs are mentioned in the context of network configuration, actionable migration steps are Windows/PowerShell focused.
Recommendations
  • Provide equivalent CLI/Bash examples for disk migration, including AzCopy usage from Linux/macOS.
  • Reference and link to Linux-specific documentation for disk swaps (e.g., using Azure CLI or REST API).
  • Include explicit instructions for performing all steps from Linux/macOS environments, not just Windows/PowerShell.
  • When mentioning tools like AzCopy, clarify cross-platform availability and provide usage examples for each OS.
  • Ensure that all code samples are available in both PowerShell and Bash/Azure CLI formats.
GitHub Create Pull Request
Devtest Labs Extend Azure DevTest Labs with Azure Functions ...es/devtest-labs/extend-devtest-labs-azure-functions.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a notable Windows bias. All step-by-step instructions focus on Visual Studio (Windows-only), screenshots are exclusively from Windows tools, and there are no Linux/macOS alternatives for building, deploying, or configuring the sample. The sample code is available in both C# and PowerShell, but no mention is made of Linux-friendly tools (e.g., VS Code, Azure CLI for deployment, or cross-platform build instructions). The only artifact mentioned is 'Windows Update', with no Linux equivalent. PowerShell is referenced as a method for creating service principals, but Linux alternatives are not highlighted.
Recommendations
  • Add instructions for building and deploying the sample using cross-platform tools such as VS Code, Azure CLI, or GitHub Actions.
  • Include screenshots and steps for Linux/macOS environments, especially for deployment and configuration.
  • Mention and provide examples for Linux update artifacts, or clarify how Linux VMs can be managed in DevTest Labs.
  • Present Azure CLI examples before or alongside PowerShell, and clarify which steps are platform-agnostic.
  • Explicitly state platform requirements and alternatives for users not on Windows.
GitHub Create Pull Request
Devtest Labs Import virtual machines from another lab ...vtest-labs/import-virtual-machines-from-another-lab.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell scripting instructions for importing VMs, with no mention of Linux/macOS shell equivalents (such as Bash or Azure CLI). The PowerShell method is presented first and in detail, while the REST API method is described generically without platform-specific guidance. No Linux or cross-platform scripting examples are provided.
Recommendations
  • Add Azure CLI examples for importing VMs, which work on Linux, macOS, and Windows.
  • Provide Bash shell script samples for Linux/macOS users.
  • Clarify whether the PowerShell script can be run using PowerShell Core on Linux/macOS, and provide installation guidance if so.
  • Present cross-platform methods (REST API, Azure CLI) before or alongside Windows-specific tools.
  • Explicitly state platform compatibility for each method.
GitHub Create Pull Request
Devtest Labs How to delete and export personal data ...n/articles/devtest-labs/personal-data-delete-export.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides only Azure PowerShell examples and instructions for exporting personal data, with no mention of Linux/macOS alternatives such as Azure CLI, Bash, or REST API. All tooling and code samples are Windows-centric, creating friction for users on non-Windows platforms.
Recommendations
  • Add equivalent instructions and code samples using Azure CLI, which is cross-platform and works natively on Linux/macOS.
  • Mention REST API options for exporting data, if available, to provide platform-agnostic solutions.
  • Explicitly state that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation guidance.
  • Present Linux/macOS-friendly examples before or alongside Windows/PowerShell examples to avoid Windows-first bias.
GitHub Create Pull Request
Devtest Labs Quickstart: Create a lab with REST API ...n/articles/devtest-labs/quickstarts/create-lab-rest.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell scripts and Windows-centric tools (Az Module, Connect-AzAccount, etc.) for all steps, with no mention of Linux/macOS alternatives (such as Bash, curl, or Azure CLI). This creates friction for non-Windows users, who must translate all instructions themselves. The bias is present throughout, including authentication, REST invocation, and resource cleanup.
Recommendations
  • Add equivalent Linux/macOS instructions using Bash and curl for REST API calls.
  • Provide Azure CLI examples for authentication and resource management, which are cross-platform.
  • Explicitly state that the instructions are PowerShell/Windows-specific, and link to cross-platform alternatives.
  • Ensure variable setup and file path examples use platform-neutral or both Windows and Linux/macOS formats.
GitHub Create Pull Request
Devtest Labs Specify resource group for Azure VMs in DevTest Labs ...b/main/articles/devtest-labs/resource-group-control.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a PowerShell script as the only command-line example for configuring resource groups for Azure DevTest Labs VMs. There are no equivalent examples for Bash, Linux shell, or cross-platform scripting, and PowerShell is presented before any mention of ARM templates or API usage. This creates friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Add a Bash or shell script example using the Azure CLI for Linux/macOS users.
  • Explicitly state that the Azure CLI commands can be run in any shell, not just PowerShell.
  • Present cross-platform examples (e.g., Bash and PowerShell) side-by-side or in parallel sections.
  • Clarify that ARM template and API methods are platform-agnostic and highlight their use for all OSes.
GitHub Create Pull Request
Devtest Labs Azure DevTest Labs usage across multiple labs and subscriptions ...abs/report-usage-across-multiple-labs-subscriptions.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the only scripting example explicitly mentioned for exporting resource usage, both via the Az.Resource module and in references to Azure Functions and Automation runbooks. There are no Linux/macOS shell (e.g., Bash, CLI) examples or references to cross-platform tools. Windows-centric tools like Power BI and SQL Server are highlighted first or exclusively, with little mention of Linux-friendly alternatives or parity in example code.
Recommendations
  • Add Azure CLI and Bash examples for exporting resource usage, alongside PowerShell.
  • Explicitly mention that Azure Functions and Automation runbooks can use Python or Bash, and provide sample code for these platforms.
  • Include references to Linux/macOS compatible visualization tools (e.g., Grafana, Jupyter) and storage solutions (e.g., PostgreSQL, MySQL).
  • Reorder examples so that cross-platform or Linux-native tools are presented alongside or before Windows tools.
  • Clarify that the REST API can be used from any OS and provide sample curl or HTTP request examples.
GitHub Create Pull Request
Devtest Labs Set up a lab, lab VM, and lab user ...in/articles/devtest-labs/tutorial-create-custom-lab.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for creating a lab and adding a VM in Azure DevTest Labs, but when guiding users to add a VM, it exclusively uses 'Windows Server 2019 Datacenter' as the example base image. There are no examples or mentions of Linux VM images, nor are there instructions or screenshots showing Linux-specific configuration options. This creates a subtle bias toward Windows, potentially leading Linux users to believe that only Windows VMs are supported or recommended.
Recommendations
  • Include explicit examples and screenshots for creating a Linux VM (e.g., Ubuntu, CentOS) alongside the Windows example.
  • Mention that both Windows and Linux images are supported and highlight any Linux-specific configuration options (e.g., SSH key setup instead of password).
  • Add notes or tips for Linux users regarding best practices for VM configuration, such as using SSH keys and selecting appropriate artifacts.
  • Ensure that references to VM base images do not default to Windows unless Windows is required for the scenario.
GitHub Create Pull Request
Devtest Labs Use commands to start and stop lab VMs ...t-labs/use-command-line-start-stop-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias: PowerShell is presented first and in greater detail, with Windows-specific syntax and tools (PowerShell, Windows batch variable syntax) featured prominently. While Azure CLI examples are provided for both Bash (Linux/macOS) and Windows, the PowerShell section is more extensive and detailed. There is no explicit Linux/macOS shell script example outside of Bash variable assignment, and Windows syntax is often shown before Bash equivalents.
Recommendations
  • Alternate the order of PowerShell and CLI sections, or present CLI (Bash) examples first to balance platform representation.
  • Expand Bash/Linux CLI examples to match the detail of PowerShell scripts, including error handling and output messaging.
  • Add explicit macOS/Linux shell script examples (e.g., using sh or zsh) where relevant.
  • Clarify that all CLI commands work equally on Linux/macOS and Windows, and provide troubleshooting notes for platform-specific issues.
  • Reduce emphasis on Windows-specific tools and syntax (e.g., batch variable assignment), or provide parity for Linux/macOS users.
GitHub Create Pull Request
Devtest Labs Create activity log alerts for labs ...-docs/blob/main/articles/devtest-labs/create-alerts.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes how to create activity log alerts using the Azure portal GUI, which is most commonly accessed via Windows. There are no examples or references to command-line methods (such as Azure CLI, Bash, or PowerShell), nor is there any mention of Linux-specific workflows or parity. This implicitly prioritizes Windows-centric usage patterns and omits guidance for Linux users or those preferring automation.
Recommendations
  • Add equivalent instructions for creating activity log alerts using Azure CLI and/or Azure PowerShell, with explicit examples for both Windows and Linux shells.
  • Include screenshots or terminal output for Linux environments where relevant.
  • Mention cross-platform access to the Azure portal and clarify that the steps apply equally regardless of OS, or note any differences.
  • Provide links to documentation for automating alert creation via scripts, and ensure examples are available for Bash and PowerShell.
  • Explicitly state that the Azure portal is accessible from any modern browser on Windows, Linux, or macOS.
GitHub Create Pull Request
Devtest Labs Hibernation for virtual machines ...main/articles/devtest-labs/devtest-lab-hibernate-vm.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively using Windows 11 Pro as the example OS for VM creation, referencing 'your Windows VM' in screenshots, and omitting any mention or example of Linux VM creation or hibernation. There are no Linux-specific instructions, screenshots, or clarifications about Linux support or differences.
Recommendations
  • Include parallel Linux VM creation instructions and screenshots (e.g., using Ubuntu or other supported Linux images).
  • Clarify whether hibernation is supported for Linux VMs, and if there are any differences or limitations compared to Windows.
  • Use neutral language in examples and screenshots (e.g., 'Select your VM' instead of 'Select your Windows VM').
  • Provide explicit examples for both Windows and Linux, or indicate OS-specific steps where necessary.
GitHub Create Pull Request
Devtest Labs Store secrets in a key vault ...devtest-labs/devtest-lab-store-secrets-in-key-vault.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by mentioning Windows VM passwords as the first example of secrets, while Linux SSH keys are mentioned second. There are no platform-specific examples or instructions for Linux users (e.g., how to use secrets for Linux VMs), nor are Linux command-line tools or patterns referenced. The screenshots and instructions are generic and do not provide parity for Linux scenarios.
Recommendations
  • Provide explicit Linux examples, such as storing and retrieving SSH keys for Linux VMs.
  • Include instructions or screenshots demonstrating secret usage in Linux VM creation workflows.
  • Mention Linux command-line tools (e.g., Bash, CLI) where relevant, alongside any Windows-specific tools.
  • Ensure that examples and ordering do not consistently prioritize Windows scenarios over Linux.
GitHub Create Pull Request
Devtest Labs Stop and resize lab VMs ...ob/main/articles/devtest-labs/devtest-lab-resize-vm.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes resizing Azure DevTest Lab VMs using the Azure portal GUI, with screenshots and instructions that implicitly assume a Windows-centric workflow. There are no examples or mentions of resizing VMs via command-line tools, such as Azure CLI, PowerShell, or Bash, nor is there any guidance for Linux users or those using non-GUI environments.
Recommendations
  • Add examples for resizing VMs using Azure CLI and/or PowerShell, with clear instructions for both Windows and Linux/macOS environments.
  • Include screenshots or terminal output for command-line workflows, demonstrating parity for users who do not use the Azure portal GUI.
  • Explicitly mention that the resizing process can be performed from any OS using the Azure CLI, and provide links to relevant cross-platform documentation.
  • If possible, add troubleshooting steps or notes relevant to Linux users, such as SSH connection guidance after resizing.
GitHub Create Pull Request
Devtest Labs Encrypt Disks with Customer-Managed Keys ...es/devtest-labs/encrypt-disks-customer-managed-keys.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes disk encryption management in Azure DevTest Labs using the Azure portal UI, with screenshots and step-by-step instructions. There are no command-line examples, and no mention of Linux-specific tools or workflows (such as Azure CLI, Bash, or Linux shell scripting). The documentation implicitly assumes a Windows-centric approach by relying solely on graphical interfaces and omitting cross-platform command-line alternatives.
Recommendations
  • Add Azure CLI and/or PowerShell command examples for each major step, ensuring parity for users on Linux, macOS, and Windows.
  • Explicitly mention that all steps can be performed using Azure CLI or REST API, and provide links or code snippets.
  • Include notes or sections for Linux users, such as how to validate disk encryption from a Linux VM or using Linux-native tools.
  • Balance screenshots with terminal output examples to support users who prefer or require command-line workflows.
GitHub Create Pull Request
Devtest Labs Set up a lab, lab VM, and lab user ...in/articles/devtest-labs/tutorial-create-custom-lab.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively providing instructions and examples for creating a Windows Server 2019 Datacenter VM, without mentioning or providing equivalent steps for Linux-based VMs. There are no references to Linux images, tools, or user patterns, and the workflow implicitly assumes Windows as the default operating system for lab VMs.
Recommendations
  • Include instructions and screenshots for creating a Linux VM (e.g., Ubuntu, CentOS) alongside the Windows example.
  • Mention Linux images as available options when selecting a base for the VM, and highlight any differences in configuration (e.g., SSH key setup instead of password).
  • Provide guidance on Linux-specific user management and access patterns, such as using SSH keys and configuring sudo privileges.
  • Ensure that artifact examples and automation templates demonstrate parity for both Windows and Linux environments.
  • Use neutral language when referring to VM operating systems, and avoid implying Windows as the default or only choice.
GitHub Create Pull Request
Devtest Labs Connect to your Linux virtual machines ...articles/devtest-labs/connect-linux-virtual-machine.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation page is focused on connecting to Linux VMs and provides a Bash SSH example. However, it mentions 'Putty' as an SSH client, which is primarily a Windows tool, without mentioning native Linux/macOS alternatives. No PowerShell or Windows-first examples are present, and the overall flow is Linux-centric.
Recommendations
  • Mention native SSH clients available on Linux and macOS (e.g., OpenSSH in terminal) alongside Putty.
  • Clarify that Putty is mainly for Windows users, while Linux/macOS users can use their built-in terminal.
  • Provide links or brief instructions for using SSH on Linux/macOS.
GitHub Create Pull Request
Devtest Labs Azure DevTest Labs concepts ...lob/main/articles/devtest-labs/devtest-lab-concepts.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a mild Windows bias. Windows is mentioned first and exclusively in key sections, such as the link to 'Windows virtual machines in Azure' under the Virtual Machines section. Examples of artifacts include Windows-centric tools like Visual Studio and Fiddler, with no mention of Linux alternatives. There are no explicit Linux or macOS examples, nor references to Linux VM documentation or tools, which may leave Linux users unclear about platform support and usage.
Recommendations
  • Add references and links to Linux and macOS VM documentation alongside Windows VM documentation.
  • Include examples of Linux/macOS tools and artifacts (e.g., VS Code, Git, Apache) in the Artifacts section.
  • Clarify that DevTest Labs supports both Windows and Linux VMs, and provide parity in examples and guidance.
  • Where VM creation or management is discussed, show both Windows and Linux workflows or considerations.
GitHub Create Pull Request
Devtest Labs Store secrets in a key vault ...devtest-labs/devtest-lab-store-secrets-in-key-vault.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page shows a subtle Windows bias: it mentions Windows VM passwords as the first example of secrets, and does not provide explicit Linux-focused examples or instructions (e.g., SSH key usage, Linux VM creation steps, or Linux command-line integration). All screenshots and instructions are generic and GUI-based, but the initial framing and lack of Linux-specific guidance may create friction for Linux users.
Recommendations
  • Include explicit Linux examples, such as storing and retrieving SSH keys for Linux VMs.
  • Provide command-line instructions for both Windows (PowerShell) and Linux (Bash/Azure CLI) users.
  • Balance introductory examples by mentioning Linux and Windows secrets equally.
  • Add screenshots or walkthroughs for Linux VM scenarios.
GitHub Create Pull Request
Devtest Labs Add tags to a lab ...blob/main/articles/devtest-labs/devtest-lab-add-tag.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references managing tags using PowerShell before mentioning Azure CLI, and does not provide explicit Linux/macOS examples or screenshots. The mention of PowerShell as a management tool may implicitly favor Windows users, as PowerShell is native to Windows, though it is available cross-platform. No Linux-specific tools, patterns, or UI screenshots are provided.
Recommendations
  • Provide explicit Azure CLI examples for tag management, as CLI is platform-agnostic and commonly used on Linux/macOS.
  • Clarify that PowerShell is available cross-platform, or avoid listing it before CLI to reduce perceived Windows-first bias.
  • Include screenshots or instructions that demonstrate usage on Linux/macOS environments.
  • Add a note or section highlighting parity and any differences in experience between platforms.
GitHub Create Pull Request
← Previous Page 4 of 5 Next →