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 151-175 of 217 flagged pages
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-dev-box-serverless-gpu.md
...les/dev-box/how-to-configure-dev-box-serverless-gpu.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows Terminal as the default shell environment and omitting any mention of Linux or cross-platform alternatives. All example commands are shown in the context of Windows, and there are no instructions for Linux or macOS users. The workflow assumes the user is operating in a Windows-based Dev Box, with no guidance for those using Linux shells or tools.
Recommendations
- Provide equivalent instructions and examples for Linux and macOS users, including how to launch the GPU shell from common Linux terminals (e.g., GNOME Terminal, Konsole, xterm) and macOS Terminal.
- Clarify whether the devbox CLI and GPU features are available and supported on non-Windows Dev Boxes, and if so, document any differences in setup or usage.
- Include screenshots or terminal output examples from Linux/macOS environments where applicable.
- Avoid referencing Windows-specific tools (like Windows Terminal) as the only option; instead, use neutral language such as 'Open your terminal' and specify alternatives for different platforms.
- Explicitly state platform requirements and support in the prerequisites section.
Create Pull Request
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-intune-conditional-access-policies.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-intune-conditional-access-policies.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-centric bias by exclusively referencing Windows-specific tools and services (such as Microsoft Remote Desktop, Windows 365, and Windows Azure Service Management API) and by not providing any Linux-specific examples or guidance. All application references and scenarios assume a Windows environment, with no mention of Linux clients, tools, or workflows for accessing or managing Dev Boxes. There are no instructions or examples for Linux users, nor is there any discussion of cross-platform compatibility.
Recommendations
- Include examples and instructions for accessing Dev Boxes from Linux clients, such as using open-source RDP clients (e.g., FreeRDP, Remmina) or SSH where applicable.
- Mention and document any differences or limitations when connecting to Dev Boxes from Linux or macOS environments.
- Add a section or table listing supported platforms (Windows, Linux, macOS) for each access method and tool, with links to relevant client downloads and setup guides.
- Provide parity in step-by-step instructions for configuring Conditional Access policies as they apply to non-Windows endpoints, including any required configuration for Linux devices in Intune.
- Clarify whether Intune device compliance and Conditional Access policies can be enforced on Linux endpoints, and provide references to relevant documentation if supported.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-connect-devices-to-dev-box.md
.../articles/dev-box/how-to-connect-devices-to-dev-box.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation exclusively describes steps for connecting Android devices to a dev box using Windows tools and workflows. All instructions reference Windows-specific utilities (Device Manager, Local Group Policy Editor, cmd), and there are no examples or guidance for Linux or macOS users. This presents a strong Windows bias and lacks parity for developers on other platforms.
Recommendations
- Add equivalent instructions for Linux (and optionally macOS), including how to check device connectivity (e.g., using `lsusb`, `adb devices`), and how to manage USB permissions.
- Describe how to configure USB redirection for remote desktop solutions commonly used on Linux (such as FreeRDP, Remmina, or xrdp), including relevant configuration files or command-line options.
- Include troubleshooting steps for ADB device detection on Linux, such as adding udev rules for Android devices.
- Clearly separate platform-specific instructions, labeling sections for Windows, Linux, and macOS, to ensure all users can follow the documentation.
- Avoid assuming the use of Windows-only tools (like Device Manager or gpedit.msc) as the default or only method.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-create-customization-tasks-catalog.md
...s/dev-box/how-to-create-customization-tasks-catalog.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows environments, with all examples and instructions focused on PowerShell scripts and Windows-native tools like WinGet and Desired State Configuration (DSC). There is no mention of Linux scripting, shell examples, or cross-platform compatibility. The documentation assumes the use of Windows-based tooling and does not provide Linux equivalents or guidance for non-Windows environments.
Recommendations
- Include examples using Bash or shell scripts alongside PowerShell, especially for tasks that could be cross-platform.
- Mention and provide guidance for Linux package managers (e.g., apt, yum) in addition to WinGet.
- Clarify whether Dev Box supports Linux-based dev boxes and, if so, provide instructions and examples relevant to those environments.
- Add a section or callout explaining how to author tasks for Linux or cross-platform scenarios, including YAML examples referencing non-Windows scripts.
- Ensure that documentation for customizing dev boxes is inclusive of both Windows and Linux developer workflows.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-create-dev-boxes-developer-portal.md
...es/dev-box/how-to-create-dev-boxes-developer-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. The 'Windows App' is recommended and described in detail as the default and enhanced experience, with legacy Remote Desktop (a Windows technology) also highlighted. There is no mention of Linux-native remote desktop clients or workflows, nor are there examples or guidance for Linux users. The only cross-platform mention is that the Windows App is available on macOS, iOS, Android, and web, but Linux is omitted. The CLI section references Azure CLI but does not provide parity examples or considerations for Linux environments.
Recommendations
- Explicitly mention and provide instructions for connecting to a dev box from Linux, including recommended Linux-compatible RDP clients (e.g., Remmina, FreeRDP, rdesktop).
- Clarify whether the Windows App is available for Linux or, if not, suggest alternative methods for Linux users.
- Add Linux-specific examples or notes in sections discussing remote desktop connections and CLI usage.
- Ensure that all cross-platform tools are introduced together, or that Linux options are not omitted or relegated to secondary status.
- Include troubleshooting tips or links specifically for Linux users who may encounter issues connecting to dev boxes.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-elevate-privilege-dev-box.md
...n/articles/dev-box/how-to-elevate-privilege-dev-box.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively describes configuring Intune Endpoint Privilege Management for Windows-based dev boxes, with all examples, screenshots, and instructions focused on Windows 10/11. There is no mention of Linux or macOS support, nor are there any examples or guidance for non-Windows environments. All tools, UI elements, and file paths are Windows-specific.
Recommendations
- Clearly state in the prerequisites or introduction whether Endpoint Privilege Management is only supported on Windows, and if so, mention any plans or alternatives for Linux/macOS.
- If Linux or macOS support is available or planned, provide equivalent configuration steps, examples, and screenshots for those platforms.
- Include a comparison table or section outlining feature parity and differences between Windows and other operating systems.
- If only Windows is supported, suggest alternative privilege management solutions for Linux (e.g., sudo policies, polkit) and reference relevant documentation.
- Avoid using language that implies Windows is the default or only environment unless it is a hard product limitation, and make this explicit for cross-platform clarity.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-enable-single-sign-on.md
.../main/articles/dev-box/how-to-enable-single-sign-on.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-based workflows, terminology, and tools. All examples and instructions assume the use of the Azure portal and Microsoft Entra authentication, which are tightly integrated with Windows environments. There is no mention of Linux-based dev boxes, Linux authentication flows, or cross-platform considerations. The only referenced user experience is for Windows sign-on, and related content links are also Windows-specific.
Recommendations
- Explicitly state whether Linux-based dev boxes are supported for SSO and, if so, provide equivalent instructions and screenshots for Linux environments.
- Include examples or notes for users connecting from Linux or macOS clients, addressing any differences in the SSO experience.
- Reference or link to documentation about SSO for non-Windows environments if available, or clarify any limitations.
- Avoid using Windows terminology exclusively (e.g., 'sign in to Windows') unless the feature is truly Windows-only; otherwise, use more neutral language such as 'sign in to your dev box.'
- Add a section on troubleshooting or expected behavior for Linux users, if supported.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-generate-visual-studio-caches.md
...ticles/dev-box/how-to-generate-visual-studio-caches.md
High Priority
View Details →
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 command-line examples use PowerShell or Windows-specific tooling (e.g., devenv.exe), and there are no Linux or cross-platform alternatives provided. The workflow assumes the use of Windows-based images and does not mention or support Linux-based development environments.
Recommendations
- Provide equivalent instructions and examples for Linux-based dev boxes, if supported.
- Include cross-platform or Linux-specific commands for cache generation, or explicitly state if the feature is Windows-only.
- Mention and document any limitations or lack of support for Linux environments up front.
- If possible, suggest alternative workflows or tools for Linux users (e.g., using VS Code with similar caching or performance optimizations).
- Balance the order of presentation so that Linux and Windows options are given equal prominence where both are supported.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-hibernate-your-dev-box.md
...main/articles/dev-box/how-to-hibernate-your-dev-box.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (RDP app, Windows App) and troubleshooting steps that assume RDP usage. There are no Linux-specific examples or mentions of Linux remote desktop clients or workflows, and the only CLI example is generic (Azure CLI) without platform-specific guidance. The 'Windows App' is mentioned as a way to resume a dev box, but no Linux equivalent is provided.
Recommendations
- Include instructions or notes for Linux users, such as how to connect to a dev box using common Linux RDP clients (e.g., Remmina, FreeRDP).
- When referencing the 'Windows App', also mention if there are equivalent applications or methods for Linux and macOS, or clarify if such options are unavailable.
- In troubleshooting, provide guidance for Linux users (e.g., what errors might appear in Linux RDP clients and how to resolve them).
- Review all screenshots and UI references to ensure they are not Windows-exclusive, or provide Linux/macOS equivalents where possible.
- Explicitly state platform compatibility and any differences in experience between Windows, Linux, and macOS users.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-set-up-dev-tunnels.md
...lob/main/articles/dev-box/how-to-set-up-dev-tunnels.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by referencing Windows-specific tools and workflows (such as Windows App, Remote Desktop client, and WSL) without providing equivalent instructions or examples for Linux or macOS users. The only mention of Linux is through WSL, which is a Windows feature, and there are no native Linux or macOS setup or connection examples. This may leave non-Windows users unclear on how to use Dev Box tunnels from their platforms.
Recommendations
- Add explicit instructions and screenshots for connecting to Dev Box tunnels from Linux and macOS clients, including any required tools or steps.
- Mention and provide examples for using SSH or other cross-platform remote access methods where applicable.
- Clarify whether the Dev Box extension and tunnel features are fully supported on Linux/macOS, and if not, specify any limitations.
- Provide parity in documentation by listing Linux/macOS steps and tools alongside Windows ones, rather than only referencing Windows-specific features like WSL or Remote Desktop.
- Include troubleshooting steps and FAQs relevant to Linux/macOS users.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-troubleshoot-dev-box-task-view.md
...icles/dev-box/how-to-troubleshoot-dev-box-task-view.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows, with all troubleshooting steps, tools, and UI references specific to Windows (e.g., Task view, Registry Editor, Windows App). There are no Linux or cross-platform examples, and the instructions assume the user is on Windows. Linux users are not addressed, and no equivalent troubleshooting steps or tools are mentioned for non-Windows environments.
Recommendations
- Add a section clarifying whether Task view and Windows App are available or relevant on Linux or macOS. If not, state this explicitly.
- If Linux or macOS clients can connect to dev boxes, provide equivalent troubleshooting steps for those platforms, or link to relevant documentation.
- Mention any cross-platform alternatives or limitations for managing dev boxes from non-Windows systems.
- If the Windows App is available on other platforms, include installation and troubleshooting instructions for those systems.
- Avoid assuming all users are on Windows; structure the documentation to address multiple platforms where possible.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-troubleshoot-repair-dev-box.md
...articles/dev-box/how-to-troubleshoot-repair-dev-box.md
High Priority
View Details →
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 associated with Windows environments. All troubleshooting steps, tool descriptions, and terminology (such as 'Windows Guest OS readiness') are Windows-centric. There are no references to Linux-based dev boxes, alternative remote access protocols (like SSH), or troubleshooting steps relevant to Linux users.
Recommendations
- Include guidance for Linux-based dev boxes, such as troubleshooting SSH connectivity issues.
- Mention and provide examples for alternative remote access protocols (e.g., SSH, VNC) where applicable.
- Clarify whether the Troubleshoot & Repair tool supports non-Windows dev boxes, and if not, provide equivalent troubleshooting steps for Linux environments.
- Add parity in troubleshooting checklists (e.g., 'Linux Guest OS readiness') if Linux dev boxes are supported.
- Ensure screenshots and terminology are inclusive of both Windows and Linux scenarios, or clearly state the scope if only Windows is supported.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-resolve-dev-box-connectivity-issues.md
.../dev-box/how-to-resolve-dev-box-connectivity-issues.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily Windows-centric, providing step-by-step instructions and troubleshooting steps that exclusively reference Windows tools (e.g., Task Manager, reg.exe, Group Policy Editor, registry keys) and Windows-specific processes (msrdc.exe, msrdcw.exe). While there is a brief mention of macOS, there are no examples or guidance for Linux users, nor are Linux-compatible tools or workflows discussed. All registry and policy changes are described only for Windows, and the overall troubleshooting flow assumes a Windows environment.
Recommendations
- Add equivalent troubleshooting steps for Linux users, including how to check and restart RDP clients (such as Remmina, FreeRDP, or rdesktop) on Linux.
- Provide Linux-specific commands for checking process status, killing hung RDP clients, and gathering logs (e.g., using ps, kill, journalctl, or syslog).
- Include instructions for configuring RDP protocol settings (TCP/UDP) on Linux RDP clients, if supported.
- Mention Linux equivalents for Windows tools (e.g., instead of Task Manager, use top/htop/ps; instead of reg.exe, explain relevant config file edits or client settings).
- Ensure that all steps referencing registry or Group Policy changes are either accompanied by Linux/macOS alternatives or clearly marked as Windows-only, with parallel guidance for other platforms.
- Consider restructuring the guide to address all major platforms (Windows, macOS, Linux) in each troubleshooting step, or provide platform-specific sections.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-troubleshoot-remote-desktop-connectivity.md
...box/how-to-troubleshoot-remote-desktop-connectivity.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All troubleshooting steps, examples, and tool references are specific to Windows environments (e.g., Windows Update, Hyper-V, Windows Hello, certutil, PowerShell cmdlets). There are no examples or troubleshooting steps for Linux or macOS clients or dev boxes, nor are cross-platform tools or alternative workflows mentioned. The guidance assumes the user is operating in a Windows-centric environment.
Recommendations
- Add troubleshooting steps and examples for connecting to dev boxes from Linux and macOS clients, including using open-source RDP clients (e.g., Remmina, FreeRDP, rdesktop).
- Include guidance for dev boxes running Linux (if supported), such as handling remote desktop protocols (e.g., xrdp, VNC) and relevant troubleshooting steps.
- When mentioning tools like certutil or PowerShell cmdlets, provide equivalent commands or approaches for Linux/macOS (e.g., using OpenSSL, SSH, or native certificate management tools).
- Avoid assuming Windows as the default environment; structure sections to address both Windows and non-Windows scenarios, or clearly indicate when a step is Windows-specific.
- Reference cross-platform documentation or official Microsoft Remote Desktop clients for Linux/macOS where applicable.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-use-copilot-generate-image-definition-file.md
...x/how-to-use-copilot-generate-image-definition-file.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong Windows bias. It exclusively references Windows-specific tools and patterns, such as WinGet and PowerShell, and mentions User Account Control (UAC) prompts, which are unique to Windows. There are no examples or instructions for Linux or cross-platform environments, and no mention of Linux package managers or shell environments. The workflow assumes the use of Windows-based Dev Boxes and does not address Linux-based development scenarios.
Recommendations
- Include examples and instructions for customizing Linux-based Dev Boxes, if supported.
- Mention Linux equivalents for tools (e.g., apt, yum, bash scripts) alongside WinGet and PowerShell.
- Clarify whether the agentic workflow and imagedefinition.yaml support Linux environments, and provide relevant guidance if so.
- Avoid assuming UAC prompts or other Windows-specific UX patterns; note differences for Linux users.
- Provide at least one Linux-focused prompt or scenario in the natural language examples.
- Explicitly state platform limitations if only Windows is supported, to set user expectations.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-use-secrets-customization-files.md
...cles/dev-box/how-to-use-secrets-customization-files.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides examples using Windows-centric paths (e.g., C:\Workspaces), and references to PowerShell tasks, without any mention of Linux or cross-platform equivalents. There are no examples or guidance for Linux-based Dev Boxes or customization tasks, and all directory and command patterns are Windows-specific.
Recommendations
- Add parallel Linux examples, including directory paths (e.g., /home/dev/Workspaces) and shell commands (e.g., Bash).
- Explicitly mention support for Linux-based Dev Boxes if available, and provide YAML examples that use Linux images and tasks.
- Clarify whether the built-in tasks (like git-clone) are cross-platform, and if so, show usage in both Windows and Linux contexts.
- Avoid using only Windows-specific tools or patterns (like PowerShell) in examples; include Bash or other common Linux shells where appropriate.
- State any platform limitations or differences in secret handling between Windows and Linux Dev Boxes.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-write-image-definition-file.md
...articles/dev-box/how-to-write-image-definition-file.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a strong Windows bias. All examples and built-in tasks focus exclusively on Windows tools such as PowerShell and WinGet, with no mention of Linux equivalents or support. The use of Desired State Configuration (DSC), a PowerShell technology, is highlighted as the primary method for configuration as code. There are no examples or guidance for Linux-based development environments, scripting, or package management tools. The documentation assumes Windows as the default and only supported platform for Dev Box customizations.
Recommendations
- Add explicit statements about platform support (Windows-only or cross-platform) early in the documentation.
- If Linux-based dev boxes are supported, provide equivalent examples using Linux tools (e.g., Bash scripts, apt/yum/dnf/pacman for package management, cloud-init, Ansible, or shell scripts for configuration).
- Include sample YAML image definition files that demonstrate Linux customizations, such as installing packages or configuring user environments.
- Mention and document any limitations or differences in customization capabilities between Windows and Linux dev boxes.
- If Linux is not supported, clearly state this to set user expectations and avoid confusion.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-write-user-customization-file.md
...ticles/dev-box/how-to-write-user-customization-file.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Windows-specific tools and workflows, such as WinGet and Desired State Configuration (DSC), without mentioning or providing equivalent Linux tools or examples. All customization examples and references are tailored to Windows environments, and there is no discussion of Linux-based dev boxes or how to customize them. This may exclude or confuse users who wish to use or manage Linux-based development environments.
Recommendations
- Add examples and guidance for customizing Linux-based dev boxes, including sample YAML files that use Linux package managers (e.g., apt, yum) or shell scripts.
- Mention and provide parity for Linux equivalents to WinGet and DSC, such as using bash scripts, Ansible, or cloud-init for configuration management.
- Explicitly state whether the customization features and Dev Box extension support Linux dev boxes, and if so, provide step-by-step instructions for those scenarios.
- Ensure that references to tools and configuration approaches are not Windows-first; introduce cross-platform options or clarify platform-specific limitations.
- Include screenshots or terminal output from Linux environments where applicable, not just Windows/VS Code on Windows.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/monitor-dev-box.md
...ure-docs/blob/main/articles/dev-box/monitor-dev-box.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides detailed instructions and code samples for enabling diagnostic logging using the Azure Portal and Azure PowerShell, but does not include equivalent examples for Linux users, such as using the Azure CLI (az) or Bash scripts. The only command-line automation shown is via PowerShell, which is primarily a Windows-centric tool, though it is available cross-platform. There are no explicit Linux or Bash examples, and the documentation does not mention or prioritize Linux-native tools or workflows.
Recommendations
- Add equivalent step-by-step instructions and code samples for enabling diagnostic logging using the Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
- Where PowerShell examples are provided, also provide Bash/Azure CLI examples side-by-side or in tabs to ensure parity for Linux users.
- Explicitly mention that PowerShell is available cross-platform, but clarify that Azure CLI is often the default on Linux and macOS.
- Review all sections for references to Windows-specific tools or workflows and ensure Linux alternatives are equally represented and easy to find.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/overview-what-is-microsoft-dev-box.md
...articles/dev-box/overview-what-is-microsoft-dev-box.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation for Microsoft Dev Box demonstrates a Windows-centric bias. It exclusively references Windows tools and management patterns (such as Microsoft Intune, Windows device management, and expedited Windows updates), and does not mention Linux or provide Linux-specific examples or guidance. There is no discussion of Linux-based dev boxes, nor are there examples or instructions for configuring or managing non-Windows environments.
Recommendations
- Explicitly state whether Linux-based dev boxes are supported, and if so, provide examples and guidance for creating and managing Linux dev boxes.
- Include Linux-specific management scenarios, such as integration with Linux configuration management tools or update mechanisms.
- Balance references to Windows tools (like Intune and Windows updates) with equivalent Linux tooling or management strategies.
- Add examples or screenshots that show Linux environments in the Dev Box workflow.
- Clarify any limitations or differences in experience between Windows and Linux dev boxes, if applicable.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/quickstart-configure-dev-box-arm-template.md
...s/dev-box/quickstart-configure-dev-box-arm-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by providing only Azure PowerShell/Windows-centric deployment instructions and code examples. There are no equivalent Linux/bash/CLI examples, and the workflow assumes familiarity with PowerShell and Windows-based tooling. While Azure CLI is briefly mentioned, no concrete Linux or cross-platform instructions are provided.
Recommendations
- Provide equivalent deployment instructions and code examples using Azure CLI (bash) that work natively on Linux and macOS.
- Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select Bash.
- Include sample Bash scripts or CLI commands for each PowerShell example, ensuring parity in guidance.
- Reorder or parallelize instructions so that Linux/macOS (CLI/bash) and Windows (PowerShell) users are equally supported.
- Clarify any platform-specific requirements or differences in the prerequisites and deployment steps.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/quickstart-configure-dev-box-service.md
...ticles/dev-box/quickstart-configure-dev-box-service.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows operating systems (Windows 10/11 Enterprise) and recommending Windows-based images (e.g., 'Visual Studio 2022 Enterprise on Windows 11 Enterprise'). There are no examples or mentions of Linux-based dev box images, nor are Linux tools or workflows discussed. The prerequisites and licensing requirements are also Windows-centric, with no guidance for Linux users or scenarios.
Recommendations
- Explicitly mention support for Linux-based dev box images if available, and provide examples of creating dev box definitions with popular Linux distributions (e.g., Ubuntu, CentOS).
- Include screenshots and walkthroughs for selecting Linux images in the Azure portal.
- Clarify in the prerequisites whether Linux-based dev boxes are supported, and if so, what licensing or identity requirements apply.
- Provide guidance for configuring dev boxes for Linux development workflows, including common tools and environments.
- Ensure parity in documentation by presenting both Windows and Linux options side-by-side where applicable.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/quickstart-get-started-template.md
...in/articles/dev-box/quickstart-get-started-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based licensing, images, and tools. The only dev box image mentioned is 'Visual Studio 2022 Enterprise on Windows 11 Enterprise + Microsoft 365 Apps 24H2', and all licensing requirements are for Windows. There are no examples or mentions of Linux-based dev boxes, nor any guidance for users who may want to use Linux environments. The documentation assumes a Windows-centric workflow and does not provide parity for Linux users.
Recommendations
- Include examples and instructions for deploying Linux-based dev box images, if supported.
- List Linux-compatible licensing and requirements alongside Windows requirements.
- Mention and provide guidance for using Linux tools and environments within Dev Box, if available.
- Ensure screenshots and walkthroughs are not exclusively tied to Windows images or workflows.
- Clarify whether Linux dev boxes are supported or not, and provide links to relevant documentation if they are.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/reference-dev-box-customizations.md
...n/articles/dev-box/reference-dev-box-customizations.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All examples use Windows-specific tools (PowerShell, WinGet), and there is no mention of Linux or cross-platform alternatives. The schema and task definitions assume PowerShell as the scripting environment, and all sample commands and built-in tasks are Windows-centric. There are no examples or guidance for Linux users or for using Bash, shell scripts, or Linux package managers.
Recommendations
- Add examples using Bash or shell scripts for task definitions, alongside PowerShell.
- Document support (or lack thereof) for Linux-based dev boxes, and clarify if only Windows is supported.
- If Linux is supported, provide equivalent built-in tasks for Bash and Linux package managers (e.g., apt, yum, dnf).
- Include Linux image examples in the image attribute section.
- Explicitly state OS compatibility for each built-in task and provide parity where possible.
- Where only Windows is supported, clearly call this out to set expectations for cross-platform users.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. All YAML examples use Windows-style paths (e.g., C:\workspaces), and the example tasks reference Windows images (Win11, Visual Studio). The main scripting example uses PowerShell and the winget package manager, both Windows-specific tools, without providing Linux/macOS alternatives. There are no Linux/macOS-specific examples, nor any mention of equivalent commands or patterns for non-Windows environments.
Recommendations
- Provide parallel examples using Linux/macOS base images and POSIX-style paths (e.g., /workspaces).
- Include alternative scripting examples using Bash or sh, and show how to install Azure CLI on Linux/macOS.
- Mention cross-platform considerations for Dev Box customizations, clarifying which features/tasks are Windows-only and which are supported on other OSes.
- If Dev Box supports Linux/macOS images, add explicit examples and guidance for those platforms.