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 226-250 of 334 flagged pages
Devtest Labs Grant user permissions to specific lab policies ...st-lab-grant-user-permissions-to-specific-lab-policies.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exclusively uses Azure PowerShell cmdlets and scripts for all examples and instructions, with no mention of Linux/macOS alternatives such as Azure CLI or Bash scripting. The installation instructions and code samples are PowerShell-centric, which is a Windows-native tool, and there is no guidance for users on non-Windows platforms. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
  • Add equivalent Azure CLI examples for all tasks (listing operations, creating custom roles, assigning roles).
  • Include installation instructions for Azure CLI and/or PowerShell on Linux/macOS.
  • Clearly indicate that PowerShell is cross-platform, but also provide Bash/Azure CLI alternatives for users who prefer them.
  • Present examples for both Windows and Linux/macOS users side-by-side or in separate sections.
  • Mention that Azure PowerShell can be installed on Linux/macOS, but highlight Azure CLI as a native alternative.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by using Windows 11 Pro as the example OS for VM creation and referencing Windows-specific screenshots and terminology (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.
  • Mention any Linux-specific requirements, limitations, or supported distributions for hibernation.
  • Provide examples that alternate between Windows and Linux, or show both in parallel.
  • Clarify whether the hibernation feature works identically for Linux VMs and highlight any differences.
GitHub Create Pull Request
Devtest Labs Azure DevTest Labs scenarios ...icles/devtest-labs/devtest-lab-guidance-get-started.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is frequently referenced as the primary automation tool, with no mention of Bash, Azure CLI, or Linux/macOS scripting alternatives. Example links and quickstarts for creating labs and VMs often specify Windows VM scenarios, and Windows-centric tools (e.g., Visual Studio, Fiddler, Active Directory domain join) are highlighted as artifacts. Linux equivalents and examples are missing or not given equal prominence.
Recommendations
  • Add Azure CLI and Bash script examples alongside PowerShell for lab and VM management.
  • Include quickstart links and templates for creating Linux VMs, not just Windows VMs.
  • Highlight Linux/macOS-compatible tools and artifacts (e.g., VS Code, open source utilities) in artifact examples.
  • Mention Linux domain join or integration options where Active Directory is discussed.
  • Ensure examples and instructions are presented in a platform-neutral order, or alternate which platform is shown first.
GitHub Create Pull Request
Devtest Labs Move DevTest Labs to another region ...cs/blob/main/articles/devtest-labs/how-to-move-labs.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias, particularly in the section on swapping OS disks, where only PowerShell commands are provided and Windows-centric tools and references (e.g., PowerShell, Windows OS disk swap article) are used. There are no CLI or Bash/Linux/macOS examples for these critical steps, which may create friction for non-Windows users.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples for disk operations (e.g., creating disks, granting SAS, swapping OS disks) alongside PowerShell.
  • Reference both Windows and Linux documentation for OS disk swap procedures.
  • Clarify that AzCopy is cross-platform and provide sample commands for Linux/macOS shells.
  • Explicitly state when steps are platform-agnostic or provide links to platform-specific guides.
  • Ensure screenshots and instructions do not assume a Windows environment.
GitHub Create Pull Request
Devtest Labs Deploy Azure DevTest Labs (Enterprise Reference Architecture) ...les/devtest-labs/devtest-lab-reference-architecture.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-specific tools (Remote Desktop Gateway) for remote access and links to Windows Server documentation. There are no explicit Linux/macOS alternatives or examples for remote access, and Windows-centric terminology (RDP) is used without mention of cross-platform equivalents. Automation examples mention PowerShell first, with Azure CLI and REST APIs listed afterward, but do not provide Linux/macOS-specific scripting guidance.
Recommendations
  • Include Linux/macOS alternatives for remote access, such as SSH gateways or cross-platform RDP solutions.
  • Provide links to documentation for setting up remote access on Linux (e.g., xrdp, SSH tunneling) alongside Windows Remote Desktop Gateway.
  • Offer scripting examples using Bash or Azure CLI on Linux/macOS, not just PowerShell.
  • Use neutral terminology (e.g., 'remote access') and clarify that RDP is one of several options.
  • Explicitly state platform support for automation and management tools.
GitHub Create Pull Request
Devtest Labs Troubleshoot Artifacts on Lab Virtual Machines ...vtest-labs/devtest-lab-troubleshoot-apply-artifacts.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. Troubleshooting steps and examples, especially for inspecting logs and running scripts, are detailed only for Windows VMs, using Windows tools (File Explorer, Command Prompt, PowerShell). Linux equivalents are either omitted or referenced only via external links, leaving Linux users with less direct guidance.
Recommendations
  • Provide parallel Linux instructions and examples for all troubleshooting steps, including log file locations, commands to inspect logs, and how to run artifact scripts.
  • Include Azure CLI examples alongside PowerShell for cross-platform parity.
  • When referencing file paths or tools, offer both Windows and Linux/macOS equivalents (e.g., File Explorer vs. 'ls' or 'cat' in the terminal).
  • Avoid referencing Windows tools or patterns exclusively; ensure Linux troubleshooting is not relegated to external links.
  • Structure sections so that Windows and Linux troubleshooting steps are presented side-by-side or clearly marked, rather than Windows-first.
GitHub Create Pull Request
Devtest Labs Upload a VHD file to lab storage by using Storage Explorer ...-labs/devtest-lab-upload-vhd-using-storage-explorer.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. While the main workflow uses Azure Storage Explorer (which is cross-platform), the instructions for obtaining the storage account name rely on navigating to a PowerShell-specific link and referencing the Add-AzureRmVhd cmdlet, which is a Windows/PowerShell tool. There are no equivalent instructions or references for Linux/macOS CLI tools (e.g., Azure CLI, Bash). Additionally, screenshots and terminology (e.g., 'PowerShell') are Windows-centric, and Windows tools are mentioned before any Linux alternatives.
Recommendations
  • Provide instructions for obtaining the storage account name using Azure CLI or Bash, which are cross-platform.
  • Include examples and screenshots for Linux/macOS users, such as using Azure CLI to list storage accounts and containers.
  • Clarify that the PowerShell method is just one option, and explicitly mention alternative methods for non-Windows users.
  • Add a section or note highlighting cross-platform approaches for each step, especially for tasks currently described with Windows/PowerShell tools.
GitHub Create Pull Request
Devtest Labs Create and deploy labs with Azure Resource Manager (ARM) templates ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/devtest-labs/devtest-lab-use-arm-and-powershell-for-lab-resources.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows Server VM is the only example given in the quickstart section, and PowerShell is heavily featured for automation tasks, with multiple links to PowerShell-specific guides and scripts. While Azure CLI is mentioned, most step-by-step instructions and linked resources focus on PowerShell, and there are no explicit Linux/macOS shell examples or references to Bash scripting. The quickstart template selection process is described only for Windows VMs, with no mention of Linux VM templates.
Recommendations
  • Include quickstart instructions for deploying labs with Linux VM templates alongside Windows examples.
  • Provide example automation workflows using Bash and Azure CLI, not just PowerShell.
  • Link to or create Linux/macOS-specific guides for common tasks (e.g., uploading VHDs, creating custom images, adding users) using CLI or REST API.
  • Ensure parity in screenshots and walkthroughs for Linux VM scenarios.
  • Highlight cross-platform compatibility in introductory sections.
GitHub Create Pull Request
Devtest Labs Import virtual machines from another lab ...vtest-labs/import-virtual-machines-from-another-lab.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and examples for importing VMs using PowerShell, a Windows-centric tool, with no mention of Linux/macOS alternatives (such as Bash, Azure CLI, or cross-platform scripting). The PowerShell method is presented first and in more detail, while the REST API section is less detailed and lacks platform-specific guidance for Linux/macOS users.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Provide Bash script samples for the REST API call, including usage of curl or httpie.
  • Explicitly state that PowerShell Core is available on Linux/macOS, and clarify if the provided script works on those platforms.
  • Reorder sections or add parity so that Linux/macOS-friendly methods are presented alongside or before Windows-specific tools.
GitHub Create Pull Request
Devtest Labs Azure DevTest Labs usage across multiple labs and subscriptions ...abs/report-usage-across-multiple-labs-subscriptions.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the only example language provided for exporting resource usage, and Windows-centric tools (PowerShell Az.Resource module, SQL Server, Power BI) are mentioned first or exclusively. There are no explicit Linux/macOS CLI or scripting examples, nor are Linux-friendly tools (e.g., Bash, Azure CLI, open-source visualization tools) referenced. This creates friction for Linux/macOS users who may not use PowerShell or Windows-specific tools.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for exporting resource usage.
  • List Linux/macOS-compatible tools (e.g., PostgreSQL, Grafana, Kibana) alongside SQL Server and Power BI.
  • Ensure that scripting and automation sections mention Python and Bash as alternatives to PowerShell, with sample code.
  • Order tool and example mentions in a platform-neutral way, or explicitly call out cross-platform options.
  • Add notes clarifying cross-platform compatibility for Azure Functions and Azure Automation, with links to relevant documentation.
GitHub Create Pull Request
Devtest Labs Specify resource group for Azure VMs in DevTest Labs ...b/main/articles/devtest-labs/resource-group-control.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
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 script example for configuring resource groups for Azure DevTest Labs VMs, but does not offer equivalent examples for Linux/macOS users (e.g., Bash, CLI, or shell scripting). The scripting section is Windows-centric, and PowerShell is presented as the only automation method. There is no mention of Linux tools or cross-platform alternatives, and the PowerShell example appears before the ARM template and API sections.
Recommendations
  • Add Bash or shell script examples using Azure CLI for Linux/macOS users.
  • Explicitly mention that the PowerShell script can be adapted to Bash or other shells.
  • Provide cross-platform instructions for invoking the Azure CLI directly from the terminal.
  • Clarify that the ARM template and API methods are platform-agnostic and suitable for all users.
  • Consider listing scripting options in a neutral order (e.g., CLI, PowerShell, ARM template) or grouping them by platform.
GitHub Create Pull Request
Devtest Labs Create a network isolated lab ...s/blob/main/articles/devtest-labs/network-isolation.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits moderate Windows bias. The only script provided for converting an existing lab to isolated network mode is a PowerShell script (.ps1), with no mention of Bash, Azure CLI, or cross-platform alternatives. Automation references mention PowerShell before Azure CLI. There is no explicit Linux/macOS example for scripting or automation, and Windows tools/scripts are referenced first and exclusively in critical conversion scenarios.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for converting an existing lab to isolated network mode.
  • Explicitly mention that PowerShell scripts can be run on Linux/macOS via PowerShell Core, or provide instructions for cross-platform usage.
  • When referencing automation, list Azure CLI and Bash alternatives alongside PowerShell, or present them first to avoid Windows-first bias.
  • Add notes or examples for Linux/macOS users, especially in sections involving scripting or automation.
GitHub Create Pull Request
Devtest Labs Quickstart: Create a lab with REST API ...n/articles/devtest-labs/quickstarts/create-lab-rest.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively uses PowerShell scripts and the Az PowerShell module for all steps, including authentication, request construction, and REST API invocation. No examples are provided for Linux/macOS users (e.g., Bash, curl, Azure CLI), and Windows tools and patterns are referenced throughout without mention of cross-platform alternatives. This creates friction for non-Windows users and may prevent them from following the quickstart without significant adaptation.
Recommendations
  • Add equivalent examples using Bash and curl for Linux/macOS users.
  • Include Azure CLI commands for authentication and REST API invocation, which are cross-platform.
  • Clearly indicate that PowerShell examples are Windows-centric and provide links or instructions for installing PowerShell Core on Linux/macOS if PowerShell must be used.
  • Present examples for both Windows and Linux/macOS side by side, or at least alternate which platform is shown first.
  • Mention that the Az PowerShell module is available for PowerShell Core on Linux/macOS, but also provide native Bash/curl/CLI alternatives.
GitHub Create Pull Request
Devtest Labs Azure CLI Samples ...re-docs/blob/main/articles/devtest-labs/samples-cli.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page consistently references 'powershell' as the script language for Azure CLI samples, even though the scripts are described as bash scripts. The primary VM creation example is for a Windows VM, and there is no mention of Linux VM creation or Linux/macOS shell usage. Windows terminology and examples are presented first and exclusively, which may create confusion or friction for Linux/macOS users.
Recommendations
  • Correct the script language references to 'bash' or 'shell' instead of 'powershell' for the included sample scripts.
  • Provide explicit examples for creating Linux VMs in addition to Windows VMs.
  • Ensure that script samples and code blocks are labeled and formatted for bash/shell when appropriate.
  • Add notes or sections clarifying usage on Linux/macOS platforms, including any differences in prerequisites or commands.
  • Present Linux and Windows examples side-by-side or alternate which is shown first.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for setting up a lab and VM in Azure DevTest Labs, but when guiding users to create a VM, it exclusively references a Windows Server 2019 Datacenter image and does not mention or provide examples for Linux-based VM creation. This may lead users to assume Windows is the default or only supported option, and Linux users may lack guidance for their use case.
Recommendations
  • Include explicit instructions and screenshots for creating a lab VM using a popular Linux image (e.g., Ubuntu, CentOS) alongside the Windows example.
  • When listing base images, mention both Windows and Linux options, and clarify that the process is similar for either OS.
  • Add notes or tips for Linux-specific configuration steps (e.g., SSH key setup, default user names).
  • Ensure that any references to VM configuration (artifacts, networking, etc.) highlight any differences or considerations for Linux VMs.
GitHub Create Pull Request
Devtest Labs Create a Service Fabric cluster environment ...test-labs/create-environment-service-fabric-cluster.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation exhibits Windows bias by presenting Windows as the default OS for the Service Fabric cluster, providing only PowerShell-based certificate creation instructions, and omitting equivalent Linux commands or guidance. The certificate creation process is described exclusively using a Windows PowerShell script, with no mention of how to perform this step on Linux or macOS. Windows is listed as the default option for the cluster OS, and no Linux-specific examples or troubleshooting are provided.
Recommendations
  • Add instructions for creating cluster certificates on Linux/macOS, using OpenSSL or equivalent tools.
  • Explicitly mention Linux as a supported OS option and provide parity in examples and screenshots.
  • Include alternative commands and scripts for Linux users where PowerShell is referenced.
  • Clarify any differences or additional steps required for Linux-based Service Fabric clusters.
GitHub Create Pull Request
Devtest Labs Create and add a VM to a lab .../blob/main/articles/devtest-labs/devtest-lab-add-vm.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page shows a moderate Windows bias. The main VM creation walkthrough uses a Windows 11 Pro image as its example, with no mention of Linux images or their settings. The only explicit scripting example for copying VMs uses a PowerShell script, with no Azure CLI or Linux shell alternatives provided. References to PowerShell and Windows appear before Azure CLI or ARM templates, and there are no screenshots or steps for Linux VM creation.
Recommendations
  • Include Linux VM creation examples and screenshots alongside Windows examples.
  • Explicitly mention that both Windows and Linux images are supported, and highlight any differences in settings (e.g., SSH keys for Linux).
  • Provide Azure CLI and Bash script alternatives for tasks currently shown only with PowerShell.
  • Ensure artifact examples include both Windows and Linux relevant artifacts.
  • Avoid using Windows images as the sole example; alternate or show parity with Linux images.
GitHub Create Pull Request
Devtest Labs Delete a lab virtual machine or a lab ...ain/articles/devtest-labs/devtest-lab-delete-lab-vm.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a PowerShell script as the only automation example for deleting all VMs in a lab, without mentioning or providing equivalent instructions for Linux/macOS users (e.g., Bash, Azure CLI). This creates friction for non-Windows users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add Azure CLI and/or Bash script examples for automating VM deletion, ensuring Linux/macOS users have clear guidance.
  • Explicitly mention cross-platform alternatives to PowerShell, such as Azure CLI, and link to relevant documentation.
  • Indicate whether PowerShell Core is required for non-Windows platforms if PowerShell must be used, and provide installation guidance.
GitHub Create Pull Request
Devtest Labs Azure CLI Samples ...re-docs/blob/main/articles/devtest-labs/samples-cli.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by consistently labeling Bash scripts as 'powershell' and by describing VM creation as producing a Windows VM by default. The code blocks use the 'powershell' language tag even though the scripts are Bash, which may confuse Linux/macOS users. Additionally, the documentation refers to creating a Windows VM without mentioning Linux VM options or examples.
Recommendations
  • Correct code block language tags from 'powershell' to 'bash' to accurately reflect the script type.
  • Explicitly mention that the scripts are Bash and compatible with Linux/macOS terminals.
  • Provide examples or notes for creating Linux VMs, not just Windows VMs.
  • Ensure that instructions and terminology do not imply Windows as the default or only supported platform.
GitHub Create Pull Request
Devtest Labs Specify resource group for Azure VMs in DevTest Labs ...b/main/articles/devtest-labs/resource-group-control.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides a detailed PowerShell script for configuring resource groups for Azure DevTest Labs VMs, but does not offer equivalent examples for Linux/macOS users (e.g., Bash or CLI). The scripting section is Windows/Powershell-centric, and PowerShell is presented before any cross-platform alternatives. There is no mention of Linux/macOS-specific instructions or examples.
Recommendations
  • Add Bash/Azure CLI example scripts for Linux/macOS users, demonstrating the same resource group configuration.
  • Explicitly state that the Azure CLI commands can be run on any platform, and provide platform-agnostic instructions.
  • Reorder examples so that cross-platform (CLI/ARM template/API) methods are presented before or alongside PowerShell.
  • Include notes or links to documentation for running Azure CLI on Linux/macOS.
GitHub Create Pull Request
Devtest Labs Add artifacts to VMs ...ocs/blob/main/articles/devtest-labs/add-artifact-vm.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and a complete script for adding artifacts to VMs using Azure PowerShell, but does not offer equivalent examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI). The PowerShell approach is presented as the only command-line method, and Windows/PowerShell tools are referenced exclusively, creating friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for artifact management, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Include Bash script samples or instructions for Linux users where applicable.
  • Explicitly mention that Azure PowerShell can be used from Linux/macOS (via Cloud Shell or local install), and provide installation guidance for those platforms.
  • Present command-line options in a neutral order (e.g., CLI first, then PowerShell, or side-by-side tabs).
GitHub Create Pull Request
Devtest Labs Add an Artifact Repository to Your Lab .../main/articles/devtest-labs/add-artifact-repository.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing detailed PowerShell scripts and examples for adding an artifact repository to Azure DevTest Labs, while omitting equivalent Linux/macOS shell (bash) examples. PowerShell is presented as the primary automation method, and deployment instructions via CLI are referenced but not shown directly. This creates friction for Linux/macOS users who may prefer bash or Azure CLI over PowerShell.
Recommendations
  • Add explicit bash/Azure CLI examples for deploying ARM templates and adding artifact repositories, including full command-line scripts.
  • Present Azure CLI and bash examples alongside PowerShell, not only as links but as first-class documentation sections.
  • Clarify that PowerShell is cross-platform, but also provide guidance for Linux/macOS users who may not use PowerShell.
  • Ensure screenshots and UI instructions do not assume Windows-only environments.
  • Where PowerShell scripts are provided, offer equivalent bash/CLI scripts for parity.
GitHub Create Pull Request
Devtest Labs Automate adding a lab user ...ob/main/articles/devtest-labs/automate-add-lab-user.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing PowerShell examples and cmdlets first and in greater detail, with no explicit Linux/macOS shell or cross-platform alternatives for key steps such as obtaining GUIDs or object IDs. The deployment and parameter generation steps are shown only with PowerShell, and references to tools are predominantly Windows-centric. While Azure CLI is mentioned, its example is brief and lacks parity with the PowerShell walkthrough.
Recommendations
  • Add equivalent Bash/Azure CLI examples for all steps currently shown only in PowerShell, including obtaining GUIDs and object IDs.
  • Explicitly mention that Azure CLI is cross-platform and provide step-by-step instructions for Linux/macOS users.
  • Where PowerShell cmdlets are referenced for tasks like GUID generation or querying Azure AD, provide CLI or REST API alternatives.
  • Reorder examples so that cross-platform (CLI) instructions are presented before or alongside PowerShell, not after.
  • Clarify any platform-specific requirements for tools and commands.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Azure PowerShell and Visual Studio tools prominently, listing PowerShell before Azure CLI, and omitting explicit Linux/macOS instructions or examples. There are no Linux-specific deployment patterns or parity in tooling coverage, and the Visual Studio reference further centers Windows workflows.
Recommendations
  • Add explicit Linux/macOS deployment instructions and examples, such as using Azure CLI on Bash.
  • Present Azure CLI examples before or alongside PowerShell to avoid Windows-first ordering.
  • Include alternative tooling for Linux/macOS users (e.g., VS Code, command-line editors) instead of only referencing Visual Studio.
  • Clarify that all steps can be performed on Linux/macOS and highlight any platform-specific considerations.
GitHub Create Pull Request
Devtest Labs Create custom artifacts for VMs ...n/articles/devtest-labs/devtest-lab-artifact-author.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. All code examples for artifact creation use PowerShell scripts and Windows-specific commands (e.g., powershell.exe, Chocolatey). There are no Linux shell script examples, nor is there guidance for creating Linux artifacts. The sample artifact references only Windows artifacts and scripts. Windows tools and patterns are mentioned exclusively, and Windows is implicitly treated as the default platform throughout.
Recommendations
  • Add parallel examples for Linux artifact creation using shell scripts (e.g., Bash) and Linux package managers (e.g., apt, yum).
  • Provide sample artifactfile.json and script files for Linux VMs, demonstrating the use of 'targetOsType': 'Linux'.
  • Include guidance on writing install commands for Linux, such as using bash, sh, or other Linux scripting languages.
  • Reference Linux tools and package managers alongside Windows tools (e.g., mention apt-get, yum, or zypper as alternatives to Chocolatey).
  • Ensure screenshots and folder examples include both Windows and Linux artifacts.
GitHub Create Pull Request
← Previous Page 10 of 14 Next →