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 126-150 of 217 flagged pages
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-what-are-dev-box-customizations.md
...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 page demonstrates a Windows bias by exclusively referencing PowerShell scripts and WinGet (both Windows-specific tools) as the primary and recommended methods for Dev Box customizations. There are no examples or mentions of Linux shell scripting, Linux package managers, or cross-platform alternatives. The language and examples assume a Windows environment, and Linux or macOS scenarios are not addressed.
Recommendations
- Include examples of using Bash scripts or other Linux shell scripts as customization tasks, if supported by Dev Box.
- Document support (or lack thereof) for Linux-based Dev Boxes, and clarify whether customizations can be applied to non-Windows environments.
- If Dev Box supports Linux images, provide equivalent instructions for using Linux-native tools (e.g., apt, yum, zypper) in customization tasks.
- Mention cross-platform scripting options (such as Python or Node.js scripts) if applicable.
- Explicitly state platform limitations and provide guidance for users who require Linux or macOS development environments.
Create Pull Request
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-customizations-connect-resource-repository.md
...x/how-to-customizations-connect-resource-repository.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), Windows images (e.g., microsoftwindowsdesktop_windows-ent-cpc_win11-24H2-ent-cpc), and PowerShell tasks. There are no examples or guidance for Linux-based Dev Boxes, Linux file paths, or Linux shell commands, which may disadvantage users working in Linux environments.
Recommendations
- Add parallel examples using Linux-based images (e.g., Ubuntu) in the YAML samples.
- Include Linux file paths (e.g., /home/dev/Workspaces) alongside Windows paths in examples.
- Demonstrate use of Linux shell commands (e.g., bash) in addition to PowerShell tasks.
- Explicitly mention support for both Windows and Linux Dev Boxes, if applicable, and clarify any limitations.
- Ensure that any tooling or workflow described (such as cloning repositories) is shown in a cross-platform manner.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-azure-compute-gallery.md
...cles/dev-box/how-to-configure-azure-compute-gallery.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 example images are Windows-based (Visual Studio on Windows), and the image requirements are exclusively for Windows OS (Windows 10/11 Enterprise). All command-line and configuration instructions use Windows-specific tools (PowerShell, DISM.exe, chkdsk, defrag), and UI instructions reference Windows features. There are no examples, instructions, or references for Linux images, tools, or workflows. Linux is not mentioned as a supported or considered platform.
Recommendations
- Add explicit guidance on whether Linux images are supported for Dev Box, and if so, provide equivalent Linux image requirements.
- Include examples of creating and preparing Linux images for use in Azure Compute Gallery, including references to Linux-compatible tools (e.g., waagent, cloud-init, relevant shell commands).
- For each Windows-specific command or tool (e.g., sysprep, DISM, chkdsk, defrag), provide Linux equivalents or note if not applicable.
- Clarify in prerequisites and requirements sections if the service is Windows-only, or explicitly state Linux support status.
- Where UI or portal instructions are given, note any differences or additional steps for Linux-based images if supported.
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 demonstrates a Windows bias by exclusively referencing Windows-based licensing (Windows 10/11 Enterprise), using a Windows-based image (Visual Studio 2022 Enterprise on Windows 11 Enterprise), and omitting any mention of Linux-based dev box images or workflows. There are no examples or instructions for deploying or configuring Linux environments, nor are Linux tools or patterns referenced.
Recommendations
- Include examples or options for deploying Linux-based dev box images, if supported.
- Mention Linux-compatible licensing or requirements where applicable.
- Provide screenshots and walkthroughs for setting up a Linux dev box environment alongside Windows examples.
- Reference Linux tools, shells, or development patterns where relevant.
- Clarify in prerequisites and throughout the guide whether Linux is supported, and if not, explicitly state this to set user expectations.
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 First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by focusing exclusively on Windows-based tools, services, and terminology (e.g., Windows 365, Microsoft Remote Desktop, Windows Azure Service Management API) without mentioning or providing equivalent Linux tools or workflows. There are no examples or guidance for Linux users, and all app references and scenarios assume a Windows-centric environment.
Recommendations
- Include explicit guidance or notes for Linux users, such as how to access Dev Boxes from Linux clients using supported RDP clients (e.g., FreeRDP, Remmina) or via browser.
- List and describe cross-platform or Linux-compatible tools for connecting to Dev Boxes, not just Microsoft Remote Desktop.
- Clarify whether Conditional Access policies and Dev Box management are supported from Linux environments, and provide examples or links to relevant documentation.
- Add a section or callout addressing Linux developer scenarios, including any limitations or required configurations.
- Ensure that app tables and scenario descriptions mention Linux compatibility or alternatives where applicable.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-network-connections.md
...ticles/dev-box/how-to-configure-network-connections.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Microsoft-centric tools and patterns (Azure portal, Active Directory, Microsoft Entra join/hybrid join) without mentioning or providing parity for Linux-based workflows, tools, or directory services. There are no Linux command-line examples, nor is there guidance for users who might manage networks or authentication using Linux-native tools or open standards. The linked 'Network requirements' page is under a Windows-365 path, reinforcing the Windows-centric approach.
Recommendations
- Include examples or references for managing network connections using Azure CLI, which is cross-platform and commonly used on Linux.
- Mention or provide guidance for integrating with non-Active Directory identity providers or open standards (e.g., LDAP, Kerberos) where possible.
- Clarify whether Linux-based dev boxes are supported and, if so, provide specific instructions or considerations for Linux environments.
- Add notes or sections for users who may be managing network connections from Linux or macOS systems, including relevant tools and commands.
- Balance references to Windows-specific tools with cross-platform alternatives (e.g., Azure CLI, REST API) and ensure documentation is inclusive of non-Windows workflows.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-what-are-dev-box-customizations.md
...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 page demonstrates a strong Windows bias by exclusively referencing PowerShell scripts and WinGet tasks as the primary means for Dev Box customization. There is no mention of Linux shell scripting, Bash, or Linux package managers, nor are there examples or guidance for non-Windows environments. The documentation assumes a Windows-centric workflow and does not address Linux developer scenarios.
Recommendations
- Include examples and guidance for Linux-based Dev Boxes, such as using Bash scripts and Linux package managers (e.g., apt, yum, zypper) in customization tasks.
- Explicitly state whether Dev Box supports Linux images and, if so, provide parity in documentation for Linux customization workflows.
- Add sample YAML customization files that use Linux scripting and tools, alongside the existing PowerShell/WinGet examples.
- Clarify in the documentation if certain features are Windows-only, and provide alternative approaches for Linux users where possible.
- Mention and document the use of cross-platform scripting (e.g., Python, Node.js) for tasks that need to run on both Windows and Linux Dev Boxes.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-customize-devbox-azure-image-builder.md
...dev-box/how-to-customize-devbox-azure-image-builder.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 and PowerShell. All code examples use PowerShell, and instructions reference Windows-specific tools and file paths (e.g., c:/temp). There is no mention or example of using Linux or Bash, and the image creation process is demonstrated only for Windows images. Even where the Azure CLI is mentioned, no CLI or Linux/Bash examples are provided. The customization step in the image template uses PowerShell scripts and Windows-specific package managers (Chocolatey), with no Linux alternatives.
Recommendations
- Provide parallel examples using Azure CLI and Bash for each PowerShell example, including registration, identity creation, and deployment steps.
- Include instructions and examples for creating Linux images, not just Windows images.
- When referencing file paths, use cross-platform notation or provide both Windows and Linux path examples.
- Show how to customize images using Linux shell scripts and package managers (e.g., apt, yum) in the image template.
- Explicitly state support for Linux where applicable, or clarify if the process is Windows-only.
- Balance the order of presentation so that Linux and Windows approaches are given equal prominence.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-manage-dev-box-definitions.md
.../articles/dev-box/how-to-manage-dev-box-definitions.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing Windows images (e.g., Windows 11 Enterprise, Visual Studio on Windows) and Microsoft 365 apps. There are no mentions or examples of Linux-based images, nor any guidance for configuring or using Linux dev boxes. All recommended images and scenarios are Windows-centric, and the documentation does not acknowledge or provide parity for Linux development environments.
Recommendations
- Explicitly mention support (or lack thereof) for Linux images in Microsoft Dev Box, and if supported, provide examples for selecting and configuring Linux-based dev box definitions.
- Include Linux image options in the 'Image' selection step, such as Ubuntu or other popular distributions, and provide example use cases for Linux development teams.
- Offer guidance on configuring dev box definitions for Linux development, including recommended images, tools, and best practices.
- Balance the documentation by presenting both Windows and Linux scenarios, ensuring that Linux development teams are equally supported.
- If Linux is not supported, clearly state this limitation early in the documentation to set user expectations.
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 highlighted as the default and recommended client for connecting to dev boxes, with detailed instructions and screenshots for Windows and legacy Remote Desktop clients. There is no mention of Linux-specific remote desktop clients or workflows, nor are there any Linux command-line or desktop environment examples. The browser-based connection is mentioned as an alternative, but Linux users are not directly addressed, and Linux-native tools are not discussed.
Recommendations
- Include explicit instructions and examples for connecting to a dev box from Linux systems, such as using open-source RDP clients (e.g., Remmina, FreeRDP, rdesktop) or relevant Linux packages.
- Mention Linux compatibility and provide parity in guidance for Linux users alongside Windows and macOS.
- Add screenshots or CLI examples from a Linux environment where applicable.
- Clarify whether the 'Windows App' is available or supported on Linux (e.g., via web or preview builds), and if not, suggest alternatives.
- Ensure that any references to remote desktop clients or connection methods are platform-neutral or provide equal detail for Linux users.
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 exclusively discusses troubleshooting Remote Desktop (RDP) connectivity to dev boxes, focusing on Windows-specific tools and concepts. All examples and checks are centered around Windows environments (e.g., RDP, Windows Guest OS readiness), with no mention of Linux-based dev boxes, alternative remote protocols (like SSH), or Linux troubleshooting steps. This creates a strong Windows-first impression and omits guidance for users of Linux dev boxes.
Recommendations
- Explicitly state whether the Troubleshoot & Repair tool supports Linux-based dev boxes, and if not, clarify its scope.
- Include troubleshooting steps and examples for Linux dev boxes, such as SSH connectivity issues, relevant diagnostic checks, and Linux guest OS readiness.
- Mention Linux remote access protocols (e.g., SSH, VNC) alongside RDP where appropriate.
- Provide parity in documentation by listing both Windows and Linux troubleshooting scenarios, tools, and expected outcomes.
- If the tool is Windows-only, add a section for Linux users with alternative troubleshooting resources or a roadmap for future support.
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 focusing on Visual Studio and Microsoft Dev Box, which are Windows-centric. All command-line examples use PowerShell and Windows tools (e.g., devenv.exe), with no mention of Linux equivalents or cross-platform alternatives. There are no instructions or examples for performing similar tasks on Linux-based dev boxes, nor is there guidance for non-Windows environments.
Recommendations
- Provide equivalent instructions and examples for Linux environments, such as using VS Code or cross-platform .NET CLI tools for solution caching.
- Include bash or shell script examples alongside PowerShell commands where possible.
- Clarify whether the described features (e.g., Visual Studio solution cache, commit-graph optimizations) are available or relevant on Linux-based dev boxes, and if not, explicitly state this.
- Mention cross-platform alternatives (e.g., Rider, VS Code, or MonoDevelop) and how to optimize their startup or cache behavior if applicable.
- Reorganize sections to avoid implicit prioritization of Windows tools and workflows, or add a 'Platform support' section to clarify scope.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-dev-box-hibernation.md
...ticles/dev-box/how-to-configure-dev-box-hibernation.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows environments, with all configuration steps, compatibility notes, and troubleshooting focused exclusively on Windows OS and tooling. There are no references to Linux or cross-platform scenarios, and all examples (including UI steps and CLI flags) assume Windows-based images and features. Linux users or those interested in non-Windows dev boxes are not addressed.
Recommendations
- Explicitly state whether hibernation is supported or not for Linux-based dev boxes, and provide parity guidance if/when it is.
- If Linux support exists, add equivalent Linux image configuration steps (e.g., for Ubuntu or other supported distros), including CLI flags and any required OS settings.
- Include troubleshooting steps and compatibility notes for Linux images, or clarify if only Windows images are supported.
- Where possible, use neutral language (e.g., 'your OS' or 'the guest OS') and provide both Windows and Linux UI/CLI examples.
- If hibernation is a Windows-only feature, clearly state this at the top of the documentation to set expectations for cross-platform users.
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 towards Windows environments. All examples and built-in tasks focus exclusively on Windows tools such as PowerShell and WinGet. There are no mentions or examples of Linux-based tools, shell scripts, or cross-platform alternatives. The schema and task definitions assume PowerShell as the scripting language, and all sample commands are Windows-specific. No Linux or bash equivalents are provided, and the documentation does not address how to customize Dev Box environments for non-Windows images.
Recommendations
- Add examples and schema references for Linux-based Dev Box images, including the use of bash or shell scripts.
- Introduce built-in tasks for common Linux tools (e.g., bash, apt, yum) alongside PowerShell and WinGet.
- Provide parallel Linux examples for each Windows example, demonstrating how to achieve similar customizations on Linux environments.
- Clarify in the documentation whether Linux-based Dev Boxes are supported, and if so, how to author cross-platform or Linux-specific tasks.
- Consider abstracting task definitions to allow specifying the shell or interpreter (e.g., 'shell: bash' or 'shell: powershell') to support both Windows and Linux environments.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/quickstart-create-dev-box.md
...lob/main/articles/dev-box/quickstart-create-dev-box.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively mentioning the Windows App as the method for connecting to a dev box, without providing equivalent instructions or references for Linux (or macOS) users. There are no examples or guidance for connecting from Linux devices, and Windows tooling is presented as the default and only option.
Recommendations
- Add explicit instructions for connecting to a dev box from Linux (and macOS) devices, such as using open-source RDP clients (e.g., Remmina, FreeRDP, rdesktop) or web-based access if available.
- Mention and provide download links for cross-platform clients alongside the Windows App, making it clear that non-Windows users are supported.
- Include example connection steps or screenshots for Linux users to ensure parity and inclusivity.
- Avoid language that implies Windows is the only or primary supported platform; instead, clarify support for multiple operating systems where applicable.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-connect-dev-box-virtual-switch.md
...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-specific tools and commands (PowerShell, Hyper-V, Windows network configuration dialogs) for configuring virtual switches, without providing any Linux equivalents or cross-platform guidance. All examples and instructions assume a Windows environment, and there is no mention of how to achieve similar results on Linux-based dev boxes or with Linux virtualization technologies.
Recommendations
- Provide parallel instructions for Linux environments, such as using libvirt/virt-manager, KVM, or other Linux virtualization tools.
- Include example commands for creating virtual switches and NAT networks on Linux (e.g., using virsh, nmcli, or iptables/nftables).
- Mention Linux prerequisites (e.g., KVM, bridge-utils) alongside Windows prerequisites.
- Add screenshots or configuration steps for Linux network settings where applicable.
- Clarify in the introduction that the guide is Windows-specific, or restructure to present both Windows and Linux options equally.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-customize-devbox-azure-image-builder.md
...dev-box/how-to-customize-devbox-azure-image-builder.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 and PowerShell. All command-line examples use PowerShell, and the prerequisites specifically mention installing Azure PowerShell on Windows. There are no examples or instructions for using Linux or Bash, and the image customization steps use Windows-specific tools (e.g., Chocolatey, PowerShell scripts). The template and gallery creation steps assume a Windows environment, and file paths use Windows conventions (e.g., c:/temp/mytemplate.txt). Azure CLI is mentioned only in passing, with no examples provided.
Recommendations
- Provide parallel examples using Azure CLI and Bash for Linux/macOS users.
- Include instructions for installing Azure CLI and/or PowerShell on Linux and macOS.
- Show how to create and edit template files using cross-platform file paths (e.g., /tmp/mytemplate.txt).
- Offer a Linux-based image customization example (e.g., using shell scripts and apt/yum instead of PowerShell and Chocolatey).
- Explicitly state which steps are Windows-specific and provide alternatives for Linux where possible.
- Reorder or balance the presentation so that Linux and Windows approaches are given equal prominence.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-dev-box-architecture.md
.../main/articles/dev-box/concept-dev-box-architecture.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation for Microsoft Dev Box architecture exhibits a Windows-centric bias. It exclusively references Windows management tools (e.g., Microsoft Intune), Windows device management, and Windows-specific identity services (Microsoft Entra join/hybrid join, Active Directory). There are no examples or mentions of Linux-based dev boxes, Linux management tools, or cross-platform development scenarios. The documentation assumes the dev box is a Windows VM and does not address Linux developer needs.
Recommendations
- Explicitly state whether Linux-based dev boxes are supported or not. If supported, provide equivalent guidance for Linux dev boxes, including management, connectivity, and configuration.
- Include examples and references for managing Linux dev boxes (e.g., using SSH for connectivity, Linux configuration management tools, and relevant identity integration).
- Mention cross-platform development scenarios and how Microsoft Dev Box can be used for non-Windows environments.
- If only Windows is supported, clarify this limitation early in the documentation to set expectations for Linux users.
- Provide parity in documentation structure and detail for both Windows and Linux environments if both are supported.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-dev-box-deployment-guide.md
...n/articles/dev-box/concept-dev-box-deployment-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page for Microsoft Dev Box deployment is heavily oriented toward Windows environments. It references Windows-specific management tools (Microsoft Intune, Entra ID, Active Directory), and all device management and configuration examples assume Windows as the guest OS. There are no examples or mentions of Linux-based dev boxes, Linux management tools, or cross-platform considerations. Windows tools and patterns are discussed exclusively, with no Linux equivalents or alternatives provided.
Recommendations
- Explicitly state whether Linux-based dev boxes are supported or not. If supported, provide parallel guidance for deploying, configuring, and managing Linux dev boxes.
- Include examples and documentation for managing Linux dev boxes, such as using Azure CLI, SSH, or Linux-native configuration management tools.
- Mention Linux-compatible alternatives to Windows-specific tools (e.g., alternatives to Intune for Linux, or how to manage Linux device configuration and access control).
- Provide sample customization tasks for Linux environments (e.g., using apt/yum/pacman for package installation instead of only WinGet/Chocolatey/PowerShell).
- Clarify any limitations or differences in feature support between Windows and Linux dev boxes, if applicable.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-dev-box-network-requirements.md
...ticles/dev-box/concept-dev-box-network-requirements.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows-centric bias. It references Windows-specific services (Windows 365, Windows activation, Group Policy), tools (Event Viewer, Windows logs), and troubleshooting steps that assume a Windows environment. There are no Linux-specific instructions, examples, or troubleshooting steps, and all references to client connectivity, troubleshooting, and configuration are framed in terms of Windows tools and patterns. Linux or cross-platform client scenarios are not addressed.
Recommendations
- Add explicit guidance for Linux and macOS clients, including how to connect to Dev Box using cross-platform Remote Desktop clients.
- Provide troubleshooting steps using Linux tools (e.g., journalctl, system logs) alongside Windows Event Viewer instructions.
- Include examples of network configuration and connectivity checks using Linux commands (e.g., curl, dig, netstat) in addition to or instead of Windows-specific tools.
- Clarify which requirements and steps apply to all platforms, and which are Windows-specific.
- Reference cross-platform documentation for remote desktop clients and network troubleshooting.
- Mention and link to open-source or cross-platform alternatives where possible (e.g., FreeRDP, Remmina for Linux).
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-what-are-team-customizations.md
...ticles/dev-box/concept-what-are-team-customizations.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 by exclusively referencing PowerShell and WinGet as the primary scripting and package management tools for Dev Box customizations. There are no examples or mentions of Linux-based tools, shell scripts, or package managers (such as Bash, apt, or yum). The documentation assumes a Windows environment and does not address cross-platform or Linux developer scenarios.
Recommendations
- Include examples and guidance for using Linux shell scripts (e.g., Bash) as customization tasks, alongside PowerShell.
- Document support for Linux-based Dev Boxes, if available, or clarify platform limitations.
- Mention and provide examples for Linux package managers (such as apt, yum, or zypper) in addition to WinGet.
- Ensure that references to scripting and automation tools are platform-neutral where possible, or provide parallel instructions for both Windows and Linux environments.
- Explicitly state whether Dev Box customizations are intended only for Windows-based environments, and if so, recommend alternatives or workarounds for Linux users.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/dev-box-roadmap.md
...ure-docs/blob/main/articles/dev-box/dev-box-roadmap.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page for Microsoft Dev Box exhibits a Windows-centric bias. It references PowerShell and Winget as primary scripting and package management primitives, with no mention of Linux equivalents (such as Bash or apt/yum). The focus is on Windows tools and workflows, and there are no examples or explicit support statements for Linux-based development environments or tools. WSL is mentioned only in passing, and always as a feature within a Windows context. There are no Linux-first or cross-platform examples or guidance.
Recommendations
- Include examples and references to Linux scripting and package management tools (e.g., Bash, apt, yum) alongside PowerShell and Winget.
- Explicitly mention support for Linux-based Dev Box environments, if available, and provide parity in documentation for Linux users.
- When describing features (such as debugging tasks or customization workflows), provide both Windows and Linux command examples.
- Clarify whether features like the CLI, VS Code extension, and Dev Box customization are cross-platform, and document any limitations or differences.
- Highlight WSL as a bridge for Linux workflows on Windows, but also address native Linux development scenarios if supported.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-conditional-access-dev-tunnels-service.md
...v-box/how-to-conditional-access-dev-tunnels-service.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 by exclusively using PowerShell and Microsoft Graph PowerShell SDK for all command-line instructions, with no mention of Linux or cross-platform alternatives. The prerequisite to install PowerShell 7.x and the absence of bash, Azure CLI, or other Linux-native instructions further reinforce this bias. All examples and tool references assume a Windows-centric environment, and there are no notes or guidance for Linux or macOS users.
Recommendations
- Provide equivalent instructions using Azure CLI or Microsoft Graph CLI, which are cross-platform and commonly used on Linux and macOS.
- Explicitly mention that PowerShell 7.x is cross-platform, and provide installation instructions for Linux and macOS, not just Windows.
- Include bash or shell script examples where possible, or clarify if certain steps are Windows-only.
- Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.
- Where screenshots or UI navigation are shown, clarify if the experience is the same across platforms or note any differences.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-azure-compute-gallery.md
...cles/dev-box/how-to-configure-azure-compute-gallery.md
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 examples are Windows-based (Windows 10/11, Visual Studio), and all technical instructions (such as sysprep, DISM, enabling features, and disk maintenance) reference Windows tools, commands, and PowerShell. There are no examples or guidance for creating or managing Linux-based images, nor are Linux-compatible tools or workflows mentioned. The requirements and optimizations are tailored exclusively for Windows environments.
Recommendations
- Include examples and requirements for Linux-based images (e.g., Ubuntu, CentOS) where supported by Azure Compute Gallery and Dev Box.
- Provide equivalent Linux commands and workflows for image preparation, such as generalizing a Linux VM (using waagent -deprovision+user), resizing partitions, and optimizing images.
- Mention Linux-compatible tools (e.g., bash, cloud-init) alongside Windows tools (PowerShell, DISM).
- Clarify in prerequisites and requirements whether Linux images are supported or not. If not supported, state this explicitly to avoid confusion.
- If Linux is supported, add screenshots and step-by-step instructions for Linux image creation and attachment, ensuring parity with the Windows-focused sections.
Dev Box
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-dev-box-hibernation.md
...ticles/dev-box/how-to-configure-dev-box-hibernation.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias: all configuration steps, compatibility notes, and troubleshooting guidance are written exclusively for Windows environments. There are no Linux-specific instructions, examples, or considerations. All references to OS-level settings (such as enabling nested virtualization or disabling Memory Integrity) are Windows-specific, and the only OS type shown in CLI examples is Windows. There is no mention of Linux images, tools, or workflows.
Recommendations
- Explicitly state whether Linux-based dev boxes support hibernation, and if so, provide equivalent instructions for Linux images.
- Include CLI examples for both Windows and Linux image types (e.g., using --os-type linux in az sig image-definition create).
- If hibernation is not supported on Linux dev boxes, clearly document this limitation and provide guidance or alternatives for Linux users.
- Add troubleshooting steps and compatibility considerations for Linux images, if applicable.
- Balance references to Windows tools and settings with Linux equivalents (e.g., how to enable nested virtualization or manage power settings on Linux).