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 76-100 of 334 flagged pages
Devtest Labs Azure CLI Samples ...re-docs/blob/main/articles/devtest-labs/samples-cli.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 Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by focusing on creating Windows VMs, labeling sample scripts as 'powershell' despite referencing bash scripts, and omitting explicit Linux VM creation examples. The terminology and script language tags suggest a preference for Windows tools and workflows, with no parity for Linux-specific scenarios or instructions.
Recommendations
  • Include explicit examples for creating Linux VMs alongside Windows VM examples.
  • Correct code block language tags to 'bash' or 'azurecli' where appropriate, instead of 'powershell', to accurately reflect the script type.
  • Add notes or sections highlighting differences or additional steps for Linux users (e.g., SSH authentication, Linux image selection).
  • Ensure that documentation does not assume Windows as the default platform and provides equal visibility to Linux workflows.
GitHub Create Pull Request
Devtest Labs Define VM start order with Azure Automation ...devtest-labs/start-machines-use-automation-runbooks.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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell for scripting and automation, with no mention of Bash, Python, or other cross-platform alternatives. All examples and instructions are tailored to Windows-centric tools and workflows (PowerShell, Azure Automation Run As Accounts, PowerShell jobs), with no Linux-specific guidance or parity. The page assumes familiarity with Windows patterns and does not provide equivalent steps for Linux users or those using non-Windows environments.
Recommendations
  • Provide equivalent Bash or Python script examples for Linux users, using Azure CLI or REST API calls.
  • Include instructions for creating and running automation scripts on Linux-based Azure Automation accounts or using hybrid workers.
  • Mention cross-platform tools (e.g., Azure CLI, Python SDK) alongside PowerShell, and offer guidance for both Windows and Linux environments.
  • Reorder examples or add parallel sections so that Linux options are presented alongside or before Windows-specific instructions.
  • Clarify which steps are platform-agnostic and which require adaptation for Linux, and link to relevant Linux documentation.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell instructions and examples before Azure CLI/Bash equivalents, using Windows-centric tools (PowerShell, Windows batch syntax), and referencing Windows environments and commands more prominently. While Bash examples are included, Windows/PowerShell approaches are given precedence and more detailed coverage.
Recommendations
  • Alternate the order of examples so that Bash/Azure CLI instructions are presented before PowerShell/Windows examples in some sections.
  • Provide equal detail and explanation for Bash/Azure CLI workflows as is given for PowerShell.
  • Avoid using Windows batch syntax (e.g., 'set VAR=VALUE') unless absolutely necessary, and clarify when Bash syntax is preferred for cross-platform use.
  • Explicitly mention Linux/macOS compatibility and environments where appropriate, including installation and usage notes for Azure CLI on those platforms.
  • Add troubleshooting or environment-specific notes for Linux users, such as file permissions, shell differences, or common issues.
  • Review related content links to ensure parity between PowerShell and CLI/Bash documentation.
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-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 Windows bias by providing troubleshooting steps and examples that reference PowerShell scripts for VM deployment, without mentioning or providing equivalent instructions for Linux users (e.g., Azure CLI or Bash). Windows tooling (PowerShell) is mentioned as the default method for ARM template deployment, and no Linux-specific tools or examples are offered.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell instructions for ARM template deployment.
  • Explicitly mention cross-platform tools and provide parity in troubleshooting steps for both Windows and Linux users.
  • Reorder examples so that Windows and Linux methods are presented together, or alternate which is presented first.
  • Add notes or links to Linux-specific documentation where relevant.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-add-vm.md .../blob/main/articles/devtest-labs/devtest-lab-add-vm.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by using Windows 11 Pro as the example image for VM creation, mentioning PowerShell scripts as the primary method for copying VMs, and omitting explicit Linux VM creation examples or Linux-specific instructions. While Azure CLI and ARM templates are referenced, no Linux-centric workflow or screenshots are provided, and Windows terminology/tools appear first or exclusively.
Recommendations
  • Include explicit Linux VM creation examples, such as selecting Ubuntu or CentOS images, and show relevant screenshots.
  • Provide Linux-specific instructions for connecting to VMs (e.g., SSH commands) alongside or before Windows RDP instructions.
  • When referencing scripts for copying VMs, include both PowerShell and Bash/Azure CLI alternatives, and link to Linux-friendly guides.
  • Ensure that examples and screenshots alternate between Windows and Linux scenarios, or present them in parallel.
  • Mention Linux tools and patterns (e.g., SSH, cloud-init) where relevant, and avoid assuming Windows as the default OS.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-delete-lab-vm.md ...ain/articles/devtest-labs/devtest-lab-delete-lab-vm.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides step-by-step instructions for deleting lab VMs and labs primarily through the Azure portal (GUI), which is cross-platform. However, for automation, only a PowerShell script is provided, with no equivalent example for Bash, Azure CLI, or other Linux-friendly tools. PowerShell is traditionally a Windows-centric tool, and its exclusive use here may disadvantage Linux users or those who prefer Bash/CLI workflows.
Recommendations
  • Add equivalent automation examples using Azure CLI (az), which is cross-platform and widely used on Linux and macOS.
  • Provide Bash script examples for deleting all VMs in a lab, leveraging Azure CLI commands.
  • Explicitly mention that PowerShell Core is available cross-platform, but also offer alternatives for users who do not wish to use PowerShell.
  • Ensure future documentation includes both PowerShell and Azure CLI/Bash examples side-by-side for parity.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-vmcli.md ...s/blob/main/articles/devtest-labs/devtest-lab-vmcli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by presenting Windows-based VM creation as the first example, referencing Windows images and tools before Linux equivalents, and providing explicit PowerShell-specific guidance. Although Linux examples and bash instructions are present, Windows scenarios and tooling are prioritized or explained first, and Windows artifacts are shown in sample outputs.
Recommendations
  • Alternate the order of Windows and Linux examples, or present Linux examples first in some sections.
  • Include more Linux-focused sample outputs (e.g., showing Linux artifacts in output JSON).
  • Provide equal detail for both Bash and PowerShell instructions, and avoid giving extra emphasis to PowerShell-specific syntax.
  • Explicitly mention Linux tools and patterns where Windows tools are referenced.
  • Ensure that both Windows and Linux VM creation commands are given equal prominence and explanation.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-concepts.md ...lob/main/articles/devtest-labs/devtest-lab-concepts.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Windows virtual machines before Linux equivalents, omitting explicit mention or examples of Linux VMs, and listing Windows-specific tools (e.g., Visual Studio, Fiddler) as artifact examples. There are no Linux-focused examples, tools, or references, and the guidance for VM creation and management is centered around Windows environments.
Recommendations
  • Include references and links to both Windows and Linux virtual machine documentation (e.g., add a link to 'Linux virtual machines in Azure').
  • Provide examples of Linux VM creation and management alongside Windows examples.
  • List Linux-relevant tools and artifacts (e.g., Git, Apache, Nginx, Python) as artifact examples.
  • Ensure artifact and template repository examples include both Windows and Linux templates.
  • Balance the order of presentation so that Windows and Linux options are introduced together or Linux is mentioned first in some cases.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/troubleshoot-vm-deployment-failures.md ...es/devtest-labs/troubleshoot-vm-deployment-failures.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the primary method for deploying VMs with ARM templates, without mentioning or providing examples for Linux-native tools (such as Azure CLI or Bash). The troubleshooting steps and examples are oriented towards Windows users, and there is no parity for Linux users in terms of command-line instructions or tool recommendations.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell for ARM template deployments.
  • Explicitly mention cross-platform tools and provide guidance for both Windows and Linux users.
  • Add troubleshooting steps and command examples relevant to Linux environments.
  • Ensure that references to command-line tools do not assume a Windows-first workflow.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/resource-group-control.md ...b/main/articles/devtest-labs/resource-group-control.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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/Powershell-centric, and there is no mention of Linux command-line tools or cross-platform alternatives. This may disadvantage users who primarily use Linux or non-Windows environments.
Recommendations
  • Add a Bash shell example using the Azure CLI for Linux/macOS users, demonstrating the same resource group configuration.
  • Explicitly mention that the Azure CLI commands shown in PowerShell are cross-platform, and provide syntax for Bash where it differs.
  • Include notes or links to documentation for using Azure CLI on Linux/macOS.
  • Consider reordering scripting examples so that cross-platform (Azure CLI in Bash) comes before or alongside PowerShell examples.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/start-machines-use-automation-runbooks.md ...devtest-labs/start-machines-use-automation-runbooks.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 scripting and Azure Automation examples, with no mention of Bash, Azure CLI, or Linux-native approaches. All code samples, instructions, and tool references are Windows-centric, and there are no alternative examples or guidance for Linux users. The workflow assumes familiarity with PowerShell and Windows tooling, which may disadvantage users on Linux or macOS platforms.
Recommendations
  • Provide equivalent examples using Bash and Azure CLI, demonstrating how to achieve the same VM startup order functionality on Linux.
  • Include instructions for creating and running runbooks with non-PowerShell scripts in Azure Automation.
  • Mention cross-platform tools and patterns, such as Azure CLI or REST API, and link to relevant documentation.
  • Add a section discussing platform differences and how Linux/macOS users can adapt the workflow.
  • Ensure that prerequisites and step-by-step instructions are not dependent on Windows-only tools.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/add-artifact-repository.md .../main/articles/devtest-labs/add-artifact-repository.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias primarily through its heavy reliance on Azure PowerShell for automation and scripting examples, with detailed PowerShell scripts and deployment instructions provided. PowerShell is a Windows-centric tool, and its usage is emphasized before mentioning Azure CLI or REST API alternatives. The ARM template deployment section also lists PowerShell as the first method, and the only full script provided is in PowerShell. There are no Linux shell (bash) or cross-platform CLI examples, and no mention of Linux-specific tools or workflows.
Recommendations
  • Provide equivalent examples using Azure CLI (az), which is cross-platform and widely used on Linux and macOS.
  • Include bash shell script samples for ARM template deployment and artifact repository addition.
  • Reorder automation sections to present CLI and REST API options before or alongside PowerShell, rather than after.
  • Explicitly mention that all steps can be performed from Linux/macOS environments using CLI and REST API.
  • Add notes or links to Linux-specific guidance where relevant, such as authenticating with managed identities or using tokens.
  • Ensure screenshots and UI instructions do not assume Windows-only environments.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/best-practices-distributive-collaborative-development-environment.md ...ces-distributive-collaborative-development-environment.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by referencing Azure PowerShell and PowerShell scripts as primary tools for resource management and automation. There is no mention of Linux equivalents (such as Bash scripts or Azure CLI), nor are examples provided for Linux users. The focus on PowerShell and lack of Linux-specific guidance may hinder Linux users from fully leveraging the collaborative development features described.
Recommendations
  • Include examples using Azure CLI and Bash scripts alongside PowerShell examples.
  • Explicitly mention Linux-compatible tools and workflows for managing DevTest Labs resources.
  • Provide links to documentation or tutorials for Linux users on setting up and automating DevTest Labs environments.
  • Ensure references to scripting and automation are platform-neutral or include both Windows and Linux options.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/add-artifact-vm.md ...ocs/blob/main/articles/devtest-labs/add-artifact-vm.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 only Azure PowerShell examples for scripting and automation, with no equivalent CLI or Bash examples for Linux users. The prerequisites and instructions for command-line operations exclusively reference PowerShell, and the example script is written entirely in PowerShell. There is no mention of Azure CLI, Bash, or Linux-specific tooling, and the documentation structure presents Windows-centric tools and patterns first and exclusively.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples for adding artifacts to VMs, including full scripts and command breakdowns.
  • Include Linux-specific prerequisites, such as instructions for installing and using Azure CLI on Linux systems.
  • Explicitly mention that artifacts can run Bash commands and provide examples of doing so.
  • Balance the documentation structure so that Windows and Linux tooling are presented with equal prominence, or use tabs to separate PowerShell and CLI/Bash instructions.
  • Reference cross-platform tools and patterns where possible, and avoid assuming PowerShell as the default automation environment.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/automate-add-lab-user.md ...ob/main/articles/devtest-labs/automate-add-lab-user.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell examples and tools throughout. PowerShell cmdlets are used for key steps such as obtaining role definition GUIDs and principal IDs, and deployment instructions are exclusively given using PowerShell. There is minimal coverage of Azure CLI, and no explicit Linux shell (bash) examples or instructions are provided. Windows-centric tools and patterns (e.g., New-Guid, Get-AzADUser) are mentioned without Linux equivalents or cross-platform alternatives.
Recommendations
  • Provide equivalent bash/Azure CLI examples for all PowerShell commands, especially for obtaining role definition IDs and principal IDs.
  • Include instructions and examples for deploying Resource Manager templates using Azure CLI (az deployment group create) and reference Linux shell usage.
  • Mention cross-platform tools for GUID generation, such as uuidgen in Linux/macOS, alongside New-Guid.
  • Ensure that CLI examples are as detailed and prominent as PowerShell examples, and consider presenting CLI and PowerShell side-by-side.
  • Add explicit notes or sections for Linux/macOS users, clarifying any differences in command syntax, file paths, or prerequisites.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/configure-lab-remote-desktop-gateway.md ...s/devtest-labs/configure-lab-remote-desktop-gateway.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. It exclusively references Windows-centric technologies (Remote Desktop Gateway, RDP, IIS, PowerShell scripts, System Center VMM, RDGatewayFedAuth.msi) and provides only Windows/PowerShell examples for certificate creation and automation. There are no Linux equivalents or cross-platform alternatives mentioned for remote access, certificate management, or gateway setup. The documentation assumes the use of RDP and Windows-based tooling throughout, with no guidance for Linux administrators or users.
Recommendations
  • Add instructions and examples for Linux-based remote access solutions, such as using xrdp, FreeRDP, or Remmina.
  • Provide Linux shell (bash) commands for certificate creation, thumbprint extraction, and Base64 encoding (e.g., using openssl).
  • Include automation examples using Azure CLI, bash scripts, or Ansible alongside PowerShell.
  • Mention Linux-compatible gateway software or alternatives to RDGatewayFedAuth.msi and IIS, such as Apache Guacamole or OpenSSH tunneling.
  • Clarify whether Azure DevTest Labs supports Linux VMs for remote desktop access and, if so, document the setup and connection process.
  • Ensure that references to RDP are accompanied by notes or links about Linux client compatibility and alternatives.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/create-environment-service-fabric-cluster.md ...test-labs/create-environment-service-fabric-cluster.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a Windows-first bias, most notably in the cluster creation workflow where Windows is the default OS and the only example for certificate creation is provided via a PowerShell script (.ps1) with instructions to run it in PowerShell. There are no equivalent Linux/bash examples or guidance for Linux users, despite the product supporting both Windows and Linux clusters.
Recommendations
  • Provide explicit Linux examples alongside Windows, especially for certificate creation (e.g., using OpenSSL commands in bash).
  • When describing OS selection, avoid defaulting to Windows or clarify that both Windows and Linux are supported equally.
  • Include instructions for Linux users on how to generate the required certificate and fill in the necessary fields.
  • Ensure that screenshots and step-by-step instructions are not exclusively Windows-centric.
  • Where scripts are referenced (such as Create-ClusterCertificate.ps1), provide or link to equivalent bash scripts or OpenSSL command lines for Linux environments.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-add-devtest-user.md .../articles/devtest-labs/devtest-lab-add-devtest-user.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 only Azure PowerShell scripting examples for automation, referencing Microsoft accounts and Windows Server documentation, and omitting any Linux-native CLI (e.g., Azure CLI/bash) examples. The PowerShell instructions are detailed and prioritized alongside the portal, with no mention of Linux shell equivalents or cross-platform automation options.
Recommendations
  • Add Azure CLI (az) examples for all automation steps, showing how to add users and assign roles using bash or other Linux shells.
  • Explicitly mention that Azure CLI is cross-platform and provide installation/use instructions for Linux and macOS.
  • Reference Linux user account concepts or clarify that Microsoft accounts are required regardless of OS.
  • Balance screenshots and step-by-step instructions with examples from Linux environments (e.g., terminal screenshots, bash commands).
  • Update prerequisites to include Azure CLI as an alternative to PowerShell, with links to relevant documentation.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/deploy-nested-template-environments.md ...es/devtest-labs/deploy-nested-template-environments.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell and Visual Studio as primary deployment tools, both of which are traditionally Windows-centric. The deployment instructions mention Azure PowerShell before Azure CLI, and the related content highlights Visual Studio, a Windows-first IDE, without mentioning cross-platform alternatives. There are no explicit Linux or macOS examples or tool recommendations.
Recommendations
  • Provide explicit Linux/macOS deployment examples using Azure CLI, Bash, or other cross-platform tools.
  • Mention Visual Studio Code as a cross-platform alternative to Visual Studio for ARM template development and deployment.
  • List Azure CLI before or alongside Azure PowerShell when describing deployment commands.
  • Include notes or links for Linux users on installing and using Azure CLI and other relevant tools.
  • Ensure all code samples and instructions are platform-neutral or offer platform-specific variants.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-add-tag.md ...blob/main/articles/devtest-labs/devtest-lab-add-tag.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references managing tags using PowerShell or Azure CLI, but lists PowerShell before Azure CLI and does not provide any explicit examples for either. There are no Linux-specific instructions, screenshots, or terminal examples. The overall workflow is described through the Azure Portal UI, which is cross-platform, but the mention of PowerShell first and the lack of Linux/CLI parity suggests a mild Windows bias.
Recommendations
  • Provide explicit Azure CLI examples for managing tags, as Azure CLI is cross-platform and preferred by many Linux users.
  • When mentioning command-line tools, list Azure CLI before or alongside PowerShell to avoid implying a Windows-first approach.
  • Include sample commands for both PowerShell and Azure CLI to ensure parity.
  • Add a note or section clarifying that all steps can be performed from any OS via the Azure Portal or Azure CLI.
  • Where screenshots are used, ensure they do not show Windows-specific UI elements (e.g., Windows file dialogs) if not necessary.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-artifact-author.md ...n/articles/devtest-labs/devtest-lab-artifact-author.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 only PowerShell-based examples for artifact creation and execution, referencing Windows-specific tools and scripts (e.g., powershell.exe, artifact.ps1, startChocolatey.ps1), and omitting equivalent Linux shell script examples. The step-by-step instructions and sample downloads are exclusively for Windows artifacts, with no guidance or samples for Linux-based artifacts. Windows terminology and tools are presented first and exclusively, leaving Linux users without clear instructions or parity.
Recommendations
  • Add parallel Linux examples throughout the documentation, including sample artifact definition files and shell scripts (e.g., Bash, sh).
  • Provide step-by-step instructions for creating and deploying Linux artifacts, including downloading and customizing Linux sample artifacts from the public repository.
  • Show equivalent Linux commands and script references in the 'runCommand' section (e.g., bash ./artifact.sh), and clarify how to handle secure parameters in Linux scripts.
  • Include screenshots or folder structure examples for Linux artifacts.
  • Ensure that both Windows and Linux options are presented equally in all relevant sections, not just mentioned as possible values.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-environment-from-arm.md ...evtest-labs/devtest-lab-create-environment-from-arm.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 by providing detailed PowerShell automation examples and referencing Azure PowerShell as a prerequisite, while only briefly mentioning Azure CLI as an alternative. There are no Linux shell (bash) examples, and the PowerShell workflow is presented first and in greater detail. The page lacks parity in step-by-step instructions for Linux users and does not address platform-specific considerations for non-Windows environments.
Recommendations
  • Provide equivalent bash/Azure CLI scripts for automating environment creation, with step-by-step instructions.
  • List both PowerShell and CLI options equally in prerequisites and automation sections, rather than prioritizing PowerShell.
  • Explicitly mention platform compatibility for all tools and scripts, and note any differences in usage on Linux/macOS.
  • Include screenshots or terminal output examples from Linux environments where relevant.
  • Add troubleshooting notes for common issues encountered on Linux/macOS (e.g., authentication, file paths, permissions).
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-template.md ...n/articles/devtest-labs/devtest-lab-create-template.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 mentioned as an alternative method for creating custom images, and uploading VHD files via PowerShell is listed as an option. Windows tools (Sysprep) are referenced before their Linux equivalents (deprovision), and PowerShell is highlighted as a primary automation tool, with no mention of Bash, CLI, or Linux-native scripting alternatives. The upload instructions and examples focus on Microsoft-centric tools (AzCopy, Storage Explorer, PowerShell), which are more familiar to Windows users, and do not provide parity for Linux command-line tools or workflows.
Recommendations
  • Include examples and instructions for using Azure CLI and Bash scripts for both uploading VHD files and creating custom images.
  • Mention Linux-native tools (such as dd, qemu-img, or SCP) for preparing and transferring VHD files.
  • Provide equal prominence to Linux workflows and tools alongside Windows/PowerShell options.
  • Add explicit examples for Linux users, such as using the Azure CLI on Linux to create custom images.
  • Ensure that references to OS-specific preparation steps (sysprep for Windows, deprovision for Linux) are presented in parallel and with equal detail.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-dev-ops.md ...blob/main/articles/devtest-labs/devtest-lab-dev-ops.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned as a primary scripting option for integrating with DevTest Labs, and Windows-centric patterns (such as VM creation with customer software and artifacts) are described without explicit mention of Linux alternatives. There are no examples or references to Linux shell scripting, Linux VM configuration, or Linux-specific tools, and Windows/PowerShell approaches are listed before Azure CLI or REST API options.
Recommendations
  • Add explicit examples using Bash scripts and Linux shell commands for integrating with DevTest Labs.
  • Include references to managing Linux VMs in DevTest Labs, such as provisioning, configuration, and artifact installation.
  • Present Azure CLI and REST API usage before or alongside PowerShell, emphasizing cross-platform compatibility.
  • Mention Linux-based CI/CD pipeline managers (e.g., GitLab CI, Travis CI) and how they can integrate with DevTest Labs.
  • Provide guidance on using DevTest Labs with Linux build agents and environments.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-grant-user-permissions-to-specific-lab-policies.md ...st-lab-grant-user-permissions-to-specific-lab-policies.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively uses Azure PowerShell and Windows-centric tools for all examples and instructions. There are no references to Linux-native tools, Bash, Azure CLI, or cross-platform alternatives. The page assumes the reader is using PowerShell, which is traditionally a Windows-first technology, and does not provide parity for Linux users or those preferring Azure CLI.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell scripts and commands.
  • Mention that Azure PowerShell is available cross-platform, but clarify installation steps for Linux/macOS users.
  • Include Bash script examples where appropriate, especially for tasks like role assignment and querying users.
  • Explicitly state that all operations can be performed from Linux/macOS environments, and provide links to relevant documentation.
  • Reorder sections to present Azure CLI and PowerShell side-by-side, or at least mention CLI alternatives before diving into PowerShell specifics.
GitHub Create Pull Request
← Previous Page 4 of 14 Next →