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 1-25 of 217 flagged pages
Dev Box
Reference: imagedefinition.yaml and task.yaml Files
...n/articles/dev-box/reference-dev-box-customizations.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Windows-specific tools and patterns, such as PowerShell and WinGet, with all examples and built-in tasks referencing these technologies. There are no examples or guidance for Linux/macOS environments, nor mention of cross-platform alternatives. The documentation assumes a Windows base image and scripting environment throughout.
Recommendations
- Add examples and built-in tasks for Linux/macOS environments, such as Bash scripts or Linux package managers (e.g., apt, yum, brew).
- Clarify whether non-Windows base images are supported and provide guidance for customizing them.
- Present cross-platform examples side-by-side, or at least mention Linux/macOS equivalents where applicable.
- Explicitly state any platform limitations or requirements for Dev Box customization tasks.
Create Pull Request
Dev Box
Use modular scripts and files in Dev Box customizations
...les/dev-box/includes/customizations-modular-scripts.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing Windows-centric tools (PowerShell, DSC, WinGet) and providing only Windows-based file paths and examples. There are no Linux/macOS equivalents or examples, and the structure and terminology are tailored to Windows environments. This creates friction for users on non-Windows platforms, as they lack guidance for implementing similar modular script workflows.
Recommendations
- Add examples using Bash scripts, shell scripts, or Ansible for Linux/macOS environments.
- Include Linux/macOS file path conventions and sample image definitions referencing non-Windows scripts.
- Document how Dev Box customizations can be performed on Linux/macOS, including supported tools and workflows.
- Clarify platform limitations and provide parity tables for supported scripting/configuration tools.
Dev Box
Microsoft Dev Box deployment guide
...n/articles/dev-box/concept-dev-box-deployment-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation for Microsoft Dev Box deployment is heavily oriented toward Windows environments, with repeated references to Windows-specific management tools (Intune, Entra ID, Active Directory), Windows device management patterns, and examples involving Windows-centric software installation (WinGet, Chocolatey, PowerShell scripts). There are no examples or guidance for Linux/macOS dev boxes, nor mention of Linux/macOS-specific configuration, management, or customization workflows. All device management and customization sections assume Windows as the target OS, and Windows tools are referenced exclusively and first.
Recommendations
- Explicitly state whether Linux/macOS dev boxes are supported, and if so, provide equivalent examples for image creation, customization, and management.
- Include examples of customization tasks using Linux/macOS package managers (e.g., apt, yum, Homebrew) and shell scripts.
- Document how device management, configuration profiles, and conditional access work for non-Windows dev boxes, or clarify limitations.
- Reference cross-platform tools and workflows (e.g., Ansible, shell scripts) alongside Windows tools like PowerShell.
- Add troubleshooting and monitoring guidance relevant to Linux/macOS dev boxes.
- Ensure that any quick start catalogs or templates include Linux/macOS setup tasks, not just Windows/PowerShell/WinGet/Chocolatey.
Dev Box
Streamline Your Workflow with Dev Box Customizations
...les/dev-box/concept-what-are-dev-box-customizations.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation for Dev Box customizations is heavily oriented toward Windows environments. All examples and instructions reference PowerShell scripts and WinGet tasks, which are Windows-specific tools. There is no mention of Linux/macOS equivalents, nor are alternative scripting or package management approaches discussed. The documentation assumes Windows as the default platform, making it difficult for Linux/macOS users to adapt the instructions.
Recommendations
- Include examples using Bash scripts and Linux/macOS package managers (e.g., apt, yum, brew) alongside PowerShell/WinGet.
- Clarify whether Dev Box supports non-Windows OS images and, if so, provide guidance for customizing those environments.
- Add a section explicitly addressing cross-platform customization strategies and limitations.
- List any platform-specific constraints up front so users can plan accordingly.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All image requirements and examples are exclusively for Windows OS (Windows 10/11 Enterprise), with no mention of Linux or macOS compatibility. All tooling and command-line instructions (e.g., Sysprep, DISM, PowerShell, defrag, chkdsk) are Windows-specific, and there are no Linux equivalents or alternative instructions. The examples and screenshots are Windows-centric, and the workflow assumes a Windows environment throughout.
Recommendations
- Explicitly state whether Linux images are supported or not for Dev Box. If not, clarify the scope early in the documentation.
- If Linux images are supported, provide equivalent instructions for creating, generalizing, and optimizing Linux VM images (e.g., using waagent, cloud-init, relevant disk cleanup commands).
- Include Linux Marketplace image examples if applicable.
- Add parity for command-line instructions, such as Azure CLI or Bash scripts, for Linux users.
- Mention any limitations or differences for Linux/macOS users in the prerequisites and requirements sections.
Dev Box
Configure hibernation for Microsoft Dev Box
...ticles/dev-box/how-to-configure-dev-box-hibernation.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page for configuring hibernation in Microsoft Dev Box demonstrates a Windows bias. All example commands and configuration steps reference Windows-specific settings, tools, and images (such as Windows Security, Memory Integrity, and the Windows Start menu). There are no examples or guidance for Linux-based dev boxes, nor any mention of Linux compatibility or equivalent settings. Troubleshooting and compatibility sections focus exclusively on Windows images and configurations.
Recommendations
- Explicitly state whether hibernation is supported for Linux-based dev boxes, and if not, clarify this early in the documentation.
- If Linux support exists, provide equivalent instructions, examples, and troubleshooting steps for Linux images (e.g., how to enable nested virtualization, disable incompatible features, etc.).
- Include CLI examples with --os-type linux and discuss any differences in flags or requirements.
- Mention Linux-specific considerations or limitations in the 'Considerations' and 'Troubleshooting' sections.
- Add links to Linux VM image documentation where relevant.
High Priority
View Details →
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 is no guidance for users who wish to customize Dev Boxes with Bash scripts, Linux tools, or cross-platform approaches.
Recommendations
- Include examples of tasks using Bash scripts and Linux/macOS tools in addition to PowerShell.
- Explicitly state whether Dev Box supports Linux/macOS images and, if so, provide instructions for customizing those environments.
- Add documentation for using cross-platform scripting languages (e.g., Python, Node.js) in tasks.
- Mention and provide examples for Linux package managers (e.g., apt, yum) if supported.
- Clarify any platform limitations and provide parity guidance for non-Windows users.
Dev Box
Configure Intune Endpoint Privilege Management
...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 is strongly focused on Windows environments, with all examples, procedures, and requirements referencing Windows tools, OS versions, and workflows. There are no Linux or macOS equivalents mentioned, and all instructions assume the use of Windows dev boxes. The Endpoint Privilege Management feature is described only in the context of Windows 10/11, and verification steps reference Windows-specific UI and file paths.
Recommendations
- Explicitly state whether Endpoint Privilege Management supports Linux/macOS dev boxes, and if not, provide guidance or alternatives for privilege management on those platforms.
- If Linux/macOS support exists, add equivalent setup, policy deployment, and verification instructions for those platforms.
- Include a comparison table of supported operating systems and note feature parity or limitations.
- Mention Linux/macOS tools or patterns for privilege management where relevant, or link to related documentation.
Dev Box
Configure virtual switches for dev boxes
...icles/dev-box/how-to-connect-dev-box-virtual-switch.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses Windows-centric tools (Hyper-V, PowerShell cmdlets) and provides only Windows-based instructions and screenshots. There are no Linux/macOS equivalents or guidance, and all examples are given in PowerShell, with terminology and steps tailored to Windows environments.
Recommendations
- Add instructions for configuring virtual switches and NAT networks using Linux tools (e.g., KVM, libvirt, iptables, bridge-utils).
- Include example commands for Linux (bash) and macOS (if supported).
- Clarify platform requirements and limitations at the start of the document.
- Provide parity in screenshots and UI walkthroughs for non-Windows platforms where possible.
- Explicitly mention if the feature is Windows-only, or provide alternative approaches for Linux/macOS users.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell. All setup, configuration, and usage examples are provided exclusively in Azure PowerShell, with explicit references to installing Azure PowerShell on Windows. There are no Linux/macOS command examples, nor any mention of Linux tools or shell equivalents. The image customization steps use Windows-specific tools (Chocolatey, PowerShell scripts), and the template is for a Windows 11 image only.
Recommendations
- Provide equivalent Azure CLI examples for all major steps, as Azure CLI is cross-platform.
- Include instructions for installing Azure PowerShell on Linux/macOS, or clarify that Azure CLI can be used.
- Offer a Linux-based image template example, or explain how to adapt the process for Linux images.
- Show how to customize images using shell scripts (bash) for Linux, not just PowerShell for Windows.
- Reorder prerequisites and examples so that cross-platform tools (Azure CLI) are presented first or in parallel with PowerShell.
- Explicitly state which steps are Windows-specific and which are applicable to Linux/macOS.
Dev Box
Configure Visual Studio caches for your dev box image
...ticles/dev-box/how-to-generate-visual-studio-caches.md
High Priority
View Details →
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. The only example for generating Visual Studio caches uses a Windows-specific tool (devenv.exe) and PowerShell syntax, with no mention of Linux/macOS equivalents or cross-platform alternatives. Windows tools and patterns are referenced exclusively, and Linux/macOS users are not provided with guidance or examples for similar workflows.
Recommendations
- Explicitly state platform limitations: If Visual Studio cache generation is only supported on Windows, clarify this early in the documentation.
- Provide Linux/macOS alternatives: If possible, offer guidance for users developing on Linux/macOS, such as using Visual Studio Code or other IDEs, and describe any available caching or performance optimization workflows.
- Include cross-platform scripting examples: Where possible, add bash or shell script equivalents alongside PowerShell commands.
- Mention platform support matrix: Add a table or section listing which features are available on Windows, Linux, and macOS.
- Reference cross-platform tools: If Git optimizations apply to all platforms, clarify that those steps are platform-agnostic.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with nearly all troubleshooting steps, tools, and examples focused on Windows clients and Windows-based dev boxes. Windows-specific tools (e.g., Windows App, gpedit.msc, Registry Editor, dsregcmd.exe, reg.exe) are mentioned exclusively or before any macOS alternatives, while Linux clients are not addressed at all. Mac instructions are present only for one scenario, and Linux is entirely omitted.
Recommendations
- Add troubleshooting steps and examples for Linux clients, including how to connect to dev boxes from Linux and how to configure remote desktop settings (e.g., switching to TCP) using Linux tools.
- Provide parity in examples: for every Windows-specific command or tool (e.g., dsregcmd.exe, reg.exe, gpedit.msc), include equivalent steps for Linux/macOS where possible, or clarify if not applicable.
- Mention cross-platform remote desktop clients (e.g., FreeRDP, Remmina) and how to use them with Dev Box.
- Clarify which steps are Windows-only and provide alternative guidance for non-Windows users.
- Reorder sections or provide tabs so that Windows, macOS, and Linux instructions are presented equally and clearly.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias, with troubleshooting steps, examples, and tools focused exclusively on Windows environments. All instructions reference Windows-specific features, tools (such as Windows App, Windows Hello, Hyper-V, certutil), and UI elements, with no mention of Linux or macOS equivalents or guidance. There are no examples or troubleshooting steps for connecting to or using dev boxes from Linux/macOS clients, nor for resolving issues in non-Windows environments.
Recommendations
- Add troubleshooting steps and examples for Linux and macOS users, including common connectivity and sign-in issues.
- Mention and provide guidance for alternative remote desktop clients available on Linux/macOS (e.g., Remmina, FreeRDP, Microsoft Remote Desktop for Mac).
- Include instructions for resolving certificate and authentication issues on Linux/macOS clients.
- Clarify which issues and solutions are Windows-specific, and provide parity for equivalent issues on other platforms.
- Add notes about Teams, virtualization, and hardware compatibility for Linux/macOS dev boxes if supported.
Dev Box
Create Dev Box Image Definition Files for Team Customizations
...ticles/dev-box/how-to-configure-team-customizations.md
High Priority
View Details →
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 technologies such as PowerShell, WinGet, and Desired State Configuration (DSC), with no mention of Linux/macOS equivalents or cross-platform alternatives. All examples and built-in tasks are Windows-specific, and there are no instructions or guidance for customizing dev boxes using Linux shell scripts, package managers (e.g., apt, yum, Homebrew), or other non-Windows tools. The documentation assumes a Windows environment for both the dev box and the customization workflow.
Recommendations
- Add examples and guidance for customizing dev boxes using Linux/macOS tools (e.g., Bash, shell scripts, apt, yum, Homebrew).
- Clarify whether Dev Box supports Linux-based dev boxes and, if so, provide parity in documentation for Linux/macOS workflows.
- Include sample image definition files that use cross-platform or Linux-specific tasks.
- Explicitly state platform limitations and provide links to Linux/macOS documentation if available.
- Mention and document any built-in tasks or catalog support for Linux/macOS environments.
Dev Box
Configure virtual switches for dev boxes
...icles/dev-box/how-to-connect-dev-box-virtual-switch.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased toward Windows, providing only PowerShell commands and referencing Windows-specific tools (Hyper-V, New-VMSwitch, New-NetIPAddress, New-NetNat). There are no Linux/macOS equivalents or instructions, and all examples and screenshots are Windows-centric. This makes it difficult or impossible for Linux/macOS users to follow the guide.
Recommendations
- Add equivalent instructions for Linux (e.g., using KVM/QEMU and Linux bridge/NAT setup).
- Include CLI examples for Linux (such as ip, brctl, virsh, or nmcli).
- Clarify platform requirements at the start (e.g., 'This guide is for Windows dev boxes only').
- Provide parity in screenshots and UI navigation for Linux environments.
- If Dev Box only supports Windows, explicitly state this limitation.
Dev Box
Authoring recommendations for Dev Box image definitions
...pt-authoring-troubleshooting-guide-team-customizations.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with exclusive references to Windows tools (WinGet, PowerShell), Windows file paths, and Windows-specific troubleshooting steps. All examples and instructions assume a Windows OS, with no mention of Linux/macOS alternatives or parity. This creates friction for users who may wish to author or test Dev Box image definitions from non-Windows platforms.
Recommendations
- Provide Linux/macOS equivalents for all CLI commands and troubleshooting steps (e.g., log locations, permissions).
- Include examples using Bash, shell scripts, or cross-platform tools where possible, not just PowerShell.
- Clarify which features or steps are Windows-only and suggest alternatives or workarounds for Linux/macOS users.
- Document any limitations or requirements for authoring/testing Dev Box image definitions on non-Windows platforms.
- Add notes or sections specifically addressing Linux/macOS developer workflows, especially for local testing and debugging.
Dev Box
Microsoft Dev Box deployment guide
...n/articles/dev-box/concept-dev-box-deployment-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation for Microsoft Dev Box deployment is heavily oriented toward Windows environments. It assumes Windows as the default OS for dev boxes, references Windows-specific management tools (Intune, Endpoint Privilege Management), and only provides examples for Windows (e.g., WinGet, Chocolatey, PowerShell scripts) in customization tasks. There is no mention of Linux or macOS dev box scenarios, nor are there examples or guidance for deploying or managing non-Windows dev boxes.
Recommendations
- Explicitly state whether Linux/macOS dev boxes are supported, and if so, provide guidance for their deployment and management.
- Include examples of customization tasks for Linux (e.g., using apt, yum, shell scripts) and macOS (e.g., Homebrew, shell scripts).
- Clarify which features (Intune, Endpoint Privilege Management, device configuration profiles) are Windows-only and suggest alternatives for Linux/macOS management.
- Add sections or notes for cross-platform considerations, such as image creation, software installation, and device management for Linux/macOS.
- Provide parity in troubleshooting and monitoring guidance for Linux/macOS dev boxes if supported.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily Windows-centric, with all image requirements, examples, and tooling focused exclusively on Windows OS and Windows-specific tools (e.g., PowerShell, DISM, sysprep). There are no Linux or macOS equivalents, nor any mention of support for non-Windows images or workflows. This creates significant friction for users on Linux/macOS, who cannot follow the instructions or use the service for non-Windows workloads.
Recommendations
- Explicitly state that only Windows images are supported, if that is the case, or clarify any future plans for Linux/macOS support.
- If Linux images are supported, add equivalent instructions and examples for creating, generalizing, and optimizing Linux VM images (e.g., using waagent, cloud-init, shell commands).
- Provide parity in CLI examples (e.g., Bash/Azure CLI commands alongside PowerShell).
- Mention Linux tools and patterns where relevant (e.g., disk cleanup, partition management, virtualization features).
- If the service is Windows-only, add a prominent note at the top to inform non-Windows users.
Dev Box
Configure hibernation for Microsoft Dev Box
...ticles/dev-box/how-to-configure-dev-box-hibernation.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation for configuring hibernation in Microsoft Dev Box is heavily Windows-centric. It references Windows-specific features (such as Memory Integrity, Virtual Machine Platform, and Windows Security), provides step-by-step instructions only for Windows OS, and does not mention Linux or macOS equivalents or considerations. All CLI examples assume Windows images, and troubleshooting is focused on Windows VM issues. There is no guidance for Linux-based dev boxes, nor any mention of Linux compatibility, limitations, or configuration steps.
Recommendations
- Explicitly state whether hibernation is supported for Linux/macOS dev boxes, and document any limitations.
- Provide equivalent instructions for Linux-based dev boxes, including how to enable/disable hibernation and any required OS settings.
- Include CLI examples for Linux images (e.g., using --os-type linux) and clarify any differences in flags or prerequisites.
- Add troubleshooting guidance for Linux-based dev boxes, if supported.
- If hibernation is not supported for Linux/macOS, clearly document this at the beginning of the article.
Dev Box
Configure Intune Endpoint Privilege Management
...n/articles/dev-box/how-to-elevate-privilege-dev-box.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily focused on Windows, with all examples, procedures, and requirements referencing Windows-specific tools, OS versions, and UI elements. There is no mention of Linux or macOS support, nor any guidance for non-Windows dev boxes. The steps assume the use of Windows 10/11 and Windows UI conventions, and Endpoint Privilege Management appears to be a Windows-only feature.
Recommendations
- Explicitly state OS support and limitations at the beginning of the documentation.
- If Endpoint Privilege Management is Windows-only, clarify this for cross-platform users.
- If Linux/macOS support is planned or available, provide equivalent instructions, examples, and screenshots for those platforms.
- Offer alternative privilege management solutions or references for Linux/macOS dev boxes.
- Reorder prerequisites and instructions to mention platform limitations before diving into Windows-specific steps.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell. All setup, configuration, and usage examples are provided exclusively in Azure PowerShell, with no Azure CLI or Bash alternatives. Windows-specific tools and patterns (such as Chocolatey, sysprep, and Windows image SKUs) are referenced throughout, and instructions for installing Azure PowerShell are only given for Windows. There is no guidance for Linux/macOS users, nor are cross-platform alternatives or considerations mentioned.
Recommendations
- Provide equivalent Azure CLI and Bash examples for all PowerShell commands.
- Include instructions for installing Azure PowerShell on Linux and macOS, or recommend Azure CLI for cross-platform usage.
- Mention Linux image building scenarios and provide sample templates for Linux images.
- Avoid using Windows-specific tools (e.g., Chocolatey) in general examples, or provide Linux alternatives (e.g., apt, yum) where relevant.
- Clearly indicate which steps are Windows-only and provide guidance for Linux/macOS users where possible.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation is heavily Windows-centric, with most troubleshooting steps, tools, and examples tailored for Windows environments. Windows-specific tools (e.g., Windows App, Group Policy Editor, Registry Editor, dsregcmd.exe) are referenced exclusively or before alternatives. Mac is mentioned only in one section, and Linux is not addressed at all, leaving Linux users without guidance for connectivity troubleshooting.
Recommendations
- Add explicit troubleshooting steps and examples for Linux clients, including how to connect to Dev Box from Linux (e.g., using RDP clients like Remmina, FreeRDP, or xfreerdp).
- Provide Linux equivalents for registry and group policy changes, such as configuration file edits or command-line flags for RDP clients.
- Include Linux-specific authentication troubleshooting steps, such as checking Entra ID join status or token refresh procedures.
- Mention and link to cross-platform remote desktop tools and clarify which features are available on each OS.
- Present examples for all platforms (Windows, macOS, Linux) side-by-side, rather than Windows-first.
Dev Box
Configure Visual Studio caches for your dev box image
...ticles/dev-box/how-to-generate-visual-studio-caches.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows environments. All examples for generating Visual Studio caches use PowerShell and Windows-specific tools (devenv.exe), with no mention of Linux/macOS alternatives or parity. The instructions assume the use of Visual Studio on Windows, and do not address cross-platform scenarios or provide guidance for non-Windows users.
Recommendations
- Clarify that Visual Studio cache generation is only supported on Windows, if true, and explicitly state platform limitations.
- If Linux/macOS support exists (e.g., via Visual Studio Code or other tools), provide equivalent instructions and examples for those platforms.
- Offer guidance for cross-platform teams, such as how to handle cache generation when some developers use Linux/macOS.
- Include a note on alternative IDEs or workflows for non-Windows users, if Visual Studio cache precaching is not available.
- Present any platform-agnostic steps (such as git commit-graph optimization) before Windows-specific instructions.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily focused on Windows environments, with troubleshooting steps, examples, and tools almost exclusively referencing Windows-specific features, commands, and issues. There are no Linux or macOS-specific troubleshooting steps, examples, or tool references, and Windows terminology and tools (such as Windows Hello, Hyper-V, Windows App, certutil, and Windows Update) are used throughout without mention of cross-platform alternatives or parity.
Recommendations
- Add troubleshooting steps and examples for Linux/macOS clients connecting to dev boxes, including common connectivity, sign-in, and performance issues.
- Include Linux/macOS equivalents for Windows-specific tools and commands (e.g., alternatives to certutil, Hyper-V, Windows Hello).
- Mention and provide guidance for connecting to dev boxes from Linux/macOS, including supported apps and configuration steps.
- Clearly indicate which troubleshooting steps are Windows-only and provide parallel instructions for other platforms where possible.
- Add sections or notes about platform-specific limitations and workarounds for Linux/macOS users.
Dev Box
Resolve connectivity issues with Troubleshoot and Repair
...articles/dev-box/how-to-troubleshoot-repair-dev-box.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation focuses exclusively on troubleshooting Remote Desktop Protocol (RDP) connectivity, which is primarily a Windows technology. All examples and checks (such as 'Windows Guest OS readiness') are Windows-centric, and there are no references to Linux/macOS remote access methods (e.g., SSH, VNC) or troubleshooting steps for non-Windows dev boxes. The troubleshooting tool and workflow are described only in the context of Windows environments, with no mention of Linux or macOS alternatives.
Recommendations
- Include troubleshooting steps for Linux/macOS dev boxes, such as SSH connectivity issues.
- Add examples and tool descriptions relevant to Linux (e.g., SSH daemon status, firewall rules) and macOS.
- Clarify whether the Troubleshoot & Repair tool supports non-Windows dev boxes, and document any limitations.
- Provide parity in documentation by listing Linux/macOS troubleshooting methods alongside Windows/RDP steps.
- Mention alternative remote access protocols (e.g., SSH, VNC) and how to resolve issues with them.