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 51-75 of 217 flagged pages
Dev Box Monitor Microsoft Dev Box and Diagnostic Data Logs ...ure-docs/blob/main/articles/dev-box/monitor-dev-box.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 Tools
Summary
The documentation page provides detailed instructions and examples for enabling diagnostic logs using the Azure portal and Azure PowerShell, but does not include equivalent examples for Linux-friendly tools such as Azure CLI or Bash scripting. The only command-line automation shown is via PowerShell, which is primarily a Windows tool, and there is no mention of Linux-specific workflows or cross-platform alternatives.
Recommendations
  • Add step-by-step instructions and code examples for enabling diagnostic logs using Azure CLI, which is cross-platform and widely used on Linux.
  • Include Bash script examples for automation, especially for users managing Dev Boxes from Linux environments.
  • Explicitly mention that Azure CLI can be used on Windows, Linux, and macOS, and provide links to relevant documentation.
  • Where PowerShell is referenced, clarify its availability on Linux and macOS, or provide CLI alternatives side-by-side.
  • Ensure screenshots and UI references do not assume a Windows environment (e.g., avoid showing only Windows-style UI elements if possible).
GitHub Create Pull Request
Dev Box Quickstart: Create and Access a Dev Box in the Cloud ...lob/main/articles/dev-box/quickstart-create-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 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Windows App as the method to connect to a Dev Box, without mentioning or providing alternatives for Linux users. There are no examples or instructions for connecting from Linux (or macOS), nor are cross-platform remote desktop tools discussed. The documentation assumes the use of Windows-centric tools and patterns, omitting Linux-specific guidance.
Recommendations
  • Add instructions for connecting to a Dev Box from Linux (and macOS), including recommended RDP clients (such as Remmina, FreeRDP, or rdesktop) and any required configuration steps.
  • Explicitly mention cross-platform compatibility in the prerequisites and connection sections, clarifying which operating systems are supported and how to connect from each.
  • Provide example commands or screenshots for Linux users, ensuring parity with the Windows App instructions.
  • If the Windows App is not available on Linux, suggest alternative methods (e.g., using the browser, or open-source RDP clients) and document any limitations or differences in experience.
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-10 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 as a prerequisite, providing only PowerShell-based command examples, and referencing Windows-specific concepts such as Dev Box and GPO. There are no Linux or macOS command-line examples, nor are alternative tools or instructions for non-Windows platforms mentioned. The workflow and terminology are oriented toward Windows environments, leaving Linux users without guidance for equivalent steps.
Recommendations
  • Include Linux and macOS command-line examples (e.g., bash/zsh) alongside PowerShell commands.
  • Clarify whether the Dev Tunnels workflow and conditional access configuration can be performed on Linux/macOS, and document any platform-specific differences.
  • List cross-platform prerequisites (e.g., bash, sh, or terminal) in addition to PowerShell, or note PowerShell's availability on Linux/macOS.
  • Provide guidance for Linux users on managing Dev Tunnels and configuring conditional access, including any relevant tools or commands.
  • Avoid Windows-centric terminology (such as GPO) without explaining or providing Linux equivalents.
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-10 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. All examples and references to scripting and automation use PowerShell and WinGet, which are Windows-specific tools. There is no mention of Linux equivalents (such as Bash, shell scripts, or apt/yum package managers), nor any indication that Dev Box supports or can be customized for Linux environments. The documentation assumes a Windows context throughout, both in terminology and in the tools recommended, with no Linux parity in examples or guidance.
Recommendations
  • Explicitly state whether Dev Box supports Linux-based images and, if so, provide equivalent examples using Bash scripts and Linux package managers (e.g., apt, yum, dnf, zypper).
  • Include documentation and examples for customizing Linux dev boxes, such as using shell scripts or Ansible playbooks.
  • When listing built-in tasks, mention both Windows (PowerShell, WinGet) and Linux (Bash, apt, etc.) options, or clarify if only Windows is supported.
  • Avoid language that assumes PowerShell or WinGet are the only or default options; instead, use more inclusive phrasing like 'PowerShell (for Windows) or Bash (for Linux)'.
  • Add a section or FAQ addressing cross-platform support and customization differences between Windows and Linux dev boxes.
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-10 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 are Windows-based (Windows 10/11, Visual Studio), and all image requirements and optimization steps are specific to Windows OS. Instructions for image preparation use Windows-specific tools and commands (Sysprep, DISM, PowerShell, defrag, chkdsk), with no mention of Linux equivalents or support for Linux images. The documentation does not provide any guidance or examples for configuring or optimizing Linux-based images, nor does it mention Linux compatibility or requirements.
Recommendations
  • Add explicit support statements for Linux images, including any requirements or limitations.
  • Provide Linux-based example images and step-by-step instructions for preparing and optimizing Linux VM images for Azure Compute Gallery and Dev Box.
  • Include Linux-specific commands and tools (e.g., cloud-init, waagent, parted, e2fsck, etc.) for image generalization, disk cleanup, and optimization.
  • Clarify whether Microsoft Dev Box supports Linux images, and if not, state this clearly at the beginning of the documentation.
  • If Linux is supported, add parity in troubleshooting, permissions, and gallery attachment/removal instructions for Linux environments.
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-10 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 demonstrates a Windows-centric bias. Windows tools and patterns (such as PowerShell and Winget) are mentioned exclusively in the context of customization and debugging, with no equivalent Linux or cross-platform examples. The roadmap references Windows, RDP, and Visual Studio as primary development tools, and features like WSL are mentioned only as part of the Windows ecosystem. There are no examples or mentions of Linux-native workflows, tools, or developer experiences, and all examples and features are described from a Windows-first perspective.
Recommendations
  • Add equivalent Linux examples for customization workflows, such as using Bash scripts or Linux package managers (e.g., apt, yum) alongside PowerShell and Winget.
  • Explicitly mention support for Linux-based Dev Box images, if available, and provide guidance for configuring and customizing Linux environments.
  • Include onboarding and management instructions for Linux users, such as SSH access, Linux-specific networking, and monitoring tools.
  • Highlight cross-platform compatibility in developer tooling (e.g., VS Code extensions) and clarify how features apply to both Windows and Linux Dev Boxes.
  • Balance references to Windows tools with Linux alternatives, and avoid assuming Windows as the default environment.
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-10 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 strong Windows bias. All examples and troubleshooting steps reference Windows-specific tools and patterns such as PowerShell, WinGet, and Windows file paths (e.g., C:\ProgramData). There are no Linux equivalents or cross-platform alternatives provided. The CLI and scripting guidance is focused exclusively on Windows environments, and troubleshooting logs are described only for Windows paths. Built-in tasks and examples (~/winget, ~/powershell) are Windows-centric, and there is no mention of Linux package managers, shell scripts, or file system paths.
Recommendations
  • Add Linux-specific examples for authoring, testing, and troubleshooting Dev Box image definitions, including shell script primitives and package managers such as apt, yum, or zypper.
  • Include cross-platform guidance for built-in tasks, showing how to install software and configure environments on Linux Dev Boxes.
  • Document log file locations and troubleshooting steps for Linux environments, using appropriate file paths and tools (e.g., /var/log/devboxagent/customizations).
  • Provide parity for scripting: show how to use Bash or other shell scripts in custom tasks, and discuss escaping/quoting issues relevant to Linux shells.
  • Mention and demonstrate Linux equivalents for tools like WinGet (e.g., apt, dnf, zypper) and PowerShell (e.g., Bash, Python).
  • Clarify which features and primitives are supported on Linux Dev Boxes, and highlight any platform-specific limitations or differences.
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-10 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 exclusively references Windows device management (Intune), Windows-specific configuration profiles, and Windows privilege management. Examples of customization tasks mention Windows-centric tools (WinGet, Chocolatey, PowerShell scripts) without Linux equivalents. There is no mention of Linux VM images, Linux device management, or cross-platform developer scenarios, and all device management and security instructions assume Windows as the target OS.
Recommendations
  • Explicitly mention support for Linux dev boxes, if available, and provide guidance for deploying and managing Linux-based dev boxes.
  • Include examples of customization tasks for Linux, such as using apt, yum, or shell scripts, alongside Windows examples.
  • Clarify whether Microsoft Intune can manage Linux dev boxes, and if not, suggest alternative management solutions for Linux.
  • Provide instructions for creating and managing Linux VM images in Azure Compute Gallery, and note any differences in configuration.
  • Discuss cross-platform developer scenarios (e.g., teams needing both Windows and Linux dev boxes) and how to accommodate them in Dev Box pools and projects.
  • Balance references to Windows tools (WinGet, Chocolatey, PowerShell) with Linux equivalents (apt, yum, bash scripts) in setup catalogs and quick start guides.
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-10 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 such as 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, with no Linux equivalents or parity in examples, making the documentation less accessible for teams using Linux-based development environments.
Recommendations
  • Include examples of tasks using Bash scripts and Linux shell commands alongside PowerShell examples.
  • Mention and provide guidance for using Linux package managers (e.g., apt, yum) in task definitions.
  • Clarify which features and tools are Windows-specific and which are cross-platform.
  • Add documentation sections or notes for customizing dev boxes based on Linux images, if supported.
  • Ensure that catalog and customization file examples demonstrate both Windows and Linux scenarios.
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-10 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 strong Windows bias. All configuration steps, compatibility notes, and troubleshooting guidance are focused exclusively on Windows environments. Windows-specific features (such as Memory Integrity, Virtual Machine Platform, and sysprep) are mentioned without Linux equivalents. There are no examples or instructions for enabling hibernation on Linux-based dev boxes, nor any mention of Linux compatibility or requirements. The CLI examples all use Windows OS parameters, and troubleshooting links are Windows-specific.
Recommendations
  • Explicitly state whether hibernation is supported for Linux-based dev boxes. If not, clarify this limitation early in the documentation.
  • If Linux support exists, provide equivalent instructions and examples for configuring hibernation on Linux dev boxes, including relevant CLI flags and compatibility considerations.
  • Include troubleshooting guidance for Linux images, or a note that troubleshooting is Windows-only if Linux is unsupported.
  • Mention Linux tools and patterns (such as cloud-init, systemd, or Linux-specific VM settings) where appropriate.
  • Ensure that references to OS-specific features (like Memory Integrity or Virtual Machine Platform) are clearly marked as Windows-only, and provide Linux alternatives or a statement of non-applicability.
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-10 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. All examples and built-in tasks focus exclusively on Windows-centric technologies such as PowerShell, WinGet, and Desired State Configuration (DSC). There are no references to Linux tools, package managers (like apt, yum, or zypper), or shell scripting. The documentation does not provide Linux equivalents or mention cross-platform support, and Windows tools are introduced first and exclusively throughout the article.
Recommendations
  • Add examples and guidance for customizing dev boxes using Linux tools and package managers (e.g., apt, yum, zypper).
  • Include sample image definition YAML files that use Bash scripts or Linux-specific tasks.
  • Clarify whether Dev Box supports Linux-based dev boxes and, if so, document the supported customization primitives for Linux.
  • Provide parity in documentation by listing Linux customization options alongside Windows options (e.g., PowerShell vs. Bash, WinGet vs. apt).
  • Explicitly mention any platform limitations or future plans for Linux support if not currently available.
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-10 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 environments. All configuration steps use PowerShell commands and Windows-specific tools (Hyper-V, New-VMSwitch, New-NetIPAddress, New-NetNat). There are no examples or instructions for Linux users, nor are Linux virtualization technologies (e.g., KVM, libvirt, bridge-utils) mentioned. The UI instructions reference Windows dialogs, and the prerequisites assume a Windows-based dev box.
Recommendations
  • Add equivalent instructions for Linux environments, using tools such as KVM, libvirt, and bridge-utils.
  • Provide Linux shell command examples for creating virtual switches and configuring NAT networks.
  • Include screenshots or descriptions of Linux network configuration dialogs or CLI steps.
  • Clarify in prerequisites that the guide is Windows-specific, or expand to cover Linux-based dev boxes.
  • Mention Linux alternatives to Hyper-V and PowerShell, such as QEMU/KVM and Bash scripts.
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-10 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. Tool installation instructions reference only Windows, and the image customization steps use Windows-specific tools (Chocolatey, PowerShell). The VM image creation process is tailored for Windows images, with no mention of Linux image workflows or customization examples.
Recommendations
  • Add equivalent Azure CLI and Bash examples alongside PowerShell commands for all steps.
  • Include instructions for installing Azure CLI and PowerShell on Linux and macOS, not just Windows.
  • Provide a parallel example for creating and customizing a Linux VM image (e.g., using apt/yum for package installation, Bash scripts for customization).
  • Mention Linux-compatible tools and patterns (e.g., cloud-init, shell scripts) in the customization section.
  • Clarify which steps are OS-agnostic and which are Windows-specific, and provide guidance for Linux users where applicable.
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-10 00:00
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 focusing exclusively on Windows-centric tools and terminology (e.g., Windows 365, Microsoft Remote Desktop, Windows Azure Service Management API) and omitting any mention of Linux-specific access patterns, tools, or client scenarios. All examples and app references are Windows-oriented, with no guidance for Linux users or alternative open-source remote desktop clients. The documentation assumes a Windows environment for both management and access, and does not address Linux parity in Dev Box access or management.
Recommendations
  • Add explicit examples and guidance for accessing Dev Boxes from Linux clients, including supported remote desktop clients (e.g., Remmina, FreeRDP) and any required configuration.
  • Clarify whether Dev Box supports Linux-based management and access, and document any limitations or differences.
  • Include references to cross-platform tools (e.g., Azure CLI, REST APIs) with Linux usage instructions and examples.
  • Provide parity in screenshots and step-by-step instructions for Linux users where applicable.
  • Mention any Linux-specific Conditional Access considerations or troubleshooting steps.
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-10 00:00
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 (WinGet, PowerShell), focusing on Windows environments and workflows (e.g., WinGet Desired State Configuration), and omitting any mention of Linux equivalents or examples. All customization examples and configuration instructions assume a Windows dev box, with no guidance for Linux-based dev boxes or cross-platform scenarios.
Recommendations
  • Include examples of customization files and tasks for Linux-based dev boxes, such as using apt, yum, or shell scripts.
  • Mention and document Linux package managers and configuration approaches alongside Windows tools like WinGet.
  • Clarify whether the Dev Box platform supports Linux environments, and if so, provide parity in documentation for Linux setup, validation, and customization.
  • Add cross-platform notes or tables that highlight differences and similarities between Windows and Linux dev box customization workflows.
  • Provide sample YAML customization files for Linux environments, and show how to validate and apply them.
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-10 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 code examples use Windows-specific paths (e.g., C:\workspaces), PowerShell scripts, and Windows tools like winget. There are no Linux or cross-platform examples, and Windows conventions are presented exclusively and first. The use of PowerShell and winget, both Windows-centric, further reinforces the bias. No mention is made of Linux equivalents (e.g., bash, apt, Linux file paths), nor are Linux-specific instructions or examples provided.
Recommendations
  • Provide parallel Linux examples for all customization tasks, using bash scripts and Linux file paths (e.g., /home/devbox/workspaces).
  • Include instructions for installing Azure CLI on Linux using apt, yum, or other package managers.
  • Show how to clone repositories and hydrate secrets in Linux environments, using bash and environment variables.
  • Avoid using Windows-only tools (like winget) in generic examples, or provide Linux alternatives.
  • Explicitly state cross-platform compatibility and note any limitations or differences for Linux users.
  • Add screenshots or references for Linux Azure DevOps and Key Vault configuration steps where applicable.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively references Windows environments, tools, and procedures. All examples, prerequisites, and instructions are tailored to Windows dev boxes, with no mention of Linux or cross-platform support. The only supported OS listed is Windows 11, and all verification steps (such as checking for agent installation and using context menus) are Windows-specific. There are no Linux equivalents or alternative instructions provided.
Recommendations
  • Explicitly state whether Endpoint Privilege Management is supported on Linux dev boxes. If not supported, clarify this limitation early in the documentation.
  • If Linux support exists or is planned, provide equivalent instructions for configuring and verifying Endpoint Privilege Management on Linux dev boxes.
  • Include Linux-specific prerequisites, such as supported distributions and required tools.
  • Offer examples of how to verify agent installation and policy application on Linux, such as relevant file paths, command-line checks, or desktop environment actions.
  • Where possible, use cross-platform terminology and avoid assuming Windows-only workflows.
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-10 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, specifically Microsoft Dev Box and Visual Studio on Windows. All code examples for generating solution caches use PowerShell and Windows-specific tools (devenv.exe), with no mention of Linux equivalents or cross-platform alternatives. The instructions and prerequisites assume a Windows-based workflow, and there are no examples or guidance for Linux users or developers using Visual Studio Code or other IDEs.
Recommendations
  • Provide equivalent instructions and examples for Linux environments, such as using Visual Studio Code or cross-platform .NET CLI tools.
  • Include bash or shell script examples for cache generation and Git optimizations, not just PowerShell.
  • Clarify whether the cache generation process is possible or relevant on Linux-based dev boxes, and if not, explicitly state the limitation.
  • Mention any cross-platform alternatives to Visual Studio (such as VS Code) and describe how similar optimizations could be performed.
  • Reorder or balance examples so that Linux and Windows instructions are presented together, or in parallel sections, to avoid Windows-first bias.
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-10 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 scenarios are focused exclusively on Windows environments, with no mention of Linux or cross-platform alternatives. Windows-specific tools (Windows App, Windows Hello, Hyper-V, certutil, Windows Insider builds) are referenced throughout, and all instructions assume the user is on Windows. There are no Linux equivalents or examples provided, nor is there guidance for users connecting from or to Linux-based dev boxes.
Recommendations
  • Add troubleshooting steps and examples for Linux-based dev boxes, including common connectivity and performance issues.
  • Include instructions for connecting to dev boxes from Linux clients, such as using RDP clients (Remmina, rdesktop, FreeRDP) or SSH.
  • Mention Linux equivalents for Windows tools (e.g., alternatives to certutil, Hyper-V, Windows Hello) or clarify if certain features are Windows-only.
  • Clearly indicate which troubleshooting steps apply only to Windows, and provide parity for Linux where possible.
  • Add notes or sections for macOS users if relevant, to ensure broader cross-platform coverage.
GitHub Create Pull Request
Dev Box Monitor Microsoft Dev Box and Diagnostic Data Logs ...ure-docs/blob/main/articles/dev-box/monitor-dev-box.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples for enabling diagnostic logs, with no equivalent examples for Linux users (e.g., Bash, Azure CLI). The scripting section is exclusively focused on PowerShell, which is primarily used on Windows, and there is no mention of Linux-native tools or workflows. Additionally, the order of presentation puts PowerShell before any mention of cross-platform alternatives, reinforcing a Windows-first approach.
Recommendations
  • Add Azure CLI examples for enabling diagnostic logs, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash shell scripting examples where relevant, especially for automation tasks.
  • Explicitly mention that the Azure portal, Azure CLI, and PowerShell are all supported and provide links or examples for each.
  • Where PowerShell is used, clarify its availability on Linux and macOS, or provide direct alternatives for those platforms.
  • Review screenshots and UI instructions to ensure they are not Windows-specific, and clarify any OS-neutral steps.
GitHub Create Pull Request
Dev Box Quickstart: Create and Access a Dev Box in the Cloud ...lob/main/articles/dev-box/quickstart-create-dev-box.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Windows App as the method for connecting to a dev box, without mentioning or providing instructions for Linux or macOS users. There are no examples or guidance for connecting from Linux (e.g., using RDP clients available on Linux), and the only tool mentioned for remote connection is the Windows App. This suggests an assumption that users are on Windows or using Microsoft tools, with no parity for Linux environments.
Recommendations
  • Add explicit instructions and examples for connecting to a dev box from Linux and macOS, including recommended RDP clients (e.g., Remmina, FreeRDP, rdesktop for Linux; Microsoft Remote Desktop for macOS).
  • Include a section or table listing supported platforms for remote connection, with links to relevant client downloads and setup guides for each OS.
  • Ensure that all steps and screenshots are not Windows-specific, or provide equivalent visuals for Linux/macOS where applicable.
  • Mention any browser-based connection options and clarify their cross-platform compatibility.
  • Avoid language that implies Windows is the default or only supported platform; use inclusive phrasing such as 'on your Windows, Linux, or macOS device...'
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-10 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 exhibits a strong Windows bias. Troubleshooting steps, examples, and tooling references are almost exclusively for Windows environments. Windows-specific tools (Windows App, Group Policy Editor, Registry Editor, dsregcmd.exe, Task Manager) are mentioned throughout, with detailed instructions and command-line examples provided only for Windows (and one for Mac). There are no Linux-specific troubleshooting steps, examples, or tool references, and Linux clients are not mentioned at all.
Recommendations
  • Add troubleshooting steps and examples for Linux client devices, including how to connect to Dev Box from Linux (e.g., using open-source RDP clients like Remmina or FreeRDP).
  • Include Linux equivalents for registry and policy changes, such as configuration file edits or environment variable settings.
  • Provide Linux-specific commands for checking connectivity, authentication, and remote desktop settings.
  • Mention Linux remote desktop tools and patterns alongside Windows and Mac, ensuring parity in instructions and examples.
  • Explicitly state platform support and limitations for Dev Box connectivity, and link to Linux client setup guides if available.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Remote Desktop Protocol (RDP) connectivity, which is primarily a Windows technology. All troubleshooting steps, tool references, and readiness checks (such as 'Windows Guest OS readiness') are Windows-centric, with no mention of Linux-based dev boxes, alternative remote access protocols (like SSH), or Linux troubleshooting steps. The documentation assumes the dev box is running Windows and does not provide parity for Linux users.
Recommendations
  • Include troubleshooting steps and tool usage for Linux-based dev boxes, such as SSH connectivity checks.
  • Mention Linux guest OS readiness and relevant checks alongside Windows checks.
  • Provide examples or guidance for resolving connectivity issues on Linux dev boxes, including common issues and solutions.
  • Clarify whether the Troubleshoot & Repair tool supports Linux dev boxes, and if not, suggest equivalent tools or manual steps for Linux environments.
  • Ensure documentation covers both RDP (Windows) and SSH (Linux) remote access scenarios.
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-10 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. All examples and references are centered on Windows-specific technologies (PowerShell, DSC, WinGet), with no mention or examples for Linux equivalents (such as Bash scripts, shell configuration files, or Linux package managers). The catalog structure and YAML example exclusively use Windows paths and tools, and Windows-centric terminology is used throughout. There is no guidance for Linux users or cross-platform scenarios.
Recommendations
  • Add equivalent examples for Linux, such as referencing Bash scripts, shell configuration files, or Linux package managers (e.g., apt, yum).
  • Include Linux file path examples alongside Windows paths in the catalog structure and YAML samples.
  • Mention and document how modular scripts and files can be used for Linux-based Dev Boxes, including any differences in task execution or file placement.
  • Provide guidance on cross-platform scripting best practices, such as using platform-agnostic scripts or conditional logic for different OS environments.
  • Ensure that intrinsic tasks and tooling references include Linux options (e.g., Bash, shell scripts, Linux package managers) and not just Windows tools.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page provides only Azure PowerShell/Cloud Shell examples for deploying the ARM template, with no equivalent Bash or Linux-native CLI instructions. The step-by-step deployment section is written entirely around PowerShell, and the only code sample is a PowerShell script. Although Azure CLI is mentioned as an alternative, no Linux/Bash example is shown. This creates a bias toward Windows users and may disadvantage those working primarily in Linux environments.
Recommendations
  • Add a Bash/Azure CLI example for deploying the ARM template, showing equivalent steps to the PowerShell script.
  • Include explicit instructions for using Azure CLI in Linux/macOS terminals, not just in Cloud Shell.
  • Present both PowerShell and Bash/CLI examples side-by-side or in tabs, so users can easily find instructions relevant to their platform.
  • When referencing tools or shell environments, avoid assuming PowerShell as the default and mention Bash/CLI alternatives equally.
  • Review all step-by-step instructions to ensure Linux users are not required to translate PowerShell commands themselves.
GitHub Create Pull Request
← Previous Page 3 of 9 Next →