Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 1176-1200 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-incremental-copy-overview.md
...les/data-factory/tutorial-incremental-copy-overview.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page consistently references tutorials and step-by-step instructions that use PowerShell, a Windows-centric tool, for incremental data copy tasks. There are no examples, instructions, or references to Linux-native tools, shell scripts, or cross-platform command-line interfaces. The exclusive use of PowerShell in links and tutorial names, and the absence of Linux or bash alternatives, indicate a strong Windows/PowerShell bias.
Recommendations
- Provide equivalent step-by-step tutorials using Azure CLI, which is cross-platform, or bash scripts for Linux users.
- Include explicit references and links to Linux-compatible tools and workflows alongside PowerShell examples.
- Ensure that all code samples and templates are available in both PowerShell and bash/Azure CLI formats.
- Add a section or callout explaining how Linux/macOS users can perform the same incremental copy operations.
- Review related content and next steps to ensure Linux parity in all recommended learning paths.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-copy-data-dot-net.md
...n//articles/data-factory/tutorial-copy-data-dot-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias by exclusively using Visual Studio (a Windows-centric IDE) and the .NET SDK for all code and project setup. All instructions and screenshots assume a Windows environment, with references to Notepad, Visual Studio, and SQL Server Management Studio (SSMS)βall Windows tools. There are no examples or guidance for Linux users (e.g., using VS Code, .NET CLI, or cross-platform editors), nor are there any alternative command-line instructions (such as Bash or Azure CLI). Package installation is shown only via the NuGet Package Manager Console (PowerShell-based), with no mention of dotnet CLI or other cross-platform methods.
Recommendations
- Provide alternative instructions for Linux/macOS users, such as using VS Code or JetBrains Rider instead of Visual Studio.
- Include .NET CLI commands (e.g., 'dotnet new console', 'dotnet add package ...') for project and package management, which work cross-platform.
- Mention cross-platform editors (e.g., VS Code, Vim, Emacs) for editing files instead of only Notepad and Visual Studio.
- Show how to run and debug the application using the dotnet CLI, not just Visual Studio menus.
- Reference Azure CLI or Bash scripts for resource creation and management, in addition to or instead of PowerShell/Windows tools.
- Suggest cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd) for verifying results, not just SSMS.
- Explicitly state that the tutorial can be followed on Linux/macOS with appropriate tools, and link to relevant setup guides.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-incremental-copy-portal.md
...icles/data-factory/tutorial-incremental-copy-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (SQL Server Management Studio), omitting Linux alternatives for database management, and providing instructions that assume a Windows environment. There are no examples or guidance for Linux users, such as using Azure Data Studio, sqlcmd, or other cross-platform tools. The browser instructions are neutral, but the database setup and verification steps are Windows-centric.
Recommendations
- Include Linux-friendly alternatives to SQL Server Management Studio, such as Azure Data Studio or the sqlcmd CLI, with example commands for table creation and data manipulation.
- Add explicit instructions or notes for Linux/macOS users on how to perform the same database operations from their platforms.
- Where GUI tools are referenced, provide equivalent CLI commands that work cross-platform.
- Review all tool references to ensure that at least one cross-platform option is always mentioned alongside any Windows-specific tool.
- Consider adding a section or callout box summarizing cross-platform options for all required tooling.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-transform-data-hive-virtual-network-portal.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-transform-data-hive-virtual-network-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Azure PowerShell, providing instructions for editing the Windows hosts file, and omitting equivalent Linux/Unix instructions. There are no examples or guidance for Linux users regarding command-line tools, file paths, or system administration tasks, making the tutorial less accessible for those using Linux-based VMs or environments.
Recommendations
- Provide equivalent instructions for Linux users, such as using Azure CLI instead of (or alongside) Azure PowerShell for setup and management tasks.
- Include guidance for editing the /etc/hosts file on Linux VMs, not just the Windows hosts file.
- Mention that the self-hosted integration runtime can be installed on both Windows and Linux VMs, and provide links or steps for both platforms.
- When referencing tools or commands (e.g., PowerShell), offer alternatives or parallel instructions for Bash or other common Linux shells.
- Ensure screenshots and file path examples are not exclusively Windows-centric; include Linux equivalents where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-transform-data-spark-portal.md
...s/data-factory/tutorial-transform-data-spark-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by requiring Azure PowerShell for setup, referencing only PowerShell installation instructions, and omitting any mention of Linux or cross-platform CLI alternatives (such as Azure CLI or azcopy) for uploading files or managing resources. No Linux shell or command-line examples are provided, and the prerequisites assume a Windows-centric toolchain.
Recommendations
- Add instructions for using Azure CLI (az) to perform all setup steps, including uploading files to Blob storage and managing resources.
- Include Linux/macOS shell command examples (e.g., using azcopy, curl, or Azure CLI) alongside or instead of PowerShell commands.
- In the prerequisites, mention both Azure PowerShell and Azure CLI as supported options, with links to installation guides for each.
- Explicitly state that all steps can be performed from Windows, Linux, or macOS, and provide parity in tooling and examples.
- Where file uploads are discussed, provide sample commands for both PowerShell and Bash (using azcopy or Azure CLI).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-manager-for-agri/how-to-set-up-private-links.md
...s/data-manager-for-agri/how-to-set-up-private-links.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation lists PowerShell before Azure CLI when describing command-line options for creating private endpoints, which may suggest a Windows-first or PowerShell-heavy bias. There are no explicit Linux-specific examples, screenshots, or references, and the CLI link is not labeled as 'Azure CLI' or 'Bash', which could help Linux users. The approval process and screenshots are portal-based, which is cross-platform, but the lack of Linux/CLI parity in the walkthrough is notable.
Recommendations
- List Azure CLI before PowerShell when presenting cross-platform command-line options, or present both equally.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows.
- Provide example commands for both PowerShell and Azure CLI inline, not just as links.
- Include at least one screenshot or terminal snippet showing Azure CLI usage on a Linux terminal.
- Clarify that the Azure portal is web-based and accessible from any OS.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-transform-data-spark-powershell.md
...ta-factory/tutorial-transform-data-spark-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong bias toward Windows and PowerShell. All command-line examples are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or cross-platform alternatives. The tutorial assumes the use of Azure PowerShell throughout, and there are no instructions or guidance for users on Linux or macOS. The prerequisite section only references Azure PowerShell, and the workflow is tightly coupled to Windows-centric tooling and patterns.
Recommendations
- Provide equivalent Azure CLI (az) commands alongside PowerShell for all deployment and management steps, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that the tutorial can be followed on Linux/macOS, and provide guidance for setting up the environment on those platforms.
- Add Bash shell script examples for key steps, such as uploading files to Azure Storage (using az storage blob upload or similar), and deploying resources.
- In the prerequisites, include instructions for installing Azure CLI and/or using the Azure Portal as alternatives to PowerShell.
- Where PowerShell is referenced, clarify that it is available on all platforms, but also offer alternative command-line approaches.
- Consider restructuring the tutorial to present cross-platform or platform-neutral approaches first, or at least in parallel with Windows-specific instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-monitor-kubernetes-dashboard.md
...e/azure-stack-edge-gpu-monitor-kubernetes-dashboard.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing instructions and file paths specific to Windows (e.g., editing C:\Windows\System32\Drivers\etc\hosts), referencing the Windows Certificate Import Wizard, and omitting equivalent steps or guidance for Linux or macOS users. There are no Linux-specific commands, file paths, or certificate installation instructions, making it less accessible for non-Windows users.
Recommendations
- Include parallel instructions for Linux and macOS users, such as editing /etc/hosts and installing certificates using Linux tools (e.g., update-ca-certificates or certutil).
- Provide example commands for Linux (and optionally macOS) alongside Windows steps, especially for file paths and certificate management.
- Clearly indicate when a step is OS-specific and offer alternatives for other platforms.
- Add screenshots or terminal commands relevant to Linux environments where appropriate.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-share/share-your-data-arm.md
.../blob/main//articles/data-share/share-your-data-arm.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides a PowerShell script for resource cleanup without offering equivalent Bash/Azure CLI examples. It references only the Azure Portal (a web UI) and PowerShell, which are common in Windows-centric workflows, and omits Linux-native command-line alternatives. There are no Linux or cross-platform CLI instructions for deploying or managing resources.
Recommendations
- Provide Azure CLI (az) and/or Bash script examples alongside PowerShell for resource cleanup and management.
- Explicitly mention that the Azure Portal is cross-platform, but also offer CLI-based deployment instructions for users who prefer terminal workflows.
- Ensure that all code snippets and automation steps have both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI) equivalents.
- Add a note or section on how to perform the same tasks from a Linux or macOS environment, including installation and usage of the Azure CLI.
Azure Docs
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page references cumulative Windows and .NET framework updates as part of the release, with no mention of Linux or cross-platform equivalents. There are no examples or notes regarding Linux environments, and the update process is described only in the context of Windows-based systems. This suggests a Windows-first perspective and omits guidance for Linux users.
Recommendations
- Include information about Linux support or lack thereof for Azure Data Box Gateway, if applicable.
- If Linux is supported, mention relevant Linux kernel or software updates alongside Windows/.NET updates.
- Provide explicit statements or examples for Linux users regarding deployment, updates, and known issues.
- Clarify whether the product is Windows-only or cross-platform early in the documentation.
Azure Docs
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows/Hyper-V as the primary provisioning method, mentioning Windows Server versions explicitly, and omitting any mention of Linux-based hypervisors (such as KVM or VirtualBox) or native Linux deployment options. All host system requirements and download links are for Hyper-V (Windows) or VMware ESXi, with no Linux-native alternatives or instructions provided.
Recommendations
- Include explicit instructions or references for deploying Data Box Gateway on Linux-based hypervisors (e.g., KVM, VirtualBox) if supported.
- Present provisioning options for Windows and Linux platforms in parallel, rather than listing Windows/Hyper-V first.
- Add a section or note clarifying Linux compatibility, or explicitly state if Linux host support is not available.
- If Linux is not supported, provide a rationale and suggest alternative Azure data transfer solutions for Linux users.
- Ensure that prerequisites and examples mention both Windows and Linux environments where applicable.
Azure Docs
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 →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows guest OS settings (e.g., instructing users to select 'Windows' and 'Microsoft Windows Server 2016 (64-bit)' as the guest OS in VMware), and by providing only PowerShell cmdlet examples (e.g., Set-HcsIpAddress) for network configuration. There are no Linux-based examples or mentions of Linux guest OS support, nor are there alternative instructions for Linux users.
Recommendations
- Include instructions and screenshots for provisioning the Data Box Gateway as a Linux guest OS, if supported, or clarify OS support limitations.
- Provide equivalent Linux shell commands or configuration steps for network setup, in addition to the PowerShell cmdlets.
- Explicitly state whether Linux-based management or configuration is supported or unsupported, and provide guidance for Linux administrators where possible.
- If only Windows is supported, clarify this early in the prerequisites and provisioning steps to set user expectations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-certificate-troubleshooting.md
...ne/azure-stack-edge-gpu-certificate-troubleshooting.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation references Windows-specific tools and patterns, such as 'Windows PowerShell' and 'Microsoft RSA/Schannel Cryptographic Provider', without mentioning Linux equivalents or providing cross-platform guidance. There are no Linux or cross-platform examples or references, and the troubleshooting steps assume a Windows environment.
Recommendations
- Include Linux equivalents for certificate management tools (e.g., OpenSSL commands for certificate inspection and troubleshooting).
- Mention cross-platform certificate providers and clarify if only Windows cryptographic providers are supported or if there are alternatives for Linux.
- Add troubleshooting steps and examples for Linux users, such as how to check certificate properties and key usage using Linux command-line tools.
- Clarify whether device management and certificate operations can be performed from Linux or only from Windows, and provide guidance accordingly.
- Ensure that references to PowerShell are balanced with Bash or other Linux shell examples where applicable.
Azure Docs
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page exhibits a Windows bias by referencing Windows-specific security tools (Windows Defender, Device Guard, BitLocker), providing only PowerShell-based remote management instructions, and omitting Linux equivalents or examples. Hyper-V and BitLocker are mentioned as primary solutions for encryption and virtualization, with no mention of Linux hypervisors or Linux-native security/encryption tools. Linux management and security options are not discussed, and all examples and links are Windows-centric.
Recommendations
- Include equivalent Linux-based instructions and examples for device management, such as SSH or Linux CLI commands for remote access.
- Mention and provide guidance for using Linux-native security tools (e.g., SELinux, AppArmor, dm-crypt/LUKS) for protecting the virtual device and data at rest.
- Reference Linux-compatible hypervisors (e.g., KVM, VMware ESXi) and provide links or instructions for enabling encryption and security features on those platforms.
- Ensure that documentation for remote management covers both PowerShell (Windows) and SSH/CLI (Linux) scenarios.
- Present Windows and Linux options in parallel, or at least mention Linux alternatives wherever Windows tools or patterns are described.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-gateway/data-box-gateway-deploy-connect-setup-activate.md
...eway/data-box-gateway-deploy-connect-setup-activate.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a subtle Windows bias. It references provisioning in Hyper-V (a Windows technology) before VMware, uses 'time.windows.com' as the default NTP server, and only mentions NTLM (a Windows authentication protocol) for proxy authentication. There are no explicit Linux or cross-platform command-line examples, and Linux-specific tools or patterns are not discussed.
Recommendations
- Present VMware and Hyper-V provisioning instructions in parallel or mention VMware first in some instances to balance platform order.
- Include Linux-friendly NTP server defaults (e.g., pool.ntp.org) alongside 'time.windows.com'.
- Mention and provide examples for Linux-based authentication methods for proxies (e.g., Basic, Digest) if supported.
- Clarify that the device and web UI are accessible from any OS/browser, and provide screenshots or notes relevant to Linux users where applicable.
- If command-line or scripting is referenced in future sections, ensure both PowerShell (Windows) and Bash (Linux) examples are provided.
Azure Docs
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing SMB (the Windows protocol) as the default share type, referencing File Explorer for permissions management, and omitting concrete Linux/NFS client usage examples. While NFS is mentioned as an option for Linux clients, there are no instructions or examples for Linux users, and Windows tools and patterns are referenced exclusively.
Recommendations
- Provide step-by-step examples for both SMB (Windows) and NFS (Linux) share creation and access, including Linux client mounting instructions.
- Include Linux command-line examples (e.g., using mount for NFS shares) alongside or after Windows/SMB instructions.
- Reference Linux tools (such as the mount command, or NFS client configuration) in relevant sections, not just Windows tools like File Explorer.
- Balance the order of presentation: mention NFS and Linux usage equally or alternate the order in which SMB and NFS are described.
- Add troubleshooting tips and permission management guidance for Linux/NFS users, similar to the File Explorer guidance for Windows users.
Azure Docs
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting Windows/SMB connection instructions before Linux/NFS, providing detailed Windows command-line and GUI (File Explorer) steps, and referencing Windows-specific tools (e.g., 'net use', Windows + R, File Explorer) without Linux GUI equivalents. The Linux/NFS section is less detailed and lacks parity in user experience guidance.
Recommendations
- Alternate the order of SMB (Windows) and NFS (Linux) instructions, or present them in parallel to avoid privileging Windows.
- Provide equivalent Linux GUI instructions (e.g., how to mount NFS shares using Nautilus or other file managers) to match the Windows File Explorer steps.
- Include Linux command-line examples for SMB (using smbclient or mount.cifs) to show cross-platform parity.
- Clarify that both Windows and Linux are first-class clients, and ensure language does not default to Windows as the primary use case.
- Where possible, use neutral language and avoid assuming the user is on Windows (e.g., 'On your client machine...' instead of 'On your Windows Server client...').
Azure Docs
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing explicit instructions and links for using Azure PowerShell to set blob tiers, without mentioning or providing equivalent examples for Linux users (e.g., using Azure CLI or REST API). The mention of PowerShell as a primary method and the absence of Linux/Unix tooling or command-line examples creates an implicit preference for Windows environments.
Recommendations
- Include Azure CLI examples alongside PowerShell instructions for tasks such as setting blob tiers, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that both Windows and Linux clients can use SMB and NFS protocols to interact with Data Box Gateway, and provide example commands for both environments.
- Add references or links to REST API documentation for users who may wish to automate tasks from non-Windows systems.
- Where PowerShell is mentioned, clarify that it is available cross-platform, but also provide Linux-native alternatives.
- Ensure that screenshots and UI instructions do not assume a Windows environment unless absolutely necessary.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-collect-virtual-machine-guest-logs.md
...zure-stack-edge-gpu-collect-virtual-machine-guest-logs.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides only PowerShell-based instructions and commands for collecting VM guest logs, which are specific to Windows environments. There are no equivalent CLI or shell examples for Linux users. While log file locations for both Linux and Windows VMs are mentioned, the actual log collection process is described solely using Windows/PowerShell tools, with no Linux-native alternatives or parity.
Recommendations
- Include equivalent Linux shell (bash) commands for collecting guest logs, such as using SSH and tar/scp to gather log files from Linux VMs.
- Provide instructions for accessing the Linux command line interface on the device, if supported, or clarify if only PowerShell is available.
- List both Windows and Linux methods side by side or in separate sections to ensure parity and clarity for users of both platforms.
- If PowerShell Core is required for cross-platform use, specify this and provide examples for Linux environments.
Azure Docs
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments, specifically focusing exclusively on provisioning Azure Data Box Gateway in Hyper-V on Windows Server. All instructions, screenshots, and tooling references are for Windows (e.g., Hyper-V Manager, Server Manager, BitLocker, PowerShell cmdlets). There are no examples, prerequisites, or alternative instructions for Linux hosts, Linux-based hypervisors (like KVM), or cross-platform virtualization tools. Linux users are not addressed at all.
Recommendations
- Add a parallel tutorial or section for provisioning Data Box Gateway using a Linux-based hypervisor (e.g., KVM, VirtualBox, or VMware Workstation on Linux).
- Include Linux-specific prerequisites, such as required packages, minimum kernel versions, and disk image compatibility (e.g., handling VHDX files on Linux).
- Provide Linux command-line examples for copying images, configuring virtual machines, and setting up networking (e.g., using virsh, qemu-img, or nmcli).
- Mention Linux-native encryption options (such as LUKS) as alternatives to BitLocker.
- Clarify in the overview and prerequisites whether Linux is supported or not, and if not, provide a rationale or a link to Linux support status.
- If PowerShell cmdlets are required inside the virtual device, clarify whether these are available in the device OS regardless of the host platform, and provide Linux-friendly ways to interact if possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-gateway/data-box-gateway-monitor.md
...//articles/databox-gateway/data-box-gateway-monitor.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools and patterns (e.g., Hyper-V, adding a hard drive via Hyper-V, and linking to a YouTube video about Hyper-V) without mentioning or providing equivalent instructions for Linux-based hypervisors (such as KVM or VMware on Linux). There are no Linux-specific examples or guidance for managing or monitoring the Data Box Gateway device in a Linux environment.
Recommendations
- Include instructions and examples for adding data disks and managing virtual devices using popular Linux hypervisors (e.g., KVM, VMware).
- Provide links or references to Linux-specific documentation or tutorials alongside Windows/Hyper-V resources.
- Ensure that all management and monitoring steps are described in a platform-agnostic way, or provide parallel instructions for both Windows and Linux environments.
- Explicitly mention supported platforms and clarify any platform-specific limitations or requirements.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-2101-release-notes.md
...abox-online/azure-stack-edge-gpu-2101-release-notes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias through the frequent mention of PowerShell interfaces, Windows-specific tools (e.g., robocopy, Explorer), and command examples that use Windows paths or syntax. Linux equivalents are not provided or are mentioned only in passing, and some workarounds or instructions assume a Windows environment. There are also cases where only Windows-based tools or approaches are suggested, with no Linux alternatives or parity.
Recommendations
- Provide Linux/bash command equivalents alongside PowerShell and Windows command examples, especially for device management and troubleshooting.
- When referencing tools like robocopy or Explorer, also mention Linux alternatives such as rsync, cp, or file managers.
- For instructions involving connecting to the device (e.g., PowerShell interface), include SSH/bash examples for Linux/macOS users.
- Ensure that all command-line examples are cross-platform or clearly indicate platform-specific steps, ideally presenting both Windows and Linux options side by side.
- Review all references to Windows-only utilities and add corresponding Linux guidance where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-2301-release-notes.md
...abox-online/azure-stack-edge-gpu-2301-release-notes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Several workarounds and examples reference Windows-specific tools (PowerShell, RDP, Windows services, robocopy, Explorer), and some instructions are provided only for Windows environments. In some cases, Linux equivalents are missing or mentioned only as an afterthought. There are also instances where Windows interfaces are referenced as the primary or only method for troubleshooting or remediation.
Recommendations
- For every PowerShell or Windows tool example, provide equivalent Linux shell/command-line instructions where applicable.
- When referencing Windows-specific utilities (e.g., robocopy, Explorer), also mention and provide examples for Linux tools (e.g., rsync, cp, scp).
- In troubleshooting steps that involve connecting to the device (e.g., via PowerShell), include SSH or Linux-native alternatives.
- Where the workaround involves restarting services or processes on Windows, provide systemd/service commands for Linux VMs if supported.
- Review all examples and ensure Linux parity is achieved, especially for VM management, log collection, and network configuration.
- Explicitly state when a workaround or tool is only available on Windows, and suggest alternatives for Linux users.
Azure Docs
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 →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by providing only PowerShell commands for resource provider registration and listing, with no equivalent CLI or Linux shell examples. The use of PowerShell and the Az module assumes a Windows environment or at least a PowerShell-capable shell, and there is no mention of Azure CLI or Bash alternatives. This may hinder Linux or cross-platform users from following the instructions easily.
Recommendations
- Provide equivalent Azure CLI commands (e.g., 'az provider list', 'az provider register --namespace Microsoft.DataBoxEdge') alongside PowerShell examples.
- Explicitly mention that the PowerShell commands can be run on any platform where PowerShell Core is available, or provide Bash examples for Linux users.
- Add a section or note clarifying cross-platform options for managing Azure resources, including links to Azure CLI documentation.
- Ensure that future documentation includes both Windows (PowerShell) and Linux (CLI/Bash) command examples wherever possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-create-vm-with-custom-size.md
...-online/azure-stack-edge-create-vm-with-custom-size.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell commands and references connecting to the PowerShell interface, with no mention of Linux shells, cross-platform CLI tools, or alternative workflows. All examples, outputs, and tool references are Windows-centric, and there are no Linux or bash equivalents provided.
Recommendations
- Provide equivalent instructions and examples using Azure CLI (az) commands, which are cross-platform and can be run on Linux, macOS, and Windows.
- If device management is only possible via PowerShell, explicitly state this limitation and suggest alternatives or workarounds for Linux users (such as using PowerShell Core on Linux).
- Include a section or note clarifying platform requirements and offering guidance for non-Windows environments.
- Where possible, add bash or shell script examples alongside PowerShell, or clarify if the commands can be run in PowerShell Core on Linux.
- Reference cross-platform tools and interfaces before or alongside Windows-specific tools.