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 126-150 of 334 flagged pages
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-add-tag.md ...blob/main/articles/devtest-labs/devtest-lab-add-tag.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 references managing tags using PowerShell or Azure CLI, but mentions PowerShell before Azure CLI, which can suggest a Windows-first or PowerShell-heavy bias. There are no explicit Linux or cross-platform command-line examples, nor is there mention of Linux-specific tools or workflows. The UI instructions are platform-agnostic, but the lack of Linux parity in scripting examples or tool references is notable.
Recommendations
  • When mentioning scripting or automation, list Azure CLI before or alongside PowerShell, as Azure CLI is cross-platform and widely used on Linux.
  • Provide explicit Azure CLI examples for managing tags, ensuring Linux users have clear, native instructions.
  • Include a note or section highlighting that all tag management operations can be performed from Linux, macOS, or Windows using Azure CLI.
  • Avoid implying PowerShell is the primary or only automation tool; balance references to both PowerShell and Azure CLI.
  • If possible, add screenshots or terminal snippets from Linux environments to reinforce cross-platform support.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/configure-lab-remote-desktop-gateway.md ...s/devtest-labs/configure-lab-remote-desktop-gateway.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias throughout. All examples and instructions are centered around Windows technologies, such as RDP, PowerShell scripts, and Windows-specific tools (IIS, RDGatewayFedAuth.msi, System Center VMM). There are no Linux equivalents or alternatives mentioned for remote access, certificate creation, or gateway configuration. The documentation assumes the use of Windows-based RDP clients and infrastructure, with no guidance for Linux users or administrators.
Recommendations
  • Provide examples for Linux-based remote desktop access (e.g., using xrdp, Remmina, rdesktop, or FreeRDP).
  • Include Linux shell commands for certificate creation and management (e.g., using OpenSSL).
  • Document how to configure a Linux-based gateway (such as using Apache/Nginx reverse proxy or xrdp gateway).
  • Mention cross-platform RDP clients and note any token authentication compatibility.
  • Add ARM template and automation examples using Bash or Azure CLI, not just PowerShell.
  • Clarify which steps are Windows-specific and offer Linux alternatives where possible.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-delete-lab-vm.md ...ain/articles/devtest-labs/devtest-lab-delete-lab-vm.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides detailed instructions for deleting lab VMs and labs primarily through the Azure portal UI and a PowerShell script. The only automation example is given in PowerShell, which is a Windows-centric tool, with no equivalent example for Linux users (e.g., Bash, Azure CLI). There is no mention of Linux-native tools or cross-platform alternatives, and the scripting section assumes familiarity with PowerShell.
Recommendations
  • Provide equivalent automation examples using Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, or clarify if the script requires Windows PowerShell.
  • Add Bash script examples for common tasks, or reference Azure CLI documentation for deleting VMs and labs.
  • Ensure that scripting and automation instructions are not Windows-centric by including Linux and macOS alternatives wherever possible.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/add-artifact-vm.md ...ocs/blob/main/articles/devtest-labs/add-artifact-vm.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 only Azure PowerShell examples for scripting and automation, with no equivalent Bash, Azure CLI, or Linux-native instructions. The prerequisites and example scripts focus exclusively on PowerShell, and the guidance for using the Azure portal does not mention platform-specific considerations or alternatives for Linux users. There are no Linux or cross-platform command-line examples, and Windows/PowerShell tooling is presented as the default or only option.
Recommendations
  • Add Azure CLI examples for artifact management, including step-by-step instructions and sample scripts.
  • Include Bash shell commands or Linux-native workflows for adding artifacts to VMs.
  • Explicitly mention platform parity and clarify which steps or tools are cross-platform.
  • Provide guidance for Linux users on prerequisites, such as using Azure CLI in Cloud Shell (Bash) or installing CLI tools on Linux.
  • Ensure that scripting and automation examples are available for both Windows (PowerShell) and Linux (Bash/Azure CLI).
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-create-template.md ...n/articles/devtest-labs/devtest-lab-create-template.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 Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned as an alternative method for creating custom images, and uploading VHD files via PowerShell is listed as one of the main options. Windows tools (sysprep) are referenced before their Linux equivalents (deprovision), and PowerShell is highlighted in both the prerequisites and related content, while Linux CLI tools (such as Bash, Azure CLI) are not mentioned or exemplified.
Recommendations
  • Add explicit examples and links for using Azure CLI and Bash scripts to create custom images and upload VHD files, alongside PowerShell.
  • Ensure Linux tools and patterns (e.g., waagent deprovision, az CLI) are mentioned with equal prominence and order as Windows tools (sysprep, PowerShell).
  • Provide step-by-step instructions for Linux users, including screenshots from Linux environments where relevant.
  • Include troubleshooting tips or notes specific to Linux VHD creation and upload processes.
  • Review related content to ensure Linux-focused articles or external resources are included.
GitHub Create Pull Request
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-08 00:53
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 consistently referencing Windows-centric tools and workflows. Examples include frequent mention of PowerShell scripts for automation, links to 'create-lab-windows-vm' resources, and references to Windows-specific tools like Visual Studio and Active Directory domain-join artifacts. Linux equivalents (such as Bash scripting or Linux VM creation) are not mentioned or are relegated to generic statements, and there are no explicit Linux-focused examples or instructions.
Recommendations
  • Add explicit Linux VM creation examples and links (e.g., 'create-lab-linux-vm-bicep.md', 'create-lab-linux-vm-template.md').
  • Include Bash or CLI-based automation examples alongside PowerShell scripts.
  • Mention Linux tools and artifacts (e.g., apt, yum, SSH, Linux dev tools) in artifact customization sections.
  • Provide parity in documentation for joining Linux VMs to identity providers (e.g., Azure AD, LDAP) where applicable.
  • Ensure that instructions and quickstarts are available for both Windows and Linux environments, and alternate the order of presentation to avoid 'windows_first' bias.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-dev-ops.md ...blob/main/articles/devtest-labs/devtest-lab-dev-ops.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 referencing PowerShell scripts and Azure CLI as primary integration methods, without mentioning Bash or Linux shell scripting. There are no explicit Linux examples, and Windows-centric tools/patterns (PowerShell) are mentioned before or instead of Linux equivalents. The absence of Linux-specific instructions or examples may hinder parity for Linux users.
Recommendations
  • Include explicit examples using Bash or Linux shell scripting for integrating DevTest Labs with CI/CD pipelines.
  • Mention Linux-based tools and workflows (e.g., Bash, cron, systemd) alongside PowerShell and Azure CLI.
  • Provide sample code snippets for both Windows (PowerShell) and Linux (Bash) environments when discussing automation or scripting.
  • Clarify that Azure CLI and REST API can be used cross-platform, and provide usage examples on Linux.
  • Add guidance for integrating DevTest Labs with popular Linux-based CI/CD tools (e.g., GitLab CI, Travis CI) in addition to Azure Pipelines.
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-08 00:53
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 Windows bias by exclusively referencing Windows-centric tools and patterns, such as Remote Desktop Gateway and RDP for remote access, and by mentioning PowerShell as a primary automation tool before Azure CLI or REST APIs. There are no examples or mentions of Linux alternatives for remote access (e.g., SSH), nor are Linux-specific automation tools or patterns discussed. The documentation assumes a Windows-centric enterprise environment, omitting guidance for Linux-based workflows.
Recommendations
  • Include Linux remote access options, such as SSH bastion hosts or Azure Bastion, alongside or before Windows RDP/Remote Desktop Gateway.
  • Provide Linux-based automation examples (e.g., Bash scripts using Azure CLI) in addition to PowerShell.
  • Mention Linux domain join scenarios (e.g., using LDAP or SSSD) where applicable.
  • Clarify that DevTest Labs supports both Windows and Linux VMs, and provide parity in management and connectivity guidance.
  • Reference cross-platform tools and patterns (e.g., Azure CLI, Terraform) equally or before platform-specific ones.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-artifact-author.md ...n/articles/devtest-labs/devtest-lab-artifact-author.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 Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based examples for artifact creation and usage, referencing Windows-specific tools (e.g., Chocolatey), and omitting equivalent Linux shell script examples. The sample artifact and folder structure are based on Windows artifacts, and the command construction examples exclusively use PowerShell. Although the documentation mentions Linux as a supported target OS, there are no Linux-specific examples, commands, or references to Linux tools or scripting patterns.
Recommendations
  • Include parallel Linux examples using Bash scripts and Linux package managers (e.g., apt, yum) in the artifact definition and command construction sections.
  • Show how to create and structure a Linux artifact folder, including sample artifactfile.json and artifact.sh files.
  • Provide sample runCommand values for Linux, demonstrating usage of bash/sh and relevant Linux commands.
  • Reference Linux tools and scripting conventions alongside Windows/PowerShell examples, ensuring equal visibility.
  • Explicitly mention differences or considerations when targeting Linux VMs, such as file permissions, shell environments, and script execution.
  • Add screenshots or illustrations of Linux artifact folders and scripts to match the Windows examples.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. AzCopy is described as a Windows-only tool, and all instructions and examples assume a Windows environment (e.g., Command Prompt, Windows file paths, PowerShell references). There are no Linux or macOS equivalents or instructions, and PowerShell is mentioned as the primary automation method. No alternative cross-platform tools or methods are suggested.
Recommendations
  • Update the documentation to clarify the current cross-platform status of AzCopy (AzCopy v10+ is cross-platform and available on Linux/macOS).
  • Provide Linux and macOS installation instructions for AzCopy, including package manager commands (e.g., apt, yum, Homebrew).
  • Add example commands for uploading VHD files using AzCopy on Linux/macOS terminals (bash/zsh), including path conventions.
  • Include automation examples using Bash scripts or Azure CLI, not just PowerShell.
  • Remove or update statements that incorrectly claim AzCopy is Windows-only.
  • Ensure screenshots and step-by-step instructions are not exclusively Windows-centric.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/create-environment-service-fabric-cluster.md ...test-labs/create-environment-service-fabric-cluster.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by defaulting to Windows as the operating system for the Service Fabric cluster, providing certificate creation instructions exclusively via a PowerShell script (.ps1), and referencing Windows tools (PowerShell, Notepad) without Linux equivalents. There are no Linux-specific instructions or examples for certificate creation or cluster management, and the documentation does not mention or provide parity for Linux command-line tools or workflows.
Recommendations
  • Provide explicit instructions and examples for Linux users, including how to create the required certificate using OpenSSL or other common Linux tools.
  • Mention both Windows and Linux options when describing OS selection, and avoid defaulting to Windows without explanation.
  • Include Linux shell (bash) command examples alongside PowerShell scripts, or provide cross-platform alternatives.
  • Reference Linux text editors (e.g., nano, vim) or platform-agnostic ways to view output files, instead of only Notepad.
  • Clarify any differences or limitations when deploying Service Fabric clusters on Linux versus Windows, and ensure all steps are covered for both platforms.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-add-devtest-user.md .../articles/devtest-labs/devtest-lab-add-devtest-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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell examples for scripting, referencing Microsoft accounts (with links to Windows Server documentation), and omitting any Linux-specific command-line alternatives (such as Azure CLI or Bash). The PowerShell instructions are detailed and prominent, while no equivalent Linux/Bash/CLI examples are given. Additionally, the prerequisites and instructions focus on PowerShell and Microsoft-centric identity management, reinforcing a Windows-first approach.
Recommendations
  • Add Azure CLI (az) examples for all scripting tasks, including user and role assignment, to provide parity for Linux/macOS users.
  • Reference Microsoft account documentation that is platform-neutral, or clarify that non-Windows users can use Microsoft accounts.
  • Explicitly mention that Azure Cloud Shell supports Bash as well as PowerShell, and provide Bash/CLI instructions.
  • Include notes or sections for Linux/macOS users, highlighting any differences or additional steps required.
  • Ensure screenshots and UI instructions are not Windows-centric, and clarify that the Azure portal is cross-platform.
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-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 referencing PowerShell as the primary CLI method for obtaining the storage account name, including screenshots and links for PowerShell usage, while omitting equivalent Linux shell (e.g., Bash, Azure CLI) instructions. The workflow assumes familiarity with Windows-centric tools and patterns, and does not provide parity for Linux users who may prefer command-line or non-PowerShell approaches.
Recommendations
  • Add instructions and examples for obtaining the storage account name using Azure CLI (az) on Linux/macOS.
  • Include screenshots or terminal output for Linux/macOS workflows where appropriate.
  • Reference cross-platform command-line alternatives alongside PowerShell, and avoid presenting Windows tools first or exclusively.
  • Explicitly state that Storage Explorer is available on Linux/macOS and provide links to installation guides for those platforms.
  • Ensure related content includes links to Linux/macOS command-line documentation (e.g., Azure CLI guides for VHD upload and management).
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell is the only CLI example provided for checking artifact status, and all troubleshooting steps for inspecting logs and running scripts on the VM are described using Windows tools (File Explorer, Command Prompt, Windows file paths). Linux equivalents are either missing or referenced only via external links, and Windows-specific artifacts are highlighted in examples. The troubleshooting flow and examples consistently prioritize Windows, with Linux guidance relegated to brief mentions or links.
Recommendations
  • Provide equivalent Azure CLI or Bash examples alongside PowerShell commands for checking artifact status.
  • Include step-by-step instructions for inspecting CSE logs and troubleshooting on Linux VMs, with Linux file paths and commands (e.g., using SSH, cat, less, tail).
  • Add Linux-specific artifact examples and troubleshooting scenarios, not just links to external documentation.
  • Balance references to Windows and Linux in artifact structure and script troubleshooting sections, including examples for both platforms.
  • Where screenshots are used, alternate between Windows and Linux environments, or provide both where relevant.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/resource-group-control.md ...b/main/articles/devtest-labs/resource-group-control.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 provides a detailed PowerShell example for scripting resource group assignment, but does not offer equivalent examples for Linux shells (e.g., Bash) or cross-platform CLI usage. The scripting section is Windows/Powershell-centric, and there is no mention of Linux-specific tools or workflows. The PowerShell example appears before any mention of generic ARM template or REST API usage, reinforcing a Windows-first approach.
Recommendations
  • Add a Bash shell example using Azure CLI for Linux/macOS users.
  • Explicitly mention that the Azure CLI commands are cross-platform and can be used in Bash, PowerShell, or other shells.
  • Provide guidance or links for using the REST API with curl or other Linux-native tools.
  • Ensure that scripting examples are presented in a way that is platform-neutral, or provide both Windows (PowerShell) and Linux (Bash) variants.
  • Consider reordering sections so that platform-neutral methods (ARM template, API) are presented before platform-specific scripting.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a Windows-first bias by providing quickstart and example templates specifically for Windows Server VMs, with no equivalent Linux VM example or explicit mention. Automation and scripting sections heavily emphasize Azure PowerShell, with multiple links and tasks described only in PowerShell, while Azure CLI is mentioned but not equally detailed. There are no Linux-specific instructions, examples, or references to Linux tools or shell environments.
Recommendations
  • Add a quickstart example for creating a DevTest Labs lab with a Linux VM (e.g., Ubuntu or CentOS), and reference it alongside the Windows example.
  • Ensure that all PowerShell-based automation tasks (such as creating custom images, uploading VHDs, adding users, and creating roles) have equivalent Azure CLI examples, and link to those instructions.
  • Explicitly mention that ARM templates can be used to deploy both Windows and Linux VMs, and provide sample templates or links for both.
  • Include screenshots or walkthroughs that show Linux VM creation and management in DevTest Labs.
  • Balance references to PowerShell and CLI throughout the documentation, ensuring that Linux users are equally supported.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools and workflows (Visual Studio, Windows Update artifact), providing examples and screenshots only for Windows environments, and omitting Linux equivalents or alternatives. PowerShell is mentioned as a supported implementation, but there are no Linux shell or cross-platform examples. The walkthrough assumes use of Visual Studio and Windows-centric artifacts, with no mention of Linux development tools or update artifacts.
Recommendations
  • Add equivalent Linux examples, such as using VS Code or CLI-based workflows for building and deploying Azure Functions.
  • Include instructions and screenshots for deploying from Linux or macOS environments.
  • Mention and provide examples for Linux VM update artifacts (e.g., apt or yum updates) alongside the Windows Update artifact.
  • Highlight cross-platform tools (e.g., Azure CLI, VS Code) before or alongside Windows-specific tools like Visual Studio.
  • Provide parity in sample code and walkthroughs for both C# and PowerShell, as well as Python or Bash for Linux users.
  • Explicitly state support for Linux VMs and provide guidance for extending DevTest Labs with Linux-focused scenarios.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-grant-user-permissions-to-specific-lab-policies.md ...st-lab-grant-user-permissions-to-specific-lab-policies.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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell and Azure PowerShell cmdlets for all examples and instructions, with no mention of Linux-native tools, Bash, or cross-platform alternatives. The setup instructions and code samples assume a Windows environment, and there is no guidance for users on Linux or macOS systems. This creates a strong Windows bias and may hinder accessibility for non-Windows users.
Recommendations
  • Provide equivalent examples using Azure CLI, which is cross-platform and works natively on Linux and macOS.
  • Include instructions for installing and using Azure CLI on Linux and macOS.
  • Add Bash script examples for common tasks, such as role assignment and querying users.
  • Explicitly state that Azure PowerShell can be used on Linux and macOS via PowerShell Core, and provide installation instructions for those platforms.
  • Where possible, mention platform-agnostic approaches first, or present both Windows and Linux/macOS options side by side.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/troubleshoot-vm-deployment-failures.md ...es/devtest-labs/troubleshoot-vm-deployment-failures.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 referencing PowerShell as the primary method for deploying VMs with ARM templates and not providing equivalent Linux (e.g., Bash, Azure CLI) examples. Windows tooling and patterns are mentioned first or exclusively, with no mention of Linux shell commands or cross-platform alternatives.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell scripts for ARM template deployments.
  • Explicitly mention that deployment steps can be performed on Linux, macOS, and Windows, and provide platform-agnostic guidance.
  • Reference cross-platform tools (e.g., Azure CLI, Terraform) where appropriate, not just Windows-centric tools.
  • Ensure troubleshooting steps and error resolution guidance are not limited to Windows environments.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-vmcli.md ...s/blob/main/articles/devtest-labs/devtest-lab-vmcli.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by presenting Windows VM creation as the first example, referencing Windows-specific images and tools (e.g., Remote Desktop), and giving PowerShell command variants before Bash. Linux examples are present but generally follow Windows ones, and Linux-specific guidance is less emphasized.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which comes first to avoid implicit prioritization.
  • Include more Linux-specific VM creation examples, such as using different Linux distributions and authentication methods.
  • Provide equal detail for Linux connection methods (e.g., SSH) as for Windows (e.g., RDP), including troubleshooting tips.
  • Ensure artifact examples include both Windows and Linux artifacts, not just one or the other.
  • Clarify command differences for Bash and PowerShell in a neutral, parallel format, and avoid labeling one as primary.
  • Add links to Linux documentation and tools where Windows equivalents are referenced.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only Azure PowerShell examples for exporting personal data, with no mention of Linux-native tools, Bash, or cross-platform alternatives. The instructions and sample code are heavily focused on PowerShell, which is traditionally associated with Windows environments. There is no guidance for users on Linux or macOS, nor are Azure CLI or REST API methods referenced.
Recommendations
  • Add equivalent Azure CLI examples for exporting personal data, which work natively on Linux and macOS.
  • Include Bash shell script samples alongside PowerShell to demonstrate cross-platform usage.
  • Reference REST API methods for data export, allowing users to automate tasks regardless of OS.
  • Explicitly state cross-platform options and clarify which tools are supported on Windows, Linux, and macOS.
  • Reorder or parallelize examples so that Linux/macOS methods are presented alongside or before Windows/PowerShell instructions.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. PowerShell (a Windows-centric tool) is presented first and in detail, with extensive scripting examples. Azure CLI examples are provided for both Bash (Linux) and Windows environments, but Windows syntax is listed alongside Bash, and some instructions (like variable setting) default to Windows batch syntax before Bash. There is no explicit Linux shell scripting example beyond Bash variable assignment, and the overall structure and examples favor Windows tools and patterns.
Recommendations
  • Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI (cross-platform) first to avoid Windows-first bias.
  • Expand Bash/Linux examples to include more idiomatic shell scripting, such as using shell functions or scripts, rather than only variable assignment.
  • Provide explicit Linux shell script examples (e.g., .sh files) for starting/stopping VMs, not just Bash commands.
  • Clarify that Azure CLI works natively on Linux/macOS and provide installation instructions or links for those platforms.
  • Reduce reliance on Windows batch syntax (e.g., 'set' commands) and emphasize Bash/Linux equivalents.
  • Include troubleshooting or notes relevant to Linux environments, such as permissions or shell differences.
GitHub Create Pull Request
Devtest Labs https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/start-machines-use-automation-runbooks.md ...devtest-labs/start-machines-use-automation-runbooks.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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell scripts and Azure Automation runbooks, which are Windows-centric tools. All code examples are in PowerShell, with no mention of Bash, Azure CLI, or Linux-native automation options. The workflow and instructions assume familiarity with Windows patterns and tools, and do not provide Linux alternatives or parity.
Recommendations
  • Provide equivalent examples using Bash scripts and Azure CLI, which are more common in Linux environments.
  • Mention and document how to use Azure Automation with non-PowerShell runbooks, such as Python or Bash.
  • Include Linux-first instructions or at least present Linux options alongside Windows/PowerShell options.
  • Reference Linux-native scheduling tools (e.g., cron) for running scripts, and show how to integrate with Azure.
  • Clarify that Azure Automation supports multiple runbook types and link to documentation for non-Windows users.
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-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 consistently presenting sample scripts as 'powershell' code blocks, even though the scripts are described as bash scripts for Azure CLI. The primary VM creation example is for a Windows VM, with no mention of Linux VM creation or Linux-specific configuration. There are no explicit Linux examples, and the use of 'powershell' code blocks may confuse Linux users.
Recommendations
  • Ensure code blocks use the correct language identifier (e.g., 'bash' or 'azurecli') rather than 'powershell' for bash scripts.
  • Include examples for creating and managing Linux VMs, with notes on differences in authentication and configuration.
  • Explicitly mention Linux compatibility in the prerequisites and throughout the documentation.
  • Provide parity in examples and instructions for both Windows and Linux VM scenarios.
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-08 00:53
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 by primarily referencing PowerShell for automation and scripting examples, mentioning PowerShell before other languages (such as Python), and omitting explicit Linux or Bash examples for exporting and managing Azure DevTest Labs usage data. Windows-centric tools like Power BI and SQL Server are highlighted, while Linux-native alternatives and workflows are not discussed.
Recommendations
  • Add Bash and Azure CLI examples for exporting resource usage, alongside PowerShell.
  • Provide Python sample scripts for automation tasks, especially in Azure Functions and Automation Runbooks.
  • Mention Linux-compatible visualization tools (e.g., Grafana) and database solutions (e.g., PostgreSQL, MySQL) as alternatives to Power BI and SQL Server.
  • Clarify cross-platform support for Azure Automation and Azure Functions, including how to run scripts on Linux hosts.
  • Ensure that examples and tool recommendations are presented in a platform-neutral order, or explicitly highlight both Windows and Linux options.
GitHub Create Pull Request
← Previous Page 6 of 14 Next →