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 101-125 of 334 flagged pages
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-guidance-get-started.md ...icles/devtest-labs/devtest-lab-guidance-get-started.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure DevTest Labs scenarios demonstrates a Windows bias in several ways. Windows-centric tools and patterns (such as PowerShell scripts and references to Visual Studio, Fiddler, and Active Directory domain join) are mentioned exclusively or before Linux equivalents. Automation examples and quickstart links focus on Windows VMs, and PowerShell is the only scripting language referenced for tasks like adding users and deleting VMs. There are no explicit Linux or Bash examples, and Linux tools or patterns are not discussed.
Recommendations
  • Include Linux/Bash scripting examples alongside PowerShell for common tasks (e.g., adding users, deleting VMs).
  • Add quickstart and template links for creating Linux VMs (e.g., Ubuntu, CentOS) using Bicep, ARM, and Terraform.
  • Mention Linux tools and artifacts (e.g., VS Code, Git, common Linux utilities) in artifact customization sections.
  • Provide examples of joining Linux VMs to identity solutions (e.g., Azure AD, LDAP) where relevant.
  • Ensure that references to VM images, formulas, and environments explicitly mention both Windows and Linux options.
  • Balance the order of presentation so that Linux and Windows approaches are given equal prominence.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-upload-vhd-using-azcopy.md ...es/devtest-labs/devtest-lab-upload-vhd-using-azcopy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. AzCopy is described as a Windows-only tool, and all instructions and examples are tailored for Windows environments (Command Prompt, Windows file paths, PowerShell references). There are no Linux or cross-platform alternatives or examples provided, and Linux users are not addressed. The use of PowerShell and Windows-centric screenshots further reinforces the bias.
Recommendations
  • Clarify whether AzCopy v10+ is cross-platform (it is, for modern versions) and update the note accordingly.
  • Provide Linux and macOS installation instructions for AzCopy.
  • Include example commands for Linux/macOS terminals (e.g., Bash), using appropriate syntax and file paths.
  • Mention and demonstrate how to use AzCopy on non-Windows platforms, including how to add it to the PATH and run commands.
  • Replace or supplement PowerShell-specific instructions and screenshots with Azure CLI or Bash alternatives.
  • Ensure that references to uploading VHDs via PowerShell are balanced with Azure CLI or REST API options.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-reference-architecture.md ...les/devtest-labs/devtest-lab-reference-architecture.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (Remote Desktop Gateway, RDP), linking to Windows Server documentation, and mentioning PowerShell before Azure CLI and REST APIs for automation. There are no examples or mentions of Linux remote access tools (e.g., SSH), nor any Linux-specific management or connectivity patterns. The guidance and examples assume a Windows-centric enterprise environment.
Recommendations
  • Include Linux remote access options, such as SSH bastion hosts or Azure Bastion, alongside or before RDP/Remote Desktop Gateway.
  • Provide examples using Azure CLI and Bash scripts, not just PowerShell, for automation and scripting.
  • Reference Linux domain join options (e.g., joining to Microsoft Entra Domain Services from Linux VMs) and management patterns.
  • Add links to documentation for Linux VM management and connectivity, not just Windows Server resources.
  • Ensure parity in describing security and networking setups for both Windows and Linux environments.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-troubleshoot-apply-artifacts.md ...vtest-labs/devtest-lab-troubleshoot-apply-artifacts.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias in several ways. Troubleshooting steps and examples are primarily provided for Windows environments, such as PowerShell commands and Windows file paths. Instructions for inspecting logs and running scripts focus on Windows tools (File Explorer, Command Prompt) and locations, with Linux guidance relegated to external links. Linux-specific troubleshooting is not presented inline, and Windows methods/tools are described first and in more detail.
Recommendations
  • Provide equivalent Linux examples alongside Windows instructions, such as using Bash/SSH commands to check VM status and inspect logs.
  • Include inline steps for locating and analyzing CSE log files on Linux VMs, not just a link to external documentation.
  • Offer troubleshooting guidance for common Linux scripting issues, including how to run and debug artifact installation scripts on Linux VMs.
  • Balance the use of Windows tools (File Explorer, Command Prompt) with Linux alternatives (terminal, file system paths).
  • Ensure that artifact structure examples and references include Linux artifacts, not just Windows ones.
  • When presenting PowerShell commands, also provide Azure CLI or Bash equivalents for cross-platform accessibility.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-upload-vhd-using-storage-explorer.md ...-labs/devtest-lab-upload-vhd-using-storage-explorer.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: it references PowerShell as the primary CLI method for obtaining the storage account name, includes screenshots and instructions that appear Windows-centric, and does not provide Linux-specific CLI alternatives (such as Bash or Azure CLI) for key steps. While Storage Explorer is cross-platform, the examples and workflow assume familiarity with Windows tools and patterns, and do not offer parity for Linux users.
Recommendations
  • Include instructions and examples for obtaining the storage account name using Azure CLI or Bash, which are commonly used on Linux and macOS.
  • Add screenshots and step-by-step guidance for Storage Explorer usage on Linux and macOS, highlighting any UI or workflow differences.
  • Mention and link to Linux-native tools (such as azcopy or Azure CLI) for uploading VHD files, and provide equivalent workflows.
  • Avoid referencing PowerShell as the default or only CLI method; present cross-platform alternatives first or alongside PowerShell.
  • Review and update related content links to ensure Linux parity, such as including guides for creating custom images using Azure CLI.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-use-arm-and-powershell-for-lab-resources.md ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-use-arm-and-powershell-for-lab-resources.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows Server VM examples, providing only Windows-based quickstart templates, and focusing on Azure PowerShell for automation tasks. There are no explicit Linux VM examples or references to Linux-specific workflows, and all automation examples use PowerShell rather than Bash or cross-platform scripting.
Recommendations
  • Include Linux VM deployment examples alongside Windows examples, such as a quickstart for creating a lab with an Ubuntu or other Linux VM.
  • Provide automation instructions and links for both Azure CLI (with Bash examples) and Azure PowerShell, ensuring parity in scripting guidance.
  • Reference and link to Linux-friendly scripts or templates in the GitHub repository, or add such resources if they are missing.
  • When listing automation tasks, alternate or parallelize PowerShell and Bash/CLI examples to avoid the impression that PowerShell is the default or only option.
  • Update screenshots and walkthroughs to show both Windows and Linux VM creation where appropriate.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/extend-devtest-labs-azure-functions.md ...es/devtest-labs/extend-devtest-labs-azure-functions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-centric tools and workflows. All step-by-step instructions use Visual Studio, a Windows-first IDE, and screenshots are exclusively from Windows environments. The sample code is provided in C# and PowerShell, both commonly used on Windows. The walkthrough references Windows-specific artifacts (Windows Update) and PowerShell automation, with no mention of Linux equivalents or cross-platform alternatives. There are no examples or instructions for using Linux-based development environments, editors, or deployment workflows.
Recommendations
  • Add instructions and screenshots for using cross-platform tools such as VS Code, Azure CLI, or GitHub Actions to build and deploy the sample.
  • Provide Linux shell (bash) examples for service principal creation and Azure Functions deployment.
  • Include sample code and deployment steps for Python or JavaScript Azure Functions, which are popular on Linux.
  • Reference Linux-compatible artifacts and automation patterns, such as package updates for Ubuntu or CentOS VMs.
  • Clarify that the sample can be built and deployed from non-Windows environments, and provide explicit steps for doing so.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/import-virtual-machines-from-another-lab.md ...vtest-labs/import-virtual-machines-from-another-lab.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based scripting instructions for importing VMs, referencing a .ps1 script, and omitting any Linux shell (bash) or cross-platform CLI examples. PowerShell is a Windows-centric tool, and its use is presented before the REST API method. There is no mention of Linux-native tools or guidance for users on Linux or macOS platforms.
Recommendations
  • Provide equivalent bash or shell script examples for Linux/macOS users, using Azure CLI or REST API calls.
  • Mention cross-platform tools such as Azure CLI and show how the import process can be performed using them.
  • Clarify that PowerShell Core is available cross-platform, but also offer instructions for users who prefer native Linux tools.
  • Reorder the documentation to present REST API and CLI methods before or alongside PowerShell, to avoid Windows-first bias.
  • Explicitly state platform compatibility for each method, helping users choose the best approach for their OS.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/network-isolation.md ...s/blob/main/articles/devtest-labs/network-isolation.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily by referencing a PowerShell script as the only method for converting an existing lab to network isolation, without mentioning or providing equivalent Bash, Azure CLI, or Linux-friendly alternatives. The automation section lists PowerShell before Azure CLI, and no explicit Linux or cross-platform examples are provided for scripting or automation. The documentation assumes familiarity with Windows tools and patterns, potentially making it less accessible for Linux users.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for converting labs to network isolation, alongside the PowerShell example.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide step-by-step CLI instructions for key tasks.
  • Where automation is discussed, present Azure CLI and PowerShell options together, or lead with the more cross-platform Azure CLI.
  • Add notes or examples for Linux users, such as how to run Azure CLI commands or access Azure resources from Linux VMs.
  • Review all scripting references to ensure parity between Windows and Linux tooling.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/how-to-move-labs.md ...cs/blob/main/articles/devtest-labs/how-to-move-labs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing PowerShell-centric instructions and examples, referencing Windows-specific tools and workflows (e.g., OS disk swap via PowerShell, RDP port for Windows VMs), and omitting equivalent Linux command-line or scripting examples. AzCopy usage is shown only in PowerShell context, and Windows VM patterns (RDP) are described before Linux (SSH). There are no Bash, CLI, or Linux-native instructions for key steps such as disk migration or template deployment.
Recommendations
  • Provide Bash/Azure CLI examples alongside PowerShell for disk migration and template deployment.
  • Include Linux VM-specific instructions (e.g., OS disk swap for Linux VMs) and reference relevant documentation.
  • Show AzCopy usage in Bash or Linux shell environments, not just PowerShell.
  • Present Linux and Windows VM configuration patterns together, or alternate which is shown first.
  • Explicitly mention cross-platform compatibility for all tools and scripts, and clarify any OS-specific requirements.
  • Add notes or links for Linux users where steps differ (e.g., disk swap, VM management).
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/quickstarts/create-lab-rest.md ...n/articles/devtest-labs/quickstarts/create-lab-rest.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively uses PowerShell for all command-line examples, assumes the use of the Az PowerShell module, and provides no equivalent instructions for Linux or cross-platform tools (such as Bash, Azure CLI, or curl). Windows-specific tools and patterns are mentioned first and solely, with no guidance for Linux users. This creates a strong Windows bias and may hinder accessibility for users on Linux or macOS.
Recommendations
  • Add equivalent examples using Bash and Azure CLI, which are cross-platform and commonly used on Linux and macOS.
  • Provide REST API invocation examples using curl or httpie, which are available on all platforms.
  • Include instructions for authenticating to Azure using Azure CLI (az login) and obtaining access tokens in Bash.
  • Clearly indicate that the steps can be performed on any OS and provide guidance for both Windows and Linux/macOS users.
  • Consider restructuring the documentation to present cross-platform tools first, or in parallel with PowerShell, to avoid Windows-first bias.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/personal-data-delete-export.md ...n/articles/devtest-labs/personal-data-delete-export.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page exclusively provides an Azure PowerShell example for exporting personal data, with no mention of Linux-native tools, Bash, Azure CLI, or cross-platform alternatives. The use of PowerShell and Windows-centric Azure modules (e.g., Connect-AzAccount, New-AzStorageAccount) suggests a strong Windows bias, making it less accessible for Linux or macOS users. There is no guidance or parity for users who prefer or require Linux-based workflows.
Recommendations
  • Add equivalent Azure CLI examples for exporting personal data, which are natively supported on Linux and macOS.
  • Include Bash script samples or instructions for using REST APIs directly, which are platform-agnostic.
  • Explicitly mention cross-platform options and clarify which steps/tools work on Linux, macOS, and Windows.
  • Reorganize the export section to present Azure CLI and REST API methods before or alongside PowerShell, to avoid Windows-first ordering.
  • Provide links to official Azure CLI documentation and installation guides for non-Windows platforms.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/report-usage-across-multiple-labs-subscriptions.md ...abs/report-usage-across-multiple-labs-subscriptions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments by primarily referencing PowerShell for automation and scripting tasks, mentioning Windows-centric tools (PowerShell Az.Resource module, Power BI, SQL Server) before or instead of Linux equivalents. There are no examples or explicit instructions for Linux users (e.g., Bash, CLI, or Linux-native automation), and the scripting examples and tool recommendations are Windows-first or Windows-only.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for exporting resource usage, alongside PowerShell.
  • Mention and demonstrate usage of Linux-compatible automation tools (e.g., cron jobs, shell scripts) for batch exports.
  • Include references to cross-platform visualization tools (e.g., Grafana, Kibana) in addition to Power BI.
  • Highlight Linux-friendly storage solutions and database options, not just SQL Server.
  • Ensure that all code samples and tool recommendations are presented in a platform-neutral or parallel fashion (Windows and Linux side-by-side).
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/use-command-line-start-stop-virtual-machines.md ...t-labs/use-command-line-start-stop-virtual-machines.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by providing detailed PowerShell examples and instructions first, referencing Windows-specific tools and patterns (such as REM comments and set commands), and generally prioritizing Windows environments. While Bash examples are present for Azure CLI, they are less emphasized and lack parity in explanation compared to the PowerShell section. There is no explicit Linux shell scripting example outside of Azure CLI, and the documentation assumes familiarity with Windows conventions.
Recommendations
  • Ensure Bash/Linux examples are presented with equal detail and prominence as PowerShell/Windows examples.
  • Avoid using Windows-specific syntax (e.g., REM, set) without providing equivalent Linux/Bash alternatives.
  • Include explicit instructions for running scripts on Linux/macOS environments, not just Windows.
  • Consider starting with cross-platform or Linux-first examples to balance the order of presentation.
  • Clarify that both PowerShell and Bash can be used in Cloud Shell, and provide guidance for local Linux setups.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/samples-cli.md ...re-docs/blob/main/articles/devtest-labs/samples-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a Windows bias by focusing on Windows VM creation, labeling code samples as 'powershell' even though they are bash scripts, and omitting explicit Linux VM examples. The script descriptions and examples prioritize Windows scenarios, and there is no parity shown for Linux VM creation or management.
Recommendations
  • Include explicit examples for creating and managing Linux VMs alongside Windows VM examples.
  • Correct code block language labels to 'bash' or 'azurecli' instead of 'powershell' for scripts written in bash.
  • Add notes or sections that clarify how scripts can be adapted for Linux environments, including differences in authentication (e.g., SSH vs. RDP).
  • Ensure that both Windows and Linux use cases are presented equally in tables and script samples.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/deploy-nested-template-environments.md ...es/devtest-labs/deploy-nested-template-environments.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-centric tools (Visual Studio, Azure PowerShell) and listing PowerShell before Azure CLI. There are no Linux-specific examples or mentions of Linux-friendly tooling or workflows. The Visual Studio reference further reinforces a Windows-first approach, and no alternative editors or deployment methods are suggested for Linux users.
Recommendations
  • Provide explicit Linux examples, such as using VS Code or other cross-platform editors for ARM template development.
  • List Azure CLI commands before or alongside PowerShell commands, emphasizing CLI as a cross-platform tool.
  • Include instructions for generating SaS tokens and deploying templates using Linux shell commands (bash) and scripting.
  • Mention Git integration and workflows using Linux tools (e.g., git, curl, jq) for template management.
  • Reference cross-platform deployment options and editors, not just Visual Studio.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-environment-from-arm.md ...evtest-labs/devtest-lab-create-environment-from-arm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed automation instructions and sample scripts exclusively using Azure PowerShell, a tool most commonly used on Windows. While the Azure CLI is briefly mentioned as an alternative, no CLI examples or scripts are provided. The step-by-step automation workflow is Windows-centric, and Linux users are left without parity in guidance or examples.
Recommendations
  • Add equivalent Azure CLI automation instructions and sample scripts for environment deployment, including full command examples.
  • Present both PowerShell and CLI options side-by-side in the 'Automate environment creation' section, or clearly indicate cross-platform alternatives.
  • Include notes or links for Linux/macOS users on how to install and use Azure CLI for these tasks.
  • Ensure screenshots and UI instructions do not assume Windows-only environments (e.g., avoid references to Windows-specific file paths or tools).
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-concepts.md ...lob/main/articles/devtest-labs/devtest-lab-concepts.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows virtual machines before Linux equivalents, omitting explicit Linux VM documentation links, and listing Windows-specific tools (e.g., Visual Studio, Fiddler) as artifact examples without mentioning Linux alternatives. There are no PowerShell-heavy examples, but the overall framing and examples prioritize Windows over Linux.
Recommendations
  • Include references and links to both Windows and Linux VM documentation (e.g., add a link to 'Linux virtual machines in Azure').
  • Provide artifact examples relevant to Linux environments (e.g., installation of Linux tools, agents, or editors like VS Code, Git, or Apache).
  • Ensure that examples and instructions are platform-neutral or include both Windows and Linux variants where applicable.
  • Mention Linux base images and their use cases alongside Windows images in the 'Base images' section.
  • Add explicit statements that DevTest Labs supports both Windows and Linux VMs, and highlight any differences or considerations for each platform.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/network-isolation.md ...s/blob/main/articles/devtest-labs/network-isolation.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing a PowerShell script as the only method for converting an existing lab to network isolation, without mentioning or providing equivalent Bash, Azure CLI, or Linux-native alternatives. The automation section mentions PowerShell and Azure CLI, but only links to general Azure Storage documentation, not to specific Linux/Bash examples. No explicit Linux or cross-platform instructions are provided, and the PowerShell solution is presented first and exclusively for a key workflow.
Recommendations
  • Provide Azure CLI and Bash script equivalents for the PowerShell script (Convert-DtlLabToIsolatedNetwork.ps1), or clarify if none exist.
  • Include explicit Linux/macOS instructions and examples for all automation steps, especially for converting existing labs to isolated network mode.
  • When mentioning automation, give equal prominence to Azure CLI and Bash examples alongside PowerShell, and link to relevant cross-platform documentation.
  • Add a note clarifying platform compatibility for scripts and tools, and recommend cross-platform approaches where possible.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/how-to-move-labs.md ...cs/blob/main/articles/devtest-labs/how-to-move-labs.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 Windows bias in several ways: PowerShell is used exclusively for command-line examples, especially in disk migration steps; Windows tools and patterns (e.g., PowerShell, Windows VM RDP configuration) are mentioned first or exclusively; AzCopy usage is shown only in the context of PowerShell; and there are no equivalent Linux CLI/bash examples or instructions for Linux users. Even when Linux is mentioned (e.g., SSH port for Linux VM), the configuration is secondary to the Windows example.
Recommendations
  • Provide equivalent bash/CLI examples for all PowerShell commands, especially for disk migration and AzCopy usage.
  • Include instructions for using AzCopy from Linux/macOS terminals, not just PowerShell or Azure Cloud Shell.
  • When showing VM configuration examples, present Linux and Windows patterns side-by-side, or alternate which is shown first.
  • Explicitly mention that all steps can be performed from Linux/macOS environments and link to relevant cross-platform documentation.
  • Where Windows-specific tools or patterns are referenced, add Linux alternatives (e.g., Azure CLI, bash scripts) and clarify platform compatibility.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/best-practices-distributive-collaborative-development-environment.md ...ces-distributive-collaborative-development-environment.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by referencing Azure PowerShell and PowerShell scripts as primary tooling for resource management and automation. There is no mention of Linux shell equivalents (such as Bash or CLI), nor are Linux-specific scripting or automation patterns discussed. Examples and references are focused on Windows-centric tools, with no parity for Linux users.
Recommendations
  • Include examples using Azure CLI and Bash scripts alongside PowerShell examples to ensure Linux users have clear guidance.
  • Mention cross-platform tools and scripting options, highlighting how both Windows and Linux users can automate and manage resources.
  • Add references to Linux-compatible automation patterns (e.g., shell scripts, Ansible) where PowerShell is mentioned.
  • Clarify that Azure DevTest Labs supports both Windows and Linux environments, and provide best practices for each.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/add-artifact-repository.md .../main/articles/devtest-labs/add-artifact-repository.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 bias toward Windows environments and tooling. The automation and scripting sections focus almost exclusively on Azure PowerShell, with detailed PowerShell scripts and command references. ARM template deployment instructions explicitly recommend PowerShell first, and only mention Azure CLI as a secondary option. There are no examples using Bash, Linux shell, or cross-platform scripting approaches. The documentation references Windows-centric tools and patterns, such as PowerShell cmdlets and concepts like 'Set-AzContext', without providing Linux or macOS equivalents or guidance for those platforms.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands, including full Bash scripts for Linux/macOS users.
  • Include instructions and sample scripts for deploying ARM templates from Linux/macOS environments, not just PowerShell.
  • Add notes or sections highlighting cross-platform compatibility and any differences in workflow for Linux/macOS users.
  • Reference and link to Linux-specific tools or documentation where appropriate, such as using curl, jq, or native Git commands.
  • Ensure that all automation steps (such as authentication, resource creation, and deployment) are demonstrated in both PowerShell and Bash/CLI formats.
  • Review screenshots and UI instructions to confirm they are not Windows-specific, or provide Linux/macOS alternatives if needed.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/automate-add-lab-user.md ...ob/main/articles/devtest-labs/automate-add-lab-user.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 strong Windows bias. PowerShell is used extensively for examples, and Windows-centric tools and cmdlets (e.g., Get-AzRoleDefinition, Get-AzADUser, New-AzResourceGroupDeployment) are referenced exclusively or before any cross-platform alternatives. There are no explicit Linux shell/bash examples, and the CLI section is brief and lacks parity with the PowerShell coverage. The guidance for obtaining GUIDs and object IDs relies on Windows/PowerShell tools, with no mention of Linux-native or cross-platform alternatives.
Recommendations
  • Add bash and Azure CLI examples for all key operations, including obtaining GUIDs and object IDs.
  • Reference cross-platform tools (e.g., uuidgen for GUID generation, az ad user show for object IDs) alongside PowerShell cmdlets.
  • Ensure Azure CLI examples are as detailed and comprehensive as PowerShell examples.
  • Reorder sections so that cross-platform (CLI, bash) examples are presented before or alongside PowerShell examples.
  • Explicitly mention that all operations can be performed on Linux/macOS as well as Windows, and provide relevant commands.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-add-vm.md .../blob/main/articles/devtest-labs/devtest-lab-add-vm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 primarily using a Windows 11 Pro image as the example for VM creation, mentioning PowerShell as the first automation option, and providing a PowerShell-only script for copying VMs into a lab. There are no explicit Linux VM examples, nor are Linux-specific tools or patterns highlighted. The documentation does not provide parity in examples or instructions for Linux users.
Recommendations
  • Include explicit Linux VM creation examples, such as using Ubuntu or CentOS images, alongside or before Windows examples.
  • Provide Linux shell (bash) equivalents for automation tasks, such as copying VMs into a lab, in addition to PowerShell scripts.
  • Mention Linux-specific tools and patterns (e.g., SSH, cloud-init) when discussing VM configuration and access.
  • Ensure that references to automation options (PowerShell, Azure CLI, ARM templates) are presented in a neutral order or with equal emphasis.
  • Add screenshots and walkthroughs using Linux VM images to demonstrate parity in the portal experience.
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
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its exclusive use of Windows-centric tools and terminology. The instructions for creating Logic Apps reference a 'Windows Plan' and default App Service Plan, with no mention of Linux hosting options. All portal screenshots and workflow steps are based on the Azure portal UI, which is platform-agnostic but the only explicit OS reference is to Windows. There are no examples or guidance for Linux-based alternatives, such as using Linux App Service Plans, Linux email clients, or command-line automation via Bash or CLI. The documentation does not provide parity for Linux users or acknowledge cross-platform considerations.
Recommendations
  • Explicitly mention that Logic Apps can be hosted on Linux App Service Plans and provide steps for both Windows and Linux hosting options.
  • Include examples of integrating with non-Windows email clients (e.g., Thunderbird, Evolution) or generic SMTP connectors.
  • Add command-line automation examples using Azure CLI and Bash scripts, alongside portal-based instructions.
  • Clarify that the autoshutdown and notification features are OS-agnostic and work for both Windows and Linux VMs.
  • Where possible, provide screenshots or instructions that demonstrate Linux VM management in the Azure portal.
  • Avoid using 'Windows Plan' as the default without noting Linux alternatives.
GitHub Create Pull Request
← Previous Page 5 of 14 Next →