Dev Box

78
Total Pages
34
Linux-Friendly Pages
44
Pages with Bias
56.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues (58)

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-customizations-connect-resource-repository.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-manage-dev-center.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation exclusively references the Azure portal (a web-based GUI) for managing Microsoft Dev Box dev centers and does not provide any command-line examples. There is an implicit Windows bias as the Azure portal is most commonly used and documented in Windows-centric environments, and there are no CLI, PowerShell, or Azure CLI/Bash examples. There is also no mention of Linux tools, workflows, or parity for users who may prefer or require non-Windows environments.
Recommendations:
  • Add equivalent instructions for managing dev centers using the Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include Bash shell examples for common tasks such as creating, deleting, and assigning permissions to dev centers.
  • Explicitly mention that the Azure portal is web-based and accessible from any OS, but provide links or steps for CLI-based management for users who prefer or require non-GUI workflows.
  • Ensure that any screenshots or step-by-step instructions do not assume a Windows-only environment (e.g., avoid referencing Windows-specific UI elements or terminology).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-azure-compute-gallery.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/quickstart-get-started-template.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-intune-conditional-access-policies.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-network-connections.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-what-are-dev-box-customizations.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-catalog.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation demonstrates a 'windows_first' and 'windows_tools' bias by exclusively referencing the Azure portal (a web UI optimized for Windows/Edge), Azure Key Vault, and Azure DevOps tools throughout all workflows. There are no Linux-specific instructions, CLI/bash examples, or references to cross-platform command-line tools. All screenshots and navigation steps assume a GUI workflow typical of Windows-centric environments, and there is no mention of Linux-native tooling or alternative approaches for Linux users.
Recommendations:
  • Provide equivalent instructions using the Azure CLI and/or Azure PowerShell for all major workflows (e.g., adding catalogs, configuring managed identities, managing Key Vault secrets).
  • Include bash shell command examples for Linux users, especially for tasks like cloning repositories, managing secrets, and interacting with Azure resources.
  • Explicitly state that all steps can be performed from Linux, macOS, or Windows, and clarify any platform-specific prerequisites.
  • Add screenshots or terminal output examples from Linux environments where relevant.
  • Reference cross-platform tools (such as az CLI) before or alongside GUI-based instructions.
  • Where GUI navigation is described, offer parallel CLI or REST API instructions for users who prefer or require non-GUI workflows.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-customize-devbox-azure-image-builder.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-stop-on-disconnect.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows-first bias by exclusively referencing RDP (Remote Desktop Protocol) sessions as the trigger for the auto-stop feature, with no mention of Linux remote desktop protocols (such as SSH or VNC) or scenarios. All examples and explanations assume Windows usage patterns, and there are no Linux-specific instructions or considerations.
Recommendations:
  • Clarify whether the auto-stop feature supports non-RDP (e.g., SSH, VNC) disconnects, especially for Linux-based dev boxes.
  • If Linux dev boxes are supported, provide equivalent examples and explanations for Linux remote access protocols.
  • Explicitly state any platform limitations (e.g., 'This feature currently only applies to Windows dev boxes using RDP').
  • Include guidance for administrators managing Linux dev boxes, or link to relevant documentation if supported elsewhere.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-manage-dev-box-definitions.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-create-dev-boxes-developer-portal.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-troubleshoot-repair-dev-box.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-generate-visual-studio-caches.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-dev-box-hibernation.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-hibernate-your-dev-box.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

Windows First Windows Tools
Summary:
The documentation demonstrates a Windows bias by referencing the Windows App for resuming a dev box and troubleshooting connectivity issues specifically via the RDP (Remote Desktop Protocol) app, which is primarily a Windows technology. There are no explicit Linux or cross-platform client examples or troubleshooting steps, and the only CLI shown is Azure CLI, which is cross-platform but not accompanied by Linux-specific context or alternative remote access methods.
Recommendations:
  • Include instructions or notes for resuming a dev box using Linux or macOS clients, such as through cross-platform remote desktop clients (e.g., Remmina, FreeRDP, or Microsoft Remote Desktop for Mac).
  • In troubleshooting, mention Linux/macOS remote desktop clients and provide guidance for users who are not using the Windows RDP app.
  • Avoid phrasing that assumes the user is on Windows (e.g., 'the Windows App'); instead, clarify if there are equivalent apps or steps for other platforms.
  • If there are platform-specific limitations or differences, explicitly document them and provide workarounds or alternatives for Linux/macOS users.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/reference-dev-box-customizations.md [View Details]
Scanned: 2025-07-13 21:37 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-stop-on-disconnect.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page exclusively references RDP sessions as the trigger for auto-stop functionality, which is a Windows-centric remote access protocol. There is no mention of Linux remote desktop protocols (such as SSH or VNC), nor any examples or clarifications for Linux-based dev boxes. All examples and explanations assume a Windows environment.
Recommendations:
  • Clarify whether the auto-stop feature supports Linux-based dev boxes and, if so, specify which disconnect events (e.g., SSH, VNC) are supported.
  • Provide examples or notes for Linux users, including how disconnects are detected for non-Windows environments.
  • If the feature is Windows-only, explicitly state this limitation early in the documentation.
  • Consider including parity features or roadmap information for Linux support if it is not currently available.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/quickstart-create-dev-box.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-connect-dev-box-virtual-switch.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-customize-devbox-azure-image-builder.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-dev-box-architecture.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-dev-box-deployment-guide.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-dev-box-concepts.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation for Microsoft Dev Box demonstrates a Windows bias by only mentioning support for Windows 10 and Windows 11 client editions in dev box definitions, with no reference to Linux or other operating systems. There are no examples or mentions of Linux-based development environments, tools, or workflows. The documentation implicitly assumes Windows as the default and only supported platform.
Recommendations:
  • Explicitly state whether Linux-based dev boxes are supported or not. If not, clarify this limitation for users.
  • If Linux support is available or planned, include examples and instructions for creating and managing Linux dev boxes, including references to Linux images in Azure Marketplace.
  • Provide parity in documentation by mentioning Linux development scenarios, tools, and workflows alongside Windows equivalents.
  • Include guidance for mixed-platform teams, such as how to manage both Windows and Linux dev boxes within the same dev center or project.
  • If only Windows is supported, add a section explaining the roadmap or alternatives for Linux developers.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-dev-box-network-requirements.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-what-are-team-customizations.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/dev-box-roadmap.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-conditional-access-dev-tunnels-service.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-azure-compute-gallery.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-dev-box-hibernation.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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).
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-dev-box-serverless-gpu.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-intune-conditional-access-policies.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-network-connections.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows Tools Missing Linux Example
Summary:
The documentation is heavily oriented around the Azure portal UI and Microsoft-specific identity solutions (Microsoft Entra, Active Directory), with references to Windows-centric network requirements and no mention of Linux tools, CLI, or cross-platform automation. There are no examples or instructions for Linux users or those preferring command-line interfaces (e.g., Azure CLI, PowerShell Core, Bash).
Recommendations:
  • Provide equivalent instructions using Azure CLI commands, which are cross-platform and can be run on Linux, macOS, and Windows.
  • Include examples for managing network connections using command-line tools (e.g., az network vnet create) in addition to the Azure portal UI.
  • Explicitly mention that the steps can be performed from any OS using the Azure CLI or REST API, and provide links to relevant documentation.
  • Clarify that Microsoft Entra and Active Directory are identity solutions that can be integrated with Linux-based environments, and provide guidance or references for Linux administrators.
  • Add troubleshooting or configuration notes relevant to Linux-based firewalls or network security tools, not just Microsoft Defender or Windows-centric solutions.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-connect-devices-to-dev-box.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-create-customization-tasks-catalog.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-create-dev-boxes-developer-portal.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-elevate-privilege-dev-box.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-enable-single-sign-on.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-generate-visual-studio-caches.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-hibernate-your-dev-box.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-manage-dev-box-definitions.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation page demonstrates a Windows-first bias by exclusively referencing Windows-based images (e.g., Windows 11 Enterprise, Visual Studio on Windows) and not mentioning Linux or other operating systems as options for dev box definitions. All example images and recommendations are Windows-centric, and there are no examples or guidance for using Linux images or configuring dev boxes for Linux development.
Recommendations:
  • Explicitly mention support for Linux images if available, or clarify if only Windows images are supported.
  • Provide examples of creating dev box definitions using popular Linux distributions (e.g., Ubuntu, CentOS) from the Azure Marketplace or custom images.
  • Include guidance or screenshots for selecting Linux images in the Azure portal, if supported.
  • Balance recommendations by suggesting Linux-based images for relevant development scenarios, not just Windows/Visual Studio.
  • If Linux is not supported, clearly state this limitation early in the documentation.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-manage-dev-box-pools.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation exclusively describes managing Dev Box pools via the Azure portal UI, with no mention of command-line tools, scripts, or automation options. There are no examples or references to PowerShell, Windows tools, or Windows-specific patterns, but there is also a complete absence of Linux CLI, Bash, or cross-platform automation examples. The documentation implicitly assumes a graphical, portal-based workflow, which is more common in Windows-centric environments, and does not address Linux users or those preferring CLI-based management.
Recommendations:
  • Add equivalent instructions for managing Dev Box pools using Azure CLI (az), which is cross-platform and works on Linux, macOS, and Windows.
  • Provide Bash script examples for common tasks (create, update, delete pools) to support Linux users.
  • Explicitly mention that all portal-based actions can also be performed via CLI or REST API, and link to relevant documentation.
  • Ensure screenshots and UI references are supplemented with CLI command blocks for parity.
  • If PowerShell examples are added in the future, ensure Bash/Azure CLI equivalents are provided alongside.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-manage-dev-center.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

Windows First Missing Linux Example
Summary:
The documentation exclusively references the Azure portal UI for managing Dev Box dev centers, with no mention of command-line tools or automation options. There are no examples or instructions for managing dev centers using cross-platform tools such as Azure CLI, and there is no mention of Linux or macOS environments. This implicitly prioritizes Windows-centric workflows, as the Azure portal experience is most commonly associated with Windows users, and omits guidance for users who prefer or require Linux-based tooling.
Recommendations:
  • Add equivalent instructions for managing dev centers using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include example commands for common tasks (create, delete, assign permissions) using Azure CLI or Azure PowerShell, and clarify which tools are available on which platforms.
  • Explicitly mention that the Azure portal can be accessed from any modern browser on any OS, to avoid the impression of Windows exclusivity.
  • Where screenshots or UI steps are shown, consider supplementing with terminal-based examples for parity.
  • If there are any limitations or differences in experience for Linux/macOS users, document them clearly.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-set-up-dev-tunnels.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-troubleshoot-dev-box-task-view.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-troubleshoot-repair-dev-box.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-resolve-dev-box-connectivity-issues.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-troubleshoot-remote-desktop-connectivity.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-use-copilot-generate-image-definition-file.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-use-secrets-customization-files.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-write-image-definition-file.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-write-user-customization-file.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/monitor-dev-box.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/overview-what-is-microsoft-dev-box.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/quickstart-configure-dev-box-arm-template.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/quickstart-configure-dev-box-service.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/quickstart-get-started-template.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/reference-dev-box-customizations.md [View Details]
Scanned: 2025-07-08 04:23 • Page-level bias detected
▼

Page-Level Analysis

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.