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 26-50 of 53 flagged pages
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-12 00:00
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 are no references to Linux/macOS remote access methods (such as SSH or VNC), nor any examples or notes for non-Windows users. The instructions and terminology assume Windows usage, creating friction for Linux/macOS users who may use different connection methods.
Recommendations
  • Clarify whether stop-on-disconnect applies to non-RDP sessions (e.g., SSH, VNC) and document any limitations.
  • Add examples or notes for Linux/macOS users, specifying how (or if) the feature works with their remote access protocols.
  • If the feature is Windows/RDP-only, explicitly state this limitation at the top of the page.
  • Provide guidance for Linux/macOS users on alternative ways to manage Dev Box lifecycle if stop-on-disconnect is not supported.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools and services (e.g., Microsoft Remote Desktop, Windows 365, Windows Azure Service Management API) are mentioned prominently and repeatedly, with no explicit mention of Linux/macOS equivalents or cross-platform alternatives for remote access or management. The examples and app tables focus on Windows-centric workflows, and the naming of apps/services is Windows-first. There are no Linux/macOS-specific instructions or references to cross-platform remote desktop clients.
Recommendations
  • Include explicit references to cross-platform remote desktop clients (e.g., Remmina, FreeRDP, rdesktop for Linux/macOS) and how they interact with Dev Box and Conditional Access policies.
  • Add examples or notes for configuring access from Linux/macOS endpoints, including any prerequisites or limitations.
  • Clarify whether the listed apps (such as Microsoft Remote Desktop) have supported clients for Linux/macOS, and provide links or instructions for those platforms.
  • Where possible, use neutral language (e.g., 'Remote Desktop client' instead of 'Microsoft Remote Desktop') and provide parity in instructions for all major platforms.
  • Consider adding a section or FAQ addressing common Linux/macOS scenarios and troubleshooting tips.
GitHub Create Pull Request
Dev Box Streamline Your Workflow with Dev Box Customizations ...les/dev-box/concept-what-are-dev-box-customizations.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for Dev Box customizations demonstrates a notable Windows bias. All examples and references to scripting and package management are centered on PowerShell and WinGet, which are Windows-specific tools. There is no mention of Linux/macOS equivalents (such as Bash, shell scripts, or apt/yum/homebrew), nor are there examples or guidance for customizing non-Windows dev boxes. The documentation assumes the use of Windows environments and does not address cross-platform scenarios.
Recommendations
  • Add examples and instructions for customizing Linux and macOS dev boxes, including supported scripting languages (e.g., Bash, shell scripts) and package managers (e.g., apt, yum, zypper, homebrew).
  • Clarify whether Dev Box supports non-Windows operating systems and, if so, document the customization process for those platforms.
  • If only Windows is supported, explicitly state this limitation early in the documentation.
  • Provide parity in examples by including both Windows (PowerShell/WinGet) and Linux/macOS (Bash/apt/homebrew) customization tasks.
  • Mention any platform-specific constraints or differences in the customization workflow.
GitHub Create Pull Request
Dev Box Secure Dev Tunnel Access with Conditional Policies ...v-box/how-to-conditional-access-dev-tunnels-service.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by requiring PowerShell 7.x as a prerequisite, providing only PowerShell-based command examples, and referencing Dev Box (a Windows-centric service) as the primary environment for testing. There are no Linux/macOS-specific instructions, nor are alternative shell examples (e.g., Bash) provided. The workflow assumes a Windows context and does not address how Linux/macOS users should perform equivalent tasks.
Recommendations
  • Add Linux/macOS prerequisites, such as Bash or compatible CLI environments.
  • Provide equivalent command-line examples for Bash/zsh and clarify cross-platform compatibility of 'code tunnel' commands.
  • Explicitly state whether Dev Tunnels and conditional access configuration can be performed from Linux/macOS environments, and document any differences.
  • Include screenshots or instructions for Linux/macOS where relevant, not just Windows/PowerShell.
  • Clarify if PowerShell 7.x is required only for Windows users, or if it is also needed on Linux/macOS, and provide installation guidance for those platforms if so.
GitHub Create Pull Request
Dev Box Configure hibernation for Microsoft Dev Box ...ticles/dev-box/how-to-configure-dev-box-hibernation.md
Medium 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 for configuring hibernation in Microsoft Dev Box exhibits a notable Windows bias. All example commands and configuration steps reference Windows-specific features (e.g., 'Virtual Machine Platform', 'Windows Security', disabling Memory Integrity), and all screenshots and UI flows are Windows-centric. There are no Linux/macOS equivalents or guidance for non-Windows images, and troubleshooting is focused exclusively on Windows VM issues. The CLI examples use Azure CLI, which is cross-platform, but all image creation and compatibility notes assume Windows OS. No mention is made of Linux-based dev boxes or how hibernation applies to them.
Recommendations
  • Explicitly state whether hibernation is supported for Linux/macOS dev boxes, and if not, clarify the limitation.
  • If Linux support exists, provide equivalent instructions for enabling hibernation on Linux-based images, including compatible SKUs and required settings.
  • Add troubleshooting steps and compatibility notes for Linux images, if applicable.
  • Balance examples and UI screenshots to include Linux scenarios, or note their absence.
  • Clarify whether features like nested virtualization and Memory Integrity have Linux analogs or are Windows-only.
GitHub Create Pull Request
Dev Box Configure Customization Tasks ...ticles/dev-box/how-to-configure-customization-tasks.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing PowerShell scripts and WinGet (a Windows package manager) as the primary mechanisms for task customization. All examples and instructions assume the use of PowerShell, with no mention of Bash, shell scripts, or Linux/macOS equivalents. The catalog and quickstart examples are Windows-centric, and there is no guidance for users wishing to use Linux-native tools or scripting languages.
Recommendations
  • Add examples of tasks using Bash scripts or shell scripts for Linux/macOS environments.
  • Clarify whether Dev Box supports Linux/macOS images and, if so, provide guidance for customizing those environments.
  • Include references to Linux package managers (e.g., apt, yum, Homebrew) and show how to use them in tasks.
  • Present cross-platform scripting options (e.g., Python, Node.js) and demonstrate their usage in task definitions.
  • Explicitly state any platform limitations or requirements at the beginning of the documentation.
GitHub Create Pull Request
Dev Box Create Dev Box Image Definition Files for Team Customizations ...ticles/dev-box/how-to-configure-team-customizations.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a notable Windows bias. It exclusively references Windows-centric tools and patterns, such as PowerShell, WinGet, and Desired State Configuration (DSC), without mentioning or providing examples for Linux/macOS equivalents. All built-in tasks are Windows-specific, and the only configuration management approach discussed is PowerShell DSC. There are no references to Linux package managers (e.g., apt, yum, Homebrew) or shell scripting, nor are there examples or guidance for customizing dev boxes based on Linux/macOS environments. The order and language also prioritize Windows tools and workflows, implicitly suggesting that Dev Box customization is a Windows-only or Windows-first experience.
Recommendations
  • Add examples and documentation for customizing dev boxes with Linux/macOS environments, including using shell scripts (bash/zsh), Linux package managers (apt, yum, dnf), and macOS tools (Homebrew).
  • Clarify whether Dev Box supports non-Windows base images, and if so, provide parity in task primitives (e.g., support for bash, sh, or other scripting languages).
  • Include sample image definition files for Linux/macOS, showing how to install packages and configure environments.
  • Mention limitations or platform support explicitly if Dev Box is Windows-only, to set expectations for non-Windows users.
  • If possible, expand built-in task support to include Linux/macOS equivalents and document their usage.
GitHub Create Pull Request
Dev Box Configure a user Customization File for Your Dev Box ...ticles/dev-box/how-to-configure-user-customizations.md
Medium 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 demonstrates a notable Windows bias. It references Windows-specific tools (WinGet, PowerShell), and the only example of a customization file uses WinGet Desired State Configuration, which is exclusive to Windows. There are no examples or guidance for Linux/macOS dev boxes, nor are equivalent Linux/macOS package managers or scripting environments mentioned. The prerequisites and workflow assume a Windows environment, and Windows terminology is used throughout.
Recommendations
  • Add examples of customization files using Linux/macOS tools (e.g., apt, yum, Homebrew, bash scripts).
  • Clarify whether the Dev Box platform supports Linux/macOS dev boxes, and if so, provide parity in documentation for those environments.
  • Include references to cross-platform package managers and scripting environments.
  • If PowerShell and WinGet are only available on Windows, explicitly state this and offer alternative workflows for non-Windows users.
  • Show Linux/macOS examples alongside Windows examples, not just after or omitted.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. All code examples use Windows-specific paths (e.g., C:\workspaces), PowerShell scripts, and Windows-only tools like winget. There are no Linux/macOS equivalents or examples, and Windows conventions are presented exclusively and first. This creates friction for Linux/macOS users who may not be able to directly apply the instructions.
Recommendations
  • Provide Linux/macOS equivalents for all customization examples, including file paths and shell commands.
  • Include examples using Bash or sh instead of only PowerShell.
  • Mention cross-platform installation methods for Azure CLI (e.g., apt, yum, Homebrew) alongside winget.
  • Clarify which steps and tools are platform-specific, and offer alternatives where possible.
  • Show how to clone repositories and hydrate secrets on Linux/macOS Dev Boxes.
GitHub Create Pull Request
Dev Box Resolve connectivity issues with Troubleshoot and Repair ...articles/dev-box/how-to-troubleshoot-repair-dev-box.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page focuses exclusively on troubleshooting Remote Desktop Protocol (RDP) connectivity issues for dev boxes, referencing Windows-specific tools and checks (such as 'Windows Guest OS readiness') and only mentioning RDP clients. There are no examples or guidance for Linux/macOS users, such as using alternative remote access protocols or troubleshooting steps for non-Windows operating systems. The troubleshooting steps and screenshots are tailored to the Microsoft developer portal and Windows environments, with no mention of Linux or cross-platform considerations.
Recommendations
  • Include troubleshooting guidance for Linux/macOS users, such as using open-source RDP clients (e.g., Remmina, rdesktop, FreeRDP) and addressing common connectivity issues on those platforms.
  • Mention alternative remote access protocols (such as SSH or VNC) if supported by dev boxes, and provide parity in troubleshooting steps.
  • Clarify whether the Troubleshoot & Repair tool is applicable to non-Windows dev boxes, and if not, provide equivalent steps or tools for Linux/macOS environments.
  • Add screenshots and examples for Linux/macOS users accessing the developer portal and running troubleshooting steps.
  • Explicitly state OS requirements and limitations for the Troubleshoot & Repair tool.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for enabling diagnostic logs via the Azure portal and PowerShell, but omits equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash). PowerShell is highlighted as the only command-line automation method, and appears after the portal steps, reinforcing a Windows-centric approach. No Linux-specific tools or cross-platform CLI examples are provided.
Recommendations
  • Add step-by-step instructions and code samples for enabling diagnostic logs using Azure CLI, which is cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that Azure CLI can be used on all platforms and provide links to CLI installation and usage guides.
  • Reorder sections so that cross-platform methods (Azure portal and Azure CLI) are presented before or alongside PowerShell, rather than PowerShell being the only automation example.
  • Include notes or tips for Linux/macOS users where relevant, such as shell differences or authentication nuances.
GitHub Create Pull Request
Dev Box Configure Microsoft Dev Box with an ARM template ...s/dev-box/quickstart-configure-dev-box-arm-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for deploying the ARM template, with no equivalent Bash or Linux/macOS CLI instructions. The step-by-step deployment section is written with PowerShell in mind, and references to Azure Cloud Shell default to PowerShell. While Azure CLI is mentioned as an alternative, no concrete Linux/macOS example is given, and the PowerShell workflow is presented first and in detail.
Recommendations
  • Add explicit Bash/Azure CLI examples for deploying the ARM template, suitable for Linux/macOS users.
  • Present both PowerShell and Bash/CLI workflows side-by-side, or clarify how to switch Cloud Shell to Bash.
  • Ensure instructions for copying/pasting code and entering parameters are not Windows-centric.
  • Where tools like Visual Studio are mentioned, note cross-platform alternatives or clarify platform requirements.
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
Medium 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 page demonstrates a Windows bias by exclusively referencing the Windows App as the method for connecting to a dev box, with no mention of Linux or macOS alternatives. All connection instructions and prerequisites center on Windows tooling, and there are no examples or guidance for users on Linux or macOS platforms. This creates friction for non-Windows users, who may not know how to access their dev boxes.
Recommendations
  • Add explicit instructions for connecting to a dev box from Linux and macOS, such as using RDP clients (e.g., Remmina, KRDC, FreeRDP, Microsoft Remote Desktop for macOS).
  • Include platform-specific prerequisites for Linux and macOS, listing supported remote desktop clients and download links.
  • Present connection options for all platforms in parallel, rather than focusing solely on Windows.
  • Clarify any limitations or differences in experience between platforms.
  • If browser-based access is supported, highlight this as a cross-platform solution.
GitHub Create Pull Request
Dev Box Configure a user Customization File for Your Dev Box ...ticles/dev-box/how-to-configure-user-customizations.md
Medium 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 page exhibits a notable Windows bias. It references Windows-specific tools (WinGet, PowerShell), and examples focus exclusively on Windows environments. There are no Linux/macOS equivalents or examples, and the customization workflow is described in terms of Windows tooling and patterns. Linux/macOS users are left without guidance for creating or applying customization files in non-Windows dev boxes.
Recommendations
  • Add explicit instructions and examples for creating and applying customization files on Linux and macOS dev boxes.
  • Include Linux/macOS-specific tools and workflows (e.g., apt, Homebrew, shell scripts) in sample customization files.
  • Clarify whether the Dev Box platform supports non-Windows dev boxes and, if so, provide parity in documentation.
  • Avoid assuming WinGet or PowerShell as the default; mention alternatives for other platforms.
  • Present cross-platform examples side-by-side or indicate platform-specific steps clearly.
GitHub Create Pull Request
Dev Box Secure Dev Tunnel Access with Conditional Policies ...v-box/how-to-conditional-access-dev-tunnels-service.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. Prerequisites require PowerShell 7.x and reference Dev Box (a Windows-based environment). All command-line examples use PowerShell, with no mention of Linux/macOS alternatives (e.g., Bash, zsh, or native terminal usage). The testing steps assume a Dev Box, and there is no guidance for users on Linux or macOS platforms. Windows tools and patterns are referenced exclusively and appear before any cross-platform considerations.
Recommendations
  • Provide equivalent command-line instructions for Linux/macOS users (e.g., using Bash/zsh).
  • Clarify whether PowerShell 7.x is required on all platforms, and if so, provide installation instructions for Linux/macOS.
  • Include examples and screenshots from Linux/macOS environments to demonstrate parity.
  • Explicitly state whether Dev Tunnels and conditional access policies can be configured and tested from non-Windows environments.
  • List prerequisites for Linux/macOS users (e.g., VS Code, PowerShell Core, or alternatives).
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for enabling diagnostic logs using the Azure portal and Azure PowerShell, but does not include equivalent examples for Linux/macOS users, such as Azure CLI commands or Bash scripts. The PowerShell section is the only command-line example, and it is presented before any mention of cross-platform alternatives. This creates friction for users on Linux or macOS who may not have access to PowerShell or prefer CLI/Bash.
Recommendations
  • Add equivalent Azure CLI examples for enabling diagnostic logs, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if relevant, and provide installation guidance or alternatives.
  • Present Azure CLI and PowerShell examples side-by-side, or offer a tabbed interface for users to choose their preferred platform.
  • Ensure screenshots and instructions for the Azure portal do not assume Windows-only usage (e.g., avoid references to Windows-specific UI elements).
GitHub Create Pull Request
Dev Box Microsoft Dev Box deployment guide ...n/articles/dev-box/concept-dev-box-deployment-guide.md
Medium 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 oriented toward Windows environments, with repeated references to Windows-specific management tools (Intune, Entra ID, Active Directory), Windows device management, and Windows-centric customization examples (WinGet, Chocolatey, PowerShell). There are no examples or guidance for Linux/macOS dev box images, device management, or developer workflows. Linux/macOS users may find it unclear how to deploy, manage, or customize non-Windows dev boxes.
Recommendations
  • Explicitly document support for Linux/macOS dev box images, including any limitations.
  • Provide examples of creating and customizing Linux/macOS dev boxes, including setup tasks using Linux/macOS package managers (e.g., apt, yum, Homebrew) and shell scripts.
  • Clarify how device management and compliance work for non-Windows dev boxes (e.g., Intune support, alternatives, or limitations).
  • Include Linux/macOS equivalents for customization tasks (not just WinGet/Chocolatey/PowerShell).
  • Add troubleshooting and monitoring guidance for Linux/macOS dev boxes.
  • Present examples for all platforms in parallel, not just Windows first.
GitHub Create Pull Request
Dev Box Streamline Your Workflow with Dev Box Customizations ...les/dev-box/concept-what-are-dev-box-customizations.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page for Dev Box customizations demonstrates a notable Windows bias. All examples and instructions reference PowerShell and WinGet, which are Windows-centric tools. There is no mention of Linux/macOS equivalents, nor are there examples or guidance for customizing non-Windows dev boxes. The language and recommendations assume a Windows environment, and Windows tools are presented as the default and recommended approach.
Recommendations
  • Add explicit guidance and examples for customizing Linux and macOS dev boxes, if supported.
  • Include references to cross-platform scripting options (e.g., Bash, shell scripts) and package managers (e.g., apt, yum, Homebrew) alongside PowerShell and WinGet.
  • Clarify whether Dev Box supports non-Windows operating systems, and if so, provide parity in documentation for those platforms.
  • Present examples for both Windows and Linux/macOS environments, and avoid recommending Windows tools as the default without alternatives.
  • Indicate any platform limitations or requirements up front so users know if the documentation is Windows-only.
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-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 roadmap documentation for Microsoft Dev Box demonstrates a notable Windows bias. It references PowerShell and Winget as primary primitives for customization and debugging, with no mention of Linux/macOS equivalents (e.g., Bash, apt, yum, Homebrew). The focus is on Windows-centric tools, patterns, and infrastructure (RDP, Windows, Visual Studio, Service Tags for Windows Firewall), and examples or features are described in a Windows-first context. There are no explicit examples or guidance for Linux/macOS users, nor are alternative workflows or tools mentioned for those platforms.
Recommendations
  • Add examples and workflows for Linux/macOS environments, such as using Bash scripts, Linux package managers (apt, yum), and alternative remote desktop protocols.
  • Explicitly mention support for Linux/macOS Dev Box images and provide parity in customization primitives (e.g., Bash, Zsh, Homebrew).
  • Highlight cross-platform capabilities in CLI and VS Code extension usage, including how Linux/macOS users can debug and customize Dev Box environments.
  • Include documentation sections or notes that address Linux/macOS-specific concerns, such as file system differences, shell environments, and network configuration.
  • Ensure that references to Windows tools (PowerShell, Winget, RDP, Windows Firewall) are balanced with Linux/macOS equivalents or alternatives.
GitHub Create Pull Request
Dev Box Configure Customization Tasks ...ticles/dev-box/how-to-configure-customization-tasks.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing PowerShell scripts and WinGet (a Windows package manager) as the primary mechanisms for task customization. All examples and instructions assume the use of PowerShell and Windows-centric tools, with no mention of Bash, shell scripts, or Linux/macOS equivalents. There are no examples or guidance for creating cross-platform tasks or supporting Linux/macOS developer environments.
Recommendations
  • Include examples using Bash or shell scripts for task definitions, alongside PowerShell.
  • Mention and provide guidance for using cross-platform tools (e.g., apt, Homebrew, or generic shell scripting) in tasks.
  • Clarify whether Dev Box supports Linux/macOS images and, if so, document how to customize those environments.
  • Present examples for both Windows and Linux/macOS environments, or clearly indicate platform limitations.
  • Avoid assuming PowerShell as the default scripting language; offer parity for other platforms.
GitHub Create Pull Request
Dev Box Configure hibernation for Microsoft Dev Box ...ticles/dev-box/how-to-configure-dev-box-hibernation.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. All example commands and configuration steps reference Windows-specific settings, features, and images. Instructions for disabling incompatible features and enabling nested virtualization are exclusively for Windows, with no mention of Linux or macOS equivalents. The troubleshooting section and recommendations focus solely on Windows VM images and configurations, omitting guidance for Linux-based dev boxes. There are no examples or considerations for Linux or macOS environments, and Windows terminology and tools are used throughout.
Recommendations
  • Include explicit guidance for configuring hibernation on Linux-based dev boxes, if supported.
  • Add Linux-specific examples for enabling/disabling features incompatible with hibernation.
  • Clarify whether hibernation is supported for non-Windows images and, if not, state this clearly at the beginning.
  • Provide troubleshooting steps for Linux dev boxes, or link to relevant documentation.
  • Balance references to Windows Marketplace images with mentions of Linux alternatives, if available.
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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It repeatedly references Windows-specific tools and services (such as Windows 365, Microsoft Remote Desktop, and Windows Azure Service Management API) and lists Windows-named apps first in tables and descriptions. There are no explicit Linux/macOS examples or mentions of cross-platform alternatives for remote access or management. While the Azure CLI and REST APIs are referenced, the documentation does not clarify Linux/macOS parity or provide platform-specific guidance for non-Windows users.
Recommendations
  • Explicitly mention and provide examples for accessing Dev Boxes from Linux and macOS clients, including supported remote desktop clients and configuration steps.
  • Clarify whether all listed apps (e.g., Microsoft Remote Desktop, Windows 365) have cross-platform equivalents and provide links or instructions for Linux/macOS users.
  • Add a section or notes on platform compatibility for each app and scenario, indicating any limitations or required steps for non-Windows environments.
  • Include Azure CLI and REST API usage examples for common tasks, demonstrating cross-platform management.
  • Ensure that tables and lists do not always prioritize Windows-named tools, and balance coverage with platform-neutral or cross-platform options.
GitHub Create Pull Request
Dev Box Create Dev Box Image Definition Files for Team Customizations ...ticles/dev-box/how-to-configure-team-customizations.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. All built-in tasks for Dev Box customizations are Windows-centric (WinGet, PowerShell, DSC), with no mention of Linux/macOS equivalents or cross-platform alternatives. Examples and workflows exclusively reference Windows tools and patterns, such as WinGet and PowerShell DSC, and do not provide guidance for customizing dev boxes with Linux-native tools (e.g., Bash, apt, yum, shell scripts). There are no Linux/macOS-specific examples, and the documentation implicitly assumes a Windows environment throughout.
Recommendations
  • Add explicit support and examples for Linux/macOS dev boxes, including tasks using Bash, shell scripts, and package managers like apt, yum, or Homebrew.
  • Clarify whether Dev Box supports non-Windows images and, if so, provide parity in documentation for customizing those environments.
  • Include sample image definition files and workflows for Linux/macOS, demonstrating installation of common tools and packages.
  • Mention cross-platform alternatives to PowerShell and WinGet, or note limitations if only Windows is supported.
  • Reorder examples or provide tabs for both Windows and Linux/macOS workflows to avoid Windows-first presentation.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias. All code examples and workflow descriptions use Windows-specific tools, paths, and conventions (e.g., PowerShell scripts, C:\workspaces, winget). There are no Linux/macOS equivalents or examples provided, and Windows-centric tools (winget, PowerShell) are referenced exclusively. This may create friction for Linux/macOS users attempting to follow the instructions.
Recommendations
  • Provide equivalent examples for Linux/macOS environments, using Bash scripts and POSIX paths (e.g., /home/dev/workspaces).
  • Include instructions for installing Azure CLI on Linux/macOS (e.g., apt, yum, Homebrew) alongside winget.
  • Show how to authenticate and download blobs/artifacts using Bash or cross-platform scripting, not just PowerShell.
  • Clarify which steps are platform-agnostic and which require adaptation for non-Windows systems.
  • Add explicit notes or sections for Linux/macOS users to ensure parity and reduce friction.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses on stopping Dev Boxes when users disconnect from RDP sessions, which is a Windows-specific protocol. There are no references to Linux/macOS remote access methods (e.g., SSH, VNC), nor any mention of how stop-on-disconnect would work for non-Windows Dev Boxes. All examples and terminology assume Windows usage.
Recommendations
  • Clarify whether stop-on-disconnect applies to Linux/macOS Dev Boxes and their typical remote access protocols (e.g., SSH, VNC).
  • If supported, provide examples for Linux/macOS Dev Boxes, including how disconnect detection works for non-RDP sessions.
  • Explicitly state any limitations or differences for Linux/macOS Dev Boxes regarding this feature.
  • Consider adding a table comparing stop-on-disconnect behavior across Windows, Linux, and macOS Dev Boxes.
GitHub Create Pull Request
← Previous Page 2 of 3 Next →