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 1076-1100 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-google-bigquery-legacy.md
...icles/data-factory/connector-google-bigquery-legacy.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation displays a Windows bias by referencing Windows support and tools (such as the integration runtime) without mentioning Linux equivalents or support. There are no Linux-specific instructions, examples, or clarifications, and the only operating system mentioned for the self-hosted integration runtime is Windows. This may lead Linux users to believe that Linux is unsupported or less prioritized.
Recommendations
- Explicitly state whether the self-hosted integration runtime supports Linux, and if so, provide setup instructions or a link to relevant documentation.
- Include Linux-specific examples or clarify any differences in configuration paths (e.g., keyFilePath, trustedCertPath) for Linux environments.
- If Linux is unsupported, clearly mention this limitation early in the documentation.
- Reference both Windows and Linux in prerequisites and supported platforms, not just Windows.
- Provide troubleshooting tips or notes for common Linux deployment scenarios, if applicable.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-dynamics-crm-office-365.md
...cles/data-factory/connector-dynamics-crm-office-365.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (such as Dynamics XRM tooling for Windows client applications), omitting any mention of Linux or cross-platform alternatives, and not providing Linux-specific instructions or examples. All authentication and configuration examples are platform-agnostic JSON, but the underlying tooling and references are Windows-centric, and there is no guidance for Linux users.
Recommendations
- Explicitly state whether the Dynamics XRM tooling and connector features are supported on Linux and provide links to any cross-platform SDKs or tools if available.
- If the connector or SDK is Windows-only, clearly mention this limitation and suggest any available alternatives for Linux users.
- Include Linux-specific instructions or examples where relevant, such as how to authenticate or configure connections from a Linux environment.
- Review all references to Windows tools and ensure that Linux equivalents (if any) are mentioned with equal prominence.
- Add a section addressing cross-platform compatibility, including any prerequisites or troubleshooting steps for Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-hdfs.md
...ocs/blob/main//articles/data-factory/connector-hdfs.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a clear Windows bias. Windows authentication is emphasized as a primary method, with detailed instructions and examples for configuring Kerberos and integration runtime on Windows. Windows-specific tools (such as Ksetup and netdom) and UI navigation are described in detail, while Linux equivalents (such as kinit, realm join, or krb5.conf editing on Linux) are either omitted or only briefly mentioned. There are no step-by-step Linux-based integration runtime setup or authentication examples, and all command-line configuration examples for the integration runtime use Windows CMD or PowerShell syntax.
Recommendations
- Provide equivalent Linux-based instructions for setting up the self-hosted integration runtime in a Kerberos realm, including commands for joining a Linux machine to a Kerberos realm and configuring krb5.conf.
- Include Linux command-line examples (e.g., kinit, klist, editing /etc/krb5.conf) alongside Windows (Ksetup/netdom) commands.
- Clarify that the integration runtime can run on Linux, if supported, and provide explicit Linux setup steps.
- Add UI screenshots or instructions for Linux environments where applicable.
- Ensure authentication examples include both Windows and Linux user scenarios, and explain any differences in required configuration files or environment variables.
- Where Windows tools are mentioned (Ksetup, netdom), mention and demonstrate the Linux equivalents or alternatives.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-sybase.md
...s/blob/main//articles/data-factory/connector-sybase.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing 'Windows authentication' as a primary authentication method, mentioning Windows-specific data providers, and omitting any explicit Linux installation or configuration guidance. There are no Linux-specific examples or instructions for setting up the Sybase connector or the required drivers on Linux-based integration runtime hosts.
Recommendations
- Add explicit instructions and examples for installing the Sybase data provider on Linux-based integration runtime hosts.
- Document Linux-compatible authentication options (e.g., Kerberos, if supported) and clarify whether 'Basic' authentication works cross-platform.
- Include Linux command-line examples (e.g., bash) for relevant setup steps, alongside any Windows/Powershell examples.
- Clarify whether the Self-hosted Integration Runtime and Sybase connector are fully supported on Linux, and provide troubleshooting tips for Linux environments.
- Avoid listing 'Windows authentication' before 'Basic' unless it is truly the most cross-platform option; otherwise, clarify platform limitations.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-troubleshoot-azure-blob-storage.md
...a-factory/connector-troubleshoot-azure-blob-storage.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (e.g., diawp.exe.config and FIPS policy on Windows VMs) and providing troubleshooting steps only for Windows environments. There are no equivalent instructions or considerations for Linux-based self-hosted integration runtimes or cross-platform scenarios.
Recommendations
- Include troubleshooting steps for Linux-based self-hosted integration runtimes, such as how to handle FIPS mode or equivalent security settings on Linux.
- When referencing configuration files or tools (e.g., diawp.exe.config), clarify if they are Windows-only and provide Linux alternatives or explicitly state if not applicable.
- Add examples or notes for Linux users where relevant, ensuring parity in troubleshooting guidance.
- Avoid assuming the runtime environment is Windows; use neutral language or provide parallel instructions for both Windows and Linux where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-postgresql-legacy.md
...//articles/data-factory/connector-postgresql-legacy.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias, particularly in the section discussing SSL verification with ODBC connections. It exclusively references Windows file paths (e.g., C:\Windows\ServiceProfiles\DIAHostService\AppData\Roaming\postgresql\root.crt) and setup steps for the Self-hosted Integration Runtime (SHIR), with no mention of Linux equivalents or guidance for Linux-based SHIR hosts. There are no Linux-specific examples or instructions, and the documentation implicitly assumes a Windows environment for configuration.
Recommendations
- Add parallel instructions and file paths for configuring SSL certificates on Linux-based SHIR hosts (e.g., ~/.postgresql/root.crt or /etc/ssl/certs/).
- Explicitly state whether the SHIR is supported on Linux and, if so, provide Linux setup steps alongside Windows instructions.
- Include example commands or screenshots for Linux environments where relevant, ensuring parity in guidance.
- Review all references to Windows-specific tools, paths, or patterns and provide Linux alternatives wherever possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-office-365.md
...ob/main//articles/data-factory/connector-office-365.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. While the core content is platform-agnostic (focused on Azure Data Factory and Microsoft 365 integration), the only explicit command-line tooling example referenced is Azure PowerShell, with no mention of Linux-native alternatives (such as Azure CLI or Bash scripting). Additionally, when discussing certificate conversion, the documentation links to a PowerShell-based method and a downloadable template, but does not provide Linux-friendly (e.g., OpenSSL) instructions. The order of tools in the 'Getting started' section also lists PowerShell before REST API or ARM templates, which can subtly reinforce a Windows-first mindset.
Recommendations
- Add explicit examples and references for Linux users, such as using Azure CLI and Bash scripts for pipeline creation and management.
- When describing certificate conversion, include OpenSSL-based instructions for converting certificates to base64 on Linux/macOS, alongside the PowerShell example.
- In the 'Getting started' section, either rotate or randomize the order of tools, or explicitly mention cross-platform options (e.g., 'Azure CLI (cross-platform)'), to avoid reinforcing a Windows-first approach.
- Wherever PowerShell is referenced, provide equivalent Azure CLI commands or links to relevant documentation.
- Explicitly state that all features and steps are supported on Linux and macOS, not just Windows, to reassure non-Windows users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-troubleshoot-sap.md
...n//articles/data-factory/connector-troubleshoot-sap.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides troubleshooting steps that exclusively use Windows-specific tools and commands, specifically PowerShell's Test-NetConnection, without offering equivalent instructions for Linux environments. This creates a bias toward Windows users and may hinder Linux users from effectively troubleshooting the same issues.
Recommendations
- Include equivalent Linux command-line examples, such as using 'nc' (netcat) or 'telnet' to test connectivity to the SAP server port.
- Mention both Windows and Linux troubleshooting tools side by side, or provide a table with commands for each platform.
- Avoid assuming the integration runtime is always installed on a Windows machine; clarify that instructions may differ by OS.
- Add a note or section specifically addressing Linux/macOS users to ensure parity and inclusivity.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-troubleshoot-file-system.md
...les/data-factory/connector-troubleshoot-file-system.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell for configuration steps and not providing equivalent instructions or examples for Linux environments. There is no mention of Linux command-line tools or guidance for non-Windows users.
Recommendations
- Provide equivalent Linux command-line instructions (e.g., using Bash or shell scripts) for configuring the self-hosted integration runtime.
- Mention and document any differences in setup or troubleshooting for Linux-based self-hosted integration runtimes.
- Ensure that all PowerShell-based recommendations are accompanied by Linux alternatives where applicable.
- Explicitly state platform requirements or limitations if certain features are Windows-only.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-sftp.md
...ocs/blob/main//articles/data-factory/connector-sftp.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates some Windows bias, particularly in the SSH public key authentication section, where the only example of a private key path uses a Windows-style path (D:\privatekey_openssh), and the guidance for converting PPK files references only the PuTTY tool, which is primarily a Windows utility. There are no Linux or macOS path examples, nor are Linux-native tools (like ssh-keygen or puttygen on Linux) mentioned. No Linux file path examples are provided, and the documentation does not clarify cross-platform considerations for file paths or key formats.
Recommendations
- Provide examples using Linux/macOS-style file paths (e.g., /home/user/.ssh/id_rsa) alongside Windows paths in the SSH public key authentication section.
- Mention Linux-native tools for key conversion (e.g., ssh-keygen, puttygen on Linux) in addition to PuTTY, and provide relevant instructions or links.
- Explicitly state that both Windows and Linux file path formats are supported, and clarify any platform-specific considerations.
- Ensure that all code and configuration examples are platform-neutral or provide parallel examples for both Windows and Linux environments.
- Add a note or section addressing cross-platform compatibility, especially for self-hosted integration runtime scenarios.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-troubleshoot-hive.md
...//articles/data-factory/connector-troubleshoot-hive.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates Windows bias by referencing only Windows file paths (e.g., C:\Program Files\MIT\Kerberos\bin), using Windows environment variable terminology ('system variable'), and omitting Linux equivalents or examples. There are no instructions or file paths for Linux systems, nor is there mention of Linux-specific Kerberos configuration (such as /etc/krb5.conf).
Recommendations
- Provide Linux equivalents for all file paths and configuration steps (e.g., mention /etc/krb5.conf for krb5 configuration on Linux).
- Include example commands and instructions for both Windows and Linux environments, such as how to set environment variables on Linux (e.g., export KRB5_CONFIG=/etc/krb5.conf).
- Avoid using only Windows terminology (like 'system variable'); instead, clarify how to perform the same actions on Linux.
- Explicitly state that the instructions apply to both Windows and Linux, or provide separate sections for each platform.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-sap-hana.md
...blob/main//articles/data-factory/connector-sap-hana.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing 'SAP HANA CLIENT for Windows' as the ODBC driver to install, without mentioning Linux or cross-platform alternatives. No Linux installation instructions, examples, or references are provided for setting up the ODBC driver or Integration Runtime. The authentication examples and terminology (e.g., 'Windows authentication') are also Windows-centric, with no mention of Linux authentication patterns or Kerberos. All setup and configuration steps implicitly assume a Windows environment.
Recommendations
- Explicitly mention and provide instructions for installing the SAP HANA ODBC driver on Linux, including relevant download links and package names.
- Clarify that the Self-hosted Integration Runtime can run on both Windows and Linux, and provide platform-specific setup guidance.
- Include Linux-specific examples for connection strings, authentication, and environment setup.
- When referencing authentication, explain options available on Linux (e.g., Kerberos, basic authentication) and clarify any differences.
- Avoid using 'Windows authentication' as the default or only example; instead, present both Windows and Linux authentication scenarios side by side.
- Add troubleshooting tips or notes for common Linux-specific issues (e.g., library dependencies, environment variables).
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/control-flow-wait-activity.md
...n//articles/data-factory/control-flow-wait-activity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides sample PowerShell commands and references a PowerShell-based tutorial for running pipelines, with no mention of Linux, Bash, or cross-platform CLI equivalents. This indicates a Windows-first approach and lacks Linux parity in examples and guidance.
Recommendations
- Include equivalent Azure CLI (az) or Bash script examples alongside PowerShell commands to support Linux and cross-platform users.
- Reference tutorials or quickstarts that use Azure CLI or REST API, not just PowerShell.
- Explicitly mention that the Wait activity and pipeline execution can be managed from any OS, and provide links or examples for non-Windows environments.
- Ensure that all code samples and walkthroughs are available in both PowerShell and Bash/Azure CLI formats.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-square.md
...s/blob/main//articles/data-factory/connector-square.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly stating that the connector supports Windows versions (with a link to Windows prerequisites), without mentioning Linux or cross-platform support for the self-hosted integration runtime. There are no Linux-specific instructions, examples, or parity notes, and no mention of Linux compatibility or requirements for self-hosted integration runtime. All tooling and environment assumptions are Windows-centric.
Recommendations
- Explicitly state whether the self-hosted integration runtime supports Linux, and if so, provide a link to Linux prerequisites and installation instructions.
- Add Linux-specific examples or notes, especially for environments where the integration runtime can be run on Linux (e.g., via Docker).
- If Linux is not supported, clearly state this limitation early in the documentation.
- Ensure parity in documentation structure and examples for both Windows and Linux environments where applicable.
- Reference cross-platform tools and patterns (e.g., Docker, CLI) where possible, not just Windows-native approaches.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-troubleshoot-ftp-sftp-http.md
...s/data-factory/connector-troubleshoot-ftp-sftp-http.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows a mild Windows bias. It references Windows-specific tools (WinSCP) as the only example for verifying SFTP credentials, and recommends a third-party web tool for base64 encoding before mentioning command-line options. While some Linux commands (openssl, ssh-keygen) are included, there are no explicit Linux or cross-platform examples for verifying SFTP connections (e.g., using sftp or scp), and the order of tool recommendations sometimes puts Windows or web tools first. There are also no PowerShell-specific examples, but Linux-native troubleshooting tools are underrepresented.
Recommendations
- When suggesting tools to verify SFTP credentials, include Linux-native options such as the 'sftp' or 'ssh' command-line tools, not just WinSCP.
- When recommending base64 encoding, provide both Linux (e.g., 'base64' command) and Windows (e.g., certutil or PowerShell) command-line examples, and mention them before or alongside web tools.
- For troubleshooting steps that involve checking connectivity or permissions, include cross-platform command-line examples (e.g., 'telnet', 'nc', 'curl', 'sftp') for both Windows and Linux.
- Ensure that Linux tools and patterns are mentioned at least as prominently as Windows tools, and avoid listing Windows tools first by default.
- Where possible, clarify that the instructions and recommendations apply to both Windows and Linux environments, or provide parallel instructions for each.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-upgrade-guidance.md
...n//articles/data-factory/connector-upgrade-guidance.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell script for programmatically finding impacted objects, with no mention of Linux-compatible alternatives (such as Bash, Azure CLI, or Python). This suggests a bias toward Windows tooling and omits guidance for users on Linux or macOS platforms.
Recommendations
- Provide equivalent examples using Azure CLI, Bash, or Python scripts that can be run on Linux and macOS.
- Explicitly mention that the PowerShell script can be run cross-platform using PowerShell Core, if applicable.
- Add a note or section addressing how Linux/macOS users can accomplish the same tasks, ensuring parity in guidance.
- Where possible, present cross-platform solutions first, or at least alongside Windows-specific ones.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-troubleshoot-guide.md
.../articles/data-factory/connector-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias, particularly in the FIPS troubleshooting section, where only Windows file paths and configuration steps are provided (e.g., editing diawp.exe.config in C:\Program Files). There are no equivalent instructions or examples for Linux-based self-hosted integration runtime environments. Additionally, the documentation assumes the use of Windows tools and patterns (such as .exe files and Windows directory structures) without mentioning or providing alternatives for Linux users.
Recommendations
- Add explicit troubleshooting steps and file paths for Linux-based self-hosted integration runtime environments, if supported.
- When referencing configuration files or directories (e.g., diawp.exe.config), include both Windows and Linux paths and instructions.
- Clarify whether certain features or troubleshooting steps are Windows-only, and provide Linux alternatives or state if not supported.
- Include examples or notes for Linux command-line tools and configuration patterns where applicable.
- Review all sections for implicit Windows assumptions and ensure parity in documentation for Linux users.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-teradata.md
...blob/main//articles/data-factory/connector-teradata.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and requirements (such as Visual C++ Redistributable and Windows authentication), mentioning Windows authentication before others, and omitting any Linux-specific instructions or examples. There are no examples or guidance for Linux-based self-hosted integration runtimes, and the documentation does not address Linux-specific prerequisites or troubleshooting.
Recommendations
- Add explicit instructions and prerequisites for deploying the self-hosted integration runtime on Linux, including supported distributions and dependencies.
- Provide Linux-specific examples for authentication (e.g., Kerberos, LDAP) and clarify any differences from Windows authentication.
- Include troubleshooting steps and common issues for Linux environments, such as permissions, required libraries, or service management.
- Mention Linux equivalents for any Windows-only tools or downloads, or clarify if certain features are Windows-only.
- Ensure parity in example payloads and configuration steps for both Windows and Linux environments.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-troubleshoot-rest.md
...//articles/data-factory/connector-troubleshoot-rest.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing 'Command Prompt' as the environment for running curl, omitting mention of Linux/macOS shells. It also recommends Fiddler, a Windows-centric tool, without suggesting Linux alternatives. No Linux-specific instructions or parity examples are provided.
Recommendations
- When suggesting 'curl', mention that it can be used in Command Prompt (Windows), PowerShell, or terminal (Linux/macOS).
- Provide example 'curl' commands for both Windows (Command Prompt/PowerShell) and Linux/macOS shells, noting syntax differences if any.
- When recommending Fiddler, also suggest cross-platform or Linux alternatives such as mitmproxy or Wireshark.
- Avoid referencing only Windows environments (e.g., 'Command Prompt') as the default; instead, use neutral language like 'terminal window' or list both Windows and Linux/macOS options.
- Add troubleshooting steps or notes relevant to Linux/macOS users where applicable.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-vertica.md
.../blob/main//articles/data-factory/connector-vertica.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias, particularly in the 'Install Vertica ODBC driver for the version 2.0' section, where only Windows installation steps and screenshots are provided. There are no instructions or examples for installing the Vertica ODBC driver on Linux or macOS, despite the self-hosted integration runtime being commonly deployed on Linux servers. The documentation also references Windows-specific tools (e.g., ODBC Data Source Administrator) and uses Windows-centric language and screenshots throughout the installation process.
Recommendations
- Add parallel instructions and screenshots for installing the Vertica ODBC driver on Linux (and optionally macOS), including command-line installation steps (e.g., using rpm, deb, or tar.gz packages).
- Mention and demonstrate how to verify ODBC driver installation on Linux (e.g., using isql or odbcinst commands) alongside the Windows ODBC Data Source Administrator.
- Clearly state that the self-hosted integration runtime can run on both Windows and Linux, and provide OS-appropriate guidance for each.
- Wherever examples or screenshots are given, provide both Windows and Linux versions, or at least link to official Vertica/Linux installation documentation.
- Avoid language that assumes a Windows environment by default; instead, present instructions for both platforms or clarify when steps are OS-specific.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-troubleshoot-synapse-sql.md
...les/data-factory/connector-troubleshoot-synapse-sql.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (such as SQL Server Management Studio and the Windows Firewall), linking to Windows-centric configuration guides, and omitting Linux or cross-platform alternatives. There are no examples or troubleshooting steps that mention Linux environments, tools, or commands, despite the cross-platform nature of Azure Data Factory and SQL Server connectors.
Recommendations
- When referencing tools like SQL Server Management Studio (SSMS), also mention cross-platform alternatives such as Azure Data Studio, sqlcmd, or other CLI tools available on Linux and macOS.
- For firewall configuration, provide guidance for both Windows Firewall and common Linux firewalls (e.g., iptables, firewalld, ufw), or reference generic network configuration steps.
- Include troubleshooting steps and examples that are applicable to Linux environments, such as command-line utilities or log file locations.
- Where possible, avoid linking exclusively to Windows-specific documentation. Instead, use cross-platform or platform-neutral resources.
- Explicitly state that the troubleshooting steps apply to both Windows and Linux integration runtimes, and call out any platform-specific differences.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/connector-troubleshoot-sharepoint-online-list.md
...ctory/connector-troubleshoot-sharepoint-online-list.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides troubleshooting steps that exclusively use the SharePoint Online Management Shell (a Windows-only tool) and PowerShell commands, with no mention of Linux or cross-platform alternatives. All example commands and tool recommendations are Windows-centric, and there are no instructions for performing the same tasks on Linux or macOS.
Recommendations
- Provide equivalent instructions for Linux and macOS users, such as using cross-platform PowerShell Core (pwsh) or Azure CLI where possible.
- Mention whether the required commands can be run using PowerShell Core on non-Windows platforms, and provide installation guidance if so.
- If SharePoint Online Management Shell is required and only available on Windows, explicitly state this limitation and suggest alternatives or workarounds for non-Windows users.
- Consider including REST API or Microsoft Graph API examples for enabling ACS, which can be executed from any platform.
- Structure troubleshooting steps to present cross-platform or platform-neutral solutions first, or in parallel with Windows-specific instructions.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/continuous-integration-delivery-sample-script.md
...ctory/continuous-integration-delivery-sample-script.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell scripts and Azure PowerShell tasks for all examples, with no mention of Bash, Azure CLI, or Linux-native scripting alternatives. All code samples, instructions, and YAML pipeline tasks are PowerShell-centric, and there is no guidance for users working in Linux or cross-platform environments.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for Linux users.
- Explicitly mention that PowerShell Core is cross-platform, but clarify any Windows-specific limitations or requirements.
- Include YAML pipeline tasks using AzureCLI@2 and Bash@3 for parity with AzurePowerShell@5 examples.
- Add a section discussing cross-platform considerations and how to adapt the scripts for Linux/macOS agents.
- Reference official documentation for installing and using Azure CLI in addition to Azure PowerShell.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/continuous-integration-delivery-automate-azure-pipelines.md
...ntinuous-integration-delivery-automate-azure-pipelines.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong Windows bias by relying heavily on PowerShell for automation tasks, specifically for managing Data Factory triggers. There are no examples or instructions for performing these tasks using cross-platform tools (such as Azure CLI, Bash, or REST API), and PowerShell is presented as the default and only scripting environment. The documentation also references .ps1 scripts and Azure PowerShell modules without mentioning Linux or macOS compatibility or alternatives. This may hinder users working on non-Windows platforms or those preferring non-PowerShell automation.
Recommendations
- Provide equivalent examples using Azure CLI and/or REST API for managing Data Factory triggers (e.g., stopping and starting triggers), alongside PowerShell.
- Explicitly mention that PowerShell Core is cross-platform, but also offer Bash or CLI scripts for users on Linux/macOS.
- Where .ps1 scripts are referenced, include or link to equivalent shell scripts or CLI commands.
- In sections discussing automation tasks, avoid assuming PowerShell as the only or primary automation tool; present alternatives in parallel or note their availability.
- Add a note or section clarifying platform compatibility for all automation steps, and ensure that Linux/macOS users are not excluded from following the guide.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/copy-data-tool-metadata-driven.md
...rticles/data-factory/copy-data-tool-metadata-driven.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing SQL Server Management Studio (SSMS) for running SQL scripts, without mentioning cross-platform or Linux alternatives. There are no examples or instructions for performing equivalent tasks on Linux systems (e.g., using Azure Data Studio, sqlcmd, or other CLI tools). The documentation assumes the use of Windows-based tools and does not provide Linux-first or cross-platform guidance.
Recommendations
- Include instructions for running the generated SQL scripts using cross-platform tools such as Azure Data Studio or sqlcmd, which are available on Linux, macOS, and Windows.
- Mention and provide examples for using command-line tools (e.g., sqlcmd) to connect to the control table server and execute scripts, in addition to SSMS.
- Explicitly state that SSMS is a Windows-only tool and suggest alternatives for users on Linux or macOS.
- Add screenshots or step-by-step instructions for Linux users where relevant, ensuring parity in the documentation.
- Review all tool references and ensure that Linux-compatible options are presented alongside or before Windows-only tools.