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 26-50 of 113 flagged pages
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 a Windows bias by referencing PowerShell as the primary example for deploying VMs with ARM templates, without mentioning or providing equivalent examples for Linux users (such as Azure CLI or Bash). The troubleshooting steps and patterns are described in a way that assumes familiarity with Windows-centric tools, and there is no parity for Linux or cross-platform command-line approaches.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for ARM template deployments.
  • Explicitly mention that both Windows and Linux users can deploy VMs and provide links or code snippets for Linux workflows.
  • Rephrase troubleshooting steps to be tool-agnostic or provide parallel instructions for both PowerShell and Azure CLI.
  • Include references to Linux documentation and troubleshooting tools where relevant.
GitHub Create Pull Request
Devtest Labs Access, claim, and connect to lab VMs .../main/articles/devtest-labs/tutorial-use-custom-lab.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 in several ways. In the VM connection instructions, Windows (RDP) is mentioned before Linux (SSH/Azure CLI), and the Windows-specific tool (RDP) is called out by name, while Linux options are grouped together. The structure and screenshots focus on portal actions that are most familiar to Windows users, and there is no parity in example depth or tool explanation for Linux users. There are no Linux-specific screenshots or step-by-step instructions, and the flow assumes familiarity with Windows patterns.
Recommendations
  • Present Linux connection options (SSH, Azure CLI) before or alongside Windows (RDP) options, not after.
  • Include Linux-specific screenshots and step-by-step instructions for connecting to Linux VMs.
  • Explicitly mention Linux tools (e.g., SSH clients, Azure CLI) and provide example commands.
  • Balance the depth of instructions and examples for both Windows and Linux users.
  • Avoid assuming Windows as the default; clarify that both OS types are supported and provide equal guidance.
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
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples first, referencing Windows-specific tools and patterns (such as REM comments and Windows environment variable syntax), and generally prioritizing Windows environments in explanations. While Azure CLI examples are provided for both Bash and Windows, the PowerShell section is more extensive and presented before CLI, reinforcing a Windows-centric approach.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid prioritizing Windows tools.
  • Expand Bash/Linux-specific instructions and examples to match the detail given to PowerShell/Windows.
  • Remove or minimize Windows-specific syntax (e.g., REM comments, set commands) unless equally balanced with Linux equivalents.
  • Explicitly mention Linux/macOS environments where applicable, including installation and usage notes.
  • Ensure parity in troubleshooting, prerequisites, and environment setup for both Windows and Linux users.
GitHub Create Pull Request
Devtest Labs Create custom artifacts for VMs ...n/articles/devtest-labs/devtest-lab-artifact-author.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 notable Windows bias. All code examples for artifact creation use PowerShell scripts and Windows-specific commands (e.g., powershell.exe, Chocolatey). There are no Linux shell script examples, nor is there guidance for creating Linux-compatible artifacts. The process for Linux artifact creation is only mentioned in passing (targetOsType: Linux), with no practical examples or instructions. Windows tools and patterns (PowerShell, Chocolatey) are referenced exclusively and appear before any mention of Linux equivalents.
Recommendations
  • Add parallel examples for Linux artifacts, including sample artifactfile.json and corresponding shell script (e.g., Bash) usage.
  • Show how to use Linux package managers (e.g., apt, yum) in artifact scripts.
  • Provide a Linux-focused runCommand example, such as executing a Bash script.
  • Explicitly mention and demonstrate how to structure artifacts for Linux VMs, including handling secure strings and parameters.
  • Ensure that Linux instructions and examples are presented alongside Windows examples, not only as an afterthought.
GitHub Create Pull Request
Devtest Labs Create environments from ARM templates ...evtest-labs/devtest-lab-create-environment-from-arm.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 in its automation section, providing a detailed PowerShell script and usage instructions for automating environment creation, while only briefly mentioning Azure CLI as an alternative without any example or walkthrough. The PowerShell example is extensive and presented first, with no equivalent Bash or Linux shell script provided. This creates friction for Linux/macOS users who may prefer or require CLI or Bash-based automation.
Recommendations
  • Add a full Azure CLI example (with Bash syntax) for automating environment creation, including parameter handling and deployment steps.
  • Present both PowerShell and Azure CLI examples side-by-side, or clearly indicate parity between platforms.
  • Explicitly mention platform compatibility for each automation method, clarifying that PowerShell is available cross-platform but CLI is native to Linux/macOS.
  • Consider providing a table or section comparing PowerShell and CLI approaches for common tasks in DevTest Labs.
GitHub Create Pull Request
Devtest Labs Add an Artifact Repository to Your Lab .../main/articles/devtest-labs/add-artifact-repository.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed instructions and examples for adding an artifact repository to an Azure DevTest Lab, with a strong emphasis on Azure PowerShell usage. All code samples and automation scripts are written in PowerShell, and deployment instructions for ARM templates explicitly use PowerShell first, with Azure CLI only mentioned as a link. There are no Linux/macOS-specific shell (bash, CLI) examples, and PowerShell is presented as the primary automation method, which may create friction for Linux/macOS users who prefer bash or Azure CLI.
Recommendations
  • Add equivalent Azure CLI examples and scripts for all PowerShell-based procedures, including ARM template deployment and artifact repository creation.
  • Explicitly mention cross-platform compatibility for automation steps, and clarify which steps can be performed from Linux/macOS terminals.
  • Where PowerShell is used, provide bash/CLI alternatives side-by-side, or in separate tabs, to ensure parity.
  • Include notes or sections on using Azure Cloud Shell (which supports both PowerShell and bash) for platform-neutral guidance.
GitHub Create Pull Request
Devtest Labs Create and add a VM to a lab .../blob/main/articles/devtest-labs/devtest-lab-add-vm.md
Medium 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 Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. The main VM creation walkthrough uses a Windows 11 Pro image as its example, with no mention of Linux images or their setup differences. The only explicit scripting example for copying VMs uses a PowerShell script, with no Linux shell or cross-platform alternative provided. While Azure CLI and ARM templates are mentioned as options, no examples or links are shown for Linux/macOS users, and Windows tools/scripts are referenced first.
Recommendations
  • Include Linux VM creation examples alongside Windows, highlighting any differences in settings or options.
  • Provide explicit Azure CLI/bash script examples for tasks currently shown only with PowerShell (e.g., copying VMs).
  • When listing automation options (PowerShell, CLI, ARM), present them in a neutral or alternating order, and link to Linux/macOS-friendly guides.
  • Add screenshots or walkthroughs using a Linux image to illustrate parity.
  • Clarify any OS-specific requirements or differences in the VM creation process.
GitHub Create Pull Request
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-12 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 exclusively uses Azure PowerShell cmdlets and scripts for all examples and instructions, with no mention of cross-platform alternatives such as Azure CLI, Bash, or Cloud Shell. The installation instructions and workflow are centered around PowerShell, a tool most commonly associated with Windows, and there are no Linux/macOS-specific notes or examples. This creates friction for users on non-Windows platforms who may prefer or require different tooling.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include instructions for using Azure Cloud Shell, which supports both Bash and PowerShell and is accessible from any OS.
  • Explicitly state that PowerShell Core is available on Linux/macOS, and provide installation links.
  • Present examples for both PowerShell and CLI side-by-side, or indicate which commands work on all platforms.
  • Add a note clarifying platform compatibility for all tools mentioned.
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-12 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/macOS users (e.g., Bash or CLI). The scripting section is Windows-centric, and PowerShell is presented as the primary automation method, with no mention of cross-platform alternatives. This creates friction for users on Linux or macOS who may prefer Bash or native Azure CLI usage.
Recommendations
  • Add a Bash/Azure CLI example for Linux/macOS users, demonstrating the same resource group configuration steps.
  • Clarify that PowerShell is available cross-platform, but also provide native Bash/CLI syntax for common tasks.
  • Reorder examples or explicitly state platform applicability to avoid implying Windows is the default or preferred environment.
  • Include notes or links to platform-specific guidance for Linux/macOS users.
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-12 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 instructions and examples exclusively for PowerShell, with no mention of Linux or macOS command-line equivalents (such as Bash, Azure CLI, or shell scripting). The PowerShell method is presented first and in greater detail, while the REST API method is described generically without platform-specific guidance. There are no Linux/macOS-specific instructions or examples, which may create friction for non-Windows users.
Recommendations
  • Add equivalent instructions and examples for Linux/macOS users, such as using Bash scripts or the Azure CLI to perform the import operation.
  • Provide sample REST API calls using curl or httpie, which are common tools on Linux/macOS.
  • Clarify that PowerShell Core is cross-platform, if applicable, and provide installation guidance for Linux/macOS users.
  • Reorder or balance the examples so that Windows and Linux/macOS methods are presented with equal prominence.
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-12 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 notable Windows bias. PowerShell is the only example provided for exporting resource usage, with no equivalent Linux or Bash examples. Windows-centric tools (PowerShell, SQL Server, Power BI) are mentioned first or exclusively, while Linux alternatives or cross-platform command-line approaches are missing. This creates friction for Linux/macOS users who may prefer Bash, CLI, or open-source visualization tools.
Recommendations
  • Add Azure CLI and Bash script examples for exporting resource usage, alongside PowerShell.
  • Explicitly mention cross-platform compatibility for Azure Functions and Azure Automation, and provide Python or Bash samples.
  • List open-source or cross-platform visualization tools (e.g., Grafana, Kibana) alongside Power BI.
  • Include Linux-friendly storage options and usage patterns, such as PostgreSQL or MySQL.
  • Reorder examples so that Windows and Linux approaches are presented equally or in parallel.
GitHub Create Pull Request
Devtest Labs Troubleshoot VM deployment failures ...es/devtest-labs/troubleshoot-vm-deployment-failures.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias by referencing PowerShell as the primary method for deploying VMs with ARM templates and mentioning PowerShell scripts before any Linux/macOS alternatives. No Linux-specific examples, tools, or CLI commands are provided, and the troubleshooting steps assume familiarity with PowerShell, which is more commonly used on Windows.
Recommendations
  • Include Azure CLI examples alongside PowerShell for ARM template deployments, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that ARM template deployments can be performed from Linux/macOS using Azure CLI or Bash scripts.
  • Provide troubleshooting steps and example commands for Linux/macOS environments where applicable.
  • Avoid assuming PowerShell as the default scripting environment; present it as one option among several.
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-12 00:00
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 VM in Azure DevTest Labs, but when guiding users to create a VM, it exclusively uses 'Windows Server 2019 Datacenter' as the base image example. There are no Linux VM examples, nor are Linux-specific configuration details or considerations mentioned. This may lead Linux/macOS users to feel unsupported or uncertain about the process for non-Windows VMs.
Recommendations
  • Include parallel instructions 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 differences in configuration (e.g., SSH keys for Linux, password requirements, artifact compatibility).
  • Add notes or links to Linux-specific guidance, such as connecting to a Linux VM via SSH or configuring Linux artifacts.
  • Ensure that examples and screenshots alternate between Windows and Linux, or present both options side-by-side.
GitHub Create Pull Request
Devtest Labs Add artifacts to VMs ...ocs/blob/main/articles/devtest-labs/add-artifact-vm.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and a full script for adding artifacts to VMs using Azure PowerShell, but does not offer equivalent examples or guidance for Linux/macOS users (e.g., Azure CLI or Bash). The PowerShell approach is presented as the only command-line option, and prerequisites explicitly mention PowerShell without referencing alternatives. This creates friction for users on Linux or macOS platforms who may not use PowerShell.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples for artifact management, especially for Linux/macOS users.
  • Include prerequisites and setup instructions for Azure CLI alongside PowerShell.
  • Present cross-platform command-line options together, or clearly indicate which are platform-specific.
  • Where possible, use generic scripting examples (e.g., Bash, Python) in addition to PowerShell.
GitHub Create Pull Request
Devtest Labs Automate adding a lab user ...ob/main/articles/devtest-labs/automate-add-lab-user.md
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias. PowerShell is used extensively for examples and tooling, with cmdlets referenced throughout for tasks like obtaining object IDs and deploying templates. Windows/PowerShell tools are mentioned first and in greater detail, while Linux/macOS equivalents (such as bash scripting or cross-platform CLI usage) are not provided. The Azure CLI section is brief and lacks parity with the PowerShell examples, and there are no explicit Linux/macOS workflow examples for tasks like GUID generation or template deployment.
Recommendations
  • Provide equivalent examples using bash and Azure CLI for all major steps, such as obtaining object IDs, generating GUIDs, and deploying templates.
  • Add explicit instructions for Linux/macOS users, including how to generate GUIDs (e.g., using uuidgen) and deploy ARM templates with Azure CLI.
  • Ensure CLI examples are as detailed and comprehensive as PowerShell examples, including parameter file usage and dynamic value generation.
  • Mention cross-platform tools and patterns before or alongside Windows-specific ones.
  • Clarify that PowerShell Core is cross-platform, but also show how tasks can be completed without PowerShell.
GitHub Create Pull Request
Devtest Labs Create a Service Fabric cluster environment ...test-labs/create-environment-service-fabric-cluster.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation exhibits Windows bias by defaulting to Windows as the operating system for cluster nodes, providing certificate creation instructions exclusively via a PowerShell script (.ps1), and omitting equivalent Linux/macOS instructions or examples. The only method described for certificate creation is Windows/PowerShell-based, and no alternative for Linux users is mentioned.
Recommendations
  • Provide explicit instructions for creating cluster certificates on Linux/macOS, such as using OpenSSL or bash scripts.
  • Include Linux/macOS examples for all steps where OS-specific actions are required, especially for certificate generation.
  • Clarify that both Windows and Linux are supported for cluster nodes, and show how to select Linux as the OS.
  • Avoid presenting Windows tools/scripts as the only or default method; offer cross-platform alternatives side-by-side.
GitHub Create Pull Request
Devtest Labs Nested ARM templates for lab environments ...es/devtest-labs/deploy-nested-template-environments.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. Deployment instructions mention Azure PowerShell first, followed by Azure CLI, and reference Visual Studio (a primarily Windows tool) for ARM template deployment. There are no Linux/macOS-specific examples or guidance, and the use of PowerShell is emphasized over cross-platform alternatives.
Recommendations
  • Provide Linux/macOS-specific deployment instructions, such as using Azure CLI from Bash.
  • Include examples for running deployments on Linux/macOS terminals.
  • Mention cross-platform editors like VS Code for ARM template authoring and deployment.
  • Clarify that Azure CLI is fully supported on Linux/macOS and provide relevant command examples.
  • Avoid listing Windows tools (PowerShell, Visual Studio) before cross-platform alternatives.
GitHub Create Pull Request
Devtest Labs Create custom artifacts for VMs ...n/articles/devtest-labs/devtest-lab-artifact-author.md
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias: all code examples use PowerShell scripts and Windows-specific commands (e.g., powershell.exe, Chocolatey), with no Linux shell or script examples provided. The artifact creation walkthrough exclusively references Windows artifacts and scripts, omitting Linux equivalents. Windows tools and patterns (PowerShell, Chocolatey) are mentioned without Linux alternatives, and Windows examples are shown first and exclusively.
Recommendations
  • Add parallel Linux examples using bash/sh scripts and Linux package managers (e.g., apt, yum) in the artifact definition and runCommand sections.
  • Include a walkthrough for creating a Linux artifact, referencing a sample Linux artifact from the public repository.
  • Show both Windows and Linux artifact folder structures and script naming conventions.
  • Mention Linux-specific considerations (e.g., shell script permissions, interpreter selection) alongside Windows notes.
  • Ensure that the documentation alternates or balances Windows and Linux examples, or clearly sections them.
GitHub Create Pull Request
Devtest Labs Create environments from ARM templates ...evtest-labs/devtest-lab-create-environment-from-arm.md
Medium Priority View Details →
Scanned: 2026-01-12 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 for Azure PowerShell, with no equivalent Bash or Azure CLI example shown. PowerShell is a Windows-centric tool, and its use is presented first and in detail, while the Azure CLI is only briefly mentioned as an alternative with no example. This creates friction for Linux/macOS users who may prefer Bash or CLI workflows.
Recommendations
  • Provide a full Azure CLI (az deployment group create) example for automating environment creation, including parameter handling and repository/template selection.
  • Include Bash script equivalents for the PowerShell automation, or at least show CLI commands with example parameters.
  • Explicitly mention cross-platform tooling and clarify which steps are OS-agnostic (e.g., Azure portal usage) and which require platform-specific tools.
  • Where PowerShell scripts are given, offer CLI/Bash alternatives side-by-side or in a dedicated Linux/macOS section.
GitHub Create Pull Request
Devtest Labs Delete a lab virtual machine or a lab ...ain/articles/devtest-labs/devtest-lab-delete-lab-vm.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a PowerShell script for automating VM deletion, which is Windows-centric and does not offer equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI). The only automation example uses PowerShell, and there is no mention of cross-platform alternatives or parity. Manual steps are portal-based and platform-neutral, but automation guidance is Windows-biased.
Recommendations
  • Add equivalent automation examples using Azure CLI and/or Bash scripts, which are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation guidance.
  • Order automation examples so that Azure CLI or Bash appears before or alongside PowerShell.
  • Clarify which tools are cross-platform and provide links to relevant documentation for Linux/macOS users.
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-12 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 for Azure DevTest Labs scenarios exhibits moderate Windows bias. PowerShell is frequently referenced as a primary automation tool, with no mention of Bash, CLI, or Linux/macOS scripting alternatives. Examples and quickstarts for lab creation and VM management consistently highlight Windows-centric tools (PowerShell, Windows VM templates), and Windows-specific software (Visual Studio, Fiddler) is listed as typical artifacts. Linux equivalents, such as Bash scripts, Linux VM templates, or open-source tools, are not provided or referenced. This creates friction for Linux/macOS users, who must infer or adapt instructions for their platforms.
Recommendations
  • Include Linux/macOS-specific examples alongside PowerShell, such as Azure CLI or Bash scripting for lab and VM management.
  • Reference Linux VM templates and provide quickstart links for creating labs with Linux VMs.
  • List and describe common Linux tools (e.g., VS Code, Git, open-source utilities) as artifacts, in addition to Windows tools.
  • When mentioning automation, provide parity between PowerShell and Bash/CLI approaches.
  • Ensure that instructions for deleting labs/VMs, adding users, and configuring policies include Linux/macOS-compatible methods.
GitHub Create Pull Request
Devtest Labs Add and configure lab users with role-based access control (RBAC) .../articles/devtest-labs/devtest-lab-add-devtest-user.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides two methods for adding lab users: Azure portal and Azure PowerShell. The PowerShell example is detailed and assumes use of Azure PowerShell, which is most commonly used on Windows. There are no CLI (az), Bash, or Linux/macOS-specific examples, and PowerShell is presented as the only scripting option. The prerequisites and instructions reference PowerShell exclusively, with no mention of Linux-native tools or cross-platform alternatives. The portal instructions are platform-neutral, but the scripting section is Windows/PowerShell-centric.
Recommendations
  • Add equivalent examples using Azure CLI (az), which is cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that Azure PowerShell can be used in Azure Cloud Shell, which is available on all platforms, but also provide Bash/CLI alternatives.
  • Include notes or links for Linux/macOS users on how to install and use Azure CLI.
  • Reorder examples so that cross-platform methods (Azure CLI) are presented before or alongside PowerShell.
GitHub Create Pull Request
Devtest Labs Create custom images for lab VMs from VHD files ...n/articles/devtest-labs/devtest-lab-create-template.md
Medium Priority View Details →
Scanned: 2026-01-12 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 mentioned as an alternative method for creating custom images and for uploading VHD files, with no explicit mention of Bash, CLI, or Linux-native tooling. Windows-specific tools (sysprep) are described before Linux equivalents (deprovision), and PowerShell is listed as an upload option alongside AzCopy and Storage Explorer, both of which are cross-platform but often associated with Windows workflows. Examples and screenshots are portal-based and do not show Linux-specific workflows or command-line examples.
Recommendations
  • Add explicit Linux/macOS command-line examples using Bash and Azure CLI for creating and uploading custom images.
  • Clarify that AzCopy and Storage Explorer are cross-platform, and provide installation/use instructions for Linux/macOS.
  • Provide parity in instructions for Linux image preparation (e.g., expand on deprovision usage with waagent or cloud-init).
  • Include screenshots or walkthroughs from Linux/macOS environments where relevant.
  • Mention alternative tools or workflows commonly used by Linux/macOS users.
GitHub Create Pull Request
Devtest Labs Integrate Azure DevTest Labs with DevOps CI/CD Pipelines ...blob/main/articles/devtest-labs/devtest-lab-dev-ops.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell scripts and Azure CLI as integration options, but mentions PowerShell first and does not provide explicit Linux/macOS examples or guidance. There is no mention of Bash, shell scripting, or Linux-specific tools, and the documentation does not clarify cross-platform compatibility for scripting tasks. The examples and recommendations are generic, but the ordering and language suggest a Windows-centric approach.
Recommendations
  • Explicitly mention Bash/shell scripting alongside PowerShell and Azure CLI as supported integration methods.
  • Provide Linux/macOS-specific examples for scripting tasks, such as using Bash or shell scripts to call REST APIs or manage Azure resources.
  • Clarify that Azure CLI and REST API calls are cross-platform and provide links or examples for Linux/macOS users.
  • Ensure that any referenced tools or scripts are described in a platform-neutral way, or provide parallel instructions for both Windows and Linux/macOS environments.
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-12 00:00
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 exclusively using Windows 11 Pro as the example OS for VM creation and referencing Windows-specific screenshots and instructions. There are no examples, screenshots, or guidance for creating or managing Linux-based VMs with hibernation in Azure DevTest Labs, nor any mention of Linux-specific considerations or parity.
Recommendations
  • Add explicit instructions and screenshots for enabling hibernation on Linux-based VMs in Azure DevTest Labs.
  • Include a section discussing supported Linux distributions and any differences in hibernation behavior or requirements compared to Windows.
  • Provide examples using Linux images (e.g., Ubuntu, CentOS) in the VM creation workflow.
  • Clarify whether hibernation is supported for Linux VMs and list any limitations or prerequisites.
  • Ensure that references to VM selection, connection, and management are not Windows-centric (e.g., avoid only showing 'select your Windows VM').
GitHub Create Pull Request
← Previous Page 2 of 5 Next →