Dev Box

148
Total Pages
122
Linux-Friendly Pages
26
Pages with Bias
17.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

53 issues found
Showing 1-25 of 53 flagged pages
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-12 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, with all examples, procedures, and requirements tailored to Windows dev boxes. There is no mention of Linux or macOS support, nor are there any examples or guidance for non-Windows platforms. The tools, policies, and verification steps are all specific to Windows, and the documentation assumes Windows as the default and only supported OS.
Recommendations
  • Explicitly state platform limitations and whether Endpoint Privilege Management supports Linux/macOS dev boxes.
  • If Linux/macOS support exists or is planned, provide equivalent setup and verification instructions for those platforms.
  • Include a comparison table or section outlining feature parity and differences between Windows and other OSes.
  • If only Windows is supported, clarify this early in the documentation to set expectations for non-Windows users.
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-12 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 is heavily biased towards Windows environments. All example images are Windows-based, and all technical instructions (sysprep, DISM, enabling features, cleanup commands) use Windows-specific tools and PowerShell commands. There are no Linux or macOS examples, nor any mention of how to use non-Windows images or tools. The prerequisites and requirements focus exclusively on Windows OS, making it unclear if Linux images are supported or how to prepare them if they are.
Recommendations
  • Clarify whether Linux images are supported for Dev Box. If not, explicitly state this in the prerequisites.
  • If Linux images are supported, add equivalent instructions for preparing, generalizing, and optimizing Linux VM images (e.g., using waagent, cloud-init, or other Linux tools).
  • Include examples of compatible Linux images from the Azure Marketplace.
  • Provide CLI or shell command alternatives for steps currently shown only with PowerShell or Windows GUI.
  • Add notes or sections for macOS users if relevant, or clarify platform limitations.
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-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 page demonstrates a strong Windows bias by exclusively referencing Windows-centric tools (PowerShell, DSC, WinGet) and providing only Windows file paths and examples. There are no Linux/macOS equivalents or examples, nor is there any mention of how to use modular scripts and files on non-Windows platforms.
Recommendations
  • Add examples using Bash scripts, shell scripts, or other Linux/macOS-compatible scripting languages.
  • Include Linux/macOS file path conventions and explain how modular scripts/files can be referenced and executed on those platforms.
  • Mention and provide examples for Linux-native configuration management tools (e.g., Ansible, shell scripts) in addition to DSC.
  • Clarify platform support and limitations for Dev Box customizations, specifying whether non-Windows images are supported and how to customize them.
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-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 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 Windows-centric customization examples (WinGet, Chocolatey, PowerShell scripts). Linux/macOS equivalents are not mentioned, and examples for customization, device management, and access control are all Windows-focused. There is no guidance for Linux/macOS dev boxes, nor are cross-platform scenarios addressed.
Recommendations
  • Explicitly state platform support for Dev Box (Windows, Linux, macOS) and clarify any limitations.
  • Provide examples for Linux/macOS dev boxes, including customization tasks (e.g., using apt, Homebrew, shell scripts) alongside Windows examples.
  • Discuss device management and conditional access for non-Windows devices, or clarify if Intune/Endpoint Privilege Management is Windows-only.
  • Include cross-platform developer scenarios and guidance for organizations with mixed OS teams.
  • Add troubleshooting and monitoring guidance relevant to Linux/macOS dev boxes if supported.
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-12 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 notable Windows bias: all examples and troubleshooting steps reference Windows-specific tools (WinGet, PowerShell, Windows file paths), and the Dev Box environment is implicitly assumed to be Windows. There are no examples or guidance for Linux/macOS Dev Box images, nor are cross-platform alternatives (e.g., Bash, apt, Homebrew) mentioned. The log file paths and troubleshooting steps are Windows-centric, and PowerShell is the only scripting language discussed for custom tasks.
Recommendations
  • Add explicit guidance and examples for authoring Dev Box image definitions targeting Linux/macOS environments.
  • Include Linux/macOS equivalents for built-in tasks (e.g., apt, yum, Homebrew for package installation; Bash for scripting).
  • Document log file locations and troubleshooting steps for non-Windows Dev Box images.
  • Clarify which built-in tasks and primitives are available on Linux/macOS Dev Box images.
  • Provide cross-platform YAML examples, showing both Windows and Linux/macOS task definitions side by side.
  • Mention any limitations or differences in Dev Box features between Windows and Linux/macOS.
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-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 is heavily biased toward Windows environments, using only PowerShell commands and Windows-specific tools (Hyper-V, New-VMSwitch, New-NetIPAddress, New-NetNat). No Linux or macOS equivalents or examples are provided, and all instructions assume a Windows setup. This creates friction for users on non-Windows platforms, as they cannot follow the steps directly.
Recommendations
  • Add equivalent instructions for Linux environments using KVM/QEMU and libvirt, including how to create virtual switches and NAT networks.
  • Provide CLI examples using Linux tools (e.g., virsh, ip, brctl, nmcli) alongside PowerShell commands.
  • Clarify platform requirements early in the document and link to Linux/macOS setup guides if available.
  • Include screenshots or configuration dialogs for Linux network settings where appropriate.
  • Explicitly state if the feature is Windows-only, or provide cross-platform alternatives.
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-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 is heavily biased towards Windows and PowerShell. All code examples use Azure PowerShell, with no Azure CLI or Bash alternatives provided. Windows-specific tools and patterns (e.g., Chocolatey, sysprep, Windows image definitions) are used exclusively, and file paths are given in Windows format. There is no guidance for Linux/macOS users, nor are cross-platform instructions or examples present.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell commands.
  • Include instructions for installing Azure CLI on Linux/macOS, and reference the official documentation.
  • Offer Linux/macOS file path examples alongside Windows paths.
  • Discuss alternatives to Chocolatey for Linux (e.g., apt, yum) and how to customize images for non-Windows OSes.
  • Clearly state OS limitations (if only Windows images are supported) at the top of the article.
  • If VM Image Builder supports Linux images, add a parallel Linux-focused example and template.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All troubleshooting steps, examples, and tool references are specific to Windows environments, such as Windows App, Windows Hello, Hyper-V, and Windows-specific commands (e.g., certutil, Set-VMProcessor). There are no Linux or macOS equivalents, examples, or troubleshooting guidance, making it difficult for non-Windows users to follow or resolve issues with dev boxes.
Recommendations
  • Add troubleshooting steps and examples for Linux and macOS clients, including how to connect to dev boxes from these platforms.
  • Mention and provide links to cross-platform remote desktop tools (e.g., Remmina, rdesktop, Microsoft Remote Desktop for macOS).
  • Include Linux/macOS equivalents for commands and configuration steps (e.g., certificate troubleshooting, virtualization settings).
  • Clarify which issues are Windows-specific and provide alternative guidance for Linux/macOS users where possible.
  • Reorder examples so that cross-platform or Linux/macOS steps are presented alongside or before Windows-specific instructions.
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-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 is heavily biased toward Windows environments, specifically focusing on Visual Studio and Microsoft Dev Box, which are Windows-centric. All example commands for generating solution caches use PowerShell and Windows tools (devenv.exe), with no mention of Linux/macOS equivalents or alternatives. The instructions assume the use of Windows-based automation and do not provide guidance for cross-platform scenarios.
Recommendations
  • Clarify early in the documentation that the described process is Windows-specific, and note any platform limitations.
  • If possible, provide alternative instructions or mention limitations for Linux/macOS users (e.g., using VS Code, cross-platform build tools, or alternative caching strategies).
  • Include a section that explicitly addresses platform support and parity, outlining what is and is not possible on non-Windows systems.
  • If Visual Studio caches cannot be generated on Linux/macOS, suggest workarounds or related optimizations for those platforms.
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-12 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 is heavily Windows-centric, with troubleshooting steps, tools, and examples almost exclusively focused on Windows environments. Windows-specific tools (such as the Windows App, Group Policy Editor, Registry Editor, and Windows command-line utilities) are referenced throughout, often without Linux equivalents or alternatives. Mac is mentioned briefly in one section, but Linux is not addressed at all, leaving Linux users without guidance for critical troubleshooting steps.
Recommendations
  • Add explicit troubleshooting steps and examples for Linux clients, including how to connect to dev boxes using supported Linux RDP clients (e.g., FreeRDP, Remmina) and how to adjust TCP/UDP settings.
  • Provide Linux equivalents for Windows-specific tools and commands, such as alternatives to Group Policy Editor and Registry Editor for configuring remote desktop settings.
  • Include Linux-specific troubleshooting checklists and guidance for common connectivity issues, such as dealing with network configuration, authentication, and remote desktop session management.
  • Ensure parity in example ordering: present Windows, macOS, and Linux instructions side-by-side or in tabs, rather than Windows-first or Windows-only.
  • Reference cross-platform remote desktop clients and provide links to their documentation.
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-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 is heavily focused on Windows-specific tooling and patterns, with all examples and built-in tasks centered around PowerShell and WinGet, both of which are Windows-only. There are no references to Linux/macOS equivalents (such as Bash, apt, or Homebrew), nor are there examples or guidance for customizing non-Windows Dev Box environments. The schema and task definitions presume Windows as the default, and Linux/macOS users are left without clear instructions or parity.
Recommendations
  • Add examples and schema options for Linux/macOS environments, such as Bash scripts or other shell types.
  • Introduce built-in tasks for common Linux/macOS package managers (e.g., apt, yum, Homebrew) alongside WinGet.
  • Clearly document how to customize Dev Box environments based on the underlying OS, including conditional logic or OS-specific task definitions.
  • Provide sample task.yaml and devbox.yaml files for Linux/macOS scenarios.
  • Explicitly state OS requirements and limitations for each built-in task.
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 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 strong Windows bias: all examples use Windows-specific tools (PowerShell, DSC, WinGet), file paths are Windows-style, and there are no Linux/macOS equivalents or examples. The catalog structure and scripting references are exclusively Windows-oriented, with no mention of Bash, shell scripts, or Linux configuration management tools.
Recommendations
  • Add equivalent examples for Linux/macOS, such as Bash scripts, shell configuration files, or Ansible playbooks.
  • Include Linux-style file paths and clarify cross-platform support for Dev Box customizations.
  • Document how to run modular scripts or configuration tasks on Linux/macOS dev boxes, if supported.
  • Mention and provide examples for Linux package managers (e.g., apt, yum) and scripting tools.
  • Explicitly state platform limitations if Dev Box customizations are Windows-only.
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 06:20
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 towards Windows and PowerShell. All setup, configuration, and usage examples use Azure PowerShell, with no Linux/macOS shell or Azure CLI equivalents provided. Windows-specific tools and patterns (e.g., Chocolatey, sysprep, Windows image sources) are used exclusively, and file paths are given in Windows format. The documentation does not mention or demonstrate how to perform these tasks on Linux or macOS, nor does it provide parity for non-Windows users.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands, with Linux/macOS shell syntax.
  • Include instructions for installing Azure CLI and PowerShell on Linux/macOS, not just Windows.
  • Offer examples of customizing Linux images (e.g., using apt or yum instead of Chocolatey).
  • Use cross-platform file path examples or clarify platform-specific differences.
  • Explicitly state platform requirements and alternatives for non-Windows users.
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 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with exclusive references to Windows tools (WinGet, PowerShell), Windows file paths, and Windows-specific troubleshooting steps. All examples and troubleshooting guidance assume a Windows OS, with no mention of Linux/macOS equivalents or alternatives. This creates friction for users on non-Windows platforms, who may not be able to follow the instructions or complete tasks as described.
Recommendations
  • Provide Linux/macOS equivalents for all major examples, especially for package installation and scripting (e.g., use apt, yum, or Homebrew alongside WinGet).
  • Include troubleshooting steps and log locations for Linux/macOS environments.
  • Clarify which Dev Box features and CLI commands are cross-platform, and note any platform-specific limitations.
  • Add examples using Bash or shell scripts in addition to PowerShell.
  • Explicitly state OS requirements and provide guidance for users working from non-Windows hosts.
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 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily Windows-centric, with all image requirements, examples, and tooling focused exclusively on Windows OS and Windows-specific tools (e.g., PowerShell, DISM, defrag, chkdsk). There are no examples or guidance for Linux or macOS images, nor any mention of how non-Windows users might interact with the Azure Compute Gallery or Dev Box. All command-line examples use Windows tools, and the prerequisites and supported images are strictly Windows-based.
Recommendations
  • Explicitly state that only Windows images are supported, if that is a product limitation. If Linux images are supported, add equivalent Linux image requirements and examples.
  • Provide Linux/macOS equivalents for image preparation steps (e.g., sysprep alternatives, disk cleanup commands, virtualization settings).
  • Include CLI examples using Bash/Azure CLI for Linux/macOS users where possible, not just PowerShell.
  • Clarify whether Dev Box supports Linux/macOS images, and if not, mention this limitation early in the documentation.
  • If future support for Linux/macOS images is planned, add a note or roadmap link.
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 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 Windows-centric tools and commands (PowerShell, Hyper-V), provides only Windows examples, and references Windows UI patterns (Network Connections dialog). There are no Linux/macOS equivalents or instructions, making it difficult or impossible for non-Windows users to follow the guide.
Recommendations
  • Add equivalent instructions for Linux (e.g., using KVM/QEMU, libvirt, or VirtualBox) and macOS (e.g., using Parallels or VMware Fusion).
  • Provide command-line examples for Linux (e.g., ip, brctl, virsh) to create virtual switches and configure NAT.
  • Include screenshots or UI navigation steps for Linux and macOS network configuration dialogs.
  • Clearly state platform limitations and provide links to cross-platform virtualization resources.
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 06:20
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 referencing Windows-specific tools, OS versions, and UI patterns. There are no mentions of Linux or macOS support, nor any guidance for non-Windows dev boxes. The instructions and screenshots are exclusively for Windows, and the Endpoint Privilege Management feature appears to be designed for Windows only.
Recommendations
  • Explicitly state in the prerequisites and introduction whether Endpoint Privilege Management is Windows-only, and clarify support for Linux/macOS dev boxes.
  • If Linux/macOS support exists or is planned, provide equivalent steps, examples, and screenshots for those platforms.
  • If the feature is Windows-only, add guidance or links for privilege management on Linux/macOS dev boxes, or recommend alternative solutions.
  • Consider including a comparison table of supported OSes and their privilege management capabilities.
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 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 is heavily focused on Windows environments, specifically Visual Studio and PowerShell commands. All code examples for generating solution caches use Windows-only tooling (devenv.exe and PowerShell), with no mention of Linux/macOS equivalents or alternatives. The instructions assume the use of Microsoft Dev Box, which is a Windows-based service, and do not provide guidance for cross-platform scenarios or non-Windows development environments.
Recommendations
  • Explicitly state that the instructions are Windows-specific and clarify platform requirements early in the documentation.
  • If possible, provide guidance or alternatives for Linux/macOS users, such as using VS Code or cross-platform build tools.
  • Include examples or notes for generating caches or optimizing Git performance on Linux/macOS environments, if supported.
  • Reorder sections or add headings to make platform dependencies clear, and avoid assuming PowerShell or Windows tools as the default.
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 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. Troubleshooting steps, tools, and examples are almost exclusively Windows-centric, with frequent references to Windows-specific utilities (e.g., Group Policy Editor, Registry Editor, Windows App, dsregcmd.exe, reg.exe, Task Manager). Mac is mentioned only once, and there are no Linux-specific instructions or parity for Linux users. Critical troubleshooting actions (such as registry edits, group policy changes, and process termination) are described only for Windows, leaving Linux users without guidance.
Recommendations
  • Add Linux-specific troubleshooting steps for remote connectivity, authentication, and network configuration.
  • Include examples for Linux remote desktop clients (e.g., xfreerdp, rdesktop, Remmina) and how to configure TCP/UDP settings.
  • Provide equivalent commands for process management, network diagnostics, and device registration on Linux (e.g., using systemctl, ps, netstat, nmcli, etc.).
  • Mention Linux prerequisites and supported tools for connecting to dev boxes.
  • Ensure that troubleshooting checklists and workflows are not Windows-exclusive and offer parallel guidance for Linux/macOS users.
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 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation is heavily Windows-centric, with troubleshooting steps, examples, and tool references almost exclusively focused on Windows environments. Windows-specific tools (Windows App, Windows Hello, Hyper-V, certutil, Teams VDI features) are mentioned without Linux/macOS equivalents or alternatives. No Linux/macOS troubleshooting steps or examples are provided, and Windows terminology and patterns are used throughout.
Recommendations
  • Add troubleshooting steps and examples for Linux and macOS clients, including connection issues, sign-in problems, and performance troubleshooting.
  • Mention cross-platform remote desktop clients (such as Microsoft Remote Desktop for macOS/Linux, or open-source alternatives) and provide installation links.
  • Provide Linux/macOS equivalents for commands (e.g., certutil alternatives, how to manage certificates or troubleshoot sign-in issues on non-Windows clients).
  • Clarify which issues are Windows-specific and which apply to all platforms.
  • Include guidance for Teams and other apps on Linux/macOS dev boxes, if supported.
  • Reorder examples so that Windows, Linux, and macOS are treated equally, or explicitly state platform applicability.
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 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 is heavily focused on Windows-specific tooling and patterns. All examples use Windows images, PowerShell, and WinGet, with no mention of Linux/macOS equivalents or cross-platform scripting. The schema and built-in tasks are described only for Windows environments, and PowerShell is the only scripting language referenced for task authoring.
Recommendations
  • Add examples for Linux-based images and show how to customize them using shell scripts (e.g., Bash) or other cross-platform tools.
  • Document built-in tasks or patterns for Linux/macOS environments, such as support for Bash, apt, yum, or Homebrew.
  • Clarify whether non-Windows images and customization tasks are supported, and if so, provide parity in schema and example coverage.
  • Present examples for both Windows and Linux/macOS environments, or explicitly state platform limitations.
  • If PowerShell is the only supported scripting language, make this clear and provide guidance for Linux users (e.g., PowerShell Core on Linux).
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
Medium Priority View Details →
Scanned: 2026-01-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page provides YAML customization examples that consistently use Windows paths (e.g., C:\workspaces), references Windows base images, and demonstrates automation tasks using PowerShell and the Windows-specific winget package manager. There are no Linux/macOS equivalent examples, and Windows tools/patterns are presented exclusively. This creates friction for Linux/macOS users who may wish to use Dev Box customizations in non-Windows environments.
Recommendations
  • Add parallel examples using Linux/macOS paths (e.g., /home/dev/workspaces) and base images, where supported.
  • Provide sample tasks using bash or shell scripts instead of PowerShell, and use cross-platform package managers (e.g., apt, yum, brew) for installing CLI tools.
  • Clarify which features are Windows-only and which are cross-platform, so users know when Linux/macOS is supported.
  • If Dev Box customizations can be used with Linux images, include explicit Linux/macOS usage scenarios and YAML samples.
GitHub Create Pull Request
Dev Box Stop Dev Boxes Automatically When User Disconnects ...rticles/dev-box/how-to-configure-stop-on-disconnect.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses on stopping Dev Boxes when users disconnect from RDP sessions, a Windows-specific protocol. There is no mention of Linux/macOS remote access methods (e.g., SSH, VNC), nor any examples or guidance for non-Windows environments. The instructions and terminology are tailored exclusively to Windows users.
Recommendations
  • Clarify whether stop-on-disconnect applies to non-Windows Dev Boxes and remote access methods such as SSH or VNC.
  • Provide examples or notes for Linux/macOS users, including how disconnects are detected and handled for those platforms.
  • Explicitly state platform limitations if the feature is Windows-only, or update the documentation to cover Linux/macOS parity if supported.
  • Include references to Linux/macOS remote access patterns where relevant.
GitHub Create Pull Request
Dev Box Roadmap for Microsoft Dev Box ...ure-docs/blob/main/articles/dev-box/dev-box-roadmap.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 Missing Linux Example
Summary
The documentation page for Microsoft Dev Box roadmap exhibits a moderate Windows bias. It references Windows-specific tools (PowerShell, Winget) as primitives for customization and debugging, without mentioning Linux/macOS equivalents. There are no examples or references to Linux-native configuration, scripting, or package management tools. The overall language and feature set are oriented toward Windows environments, with only a brief mention of WSL (Windows Subsystem for Linux) as a way to access Linux environments, rather than supporting Linux/macOS as first-class platforms.
Recommendations
  • Include examples and workflows using Linux-native tools (e.g., Bash, apt, yum) alongside PowerShell and Winget.
  • Explicitly state support for Linux/macOS Dev Box images and provide guidance for customizing and managing these environments.
  • Add parity in CLI and VS Code extension documentation for Linux/macOS users, including troubleshooting and debugging steps.
  • Highlight cross-platform compatibility in feature descriptions, and avoid assuming Windows as the default environment.
GitHub Create Pull Request
Dev Box Grant access to Microsoft Dev Box .../main/articles/dev-box/how-to-manage-dev-box-access.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes role assignment and access management using the Azure portal GUI, which is most commonly accessed from Windows environments. There are no examples or instructions for performing these tasks via cross-platform command-line tools such as Azure CLI, PowerShell, or REST API. No mention is made of Linux/macOS workflows or tools, and all screenshots and step-by-step instructions assume use of the Azure portal, which is often presented from a Windows perspective.
Recommendations
  • Add equivalent instructions for assigning roles using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include PowerShell examples, but ensure Azure CLI is presented first or alongside for parity.
  • Mention REST API methods for role assignment for automation and non-GUI workflows.
  • Explicitly state that the Azure portal is accessible from any OS/browser, and clarify that the instructions are not Windows-specific.
  • Add notes or sections for Linux/macOS users, highlighting any OS-agnostic steps or differences.
GitHub Create Pull Request
← Previous Page 1 of 3 Next →