Dev Box

85
Total Pages
35
Linux-Friendly Pages
50
Pages with Bias
58.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

217 issues found
Showing 26-50 of 217 flagged pages
Dev Box Use modular scripts and files in Dev Box customizations ...les/dev-box/includes/customizations-modular-scripts.md
High 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 strong Windows bias by exclusively referencing Windows-centric tools (PowerShell, DSC, WinGet), using Windows file paths, and omitting any Linux/macOS equivalents or examples. All code samples and catalog structures are tailored to Windows environments, with no mention of Bash, shell scripts, or cross-platform alternatives.
Recommendations
  • Add equivalent examples for Linux/macOS, such as Bash scripts or shell scripts.
  • Reference Linux file paths and demonstrate how modular scripts and files can be structured for non-Windows environments.
  • Include cross-platform tools (e.g., apt, yum, Homebrew) in addition to WinGet.
  • Clarify whether Dev Box supports Linux/macOS images and, if so, provide relevant customization guidance.
  • Present examples for both Windows and Linux/macOS side-by-side, or indicate platform-specific sections.
GitHub Create Pull Request
Dev Box Reference: imagedefinition.yaml and task.yaml Files ...n/articles/dev-box/reference-dev-box-customizations.md
High 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 is heavily oriented toward Windows environments, with all examples and built-in tasks focused on PowerShell and WinGetβ€”both Windows-specific tools. There are no examples or guidance for Linux/macOS users, nor mention of cross-platform alternatives. The schema and usage patterns assume Windows as the default, creating friction for non-Windows users.
Recommendations
  • Add examples for Linux/macOS environments, such as using Bash or shell scripts as built-in tasks.
  • Document how to customize dev boxes based on non-Windows images, including supported base images and relevant tooling.
  • Introduce built-in tasks for common Linux package managers (e.g., apt, yum, dnf, Homebrew) alongside WinGet.
  • Clarify platform compatibility for each built-in task and provide parity in features and examples.
  • Present examples for both Windows and Linux/macOS environments, or explicitly state platform limitations.
GitHub Create Pull Request
Dev Box Configure Azure Compute Gallery ...cles/dev-box/how-to-configure-azure-compute-gallery.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All example images and OS requirements are Windows-only (Windows 10/11 Enterprise), with no mention of Linux or other operating systems. All image preparation steps reference Windows-specific tools and commands (Sysprep, DISM, defrag, chkdsk, PowerShell), and UI instructions are for Windows features. There are no Linux equivalents, examples, or guidance for preparing Linux images or using Linux tools. The documentation assumes the user is working in a Windows environment throughout.
Recommendations
  • Add explicit support and examples for Linux images, including listing compatible Linux distributions and versions.
  • Provide Linux-specific image preparation steps, such as using waagent for generalization, and commands for cleaning up and optimizing Linux images.
  • Include CLI examples for Linux environments (bash, Azure CLI) alongside PowerShell commands.
  • Clarify whether Microsoft Dev Box supports Linux images, and if not, state this limitation early and clearly.
  • If Linux is supported, add screenshots and UI guidance relevant to Linux image creation and management.
  • Ensure parity in troubleshooting and optimization steps for both Windows and Linux images.
GitHub Create Pull Request
Dev Box Resolve connectivity issues with Troubleshoot and Repair ...articles/dev-box/how-to-troubleshoot-repair-dev-box.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation page focuses exclusively on troubleshooting Remote Desktop Protocol (RDP) connectivity issues for dev boxes, with all examples and checks centered around Windows environments. Windows-specific terms (RDP, Windows Guest OS readiness) are used throughout, and there are no references to Linux connectivity methods (such as SSH), Linux guest OS readiness, or troubleshooting steps for Linux-based dev boxes. The troubleshooting tool and its checks are described only in the context of Windows, and no Linux equivalents or alternative instructions are provided.
Recommendations
  • Include troubleshooting steps and examples for Linux-based dev boxes, such as SSH connectivity issues.
  • Mention Linux guest OS readiness checks alongside Windows checks.
  • Provide parity in tool descriptions and screenshots for Linux environments, if supported.
  • Clarify whether the Troubleshoot & Repair tool supports Linux dev boxes, and if not, suggest alternative troubleshooting methods for Linux users.
  • Add documentation sections or links for Linux-specific troubleshooting and repair processes.
GitHub Create Pull Request
Dev Box Configure virtual switches for dev boxes ...icles/dev-box/how-to-connect-dev-box-virtual-switch.md
High Priority View Details →
Scanned: 2026-01-11 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 strong Windows bias. All configuration steps use PowerShell commands and reference Windows-specific tools (Hyper-V, New-VMSwitch, New-NetIPAddress, New-NetNat). There are no examples or guidance for Linux users, nor mention of Linux virtualization tools or commands. The instructions and screenshots assume a Windows environment, with no parity for Linux workflows.
Recommendations
  • Add equivalent Linux instructions using tools such as KVM, libvirt, and virsh for creating virtual switches and NAT networks.
  • Provide Linux command-line examples (e.g., using ip, brctl, virsh, or nmcli) alongside PowerShell commands.
  • Include notes or sections clarifying support and steps for Linux-based dev boxes.
  • Add screenshots and UI guidance for Linux network configuration dialogs.
  • Mention Linux prerequisites (e.g., installation of KVM, libvirt, bridge-utils) in the prerequisites section.
GitHub Create Pull Request
Dev Box Grant access to Microsoft Dev Box .../main/articles/dev-box/how-to-manage-dev-box-access.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
πŸ”§ Windows Tools Windows First Missing Linux Example
Summary
The documentation page exclusively describes role assignment and management using the Azure portal, a graphical interface most commonly used on Windows. There are no examples or instructions for performing these tasks via command-line tools such as Azure CLI or PowerShell, nor are Linux-specific workflows or screenshots provided. The documentation implicitly assumes use of the Azure portal, which is most familiar to Windows users, and does not mention or prioritize cross-platform alternatives.
Recommendations
  • Add step-by-step instructions for assigning roles using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include PowerShell examples for role assignment, and clarify that PowerShell Core is available on Linux and macOS.
  • Provide screenshots or terminal output examples from Linux environments to demonstrate parity.
  • Explicitly mention that all role assignment tasks can be performed from Linux, macOS, or Windows using CLI tools.
  • Consider reordering sections so that cross-platform command-line methods are presented before or alongside portal-based instructions.
GitHub Create Pull Request
Dev Box Authoring recommendations for Dev Box image definitions ...pt-authoring-troubleshooting-guide-team-customizations.md
High Priority View Details →
Scanned: 2026-01-11 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 strong Windows bias. All examples, tools, and troubleshooting steps are centered around Windows-specific technologies such as PowerShell, WinGet, and Windows file paths. The Dev Box CLI usage, log locations, and built-in tasks (~/winget, ~/powershell) are described exclusively in a Windows context. There are no Linux or cross-platform equivalents provided, nor any mention of Linux package managers, shell scripting, or file system paths. The troubleshooting and optimization sections also focus on PowerShell and Windows conventions, with no guidance for Linux-based Dev Boxes.
Recommendations
  • Include Linux-specific examples alongside Windows ones, such as using Bash scripts, apt/yum/dnf package managers, and Linux file paths.
  • Document how to author and test image definitions for Linux Dev Boxes, if supported, including relevant built-in tasks and troubleshooting steps.
  • Mention cross-platform tools and patterns (e.g., using VS Code on Linux, using shell scripts as primitives) where applicable.
  • Clarify which features, tasks, and troubleshooting steps apply only to Windows Dev Boxes and which are available for Linux.
  • Provide guidance on handling secrets, logs, and context placement in Linux environments (e.g., log file locations, permissions).
  • Add parity in optimization tips for file downloads, such as using wget/curl on Linux, and discuss performance considerations for Linux.
GitHub Create Pull Request
Dev Box Microsoft Dev Box deployment guide ...n/articles/dev-box/concept-dev-box-deployment-guide.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools Powershell Heavy
Summary
The documentation for Microsoft Dev Box deployment is heavily oriented toward Windows environments. It references Windows-specific management tools (Intune, Endpoint Privilege Management), Windows device configuration, and examples involving Windows-centric package managers (WinGet, Chocolatey) and PowerShell scripts. There is no mention of Linux VM images, Linux device management, or Linux-specific customization/catalog options. All device management, access control, and troubleshooting guidance is framed in terms of Windows tools and patterns, with no Linux parity or examples.
Recommendations
  • Add explicit guidance and examples for deploying and managing Linux-based dev boxes, including supported Linux distributions and configuration steps.
  • Include Linux equivalents for customization tasks, such as using apt, yum, or other package managers, and shell scripts instead of only PowerShell/WinGet/Chocolatey.
  • Document how device management, compliance, and access control can be handled for Linux dev boxes, including any Intune or alternative tooling support.
  • Provide troubleshooting and monitoring instructions relevant to Linux dev boxes (e.g., log locations, remote access methods, OS-specific health checks).
  • Ensure that examples and patterns are presented in a cross-platform manner, or at least alternate between Windows and Linux, rather than Windows-first.
GitHub Create Pull Request
Dev Box Roadmap for Microsoft Dev Box ...ure-docs/blob/main/articles/dev-box/dev-box-roadmap.md
High Priority View Details →
Scanned: 2026-01-11 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 for Microsoft Dev Box roadmap demonstrates a Windows bias in several ways. It references Windows-specific tools and patterns (PowerShell, Winget, RDP), and features are described in terms of Windows-centric workflows. Examples and customization primitives are limited to PowerShell and Winget, with no mention of Linux equivalents (e.g., Bash, apt, yum). The language and feature descriptions prioritize Windows tools and experiences, and there are no examples or guidance for Linux-based development environments or tools. Even when mentioning WSL, it is in the context of accessing it from a Windows Dev Box, not as a first-class Linux environment.
Recommendations
  • Include examples and customization primitives for Linux environments (e.g., Bash scripts, apt/yum/dnf package managers) alongside PowerShell and Winget.
  • Explicitly mention support for Linux-based Dev Box images and workflows, if available, or clarify roadmap plans for Linux parity.
  • Provide guidance and examples for onboarding, configuring, and managing Dev Box environments using Linux tools and patterns.
  • Ensure that documentation references cross-platform tools (e.g., VS Code, GitHub Copilot) in a way that highlights their use on both Windows and Linux.
  • Add sections or notes describing how Linux developers can leverage Dev Box, including remote access, package management, and environment customization.
GitHub Create Pull Request
Dev Box Secure Dev Tunnel Access with Conditional Policies ...v-box/how-to-conditional-access-dev-tunnels-service.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by requiring PowerShell 7.x in the prerequisites, providing only PowerShell command examples, and referencing Windows-specific concepts such as Dev Box and GPO. There are no Linux shell (bash/zsh) or cross-platform CLI examples, and Linux tools or workflows are not mentioned. The documentation assumes a Windows-centric environment and does not address Linux developer needs.
Recommendations
  • Include Linux shell (bash/zsh) equivalents for all command-line examples, especially for 'code tunnel' commands.
  • Clarify whether PowerShell is required on Linux/macOS, or provide instructions for using native shells.
  • Mention Linux and macOS compatibility for Dev Tunnels and conditional access configuration, if supported.
  • Add notes or sections for Linux users, including any platform-specific limitations or requirements.
  • Reference cross-platform tools and patterns alongside Windows-specific ones, and avoid assuming a Windows-first workflow.
GitHub Create Pull Request
Dev Box Streamline Your Workflow with Dev Box Customizations ...les/dev-box/concept-what-are-dev-box-customizations.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a strong Windows bias by exclusively referencing PowerShell scripts and WinGet as the primary mechanisms for Dev Box customization tasks. There are no examples or mentions of Linux shell scripts, Linux-native tools, or cross-platform scripting options. The documentation assumes a Windows environment and does not address how Linux-based Dev Boxes (if supported) would be customized, nor does it provide parity in examples or guidance for non-Windows users.
Recommendations
  • Include examples and guidance for customizing Linux-based Dev Boxes, if supported, such as using Bash scripts or Linux package managers (e.g., apt, yum).
  • Mention and provide parity for Linux-native tools and scripting environments alongside PowerShell and WinGet.
  • Clarify whether Dev Box supports Linux environments, and if so, provide documentation and examples for both Windows and Linux scenarios.
  • When listing built-in tasks or customization mechanisms, present Windows and Linux options together, or clearly indicate platform-specific differences.
  • Add sample YAML customization files that demonstrate both Windows (PowerShell/WinGet) and Linux (Bash/apt/yum) task usage.
GitHub Create Pull Request
Dev Box Configure Customization Tasks ...ticles/dev-box/how-to-configure-customization-tasks.md
High Priority View Details →
Scanned: 2026-01-11 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 strong Windows bias by exclusively referencing PowerShell scripts and Windows-specific tools like WinGet and Desired State Configuration (DSC). All examples and instructions assume the use of PowerShell, with no mention of Linux shell scripting, Bash, or cross-platform alternatives. Windows tools and patterns are presented as the default or only option, and there are no examples or guidance for Linux environments or non-Windows customization workflows.
Recommendations
  • Include examples of tasks using Bash scripts or other Linux shell scripting languages alongside PowerShell.
  • Mention and provide guidance for Linux package managers (e.g., apt, yum) in addition to WinGet.
  • Clarify whether Dev Box supports Linux-based images and, if so, provide equivalent instructions for customizing those environments.
  • Add documentation sections or links for cross-platform or Linux-specific customization scenarios.
  • Avoid presenting Windows tools and patterns as the only or default option; instead, explicitly state platform limitations and alternatives.
GitHub Create Pull Request
Dev Box Intune Conditional Access Policies for Dev Boxes ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-intune-conditional-access-policies.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by focusing exclusively on Windows-centric tools and services such as Microsoft Remote Desktop, Windows 365, and Windows Azure Service Management API. There are no examples or mentions of Linux-specific tools, clients, or access patterns, nor are there instructions for configuring access from Linux environments. All scenarios and app tables prioritize Windows technologies, with no parity for Linux users.
Recommendations
  • Include examples and instructions for accessing Dev Boxes from Linux clients, such as using open-source RDP clients (e.g., FreeRDP, Remmina) or SSH.
  • Mention Linux-compatible alternatives for remote desktop and management, and clarify any limitations or requirements for Linux users.
  • Add guidance for configuring Conditional Access policies for Linux endpoints, including compliance and registration steps.
  • Provide parity in tables and scenarios by listing Linux tools and workflows alongside Windows ones.
  • Explicitly state support or lack thereof for Linux in Dev Box scenarios, so users can plan accordingly.
GitHub Create Pull Request
Dev Box Configure hibernation for Microsoft Dev Box ...ticles/dev-box/how-to-configure-dev-box-hibernation.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Missing Linux Example
Summary
The documentation page exhibits a clear Windows bias. All example commands, troubleshooting steps, and configuration instructions are focused exclusively on Windows environments. Windows-specific features (such as Memory Integrity, Nested Virtualization, and Windows Security UI) are discussed in detail, while there is no mention of Linux equivalents or support. No Linux-based dev box scenarios, images, or configuration steps are provided, and all CLI examples use Windows as the OS type. The troubleshooting section also refers only to Windows VM issues.
Recommendations
  • Add explicit guidance for configuring hibernation on Linux-based dev boxes, if supported.
  • Include CLI examples for Linux images (e.g., using --os-type linux) and note any differences in flags or prerequisites.
  • Discuss compatibility considerations for Linux images, such as kernel or virtualization settings that may affect hibernation.
  • Provide troubleshooting steps and links for Linux VM hibernation issues.
  • Clarify in the introduction and relevant sections whether hibernation is supported for Linux dev boxes, and if not, state this explicitly.
GitHub Create Pull Request
Dev Box Create Dev Box Image Definition Files for Team Customizations ...ticles/dev-box/how-to-configure-team-customizations.md
High Priority View Details →
Scanned: 2026-01-11 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 clear Windows bias. All built-in tasks and examples focus exclusively on Windows-centric tools such as PowerShell, WinGet, and Desired State Configuration (DSC), with no mention of Linux equivalents (e.g., Bash, apt, yum, shell scripts). The only configuration management example is PowerShell DSC, and all sample prompts and workflows assume Windows environments and tooling. There are no Linux-specific instructions, examples, or references to cross-platform support, and Windows tools are introduced first and exclusively.
Recommendations
  • Add examples and instructions for Linux-based dev boxes, including how to use Bash, shell scripts, and Linux package managers (apt, yum, zypper) in image definition files.
  • Include Linux equivalents for built-in tasks, such as support for Bash scripts or Linux-native configuration management tools (e.g., Ansible, cloud-init).
  • Provide sample YAML image definition files for Linux environments, showing installation of common Linux development tools.
  • Clarify platform support in the prerequisites and task sections, explicitly stating whether Linux dev boxes are supported and how to customize them.
  • Mention cross-platform considerations when describing catalog tasks and agentic workflows, ensuring parity for both Windows and Linux users.
GitHub Create Pull Request
Dev Box Use Azure VM Image Builder ...dev-box/how-to-customize-devbox-azure-image-builder.md
High Priority View Details →
Scanned: 2026-01-11 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 is heavily biased toward Windows and PowerShell usage. All code examples use Azure PowerShell, with no Azure CLI or Bash alternatives provided. Tool installation instructions reference only Windows, and all image customization steps use Windows-specific tools (Chocolatey, PowerShell). The image template is for Windows 11, and there is no mention of Linux images, Linux tools, or cross-platform usage. Linux users are left without guidance or parity.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell commands.
  • Include instructions for installing Azure CLI and PowerShell on Linux and macOS.
  • Add examples for creating and customizing Linux VM images, including using Linux package managers (e.g., apt, yum) in the image builder template.
  • Mention cross-platform compatibility and clarify which steps are Windows-specific.
  • Ensure documentation sections are not Windows-first; present Linux and Windows options side by side where possible.
GitHub Create Pull Request
Dev Box Configure Intune Endpoint Privilege Management ...n/articles/dev-box/how-to-elevate-privilege-dev-box.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example πŸ”§ Windows Tools
Summary
The documentation is heavily focused on Windows environments, specifically Windows 10/11 dev boxes. All examples, prerequisites, and procedures reference Windows tools, patterns, and UI elements. There is no mention of Linux or cross-platform dev boxes, nor are there examples or guidance for configuring Endpoint Privilege Management on non-Windows systems.
Recommendations
  • Clarify in the introduction and prerequisites whether Endpoint Privilege Management is Windows-only, or provide guidance for Linux/macOS dev boxes if supported.
  • Add equivalent procedures or notes for Linux/macOS environments, including any alternative privilege management solutions or integration points.
  • Include examples and screenshots for non-Windows platforms if supported, or explicitly state platform limitations.
  • Mention Linux/macOS tools or patterns where relevant, such as sudo, polkit, or other privilege elevation mechanisms.
  • If Endpoint Privilege Management is not available for Linux/macOS, provide links to recommended best practices or third-party solutions for those platforms.
GitHub Create Pull Request
Dev Box Configure a user Customization File for Your Dev Box ...ticles/dev-box/how-to-configure-user-customizations.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
πŸ”§ Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by focusing on Windows-specific tools (WinGet, PowerShell), referencing Windows environments and configuration patterns, and omitting Linux equivalents or examples. The only configuration example provided uses WinGet, which is exclusive to Windows. There is no mention of Linux package managers, shell scripts, or how to customize dev boxes for Linux environments. The prerequisites and workflow assume a Windows-centric development experience.
Recommendations
  • Add examples of customization files that use Linux tools (e.g., apt, yum, shell scripts) alongside WinGet examples.
  • Explicitly state whether Dev Box supports Linux-based dev boxes and, if so, provide instructions for customizing those environments.
  • Include references to Linux package managers and scripting languages (e.g., Bash) in the customization workflow.
  • Clarify any platform-specific limitations or features, so users know if certain steps/tools are Windows-only.
  • Balance the documentation by presenting Linux customization options before or alongside Windows options, rather than exclusively or first referencing Windows tools.
GitHub Create Pull Request
Dev Box Use Customizations to Connect to Azure Resources or Clone Private Repositories ...x/how-to-customizations-connect-resource-repository.md
High Priority View Details →
Scanned: 2026-01-11 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 exclusively providing examples and instructions using Windows-centric tools, patterns, and file paths. All YAML customization examples reference Windows images (e.g., Visual Studio on Windows 11), use Windows file paths (C:\workspaces), and rely on Windows-specific package managers (winget) and scripting environments (PowerShell). There are no equivalent examples or guidance for Linux-based dev boxes, nor are Linux tools or shell environments (such as Bash) mentioned.
Recommendations
  • Provide parallel examples for Linux-based dev boxes, including YAML snippets referencing Linux images and using Linux file paths (e.g., /home/workspaces).
  • Include instructions and examples using Bash or shell scripts instead of only PowerShell.
  • Mention and demonstrate installation of Azure CLI via Linux package managers (e.g., apt, yum) in addition to winget.
  • Clarify which features and workflows are supported on Linux dev boxes, and note any limitations.
  • Add screenshots or references to Linux environments where relevant.
  • Ensure that documentation does not assume Windows as the default platform, and present Linux options alongside Windows options.
GitHub Create Pull Request
Dev Box Configure Visual Studio caches for your dev box image ...ticles/dev-box/how-to-generate-visual-studio-caches.md
High Priority View Details →
Scanned: 2026-01-11 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 strong Windows bias by exclusively providing PowerShell and Windows-centric command examples (such as using 'devenv' and PowerShell syntax), referencing only Visual Studio (a Windows-first IDE), and omitting any Linux or cross-platform alternatives for cache generation or dev box configuration. The instructions and tooling are tailored to Windows environments, with no mention of Linux equivalents or how to achieve similar results on non-Windows dev boxes.
Recommendations
  • Provide equivalent cache generation instructions for Visual Studio Code or other cross-platform IDEs.
  • Include Linux shell (bash) examples for repository cloning and cache generation steps.
  • Clarify whether the process is supported only on Windows-based dev boxes, and if so, explicitly state this limitation.
  • If possible, mention or link to Linux-compatible tools or workflows for similar developer experience optimization.
  • Add a section comparing Windows and Linux dev box setup processes, highlighting any differences and parity gaps.
GitHub Create Pull Request
Dev Box Troubleshoot known dev box issues ...box/how-to-troubleshoot-remote-desktop-connectivity.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 strong Windows bias. All troubleshooting examples, tools, and error codes are specific to Windows environments, with exclusive references to Windows features (Windows App, Windows Hello, Hyper-V, Windows Update, Windows Insider builds, Windows-specific error codes, and PowerShell/certutil commands). There are no Linux or cross-platform troubleshooting steps, nor are Linux equivalents mentioned for remote connectivity, authentication, or virtualization issues.
Recommendations
  • Add troubleshooting steps and examples for Linux client devices, including how to connect to dev boxes from Linux and common issues encountered.
  • Include Linux equivalents for remote desktop tools (e.g., Remmina, rdesktop, xfreerdp) and authentication methods.
  • Document how to resolve connectivity, sign-in, and performance issues on Linux-based dev boxes or clients.
  • Provide parity for virtualization troubleshooting, such as guidance for nested virtualization or CPU profiling on Linux.
  • Mention Linux-specific error codes, logs, and diagnostic commands where relevant.
  • Ensure that all instructions and recommendations are platform-agnostic or clearly indicate platform-specific steps.
GitHub Create Pull Request
Dev Box Use modular scripts and files in Dev Box customizations ...les/dev-box/includes/customizations-modular-scripts.md
High Priority View Details →
Scanned: 2026-01-11 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 strong Windows bias by exclusively referencing Windows-centric tools and scripting languages (PowerShell, DSC, WinGet) and providing only Windows file paths and examples. There are no Linux shell script examples, nor any mention of Linux-compatible tools or configuration patterns. The catalog structure and usage instructions are described solely in the context of Windows environments.
Recommendations
  • Include examples using Bash scripts, shell scripts, or Linux configuration files alongside PowerShell and DSC.
  • Mention and demonstrate Linux-compatible tools such as apt, yum, or other package managers in addition to WinGet.
  • Provide Linux file path examples and clarify cross-platform support for catalog structure and task execution.
  • Explicitly state platform compatibility and limitations, and offer guidance for customizing Dev Box images for Linux environments.
  • Balance the order of examples so that Linux and Windows are presented with equal prominence.
GitHub Create Pull Request
Dev Box Configure Microsoft Dev Box with an ARM template ...s/dev-box/quickstart-configure-dev-box-arm-template.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias towards Windows environments by providing only Azure PowerShell/Cloud Shell deployment instructions, with no Linux shell (bash) or cross-platform CLI examples. The main deployment script is written in PowerShell, and the workflow assumes familiarity with Windows-centric tools and patterns. Although Azure CLI is briefly mentioned, no concrete Linux/bash example is provided, and PowerShell is presented as the primary method.
Recommendations
  • Add equivalent deployment instructions using Azure CLI in bash, suitable for Linux and macOS users.
  • Provide explicit bash script examples alongside PowerShell, especially for steps involving user input and resource creation.
  • Reorder or parallelize instructions so that both Windows (PowerShell) and Linux/macOS (bash/CLI) users see their preferred environment represented equally.
  • Clarify that Azure Cloud Shell supports both bash and PowerShell, and show how to select and use bash.
  • Where possible, avoid Windows-specific terminology or explain cross-platform alternatives.
GitHub Create Pull Request
Dev Box Reference: imagedefinition.yaml and task.yaml Files ...n/articles/dev-box/reference-dev-box-customizations.md
High Priority View Details →
Scanned: 2026-01-11 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 is heavily biased toward Windows environments. All examples use Windows-specific tools (PowerShell, WinGet), and there are no references to Linux equivalents or cross-platform scripting options. The built-in tasks and sample YAMLs exclusively mention Windows images and commands, with no mention of Linux images, Bash, or package managers like apt or yum. The documentation assumes Windows as the default and does not provide parity for Linux users.
Recommendations
  • Add examples using Linux base images and show how to specify them in the YAML files.
  • Include built-in tasks for Bash or shell scripts, and provide sample YAMLs for these.
  • Mention Linux package managers (apt, yum, dnf) alongside WinGet, and show how to install packages on Linux dev boxes.
  • Clarify which features/tasks are Windows-only and which are cross-platform.
  • Provide guidance and examples for customizing Linux dev boxes, including relevant schema attributes and task definitions.
  • Ensure that documentation sections do not assume Windows as the default; present Windows and Linux options side by side where possible.
GitHub Create Pull Request
Dev Box Troubleshoot connectivity issues .../dev-box/how-to-resolve-dev-box-connectivity-issues.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First πŸ”§ Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. Troubleshooting steps, examples, and tools are almost exclusively Windows-centric, with frequent references to Windows-specific utilities (e.g., gpedit.msc, Registry Editor, dsregcmd.exe, reg.exe, Task Manager). The Windows App is presented as the primary connection method, and Windows solutions are listed before alternatives. There is a lack of Linux-specific guidance, examples, or parity in troubleshooting steps, despite the mention of a Mac client in one section.
Recommendations
  • Add troubleshooting steps and examples for Linux client devices, including remote desktop connection configuration and relevant tools.
  • Include Linux equivalents for registry and group policy changes, such as modifying configuration files or using dconf/gsettings where applicable.
  • Provide Linux-specific commands for checking connectivity, authentication, and remote desktop session status (e.g., using xfreerdp, rdesktop, or Remmina).
  • Mention and link to Linux-compatible remote desktop clients and describe how to connect to Dev Box from Linux.
  • Ensure that troubleshooting checklists and quick workarounds are not Windows-exclusive and address cross-platform scenarios.
  • Present platform-specific instructions in parallel tabs or sections (Windows, Mac, Linux) for each troubleshooting step.
GitHub Create Pull Request
← Previous Page 2 of 9 Next →