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 26-50 of 334 flagged pages
Devtest Labs Create environments from ARM templates ...evtest-labs/devtest-lab-create-environment-from-arm.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed automation instructions and scripts exclusively using Azure PowerShell, a tool most commonly associated with Windows environments. While the Azure CLI is briefly mentioned as an alternative, no example or script is provided for it. There are no Linux-specific instructions, nor are Linux shell/CLI examples given equal prominence or detail. The PowerShell approach is presented first and in depth, reinforcing a Windows-centric workflow.
Recommendations
  • Provide a complete example using Azure CLI (az deployment group create) for automating environment creation, including a sample Bash script.
  • Explicitly mention cross-platform compatibility and clarify which steps/tools work on Linux, macOS, and Windows.
  • Ensure that CLI and PowerShell instructions are given equal prominence and detail, possibly in parallel sections.
  • Include notes or examples for Linux users, such as how to install Azure CLI, authenticate, and run deployments from Bash.
  • Review screenshots and terminology to avoid Windows-centric language or UI references where possible.
GitHub Create Pull Request
Devtest Labs Create custom images for lab VMs from VHD files ...n/articles/devtest-labs/devtest-lab-create-template.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is referenced multiple times as a method for creating and uploading custom images, with a dedicated link for PowerShell instructions. Windows tools (such as Sysprep) are mentioned before their Linux equivalents (deprovision), and PowerShell is listed as an upload method alongside AzCopy and Storage Explorer, but no Linux-specific CLI tools (e.g., Bash, Azure CLI) are referenced. The examples and instructions tend to mention Windows options first or exclusively, with Linux options as secondary.
Recommendations
  • Add explicit examples and instructions for Linux users, such as using Azure CLI or Bash scripts for image creation and VHD upload.
  • Include references to Linux-native tools (e.g., dd, qemu-img) for preparing VHDs.
  • Present Windows and Linux options in parallel, rather than listing Windows tools or steps first.
  • Provide links to Linux-specific documentation for image preparation and upload.
  • Ensure screenshots and UI descriptions clarify parity for both OS types.
GitHub Create Pull Request
Devtest Labs Azure DevTest Labs scenarios ...icles/devtest-labs/devtest-lab-guidance-get-started.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. Windows-specific tools and patterns (such as PowerShell scripts and references to Visual Studio and Active Directory) are mentioned exclusively or before Linux equivalents. Most automation and scripting examples reference PowerShell, with no mention of Bash, CLI, or Linux-native approaches. VM creation and customization examples focus on Windows images and tools, and there is a lack of explicit Linux examples or parity in artifact/tool references.
Recommendations
  • Add Linux-focused examples for lab creation, VM provisioning, and automation (e.g., Bash scripts, Azure CLI commands).
  • Include references to Linux tools and artifacts (such as installing common Linux packages, using SSH, or joining Linux domains).
  • Balance mentions of Windows and Linux images when discussing VM creation and formulas.
  • Provide equivalent instructions for deleting VMs/labs using Linux-native tools (e.g., Bash, Azure CLI), not just PowerShell.
  • Reference cross-platform editors and tools (e.g., VS Code, JetBrains IDEs) alongside Windows-only tools like Visual Studio.
  • Explicitly mention support for Linux environments in multi-VM scenarios, with concrete examples.
GitHub Create Pull Request
Devtest Labs Troubleshoot Artifacts on Lab Virtual Machines ...vtest-labs/devtest-lab-troubleshoot-apply-artifacts.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 Windows bias by providing PowerShell commands and Windows-specific troubleshooting steps (such as using File Explorer and Command Prompt) without equivalent Linux examples. Instructions for inspecting logs and running scripts are detailed for Windows, while Linux guidance is relegated to external links. Windows tools and patterns (File Explorer, Command Prompt, Windows log paths) are mentioned exclusively or before Linux equivalents.
Recommendations
  • Provide Linux-specific examples alongside Windows instructions, such as using Bash commands to check artifact status and inspect logs.
  • Include Linux paths and troubleshooting steps for CSE logs and VM Agent logs directly in the documentation, not just as external links.
  • Offer sample commands for common Linux distributions (e.g., Ubuntu, CentOS) for artifact troubleshooting.
  • Balance the use of Windows tools (File Explorer, Command Prompt) with Linux tools (terminal, file system navigation commands).
  • Ensure that script troubleshooting steps include both Windows (CMD/PowerShell) and Linux (Bash/sh) approaches.
  • Add explicit Linux artifact examples and references in the 'Related content' and troubleshooting sections.
GitHub Create Pull Request
Devtest Labs Deploy Azure DevTest Labs (Enterprise Reference Architecture) ...les/devtest-labs/devtest-lab-reference-architecture.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools (Remote Desktop Gateway, RDP), linking to Windows Server documentation, and mentioning PowerShell before Azure CLI or REST APIs for automation. There are no Linux-specific remote access or automation examples, and Windows-centric patterns (RDP, domain join) are described without Linux alternatives.
Recommendations
  • Include Linux remote access options (e.g., SSH, xrdp) alongside RDP and Remote Desktop Gateway.
  • Provide automation examples using Bash scripts and Azure CLI, not just PowerShell.
  • Mention Linux domain join scenarios (e.g., using SSSD or realmd) when discussing domain-based VM access.
  • Reference cross-platform tools and patterns before or alongside Windows-specific ones.
  • Add links to relevant Linux documentation for remote access, automation, and domain integration.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows Server VM deployment examples, referencing PowerShell extensively for automation and common tasks, and omitting explicit Linux VM or Bash/Unix shell examples. Windows-specific tools and workflows (PowerShell, Windows Server) are mentioned before or instead of Linux equivalents, and there is a lack of guidance for Linux users.
Recommendations
  • Add explicit examples for deploying Linux VMs using ARM templates, both in quickstart and automation sections.
  • Include Bash/Azure CLI scripts for common automation tasks currently only demonstrated with PowerShell (e.g., creating custom images, uploading VHDs, adding users).
  • Reference Linux base images and workflows alongside Windows Server in quickstart and template selection instructions.
  • Balance mentions of PowerShell with equivalent Bash/CLI instructions throughout the documentation.
  • Provide links to Linux-focused resources and scripts in the GitHub repository and Azure documentation.
GitHub 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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a Windows bias by presenting Windows-based VM creation as the first example, referencing Windows images and tools before Linux equivalents, and providing PowerShell-specific guidance and output. Linux examples are present but appear after Windows ones, and Windows artifacts are highlighted in sample outputs.
Recommendations
  • Alternate the order of Windows and Linux examples, or present both side-by-side to ensure parity.
  • Include Linux-based VM creation as the first example or in parallel with Windows examples.
  • Provide equal emphasis on Linux artifacts in sample outputs, not just Windows ones.
  • Expand explanations for both Bash and PowerShell, ensuring neither is prioritized.
  • Reference Linux tools and connection methods (e.g., SSH) with the same prominence as Windows tools (e.g., Remote Desktop).
  • Add more Linux-specific scenarios and troubleshooting tips to match the Windows coverage.
GitHub Create Pull Request
Devtest Labs Upload a VHD file to lab storage by using Storage Explorer ...-labs/devtest-lab-upload-vhd-using-storage-explorer.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the primary command-line method for obtaining the storage account name and uploading VHDs. The steps and screenshots focus on PowerShell and do not mention or provide equivalent Linux shell commands (such as Azure CLI or Bash). The related content also links to PowerShell-specific instructions before mentioning alternatives. While Azure Storage Explorer is cross-platform, the documentation does not provide Linux/macOS-specific guidance or examples.
Recommendations
  • Add instructions and screenshots for obtaining the storage account name using Azure CLI or Bash, which are commonly used on Linux/macOS.
  • Include examples for uploading VHDs using Azure CLI, azcopy, or other cross-platform tools, alongside PowerShell.
  • Reorder or balance references to PowerShell and non-Windows tools so that Linux/macOS methods are presented equally or in parallel.
  • Explicitly mention that all steps can be performed on Linux/macOS, and clarify any OS-specific differences in Storage Explorer usage.
  • Provide links to Linux/macOS-specific documentation in the 'Related content' section.
GitHub Create Pull Request
Devtest Labs Extend Azure DevTest Labs with Azure Functions ...es/devtest-labs/extend-devtest-labs-azure-functions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-centric tools and workflows, such as Visual Studio, PowerShell, and Windows Update artifacts. All step-by-step instructions and screenshots use Visual Studio, with no mention of cross-platform alternatives like VS Code or CLI-based workflows. The sample scenario and artifacts are Windows-specific, and Linux equivalents (e.g., Linux update artifacts) are not discussed. PowerShell is referenced as a primary automation tool, and Linux shell or Bash alternatives are absent.
Recommendations
  • Add equivalent examples and instructions for Linux environments, such as using VS Code, Azure CLI, or other cross-platform editors.
  • Include Linux-specific artifacts (e.g., Linux update or patching artifacts) in sample scenarios and walkthroughs.
  • Provide step-by-step deployment and configuration instructions for Linux users, including screenshots and commands for Bash or CLI workflows.
  • Reference cross-platform automation tools (e.g., Azure CLI, Bash scripts) alongside PowerShell, and avoid presenting Windows tools first or exclusively.
  • Ensure parity in documentation by explicitly mentioning support for both Windows and Linux VMs in DevTest Labs and Azure Functions scenarios.
GitHub Create Pull Request
Devtest Labs Create a network isolated lab ...s/blob/main/articles/devtest-labs/network-isolation.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias by referencing a PowerShell script as the sole method for converting an existing lab to network isolation, without mentioning or providing equivalent Bash or Azure CLI examples. The script is presented as the primary automation option, and there are no Linux-specific instructions or parity for non-Windows users. While Azure CLI is briefly mentioned as an automation alternative, no concrete CLI or Bash examples are provided, and PowerShell is referenced first and exclusively in the conversion context.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for converting an existing lab to network isolation, alongside the PowerShell script.
  • Explicitly mention cross-platform options (e.g., Azure CLI, Bash) wherever automation is discussed, and offer sample commands/scripts.
  • Avoid presenting PowerShell as the only or primary automation tool; list Azure CLI and Bash alternatives in parallel.
  • Add a section or note for Linux/macOS users, clarifying how they can perform the same tasks without PowerShell.
  • Ensure that all referenced scripts/tools are available and documented for both Windows and Linux environments.
GitHub Create Pull Request
Devtest Labs Move DevTest Labs to another region ...cs/blob/main/articles/devtest-labs/how-to-move-labs.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing PowerShell-centric instructions and examples, referencing Windows-specific tools (such as AzCopy and PowerShell), and linking to articles focused on Windows VM management. Linux alternatives (e.g., Bash, CLI) are mentioned only briefly or not at all, and example scripts are exclusively in PowerShell. There is no parity in step-by-step guidance for Linux users, nor are Linux command-line examples provided for key operations.
Recommendations
  • Include equivalent Bash/CLI examples for all PowerShell commands, especially for disk operations and AzCopy usage.
  • Reference both Windows and Linux VM management articles when discussing OS disk swaps and other VM-specific tasks.
  • Provide explicit instructions for performing steps in Linux environments, such as using Azure CLI in Bash or Cloud Shell (Bash tab).
  • Clarify that AzCopy and other tools are cross-platform, and show usage examples for Linux/macOS.
  • Ensure screenshots and UI references are OS-neutral or include both Windows and Linux perspectives where relevant.
GitHub Create Pull Request
Devtest Labs Import virtual machines from another lab ...vtest-labs/import-virtual-machines-from-another-lab.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell scripting examples for importing VMs, referencing a .ps1 script, and omitting any Linux shell or cross-platform CLI examples. The PowerShell method is described first and in greater detail, while no Linux-native tools or instructions (such as Bash, Azure CLI, or shell scripts) are mentioned. This may disadvantage users on Linux or macOS platforms.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and work natively on Linux and macOS.
  • Provide Bash shell script samples for the import process, especially for users who prefer scripting outside of PowerShell.
  • Clarify that PowerShell Core is available cross-platform, but explicitly show how to run the script on Linux/macOS, including installation steps if needed.
  • Reorder or balance the documentation so that REST API and CLI methods are presented before or alongside PowerShell, to avoid Windows-first impressions.
  • Mention any platform requirements or limitations for the provided scripts, and offer alternatives for non-Windows environments.
GitHub Create Pull Request
Devtest Labs How to delete and export personal data ...n/articles/devtest-labs/personal-data-delete-export.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page provides only Azure PowerShell examples for exporting personal data, with no mention of Linux-native tools, Bash, or cross-platform alternatives. The use of PowerShell and Windows-centric Azure modules is presented as the sole method, implicitly prioritizing Windows users and omitting guidance for Linux or macOS environments.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and works natively on Linux and macOS.
  • Include Bash script samples for exporting data, showing how to use az commands and handle authentication/storage.
  • Explicitly mention that the export process can be performed on Linux/macOS, and provide step-by-step instructions for those platforms.
  • Reference relevant documentation for Azure CLI and REST API methods for data export.
  • Clarify any platform-specific requirements or limitations, ensuring users on all operating systems understand their options.
GitHub Create Pull Request
Devtest Labs Quickstart: Create a lab with REST API ...n/articles/devtest-labs/quickstarts/create-lab-rest.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell for all command-line examples, assumes the presence of the Az PowerShell module, and provides no equivalent instructions for Linux users (e.g., Bash, curl, Azure CLI). Windows tools and patterns are mentioned throughout, with no mention of Linux alternatives or cross-platform options.
Recommendations
  • Provide parallel examples using Bash and curl or Azure CLI for Linux/macOS users.
  • Mention installation and usage of Azure CLI as an alternative to PowerShell.
  • Clarify that the REST API can be invoked from any platform and provide generic HTTP request examples.
  • Reorder sections or add notes to avoid implying Windows/PowerShell is the default or only supported environment.
  • Add troubleshooting or prerequisites for Linux environments (e.g., installing curl, jq, Azure CLI).
GitHub Create Pull Request
Devtest Labs Azure DevTest Labs usage across multiple labs and subscriptions ...abs/report-usage-across-multiple-labs-subscriptions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 Windows bias by primarily referencing PowerShell for automation and scripting, mentioning Windows-centric tools (PowerShell, SQL Server, Power BI) before or instead of Linux alternatives, and omitting explicit Linux or cross-platform CLI examples. There is no mention of Bash, Azure CLI, or Linux-specific workflows, and PowerShell is presented as the default scripting language for Azure Functions and Automation Runbooks.
Recommendations
  • Add examples using Azure CLI and Bash scripts for exporting resource usage, alongside PowerShell.
  • Explicitly mention that Azure Functions and Automation Runbooks support Python and other cross-platform languages, and provide sample code in those languages.
  • Include Linux-friendly storage and visualization tools (e.g., PostgreSQL, Grafana) as alternatives to SQL Server and Power BI.
  • Reorder examples to present cross-platform or Linux-native options before or alongside Windows-centric tools.
  • Clarify that all steps can be performed from Linux, macOS, and Windows environments, and provide platform-agnostic instructions where possible.
GitHub Create Pull Request
Devtest Labs Specify resource group for Azure VMs in DevTest Labs ...b/main/articles/devtest-labs/resource-group-control.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a detailed PowerShell script example for configuring resource groups for Azure DevTest Labs VMs, but does not offer equivalent examples for Linux users (e.g., Bash shell). The scripting section is Windows-centric, and PowerShell is presented as the primary automation method, with no mention of Linux shell alternatives or cross-platform CLI usage. This may disadvantage users working on Linux or macOS platforms.
Recommendations
  • Add a Bash shell example using the Azure CLI for Linux/macOS users, demonstrating the same resource group configuration steps.
  • Clarify that the Azure CLI commands used in PowerShell are cross-platform and can be run in Bash, but provide explicit Bash syntax for variables and command chaining.
  • Include a note or section highlighting cross-platform compatibility and provide links to Azure CLI installation guides for Linux/macOS.
  • Ensure that future scripting examples are presented in both PowerShell and Bash (or generic CLI), or use a neutral format where possible.
GitHub Create Pull Request
Devtest Labs Troubleshoot VM deployment failures ...es/devtest-labs/troubleshoot-vm-deployment-failures.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing troubleshooting steps and examples that reference PowerShell scripts for VM deployment, without mentioning or providing equivalent instructions for Linux users (such as Azure CLI or Bash). The guidance assumes familiarity with Windows-centric tools and patterns, and does not offer parity for Linux environments.
Recommendations
  • Include Linux-specific examples, such as using Azure CLI or Bash scripts, alongside PowerShell instructions for ARM template deployments.
  • When referencing scripts or automation, present both Windows (PowerShell) and Linux (CLI/Bash) options, or link to equivalent documentation.
  • Avoid assuming the use of Windows tools by default; explicitly mention cross-platform alternatives where applicable.
  • Add troubleshooting steps and error resolution guidance relevant to Linux users, ensuring equal coverage for both platforms.
GitHub Create Pull Request
Devtest Labs Use commands to start and stop lab VMs ...t-labs/use-command-line-start-stop-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is presented first in all major sections, with detailed scripting examples. The Azure CLI section provides both Bash and Windows command syntax, but Windows batch syntax is given equal prominence to Bash, and Windows-specific commands (e.g., REM for comments, set for variables) are included. There is no explicit Linux example or mention of Linux-specific considerations, and the documentation assumes familiarity with Windows tools and patterns throughout.
Recommendations
  • Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI first to balance platform representation.
  • In CLI examples, prioritize Bash syntax and provide Windows batch syntax as a secondary note, since Bash is more common on Linux and macOS.
  • Explicitly mention Linux and macOS compatibility for Azure CLI, and provide troubleshooting notes or tips for those platforms if needed.
  • Add a note clarifying that PowerShell Core is available cross-platform, and provide examples for running PowerShell scripts on Linux/macOS.
  • Include links to installation guides for Azure CLI and PowerShell on Linux and macOS, not just Windows.
  • Review terminology to avoid Windows-centric language (e.g., avoid assuming 'set' and 'REM' are familiar to all users).
GitHub Create Pull Request
Devtest Labs Add an Artifact Repository to Your Lab .../main/articles/devtest-labs/add-artifact-repository.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell environments. All command-line automation examples use Azure PowerShell, with no equivalent Bash or Linux shell examples provided. The deployment section instructs users to use PowerShell first, and the only script provided is a PowerShell script. There are no Linux-specific instructions, nor are there CLI or Bash script equivalents shown alongside PowerShell. The documentation assumes familiarity with Windows tools and patterns, and does not address Linux users' needs for parity in automation or scripting.
Recommendations
  • Provide equivalent Azure CLI (az) examples for all PowerShell scripts and deployment instructions.
  • Include Bash shell script samples for Linux users, especially for ARM template deployment and repository addition.
  • Explicitly mention cross-platform compatibility and note any differences or requirements for Linux environments.
  • Reorder sections to present Azure CLI and Bash options alongside or before PowerShell, to avoid Windows-first bias.
  • Add troubleshooting notes or links relevant to Linux environments, not just Windows or PowerShell.
GitHub Create Pull Request
Devtest Labs Azure DevTest Labs concepts ...lob/main/articles/devtest-labs/devtest-lab-concepts.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows virtual machines before Linux equivalents, omitting explicit mention or examples of Linux VM creation and management, and listing Windows-specific tools (e.g., Visual Studio, Fiddler) as artifact examples. There are no Linux-focused examples, tools, or references, and the only deep link for VM information is for Windows VMs.
Recommendations
  • Add explicit references and links to Linux virtual machines in Azure, alongside or before Windows VM references.
  • Provide examples of artifacts and tools relevant to Linux environments (e.g., Git, Apache, Nginx, Python).
  • Include sample ARM templates or walkthroughs for creating and managing Linux VMs and environments.
  • Mention Linux-compatible base images and highlight their use cases.
  • Balance the documentation by alternating or parallelizing Windows and Linux examples and terminology throughout the page.
GitHub Create Pull Request
Devtest Labs Specify resource group for Azure VMs in DevTest Labs ...b/main/articles/devtest-labs/resource-group-control.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a detailed PowerShell script for configuring resource groups for Azure DevTest Labs VMs, but does not offer equivalent examples for Linux users (e.g., Bash or shell scripts). The scripting section is Windows-centric, and PowerShell is presented as the primary automation method, with no mention of Linux command-line alternatives or cross-platform usage. This may hinder Linux users from easily following the instructions.
Recommendations
  • Add a Bash or shell script example using Azure CLI for Linux/macOS users.
  • Explicitly mention that the Azure CLI commands can be run on any platform, and provide platform-agnostic instructions.
  • Reorder or supplement the scripting section to present both PowerShell and Bash examples side-by-side.
  • Clarify tool requirements and compatibility for both Windows and Linux environments.
GitHub Create Pull Request
Devtest Labs Upload a VHD file to Azure DevTest Labs by using AzCopy ...es/devtest-labs/devtest-lab-upload-vhd-using-azcopy.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. AzCopy is described as a Windows-only utility, and all usage instructions and examples assume a Windows environment (Command Prompt, Windows file paths, and installation locations). PowerShell is referenced as the primary scripting method, with screenshots and instructions focused on Windows tools. There are no examples or guidance for Linux or macOS users, nor any mention of cross-platform alternatives or parity.
Recommendations
  • Update the documentation to reference AzCopy v10+, which is cross-platform and available for Windows, Linux, and macOS.
  • Provide Linux and macOS installation instructions for AzCopy, including download links and example commands.
  • Include example commands for uploading VHD files using AzCopy on Linux/macOS (e.g., bash shell examples).
  • Mention and demonstrate how to use Azure CLI or REST API for VHD uploads as platform-agnostic alternatives.
  • Avoid referring to AzCopy as 'Windows-only' and clarify which versions are cross-platform.
  • Add screenshots and instructions for non-Windows environments where relevant.
GitHub Create Pull Request
Devtest Labs How to delete and export personal data ...n/articles/devtest-labs/personal-data-delete-export.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing Azure PowerShell examples and instructions for exporting personal data. There are no equivalent examples or guidance for Linux users (e.g., using Azure CLI, Bash, or cross-platform tools). The use of PowerShell and Windows-centric Azure modules is presented as the sole method, implicitly prioritizing Windows environments and tools.
Recommendations
  • Add equivalent export instructions using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Provide Bash script examples for exporting personal data, demonstrating how Linux users can accomplish the same tasks.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, but also highlight Azure CLI as an alternative.
  • Reorder or parallelize examples so that Windows and Linux methods are presented together, avoiding implicit prioritization.
  • Include notes or links to documentation for using Azure DevTest Labs with Linux environments.
GitHub Create Pull Request
Devtest Labs Quickstart: Create a lab with REST API ...n/articles/devtest-labs/quickstarts/create-lab-rest.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows, exclusively using PowerShell for all examples and instructions. Windows tools and patterns (such as the Az PowerShell module and Windows-style file paths) are mentioned without any reference to Linux equivalents. There are no bash, curl, or Azure CLI examples, and Linux users are not provided with alternative instructions. The documentation assumes a Windows environment throughout.
Recommendations
  • Add equivalent examples using Bash and curl for REST API calls.
  • Include instructions for using Azure CLI, which is cross-platform.
  • Show how to authenticate and manage Azure resources from Linux/macOS environments.
  • Use platform-neutral file paths and variable names, or clarify differences.
  • Explicitly mention that the steps can be performed on Linux/macOS and provide links to relevant setup guides.
  • Present both Windows and Linux examples side-by-side where possible.
GitHub Create Pull Request
Devtest Labs Create a network isolated lab ...s/blob/main/articles/devtest-labs/network-isolation.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing a PowerShell script as the only automation method for converting an existing lab to network isolation. There are no equivalent Bash, Azure CLI, or Linux shell examples provided for this key scenario. The mention of PowerShell and .ps1 scripts, without cross-platform alternatives, may exclude Linux users or those preferring non-Windows tooling.
Recommendations
  • Provide Azure CLI or Bash script equivalents for the PowerShell script (Convert-DtlLabToIsolatedNetwork.ps1) to enable Linux/macOS users to perform the same conversion.
  • When mentioning automation, list Azure CLI and Bash options alongside PowerShell, or reference cross-platform tools first.
  • Add explicit examples and instructions for Linux environments, including screenshots or terminal commands where appropriate.
  • Clarify that all portal-based steps are OS-agnostic, and highlight any steps that require Windows-specific tools, offering alternatives where possible.
GitHub Create Pull Request
← Previous Page 2 of 14 Next →