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 201-217 of 217 flagged pages
Dev Box Stop Dev Boxes Automatically When User Disconnects ...rticles/dev-box/how-to-configure-stop-on-disconnect.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing RDP (Remote Desktop Protocol) sessions as the trigger for auto-stop functionality, which is a Windows-centric remote access method. There are no mentions of Linux remote access protocols (such as SSH or VNC), nor examples or guidance for Linux users. All examples and explanations assume a Windows workflow, potentially excluding Linux-based Dev Box scenarios.
Recommendations
  • Clarify whether stop-on-disconnect functionality applies only to Windows Dev Boxes or if Linux Dev Boxes are supported.
  • If Linux Dev Boxes are supported, provide equivalent examples and explanations for Linux remote access protocols (e.g., SSH, VNC), including how disconnects are detected and handled.
  • Explicitly state any platform limitations in the prerequisites or notes section.
  • Add cross-platform guidance to ensure Linux administrators understand how to configure and benefit from auto-stop features.
GitHub Create Pull Request
Dev Box Grant access to Microsoft Dev Box .../main/articles/dev-box/how-to-manage-dev-box-access.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes role assignment and management using the Azure portal GUI, which is most commonly accessed from Windows environments. There are no examples or instructions for performing these tasks via cross-platform command-line tools such as Azure CLI, nor are PowerShell or Linux shell examples provided. This results in a Windows-first bias and a lack of Linux parity.
Recommendations
  • Add step-by-step instructions for assigning roles using Azure CLI, which is available on both Windows and Linux.
  • Include examples for role assignment using PowerShell and Bash, highlighting cross-platform usage.
  • Explicitly mention that the Azure portal is accessible from any OS, but provide alternatives for users who prefer command-line or automated approaches.
  • Ensure troubleshooting and clean-up sections include CLI commands for removing role assignments.
GitHub Create Pull Request
Dev Box Stop Dev Boxes Automatically When User Disconnects ...rticles/dev-box/how-to-configure-stop-on-disconnect.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on stopping Dev Boxes when users disconnect from RDP sessions, a Windows-centric protocol. There is no mention of Linux remote access methods (such as SSH or VNC), nor are there examples or instructions for Linux-based Dev Boxes. All references to user disconnection are tied to RDP, implicitly prioritizing Windows environments.
Recommendations
  • Explicitly state whether stop-on-disconnect applies to Linux Dev Boxes and their remote access protocols (e.g., SSH, VNC).
  • Provide examples and instructions for managing stop-on-disconnect for Linux Dev Boxes, if supported.
  • If only Windows Dev Boxes are supported for this feature, clarify this limitation early in the documentation.
  • Include parity in terminology and examples for both Windows (RDP) and Linux (SSH/VNC) where applicable.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-stop-on-disconnect.md ...rticles/dev-box/how-to-configure-stop-on-disconnect.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on stopping Dev Boxes after users disconnect from RDP sessions, a protocol primarily associated with Windows environments. There is no mention of Linux remote access protocols (such as SSH), nor any examples or instructions for Linux users. The documentation implicitly assumes Windows usage patterns and does not address Linux scenarios.
Recommendations
  • Include information about stopping Dev Boxes after disconnects from Linux remote access protocols, such as SSH.
  • Add examples or instructions for configuring auto-stop for Linux-based Dev Boxes, if supported.
  • Clarify whether the stop-on-disconnect feature is available for non-Windows Dev Boxes and, if not, explicitly state this limitation.
  • Provide parity in documentation by mentioning both Windows (RDP) and Linux (SSH, etc.) scenarios where applicable.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-manage-dev-box-access.md .../main/articles/dev-box/how-to-manage-dev-box-access.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes role assignment and management using the Azure portal UI, which is primarily accessed via web browsers on Windows. There are no examples or references to command-line methods (such as Azure CLI or PowerShell), nor is there any mention of Linux tools or workflows. This creates a subtle Windows-first bias and omits Linux parity, as many platform engineers and developers may prefer or require CLI-based instructions, especially on Linux or macOS systems.
Recommendations
  • Add examples for assigning roles using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • If relevant, include PowerShell examples but ensure Azure CLI instructions are presented first or in parallel.
  • Explicitly mention that all steps can be performed from any OS using the Azure portal or CLI.
  • Provide troubleshooting steps for CLI users, including common errors and verification commands.
  • Include a note on supported platforms for all tools referenced.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-stop-on-disconnect.md ...rticles/dev-box/how-to-configure-stop-on-disconnect.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing RDP (Remote Desktop Protocol) sessions as the trigger for stopping Dev Boxes, which is a Windows-centric remote access technology. There are no mentions of Linux remote access protocols (such as SSH or VNC), nor any examples or notes addressing how stop-on-disconnect would work for Linux-based Dev Boxes or users connecting via non-Windows methods.
Recommendations
  • Clarify whether stop-on-disconnect applies only to RDP sessions or if it also supports Linux remote access protocols (e.g., SSH, VNC).
  • Add examples or notes for Linux users, including how stop-on-disconnect behaves for Linux Dev Boxes and what triggers the stop event in those scenarios.
  • If the feature is Windows-only, explicitly state this limitation in the documentation.
  • If Linux is supported, provide parity in examples and parameter explanations for Linux remote access methods.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-manage-dev-box-access.md .../main/articles/dev-box/how-to-manage-dev-box-access.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes role assignment and access management using the Azure portal GUI, which is primarily a Windows-centric workflow. There are no CLI, PowerShell, or Azure CLI examples, nor any mention of Linux-compatible workflows or tools. The instructions and screenshots assume use of the Azure portal, which is most commonly accessed from Windows environments, and do not provide parity for Linux users who may prefer command-line or automation approaches.
Recommendations
  • Add equivalent instructions for assigning roles using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include PowerShell examples for users who prefer scripting, but ensure Azure CLI examples are presented first or alongside to avoid Windows-first bias.
  • Explicitly mention that all steps can be performed from any OS using the Azure CLI or REST API, and provide links to relevant documentation.
  • Add troubleshooting steps for command-line workflows, not just portal-based issues.
  • Include notes or sections on how Linux/macOS users can accomplish the same tasks without relying on the Azure portal GUI.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-manage-dev-center.md ...blob/main/articles/dev-box/how-to-manage-dev-center.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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).
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-catalog.md ...blob/main/articles/dev-box/how-to-configure-catalog.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-stop-on-disconnect.md ...rticles/dev-box/how-to-configure-stop-on-disconnect.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-hibernate-your-dev-box.md ...main/articles/dev-box/how-to-hibernate-your-dev-box.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-stop-on-disconnect.md ...rticles/dev-box/how-to-configure-stop-on-disconnect.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/concept-dev-box-concepts.md ...blob/main/articles/dev-box/concept-dev-box-concepts.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 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.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-configure-network-connections.md ...ticles/dev-box/how-to-configure-network-connections.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 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.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-manage-dev-box-definitions.md .../articles/dev-box/how-to-manage-dev-box-definitions.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-manage-dev-box-pools.md ...b/main/articles/dev-box/how-to-manage-dev-box-pools.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
Dev Box https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dev-box/how-to-manage-dev-center.md ...blob/main/articles/dev-box/how-to-manage-dev-center.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
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.
GitHub Create Pull Request
← Previous Page 9 of 9 Next →