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 1-25 of 334 flagged pages
Devtest Labs Define VM start order with Azure Automation ...devtest-labs/start-machines-use-automation-runbooks.md
High Priority View Details →
Scanned: 2026-01-14 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 exclusively uses PowerShell for scripting and Azure Automation, with no mention of Bash, Azure CLI, or Linux/macOS-compatible alternatives. All code examples and instructions are tailored to Windows/PowerShell environments, making it difficult for Linux/macOS users to follow or adapt the guidance.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for defining VM start order.
  • Mention cross-platform tools and approaches, such as using Azure CLI runbooks or Python scripts.
  • Clarify which steps are platform-agnostic and which are Windows-specific.
  • Add notes or links for Linux/macOS users on how to adapt the process using their preferred tools.
GitHub Create Pull Request
Devtest Labs Secure Labs by Using Remote Desktop Gateways ...s/devtest-labs/configure-lab-remote-desktop-gateway.md
High Priority View Details →
Scanned: 2026-01-14 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 is heavily oriented toward Windows environments, with all remote desktop examples and tooling based on Windows technologies (RDP, PowerShell, IIS, RDGatewayFedAuth.msi). There are no Linux/macOS equivalents or instructions for connecting from non-Windows clients, and all automation and certificate management examples use PowerShell. Windows tools and patterns are mentioned exclusively and first, with no mention of Linux alternatives for remote desktop gateway setup or usage.
Recommendations
  • Add explicit instructions and examples for connecting to lab VMs via the gateway from Linux and macOS clients, including supported RDP clients and token authentication compatibility.
  • Provide Linux/macOS equivalents for certificate management (e.g., using OpenSSL for certificate creation, thumbprint extraction, and Base64 encoding).
  • Include automation examples using Bash scripts and Azure CLI, not just PowerShell.
  • Mention and document cross-platform RDP clients (such as FreeRDP, Remmina, or Microsoft Remote Desktop for macOS) and clarify token authentication support.
  • If IIS and RDGatewayFedAuth.msi are Windows-only, suggest or provide alternatives for Linux gateway hosts (e.g., Apache/Nginx reverse proxy, or note limitations).
  • Reorder examples so that platform-neutral or cross-platform approaches are presented first, or provide parallel instructions for each OS.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows, with AzCopy described as a Windows-only tool and all instructions, examples, and screenshots referencing Windows environments and PowerShell. There are no Linux or macOS equivalents, nor any guidance for non-Windows users, making it difficult or impossible for them to complete the task as described.
Recommendations
  • Update the documentation to reference AzCopy v10+, which is cross-platform and works on Linux and macOS.
  • Provide installation and usage instructions for AzCopy on Linux and macOS, including example commands and directory paths.
  • Include screenshots or terminal examples for Linux/macOS environments.
  • Mention alternative upload methods (e.g., Azure CLI, Storage Explorer) for users who cannot use AzCopy on Windows.
  • Clarify which steps are platform-specific and offer parity for non-Windows users.
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-13 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 use of the PowerShell Az Module, and does not provide equivalent instructions or examples for Linux/macOS users (e.g., Bash, curl, Azure CLI). Windows tools and patterns are referenced throughout, with no mention of cross-platform alternatives or parity.
Recommendations
  • Add Bash and Azure CLI examples alongside PowerShell for all steps, including authentication, request body preparation, and REST API invocation.
  • Explicitly note cross-platform compatibility and provide instructions for Linux/macOS users.
  • Reference and link to Azure CLI documentation as an alternative to PowerShell Az Module.
  • Present examples for both Windows and Linux/macOS side-by-side or in separate tabs/sections.
GitHub Create Pull Request
Devtest Labs Secure Labs by Using Remote Desktop Gateways ...s/devtest-labs/configure-lab-remote-desktop-gateway.md
High Priority View Details →
Scanned: 2026-01-13 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 exhibits a strong Windows bias. All remote desktop connection examples and instructions are centered around RDP, a Windows protocol, and Windows tooling such as PowerShell scripts and IIS modules. There are no examples or guidance for Linux or macOS users, either for connecting to lab VMs or for gateway setup. Windows tools and patterns (PowerShell, IIS, RDGatewayFedAuth.msi) are mentioned exclusively and repeatedly, with no mention of Linux alternatives or cross-platform approaches.
Recommendations
  • Provide explicit instructions and examples for Linux and macOS users, including how to connect to lab VMs via RDP (e.g., using xfreerdp, rdesktop, or Microsoft Remote Desktop for Mac).
  • Mention and document Linux-compatible tools for certificate creation and management (e.g., openssl commands for signing certificates and extracting thumbprints/Base64).
  • Clarify whether the gateway and authentication modules (such as RDGatewayFedAuth.msi) are Windows-only, and if so, suggest or document Linux-compatible alternatives or workarounds.
  • Include Linux/macOS automation examples (e.g., Bash scripts, Azure CLI commands) alongside PowerShell.
  • Discuss cross-platform remote desktop gateway solutions or alternatives, such as using Azure Bastion (already briefly mentioned), and provide parity in setup documentation.
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-13 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 is heavily biased toward Windows, with AzCopy described as a Windows-only tool, all instructions and examples using Windows Command Prompt and PowerShell, and no mention of Linux/macOS equivalents or alternatives. Linux users are left without guidance or supported tooling for the described workflow.
Recommendations
  • Clarify whether AzCopy v10+ is cross-platform (the latest versions are available for Linux/macOS) and update instructions accordingly.
  • Provide Linux/macOS installation steps for AzCopy.
  • Include Linux/macOS command-line examples (e.g., Bash syntax) for uploading VHD files.
  • Mention Azure CLI or REST API alternatives for non-Windows users.
  • Avoid stating AzCopy is Windows-only unless referring specifically to legacy versions.
GitHub Create Pull Request
Devtest Labs Add artifacts to VMs ...ocs/blob/main/articles/devtest-labs/add-artifact-vm.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 exclusively providing Azure PowerShell examples and instructions, with no mention of Linux-native tools or CLI alternatives. The prerequisites and step-by-step instructions focus on PowerShell, and the only provided script is in PowerShell. There is no coverage of Bash, Azure CLI, or Linux shell usage, nor are Linux-specific patterns or tools discussed.
Recommendations
  • Add equivalent instructions and examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux.
  • Include Bash script examples for artifact management, especially for users working in Linux environments.
  • Explicitly mention that artifacts can run Bash commands and provide a sample Bash-based artifact.
  • In the prerequisites section, provide guidance for Linux users, such as installing Azure CLI or using Bash in Cloud Shell.
  • Ensure screenshots and UI instructions are not Windows-centric and clarify that the portal experience is OS-agnostic.
  • Where PowerShell is referenced, also provide the Linux/Bash/CLI alternative side-by-side or in tabs.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by referencing Windows virtual machines before Linux equivalents, omitting Linux VM documentation links, and listing Windows-specific tools (e.g., Visual Studio, Fiddler) as artifact examples without mentioning Linux alternatives. There are no Linux/Powershell command examples, but the overall focus and examples prioritize Windows environments and tooling.
Recommendations
  • Include references and links to both Windows and Linux VM documentation (e.g., add a link to 'Linux virtual machines in Azure').
  • Provide examples of artifacts and tools relevant to Linux environments (e.g., Git, Apache, Nginx, VS Code, etc.) alongside Windows tools.
  • Ensure that any instructions or examples for VM creation, templates, or artifacts mention both Windows and Linux scenarios where applicable.
  • Balance the order of presentation so that Linux is mentioned equally or alongside Windows, rather than Windows-first.
  • Add explicit examples or references for managing Linux VMs, images, and environments in DevTest Labs.
GitHub Create Pull Request
Devtest Labs Create a custom image from a lab VM ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-custom-image-from-vm-using-portal.md
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 page demonstrates a mild Windows bias. Windows-specific terminology (e.g., 'sysprep') is mentioned before Linux equivalents ('deprovision'), and the generalization process is described with a Windows-first approach. References to Windows tools (sysprep) are explicit, while Linux instructions are less detailed and lack parity in explanation. There are no Linux-specific command examples or screenshots, and the overall workflow assumes familiarity with Windows patterns.
Recommendations
  • Present Linux and Windows generalization steps with equal detail and prominence, possibly in parallel sections.
  • Include explicit Linux command examples (e.g., waagent --deprovision+user) and clarify the process for Linux users.
  • Add screenshots or illustrations showing the Linux generalization process in the Azure portal.
  • Avoid mentioning Windows tools (sysprep) before Linux equivalents; use neutral phrasing or alternate between platforms.
  • Provide links to both Windows and Linux documentation with equal visibility.
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-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 strong Windows bias. AzCopy is described as a Windows-only utility, and all instructions and examples assume a Windows environment (Command Prompt, Windows file paths, installation directory). PowerShell is referenced and shown in screenshots, with no mention of Linux or cross-platform alternatives. There are no Linux shell examples, nor guidance for Linux users.
Recommendations
  • Update the documentation to clarify the current cross-platform status of AzCopy (AzCopy v10+ is cross-platform and works on Linux/macOS).
  • Provide Linux and macOS installation instructions for AzCopy.
  • Include Linux shell (bash) examples for uploading VHD files using AzCopy.
  • Replace or supplement Windows Command Prompt instructions with bash/zsh equivalents.
  • Add notes or sections for Linux users, including default installation paths and environment setup.
  • Avoid referencing PowerShell exclusively; provide Azure CLI or bash alternatives where possible.
GitHub Create Pull Request
Devtest Labs Create a Service Fabric cluster environment ...test-labs/create-environment-service-fabric-cluster.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 demonstrates a Windows bias in several ways. The default operating system for cluster VMs is Windows, and the certificate creation process is described exclusively using a PowerShell script (Create-ClusterCertificate.ps1), with instructions to launch PowerShell and run the script. There are no equivalent instructions or examples for Linux users (e.g., using OpenSSL or bash), nor are Linux tools or workflows mentioned for certificate creation. The documentation refers to Windows first in OS selection and omits Linux-specific guidance in critical steps.
Recommendations
  • Provide Linux-specific instructions for certificate creation, such as using OpenSSL commands and bash scripts.
  • Include examples and screenshots for both Windows and Linux environments when describing cluster creation and configuration.
  • Mention Linux tools and workflows alongside Windows tools, ensuring parity in documentation.
  • Change language to be OS-neutral where possible, or explicitly offer both Windows and Linux options in step-by-step guides.
  • Set the default OS selection to prompt the user to choose, rather than defaulting to Windows.
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-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 exclusively uses PowerShell for scripting and automation, with no mention of Bash, Python, or other cross-platform alternatives. All examples, instructions, and code are tailored for PowerShell and Azure Automation, which is most commonly used in Windows environments. There is no guidance for Linux users or those who prefer non-Windows shells, and Windows-centric tools and patterns (e.g., PowerShell runbooks, PowerShell jobs, Windows environment variables) are used throughout.
Recommendations
  • Provide equivalent Bash or Python scripts for Linux users, demonstrating how to achieve the same VM start order functionality using Azure CLI or REST API.
  • Include instructions for running automation tasks from Linux environments, such as using Azure CLI in a cron job or leveraging Azure Logic Apps.
  • Mention cross-platform options for Azure Automation runbooks, such as Python or graphical runbooks, and link to relevant documentation.
  • Clarify which steps or tools are Windows-specific and offer Linux alternatives where possible.
  • Add a section comparing PowerShell and non-PowerShell approaches, helping users choose the best fit for their environment.
GitHub Create Pull Request
Devtest Labs Azure CLI Samples ...re-docs/blob/main/articles/devtest-labs/samples-cli.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits Windows bias by focusing on creating Windows VMs, labeling example scripts as 'powershell' even though they are bash scripts, and not providing explicit Linux VM creation examples or Linux-specific usage notes. The examples and descriptions prioritize Windows scenarios and terminology, with no mention of Linux images or SSH authentication details for Linux VMs.
Recommendations
  • Include examples for creating Linux VMs, with appropriate configuration and authentication details (e.g., SSH key setup for Linux).
  • Correct the code block language tags to 'bash' or 'azurecli' instead of 'powershell' for scripts that are shell scripts.
  • Explicitly mention both Windows and Linux VM creation options in the table and script descriptions.
  • Add notes or examples for connecting to Linux VMs (e.g., using SSH) alongside Windows connection instructions.
  • Ensure terminology and instructions are platform-neutral where possible, or provide parallel guidance for both Windows and Linux 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-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 Windows bias primarily through its heavy reliance on PowerShell for automation and scripting examples. The ARM template deployment section explicitly instructs users to deploy using Azure PowerShell first, with Linux-friendly Azure CLI only mentioned as a secondary option. The scripting and command-line automation guidance is almost exclusively PowerShell-based, which is native to Windows and only more recently available on Linux. There is no Bash or Linux shell scripting example, and Windows-centric tools and patterns (such as Set-AzContext, New-AzResourceGroup, New-AzResourceGroupDeployment) are used throughout. The documentation does not provide parity for Linux users in terms of CLI or Bash examples, nor does it mention Linux-specific considerations for repository management or authentication.
Recommendations
  • Provide equivalent Azure CLI and Bash script examples for all automation and deployment scenarios, not just PowerShell.
  • When listing deployment options, present Azure CLI and PowerShell together, or alternate which is shown first, to avoid Windows-first ordering.
  • Include notes or examples for running scripts on Linux, including installation and usage of PowerShell Core on Linux, and highlight any differences.
  • Reference Linux-native tools and patterns where appropriate (e.g., curl, jq, Bash scripting) for REST API calls and resource management.
  • Ensure screenshots and UI instructions are platform-neutral or provide Linux-specific guidance where the experience differs.
GitHub Create Pull Request
Devtest Labs Create and add a VM to a lab .../blob/main/articles/devtest-labs/devtest-lab-add-vm.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 using a Windows 11 Pro image as the example for VM creation, mentioning PowerShell scripts as the primary method for copying VMs into a lab, and omitting explicit Linux VM creation examples or Linux-specific instructions. While Azure CLI and ARM templates are referenced, the step-by-step walkthrough and screenshots focus on Windows scenarios, and there are no Linux or cross-platform examples provided.
Recommendations
  • Include explicit Linux VM creation examples, such as using Ubuntu or CentOS images, alongside Windows examples.
  • Provide step-by-step instructions and screenshots for creating Linux VMs in DevTest Labs.
  • When referencing scripts for copying VMs, offer both PowerShell and Azure CLI/bash script alternatives, or clarify cross-platform options.
  • Ensure artifact examples include popular Linux tools and installation steps, not just Windows-centric software.
  • Review and update language and screenshots to represent both Windows and Linux VM scenarios equally.
GitHub Create Pull Request
Devtest Labs Automate adding a lab user ...ob/main/articles/devtest-labs/automate-add-lab-user.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 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a clear Windows bias. PowerShell is used extensively for examples and tooling, with PowerShell cmdlets mentioned and demonstrated before Azure CLI equivalents. Windows-centric tools (PowerShell, GUID generation via PowerShell) are referenced exclusively, and there are no explicit Linux/bash examples or guidance for Linux users. The CLI section is brief and lacks parity with the PowerShell coverage.
Recommendations
  • Provide equivalent bash/Azure CLI examples for all PowerShell commands, including how to retrieve ObjectId and role definition IDs using Azure CLI or REST API.
  • Mention Linux/macOS compatibility and usage patterns, such as using bash scripts and common Linux tools for GUID generation.
  • Reorder sections so that Azure CLI and ARM template examples are presented before PowerShell, or at least in parallel, to avoid Windows-first impression.
  • Add explicit notes or examples for Linux users, including installation and usage of Azure CLI on Linux.
  • Reference cross-platform tools for GUID generation (e.g., uuidgen in Linux/macOS) and REST API usage instead of only PowerShell cmdlets.
GitHub Create Pull Request
Devtest Labs Secure Labs by Using Remote Desktop Gateways ...s/devtest-labs/configure-lab-remote-desktop-gateway.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 strong Windows bias. It exclusively references Windows-centric technologies (Remote Desktop Gateway, RDP, IIS, System Center VMM, PowerShell scripts) and provides only Windows-based examples and tooling. There is no mention of Linux equivalents for remote access, certificate management, or automation, nor are Linux-friendly connection methods (like SSH) discussed. All code samples and automation scripts are in PowerShell, and Windows tools are referenced before any alternatives.
Recommendations
  • Provide Linux-based examples for remote access, such as using SSH tunnels or xrdp for RDP on Linux VMs.
  • Include automation scripts using Bash or Azure CLI, not just PowerShell.
  • Mention Linux-compatible certificate creation and management tools (e.g., OpenSSL) alongside PowerShell scripts.
  • Reference Linux-friendly remote desktop clients and clarify token authentication support for non-Windows programs.
  • Describe how to configure similar gateway and security setups for Linux VMs in DevTest Labs.
  • Add links to documentation for Linux remote desktop solutions and Azure Bastion usage with Linux VMs.
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
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 exclusively providing Azure PowerShell examples for command-line automation, referencing Microsoft accounts and Entra ID (formerly Azure AD) in a Windows-centric context, and omitting any Linux-specific CLI examples (such as Azure CLI/bash). The prerequisites and instructions focus on PowerShell and Windows tools, with no mention of Linux shell equivalents or cross-platform alternatives. The ordering and content suggest Windows/PowerShell as the primary automation method, with no parity for Linux users.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell scripts and procedures, with clear instructions for Linux/macOS users.
  • Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide links to installation guides for each platform.
  • Include guidance for using Bash in Azure Cloud Shell, not just PowerShell.
  • Clarify that Microsoft accounts and Entra ID are platform-agnostic, and provide context for Linux users where relevant.
  • Review screenshots and UI references to ensure they are not Windows-specific, or provide alternative visuals for other platforms if necessary.
GitHub Create Pull Request
Devtest Labs Distributed collaborative development of Azure DevTest Labs resources ...ces-distributive-collaborative-development-environment.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 primarily through its references to Azure PowerShell and PowerShell scripts as the main example for automation and scripting. There is no mention of Bash, Linux shell scripts, or cross-platform alternatives. The only scripting examples referenced are PowerShell and DSC, both Windows-centric technologies. No Linux-specific tools, patterns, or examples are provided, nor is there guidance for users working in Linux environments.
Recommendations
  • Include examples and references for Bash scripts and Linux shell scripting alongside PowerShell.
  • Mention cross-platform tools and workflows, such as Azure CLI, which work natively on Linux and macOS.
  • Provide guidance or links for Linux users on how to author and use artifacts and templates with Linux-based scripts.
  • Clarify that DevTest Labs supports both Windows and Linux VMs, and provide parity in documentation for both platforms.
  • Add sample repository structures or templates that include Linux-oriented resources (e.g., shell scripts, Ansible playbooks).
GitHub Create Pull Request
Devtest Labs Add tags to a lab ...blob/main/articles/devtest-labs/devtest-lab-add-tag.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page references managing tags using PowerShell or Azure CLI, but mentions PowerShell first and does not provide explicit Linux or Bash examples. The examples and screenshots are all based on the Azure Portal UI, which is platform-agnostic, but the only command-line tool mentioned by name is PowerShell, a Windows-centric tool. There are no Linux-specific instructions or examples, nor is Bash or shell scripting referenced.
Recommendations
  • Mention Azure CLI before or alongside PowerShell when discussing command-line management of tags.
  • Provide explicit examples for both PowerShell and Azure CLI (with Bash syntax) for common tag operations.
  • Include a note clarifying that Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Add links to Linux-specific documentation or tutorials for managing tags in Azure DevTest Labs.
  • Ensure that any future command-line examples are provided in both PowerShell and Bash/CLI formats.
GitHub Create Pull Request
Devtest Labs Create custom artifacts for VMs ...n/articles/devtest-labs/devtest-lab-artifact-author.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 strong Windows bias. All code examples use PowerShell scripts and Windows-specific commands (e.g., powershell.exe, Chocolatey), with no equivalent Linux shell or script examples. The step-by-step instructions and sample downloads reference only Windows artifacts and scripts. Linux support is mentioned only as an option for the target OS type, but no Linux-specific guidance, examples, or tools are provided.
Recommendations
  • Add equivalent Linux examples using Bash scripts and Linux package managers (e.g., apt, yum) in the artifact definition and runCommand sections.
  • Provide sample artifactfile.json and script files for Linux, and reference their locations in the public artifact repository.
  • Include instructions for creating and testing Linux artifacts, such as using shell scripts (.sh) and common Linux installation patterns.
  • Ensure screenshots and folder structures demonstrate both Windows and Linux artifact scenarios.
  • Mention Linux tools and commands alongside Windows ones, and avoid presenting Windows as the default or only option.
GitHub Create Pull Request
Devtest Labs Configure autoshutdown for lab virtual machines ...ain/articles/devtest-labs/devtest-lab-auto-shutdown.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 Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific concepts and tools, such as the 'Windows Plan' for Logic Apps and exclusive use of Office 365 Outlook for email integration. There are no examples or mentions of Linux-specific alternatives, nor is there guidance for users who may be using Linux-based email clients or non-Windows Logic App plans. The instructions and screenshots are tailored to the Azure portal UI, which is platform-agnostic, but the underlying assumptions and integrations favor Windows environments.
Recommendations
  • Include guidance for Linux users, such as using SMTP connectors with open-source email clients (e.g., Thunderbird, Evolution) in Logic Apps.
  • Clarify whether the 'Windows Plan' is required for all users or provide instructions for selecting Linux-based plans if available.
  • Offer examples of integrating with non-Microsoft email services (e.g., Gmail, Sendmail, Postfix) for notification delivery.
  • Add notes or sections that address cross-platform compatibility and alternative workflows for Linux/macOS users.
  • Review terminology and UI references to ensure they do not assume a Windows-centric environment where not necessary.
GitHub Create Pull Request
Devtest Labs Delete a lab virtual machine or a lab ...ain/articles/devtest-labs/devtest-lab-delete-lab-vm.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell scripting examples for automating VM deletion, with no mention of Linux-native tools or cross-platform alternatives such as Azure CLI, Bash, or REST API. The automation section is Windows-centric, assuming the user is on Windows or using PowerShell, and does not offer parity for Linux users.
Recommendations
  • Add equivalent examples using Azure CLI (az commands) for automating VM and lab deletion, which are cross-platform and commonly used on Linux.
  • Include Bash script examples for Linux users, demonstrating how to perform the same operations.
  • Mention REST API options for advanced users who may wish to automate via HTTP requests, which are platform-agnostic.
  • Explicitly state that PowerShell Core is available on Linux and macOS, if PowerShell must be used, and clarify compatibility.
  • Reorder automation sections to present cross-platform solutions (Azure CLI, REST API) before or alongside PowerShell examples.
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
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 exhibits subtle Windows bias by referencing PowerShell scripts and Azure CLI as primary integration methods, without mentioning Linux shell scripting or providing Linux-specific examples. The mention of 'PowerShell scripts' occurs before 'Azure CLI', and there are no explicit references to Bash, Linux tools, or cross-platform scripting approaches. No Linux-specific patterns or examples are given, and the documentation does not clarify platform parity for DevTest Labs usage in CI/CD pipelines.
Recommendations
  • Explicitly mention Bash and Linux shell scripting as supported integration methods alongside PowerShell and Azure CLI.
  • Provide Linux-specific examples for integrating DevTest Labs in CI/CD pipelines, such as using Bash scripts or Linux-based build agents.
  • Clarify that DevTest Labs and Azure Pipelines support both Windows and Linux environments, and highlight any platform-specific considerations.
  • List cross-platform tools and patterns first, or in parallel, rather than defaulting to Windows-centric approaches.
  • Include references to Linux-based CI/CD pipeline managers and open-source plug-ins, if available.
GitHub Create Pull Request
Devtest Labs Grant user permissions to specific lab policies ...st-lab-grant-user-permissions-to-specific-lab-policies.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 exclusively uses Azure PowerShell cmdlets and scripts for all examples, with no mention of Azure CLI, Bash, or Linux-native tooling. The instructions assume the reader is using PowerShell, which is traditionally a Windows-first tool, and do not provide Linux or cross-platform alternatives. There is no guidance for users who may be working on Linux or macOS, nor is there any mention of how to perform these tasks using Azure CLI or REST API.
Recommendations
  • Add equivalent examples using Azure CLI commands, which are cross-platform and commonly used on Linux and macOS.
  • Include notes or sections specifying how to perform these tasks on Linux and macOS, including installation instructions for Azure CLI.
  • Where possible, provide REST API examples or links for users who prefer scripting in Bash or other shells.
  • Clarify that PowerShell Core is available cross-platform, but still provide CLI alternatives for users who do not use PowerShell.
  • Reorder examples or provide parallel examples so that Windows and Linux approaches are presented with equal prominence.
GitHub Create Pull Request
← Previous Page 1 of 14 Next →