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 276-300 of 334 flagged pages
Devtest Labs Encrypt Disks with Customer-Managed Keys ...es/devtest-labs/encrypt-disks-customer-managed-keys.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 how to manage disk encryption using the Azure portal GUI, which is heavily oriented toward Windows users. There are no command-line examples (such as Azure CLI, Bash, or PowerShell), nor are there any Linux-specific instructions or references. The workflow assumes use of graphical tools and patterns familiar to Windows users, with no mention of Linux workflows or parity.
Recommendations
  • Add Azure CLI and/or PowerShell command examples for all major steps, including enabling system-assigned identity, assigning roles, and configuring disk encryption sets.
  • Include explicit instructions or examples for Linux users, such as using Bash scripts or CLI commands.
  • Reference cross-platform tools and clarify that the process can be completed from any OS, not just via the Azure portal GUI.
  • Provide screenshots or terminal output examples for Linux environments where relevant.
  • Ensure that documentation sections do not assume a Windows-first workflow and mention Linux parity where possible.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively providing a Windows Server 2019 Datacenter VM example when guiding users to create a lab VM. There are no Linux VM examples, nor is there mention of Linux images or instructions for Linux-specific configurations. The tutorial implicitly prioritizes Windows by not presenting Linux as an option or alternative.
Recommendations
  • Include examples for creating Linux-based VMs (e.g., Ubuntu, CentOS) alongside Windows examples.
  • Explicitly mention that both Windows and Linux images are available and supported in Azure DevTest Labs.
  • Provide instructions or screenshots for Linux VM setup, including relevant differences (e.g., SSH key authentication instead of password).
  • Add notes or tips for Linux-specific configurations, such as artifact installation or remote access methods.
  • Ensure parity in documentation by alternating or balancing Windows and Linux examples throughout the tutorial.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias by referencing Azure PowerShell and Visual Studio as primary deployment tools, with Azure PowerShell mentioned before Azure CLI. The related content section highlights Visual Studio (a Windows-centric IDE) for ARM template deployment, without mentioning Linux-native alternatives or editors. There are no explicit Linux or cross-platform examples, and Linux-friendly tooling is not discussed.
Recommendations
  • Provide explicit Linux deployment examples using Azure CLI and Bash.
  • Mention cross-platform editors such as VS Code and their ARM template extensions.
  • List Azure CLI before or alongside Azure PowerShell when describing deployment commands.
  • Include instructions for generating SaS tokens and deploying templates from Linux/macOS environments.
  • Add references to Linux documentation or tutorials for ARM template deployment.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively providing a Windows Server 2019 Datacenter VM example when guiding users to create a lab VM. There are no Linux VM examples, nor is there mention of Linux images or configuration differences for Linux VMs. The tutorial implicitly assumes Windows as the default, which may exclude or confuse users seeking to deploy Linux-based environments.
Recommendations
  • Include Linux VM creation examples alongside Windows examples, such as Ubuntu or CentOS images.
  • Explicitly mention that both Windows and Linux VMs are supported, and highlight any differences in configuration (e.g., SSH keys for Linux vs. passwords for Windows).
  • Provide screenshots and step-by-step instructions for creating a Linux VM in the lab.
  • Add notes or tips about Linux-specific settings, such as selecting SSH authentication, configuring artifacts for Linux, and post-deployment access methods.
  • Ensure parity in documentation by alternating or balancing Windows and Linux references throughout tutorials.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes how to create 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, PowerShell, or Bash), nor does it mention automation or scripting approaches. There is no explicit Windows bias in terms of tools or examples, but the lack of CLI examples means Linux users who prefer terminal-based workflows are not served. If scripting were discussed, Windows/PowerShell examples would likely appear first, as is common in Azure docs.
Recommendations
  • Add examples using Azure CLI commands to create and manage activity log alerts, ensuring Linux users have parity.
  • If PowerShell examples are added, ensure Azure CLI or Bash equivalents are presented alongside or before them.
  • Explicitly mention that all steps can be performed from any OS via the Azure portal, but provide links or sections for automation via CLI for cross-platform users.
  • Include a section on automating alert creation using ARM templates or Bicep, which are platform-agnostic.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively using Windows 11 Pro as the example OS when creating a VM, and by referencing screenshots and instructions that appear to be tailored to Windows VMs. There are no examples, screenshots, or instructions for creating or hibernating Linux-based VMs, nor is there mention of Linux-specific considerations or parity in the hibernation feature.
Recommendations
  • Include examples and screenshots for creating and hibernating Linux-based VMs in Azure DevTest Labs.
  • Explicitly mention supported Linux distributions and any differences in hibernation support or configuration for Linux VMs.
  • Provide guidance for Linux users, such as SSH connection instructions, and clarify any OS-specific limitations or requirements.
  • Ensure that documentation does not default to Windows-first language or examples, and that both platforms are represented equally in instructions and visuals.
GitHub Create Pull Request
Devtest Labs Stop and resize lab VMs ...ob/main/articles/devtest-labs/devtest-lab-resize-vm.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively describes resizing Azure DevTest Lab VMs using the Azure portal GUI, with screenshots and instructions that implicitly assume a Windows-centric workflow. There are no examples or mentions of Linux-specific tools, command-line interfaces (such as Bash or Azure CLI), or Linux user workflows. The absence of Linux or cross-platform command-line instructions suggests a bias toward Windows users and GUI-based management.
Recommendations
  • Add Azure CLI and/or PowerShell command examples for stopping, resizing, and starting VMs, with explicit instructions for both Windows and Linux environments.
  • Include notes or sections on how Linux users can perform these tasks from the terminal, highlighting any platform-specific considerations.
  • Provide screenshots or terminal output examples for Linux users, not just GUI screenshots.
  • Clarify that the Azure portal is cross-platform, but also mention alternative methods for users who prefer command-line or automation workflows.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page mentions secrets for both Windows and Linux VMs, but provides examples and context primarily around Windows use cases (e.g., passwords for Windows VMs) and does not include explicit Linux-focused examples (such as SSH key usage or Linux command-line integration). There are no PowerShell-heavy or Windows tool-specific instructions, but the examples and screenshots do not demonstrate Linux parity.
Recommendations
  • Add explicit examples for storing and retrieving SSH keys for Linux VMs, including screenshots or code snippets.
  • Include instructions or references for using secrets with Linux VM creation, such as integration with cloud-init or Linux shell scripts.
  • Ensure that both Windows and Linux scenarios are equally represented in step-by-step guides and visuals.
  • Mention Linux-specific considerations or workflows where relevant, such as using secrets for package installation or configuration management on Linux.
GitHub Create Pull Request
Devtest Labs Encrypt Disks with Customer-Managed Keys ...es/devtest-labs/encrypt-disks-customer-managed-keys.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes disk encryption management in Azure DevTest Labs using the Azure portal GUI, with screenshots and navigation patterns typical of Windows environments. There are no CLI, PowerShell, or Linux shell examples, nor any mention of how to perform these steps on Linux or cross-platform tools. The workflow assumes users interact with the Azure portal, which is most commonly accessed from Windows, and does not provide parity for Linux users who may prefer command-line or automation approaches.
Recommendations
  • Add equivalent instructions using Azure CLI commands, which are cross-platform and commonly used on Linux.
  • Include PowerShell examples for Windows users, but ensure Azure CLI or REST API examples are presented first or alongside.
  • Explicitly mention that all steps can be performed from any OS via the Azure portal, but highlight command-line alternatives for Linux users.
  • Provide links to documentation on using Azure CLI and REST API for disk encryption management.
  • Add a section comparing GUI and CLI workflows, noting any differences or limitations.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias in the 'Connect to a lab VM' section. When Bastion is unavailable, Windows connection instructions (RDP) are mentioned before Linux connection instructions (Azure CLI/Native SSH). Additionally, the Windows tool (RDP) is explicitly named, while Linux connection methods are grouped together and referenced less prominently.
Recommendations
  • Present Windows and Linux connection options in parallel, rather than listing Windows first.
  • Explicitly name Linux connection tools (e.g., SSH, Azure CLI) with equal prominence to RDP.
  • Provide direct example commands or screenshots for both Windows and Linux connection methods.
  • Ensure that references to detailed instructions for both OS types are equally visible and accessible.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/create-alerts.md ...-docs/blob/main/articles/devtest-labs/create-alerts.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes how to create activity log alerts using the Azure portal, which is a graphical interface most commonly accessed from Windows environments. There are no examples or references to command-line methods (such as Azure CLI, Bash, or PowerShell), nor is there any mention of Linux-specific workflows or tools. The absence of CLI or script-based instructions means Linux users, who may prefer or require non-GUI methods, are not served equally.
Recommendations
  • Add equivalent instructions for creating activity log alerts using Azure CLI, including example commands that work on Linux and macOS.
  • Include PowerShell examples only if accompanied by Bash/Azure CLI examples, and present them in parallel.
  • Explicitly mention that the Azure portal is accessible from any OS/browser, but provide parity for users who prefer or require command-line interfaces.
  • Reference documentation for automating alert creation via ARM templates or REST API, which are platform-agnostic.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-store-secrets-in-key-vault.md ...devtest-labs/devtest-lab-store-secrets-in-key-vault.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits a subtle Windows bias by mentioning Windows VM password secrets before Linux SSH keys, and by not providing concrete Linux-specific examples or instructions. All examples and screenshots are generic and do not demonstrate Linux workflows, such as using SSH keys or integrating secrets into Linux VM creation. There are no references to Linux command-line tools or patterns.
Recommendations
  • Provide explicit examples for both Windows and Linux scenarios, such as storing and retrieving SSH keys for Linux VMs.
  • Include screenshots or code snippets showing the use of secrets in Linux VM creation workflows.
  • Mention Linux tools (e.g., bash, cloud-init) and how secrets can be injected or used during Linux VM provisioning.
  • Ensure that instructions and terminology are balanced between Windows and Linux, avoiding Windows-first ordering.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-auto-shutdown.md ...ain/articles/devtest-labs/devtest-lab-auto-shutdown.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation demonstrates a Windows bias primarily in the Logic Apps creation workflow, where the 'Windows Plan' is referenced as the default and no mention is made of Linux-based hosting or alternatives. The email integration example exclusively uses Office 365 Outlook, a Microsoft-centric tool, with no mention of Linux-friendly or open-source email clients. Throughout, there are no CLI or script examples (e.g., Bash, PowerShell), but where platform specifics are mentioned, Windows is referenced first or exclusively.
Recommendations
  • Clarify whether Logic Apps can be hosted on Linux plans and provide instructions or notes for Linux-based hosting if supported.
  • Include examples or notes for integrating with non-Microsoft email clients (e.g., Gmail, Thunderbird, or SMTP) to support Linux users.
  • If any scripting or automation is possible, provide both PowerShell and Bash examples for configuring autoshutdown or notifications.
  • Avoid using terms like 'Windows Plan' without context; specify if Linux hosting is available or required.
  • Add explicit statements about cross-platform compatibility for all steps, especially those involving Azure portal, Logic Apps, and email integration.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-resize-vm.md ...ob/main/articles/devtest-labs/devtest-lab-resize-vm.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes resizing Azure DevTest Lab VMs using the Azure portal GUI, with screenshots and instructions that implicitly assume a Windows environment (e.g., toolbar navigation, GUI-centric workflow). There are no examples or mentions of resizing VMs via command-line tools such as Azure CLI, PowerShell, or Bash, nor are there instructions for Linux users or those working in non-GUI environments.
Recommendations
  • Add equivalent instructions for resizing VMs using Azure CLI and PowerShell, with explicit examples for both Windows and Linux shells.
  • Include screenshots or terminal output for command-line workflows on both Windows (PowerShell) and Linux (Bash).
  • Mention cross-platform tools and clarify that resizing can be performed from any OS using CLI tools.
  • Add a section comparing GUI and CLI workflows, highlighting parity and differences for Windows and Linux users.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-hibernate-vm.md ...main/articles/devtest-labs/devtest-lab-hibernate-vm.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 operating system when creating a VM, and by referencing screenshots and instructions that imply Windows usage (e.g., 'select your Windows VM'). There are no examples, instructions, or screenshots for Linux-based VMs, nor is there any mention of Linux-specific considerations or parity in the hibernation process.
Recommendations
  • Include explicit instructions and screenshots for creating and hibernating Linux-based VMs in Azure DevTest Labs.
  • Mention supported Linux distributions and any differences or limitations in hibernation support for Linux VMs.
  • Provide examples that alternate between Windows and Linux, or present both side-by-side, to ensure parity.
  • Clarify whether features such as hibernation, security options, and artifact configuration apply equally to Linux VMs.
  • Avoid language and imagery that exclusively references Windows unless the feature is truly Windows-only; if so, state this clearly.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/encrypt-disks-customer-managed-keys.md ...es/devtest-labs/encrypt-disks-customer-managed-keys.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes procedures using the Azure portal GUI, which is most commonly used on Windows systems. There are no command-line examples (such as Azure CLI, Bash, or PowerShell), nor are there any references to Linux-specific tools or workflows. The lack of Linux command-line instructions or parity in example coverage suggests a bias toward Windows-centric usage patterns.
Recommendations
  • Add Azure CLI and/or PowerShell command examples for all major steps, ensuring cross-platform compatibility.
  • Explicitly mention that the procedures can be performed from Linux, macOS, or Windows systems, and provide instructions for each where relevant.
  • Include screenshots or terminal output from Linux environments where applicable.
  • Reference Linux-specific documentation or tools if there are differences in workflow or prerequisites.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/tutorial-create-custom-lab.md ...in/articles/devtest-labs/tutorial-create-custom-lab.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively providing instructions and examples for creating a Windows Server 2019 Datacenter VM, with no mention of Linux VM options or Linux-specific configuration steps. The tutorial implicitly assumes Windows as the default platform for VM creation, omitting parity for Linux users.
Recommendations
  • Include examples for creating Linux-based VMs (e.g., Ubuntu, CentOS) alongside Windows examples.
  • Add instructions or screenshots for Linux VM configuration, such as SSH key setup and Linux-specific artifact installation.
  • Explicitly mention that both Windows and Linux VMs are supported, and highlight any differences in setup or user access.
  • Provide guidance for connecting to Linux VMs (e.g., SSH access) in addition to Windows (RDP).
  • Ensure artifact and automation examples (ARM templates, scripts) demonstrate both Windows and Linux scenarios.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/tutorial-use-custom-lab.md .../main/articles/devtest-labs/tutorial-use-custom-lab.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents connection options for Windows VMs (RDP) before Linux VMs (Azure CLI/Native SSH), and explicitly names the Windows tool (RDP) while Linux options are grouped together. This ordering and explicit mention of Windows tools suggest a subtle Windows bias, prioritizing Windows connection patterns and terminology.
Recommendations
  • Present connection options for Windows and Linux VMs in parallel, rather than listing Windows first.
  • Explicitly name Linux connection tools (e.g., SSH, Azure CLI) with equal prominence to RDP.
  • Provide direct, side-by-side examples or links for both Windows and Linux connection methods.
  • Ensure screenshots and step-by-step instructions are balanced between Windows and Linux scenarios.
  • Consider including a table summarizing connection options for both OS types for clarity and parity.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-resize-vm.md ...ob/main/articles/devtest-labs/devtest-lab-resize-vm.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on resizing VMs using the Azure portal GUI, with screenshots and instructions that implicitly assume a Windows-centric workflow. There are no examples or mentions of resizing VMs via command-line tools such as Azure CLI, PowerShell, or Bash, nor are there instructions tailored for Linux users or remote management scenarios. The absence of Linux-specific guidance or parity in tooling demonstrates a bias toward Windows users and GUI-based workflows.
Recommendations
  • Add examples for resizing VMs using Azure CLI and Bash, which are commonly used on Linux and macOS.
  • Include PowerShell examples if relevant, but ensure they are presented alongside CLI/Bash equivalents.
  • Mention remote management options for users who may not use the Azure portal GUI, such as SSH or command-line interfaces.
  • Clarify that the instructions apply to all VM operating systems, and provide guidance for connecting to both Windows and Linux VMs after resizing.
  • Add screenshots or terminal output examples for Linux users where appropriate.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-hibernate-vm.md ...main/articles/devtest-labs/devtest-lab-hibernate-vm.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively using Windows 11 Pro as the example OS when creating a VM, and by referencing 'your Windows VM' in screenshots and instructions. There are no examples, screenshots, or instructions for Linux-based VMs, nor any mention of Linux-specific considerations or parity in the hibernation process.
Recommendations
  • Include examples and screenshots for creating and hibernating Linux-based VMs alongside Windows examples.
  • Explicitly mention supported Linux distributions and any differences in hibernation support or configuration.
  • Use neutral language in instructions and screenshots (e.g., 'Select your VM' instead of 'Select your Windows VM').
  • Add a section detailing any Linux-specific prerequisites or limitations for VM hibernation.
  • Ensure that artifact and security configuration examples cover both Windows and Linux scenarios.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/encrypt-disks-customer-managed-keys.md ...es/devtest-labs/encrypt-disks-customer-managed-keys.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes disk encryption management in Azure DevTest Labs using the Azure portal GUI, with screenshots and step-by-step instructions. There are no examples or references to command-line tools, scripts, or automation methods (such as Azure CLI, PowerShell, or Bash), nor is there any mention of Linux-specific workflows or considerations. The portal-centric approach implicitly favors Windows users, as Linux administrators often prefer or require CLI-based automation and scripting.
Recommendations
  • Add equivalent instructions for managing disk encryption using Azure CLI and/or Azure PowerShell, with example commands.
  • Include Bash script examples for Linux users to automate disk encryption set assignment and validation.
  • Mention cross-platform tools and clarify that all steps can be performed from Linux, macOS, or Windows environments using CLI tools.
  • Provide links to CLI documentation and reference automation best practices for both Windows and Linux users.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-store-secrets-in-key-vault.md ...devtest-labs/devtest-lab-store-secrets-in-key-vault.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page mentions secrets for both Windows and Linux VMs, but provides examples and screenshots that focus on generic secret storage and usage without platform-specific details. However, the initial mention of 'passwords for your Windows VMs' before 'public SSH keys for your Linux VMs' suggests a subtle Windows-first bias. There are no explicit examples or instructions for Linux-specific secret usage (e.g., SSH key integration), nor are there Linux command-line or tooling references.
Recommendations
  • Provide explicit examples for storing and retrieving Linux SSH keys as secrets, including how to use them during Linux VM creation.
  • Include screenshots or instructions that demonstrate Linux VM scenarios, such as injecting SSH keys from Key Vault into a Linux VM.
  • Balance the order of platform references (e.g., mention Linux and Windows secrets together or alternate their order).
  • Add references to Linux tools or command-line usage (e.g., Azure CLI on Linux) for secret management.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/tutorial-create-custom-lab.md ...in/articles/devtest-labs/tutorial-create-custom-lab.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively providing a Windows Server 2019 Datacenter example when creating a VM, with no mention or example of Linux-based images. There are no Linux-specific instructions, screenshots, or references to Linux VM setup, tools, or patterns. The tutorial implicitly assumes Windows as the default, which may discourage or confuse users seeking to deploy Linux VMs in DevTest Labs.
Recommendations
  • Include Linux VM creation examples alongside Windows examples, such as selecting Ubuntu or CentOS images.
  • Add screenshots and step-by-step instructions for Linux VM setup, including differences in username/password requirements and SSH key configuration.
  • Mention Linux-specific artifacts or post-deployment configuration options.
  • Clarify that DevTest Labs supports both Windows and Linux VMs, and provide links to relevant Linux documentation.
  • Ensure that references to OS images, tools, and patterns are presented in a platform-neutral or parallel manner (e.g., 'Choose a base: Windows Server or Ubuntu').
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/tutorial-use-custom-lab.md .../main/articles/devtest-labs/tutorial-use-custom-lab.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents connection options for Windows VMs before Linux VMs, listing 'Connect via RDP' for Windows and then 'Connect via Azure CLI' or 'Connect via Native SSH' for Linux. Windows-specific tools (RDP) are mentioned by name, while Linux connection methods are grouped and less prominently described. No explicit Linux command-line examples or screenshots are provided, and the flow prioritizes Windows terminology and patterns.
Recommendations
  • Present Linux and Windows connection methods with equal prominence, possibly in parallel bullet points or tables.
  • Include example commands or screenshots for Linux connection methods (e.g., SSH command-line usage, Azure CLI steps).
  • Avoid listing Windows connection options before Linux; alternate or group them together.
  • Explicitly mention Linux tools and workflows, such as SSH clients, and provide parity in instructions and visuals.
  • Ensure that references to further documentation for both platforms are equally visible and accessible.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/connect-environment-lab-virtual-network.md ...evtest-labs/connect-environment-lab-virtual-network.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides an ARM template example that exclusively references Windows Server images and OS versions, with no mention of Linux options or examples. The parameters and variables are all tailored to Windows (e.g., 'MicrosoftWindowsServer', 'WindowsServer', and specific Windows Server versions), and there is no guidance or parity for deploying Linux-based environments.
Recommendations
  • Include Linux image options in the ARM template, such as Ubuntu, CentOS, or other popular distributions.
  • Add a parallel example or section demonstrating how to connect a Linux VM to the lab's VNet, including relevant parameters and variables.
  • Mention both Windows and Linux scenarios in the introductory and instructional text to ensure cross-platform applicability.
  • Provide guidance or links for customizing the template for Linux environments, including admin username conventions and SSH key authentication.
GitHub Create Pull Request
← Previous Page 12 of 14 Next →