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 101-125 of 217 flagged pages
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-customize-devbox-azure-image-builder.md ...dev-box/how-to-customize-devbox-azure-image-builder.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell. All setup, configuration, and usage instructions are provided exclusively with Azure PowerShell commands, with no Azure CLI or Bash equivalents. The prerequisites and installation instructions reference only Windows and PowerShell, and tools like Chocolatey (Windows-specific) are used in customization steps. There are no examples or guidance for Linux users, and Windows terminology and tools are prioritized throughout.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell commands, especially for setup, resource creation, and deployment steps.
  • Include instructions for installing Azure CLI and using it on Linux and macOS, not just PowerShell on Windows.
  • Offer alternative customization steps using Linux-native tools (e.g., apt, yum) and show how to build Linux-based images.
  • Add a section or callouts for Linux users, clarifying any OS-specific requirements or differences.
  • Mention cross-platform compatibility in prerequisites and tool selection, and avoid assuming Windows as the default environment.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-connect-dev-box-virtual-switch.md ...icles/dev-box/how-to-connect-dev-box-virtual-switch.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows environments, using only PowerShell commands and Windows-specific tools (Hyper-V, New-VMSwitch, New-NetIPAddress, New-NetNat). All examples and instructions assume a Windows OS, with no mention of Linux equivalents (such as KVM, libvirt, or Linux networking commands). The configuration steps and screenshots are Windows-centric, and there is no guidance for users on Linux or other platforms.
Recommendations
  • Add equivalent instructions for Linux environments, such as using KVM/QEMU, libvirt, or VirtualBox to create virtual switches and NAT networks.
  • Provide Linux command-line examples (e.g., ip, brctl, virsh, nmcli) for creating and configuring virtual switches and NAT.
  • Include notes on cross-platform compatibility and limitations, clarifying which features are Windows-only and how Linux users can achieve similar outcomes.
  • Add screenshots or step-by-step guides for configuring network settings in popular Linux desktop environments.
  • Consider reordering sections or providing parallel instructions so that Linux users do not feel secondary to Windows users.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-dev-box-deployment-guide.md ...n/articles/dev-box/concept-dev-box-deployment-guide.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation for Microsoft Dev Box deployment is heavily oriented toward Windows environments. It references Windows-specific management tools (Intune, Endpoint Privilege Management), Windows device management, and Windows-centric customization tools (WinGet, Chocolatey, PowerShell). There are no examples or guidance for Linux-based dev boxes, nor mention of Linux equivalents for device management, customization, or access control. The documentation assumes Windows as the default platform for dev boxes and omits Linux scenarios entirely.
Recommendations
  • Add explicit guidance and examples for deploying and managing Linux-based dev boxes, including supported Linux distributions.
  • Include Linux equivalents for customization tasks (e.g., apt, yum, shell scripts) alongside WinGet, Chocolatey, and PowerShell.
  • Clarify which features (Intune, Endpoint Privilege Management, device configuration profiles) are Windows-only and provide alternatives or limitations for Linux dev boxes.
  • Provide sample YAML customization files for Linux environments.
  • Mention Linux-specific considerations for networking, access control, and monitoring.
  • Ensure that examples and instructions do not assume Windows as the default, and present Linux options in parallel where supported.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-customizations-connect-resource-repository.md ...x/how-to-customizations-connect-resource-repository.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing all code examples and file paths in Windows-centric formats (e.g., C:\workspaces), using Windows-specific tools (winget, PowerShell), and referencing Windows base images. There are no Linux equivalents or examples, and Linux tools or patterns are not mentioned. The documentation assumes a Windows environment for Dev Box customization and does not address how to perform similar tasks on Linux-based Dev Boxes.
Recommendations
  • Provide parallel examples for Linux environments, including file paths (e.g., /home/devuser/workspaces) and shell commands (bash, sh).
  • Include Linux base image references in YAML examples.
  • Show how to install Azure CLI on Linux (e.g., using apt, yum, or direct download) instead of only winget.
  • Replace or supplement PowerShell scripts with bash equivalents for authentication and resource access.
  • Explicitly mention cross-platform support and note any limitations or differences between Windows and Linux Dev Boxes.
  • Add a section comparing customization workflows for Windows and Linux environments.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/reference-dev-box-customizations.md ...n/articles/dev-box/reference-dev-box-customizations.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows-specific tools and workflows. All examples use Windows images, PowerShell, and WinGet, with no mention of Linux equivalents or cross-platform support. The built-in tasks and customization examples are exclusively Windows-centric, and there is no guidance for Linux environments or shell scripting alternatives.
Recommendations
  • Add examples using Linux images and show how to customize them in devbox.yaml and task.yaml files.
  • Include built-in tasks for Bash or other Linux shell scripting, with example parameters and usage.
  • Document Linux package managers (e.g., apt, yum) as alternatives to WinGet, with sample tasks.
  • Present Windows and Linux examples side-by-side or in parallel sections to ensure parity.
  • Clarify platform compatibility for each feature and task, specifying which are Windows-only and which are cross-platform.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-authoring-troubleshooting-guide-team-customizations.md ...pt-authoring-troubleshooting-guide-team-customizations.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All examples and troubleshooting steps assume a Windows environment, with exclusive use of Windows-specific tools such as PowerShell, WinGet, and Windows file paths (e.g., C:\ProgramData). There are no examples or guidance for Linux-based Dev Box images, nor mention of Linux equivalents for tasks like package installation, scripting, or log file locations. The CLI and YAML examples exclusively reference Windows primitives and patterns, and troubleshooting is centered around Windows error messages and log directories.
Recommendations
  • Include Linux-specific examples for common tasks, such as using Bash scripts, apt/yum/dnf for package installation, and Linux file paths.
  • Document how to author and troubleshoot Dev Box images based on Linux distributions, including context placement, available primitives, and log file locations.
  • Provide parity in troubleshooting guidance for Linux environments, such as where to find logs and how to interpret errors.
  • Mention Linux equivalents for built-in tasks (e.g., ~/bash, ~/apt) and clarify which primitives are available for Linux Dev Boxes.
  • Add notes or tables comparing Windows and Linux workflows, highlighting differences and best practices for each platform.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-what-are-dev-box-customizations.md ...les/dev-box/concept-what-are-dev-box-customizations.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias by exclusively referencing PowerShell scripts and WinGet tasks as the primary mechanisms for Dev Box customizations. There are no examples or mentions of Linux shell scripting, Linux package managers, or cross-platform tooling. Windows-centric tools and patterns are presented as the default and recommended approach, with no guidance for Linux-based Dev Boxes or parity for non-Windows environments.
Recommendations
  • Add examples and guidance for Linux-based Dev Boxes, including the use of Bash scripts and Linux package managers (e.g., apt, yum, dnf, zypper) in customization tasks.
  • Explicitly mention support for Linux Dev Boxes, if available, and provide documentation on how to author cross-platform or Linux-specific customization files.
  • Include sample YAML customization files that demonstrate both Windows (PowerShell/WinGet) and Linux (Bash/apt) tasks.
  • Clarify whether Dev Box supports Linux images and, if so, provide parity in tooling and task definitions for Linux environments.
  • Avoid recommending Windows tools (PowerShell, WinGet) as the default without mentioning alternatives for Linux users.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-customization-tasks.md ...ticles/dev-box/how-to-configure-customization-tasks.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias by exclusively referencing PowerShell scripts and WinGet for task automation and software installation. All examples and instructions center on Windows-native tools, with no mention of Linux shell scripts, package managers (e.g., apt, yum), or cross-platform scripting approaches. The catalog structure and quickstart examples are also Windows-centric, and Linux equivalents are neither mentioned nor provided.
Recommendations
  • Include examples of tasks using Linux shell scripts (e.g., Bash) alongside PowerShell.
  • Document how to install software using common Linux package managers (apt, yum, zypper) in tasks.
  • Clarify whether Dev Box supports Linux-based images and, if so, provide guidance for Linux customizations.
  • Present cross-platform scripting patterns and highlight any platform-specific requirements or limitations.
  • Update quickstart catalog to include Linux-focused tasks and examples.
  • Explicitly state platform support and limitations at the beginning of the documentation.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/dev-box-roadmap.md ...ure-docs/blob/main/articles/dev-box/dev-box-roadmap.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for Microsoft Dev Box exhibits a Windows bias by referencing Windows-specific tools (PowerShell, Winget), focusing on Windows-centric workflows and technologies (RDP, Visual Studio, Windows), and omitting explicit Linux or cross-platform examples. Linux equivalents or workflows are not mentioned, and Windows tools are referenced first and exclusively in customization and connectivity sections.
Recommendations
  • Include examples and workflows for Linux-based Dev Box environments, such as using Bash scripts, apt/yum package managers, and Linux desktop environments.
  • Mention cross-platform tools and patterns (e.g., VS Code extensions, CLI usage on Linux/macOS) alongside Windows-specific ones.
  • Provide parity in documentation for Linux onboarding, customization, and troubleshooting, including references to WSL, SSH, and Linux-native developer tools.
  • Explicitly state support for Linux and macOS developer scenarios where applicable, and link to relevant guides.
  • Balance references to Windows tools (PowerShell, Winget, RDP) with Linux alternatives (Bash, apt/yum, SSH, X11/VNC).
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-troubleshoot-repair-dev-box.md ...articles/dev-box/how-to-troubleshoot-repair-dev-box.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses exclusively on troubleshooting Remote Desktop Connectivity (RDC/RDP) issues for dev boxes, referencing Windows-specific tools and concepts (RDP, Windows Guest OS readiness) without mentioning Linux equivalents (such as SSH or Linux guest readiness). All examples, checks, and screenshots are Windows-centric, and there are no instructions or troubleshooting steps for Linux-based dev boxes or connectivity methods.
Recommendations
  • Add troubleshooting steps and examples for Linux-based dev boxes, including SSH connectivity issues.
  • Include checks for Linux guest OS readiness alongside Windows checks.
  • Provide parity in screenshots and instructions for both Windows and Linux dev box environments.
  • Mention and explain Linux connectivity tools (e.g., SSH, VNC) where appropriate.
  • Clarify whether the Troubleshoot & Repair tool supports Linux dev boxes, and if not, provide alternative guidance.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-azure-compute-gallery.md ...cles/dev-box/how-to-configure-azure-compute-gallery.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All example images are Windows-based (Visual Studio 2019/2022), and image requirements are exclusively for Windows OS (Windows 10/11 Enterprise). Instructions for image preparation rely on Windows-specific tools and commands (Sysprep, DISM, defrag, chkdsk, PowerShell), with no mention of Linux equivalents or support. There are no Linux image examples, requirements, or preparation steps, and the documentation does not address how to use or optimize Linux images for Dev Box.
Recommendations
  • Add explicit guidance and examples for creating and attaching Linux images to Azure Compute Gallery for Dev Box.
  • Include Linux-compatible image requirements and highlight any differences or limitations compared to Windows images.
  • Provide Linux-specific image preparation steps, such as generalizing images (e.g., using waagent or cloud-init), disk cleanup, and optimization commands.
  • Offer CLI or shell command examples for Linux image management, in addition to PowerShell and Windows tools.
  • Clarify whether Dev Box supports Linux images, and if not, state this limitation clearly at the start of the documentation.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-intune-conditional-access-policies.md ...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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by exclusively referencing Windows-specific tools and services (e.g., Windows 365, Microsoft Remote Desktop, Windows Azure Service Management API) and by not providing any examples or guidance for Linux-based access, management, or client tools. All scenarios and app references focus on Windows environments, with no mention of Linux equivalents or cross-platform considerations.
Recommendations
  • Include examples and guidance for accessing Dev Boxes from Linux clients, such as using open-source RDP clients (e.g., FreeRDP, Remmina) or SSH where applicable.
  • Document how Conditional Access policies apply to Linux-based dev boxes or users accessing from Linux endpoints.
  • Add parity in app tables and scenarios by listing Linux-compatible management and connection tools, and clarify any differences in experience or requirements.
  • Provide troubleshooting steps or considerations for Linux users, including authentication, compliance, and device registration in Intune.
  • Explicitly state platform support and limitations for Dev Box access and management, ensuring Linux users are aware of their options.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-conditional-access-dev-tunnels-service.md ...v-box/how-to-conditional-access-dev-tunnels-service.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by requiring PowerShell 7.x as a prerequisite, providing only PowerShell-based command examples, and referencing Windows-specific concepts like Dev Box and GPO. There are no Linux or cross-platform CLI examples, nor any mention of Linux-specific tools or workflows. The instructions and screenshots are tailored to Windows environments, leaving Linux users without guidance.
Recommendations
  • Include Linux-specific prerequisites, such as bash or compatible shell environments.
  • Provide equivalent command-line examples for Linux/macOS (e.g., using bash or sh instead of PowerShell).
  • Clarify whether Dev Tunnels and related policies can be managed from Linux environments, and document any differences.
  • Add screenshots or instructions for Linux users where UI or workflow differs.
  • Mention cross-platform compatibility explicitly and ensure parity in examples and troubleshooting steps.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-elevate-privilege-dev-box.md ...n/articles/dev-box/how-to-elevate-privilege-dev-box.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, with all examples, prerequisites, and procedures tailored exclusively to Windows dev boxes. There is no mention of Linux or cross-platform support, and all tooling, policy configuration, and verification steps assume Windows OS and Windows-specific features (e.g., 'Run with elevated access', 'Program Files' directory).
Recommendations
  • Add explicit statements about platform support, clarifying whether Endpoint Privilege Management is available for Linux dev boxes.
  • If Linux support exists, provide equivalent examples and procedures for configuring privilege management on Linux dev boxes.
  • Include Linux-specific prerequisites, such as supported distributions and required tools.
  • Offer verification steps for Linux, such as checking agent installation paths and privilege elevation mechanisms.
  • If Linux is not supported, clearly state this at the beginning of the documentation to set expectations for cross-platform users.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-dev-box-hibernation.md ...ticles/dev-box/how-to-configure-dev-box-hibernation.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a clear Windows bias. All compatibility and configuration instructions are focused exclusively on Windows OS, with no mention of Linux or cross-platform scenarios. Steps for disabling incompatible features, enabling nested virtualization, and troubleshooting are all Windows-specific. There are no Linux examples, nor is there any discussion of Linux images, tools, or settings. The documentation assumes the use of Windows-based dev boxes and images throughout.
Recommendations
  • Add explicit guidance for Linux-based dev boxes, including supported SKUs and any hibernation limitations.
  • Provide examples for enabling hibernation on Linux images, including relevant Azure CLI flags and image requirements.
  • Discuss any Linux-specific compatibility considerations (e.g., kernel requirements, virtualization settings) for hibernation.
  • Include troubleshooting steps and links for Linux VM hibernation issues.
  • Clarify whether hibernation is supported for non-Windows images and, if not, state this clearly at the top of the documentation.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-resolve-dev-box-connectivity-issues.md .../dev-box/how-to-resolve-dev-box-connectivity-issues.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. Troubleshooting steps, examples, and tools are almost exclusively focused on Windows environments, such as the Windows App, Windows Update, Group Policy Editor, Registry Editor, and Windows-specific command-line utilities (e.g., dsregcmd.exe, reg.exe, gpupdate). Mac is mentioned briefly for one setting, but there are no Linux-specific instructions, examples, or parity in troubleshooting steps. Linux users are not addressed in prerequisites, connection troubleshooting, or configuration guidance.
Recommendations
  • Add explicit troubleshooting steps and examples for Linux clients, including how to connect to Dev Box from Linux (e.g., using open-source RDP clients like Remmina or xfreerdp).
  • Include Linux equivalents for registry and group policy changes, such as configuration file edits or environment variable settings for RDP clients.
  • Provide guidance for checking and updating Linux system packages relevant to remote connectivity (e.g., xrdp, freerdp, network settings).
  • Mention Linux-specific tools and commands for diagnosing network and authentication issues (e.g., nmcli, journalctl, systemctl, netstat, etc.).
  • Ensure all troubleshooting checklists and steps are presented for Windows, Mac, and Linux in parallel, ideally using tabs or sections for each OS.
  • Clarify whether the Dev Box service supports Linux clients and, if so, provide official recommendations for supported RDP clients and configuration.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-team-customizations.md ...ticles/dev-box/how-to-configure-team-customizations.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias. All examples and built-in tasks focus on Windows-centric tools such as PowerShell and WinGet, with no mention of Linux equivalents (e.g., Bash, apt, yum). The only configuration management example uses PowerShell DSC, and the workflow assumes Windows-based environments. There are no Linux-specific instructions, examples, or references to Linux package managers or shell scripting. Windows tools and patterns are mentioned exclusively and are presented first and only.
Recommendations
  • Add examples for Linux-based dev boxes, including tasks using Bash scripts and Linux package managers (apt, yum, dnf, etc.).
  • Document how to use Linux equivalents for configuration management (e.g., Ansible, shell scripts) in image definition files.
  • Clarify whether Dev Box supports Linux images and, if so, provide parity in instructions and examples.
  • Include references to cross-platform tools and workflows, and explicitly state platform limitations if any exist.
  • Present Windows and Linux options side-by-side where possible, rather than focusing solely on Windows.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/monitor-dev-box.md ...ure-docs/blob/main/articles/dev-box/monitor-dev-box.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides detailed instructions and examples for enabling diagnostic logs using Azure PowerShell, which is primarily a Windows-centric tool. There are no equivalent examples for Bash, Azure CLI, or Linux shell environments. The only command-line automation shown is via PowerShell, and there is no mention of Linux-specific tools or cross-platform alternatives. This creates a bias toward Windows users and may hinder Linux users from following automation steps.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands for enabling diagnostic logs, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that Azure CLI can be used on Linux, macOS, and Windows, and provide links to relevant documentation.
  • Where PowerShell is referenced, clarify its availability on Linux and macOS, or suggest alternatives for those platforms.
  • Ensure screenshots and UI instructions do not assume a Windows environment (e.g., avoid references to Windows-only features or UI elements).
  • Consider including a section or note for Linux/macOS users, outlining any platform-specific considerations or differences.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-generate-visual-studio-caches.md ...ticles/dev-box/how-to-generate-visual-studio-caches.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, specifically Microsoft Dev Box and Visual Studio on Windows. All example commands for generating solution caches use PowerShell and Windows-specific tooling (devenv.exe), with no mention of Linux equivalents or cross-platform alternatives. The guidance assumes the use of Windows-based images and tools, and does not provide instructions or examples for Linux-based dev boxes or Visual Studio Code scenarios.
Recommendations
  • Provide equivalent instructions and examples for Linux-based dev box images, including how to precache solutions using cross-platform tools (e.g., dotnet CLI for .NET projects).
  • Include bash or shell script examples alongside PowerShell commands, especially for steps like cloning repositories and running build/cache generation.
  • Clarify whether Visual Studio Code or other cross-platform IDEs can benefit from similar caching, and provide relevant instructions if possible.
  • Explicitly state platform limitations or requirements (e.g., that Visual Studio solution cache generation is only available on Windows), and suggest Linux alternatives where applicable.
  • Consider reordering sections to mention cross-platform options before or alongside Windows-specific instructions to avoid 'windows_first' bias.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-user-customizations.md ...ticles/dev-box/how-to-configure-user-customizations.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools and patterns (WinGet, PowerShell), focusing on configuring Windows environments, and omitting any mention or examples for Linux-based dev boxes. All examples and workflows assume a Windows context, with no guidance for Linux users or parity in tooling.
Recommendations
  • Include examples of customization files and tasks for Linux-based dev boxes, such as installing packages with apt, yum, or other Linux package managers.
  • Document how to use shell scripts (bash/sh) as customization tasks, alongside PowerShell examples.
  • Clarify whether the Dev Box platform supports Linux dev boxes, and if so, provide equivalent steps and screenshots for Linux environments.
  • Mention Linux equivalents to WinGet (such as apt, dnf, zypper, etc.) and provide sample YAML configurations for those.
  • Ensure that prerequisites and setup instructions are not Windows-centric, and add notes for cross-platform compatibility.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-troubleshoot-remote-desktop-connectivity.md ...box/how-to-troubleshoot-remote-desktop-connectivity.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All troubleshooting steps, examples, and referenced tools are specific to Windows environments (e.g., Windows App, Windows Hello, Hyper-V, Windows Update, Windows Insider builds). There are no Linux or cross-platform instructions, nor are Linux tools or equivalents mentioned. The troubleshooting commands and UI navigation (e.g., certutil, Settings > Privacy & security) are Windows-specific, and PowerShell/Windows command-line tools are referenced without Linux alternatives.
Recommendations
  • Add troubleshooting steps and examples for Linux-based dev boxes, if supported.
  • Include Linux equivalents for Windows-specific tools and commands (e.g., provide Linux command-line alternatives for certutil, Hyper-V, etc.).
  • Mention cross-platform remote desktop clients and how to use them with dev boxes.
  • Clarify in the prerequisites and throughout the document whether dev boxes support Linux, and if not, state this explicitly.
  • If Linux is supported, provide parity in troubleshooting for common issues (connectivity, sign-in, performance) on Linux clients.
  • Balance the order of presentation so that Linux and Windows instructions are given equal prominence where both are relevant.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/quickstart-configure-dev-box-arm-template.md ...s/dev-box/quickstart-configure-dev-box-arm-template.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell deployment instructions and examples, with no equivalent Bash or Linux CLI walkthrough. The deployment script and Cloud Shell instructions are PowerShell-centric, and there is no mention or prioritization of Linux tools or workflows. Although Azure CLI is briefly mentioned as an alternative, no concrete Linux/Bash example is given.
Recommendations
  • Add a full Bash/Azure CLI example for deploying the ARM template, including step-by-step instructions and code blocks.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide parity in instructions for both environments.
  • Where PowerShell scripts are shown, offer equivalent Bash/CLI scripts side-by-side or in tabs.
  • Review all references to tools and workflows to ensure Linux users are equally supported and not required to adapt Windows-centric instructions.
  • Consider including screenshots or walkthroughs from Linux environments (e.g., Azure CLI in Bash) to reinforce cross-platform support.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/includes/customizations-modular-scripts.md ...les/dev-box/includes/customizations-modular-scripts.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing Windows-centric tools and scripting languages (PowerShell, DSC, WinGet), providing only Windows file paths and examples, and omitting any mention of Linux equivalents or cross-platform alternatives. The catalog structure and task examples are tailored to Windows environments, with no guidance for Linux users.
Recommendations
  • Include examples using Bash scripts, shell scripts, or other Linux-compatible scripting languages.
  • Reference Linux file paths and demonstrate how modular scripts and files can be used in Linux-based Dev Boxes.
  • Mention Linux configuration management tools (e.g., Ansible, shell scripts) alongside PowerShell and DSC.
  • Clarify whether Dev Box supports Linux images and, if so, provide parity in documentation for Linux customization workflows.
  • Add cross-platform guidance for users who may be working in mixed OS environments.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/quickstart-create-dev-box.md ...lob/main/articles/dev-box/quickstart-create-dev-box.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Windows App as the method for connecting to a Dev Box, with no mention of Linux or cross-platform alternatives. All connection instructions and prerequisites focus on Windows tooling, and there are no examples or guidance for Linux users. The documentation assumes a Windows-centric workflow and omits Linux-specific steps or tools.
Recommendations
  • Add instructions for connecting to a Dev Box from Linux, such as using RDP clients (e.g., Remmina, rdesktop, FreeRDP) or browser-based access.
  • Include Linux-specific prerequisites and installation steps for recommended remote desktop clients.
  • Provide examples and screenshots for Linux users to mirror the Windows App guidance.
  • Clarify cross-platform support and explicitly state which operating systems are supported for connecting to Dev Boxes.
  • If browser-based access is supported, highlight it as a platform-agnostic option and provide details for both Windows and Linux users.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-user-customizations.md ...ticles/dev-box/how-to-configure-user-customizations.md
High Priority View Details →
Scanned: 2025-08-25 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by focusing exclusively on Windows-specific tools (such as WinGet and PowerShell), referencing Windows configuration patterns, and omitting any mention of Linux or cross-platform alternatives. All examples and workflows assume a Windows environment, with no guidance for Linux users or parity in tooling.
Recommendations
  • Include examples of customization files and tasks that are relevant for Linux-based dev boxes, if supported.
  • Mention and provide guidance for Linux package managers (e.g., apt, yum) or scripting (e.g., Bash) where appropriate, alongside or instead of WinGet and PowerShell.
  • Clarify whether user customizations are supported on non-Windows dev boxes, and if not, state this explicitly.
  • If the Dev Box service is Windows-only, add a note at the top of the documentation to set user expectations.
  • Provide parity in documentation structure: for every Windows-specific example or tool, offer a Linux equivalent or explain the limitations.
GitHub Create Pull Request
← Previous Page 5 of 9 Next →