Databox Gateway

27
Total Pages
11
Linux-Friendly Pages
16
Pages with Bias
59.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

102 issues found
Showing 26-50 of 102 flagged pages
Databox Gateway Microsoft Azure Data Box Gateway use cases | Microsoft Docs ...articles/databox-gateway/data-box-gateway-use-cases.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 primarily through the exclusive mention of Azure PowerShell for setting blob tiers, without providing equivalent Linux/CLI examples. The instructions for moving data to the Archive tier list PowerShell before mentioning Azure Lifecycle Management, and do not reference cross-platform tools such as Azure CLI or REST API. There are no Linux-specific examples or references to Linux tools, and the documentation does not clarify how users on Linux or macOS should perform these operations.
Recommendations
  • Add Azure CLI examples for setting blob tiers and managing lifecycle policies, alongside PowerShell instructions.
  • Explicitly mention that operations can be performed from Linux/macOS using Azure CLI or REST API, and provide links or code samples.
  • Ensure that any scripting or automation examples are provided in both PowerShell and Bash/CLI formats.
  • Clarify that SMB and NFS protocols are cross-platform, and provide example commands for mounting shares on Linux.
  • Review all step-by-step instructions to ensure Linux parity and avoid assuming a Windows-only environment.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-2101-release-notes.md ...databox-gateway/data-box-gateway-2101-release-notes.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 for Azure Data Box Gateway 2101 release notes demonstrates a Windows bias by referencing cumulative Windows and .NET framework updates as part of the release, without mentioning equivalent updates or considerations for Linux environments. There are no examples, notes, or references to Linux tools, commands, or deployment patterns, and the documentation implicitly assumes a Windows-centric deployment and maintenance workflow.
Recommendations
  • Include information about Linux compatibility, if supported, and reference any relevant Linux updates or dependencies.
  • Provide examples or notes for Linux-based deployment, configuration, and troubleshooting, where applicable.
  • Clarify whether the Data Box Gateway is Windows-only or cross-platform, and if cross-platform, ensure parity in documentation for Linux users.
  • Mention alternative tools or frameworks for Linux environments if .NET or Windows-specific updates are referenced.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-manage-access-power-connectivity-mode.md ...data-box-gateway-manage-access-power-connectivity-mode.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only PowerShell commands for resource provider registration and querying, which are Windows-centric. There are no equivalent examples for Linux users (e.g., Azure CLI or Bash). The exclusive use of PowerShell and lack of mention of Linux tools or workflows indicates a bias toward Windows environments.
Recommendations
  • Add Azure CLI examples for resource provider registration and querying, which work cross-platform (Linux, macOS, Windows).
  • Explicitly mention that the operations can be performed from Linux or macOS using Azure CLI.
  • Where PowerShell is shown, provide side-by-side Azure CLI/Bash equivalents.
  • Clarify any platform-specific requirements for the local web UI or device management, if applicable.
  • Review other sections for similar Windows-centric instructions and ensure Linux parity throughout.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-manage-shares.md ...cles/databox-gateway/data-box-gateway-manage-shares.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 Windows bias in several ways. SMB (Windows standard) is presented as the default share type, with NFS (Linux standard) mentioned secondarily. Instructions for SMB shares include details about creating local users and modifying permissions via File Explorer, a Windows tool, while NFS shares only mention IP address configuration and lack further Linux-specific guidance. There are no Linux command-line or tool examples, nor references to Linux file managers or permission management. The documentation assumes familiarity with Windows patterns and omits parity for Linux workflows.
Recommendations
  • Present SMB and NFS options with equal prominence, avoiding defaulting to Windows-centric SMB.
  • Include Linux-specific instructions for NFS shares, such as mounting NFS shares from Linux clients and managing permissions using Linux tools (e.g., chmod, chown).
  • Provide examples of accessing shares from both Windows (File Explorer, net use) and Linux (mount, smbclient, nfs-utils).
  • Reference Linux file managers (e.g., Nautilus, Dolphin) alongside Windows File Explorer.
  • Add troubleshooting steps and permission management examples for Linux environments.
  • Ensure all screenshots and step-by-step instructions are platform-neutral or include both Windows and Linux perspectives.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-2007-release-notes.md ...databox-gateway/data-box-gateway-2007-release-notes.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 Windows bias by referencing Windows-specific tools and updates (e.g., Windows VHD, cumulative Windows updates, .NET framework updates) without mentioning Linux equivalents or providing Linux-specific guidance. There are no examples or notes for Linux-based deployments, and Windows terminology appears first and exclusively.
Recommendations
  • Include information about Linux-based deployment images, updates, or compatibility if supported.
  • Provide parity by listing Linux-specific updates or changes alongside Windows updates.
  • Add examples or notes for Linux users, such as supported distributions, kernel versions, or troubleshooting steps.
  • Clarify whether the product is Windows-only or cross-platform, and if cross-platform, ensure equal coverage in release notes.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-deploy-add-shares.md .../databox-gateway/data-box-gateway-deploy-add-shares.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting Windows/SMB connection instructions and examples before Linux/NFS equivalents. Windows-specific tools and patterns (e.g., 'net use', File Explorer, Windows + R) are described in detail, including command output, while Linux instructions are more concise and lack equivalent depth (no sample output, less step-by-step guidance). The page also refers to SMB as the default and standard for Windows clients, reinforcing Windows-centric usage.
Recommendations
  • Provide Linux/NFS connection instructions before or alongside Windows/SMB instructions to ensure parity.
  • Include detailed Linux examples, such as sample output from mount commands and step-by-step guidance for accessing shares in Linux file managers (e.g., Nautilus, Dolphin).
  • Mention Linux tools and patterns (e.g., using 'mount', browsing shares via GUI) with equal prominence to Windows tools.
  • Clarify that both SMB and NFS are supported equally, and avoid language that positions SMB/Windows as the default or primary use case.
  • Add troubleshooting tips and caveats for Linux users similar to those provided for Windows users.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-deploy-provision-vmware.md ...ox-gateway/data-box-gateway-deploy-provision-vmware.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 Powershell Heavy
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows as the guest OS, requiring selection of 'Windows Server 2016 (64-bit)' during VM creation, and providing only Windows PowerShell cmdlets (e.g., Set-HcsIpAddress) for network configuration. There are no Linux guest OS instructions, nor are Linux shell commands or configuration patterns mentioned. The tutorial assumes the virtual device is Windows-based and does not address Linux alternatives or parity.
Recommendations
  • Provide instructions for provisioning the Data Box Gateway with a Linux guest OS, if supported, including selection of appropriate Linux distributions and versions.
  • Include Linux shell command equivalents for network configuration (e.g., using ip, nmcli, or netplan) alongside PowerShell examples.
  • Clarify whether the Data Box Gateway image is Windows-only or if Linux-based images are available, and document any limitations.
  • If only Windows is supported, explicitly state this early in the documentation to set expectations for Linux users.
  • Add troubleshooting and configuration steps relevant to Linux environments, such as handling network interfaces and disk mounting.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-deploy-prep.md ...ticles/databox-gateway/data-box-gateway-deploy-prep.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 prioritizing Windows Server/Hyper-V as the primary platform for provisioning Data Box Gateway, with explicit references to Windows Server versions and Hyper-V. There are no examples, instructions, or mentions of Linux-based hypervisors (such as KVM or Xen), nor are Linux-specific deployment patterns or tools discussed. VMware ESXi is mentioned as an alternative, but Linux platforms are entirely absent from prerequisites, download options, and step-by-step instructions.
Recommendations
  • Add explicit support and instructions for deploying Data Box Gateway on Linux-based hypervisors (e.g., KVM, Xen), including prerequisites, image formats (such as QCOW2), and step-by-step guides.
  • Include Linux-specific examples for downloading, unzipping, and provisioning the virtual device image.
  • Mention Linux-compatible management tools and patterns where relevant, such as using libvirt/virt-manager or command-line tools for VM provisioning.
  • Clarify platform support in prerequisites and download sections, listing all supported host OS types in parallel (Windows, Linux, VMware) rather than prioritizing Windows.
  • If Linux is not supported, explicitly state this in the documentation to avoid confusion and set expectations for cross-platform users.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-deploy-provision-hyperv.md ...ox-gateway/data-box-gateway-deploy-provision-hyperv.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 is heavily biased toward Windows environments, specifically Windows Server and Hyper-V. All instructions, screenshots, and tooling references are for Windows only, with no mention of Linux or cross-platform alternatives. PowerShell cmdlets are used for network configuration, and there are no examples or guidance for Linux-based hypervisors (such as KVM, QEMU, or VMware on Linux), nor for Linux command-line equivalents. The documentation assumes the user is operating in a Windows ecosystem from start to finish.
Recommendations
  • Add equivalent instructions for provisioning Data Box Gateway on Linux-based hypervisors (e.g., KVM, QEMU, VMware Workstation/Fusion on Linux).
  • Include Linux-specific prerequisites, such as required hardware resources and supported distributions.
  • Provide command-line examples for Linux (e.g., using virsh, qemu-img, or other relevant tools) for creating and configuring virtual machines and disks.
  • Offer guidance for network configuration on Linux, including how to set static IPs using common Linux tools (e.g., ip, nmcli, netplan).
  • Clarify whether the Data Box Gateway VHDX image can be used on non-Hyper-V platforms and, if so, provide conversion steps (e.g., using qemu-img to convert VHDX to other formats).
  • Ensure parity in troubleshooting and diagnostic steps for Linux environments.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-system-requirements.md ...atabox-gateway/data-box-gateway-system-requirements.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 demonstrates a Windows bias by listing Hyper-V (a Windows virtualization platform) first in the supported virtualization platforms table, with no mention of Linux-native hypervisors such as KVM or Xen. There are no explicit Linux examples, and the only virtualization tools referenced are Windows-centric (Hyper-V) and VMware (which is cross-platform but not Linux-native). There is no discussion of Linux-specific deployment patterns, tools, or troubleshooting steps. The documentation does not mention Linux command-line tools or provide parity for Linux administrators.
Recommendations
  • Add explicit support statements and examples for Linux-native hypervisors (e.g., KVM, Xen) if supported.
  • Include Linux-specific deployment and configuration instructions, such as using Linux CLI tools for networking and firewall configuration.
  • Provide parity in examples and troubleshooting steps for both Windows and Linux environments.
  • List Linux platforms alongside Windows platforms in tables and descriptions, rather than only referencing Windows tools first.
  • If VMware is supported on Linux hosts, clarify this and provide Linux-specific guidance.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-monitor.md ...n/articles/databox-gateway/data-box-gateway-monitor.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 Windows bias primarily through the exclusive mention of Hyper-V (a Windows virtualization technology) for expanding device capacity, with no reference to Linux-based hypervisors (such as KVM or VMware on Linux). The linked instructional material is also Windows-specific. There are no Linux-specific examples, instructions, or tool mentions, and the documentation does not provide parity for Linux users managing Azure Data Box Gateway devices.
Recommendations
  • Include instructions for adding data disks using popular Linux hypervisors (e.g., KVM, VMware Workstation/ESXi on Linux).
  • Provide links to Linux-specific documentation or video tutorials for expanding virtual device capacity.
  • Add examples or references for monitoring and managing the device using Linux tools or command-line utilities where applicable.
  • Ensure that any referenced guides or external resources (such as YouTube videos) have Linux equivalents or alternatives.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-security.md .../articles/databox-gateway/data-box-gateway-security.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 demonstrates a Windows bias by referencing Windows-specific security features (Windows Defender Device Guard, BitLocker), providing remote management instructions only for PowerShell, and linking to Windows-centric resources (Hyper-V Manager, BitLocker support). There are no examples or mentions of equivalent Linux tools, management interfaces, or security practices, and Linux hypervisors or management patterns are not discussed.
Recommendations
  • Include Linux-specific security features and instructions, such as SELinux, AppArmor, or Linux-native disk encryption (e.g., LUKS).
  • Provide remote management examples using SSH, Bash, or other Linux-native tools alongside PowerShell.
  • Reference and link to Linux hypervisor documentation (e.g., KVM, VMware ESXi) and describe how to secure Data Box Gateway devices in those environments.
  • Present cross-platform examples in parallel, ensuring that Linux instructions are given equal prominence and detail as Windows instructions.
  • Clarify which features are Windows-only and offer Linux alternatives where possible.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-use-cases.md ...articles/databox-gateway/data-box-gateway-use-cases.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 explicit instructions for using Azure PowerShell to set blob tiers, mentioning PowerShell before Azure Lifecycle Management (which is platform-neutral), and omitting any Linux-specific command-line examples or guidance. There are no references to Linux tools or shell commands for managing blob tiers or interacting with Data Box Gateway, and the examples and screenshots use terminology and workflows familiar to Windows users (e.g., SMB protocol, PowerShell scripts), with no parity for Linux users.
Recommendations
  • Add Linux-specific examples for setting blob tiers, such as using Azure CLI or REST API commands.
  • Include sample workflows for data transfer using NFS (which is more common on Linux) alongside SMB examples.
  • Provide equivalent shell scripts or command-line instructions for Linux environments where PowerShell is not available or preferred.
  • Ensure that references to management tools (e.g., PowerShell, Azure Portal) are balanced with platform-neutral or Linux-friendly alternatives.
  • Explicitly mention compatibility and best practices for Linux deployments in relevant sections.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-manage-access-power-connectivity-mode.md ...data-box-gateway-manage-access-power-connectivity-mode.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell commands for resource provider registration, which are specific to Windows environments. There are no equivalent examples for Linux users (e.g., Azure CLI or Bash), nor is there mention of Linux tools or workflows. This creates a bias toward Windows and PowerShell users, potentially excluding or inconveniencing Linux administrators.
Recommendations
  • Add Azure CLI examples alongside PowerShell commands for resource provider registration and querying.
  • Explicitly mention that both Windows and Linux are supported, and provide instructions or links for Linux users.
  • Where PowerShell is used, clarify that Azure CLI or REST API alternatives exist and link to relevant documentation.
  • Review other management workflows (e.g., device password changes, connectivity mode) to ensure parity in instructions for Linux environments, especially if any steps differ.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-deploy-provision-hyperv.md ...ox-gateway/data-box-gateway-deploy-provision-hyperv.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments, specifically Windows Server and Hyper-V. All instructions, prerequisites, and screenshots reference Windows tools (Server Manager, Hyper-V Manager), and there are no examples or guidance for Linux hosts or alternative hypervisors (e.g., KVM, VMware on Linux). Network configuration steps use Windows PowerShell cmdlets, with no Linux equivalents provided. The documentation assumes the user is operating in a Windows ecosystem from start to finish.
Recommendations
  • Add equivalent instructions for provisioning Data Box Gateway on Linux hosts using supported hypervisors (e.g., KVM, VMware Workstation/ESXi on Linux).
  • Include Linux-specific prerequisites, such as required packages, hardware requirements, and supported distributions.
  • Provide step-by-step examples for creating and configuring virtual machines using Linux tools (e.g., virsh, virt-manager, qemu-img).
  • Offer network configuration guidance for Linux environments, including commands for setting static IPs (e.g., using nmcli, ip, or netplan).
  • Clarify whether Data Box Gateway is supported on non-Windows hypervisors and, if not, explicitly state this limitation earlier in the documentation.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-deploy-provision-vmware.md ...ox-gateway/data-box-gateway-deploy-provision-vmware.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation demonstrates a Windows bias in several ways: the guest OS is specified as Windows Server 2016, with no mention of Linux alternatives; network configuration examples use only Windows PowerShell cmdlets (Set-HcsIpAddress, Get-HcsIpAddress) without Linux equivalents; and there are no instructions or examples for provisioning or configuring the Data Box Gateway using Linux as the guest OS or for Linux-based administration. All screenshots and steps assume a Windows environment, and there is no guidance for users who may wish to use Linux tools or patterns.
Recommendations
  • Include instructions and screenshots for provisioning the Data Box Gateway with a Linux guest OS, if supported.
  • Provide Linux-based network configuration examples, such as using 'ip', 'ifconfig', or 'nmcli' commands.
  • Clarify whether Linux is supported as a guest OS and, if not, explicitly state this in the prerequisites.
  • If PowerShell cmdlets are required, explain how Linux users can access or use these tools (e.g., via PowerShell Core on Linux or alternative methods).
  • Add troubleshooting and setup steps relevant to Linux environments, including log collection and diagnostics.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-2409-release-notes.md ...databox-gateway/data-box-gateway-2409-release-notes.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure Data Box Gateway 2409 release notes exhibits Windows bias by referencing Windows-specific technologies (e.g., Hyper-V, Defender-based Device Guard, .NET framework) without mentioning Linux equivalents or support. There are no examples, instructions, or notes for Linux-based environments, and all enhancements and compatibility notes are Windows-centric.
Recommendations
  • Include information on Linux compatibility, such as supported hypervisors (e.g., KVM, VMware) and security tools (e.g., SELinux, AppArmor).
  • Provide examples or notes for Linux-based deployment and management, if supported.
  • Clarify whether features like Defender-based Device Guard and .NET framework updates impact Linux users, or provide Linux alternatives.
  • Add explicit statements about OS support (Windows vs. Linux) and any limitations for non-Windows environments.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-2101-release-notes.md ...databox-gateway/data-box-gateway-2101-release-notes.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Data Box Gateway 2101 release notes demonstrates a Windows bias. It references cumulative Windows and .NET framework updates as a key part of the release, without mentioning any Linux equivalents or updates. There are no examples, instructions, or notes relevant to Linux environments, and all tooling and update references are Windows-centric.
Recommendations
  • Include information about Linux support, if available, such as kernel or package updates relevant to Data Box Gateway.
  • Provide parity in release notes by mentioning any Linux-specific issues, updates, or workarounds.
  • Add examples or instructions for both Windows and Linux environments where applicable, especially in deployment or troubleshooting sections.
  • Clarify platform support in the documentation introduction, specifying whether Data Box Gateway is Windows-only or cross-platform.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-monitor.md ...n/articles/databox-gateway/data-box-gateway-monitor.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Hyper-V (a Windows virtualization technology) and linking to a YouTube video specifically about adding a hard drive for Hyper-V virtual machines. There are no equivalent instructions or references for Linux-based hypervisors (such as KVM or VMware on Linux), nor are there examples or guidance for Linux users. The documentation assumes a Windows environment for device management and expansion tasks.
Recommendations
  • Include instructions and references for adding data disks in popular Linux hypervisors such as KVM and VMware.
  • Provide parity in examples and links for both Windows and Linux environments when discussing device management tasks.
  • Explicitly mention support for Linux-based management tools and provide step-by-step guidance for Linux users.
  • Avoid referencing only Windows-specific tools (such as Hyper-V) or, if referenced, ensure Linux equivalents are also covered.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-deploy-prep.md ...ticles/databox-gateway/data-box-gateway-deploy-prep.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows Server/Hyper-V as the primary host platform for provisioning Data Box Gateway, with VMware ESXi as the only alternative. There are no examples or instructions for Linux-based hypervisors (such as KVM or Xen), nor are Linux tools or patterns mentioned for image deployment, management, or activation. All prerequisites and download instructions focus on Windows and VMware environments, omitting Linux entirely.
Recommendations
  • Add instructions and examples for deploying Data Box Gateway on Linux-based hypervisors (e.g., KVM, Xen).
  • Include download options for virtual device images compatible with Linux platforms (e.g., QCOW2 for KVM).
  • Provide Linux command-line examples for image deployment, activation, and management alongside Windows/PowerShell examples.
  • Mention Linux tools and patterns (such as virt-manager, qemu-img, or libvirt) where relevant.
  • Clearly state platform limitations and support in the prerequisites section, and consider parity in future product support.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-system-requirements.md ...atabox-gateway/data-box-gateway-system-requirements.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing Hyper-V (a Windows virtualization platform) first in the supported virtualization platforms table, and providing detailed version support for it. There is no mention of Linux-native virtualization platforms such as KVM or Xen. The page also references Windows-centric tools (Hyper-V, VMware) without Linux equivalents, and does not provide Linux-specific deployment or configuration examples. There are no explicit Linux command-line or tool references, nor guidance for Linux administrators.
Recommendations
  • Add support and documentation for Linux-native virtualization platforms (e.g., KVM, Xen, VirtualBox) if applicable.
  • Include Linux-specific examples for deployment, configuration, and connectivity.
  • Provide parity in tool references, such as mentioning Linux alternatives to Hyper-V and VMware.
  • Ensure that any referenced scripts, commands, or configuration steps include both Windows (PowerShell, CMD) and Linux (bash, shell) versions.
  • Clarify any platform-specific limitations or requirements for Linux hosts and clients.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-deploy-add-shares.md .../databox-gateway/data-box-gateway-deploy-add-shares.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting Windows/SMB connection instructions and examples before Linux/NFS equivalents. The SMB section uses Windows-specific tools (net use, File Explorer, Windows + R) and provides detailed PowerShell output, while the Linux/NFS section is shorter and less detailed. There is more emphasis on Windows workflows and tools, with Linux instructions presented second and with less context.
Recommendations
  • Present Linux/NFS and Windows/SMB instructions in parallel, or alternate which platform is shown first.
  • Provide equally detailed command examples and screenshots for Linux workflows (e.g., show terminal output for NFS mount, file browsing in Linux file managers).
  • Include troubleshooting tips and caveats for both platforms, not just Windows.
  • Mention cross-platform tools (e.g., smbclient for Linux) when discussing SMB shares.
  • Avoid using Windows-specific terminology (e.g., File Explorer, Windows + R) without Linux equivalents (e.g., Nautilus, Dolphin, or CLI alternatives).
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-manage-shares.md ...cles/databox-gateway/data-box-gateway-manage-shares.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates Windows bias by prioritizing SMB (Windows standard) as the default share type and referencing Windows tools like File Explorer for permission management. Examples and instructions for managing shares and permissions are focused on Windows workflows, with minimal detail for NFS (Linux) shares and no Linux-specific management examples or tool references. There is no mention of Linux command-line tools or procedures for managing NFS shares, and the documentation lacks parity in guidance for Linux administrators.
Recommendations
  • Provide step-by-step examples for managing NFS shares using Linux tools (e.g., mounting NFS shares, setting permissions via Linux commands).
  • Reference Linux file management tools (e.g., Nautilus, command-line utilities) alongside Windows File Explorer.
  • Include screenshots and instructions for Linux environments where relevant.
  • Clarify differences in user and permission management for NFS shares, including how Linux clients interact with share permissions.
  • Ensure that both SMB and NFS workflows are equally detailed and accessible to users of both platforms.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-use-cases.md ...articles/databox-gateway/data-box-gateway-use-cases.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 primarily through the use of Azure PowerShell as the only explicit scripting example for moving blobs to the Archive tier. There are no Linux-specific CLI examples (such as Azure CLI or Bash), and PowerShell is mentioned before the alternative (Lifecycle Management policy), reinforcing a Windows-first approach. The documentation does not provide parity for Linux users in terms of command-line instructions or tooling references.
Recommendations
  • Add Azure CLI (az) examples for blob tier management alongside PowerShell instructions.
  • Explicitly mention that both Windows and Linux clients can use SMB/NFS, and provide sample commands for both platforms.
  • Include Bash scripting examples for common operations, such as moving blobs between tiers.
  • Reference Linux tools (e.g., azcopy, shell scripts) where appropriate, and provide step-by-step instructions.
  • Ensure that any PowerShell instructions are matched with equivalent Linux/Unix instructions in the same section, not relegated to later or omitted.
GitHub Create Pull Request
Databox Gateway https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/databox-gateway/data-box-gateway-2007-release-notes.md ...databox-gateway/data-box-gateway-2007-release-notes.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by mentioning Windows VHD base image updates and cumulative Windows/.NET updates, without reference to Linux equivalents or updates. There are no examples or notes about Linux-based deployment, troubleshooting, or parity. The release notes focus on Windows tooling and update patterns, and do not provide Linux-specific information or guidance.
Recommendations
  • Include information about Linux-based deployments, if supported, such as updates to Linux images or kernel versions.
  • Provide parity in update notes by mentioning both Windows and Linux cumulative updates, where applicable.
  • Add troubleshooting steps or examples for both Windows and Linux environments.
  • Clarify whether features or fixes apply to Linux-based devices, and explicitly state any platform limitations.
  • If only Windows is supported, make this explicit to avoid confusion and help set user expectations.
GitHub Create Pull Request
← Previous Page 2 of 5 Next →