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 1926-1950 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/load-sap-bw-data.md
...s/blob/main//articles/data-factory/load-sap-bw-data.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by requiring the use of the SAP .NET Connector 3.0, which is only available for Windows, and by referencing installation steps and dialogs specific to Windows environments. There are no instructions or examples for Linux-based integration runtimes or alternative connectors that would enable Linux parity.
Recommendations
- Explicitly state that the SAP .NET Connector 3.0 is Windows-only and clarify platform requirements early in the prerequisites.
- Provide guidance or alternatives for Linux environments, such as using the SAP Java Connector (JCo) if supported, or clarify if Linux-based self-hosted integration runtimes are not supported for this scenario.
- If Linux is not supported, suggest possible workarounds or roadmap information for cross-platform support.
- Include a comparison table of platform support for self-hosted integration runtime and SAP connectors.
- If possible, provide Linux-based setup instructions or acknowledge the limitation and direct Linux users to relevant resources.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/known-issues-troubleshoot-guide.md
...ticles/data-factory/known-issues-troubleshoot-guide.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation assumes the use of a 'SHIR machine' without specifying OS, but the workaround for retrieving the IP address directs users to use a website from the SHIR machine, which implicitly assumes a GUI/browser environment typical of Windows. There are no Linux-specific instructions or CLI-based alternatives provided, and no mention of Linux command-line tools or headless environments.
Recommendations
- Provide Linux/Unix command-line alternatives for retrieving the IP address, such as using curl or wget (e.g., curl ifconfig.me).
- Explicitly mention that the workaround applies to both Windows and Linux SHIR hosts, and provide steps for both.
- Avoid assuming the presence of a web browser or GUI; include headless options for server environments.
- Wherever a workaround or example is given, ensure parity by including both Windows and Linux instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/solution-template-bulk-copy-with-control-table.md
...tory/solution-template-bulk-copy-with-control-table.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by only providing SQL Server/Azure SQL Database examples for the control table, without mentioning or giving examples for Linux-based databases (e.g., PostgreSQL, MySQL) or showing cross-platform SQL syntax. There are no Linux-specific instructions, tools, or screenshots, and the workflow assumes familiarity with Microsoft-centric environments.
Recommendations
- Include examples for creating the control table in popular Linux-based databases such as PostgreSQL and MySQL, with appropriate SQL syntax.
- Explicitly mention that the solution works with non-Windows databases and provide guidance for those environments.
- Add screenshots or CLI instructions that are platform-agnostic or show both Windows and Linux tools (e.g., Azure CLI, psql, mysql client).
- Clarify that the steps are not limited to SQL Server/Azure SQL Database and provide parity in documentation for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/solution-template-migration-s3-azure.md
...s/data-factory/solution-template-migration-s3-azure.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively uses Azure SQL Database and T-SQL/Stored Procedures for control tables and workflow orchestration, which are Windows-centric technologies. There are no examples or guidance for using Linux-native alternatives (such as PostgreSQL, MySQL, or open-source workflow tools), nor are there any references to Linux command-line tools or scripting environments. No PowerShell is present, but the overall workflow assumes a Windows/SQL Server ecosystem.
Recommendations
- Provide examples using open-source databases such as PostgreSQL or MySQL for the control table and stored procedure logic, including equivalent SQL and procedure code.
- Mention that Azure SQL Database is not required and that other database engines can be used, with links or examples for Linux-friendly options.
- Include guidance or examples for users who may want to orchestrate the migration using Linux-native tools (e.g., bash scripts, cron jobs, or open-source workflow orchestrators).
- Clarify that the solution is not limited to Windows environments and provide parity for Linux users in terms of setup and operation.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/transform-data-using-hadoop-streaming.md
.../data-factory/transform-data-using-hadoop-streaming.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation provides only Windows-centric examples for Hadoop Streaming activities, notably referencing '.exe' executables (e.g., MyMapper.exe, MyReducer.exe) as mapper and reducer programs. There are no examples or mentions of Linux/Unix-style scripts (such as Python, Bash, or shell scripts), which are more common in Hadoop environments. This could mislead users into thinking only Windows executables are supported, omitting the typical Linux usage patterns.
Recommendations
- Add examples using Linux/Unix-style scripts (e.g., 'MyMapper.py', 'MyReducer.sh') as mapper and reducer programs in the JSON sample.
- Explicitly state that both Windows executables and Linux scripts are supported, and clarify any platform-specific requirements.
- Provide guidance or links on how to create and upload Linux-compatible scripts for Hadoop Streaming jobs.
- Ensure that documentation does not imply a Windows-only workflow by balancing references to both Windows and Linux tools and patterns.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-copy-data-portal.md
...in//articles/data-factory/tutorial-copy-data-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Windows-specific tools and workflows (e.g., Notepad for file creation) and omitting Linux/macOS equivalents. There are no command-line examples for Linux users, and the only file creation step assumes a Windows environment. While the Azure portal is cross-platform, the instructions do not acknowledge or provide parity for Linux/macOS users.
Recommendations
- When instructing users to create a text file, mention cross-platform editors (e.g., 'Use Notepad (Windows), TextEdit (macOS), or nano/vi (Linux)').
- Include CLI-based alternatives for file creation and upload, such as using the Azure CLI or azcopy, with example commands for Linux/macOS.
- Where third-party tools are mentioned (e.g., Azure Storage Explorer), clarify that they are available on all major platforms.
- Explicitly state that all steps can be performed from Windows, Linux, or macOS, and provide notes or links for platform-specific guidance where relevant.
- Review for other subtle Windows-centric language or assumptions, and ensure parity in terminology and tool recommendations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/transform-data-using-data-lake-analytics.md
...ta-factory/transform-data-using-data-lake-analytics.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. The only file path example for the U-SQL script uses backslashes (scripts\kona\SearchLogProcessing.txt), which is a Windows convention. There are no explicit Linux or cross-platform examples or notes about path separators. No PowerShell or Windows-specific tools are mentioned, but the lack of Linux/Unix-style examples or clarifications may confuse non-Windows users.
Recommendations
- Provide both Windows (backslash) and Linux/macOS (forward slash) path examples when referencing file paths.
- Add a note clarifying that Azure Data Lake paths and script paths are platform-agnostic or specify the required separator.
- Ensure that any code snippets or configuration examples use forward slashes (/) for paths, or explicitly state if backslashes are required.
- If relevant, include CLI or scripting examples for both Windows (PowerShell, CMD) and Linux/macOS (Bash, Azure CLI).
- Review all screenshots and UI references to ensure they do not assume a Windows-only environment.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-copy-data-tool.md
...main//articles/data-factory/tutorial-copy-data-tool.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing Notepad as the default text editor for creating the sample data file, without mentioning Linux or cross-platform alternatives. No Linux-specific instructions or examples are provided for preparing the source file, and no command-line examples (such as Bash or PowerShell) are given for either platform. The rest of the tutorial is platform-agnostic, focusing on the Azure Portal UI, but the initial setup assumes a Windows environment.
Recommendations
- When instructing users to create a text file, mention cross-platform editors (e.g., 'Use Notepad (Windows), nano (Linux), or TextEdit (macOS) to create the file...').
- Provide a sample command-line instruction for creating the file, such as using 'echo' or 'cat' in Bash, to support Linux/macOS users.
- Avoid referencing only Windows tools or applications in setup steps; always include or mention Linux/macOS equivalents.
- Consider adding a note that all steps can be performed from any OS, as the Azure Portal and Storage Explorer are cross-platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/supported-file-formats-and-compression-codecs-legacy.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/supported-file-formats-and-compression-codecs-legacy.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits a mild Windows bias, primarily in its references to Windows-specific tools and patterns. For example, encoding names are referenced via .NET's Encoding.EncodingName property, and the process for locating the Java runtime on Self-hosted Integration Runtime (IR) prioritizes checking the Windows registry before checking the JAVA_HOME environment variable. There are also links to .NET and Windows-centric documentation. However, there are no explicit PowerShell examples, nor are there command-line examples that are Windows-only. Linux equivalents are not mentioned or prioritized in these areas.
Recommendations
- When referencing encoding names, provide a cross-platform resource or clarify that .NET encoding names are also applicable on Linux/Unix environments where .NET Core/.NET 5+ is used.
- In the section about locating Java for Self-hosted IR, explicitly mention how this works on Linux (if supported), or clarify that the registry check is Windows-specific and JAVA_HOME is the cross-platform method.
- Where links are provided to .NET or Windows documentation (e.g., Encoding.EncodingName, CompressionLevel), add notes or alternative links for Linux users, or clarify applicability.
- If any platform-specific setup is required (such as setting environment variables), provide both Windows and Linux syntax/examples (e.g., set vs export).
- Consider including a brief section or note on Linux/macOS compatibility for all relevant features, especially for integration runtime and file encoding/compression scenarios.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-incremental-copy-change-tracking-feature-portal.md
...torial-incremental-copy-change-tracking-feature-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by exclusively referencing Windows tools (SQL Server Management Studio) for database access and omitting any mention of Linux-compatible alternatives (such as Azure Data Studio or command-line tools). There are no PowerShell or Windows command-line examples, but the only database client mentioned is a Windows-only tool. No Linux or cross-platform options are suggested, and no Linux-specific instructions or screenshots are provided.
Recommendations
- Mention and provide instructions for using cross-platform tools such as Azure Data Studio or the Azure CLI for database access and management.
- Include alternative steps or notes for users on Linux/macOS, especially for tasks like running SQL queries (e.g., using sqlcmd, Azure Data Studio, or the Azure Portal's Query Editor).
- Where screenshots or UI steps are shown, clarify that the steps are similar in cross-platform tools or provide equivalent screenshots for those tools.
- Explicitly state that SQL Server Management Studio is a Windows-only tool and suggest alternatives for non-Windows users.
- Review all tool and workflow references to ensure Linux users are not excluded from any step.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-deploy-ssis-virtual-network.md
...s/data-factory/tutorial-deploy-ssis-virtual-network.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation focuses exclusively on using the Azure Portal and Azure Data Factory UI, which are web-based and cross-platform, but does not provide any command-line examples or automation options. The only alternative method referenced is via Azure PowerShell, a tool primarily associated with Windows environments. There are no examples or references to Linux-native tools (such as Azure CLI or Bash scripts), nor are there instructions for performing these tasks from a Linux shell or terminal.
Recommendations
- Add equivalent instructions and examples for configuring and joining Azure-SSIS IR to a virtual network using Azure CLI, which is cross-platform and widely used on Linux.
- Include Bash script snippets or command-line workflows for Linux users to automate the process.
- When referencing automation or scripting options, mention Azure CLI before or alongside Azure PowerShell to ensure Linux parity.
- Explicitly state that the Azure Portal and ADF UI are accessible from any OS with a supported browser, and clarify that all steps can be performed from Linux, macOS, or Windows.
- Provide links to both Azure PowerShell and Azure CLI documentation for users who prefer command-line interfaces.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-incremental-copy-lastmodified-copy-data-tool.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-incremental-copy-lastmodified-copy-data-tool.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation consistently recommends Azure Storage Explorer as the tool for creating containers, uploading files, and verifying results. Azure Storage Explorer is a GUI tool that is primarily distributed for Windows (though it is available for Mac and Linux), and no mention is made of Linux-native tools or command-line alternatives such as Azure CLI, azcopy, or REST APIs. There are no examples or instructions for performing these tasks from a Linux shell or terminal, nor are Linux-specific workflows or tools mentioned.
Recommendations
- Provide alternative instructions using Azure CLI (az storage container create, az storage blob upload, etc.) for creating containers and uploading files, which work cross-platform.
- Mention and give examples for using azcopy, a cross-platform command-line tool, for file operations.
- Explicitly state that Azure Storage Explorer is available for Linux and Mac, and provide download links for those platforms.
- Include at least one example using Linux shell commands to create files (e.g., touch file1.txt) and upload them.
- Balance tool recommendations by listing both GUI and CLI options, and avoid implying that Windows GUI tools are the only or primary method.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/tutorial-push-lineage-to-purview.md
...icles/data-factory/tutorial-push-lineage-to-purview.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references and provides examples for SSIS (SQL Server Integration Services) activities, which are Windows-centric tools, without mentioning Linux alternatives or clarifying cross-platform support. The focus on SSIS and lack of Linux-specific guidance or examples suggests a Windows-first and Windows-tools bias.
Recommendations
- Clarify whether SSIS activities are supported on Linux-based integration runtimes or only on Windows, and provide equivalent Linux-compatible options or alternatives if available.
- Include explicit statements about cross-platform compatibility for all activities, especially for those (like SSIS) that are traditionally Windows-only.
- Add examples or notes for Linux users, such as using Azure Data Factory's native activities or Data Flows, and clarify any limitations or differences in lineage capture on Linux integration runtimes.
- If certain features (like SSIS) are Windows-only, recommend Linux-friendly alternatives and document their lineage support.
- Ensure that screenshots and UI references are not exclusively from Windows environments, or provide Linux/portal-neutral visuals where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-manager-for-agri/concepts-ingest-weather-data.md
.../data-manager-for-agri/concepts-ingest-weather-data.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation provides a command-line example using ARMClient, a tool that is primarily distributed as a Windows executable, and does not mention or provide equivalent instructions for Linux or cross-platform environments. There are no Linux-specific examples or alternative tools suggested, and the documentation does not clarify whether ARMClient is available or supported on Linux.
Recommendations
- Provide equivalent instructions using cross-platform tools such as Azure CLI or REST API calls via curl, which are available on both Windows and Linux.
- Explicitly mention the platform compatibility of ARMClient, and if it is Windows-only, suggest alternatives for Linux users.
- Include Linux shell (bash) examples alongside PowerShell or Windows-specific commands.
- Add a note or section addressing how to perform the same operations on Linux systems to ensure parity and inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-manager-for-agri/quickstart-install-data-manager-for-agriculture.md
...gri/quickstart-install-data-manager-for-agriculture.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for generating an access token, but the PowerShell example is more elaborate and appears after the Bash example. Throughout the rest of the documentation, all instructions are oriented around the Azure Portal GUI, which is platform-agnostic, but there are no CLI examples (such as Azure CLI or Azure Cloud Shell) that would be more familiar to Linux users. The only command-line examples are Bash and PowerShell for token generation, with no mention of Linux-specific tools or workflows elsewhere. There is a slight Windows bias in the inclusion of a detailed PowerShell example and the lack of parity in CLI-based resource creation or management steps.
Recommendations
- Provide Azure CLI examples for all resource creation and management steps, not just portal-based instructions.
- Ensure that Bash and PowerShell examples are equally detailed and placed in parallel, not with one being more elaborate.
- Explicitly mention that Bash examples are suitable for Linux/macOS users and PowerShell for Windows users.
- Include references to Azure Cloud Shell, which is cross-platform and accessible from any OS.
- Where possible, avoid Windows-first ordering (e.g., always listing PowerShell before Bash) and instead present both options side-by-side.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/event-grid/get-access-keys.md
...docs/blob/main//articles/event-grid/get-access-keys.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation presents Azure PowerShell instructions before Azure CLI, which may suggest a Windows-first approach. PowerShell is traditionally associated with Windows, while Azure CLI is cross-platform and more commonly used on Linux/macOS. No explicit Linux-specific examples or shell commands (e.g., bash) are provided, though the CLI section is present.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding bash/zsh shell examples or notes for Linux users, such as environment variable usage or command-line tips.
- If referencing PowerShell, clarify that PowerShell Core is available cross-platform, or provide a link to installation instructions for Linux/macOS.
- Ensure parity in detail and explanation between PowerShell and CLI sections.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-create-a-vm-from-azure-marketplace.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-create-a-vm-from-azure-marketplace.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. While it does mention that both Windows and Linux images can be used, the only linked prerequisite for uploading a VHD image refers to a page with a Windows-specific tab (as indicated by '?tabs=windows' in the URL). There are no explicit Linux-specific instructions, examples, or screenshots, and the documentation does not provide parity for Linux users in terms of tooling or process. The overall workflow is described in a platform-neutral way, but the lack of Linux-specific guidance or references may disadvantage Linux users.
Recommendations
- Provide explicit Linux examples and instructions, especially for steps like uploading VHD images (e.g., using AzCopy or Azure CLI on Linux).
- Ensure that linked documentation covers both Windows and Linux workflows, or link directly to Linux-specific sections where available.
- Include screenshots or command-line examples from Linux environments where applicable.
- Clarify in each step that the process applies equally to both Windows and Linux images, and note any differences if they exist.
- Review all referenced links and ensure they do not default to Windows-only tabs or instructions.
Azure Docs
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by listing Hyper-V (a Windows virtualization platform) before VMware ESXi and omitting any mention of Linux-based virtualization platforms (such as KVM or Xen). There are no Linux-specific instructions, tools, or examples provided, and the documentation does not clarify support for Linux hosts or clients beyond what may be in the included files. This may leave Linux users uncertain about compatibility and deployment steps.
Recommendations
- Explicitly state whether Linux-based virtualization platforms (e.g., KVM, Xen) are supported or not. If unsupported, clarify this for transparency.
- If Linux is supported as a client or host, provide specific instructions, examples, and requirements for Linux environments alongside Windows.
- Include Linux command-line examples (e.g., for firewall configuration, network setup) where relevant, not just Windows or PowerShell equivalents.
- List supported operating systems and platforms in a neutral order (e.g., alphabetically) rather than Windows-first.
- Reference Linux tools and patterns (e.g., iptables, firewalld) where appropriate for networking and firewall configuration.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-activation-key-vault.md
...ox-online/azure-stack-edge-gpu-activation-key-vault.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes interactions with Azure Stack Edge and Azure Key Vault via the Azure Portal UI, with no mention of command-line or scripting approaches. There are no examples or references to using PowerShell, Azure CLI, or any OS-specific tools. However, the UI navigation and terminology (e.g., BitLocker recovery key, BMC user password) are more familiar to Windows administrators, and there is no mention of Linux-based workflows, tools, or alternative approaches. This results in a 'windows_first' and 'missing_linux_example' bias, as Linux users or those preferring CLI automation are not addressed.
Recommendations
- Provide equivalent instructions for managing Azure Key Vault and Azure Stack Edge resources using Azure CLI, including Linux shell examples.
- Include PowerShell and Bash script snippets for common operations (e.g., viewing secrets, regenerating activation keys, recovering key vaults).
- Explicitly mention that the procedures are OS-agnostic where possible, or provide OS-specific notes if there are differences.
- Reference documentation or guides for Linux users who may want to automate these tasks or avoid the Azure Portal UI.
- Clarify how BitLocker recovery keys and BMC user passwords are relevant for both Windows and Linux device administrators, or provide Linux-specific security considerations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-deploy-compute-module-simple.md
...e/azure-stack-edge-gpu-deploy-compute-module-simple.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Windows tools and workflows (e.g., File Explorer) for verifying share access, while not providing equivalent Linux instructions or examples. Although there is a strong recommendation to use Linux for IoT Edge deployment, practical steps and screenshots for Linux users are missing, especially in sections involving file operations and share access.
Recommendations
- Add explicit Linux instructions and examples for accessing Edge shares (e.g., using the mount command, smbclient, or NFS mount commands) alongside or before Windows File Explorer references.
- Include screenshots or terminal output demonstrating Linux workflows for copying files to shares and verifying data movement.
- Where File Explorer is mentioned, also mention and demonstrate equivalent Linux file managers (e.g., Nautilus, Dolphin) or command-line alternatives.
- Ensure parity in tool recommendations (e.g., mention both Azure Storage Explorer and azcopy for cross-platform access to Azure Storage).
- Review all step-by-step instructions to ensure Linux users have clear, actionable guidance without needing to infer or translate from Windows-centric steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-local-resource-manager-overview.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-local-resource-manager-overview.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page does not provide any platform-specific examples, but the only 'Next steps' link points to a PowerShell-based guide, implying a Windows-first approach and omitting Linux or cross-platform alternatives. There are no explicit Linux command-line or tool references, nor any mention of Linux-compatible workflows.
Recommendations
- Provide equivalent Linux/Bash/CLI examples alongside or in place of PowerShell examples.
- Include links to documentation that covers Linux or cross-platform methods for connecting to and managing Azure Resource Manager on Azure Stack Edge devices.
- Explicitly mention that management can be performed from Linux systems, and list any required tools or dependencies.
- Ensure that all platform-specific instructions are clearly labeled and that parity exists between Windows and Linux guidance.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-overview-gpu-virtual-machines.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-overview-gpu-virtual-machines.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation lists Windows Server OS support before Linux, and provides more detailed support for Windows (multiple versions) compared to Linux (only RHEL 7.4 explicitly supported, Ubuntu deprecated). There are no Linux-specific deployment or management examples, nor are Linux command-line tools or workflows mentioned. Troubleshooting and manual installation guidance for Linux is relegated to external links, with no in-page examples.
Recommendations
- List supported Linux distributions and versions with the same level of detail as Windows, and consider including more than one supported Linux distribution.
- Provide explicit Linux deployment and management examples, such as using Azure CLI or SSH, alongside or before Windows/Powershell examples.
- Include in-page Linux troubleshooting steps and manual installation instructions, not just links to external resources.
- Mention Linux command-line tools and workflows (e.g., bash, systemctl, apt/yum) where relevant.
- Ensure parity in documentation structure and detail between Windows and Linux sections.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-recover-device-failure.md
...-online/azure-stack-edge-gpu-recover-device-failure.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by listing the Microsoft Azure Recovery Services (MARS) agent for Azure Backup, which is Windows-only, as the first and only detailed backup solution for VM file/folder recovery. There are no explicit Linux-specific instructions or examples, and the documentation does not provide parity in backup/restore guidance for Linux VMs, instead referring users to third-party solutions for Linux support.
Recommendations
- Include explicit examples and instructions for restoring Linux VM files and folders, not just Windows.
- If referencing the MARS agent for Windows, provide equivalent first-party or recommended solutions for Linux VM backup and restore, or clarify the process for Linux VMs using Azure-native tools.
- When listing backup solutions, avoid placing Windows-only solutions first or as the only detailed example; instead, present cross-platform solutions or group by OS support.
- Provide command-line examples (e.g., shell scripts) for Linux where relevant, alongside any PowerShell or Windows-specific instructions.
- Explicitly mention any differences or additional steps required for Linux environments throughout the recovery process.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-prepare-device-failure.md
...-online/azure-stack-edge-gpu-prepare-device-failure.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by listing the Microsoft Azure Recovery Services (MARS) agent for Azure Backup, which only supports Windows, as the first and only Microsoft-native backup solution. There are no equivalent Microsoft-native Linux backup solutions mentioned, and no Linux-specific backup guidance or examples are provided. Third-party solutions supporting both Windows and Linux are listed, but Linux users are not given the same level of first-party support or documentation detail.
Recommendations
- Include Microsoft-native Linux backup solutions if available, or explicitly state their absence and recommend third-party alternatives.
- Provide Linux-specific backup instructions or examples, especially for common scenarios such as backing up Linux VMs.
- Ensure that any first-party tools or agents (like MARS) are accompanied by Linux equivalents or alternatives, or clarify their platform limitations.
- Present third-party solutions in a way that does not prioritize Windows over Linux, and ensure parity in documentation detail for both platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/databox-online/azure-stack-edge-gpu-troubleshoot-activation.md
...online/azure-stack-edge-gpu-troubleshoot-activation.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by referencing PowerShell-specific recovery commands (e.g., 'Undo Key vault key removal' via the Az.KeyVault PowerShell module) and omitting equivalent CLI or Linux-native instructions. There are no examples or guidance for Linux users, and all command-line references are implicitly Windows-centric.
Recommendations
- Provide equivalent Azure CLI commands for all PowerShell examples, especially for key recovery and management tasks.
- Explicitly mention that recovery steps can be performed on Linux/macOS using Azure CLI, and provide those instructions.
- Where PowerShell modules are referenced, add parallel instructions for Bash/Azure CLI environments.
- Review all troubleshooting steps to ensure parity for users on non-Windows platforms, and include screenshots or terminal output from Linux where appropriate.