Devtest Labs

188
Total Pages
144
Linux-Friendly Pages
44
Pages with Bias
23.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

113 issues found
Showing 51-75 of 113 flagged pages
Devtest Labs Deploy Azure DevTest Labs (Enterprise Reference Architecture) ...les/devtest-labs/devtest-lab-reference-architecture.md
Medium Priority View Details →
Scanned: 2026-01-12 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, primarily in its discussion of remote desktop connectivity. It exclusively references the Windows Remote Desktop Gateway and RDP protocol for remote access, linking to Windows Server documentation, without mentioning Linux/macOS alternatives (e.g., SSH, xrdp, VNC). Additionally, Windows-centric tools and patterns are discussed first or exclusively, with no Linux-specific examples or guidance for remote management or automation.
Recommendations
  • Include Linux/macOS remote access options (e.g., SSH, xrdp, VNC) alongside RDP/Remote Desktop Gateway.
  • Provide examples or references for managing DevTest Labs from Linux/macOS environments, such as using Azure CLI or REST APIs from Bash.
  • Add links to cross-platform remote access documentation and tools.
  • Clarify that DevTest Labs supports both Windows and Linux VMs, and describe any platform-specific considerations for connectivity and automation.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. Windows Server is the only OS mentioned in quickstart examples, and PowerShell is heavily featured for automation tasks, with multiple links to PowerShell-specific guides and scripts. There are no explicit Linux VM deployment examples, nor references to Linux-specific scripting or tools. Azure CLI is mentioned, but PowerShell instructions and links are more prominent and detailed.
Recommendations
  • Add explicit Linux VM deployment examples alongside Windows examples, especially in quickstart sections.
  • Include links to Linux shell (bash) scripts and automation guides in addition to PowerShell resources.
  • Ensure parity in instructions for Azure CLI and PowerShell, giving equal detail and prominence.
  • Reference Linux-compatible tools and workflows (e.g., Bash, cloud-init) where appropriate.
  • Clarify that ARM templates can deploy both Windows and Linux VMs, and provide sample templates for each.
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-12 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 are primarily focused on Windows environments, with PowerShell commands and Windows file paths shown exclusively. Linux troubleshooting is only referenced via external links, and no Linux-specific examples, commands, or file locations are provided inline. Windows tools (File Explorer, Command Prompt) are mentioned throughout, while Linux equivalents are absent.
Recommendations
  • Provide equivalent Linux troubleshooting steps inline, including commands for checking artifact status and inspecting logs (e.g., using Bash, SSH, Linux file paths).
  • Include Linux-specific examples for inspecting CSE logs, such as the default log file locations and commands to view them (e.g., cat, less).
  • Add Linux shell commands for verifying VM status and artifact application, using Azure CLI or Bash scripts.
  • Balance the use of Windows and Linux tools in instructions (e.g., mention Terminal instead of only Command Prompt/File Explorer).
  • Present both Windows and Linux examples side-by-side where possible, or clearly indicate which steps apply to each OS.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary method for obtaining the storage account name, including screenshots and instructions for using PowerShell cmdlets. There are no equivalent instructions or examples for Linux/macOS users (e.g., using Azure CLI or Bash). The workflow assumes familiarity with Windows tools and patterns, and PowerShell is mentioned before any cross-platform alternatives.
Recommendations
  • Add instructions and screenshots for obtaining the storage account name using Azure CLI, which is cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that PowerShell steps can be performed on Linux/macOS using PowerShell Core, or provide alternative commands for Bash/CLI.
  • Reorder sections so that cross-platform methods (Azure CLI, portal) are presented before or alongside PowerShell.
  • Clarify that Storage Explorer is available on all platforms and provide platform-specific tips if needed.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell commands are provided for disk migration, and references to Windows-specific patterns (such as RDP and OS disk swap via PowerShell) appear before or in more detail than Linux/SSH equivalents. The use of AzCopy is cross-platform, but the command-line examples and instructions are PowerShell-centric, with no explicit Bash or Linux CLI alternatives. Windows VM configuration (RDP) is described before Linux VM configuration (SSH), and the OS disk swap instructions link to a Windows PowerShell article, omitting Linux-specific guidance.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for disk migration and other tasks, alongside PowerShell.
  • Include explicit instructions or links for swapping OS disks on Linux VMs, not just Windows.
  • Present Linux/SSH examples in parallel with Windows/RDP examples, rather than after.
  • Clarify that AzCopy is available on Linux/macOS and provide sample commands for those platforms.
  • Reference Azure Cloud Shell's Bash option, not just PowerShell.
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-12 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, primarily through its reliance on PowerShell for scripting tasks (specifically, converting an existing lab to isolated network mode), and by referencing a PowerShell script as the sole automation method. While Azure CLI is mentioned as an alternative for automating some steps, no explicit Linux/macOS-friendly examples or scripts are provided. The documentation also lists PowerShell before Azure CLI, and does not offer Bash or Linux-native instructions for key automation tasks.
Recommendations
  • Provide Azure CLI and Bash script equivalents for all PowerShell automation tasks, especially for converting an existing lab to isolated network mode.
  • Explicitly include Linux/macOS command-line examples alongside PowerShell, ensuring parity in instructions and tooling.
  • Reference cross-platform tools (e.g., Azure CLI) before or alongside PowerShell, and clarify platform compatibility for each method.
  • Add notes or sections for Linux/macOS users, highlighting any differences or additional steps required.
GitHub Create Pull Request
Devtest Labs Extend Azure DevTest Labs with Azure Functions ...es/devtest-labs/extend-devtest-labs-azure-functions.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All development and deployment instructions are centered around Visual Studio, a Windows-first IDE, with screenshots and steps that assume a Windows environment. The sample code is provided for C# and PowerShell, both of which are traditionally Windows-centric, and the only explicit automation example in 'Related content' is PowerShell-based. There are no instructions, examples, or screenshots for Linux/macOS users, nor are alternative tools (such as VS Code or Azure CLI for deployment) mentioned.
Recommendations
  • Add instructions for building and deploying the sample using cross-platform tools like VS Code and Azure CLI.
  • Include Linux/macOS-specific steps and screenshots where relevant.
  • Provide bash or shell script equivalents for service principal creation and automation tasks.
  • Highlight that Azure Functions development can be done on Linux/macOS and link to relevant documentation.
  • Mention and provide examples for deploying from non-Windows environments.
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-12 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 describing the creation of a 'Windows VM' as the default use case and labeling all sample scripts as 'powershell' language blocks, even though the scripts are Bash scripts for Azure CLI. There is no mention of Linux VMs or Linux-specific instructions, and the terminology and examples are Windows-centric.
Recommendations
  • Clarify that the sample scripts are Bash scripts and update code block language to 'bash' instead of 'powershell'.
  • Provide examples for creating both Windows and Linux VMs, or clarify that the scripts work for both.
  • Include notes or sections relevant to Linux/macOS users, such as SSH authentication details or platform-specific considerations.
  • Avoid using Windows terminology as the default; use neutral language (e.g., 'virtual machine') and specify OS options.
GitHub Create Pull Request
Devtest Labs Define VM start order with Azure Automation ...devtest-labs/start-machines-use-automation-runbooks.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell for scripting and Azure Automation, which is most commonly used on Windows. There are no examples or guidance for Bash, Azure CLI, or Linux-native automation tools. The script and instructions assume a Windows-centric workflow, with no mention of Linux/macOS alternatives or cross-platform compatibility.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for Linux/macOS users.
  • Clarify whether the PowerShell script can run on PowerShell Core (cross-platform) and, if so, provide guidance for Linux/macOS environments.
  • Mention and link to Linux-friendly automation options, such as using Azure CLI in Azure Automation or GitHub Actions.
  • Add a section comparing Windows and Linux approaches, including any platform-specific caveats.
GitHub Create Pull Request
Devtest Labs Use commands to start and stop lab VMs ...t-labs/use-command-line-start-stop-virtual-machines.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. PowerShell (a Windows-centric tool) is presented first in both prerequisites and example sections. Azure CLI examples do include both Bash (Linux/macOS) and Windows syntax, but Windows command syntax is shown alongside Bash, sometimes with Windows examples appearing first. The PowerShell section is more detailed and uses Windows-specific cmdlets. There is no explicit Linux/macOS-only workflow or troubleshooting guidance, and the overall structure assumes familiarity with Windows tools and patterns.
Recommendations
  • Alternate the order of PowerShell and Azure CLI sections, or present Azure CLI (cross-platform) first.
  • Provide more detailed Bash/Linux/macOS examples, including troubleshooting steps specific to non-Windows environments.
  • Clarify that PowerShell Core is available on Linux/macOS, and provide installation links for those platforms.
  • Avoid using Windows-specific syntax (e.g., 'REM' for comments) in CLI examples unless clearly marked as Windows-only.
  • Add explicit notes or sections for Linux/macOS users regarding environment setup and common issues.
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-11 06:20
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 example for automating deletion of all VMs in a lab, with no mention of Azure CLI, Bash, or Linux/macOS-compatible alternatives. This creates friction for Linux and macOS users who may not have access to PowerShell or prefer other tools.
Recommendations
  • Add equivalent Azure CLI and/or Bash script examples for automating VM deletion.
  • Explicitly mention that PowerShell is available cross-platform, or provide links to install PowerShell on Linux/macOS if PowerShell must be used.
  • List both Windows and Linux/macOS automation options side-by-side, or alternate which is shown first.
  • Clarify tool requirements for each example and provide guidance for users on different platforms.
GitHub Create Pull Request
Devtest Labs Integrate Azure DevTest Labs with DevOps CI/CD Pipelines ...blob/main/articles/devtest-labs/devtest-lab-dev-ops.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation references PowerShell scripts and Azure CLI as integration methods, but lists PowerShell before Azure CLI and does not provide explicit Linux/macOS examples or mention Bash scripting. There is an implicit prioritization of Windows tools and patterns, with no direct guidance for Linux users.
Recommendations
  • Explicitly mention Bash scripting and provide examples for Linux/macOS environments alongside PowerShell.
  • List Azure CLI and REST API usage before or alongside PowerShell to avoid Windows-first ordering.
  • Add a section or callout for Linux/macOS users, clarifying how to perform tasks using their native tools.
  • Ensure that all sample scripts and automation patterns are cross-platform or provide platform-specific variants.
GitHub Create Pull Request
Devtest Labs Add and configure lab users with role-based access control (RBAC) .../articles/devtest-labs/devtest-lab-add-devtest-user.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides two methods for adding lab users: Azure portal and Azure PowerShell. The scripting example is exclusively in PowerShell, with no Bash, CLI, or Linux/macOS shell equivalent. PowerShell is presented as the only automation option, and prerequisites reference installing Azure PowerShell, which is natively a Windows tool (though it can run cross-platform). There is no mention of Azure CLI or Bash scripting, and the PowerShell tab appears before any Linux-friendly alternatives.
Recommendations
  • Add an Azure CLI example for adding lab users, which works natively on Linux/macOS.
  • Explicitly mention that Azure PowerShell is available cross-platform, but provide parity with CLI/Bash for Linux/macOS users.
  • Reorder or parallelize examples so that Azure CLI and PowerShell are presented together, or allow users to select their preferred environment.
  • Reference installation and usage instructions for Azure CLI alongside PowerShell.
  • Clarify that all steps can be performed from any OS via the portal, and highlight automation options for Linux/macOS users.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Although Azure Storage Explorer is cross-platform, the instructions for obtaining the storage account name rely exclusively on navigating to a PowerShell-based workflow, with screenshots and steps referencing PowerShell cmdlets. There are no Linux or macOS CLI alternatives (such as Azure CLI or Bash) provided for this step, and PowerShell is mentioned before any other tool. The upload process itself is platform-neutral, but the prerequisite steps may create friction for non-Windows users.
Recommendations
  • Provide alternative instructions for obtaining the storage account name using Azure CLI or Bash, which are available on Linux/macOS.
  • Include screenshots or examples for Linux/macOS environments where relevant.
  • Clarify that the PowerShell workflow is just one option, and link to platform-neutral or Linux/macOS-specific methods.
  • Reorder examples so that platform-neutral or cross-platform methods are presented before Windows-specific ones.
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-11 06:20
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 sample scripts as 'powershell' even though the script files have a '.sh' extension, indicating Bash shell scripts. Additionally, the first example explicitly creates a Windows VM, with no mention or example for creating a Linux VM. The documentation does not provide Linux/macOS-specific instructions or parity in VM creation examples.
Recommendations
  • Correct the code block language labeling from 'powershell' to 'bash' for .sh scripts to avoid confusion for Linux/macOS users.
  • Add explicit examples for creating Linux VMs in Azure DevTest Labs, including sample scripts and command options.
  • Ensure that instructions and examples are platform-neutral or provide parallel instructions for both Windows and Linux/macOS users.
  • Clarify any platform-specific prerequisites or differences in script execution environments.
GitHub Create Pull Request
Devtest Labs Define VM start order with Azure Automation ...devtest-labs/start-machines-use-automation-runbooks.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell scripts and Azure Automation runbooks, which are Windows-centric tools. There are no examples or guidance for Linux/macOS users, such as Bash, Azure CLI, or Python alternatives. The instructions and code are tailored to Windows environments, creating friction for users on other platforms.
Recommendations
  • Provide equivalent examples using Azure CLI, Bash, or Python scripts for Linux/macOS users.
  • Explicitly mention cross-platform alternatives to PowerShell and Azure Automation, such as using Azure CLI tasks in pipelines or cron jobs.
  • Reorder examples so that cross-platform solutions are presented alongside or before Windows-specific instructions.
  • Add a section discussing platform compatibility and how Linux/macOS users can achieve the same outcome.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page provides detailed instructions and a full script for adding artifacts to Azure DevTest Labs VMs using Azure PowerShell, but does not offer equivalent examples or guidance for Linux/macOS users (e.g., Azure CLI or Bash). The prerequisites and examples focus exclusively on PowerShell, which is traditionally a Windows tool, and the instructions for command-line usage are Windows-centric. There is no mention of Linux-native tools or workflows, nor are Linux/macOS command-line examples provided.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples for adding artifacts to VMs, ensuring Linux/macOS users have clear guidance.
  • In the prerequisites, mention Azure CLI as an alternative to PowerShell, with installation and usage instructions.
  • Present both PowerShell and CLI/Bash examples side-by-side or in tabs, rather than only PowerShell.
  • Clarify that PowerShell Core is cross-platform, but also provide native Linux/macOS options for users who prefer them.
  • Review related content for similar bias and add Linux/macOS parity where missing.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by providing extensive PowerShell examples and cmdlet references, mentioning PowerShell tools and patterns first, and omitting explicit Linux/macOS shell or cross-platform CLI examples for key steps such as GUID generation and Active Directory object lookup. While Azure CLI is mentioned, the majority of walkthroughs and code samples are PowerShell-centric, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent bash/Azure CLI examples for all PowerShell commands, especially for GUID generation and Active Directory object lookup.
  • Present Azure CLI and PowerShell examples side-by-side, or alternate which is shown first.
  • Explicitly note cross-platform alternatives for tasks currently described only with PowerShell (e.g., using uuidgen for GUIDs, az ad user for object IDs).
  • Clarify that Azure CLI and REST API approaches work on all platforms, and provide full command examples for Linux/macOS users.
GitHub Create Pull Request
Devtest Labs Secure Labs by Using Remote Desktop Gateways ...s/devtest-labs/configure-lab-remote-desktop-gateway.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. All examples and instructions for certificate creation, configuration automation, and gateway setup use Windows-centric tools (PowerShell scripts, IIS modules, RDGatewayFedAuth.msi, and references to Windows Server Remote Desktop Services). There are no Linux/macOS equivalents or alternative instructions for users on those platforms. Windows tools and patterns are mentioned exclusively and appear first throughout the guide.
Recommendations
  • Provide Linux/macOS equivalents for certificate creation (e.g., using OpenSSL commands).
  • Include instructions for automating lab configuration using Bash scripts or Azure CLI on Linux/macOS.
  • Mention and document alternatives to IIS for request routing, such as NGINX or Apache on Linux.
  • Clarify whether RDGatewayFedAuth.msi or other components have cross-platform support, and if not, suggest Linux-compatible alternatives.
  • Add explicit examples for connecting to VMs from Linux/macOS clients (e.g., using FreeRDP, Remmina, or Microsoft Remote Desktop for macOS).
  • Ensure that ARM template deployment steps are platform-neutral and provide CLI commands that work on all OSes.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed instructions and examples for adding an artifact repository to Azure DevTest Labs, with a strong emphasis on Azure PowerShell and ARM template deployment via PowerShell. PowerShell scripts and commands are featured prominently and exclusively for automation, with no Bash, shell, or Linux-native CLI script examples. While Azure CLI is mentioned as an alternative for ARM template deployment, it is not demonstrated, and all code samples are PowerShell-centric. This creates friction for Linux/macOS users who may prefer Bash or Azure CLI workflows.
Recommendations
  • Add equivalent Azure CLI (az) command examples for ARM template deployment and repository management.
  • Provide Bash or shell script examples for automating repository addition, especially for Linux/macOS users.
  • Ensure that automation sections present both PowerShell and CLI/Bash options side-by-side.
  • Clarify that PowerShell is cross-platform, but explicitly mention and demonstrate Linux/macOS usage where relevant.
  • Reorder or balance examples so that Windows and Linux approaches are presented with equal prominence.
GitHub Create Pull Request
Devtest Labs Nested ARM templates for lab environments ...es/devtest-labs/deploy-nested-template-environments.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references Azure PowerShell (New-AzResourceGroupDeployment) before Azure CLI (az deployment group create) when describing deployment commands, and mentions Visual Studio as a tool for ARM template development without Linux/macOS alternatives. There are no explicit Linux/macOS-specific instructions or examples, and the command-line examples do not show parity between PowerShell and Bash/shell usage.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform.
  • Include explicit Bash/shell command examples for Linux/macOS users.
  • Mention cross-platform editors (such as VS Code) in addition to Visual Studio.
  • Clarify that both Azure CLI and PowerShell are available on all platforms, and provide installation links for Linux/macOS.
  • Add notes or sections highlighting any platform-specific considerations for template deployment.
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-11 06:20
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 tools (e.g., powershell.exe, Chocolatey). There are no equivalent Linux shell script examples, nor is there guidance for Linux artifact creation. Windows artifacts and tools are mentioned first and exclusively in critical sections, leaving Linux users without clear instructions or parity.
Recommendations
  • Add Linux-focused examples, such as using Bash scripts in the artifact definition (e.g., commandToExecute with bash or sh).
  • Provide sample artifactfile.json and script files for Linux, similar to the Windows/PowerShell examples.
  • Include references to Linux package managers (e.g., apt, yum) in artifact creation scenarios.
  • Ensure that instructions and screenshots show both Windows and Linux artifact folder structures.
  • Explicitly describe differences and requirements for Linux artifact development, including script file extensions and execution permissions.
GitHub Create Pull Request
Devtest Labs Create environments from ARM templates ...evtest-labs/devtest-lab-create-environment-from-arm.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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, especially in the automation section. The only detailed script provided for automating environment creation uses Azure PowerShell, which is most commonly used on Windows. While the Azure CLI is briefly mentioned as an alternative, no example or walkthrough is provided for it. The step-by-step instructions and screenshots focus on the Azure portal, which is cross-platform, but the scripting and automation guidance is Windows-centric. There are no Linux/macOS-specific examples or notes about platform compatibility for the PowerShell script.
Recommendations
  • Provide a full Azure CLI example for automating environment creation, including a sample script and usage instructions.
  • Explicitly note platform compatibility for the PowerShell script and offer guidance for running it on Linux/macOS (e.g., using PowerShell Core).
  • Present both PowerShell and Azure CLI automation options side-by-side, or show CLI first to avoid Windows-first bias.
  • Include troubleshooting notes or links for Linux/macOS users who may encounter issues with PowerShell modules.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias by presenting Windows as the default OS for cluster VMs, providing only PowerShell-based certificate creation instructions, and omitting Linux-specific guidance or examples. The certificate creation process relies exclusively on a PowerShell script (.ps1), with no mention of Linux-compatible alternatives or commands. Although the cluster can be created on Linux or Windows, the steps and tooling are Windows-centric.
Recommendations
  • Provide explicit instructions and examples for Linux users, including how to generate the required certificate using Linux tools (e.g., OpenSSL) and how to encode it in Base64.
  • Include Linux shell (bash) commands alongside PowerShell for certificate creation and other steps.
  • Clarify that the default OS is Windows, but Linux is fully supported, and offer guidance on selecting and configuring Linux as the cluster OS.
  • Add screenshots or walkthroughs for Linux-based environments where relevant.
GitHub Create Pull Request
Devtest Labs Create custom images for lab VMs from VHD files ...n/articles/devtest-labs/devtest-lab-create-template.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
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 an option. Windows-specific tools and terminology (such as 'sysprep') are referenced before their Linux equivalents ('deprovision'), and PowerShell is highlighted as a primary automation method. While Linux is supported and mentioned, Windows examples and tools are consistently presented first, and there is a lack of explicit Linux/macOS command-line alternatives (e.g., Bash/Azure CLI) for key steps.
Recommendations
  • Provide explicit Linux/macOS command-line examples (e.g., Bash, Azure CLI) for uploading VHD files and creating images.
  • Mention Linux tools and patterns (such as Azure CLI, shell scripts) alongside or before Windows/PowerShell options.
  • Ensure that instructions for Linux users are equally detailed and accessible as those for Windows users.
  • Add screenshots or walkthroughs from Linux/macOS environments where relevant.
GitHub Create Pull Request
← Previous Page 3 of 5 Next →