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 176-200 of 217 flagged pages
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation for Microsoft Dev Box roadmap demonstrates a moderate Windows bias. It references PowerShell and Winget as primary primitives for customization and debugging tasks, and mentions Windows, RDP, and Visual Studio tools as core components of the developer experience. Linux equivalents (e.g., Bash, apt, Linux desktop protocols) are not mentioned, and Windows-centric tools are referenced before any cross-platform or Linux options. The only nod to Linux is a brief mention of WSL (Windows Subsystem for Linux), which is itself a Windows feature.
Recommendations
  • Provide examples and support for Linux/macOS customization workflows, such as Bash scripts or Linux package managers (apt, yum, etc.) alongside PowerShell and Winget.
  • Explicitly mention cross-platform tooling and remote desktop protocols (e.g., SSH, VNC, RDP alternatives) for Linux/macOS users.
  • Include documentation and examples for setting up Dev Box environments tailored for Linux/macOS development, not just Windows-centric scenarios.
  • Balance references to Windows tools by also listing Linux/macOS equivalents where relevant.
  • Clarify whether Dev Box supports non-Windows OS images and, if so, provide guidance for those platforms.
GitHub Create Pull Request
Dev Box Authoring recommendations for Dev Box image definitions ...pt-authoring-troubleshooting-guide-team-customizations.md
Medium Priority View Details →
Scanned: 2026-01-14 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 registry modifications). The CLI and log file locations use Windows conventions exclusively. There are no Linux/macOS equivalents or examples provided, and Windows patterns (such as running VS Code as administrator and using C:\ paths) are presented as defaults. Linux and macOS users are left without guidance for adapting these instructions to their platforms.
Recommendations
  • Add explicit guidance and examples for Linux/macOS users, including equivalent tools (e.g., apt, yum, bash scripts) and file paths.
  • Clarify which Dev Box features and built-in tasks are Windows-only and which are cross-platform.
  • Provide troubleshooting steps and log file locations for Linux/macOS environments.
  • Include notes or tables comparing Windows and Linux/macOS workflows for common tasks (software installation, scripting, permissions).
  • Ensure that references to PowerShell and WinGet are accompanied by alternatives or caveats for non-Windows platforms.
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-14 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, presenting only PowerShell command examples, and referencing Dev Box (a Windows-centric service) throughout. There are no Linux/macOS shell examples or explicit instructions for non-Windows platforms, despite Visual Studio Code and Dev Tunnels being cross-platform.
Recommendations
  • Add equivalent Linux/macOS shell commands (e.g., bash/zsh) for all PowerShell examples.
  • Clarify that PowerShell Core is cross-platform, but also provide native shell alternatives for Linux/macOS users.
  • Explicitly mention compatibility and steps for Linux/macOS environments in prerequisites and testing sections.
  • Include screenshots or instructions relevant to Linux/macOS 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
Medium Priority View Details →
Scanned: 2026-01-14 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. The apps table and scenario descriptions consistently reference Windows-specific tools and services (e.g., Windows 365, Microsoft Remote Desktop, Windows Azure Service Management API) without mention of Linux/macOS alternatives or cross-platform usage notes. The examples and instructions assume the use of Microsoft Entra admin center and Intune, which are web-based and cross-platform, but the app focus and terminology are Windows-centric. There are no explicit Linux/macOS examples or references to Linux-compatible remote desktop clients or management tools.
Recommendations
  • Add explicit notes or examples for Linux/macOS users, such as how to connect to Dev Boxes using cross-platform clients (e.g., FreeRDP, Remmina, or Microsoft Remote Desktop for macOS).
  • Clarify whether the listed apps (especially Microsoft Remote Desktop and Windows 365) have Linux/macOS equivalents or supported clients, and link to relevant documentation.
  • Include a section or table column indicating platform compatibility for each app/tool.
  • Provide troubleshooting or configuration guidance for Linux/macOS users where workflows may differ (e.g., remote desktop setup, SSO).
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-14 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. It references Windows-specific tools (WinGet, PowerShell), and examples focus exclusively on configuring Windows environments. There are no examples or guidance for Linux/macOS dev boxes, nor are Linux-native configuration tools or patterns mentioned. The use of WinGet and PowerShell is described without alternatives, and the overall workflow assumes a Windows-centric setup.
Recommendations
  • Add equivalent examples for Linux/macOS dev boxes, including sample customization files using Linux-native package managers (e.g., apt, yum, Homebrew).
  • Clarify whether the customization workflow and catalog tasks support Linux/macOS environments, and document any differences.
  • Provide guidance on how to configure dev boxes running Linux/macOS, including validation and troubleshooting steps.
  • Mention cross-platform tools or patterns where possible, and avoid assuming WinGet/PowerShell as the default.
  • Explicitly state platform limitations if user customizations are only supported for Windows dev boxes.
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-14 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 Windows bias by consistently providing examples that use Windows-specific tools, paths, and patterns (e.g., PowerShell scripts, C:\workspaces, winget for package installation). All code snippets and workflow descriptions assume a Windows environment, with no equivalent Linux/macOS examples or instructions. Linux tools (e.g., bash, apt, Linux file paths) are not mentioned, and Windows-centric tools are referenced exclusively and first.
Recommendations
  • Provide parallel examples for Linux/macOS environments, including bash scripts and Linux file paths (e.g., /home/dev/workspaces).
  • Include instructions for installing Azure CLI using Linux-native package managers (e.g., apt, yum, brew) alongside winget.
  • Show how to run customization tasks using bash or sh in addition to PowerShell.
  • Clarify which features and tasks are cross-platform and which are Windows-only.
  • Add notes or tables indicating platform compatibility for each example.
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-14 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, specifically referencing RDP sessions, which are primarily associated with Windows environments. There are no explicit Linux/macOS examples or mentions of equivalent remote access protocols (e.g., SSH, VNC), and the instructions are tailored to scenarios typical for Windows users. The Azure CLI commands themselves are cross-platform, but the context and terminology are Windows-centric.
Recommendations
  • Clarify whether stop-on-disconnect applies to non-RDP sessions (e.g., SSH for Linux/macOS Dev Boxes).
  • Provide examples or notes for Linux/macOS users, including how disconnects are detected for non-Windows sessions.
  • Mention alternative remote access protocols and their compatibility with the stop-on-disconnect feature.
  • Explicitly state platform limitations or parity in feature support.
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-14 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. All built-in task examples and configuration primitives (WinGet, PowerShell, Desired State Configuration) are Windows-specific. There are no references to Linux/macOS equivalents (e.g., Bash, apt, Homebrew, shell scripts), nor examples for customizing non-Windows dev boxes. Windows tools and patterns (WinGet, PowerShell DSC) are mentioned exclusively and before any cross-platform alternatives. This bias may create friction for teams wanting to use Linux/macOS dev boxes or customize them with native tools.
Recommendations
  • Add examples and guidance for customizing Linux/macOS dev boxes, including using Bash, shell scripts, apt, yum, Homebrew, etc.
  • Clarify whether Dev Box supports non-Windows images and, if so, provide parity in documentation for those platforms.
  • Include sample YAML image definition files for Linux/macOS environments.
  • Mention cross-platform configuration tools (e.g., Ansible, shell scripts) if supported.
  • Explicitly state platform limitations if Dev Box is Windows-only, to set expectations.
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-14 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 using the Azure portal GUI, which is most commonly accessed via Windows. There are no examples or instructions for performing these tasks using cross-platform tools such as Azure CLI, PowerShell, or REST API, which would allow Linux and macOS users to complete the same tasks from their native environments. The documentation does not mention or provide parity for command-line or automation approaches, and all screenshots and step-by-step instructions are based on the Azure portal interface.
Recommendations
  • Add instructions and examples for assigning roles using Azure CLI, which is available on Windows, Linux, and macOS.
  • Include PowerShell examples for users who prefer scripting, but ensure Azure CLI is presented first or alongside PowerShell.
  • Mention REST API methods for advanced users who may want to automate role assignments.
  • Explicitly state that the Azure portal is accessible from any modern browser on any OS, and clarify any OS-specific limitations if they exist.
  • Add a section comparing GUI and CLI approaches, highlighting cross-platform options.
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-14 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 concepts (RDP, Windows Guest OS readiness) and tools (developer portal, Troubleshoot & repair tool). There are no examples or guidance for Linux/macOS users, nor mention of alternative remote access protocols (e.g., SSH, VNC) commonly used on non-Windows platforms. The troubleshooting steps and checks are tailored to Windows environments, creating friction for users with Linux/macOS dev boxes or those connecting from non-Windows clients.
Recommendations
  • Include troubleshooting steps and examples for Linux/macOS dev boxes, such as SSH connectivity checks.
  • Mention alternative remote access protocols (SSH, VNC) and provide parity in troubleshooting guidance.
  • Clarify whether the Troubleshoot & repair tool supports non-Windows dev boxes, and if not, provide equivalent tools or manual steps for Linux/macOS.
  • Add notes or sections for users connecting from Linux/macOS clients, including relevant troubleshooting tips.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides deployment instructions using Azure PowerShell in Cloud Shell, with a full PowerShell script and step-by-step instructions referencing PowerShell-specific actions (e.g., right-click to paste, PowerShell cmdlets). There are no Linux/macOS shell (bash) or Azure CLI examples shown inline, and PowerShell is presented as the primary method. Although the page mentions that Azure CLI and portal can be used, no equivalent Linux/macOS-friendly example is provided.
Recommendations
  • Add a full Azure CLI (bash) example for deploying the ARM template, including parameter input and resource creation steps.
  • Present both PowerShell and CLI examples side-by-side, or offer a tabbed interface for Windows (PowerShell) and Linux/macOS (bash/CLI) users.
  • Clarify that Azure Cloud Shell supports both bash and PowerShell, and provide instructions for both environments.
  • Avoid instructions that reference Windows-specific UI actions (e.g., right-click to paste) without noting alternatives for Linux/macOS terminals.
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-14 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 and examples for enabling diagnostic logs using the Azure portal and PowerShell, but omits equivalent examples for Linux/macOS users, such as Azure CLI commands or Bash scripts. PowerShell is featured as the only command-line automation method, and is presented before any mention of CLI alternatives. This creates friction for users on Linux or macOS platforms who may not use PowerShell.
Recommendations
  • Add step-by-step instructions and examples for enabling diagnostic logs using Azure CLI, which is cross-platform and commonly used on Linux/macOS.
  • Present Azure CLI and PowerShell examples side-by-side, or at least mention CLI before or alongside PowerShell to avoid Windows-first bias.
  • Explicitly state that PowerShell examples are optional and provide links to CLI documentation for Linux/macOS users.
  • Include Bash script examples where appropriate for automation tasks.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by exclusively referencing the Windows App as the method to connect to a Dev Box, with no mention of Linux or macOS alternatives. The prerequisites and connection instructions focus solely 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 Box or whether alternative clients are supported.
Recommendations
  • Explicitly mention and provide instructions for connecting to a Dev Box from Linux and macOS, including supported RDP clients or browser-based access.
  • Add a table or section listing connection options for Windows, Linux, and macOS, with download links and basic usage instructions for each.
  • Clarify whether the developer portal and browser-based connection work equally well on non-Windows platforms.
  • If certain features (e.g., multi-monitor support) are Windows-only, clearly state this and suggest alternatives or workarounds for other platforms.
GitHub Create Pull Request
Dev Box Configure a user Customization File for Your Dev Box ...ticles/dev-box/how-to-configure-user-customizations.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a notable Windows bias. It references Windows-specific tools such as WinGet and PowerShell tasks, and the only example provided for customizing a dev box uses a WinGet Desired State Configuration file, which is exclusive to Windows. There are no Linux/macOS equivalents or examples, nor is there mention of how to use Linux package managers or shell scripts for customization. The language and examples assume a Windows environment, creating friction for Linux/macOS users.
Recommendations
  • Add examples of customization files that use Linux/macOS tools, such as apt, yum, Homebrew, or shell scripts.
  • Clarify whether dev boxes can be Linux-based, and if so, provide instructions for customizing those environments.
  • Include references to cross-platform package managers or scripting approaches.
  • Explicitly state any platform limitations for customization tasks.
  • Provide parity in documentation by showing both Windows and Linux/macOS workflows and examples.
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-13 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 web interface, which is most commonly accessed from Windows environments. There are no examples or instructions for performing these tasks using cross-platform tools such as Azure CLI, PowerShell, or REST API, nor is there any mention of Linux/macOS workflows. The absence of CLI or API instructions creates friction for users who prefer or require command-line automation, especially on Linux/macOS.
Recommendations
  • Add equivalent instructions for assigning roles using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include PowerShell examples for Windows users, but ensure CLI/API examples are presented first or alongside.
  • Mention REST API options for automation and scripting, with example requests.
  • Explicitly state that the Azure portal is accessible from any OS, but highlight CLI/API alternatives for Linux/macOS users.
  • Where screenshots are used, clarify that the portal UI is the same across platforms.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for Microsoft Dev Box roadmap demonstrates a moderate Windows bias. It references PowerShell and Winget as primary customization primitives, and highlights Windows, RDP, and Visual Studio tooling as core to the developer experience. Linux equivalents (e.g., Bash, Linux package managers, remote desktop protocols) are not mentioned, and Windows-centric tools are referenced before any cross-platform alternatives. There is a brief mention of WSL, but only in the context of accessing it from VS Code, not as a first-class platform.
Recommendations
  • Include Linux/macOS equivalents for customization workflows (e.g., Bash scripts, apt/yum/zypper for package management).
  • Provide examples and documentation for Dev Box customization using Linux-native tools and scripting.
  • Explicitly mention support for Linux/macOS Dev Box images and detail how to configure and manage them.
  • Highlight cross-platform remote connectivity options (e.g., SSH, VNC) alongside Windows RDP.
  • Ensure that onboarding and management features are described with parity for Linux/macOS environments.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. PowerShell is listed as a prerequisite, and all command-line examples use PowerShell syntax. There are no Linux/macOS equivalents or instructions for using Bash, zsh, or other common shells. The prerequisites and testing steps assume a Windows-centric workflow, with no mention of Linux or macOS environments or tools.
Recommendations
  • Add Linux/macOS prerequisites, such as Bash or zsh, and clarify if PowerShell Core is required or if native shells are supported.
  • Provide command-line examples for Linux/macOS, using their native shells (e.g., Bash).
  • Explicitly state whether the Dev Tunnels and conditional access workflows are supported on Linux/macOS, and document any differences.
  • Reorder examples or provide parallel instructions so Linux/macOS users are not secondary.
  • Mention cross-platform compatibility in the introduction and prerequisites.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. All examples and instructions reference PowerShell and WinGet, which are Windows-specific tools. There is no mention of Linux/macOS equivalents or how to customize Dev Box environments for non-Windows platforms. The documentation assumes Windows as the default environment and does not provide parity for Linux/macOS users.
Recommendations
  • Add examples and instructions for customizing Dev Box environments using Linux/macOS tools (e.g., Bash scripts, apt/yum/pacman for package management).
  • Clarify whether Dev Box supports Linux/macOS images and, if so, provide guidance for those platforms.
  • Include cross-platform scripting options and highlight differences in task execution between Windows and Linux/macOS environments.
  • Present examples for both Windows and Linux/macOS side by side, or indicate platform-specific steps clearly.
  • Avoid recommending Windows tools (PowerShell, WinGet) exclusively; mention alternatives where appropriate.
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 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on stopping Dev Boxes after RDP (Remote Desktop Protocol) session disconnects, which is a Windows-centric technology. There are no references to Linux/macOS remote access methods (such as SSH or VNC), nor any examples or guidance for non-Windows users. All terminology and instructions assume RDP usage, implicitly prioritizing Windows environments.
Recommendations
  • Clarify whether stop-on-disconnect applies to non-RDP sessions (e.g., SSH for Linux/macOS Dev Boxes).
  • If supported, add examples and explanations for Linux/macOS remote access scenarios (such as SSH disconnects).
  • Explicitly state any platform limitations (e.g., 'This feature is only available for Windows Dev Boxes using RDP').
  • If Linux/macOS Dev Boxes are supported, provide parity in documentation with relevant commands and workflows.
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-13 00:00
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 use Windows-specific paths (e.g., C:\workspaces), reference Windows images (e.g., Visual Studio on Windows 11), and use Windows tools such as PowerShell and winget. There are no Linux/macOS equivalents or examples, and Windows-centric patterns (PowerShell scripts, winget for Azure CLI installation) are presented exclusively. Linux users are left without guidance for adapting these workflows to their platforms.
Recommendations
  • Provide parallel Linux/macOS examples for all customization tasks, including file paths, shell commands, and package installation methods (e.g., apt, yum, brew).
  • Include examples using bash or sh instead of PowerShell, and clarify how to authenticate and use Azure CLI in non-Windows environments.
  • Reference Linux-compatible base images and show how to configure them for Dev Box customization.
  • List Windows and Linux/macOS examples side-by-side or indicate platform-specific instructions clearly.
  • Avoid assuming the use of Windows-only tools (e.g., winget, PowerShell) and mention alternatives for other platforms.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily focused on Windows-centric tools and patterns, such as PowerShell scripts and WinGet, with no mention of Linux/macOS equivalents or cross-platform scripting options. All examples and instructions assume the use of PowerShell and Windows-specific package managers, and there are no references to Bash, shell scripts, or Linux-native tools. This creates friction for users who wish to customize Dev Box environments for Linux or macOS development.
Recommendations
  • Add examples and guidance for creating tasks using Bash or shell scripts, especially for Linux/macOS environments.
  • Mention and provide parity for Linux package managers (e.g., apt, yum, Homebrew) alongside WinGet.
  • Clarify whether Dev Box supports non-Windows images and, if so, provide documentation for customizing those environments.
  • Include cross-platform scripting recommendations and highlight any limitations or requirements for non-Windows customization.
  • Present examples for both Windows and Linux/macOS environments, or clearly indicate Windows-only sections.
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-13 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. It references Windows-specific tools and services (e.g., Windows 365, Microsoft Remote Desktop, Windows Azure Service Management API) throughout, and the app table lists Windows-centric applications first. There are no explicit Linux/macOS examples, nor is there mention of Linux/macOS-specific access patterns or tools for connecting to Dev Boxes. However, some cross-platform tools (e.g., Azure CLI, browser access) are mentioned, and the instructions are generally platform-agnostic regarding policy configuration.
Recommendations
  • Add explicit examples or guidance for Linux/macOS users, such as how to connect to Dev Boxes using cross-platform clients (e.g., FreeRDP, Remmina, or the Microsoft Remote Desktop client for macOS).
  • Clarify which listed apps and connection methods are available on Linux/macOS and provide links to relevant client downloads or documentation.
  • Include a section or table column indicating platform compatibility for each app/tool.
  • Where possible, provide parity in step-by-step instructions for Linux/macOS environments, especially for remote desktop and CLI access.
  • Avoid listing Windows-specific tools first; present cross-platform options equally or in a platform-neutral order.
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-13 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 using the Azure portal and Azure PowerShell, but does not include equivalent CLI (az) or Bash examples. PowerShell is highlighted as the only command-line method, which is typically associated with Windows environments. There is no mention of Linux/macOS-specific workflows or tools, and the order of presentation puts PowerShell before any CLI or cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI (az) examples for enabling diagnostic logs, which are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, or clarify platform requirements.
  • Present CLI and PowerShell examples side-by-side or in parallel sections to avoid implying a Windows-first approach.
  • Include notes or links for Linux/macOS users regarding installation and usage of Azure CLI and PowerShell.
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-13 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 Windows bias by exclusively referencing the Windows App as the method to connect to a dev box, with no mention of Linux or macOS alternatives. All connection instructions and prerequisites focus on Windows tools, and there are no examples or guidance for users on non-Windows platforms. This creates friction for Linux/macOS users who may need to connect to their dev boxes using other remote desktop clients or protocols.
Recommendations
  • Add explicit instructions for connecting to a dev box from Linux and macOS, including recommended remote desktop clients (e.g., Remmina, FreeRDP, Microsoft Remote Desktop for macOS).
  • Include platform-specific prerequisites for Linux and macOS, such as installation steps for compatible remote desktop clients.
  • Provide examples and screenshots for connecting from non-Windows platforms.
  • Clarify whether browser-based access is cross-platform and provide details if so.
  • List any limitations or differences in experience for Linux/macOS users.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only Azure PowerShell examples for deploying the ARM template, with no equivalent Bash or Linux/macOS shell instructions. The step-by-step deployment instructions and code samples are Windows/PowerShell-centric, and the guidance assumes use of Azure Cloud Shell with PowerShell. Linux alternatives (Azure CLI in Bash, etc.) are mentioned only briefly and not demonstrated, making it harder for Linux/macOS users to follow along.
Recommendations
  • Add equivalent Azure CLI (bash) examples for deploying the ARM template, with step-by-step instructions.
  • Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
  • Reorder or parallelize example sections so that Linux/macOS instructions are shown alongside or before Windows/PowerShell instructions.
  • Clarify that all steps can be performed from Linux/macOS terminals using Azure CLI, and provide sample commands.
  • Where possible, avoid referencing only Windows-specific workflows (e.g., right-click to paste) and offer cross-platform alternatives.
GitHub Create Pull Request
← Previous Page 8 of 9 Next →