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 76-100 of 217 flagged pages
Dev Box Reference: imagedefinition.yaml and task.yaml Files ...n/articles/dev-box/reference-dev-box-customizations.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily focused on Windows-specific tools and patterns. All examples use Windows images, PowerShell scripts, and WinGet, with no mention of Linux equivalents or cross-platform alternatives. The built-in tasks are exclusively Windows-centric, and the schema and usage examples assume a Windows environment. There are no Linux image references, Bash examples, or Linux package managers discussed.
Recommendations
  • Add examples using Linux base images (e.g., Ubuntu, CentOS) in the 'image' section.
  • Include built-in tasks for Bash or shell scripts alongside PowerShell, with example YAML snippets.
  • Document support for Linux package managers (e.g., apt, yum) similar to WinGet, if available.
  • Provide sample task.yaml definitions for Linux environments, showing how to run shell commands.
  • Clarify platform support and limitations at the top of the page, including whether Linux dev boxes are supported.
  • If Linux is not supported, explicitly state this to avoid confusion; if it is, ensure parity in documentation.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a prerequisite, referencing Dev Box (a Windows-centric service) throughout, and providing only PowerShell command examples for testing. There are no Linux-specific instructions, nor are alternative shell commands (e.g., Bash) or Linux tools mentioned. The workflow assumes a Windows environment and does not address Linux users or provide parity in examples.
Recommendations
  • Include Linux prerequisites, such as Bash or compatible shell environments, and clarify if PowerShell Core (cross-platform) is required or if alternatives are supported.
  • Provide Linux-specific command examples for testing Dev Tunnel access, using Bash or other common Linux shells.
  • Explicitly mention how Linux users can perform each step, including any differences in setup or tooling.
  • Add notes or sections addressing cross-platform compatibility and any limitations or considerations for Linux environments.
  • If Dev Box is Windows-only, clarify how Linux users can access Dev Tunnels or suggest alternative workflows.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Windows App as the method for connecting to a Dev Box, with no mention of Linux or cross-platform alternatives. All connection instructions and prerequisites focus on Windows tools, and there are no examples or guidance for Linux users. The documentation implicitly assumes a Windows environment, omitting Linux-specific connection methods or tools.
Recommendations
  • Add instructions and examples for connecting to a Dev Box from Linux systems, such as using RDP clients (e.g., Remmina, rdesktop, FreeRDP) or web-based access.
  • List Linux-compatible tools in the prerequisites section, alongside the Windows App.
  • Provide parity in screenshots and step-by-step guides for Linux users.
  • Explicitly state cross-platform support and limitations, if any, for Dev Box access.
  • Include troubleshooting tips for Linux environments.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a clear Windows bias. All code examples for generating Visual Studio caches use PowerShell and Windows-specific tooling (devenv.exe), with no mention of Linux equivalents or cross-platform alternatives. The instructions assume the use of Visual Studio on Windows and do not address scenarios for Visual Studio Code or .NET development on Linux. The order of presentation and terminology also prioritize Windows environments and tools, with Linux support absent throughout.
Recommendations
  • Provide equivalent instructions and examples for Linux environments, such as using .NET CLI (dotnet build) for cache generation where applicable.
  • Clarify whether Visual Studio cache precaching is supported or relevant for Visual Studio Code or .NET development on Linux.
  • Include bash or shell script examples alongside PowerShell, and mention any platform-specific limitations.
  • Explicitly state platform requirements and limitations at the start of the documentation.
  • If features are Windows-only, add a note explaining the lack of Linux support and suggest alternative workflows for Linux users.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All examples use Windows images, PowerShell, and WinGet (Windows-specific tools). There are no examples or mentions of Linux images, Bash, or Linux-native tools. The schema and built-in tasks are described exclusively in terms of Windows usage, with PowerShell as the default scripting language and WinGet as the package manager, both of which are unavailable on Linux. No Linux equivalents or cross-platform options are provided.
Recommendations
  • Add examples using Linux images (e.g., Ubuntu, CentOS) in imagedefinition.yaml.
  • Introduce built-in tasks for Bash or shell scripts, and document their usage.
  • Provide Linux-native package manager examples (e.g., apt, yum) alongside WinGet.
  • Clarify which features/tasks are Windows-only and which are cross-platform.
  • Present Windows and Linux examples side-by-side to improve parity.
  • Mention any limitations or differences for Linux environments explicitly.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page for Microsoft Dev Box deployment is heavily oriented towards Windows environments. It exclusively references Windows-based management tools (Microsoft Intune, Entra ID, Active Directory), Windows device management, and Windows-specific configuration profiles. Examples and customization tasks mention Windows package managers (WinGet, Chocolatey) and PowerShell scripts, with no mention of Linux equivalents or cross-platform scenarios. There are no examples or guidance for deploying or managing Linux-based dev boxes, nor are Linux-specific tools or patterns discussed.
Recommendations
  • Add explicit guidance and examples for deploying Linux-based dev boxes, including image selection, customization, and management.
  • Include Linux package managers (e.g., apt, yum, zypper) and shell scripting (bash) in customization catalog examples alongside WinGet, Chocolatey, and PowerShell.
  • Clarify which features (such as Intune device management, conditional access, and privilege management) are available or not available for Linux dev boxes.
  • Provide parity in troubleshooting and monitoring guidance for Linux dev boxes (e.g., logs, compliance reporting).
  • Mention cross-platform developer scenarios and highlight any limitations or differences between Windows and Linux dev boxes.
  • Ensure that references to 'device' or 'dev box' are not implicitly limited to Windows, and specify when instructions are OS-specific.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-authoring-troubleshooting-guide-team-customizations.md ...pt-authoring-troubleshooting-guide-team-customizations.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All examples, tools, and troubleshooting steps are centered around Windows environments, with exclusive references to Windows-specific technologies such as PowerShell, WinGet, and Windows file paths. There are no Linux or cross-platform equivalents provided for tasks, commands, or troubleshooting. The guidance assumes Dev Box usage on Windows, omitting any mention of Linux-based Dev Boxes, Bash scripting, or Linux-native package managers.
Recommendations
  • Add parallel examples for Linux-based Dev Boxes, including Bash scripts and usage of Linux package managers (e.g., apt, yum).
  • Mention and document Linux equivalents for built-in tasks (e.g., using apt for software installation, Bash for scripting).
  • Include troubleshooting steps and log locations for Linux environments.
  • Clarify which features and primitives are cross-platform and which are Windows-only.
  • Provide guidance for authoring and testing image definitions on Linux, including required permissions and environment setup.
  • Ensure that references to tools (e.g., WinGet, PowerShell) are accompanied by Linux alternatives or a note about platform support.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias. All examples and instructions reference PowerShell scripts and WinGet, both of which are Windows-specific tools. There is no mention of Linux equivalents, nor are there examples or guidance for customizing Dev Boxes running Linux. The documentation assumes a Windows environment by default, omitting cross-platform considerations and failing to address how Linux users can create or apply customizations.
Recommendations
  • Add explicit support and examples for Linux-based Dev Boxes, including how to author customization tasks using Bash scripts or other Linux-native tools.
  • Mention and document Linux package managers (e.g., apt, yum, dnf) alongside WinGet for software installation tasks.
  • Provide parallel examples for both Windows and Linux environments in all relevant sections, ensuring parity in guidance and tooling.
  • Clarify which features and customization mechanisms are available or limited on Linux Dev Boxes, and provide links to Linux-specific documentation if available.
  • Avoid recommending Windows tools (PowerShell, WinGet) as the default or only option; instead, present platform-appropriate choices based on the Dev Box OS.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a strong Windows bias. All example images are Windows-based (Visual Studio 2019/2022), and the image requirements section exclusively lists Windows OS versions. Instructions for image preparation rely on Windows-specific tools and commands (Sysprep, DISM, defrag, chkdsk, PowerShell), with no mention of Linux equivalents or support for Linux images. The workflow and screenshots are tailored to Windows environments, and there are no examples or guidance for using Linux images or tools.
Recommendations
  • Explicitly state whether Linux images are supported or not. If supported, add a section detailing requirements and preparation steps for Linux images.
  • Provide Linux-specific examples for image creation, generalization, and optimization (e.g., using waagent, cloud-init, or other relevant tools).
  • Include references to Linux Marketplace images compatible with Dev Box, if available.
  • Add CLI commands and instructions relevant to Linux environments (e.g., Bash, Azure CLI for Linux).
  • Balance the documentation by mentioning Linux tools and patterns alongside Windows ones, or clarify the Windows-only scope if Linux is not supported.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by exclusively referencing Windows OS features, settings, and troubleshooting steps. All configuration examples, compatibility notes, and troubleshooting guidance are centered on Windows-specific tools and patterns (e.g., Windows Security, Core Isolation, Virtual Machine Platform, sysprep). There are no mentions of Linux images, Linux-specific hibernation considerations, or examples for enabling hibernation on Linux-based dev boxes. The documentation assumes the reader is working with Windows environments and omits Linux parity.
Recommendations
  • Add explicit guidance for enabling hibernation on Linux-based dev boxes, if supported.
  • Include Linux-specific compatibility considerations and troubleshooting steps.
  • Provide CLI examples for both Windows and Linux images (e.g., using --os-type linux).
  • Clarify whether hibernation is supported for Linux dev boxes and, if not, state this explicitly.
  • Mention Linux equivalents for settings/features (e.g., kernel modules, virtualization features) where relevant.
  • Balance recommendations for base images by including popular Linux images alongside Windows/Visual Studio images.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for Microsoft Dev Box exhibits a Windows-centric bias. It references Windows-specific tools and patterns (such as PowerShell, Winget, RDP, and Visual Studio), and provides examples or workflow improvements only for these technologies. There is no mention of Linux equivalents (e.g., Bash, apt, SSH, Linux desktop environments), nor are Linux-focused onboarding or customization scenarios described. Windows tools and workflows are mentioned first and exclusively, while Linux support is either absent or only implied (e.g., WSL is referenced but not explained or exemplified).
Recommendations
  • Add explicit examples and workflow descriptions for Linux-based Dev Box environments, including customization using Bash scripts and Linux package managers (e.g., apt, yum).
  • Mention and provide parity for Linux desktop environments and remote access tools (e.g., SSH, VNC) alongside RDP and Windows desktop references.
  • Include onboarding and enterprise management scenarios for Linux Dev Boxes, such as configuring prerequisites and policies for Linux images.
  • Ensure CLI and VS Code extension documentation covers Linux scripting and automation, not just PowerShell and Winget.
  • Highlight Linux image support and provide links to relevant documentation for creating and managing Linux Dev Boxes.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-customization-tasks.md ...ticles/dev-box/how-to-configure-customization-tasks.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing PowerShell scripts and WinGet (Windows package manager) as the primary mechanisms for task customization. All examples and instructions are centered around Windows tooling, with no mention of Linux shell scripts, Bash, or Linux-native package managers. The documentation does not provide Linux equivalents or alternatives, nor does it acknowledge cross-platform scenarios or how to customize Dev Boxes running Linux.
Recommendations
  • Include examples using Bash scripts and Linux shell commands alongside PowerShell examples.
  • Mention and provide guidance for using Linux package managers (e.g., apt, yum) in customization tasks.
  • Clarify whether Dev Box supports Linux-based environments and, if so, document how to create and manage tasks for those environments.
  • Add sample task.yaml configurations for Linux scenarios.
  • Ensure documentation language is inclusive of both Windows and Linux users, and avoid assuming PowerShell/WinGet as the default or only option.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-intune-conditional-access-policies.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-intune-conditional-access-policies.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-specific tools (such as Microsoft Remote Desktop, Windows 365, Windows Azure Service Management API, and Windows Cloud sign-in) and by focusing on workflows and applications that are primarily relevant to Windows environments. There are no examples or mentions of Linux-based access patterns, tools, or client applications, nor is there guidance for Linux users connecting to Dev Boxes or managing Conditional Access policies. The documentation assumes a Windows-centric approach throughout, both in terminology and in the listed applications.
Recommendations
  • Include examples and guidance for accessing Dev Boxes from Linux clients, such as using open-source RDP clients (e.g., FreeRDP, Remmina) or SSH where applicable.
  • Document Conditional Access scenarios for Linux-based development environments, including how compliance and device management work for Linux dev boxes.
  • List Linux-compatible tools and workflows in the 'Apps that are required for Dev Box' section, clarifying which apps are cross-platform and providing alternatives where needed.
  • Add explicit notes or sections on how Linux users can interact with Dev Box, including authentication, remote desktop, and portal access.
  • Ensure parity in step-by-step instructions for both Windows and Linux users, especially for connectivity and troubleshooting.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-user-customizations.md ...ticles/dev-box/how-to-configure-user-customizations.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows-specific tools (WinGet, PowerShell), focusing on configuring Windows environments, and omitting any mention of Linux equivalents or workflows. All examples and configuration patterns are tailored to Windows, with no guidance for Linux-based dev boxes or cross-platform scenarios.
Recommendations
  • Include examples and instructions for customizing Linux-based dev boxes, such as using apt, yum, or shell scripts.
  • Mention and provide parity for Linux package managers and configuration tools alongside WinGet and PowerShell.
  • Clarify whether the customization system supports Linux dev boxes and, if so, document any differences or limitations.
  • Provide sample YAML customization files for Linux environments.
  • Add guidance for validating and troubleshooting customizations on Linux dev boxes.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-team-customizations.md ...ticles/dev-box/how-to-configure-team-customizations.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias. All examples and built-in tasks focus on Windows-centric technologies such as PowerShell, WinGet, and Desired State Configuration (DSC), with no mention of Linux equivalents (e.g., Bash, apt, yum, shell scripts). The workflow and customization examples exclusively use Windows tools and patterns, and there are no examples or guidance for Linux-based dev boxes or cross-platform scenarios. Windows tools are mentioned first and exclusively throughout the documentation.
Recommendations
  • Add examples and guidance for customizing Linux-based dev boxes, including using shell scripts, apt/yum/dnf package managers, and Linux configuration management tools.
  • Introduce Linux equivalents for built-in tasks, such as Bash scripts, apt/yum package installation, and git-clone for Linux environments.
  • Clarify whether Dev Box supports Linux images and, if so, provide parity in documentation for Linux customization workflows.
  • Present cross-platform examples side-by-side, showing both Windows (PowerShell/WinGet) and Linux (Bash/apt/yum) approaches.
  • Explicitly mention platform limitations or support in the prerequisites and task sections, so users know whether Linux is supported and how to proceed.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All configuration steps use PowerShell commands and Windows-specific tools (Hyper-V, New-VMSwitch, New-NetIPAddress, New-NetNat). There are no examples or instructions for performing similar tasks on Linux, nor is there mention of Linux virtualization platforms or networking tools. The instructions and screenshots are tailored exclusively to Windows environments.
Recommendations
  • Add equivalent instructions for Linux environments, such as using KVM/QEMU, libvirt, or VirtualBox.
  • Provide Linux command-line examples (e.g., using ip, brctl, virsh, or nmcli) for creating virtual switches and NAT networks.
  • Include notes on Linux prerequisites (e.g., required packages, kernel modules).
  • Offer screenshots or configuration dialogs from popular Linux desktop environments.
  • Clarify which steps are Windows-specific and provide cross-platform guidance where possible.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All code examples use Azure PowerShell, with explicit instructions for installing Azure PowerShell on Windows and no mention of Linux or macOS installation. The image customization steps use Windows-specific tools (Chocolatey, PowerShell scripts), and the VM Image Builder template is tailored for Windows images (Windows-11 SKU, OS type set to Windows). There are no examples or guidance for using Azure CLI, Bash, or Linux-based images, despite a brief mention that Azure CLI can be used. The documentation assumes a Windows-centric workflow throughout.
Recommendations
  • Provide parallel examples using Azure CLI and Bash scripts for all steps, including resource creation, template deployment, and image building.
  • Include instructions for installing Azure PowerShell on Linux and macOS, or link to cross-platform installation guides.
  • Add a section or examples for building Linux-based images (e.g., Ubuntu), including customization steps using Linux-native tools (such as apt, shell scripts).
  • Mention and demonstrate how to use Linux equivalents of Chocolatey (such as apt, yum, or snap) for software installation in image customization.
  • Ensure that references to tools and workflows do not assume a Windows environment (e.g., avoid hardcoded Windows file paths like c:\temp\).
  • Reorder prerequisites and instructions to present cross-platform options equally, rather than Windows-first.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-troubleshoot-remote-desktop-connectivity.md ...box/how-to-troubleshoot-remote-desktop-connectivity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a strong Windows bias. All troubleshooting steps, examples, and tool references are specific to Windows environments. There are no mentions of Linux or cross-platform scenarios, and all command-line instructions (such as certutil and Set-VMProcessor) are Windows-specific. The documentation assumes the use of Windows tools and patterns, with no Linux equivalents or alternative instructions provided.
Recommendations
  • Include troubleshooting steps and examples for Linux-based dev boxes, if supported.
  • Provide Linux equivalents for Windows-specific commands (e.g., alternatives to certutil and PowerShell commands).
  • Mention and link to Linux-compatible remote desktop clients or tools where appropriate.
  • Clarify in the prerequisites and throughout the documentation whether non-Windows dev boxes are supported, and if not, state this explicitly.
  • If features or issues are Windows-only, clearly label them as such and provide parity guidance for Linux users where possible.
GitHub 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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All code examples use Windows-specific paths (e.g., C:\workspaces), PowerShell scripts, and Windows tools such as winget. There are no examples for Linux environments, such as Bash scripts, Linux file paths, or package managers like apt or yum. Windows-centric terminology and tooling are presented exclusively, with no mention of Linux equivalents or cross-platform considerations.
Recommendations
  • Provide parallel examples for Linux environments, including Bash scripts and Linux file paths (e.g., /home/dev/workspaces).
  • Include instructions for installing Azure CLI using Linux package managers (e.g., apt, yum) alongside winget.
  • Demonstrate how to clone repositories and hydrate secrets using Linux shell commands.
  • Clarify which customization features and Dev Box tasks are cross-platform, and note any platform-specific limitations.
  • Add screenshots or references for Linux-based workflows where applicable.
  • Explicitly state platform requirements or supported operating systems for each example.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-elevate-privilege-dev-box.md ...n/articles/dev-box/how-to-elevate-privilege-dev-box.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, specifically Windows 10/11 dev boxes, with all examples, configuration steps, and verification instructions tailored exclusively to Windows. There are no references to Linux or cross-platform scenarios, and all tooling and procedures assume a Windows OS and ecosystem.
Recommendations
  • Add explicit statements about platform support, clarifying whether Linux dev boxes are supported or not.
  • If Linux support exists or is planned, provide equivalent configuration and verification steps for Linux dev boxes.
  • Include examples of how privilege management would work on Linux, referencing relevant tools (e.g., sudo, polkit) and how Intune integrates or does not integrate with them.
  • Mention any limitations or differences in Endpoint Privilege Management functionality between Windows and Linux.
  • If only Windows is supported, make this clear early in the documentation to set expectations for cross-platform users.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-resolve-dev-box-connectivity-issues.md .../dev-box/how-to-resolve-dev-box-connectivity-issues.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a clear Windows bias: troubleshooting steps, examples, and tools are overwhelmingly Windows-centric. Windows tools (such as Group Policy Editor, Registry Editor, Task Manager, and Windows-specific command-line utilities like dsregcmd.exe and reg.exe) are referenced exclusively or before any alternatives. The only non-Windows example is a brief macOS command for TCP/UDP settings, with no mention of Linux clients or troubleshooting steps for Linux users. There are no Linux-specific instructions, tools, or parity in troubleshooting workflows.
Recommendations
  • Add Linux client troubleshooting steps and examples, including how to connect to Dev Box from Linux (e.g., using open-source RDP clients like xfreerdp or Remmina).
  • Provide Linux equivalents for registry and group policy changes, such as configuration file edits or command-line flags for Linux RDP clients.
  • Include Linux-specific diagnostic commands and tools (e.g., checking network connectivity with ping, traceroute, or netstat).
  • Mention Linux support explicitly in prerequisites and troubleshooting checklists, clarifying which steps apply to Linux and providing alternatives where necessary.
  • Ensure all platform-specific instructions are grouped under clear tabs or sections (Windows, macOS, Linux) for parity and discoverability.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses exclusively on troubleshooting Remote Desktop Protocol (RDP) connectivity to dev boxes, referencing Windows-specific concepts such as 'Windows Guest OS readiness' and RDP, without mentioning Linux equivalents (e.g., SSH). All examples and troubleshooting steps are tailored to Windows environments, with no guidance for Linux-based dev boxes or alternative remote access methods. Windows tools and terminology are used throughout, and Linux scenarios are omitted.
Recommendations
  • Include troubleshooting steps for Linux-based dev boxes, such as SSH connectivity issues.
  • Add examples and checks relevant to Linux OS readiness, such as verifying SSH daemon status and firewall rules.
  • Mention Linux remote access tools (e.g., SSH, VNC) alongside RDP, and clarify which steps apply to Windows vs. Linux dev boxes.
  • Provide parity in screenshots and instructions for both Windows and Linux environments.
  • Explicitly state OS prerequisites and limitations for the Troubleshoot & Repair tool, and link to Linux-specific troubleshooting resources if available.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/includes/customizations-modular-scripts.md ...les/dev-box/includes/customizations-modular-scripts.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias. All examples and references use Windows-specific technologies such as PowerShell scripts, Desired State Configuration (DSC), and WinGet. The YAML sample exclusively references Windows file paths and tools, with no mention of Linux equivalents (e.g., Bash scripts, shell scripts, or Linux package managers). The catalog structure and task execution are described in terms of Windows conventions, and no Linux or cross-platform alternatives are provided.
Recommendations
  • Include examples using Linux shell scripts (e.g., Bash) and configuration files relevant to Linux environments.
  • Show how to reference and execute Linux scripts in the image definition YAML, including Linux file paths and permissions.
  • Mention Linux package managers (e.g., apt, yum) and how to use them in Dev Box customizations.
  • Clarify whether Dev Box supports Linux images and, if so, provide parity in documentation for Linux-based customization tasks.
  • Add a section comparing Windows and Linux customization workflows to help users understand cross-platform capabilities.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/quickstart-configure-dev-box-arm-template.md ...s/dev-box/quickstart-configure-dev-box-arm-template.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for deploying the ARM template, with no equivalent Bash or Linux shell instructions. The deployment walkthrough assumes use of Azure Cloud Shell with PowerShell, and the step-by-step instructions reference Windows-centric actions (e.g., right-clicking to paste). Although Azure CLI is mentioned as an alternative, no Linux/Bash example is provided, and PowerShell is presented first and exclusively in the main workflow.
Recommendations
  • Add equivalent deployment instructions using Azure CLI in Bash, including a full example script for Linux/macOS users.
  • Present both PowerShell and Bash/CLI examples side-by-side, or clearly indicate both options at the start of the deployment section.
  • Avoid Windows-specific UI instructions (such as right-click to paste) or provide Linux/macOS alternatives.
  • Explicitly mention that Azure Cloud Shell supports Bash and PowerShell, and show how to select Bash.
  • Ensure that all referenced tools (e.g., VS Code, Azure CLI) are described as cross-platform where applicable.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/monitor-dev-box.md ...ure-docs/blob/main/articles/dev-box/monitor-dev-box.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples for enabling diagnostic logs, while omitting equivalent CLI or Bash examples that would be more familiar to Linux users. The only command-line automation shown is via Azure PowerShell, which is primarily used on Windows. There is no mention of Azure CLI or Bash scripting, and the order of presentation puts PowerShell before any Linux-friendly alternatives. This may make it harder for Linux users to follow or automate the process.
Recommendations
  • Add equivalent Azure CLI examples for enabling diagnostic logs, including both storage account and Log Analytics workspace scenarios.
  • Include Bash scripting samples where appropriate, especially for automation tasks.
  • Explicitly mention cross-platform tools (e.g., Azure CLI) and clarify that they can be used on Linux, macOS, and Windows.
  • Present CLI and PowerShell examples side-by-side or in parallel tabs, rather than only PowerShell.
  • Review screenshots and UI instructions to ensure they do not assume a Windows environment (e.g., avoid references to Windows-specific UI elements unless necessary).
GitHub Create Pull Request
← Previous Page 4 of 9 Next →