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 251-275 of 334 flagged pages
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-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 page demonstrates a notable Windows bias by exclusively providing Azure PowerShell examples for automation, referencing PowerShell as the only CLI method, and omitting equivalent instructions for Linux/macOS users (such as Azure CLI or Bash). Windows tools and terminology (PowerShell, Microsoft account, Windows Server links) are mentioned first and/or exclusively, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for all automation tasks, especially for adding lab users and role assignments.
  • Explicitly mention that Azure Cloud Shell supports Bash as well as PowerShell, and provide Bash instructions.
  • Reference cross-platform authentication options and avoid linking only to Windows Server documentation for Microsoft accounts.
  • Ensure that prerequisites and instructions are platform-neutral or provide parallel guidance for Linux/macOS users.
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 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 in its automation section by providing only a detailed PowerShell script and usage instructions, with Azure CLI mentioned only briefly and without example. The PowerShell example is extensive, while Linux/macOS users are left without equivalent Bash or Azure CLI walkthroughs, making automation less accessible for non-Windows users. Throughout the page, Windows-centric tools and patterns (PowerShell, screenshots of Azure portal) are presented first or exclusively.
Recommendations
  • Provide a complete Azure CLI (az) example for automating environment creation, including a sample script and usage instructions.
  • Include Bash shell script examples for Linux/macOS users where automation is discussed.
  • Explicitly state cross-platform compatibility for all steps, and clarify which tools work on Windows, Linux, and macOS.
  • Where PowerShell is used, offer equivalent commands in Azure CLI or Bash, and present them side-by-side or with equal prominence.
  • Add notes or links to official Azure CLI documentation for 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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation references running PowerShell scripts and Azure CLI for integration, but lists PowerShell before Azure CLI and does not provide explicit Linux/macOS examples or mention Bash. There is no mention of Linux-specific tools, patterns, or scripting approaches, and the examples and instructions are generic or Windows-centric.
Recommendations
  • Explicitly mention Bash and shell scripting as alternatives to PowerShell for Linux/macOS users.
  • Provide examples using Azure CLI commands in Bash or shell environments.
  • Clarify that REST API calls and Azure CLI are fully supported on Linux/macOS, and provide links to relevant cross-platform documentation.
  • Where scripting is discussed, show both PowerShell and Bash examples side-by-side.
  • Reference Linux-based CI/CD tools and agents (e.g., self-hosted Linux build agents) in addition to Windows-based ones.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on PowerShell, with all examples and instructions using Azure PowerShell cmdlets. There are no CLI (az), Bash, or Linux/macOS-specific instructions or examples. The prerequisite step is to install Azure PowerShell, which is most commonly used on Windows, and no mention is made of cross-platform alternatives. This creates friction for Linux and macOS users who may prefer or require Bash or Azure CLI.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell scripts and tasks.
  • Explicitly mention that Azure PowerShell is cross-platform, but also provide Bash/CLI alternatives.
  • Reorder examples so that CLI and PowerShell are presented side-by-side, or at least alternate which is shown first.
  • Include installation instructions for Azure CLI and note its compatibility with Linux/macOS.
  • Add a section discussing tool choice for different platforms.
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-13 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 when creating a VM, and by showing screenshots and instructions that reference Windows VMs. There are no examples, screenshots, or guidance for Linux-based VMs, nor any mention of Linux-specific considerations or parity in the hibernation feature.
Recommendations
  • Include explicit examples and screenshots for creating and hibernating Linux VMs (e.g., Ubuntu, CentOS) in DevTest Labs.
  • Clarify whether hibernation is supported for Linux VMs, and list any OS-specific limitations or requirements.
  • Provide guidance on connecting to Linux VMs (e.g., SSH instructions) alongside Windows (RDP) instructions.
  • Ensure that images and step-by-step instructions do not assume Windows as the default or only use case.
GitHub Create Pull Request
Devtest Labs Deploy Azure DevTest Labs (Enterprise Reference Architecture) ...les/devtest-labs/devtest-lab-reference-architecture.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by referencing Windows-centric tools (Remote Desktop Gateway, RDP) and linking to Windows Server documentation for remote access. No Linux equivalents (such as SSH gateways or Linux remote access solutions) are mentioned, and examples for remote connectivity focus exclusively on Windows patterns. Automation examples mention PowerShell first, but do include Azure CLI and REST APIs, which are cross-platform.
Recommendations
  • Include Linux/macOS remote access options, such as SSH bastion hosts or alternatives to RDP for VM connectivity.
  • Provide links to documentation for setting up secure SSH access and Linux-based remote gateways in Azure.
  • When listing automation tools, alternate the order or explicitly state cross-platform compatibility (e.g., 'PowerShell, Azure CLI, Bash, REST APIs').
  • Add examples or references for managing DevTest Labs from Linux/macOS environments.
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-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 moderate Windows bias. Windows-centric tools (PowerShell, Visual Studio, Fiddler, Active Directory domain join) are referenced frequently, often without Linux/macOS equivalents or examples. Automation and scripting are described primarily with PowerShell, and links to quickstarts and templates are labeled as 'create-lab-windows-vm-*', with no explicit mention of Linux VM creation. Artifact examples and VM customization focus on Windows tools, and deletion of VMs is described via PowerShell script only. Linux options are mentioned in passing (e.g., ARM templates can define Windows or Linux environments), but are not given equal prominence or examples.
Recommendations
  • Add explicit Linux/macOS examples for lab creation, VM provisioning, and automation (e.g., Bash, Azure CLI, Terraform for Linux VMs).
  • Include Linux-specific tools and artifacts in customization examples (e.g., install Apache, NGINX, or other common Linux software).
  • Provide equivalent instructions for deleting VMs/labs using Bash or Azure CLI, not just PowerShell.
  • Balance references to Windows tools (Visual Studio, Fiddler, Active Directory) with Linux alternatives (VS Code, Wireshark, LDAP integration).
  • Rename quickstart/template links to include both Windows and Linux VM creation, or provide parallel Linux-focused guides.
GitHub Create Pull Request
Devtest Labs Upload a VHD file to lab storage by using Storage Explorer ...-labs/devtest-lab-upload-vhd-using-storage-explorer.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It references PowerShell as a method for obtaining the storage account name and includes screenshots and instructions for using PowerShell, which is primarily a Windows tool. There is no mention of Linux/macOS CLI alternatives (such as Azure CLI or Bash), nor are Linux-specific patterns or tools discussed. While Azure Storage Explorer itself is cross-platform, the supporting instructions and examples lean toward Windows-centric workflows.
Recommendations
  • Provide instructions and screenshots for obtaining the storage account name using Azure CLI or Bash, which are available on Linux/macOS.
  • Include alternative steps for users who do not have PowerShell installed, especially on Linux/macOS.
  • Clearly state that PowerShell is optional and link to cross-platform alternatives.
  • Balance examples and screenshots to show parity between Windows and Linux/macOS environments.
GitHub Create Pull Request
Devtest Labs Troubleshoot Artifacts on Lab Virtual Machines ...vtest-labs/devtest-lab-troubleshoot-apply-artifacts.md
Medium Priority View Details →
Scanned: 2026-01-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 demonstrates a notable Windows bias. Troubleshooting steps and examples are primarily provided for Windows VMs, including detailed PowerShell commands, Windows file paths, and screenshots of Windows tools. Linux equivalents are either missing, referenced only via external links, or not described in detail. This creates friction for Linux users attempting to troubleshoot artifacts on their lab VMs.
Recommendations
  • Provide equivalent Linux troubleshooting steps alongside Windows instructions, including example commands for Bash/SSH.
  • Include file paths and log locations for Linux VMs directly in the documentation, not just via external links.
  • Show how to check artifact status and logs using Azure CLI or SSH for Linux VMs, not only PowerShell.
  • Add screenshots or terminal output examples from Linux environments where appropriate.
  • Ensure that artifact structure and script troubleshooting sections include Linux-specific examples and references.
GitHub Create Pull Request
Devtest Labs Create and deploy labs with Azure Resource Manager (ARM) templates ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-use-arm-and-powershell-for-lab-resources.md
Medium Priority View Details →
Scanned: 2026-01-13 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 a moderate Windows bias. Windows-based examples (such as creating labs with Windows Server VMs) are presented first and exclusively in the quickstart section. Automation instructions and linked tasks heavily favor Azure PowerShell, with no equivalent Bash or Linux shell examples. Several common lab tasks (custom image creation, VHD upload, user management) are documented only with PowerShell, omitting CLI or Linux-native alternatives.
Recommendations
  • Provide quickstart examples for both Windows and Linux VM creation, giving equal prominence.
  • Include automation instructions and sample scripts using Azure CLI and Bash alongside PowerShell for all major tasks.
  • Add links to Linux/macOS-specific guides or note any differences in workflow for non-Windows users.
  • Ensure that repository references highlight both PowerShell and CLI/Bash script resources.
  • Explicitly mention cross-platform compatibility in relevant sections.
GitHub Create Pull Request
Devtest Labs Extend Azure DevTest Labs with Azure Functions ...es/devtest-labs/extend-devtest-labs-azure-functions.md
Medium Priority View Details →
Scanned: 2026-01-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 demonstrates a notable Windows bias. It exclusively uses Visual Studio for building and deploying the sample, with no mention of cross-platform alternatives like VS Code or CLI-based workflows. The walkthrough references Windows-specific artifacts (Windows Update), and PowerShell is highlighted as a method for creating service principals, with no Linux shell or Bash examples. There are no instructions or screenshots for Linux/macOS users, nor any mention of how to complete the process outside of Windows/Visual Studio.
Recommendations
  • Add instructions for building and deploying the sample using cross-platform tools such as VS Code, Azure CLI, or GitHub Actions.
  • Include Linux/macOS-specific examples for creating service principals (e.g., Bash/Azure CLI commands).
  • Provide parity for artifact application, such as mentioning or demonstrating Linux update artifacts if available.
  • Add screenshots and workflow steps for non-Windows environments, especially for development and deployment.
  • Clarify that the sample can be adapted for Linux/macOS and provide guidance for doing so.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a notable Windows bias by providing detailed instructions and examples for PowerShell, a Windows-centric tool, without offering equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI). The PowerShell method is presented first and in more detail, while no Linux-native scripting or cross-platform CLI alternatives are discussed. This may create friction for non-Windows users attempting to automate VM imports.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Provide Bash script samples for Linux users, or at least describe how to invoke the REST API using curl or similar tools.
  • Explicitly state platform requirements or limitations for the PowerShell script, and suggest alternatives for Linux/macOS.
  • Reorder or balance the presentation so that REST API and CLI methods are shown before or alongside PowerShell, to avoid Windows-first bias.
GitHub Create Pull Request
Devtest Labs Move DevTest Labs to another region ...cs/blob/main/articles/devtest-labs/how-to-move-labs.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias, especially in the section on swapping OS disks, where only PowerShell commands are provided and referenced. The use of PowerShell and references to Windows-specific articles (e.g., changing OS disks using PowerShell) are prominent, with no equivalent Bash, Azure CLI, or Linux/macOS instructions. While AzCopy is cross-platform, its usage is only shown within a PowerShell context, and the overall workflow assumes familiarity with Windows tooling.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples for disk operations, especially for swapping OS disks and using AzCopy.
  • Reference cross-platform documentation for tasks like changing the OS disk, not just Windows/PowerShell-specific articles.
  • Clarify that AzCopy can be used on Linux/macOS and provide example commands in Bash.
  • Where PowerShell is used, add a parallel section or code block for Linux/macOS users.
  • Explicitly mention that all steps can be performed from Azure Cloud Shell (which supports Bash and PowerShell) and show both options.
GitHub Create Pull Request
Devtest Labs How to delete and export personal data ...n/articles/devtest-labs/personal-data-delete-export.md
Medium Priority View Details →
Scanned: 2026-01-13 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 provides only Azure PowerShell examples for exporting personal data, with no mention of Linux/macOS alternatives such as Azure CLI, Bash, or REST API. The instructions and sample code are heavily focused on PowerShell, which is primarily a Windows tool, and there is no guidance for users on non-Windows platforms. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
  • Add equivalent Azure CLI examples for exporting personal data, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Include Bash script samples or REST API instructions for users who prefer shell scripting or direct API calls.
  • Explicitly state platform requirements and provide installation guidance for PowerShell on Linux/macOS if PowerShell is required.
  • Present cross-platform methods first or side-by-side, rather than focusing solely on Windows-centric tools.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation references PowerShell specifically when discussing ARM template deployments, implying a Windows-centric workflow. No Linux or cross-platform CLI examples are provided, and PowerShell is mentioned as the default scripting environment. There are no explicit Linux/macOS instructions or parity in example commands.
Recommendations
  • Include equivalent Azure CLI (az) examples for ARM template deployments, which are cross-platform and commonly used on Linux/macOS.
  • Rephrase references to PowerShell to clarify that other tools (such as Azure CLI or Bash scripts) can be used.
  • When mentioning scripting or automation, provide both PowerShell and Bash/Azure CLI examples, or link to cross-platform documentation.
  • Avoid implying PowerShell is the only or primary method unless there is a technical limitation.
GitHub Create Pull Request
Devtest Labs Use commands to start and stop lab VMs ...t-labs/use-command-line-start-stop-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-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 shows a moderate Windows bias. PowerShell is presented first in every section, and the Azure CLI examples explicitly separate Bash and Windows syntax, but Windows command syntax is shown alongside Bash rather than focusing on cross-platform Bash as the default. The PowerShell section is more detailed and uses Windows-centric cmdlets. There is no mention of macOS or Linux-specific considerations, and some instructions (e.g., variable setting) are shown for Windows batch before Bash, which may confuse Linux users.
Recommendations
  • Present Bash (Linux/macOS) examples before Windows batch syntax in Azure CLI sections.
  • Add explicit notes about macOS and Linux compatibility for Azure CLI and PowerShell (where applicable).
  • Balance the detail level between PowerShell and Azure CLI sections, ensuring Linux users have equally comprehensive instructions.
  • Consider adding troubleshooting tips for Linux/macOS users (e.g., shell differences, installation notes).
  • Use cross-platform variable setting syntax (e.g., Bash) as the default in CLI examples.
GitHub Create Pull Request
Devtest Labs Create a network isolated lab ...s/blob/main/articles/devtest-labs/network-isolation.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits moderate Windows bias. The only script provided for converting an existing lab to isolated network mode is a PowerShell script (.ps1), with no mention of Bash or cross-platform alternatives. PowerShell is a Windows-centric tool, and its exclusive use may create friction for Linux/macOS users. Additionally, the reference to automation mentions PowerShell before Azure CLI, and does not provide explicit CLI or Bash examples. The rest of the instructions are portal-based and generally platform-neutral, but scripting and automation guidance leans toward Windows tools.
Recommendations
  • Provide Bash or Azure CLI equivalents for the PowerShell script used to convert labs to isolated network mode.
  • Explicitly mention and provide examples for Azure CLI automation alongside PowerShell, ensuring parity for Linux/macOS users.
  • Where scripting is referenced, avoid listing Windows tools first or exclusively; present cross-platform options together.
  • Consider linking to or providing documentation for running PowerShell Core on Linux/macOS if PowerShell is required.
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-13 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 by primarily referencing PowerShell and Windows-centric tools for exporting and managing Azure DevTest Labs usage data. PowerShell is presented as the main scripting example, with no equivalent Bash, CLI, or Linux/macOS workflow provided. Windows tools like SQL Server and Power BI are mentioned before or instead of cross-platform alternatives. There is no guidance for Linux/macOS users on how to perform these tasks using their native environments.
Recommendations
  • Provide Azure CLI and Bash examples for exporting resource usage, alongside PowerShell.
  • Explicitly mention that Azure Functions and Automation Runbooks support Python and other cross-platform languages, and provide sample code.
  • Include references to cross-platform visualization tools (e.g., Grafana) and database solutions (e.g., PostgreSQL, MySQL) in addition to SQL Server and Power BI.
  • Add a section or notes on how Linux/macOS users can set up and automate exports without relying on PowerShell.
  • Ensure examples and tool recommendations are presented in a platform-neutral order or grouped by OS.
GitHub Create Pull Request
Devtest Labs Define VM start order with Azure Automation ...devtest-labs/start-machines-use-automation-runbooks.md
Medium Priority View Details →
Scanned: 2026-01-13 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 automation, with no mention of Bash, Python, or other cross-platform alternatives. All examples and instructions are tailored to PowerShell and Azure Automation, which is most commonly used on Windows. There are no Linux/macOS-specific instructions or examples, and Windows-centric tools and modules (e.g., AzureRM, PowerShell jobs) are used throughout.
Recommendations
  • Provide equivalent Bash or Python scripts for Linux/macOS users.
  • Include instructions for running automation tasks using Azure CLI or REST API, which are cross-platform.
  • Add notes or sections highlighting how Linux/macOS users can set up and execute similar automation workflows.
  • Mention platform-agnostic alternatives to PowerShell modules, such as Azure CLI commands for VM management.
  • Ensure that examples are not exclusively PowerShell, or at least present Linux/macOS options alongside Windows ones.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides only Windows VM creation examples, specifically instructing users to select a 'Windows Server 2019 Datacenter' base when adding a VM to the lab. There are no examples or guidance for creating Linux-based VMs, nor are Linux-specific options, patterns, or troubleshooting tips mentioned. This may lead Linux/macOS users to believe that only Windows VMs are supported or recommended, creating friction for those intending to use Linux environments.
Recommendations
  • Include examples for creating Linux VMs (e.g., Ubuntu, CentOS) alongside Windows examples.
  • Explicitly mention that both Windows and Linux VM images are supported in DevTest Labs.
  • Provide guidance on Linux-specific settings, such as SSH key authentication, default usernames, and password requirements.
  • Add screenshots and walkthroughs for Linux VM creation steps.
  • Reference documentation for connecting to Linux VMs (e.g., via SSH) and managing Linux artifacts.
GitHub Create Pull Request
Devtest Labs Create activity log alerts for labs ...-docs/blob/main/articles/devtest-labs/create-alerts.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes creating activity log alerts using the Azure portal GUI, which is a cross-platform web interface. However, it does not provide any command-line examples (such as Azure CLI, Bash, or PowerShell), nor does it mention automation or scripting approaches. There is no explicit Windows bias in terms of mentioning Windows-specific tools or PowerShell, but the lack of Linux-oriented examples (e.g., Azure CLI commands, Bash scripts) means Linux users do not see parity in automation or scripting guidance.
Recommendations
  • Add examples using Azure CLI commands for creating and managing activity log alerts, as Azure CLI is cross-platform and widely used on Linux.
  • If automation is relevant, include Bash script snippets for Linux users.
  • If PowerShell is mentioned in related documentation, ensure Azure CLI or Bash equivalents are provided and referenced.
  • Explicitly state that the Azure portal is accessible from any OS/browser to reinforce cross-platform support.
  • Consider a section comparing GUI and command-line approaches for alert management, highlighting platform-neutral options.
GitHub Create Pull Request
Devtest Labs Store secrets in a key vault ...devtest-labs/devtest-lab-store-secrets-in-key-vault.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by mentioning Windows VM passwords as the first example of secrets, while Linux VM SSH keys are mentioned second. There are no platform-specific examples or instructions for either Windows or Linux, but the order of mention and lack of explicit Linux-focused guidance (such as handling SSH keys or integration with Linux tools) suggests a slight preference for Windows scenarios. No PowerShell or Windows-only tools are referenced, but Linux parity could be improved.
Recommendations
  • Provide explicit examples for both Windows and Linux scenarios, such as storing and retrieving SSH keys for Linux VMs.
  • Alternate the order of examples to avoid always listing Windows first.
  • Include platform-specific guidance or screenshots for Linux users, such as using secrets for SSH key injection.
  • Reference Linux command-line tools or scripts where relevant, alongside any Windows tools.
GitHub Create Pull Request
Devtest Labs Access, claim, and connect to lab VMs .../main/articles/devtest-labs/tutorial-use-custom-lab.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in the 'Connect to a lab VM' section, where Windows connection methods (RDP) are mentioned before Linux methods (Azure CLI, Native SSH). The instructions for connecting to Windows VMs reference RDP and link to a dedicated Windows VM connection guide, while Linux connection methods are listed after and referenced with less detail. The page also refers to Windows-specific tools (RDP) before Linux equivalents.
Recommendations
  • Present connection instructions for Windows and Linux VMs in parallel, rather than listing Windows first.
  • Provide equal detail and visibility for Linux connection methods (Azure CLI, Native SSH) as for Windows (RDP).
  • Include screenshots or step-by-step instructions for Linux connection methods, matching the detail given to Windows.
  • Where possible, avoid Windows-centric terminology and tools unless contextually necessary, and ensure Linux tools are equally represented.
  • Consider a table or side-by-side comparison for connection options for both OS types to improve parity.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits Windows bias by referencing Azure PowerShell and Visual Studio as primary tools for deploying and managing ARM templates, with Azure PowerShell mentioned before Azure CLI. Visual Studio is highlighted as a resource group deployment tool, which is Windows-centric, while Linux-native alternatives are not mentioned or linked. There are no explicit Linux or cross-platform editor/tool examples, and the deployment commands prioritize Windows workflows.
Recommendations
  • Provide equal prominence to Azure CLI examples, and mention it before or alongside Azure PowerShell.
  • Include references to cross-platform editors such as VS Code, and deployment options from Linux/macOS terminals.
  • Add explicit Linux/macOS command-line examples for ARM template deployment.
  • Mention alternative tools for ARM template development and deployment that are available on Linux, such as using GitHub Actions, VS Code, or native shell scripts.
  • Clarify that all deployment steps can be performed on Linux, macOS, and Windows, and provide links to platform-specific guides.
GitHub Create Pull Request
Devtest Labs Hibernation for virtual machines ...main/articles/devtest-labs/devtest-lab-hibernate-vm.md
Medium Priority View Details →
Scanned: 2026-01-11 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 by referencing screenshots and instructions that focus on Windows VMs. There are no examples, screenshots, or instructions for creating or managing Linux-based VMs with hibernation, nor is there mention of Linux-specific considerations or parity in the feature's support.
Recommendations
  • Include explicit examples and screenshots for creating and hibernating Linux VMs in Azure DevTest Labs.
  • Clarify whether hibernation is supported for Linux VMs, and if so, list supported distributions and versions.
  • Provide guidance on any Linux-specific configuration steps or limitations related to hibernation.
  • Ensure that instructions and illustrations alternate or equally represent both Windows and Linux scenarios.
  • Add notes or tables summarizing OS support for hibernation, including both Windows and Linux.
GitHub Create Pull Request
← Previous Page 11 of 14 Next →