Data Factory
564
Total Pages
364
Linux-Friendly Pages
200
Pages with Bias
35.5%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
1000 issues found
Showing 926-950 of 1000 flagged pages
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-azure-data-lake.md
...data-factory/connector-troubleshoot-azure-data-lake.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation references 'network monitor (netmon) trace' for troubleshooting SSL/TLS issues, which is a Windows-specific tool, and does not provide equivalent instructions or tool suggestions for Linux environments. No command-line examples (e.g., PowerShell, Bash) are given, but the only explicit tool mentioned is Windows-centric. There are no Linux-specific troubleshooting steps or parity in tooling guidance.
Recommendations
- When suggesting network monitoring, mention cross-platform tools such as Wireshark or tcpdump, and provide brief instructions or links for both Windows and Linux users.
- If referencing a Windows tool (like netmon), also list equivalent Linux tools and how to use them for the same troubleshooting task.
- Wherever possible, provide troubleshooting steps or examples that are platform-agnostic, or explicitly include both Windows and Linux variants.
- Audit the documentation for other implicit assumptions of a Windows environment and ensure Linux users are equally supported.
Create Pull Request
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sap-business-warehouse.md
...icles/data-factory/connector-sap-business-warehouse.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific paths (e.g., %windir%\system32) for library placement and troubleshooting, and does not provide equivalent instructions or examples for Linux environments. There are no Linux-specific installation paths, troubleshooting tips, or examples, which may hinder users deploying Self-hosted Integration Runtime on Linux.
Recommendations
- Include Linux-specific instructions for installing the SAP NetWeaver library and its dependencies, such as typical library paths (e.g., /usr/lib or /opt/sap), and how to set environment variables (e.g., LD_LIBRARY_PATH).
- Provide troubleshooting tips for Linux environments, such as checking shared library dependencies with ldd, and ensuring correct permissions.
- Mention any differences or additional requirements when running Self-hosted Integration Runtime on Linux, if supported.
- Where Windows environment variables or paths are referenced, add Linux equivalents in parallel.
- Explicitly state if Linux is not supported for Self-hosted Integration Runtime, or provide a link to platform compatibility documentation.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/copy-activity-performance-features.md
...les/data-factory/copy-activity-performance-features.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is generally cross-platform and does not provide command-line examples specific to Windows or Linux. However, there is a subtle Windows bias in the 'Staged copy' section, where firewall configuration is discussed only in the context of the Windows firewall, and port requirements are described with reference to Windows and corporate firewalls. No mention is made of Linux firewall equivalents (e.g., iptables, firewalld, ufw), nor are Linux-specific considerations or examples provided. This may lead Linux users to feel their scenarios are not fully addressed.
Recommendations
- When discussing firewall configuration, mention both Windows (Windows Firewall) and Linux (e.g., iptables, firewalld, ufw) firewalls to ensure Linux users are included.
- Where platform-specific configuration is referenced, provide parallel guidance or links for both Windows and Linux environments.
- Explicitly state that the guidance applies to both Windows and Linux self-hosted integration runtime nodes, and note any differences if they exist.
- Consider adding a short section or note acknowledging cross-platform support and linking to platform-specific setup/configuration guides where appropriate.
Data Factory
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 page provides only Windows-centric examples for Hadoop Streaming activities, specifically referencing '.exe' files (e.g., MyMapper.exe, MyReducer.exe) as mapper and reducer executables. There are no examples or mentions of Linux/Unix-style scripts (e.g., Python, Bash, or shell scripts), which are more common in Hadoop environments. This may mislead users into thinking only Windows executables are supported or recommended.
Recommendations
- Add Linux/Unix-based examples for mapper and reducer scripts, such as Python (.py), Bash (.sh), or other common script types used in Hadoop Streaming.
- Clarify in the documentation that both Windows executables and Linux/Unix scripts are supported, if applicable.
- Provide at least one example using a non-Windows executable (e.g., 'MyMapper.py', 'MyReducer.sh') in the JSON sample and file paths.
- Explicitly mention any platform requirements or limitations for the mapper/reducer programs.
- Consider reordering or balancing examples to reflect the prevalence of Linux in Hadoop environments.
Data Factory
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 configuring Azure-SSIS IR via the Azure portal and ADF UI, which are web-based and cross-platform, but does not provide any command-line examples or automation options for Linux users. The only alternative automation method referenced is via Azure PowerShell, a tool primarily associated with Windows environments. There are no mentions of Azure CLI or Bash-based workflows, and no Linux-specific guidance or parity is provided.
Recommendations
- Add equivalent instructions for configuring Azure-SSIS IR and joining a virtual network using Azure CLI, which is cross-platform and widely used on Linux.
- Include Bash shell command examples for automation, where applicable.
- Reference both Azure PowerShell and Azure CLI options in the 'Related content' section, ensuring Linux users are aware of non-Windows tooling.
- Explicitly state that the Azure portal and ADF UI are accessible from any OS with a supported browser, to reassure Linux and macOS users.
- If certain features are only available via PowerShell, clarify this and provide a roadmap or alternatives for Linux users.
Data Factory
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/SQL Server stored procedures for control tables and workflow orchestration, which are Windows-centric technologies. There are no examples or mentions of Linux-native alternatives (such as PostgreSQL, MySQL, or open-source orchestration tools), nor any guidance for users who may wish to use non-Windows database engines or scripting environments. No PowerShell or Windows command-line examples are present, but the overall workflow assumes a Windows/Azure SQL Server environment.
Recommendations
- Provide equivalent examples using open-source databases such as PostgreSQL or MySQL, including DDL and stored procedure syntax.
- Mention that the control table could be implemented in other database engines, and provide guidance or links for Linux users.
- Clarify whether Azure Data Factory supports non-SQL Server control tables and, if so, how to configure them.
- If possible, include a section or appendix with Linux-friendly alternatives for the control table and orchestration logic.
- Explicitly state the platform requirements and suggest cross-platform options where available.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/sap-change-data-capture-debug-shir-logs.md
...ata-factory/sap-change-data-capture-debug-shir-logs.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references the Microsoft Integration Runtime Configuration Manager, which is a Windows-only tool. There are no instructions or examples for users running the self-hosted integration runtime on Linux, nor is there any mention of Linux command-line alternatives or parity.
Recommendations
- Add instructions for collecting and sending logs when the self-hosted integration runtime is running on Linux.
- Specify whether the Integration Runtime Configuration Manager is available on platforms other than Windows, and provide alternatives if not.
- Include command-line or script-based methods (e.g., using shell commands) for Linux users to gather and send logs.
- Clearly indicate platform-specific steps and provide equivalent guidance for both Windows and Linux environments.
Data Factory
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 page demonstrates a Windows bias by providing only SQL Server/Azure SQL Database examples for the control table, with no equivalent examples or instructions for Linux-based database systems (e.g., PostgreSQL, MySQL) or command-line environments. The workflow and examples are centered on Microsoft technologies, and there is no mention of Linux tools, shell commands, or cross-platform database creation steps.
Recommendations
- Add equivalent examples for creating the control table in popular Linux-supported databases such as PostgreSQL and MySQL.
- Include instructions or code snippets using Linux command-line tools (e.g., psql, mysql) for creating and populating the control table.
- Clarify that the template is database-agnostic and provide guidance for users working on non-Windows platforms.
- If screenshots are shown for connection creation, ensure at least one example uses a non-SQL Server source (e.g., Oracle, PostgreSQL) to demonstrate cross-platform applicability.
- Explicitly mention that the steps are applicable regardless of the operating system, and provide any OS-specific notes if necessary.
Data Factory
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 demonstrates the use of SSIS (SQL Server Integration Services) activities, which are Windows-centric tools, and highlights them alongside cross-platform activities (Copy, Data Flow). There are no explicit Linux or cross-platform command-line examples, and the only specific tool mentioned beyond the Data Factory UI is SSIS, which is traditionally Windows-based. No Linux-specific tools, patterns, or examples are provided.
Recommendations
- Include explicit mention of cross-platform compatibility for all activities, clarifying which features are available on Linux-based integration runtimes.
- Add examples or notes for users running Data Factory pipelines on Linux-based integration runtimes, especially for Data Flow and Copy activities.
- If SSIS is Windows-only, clearly state this and suggest Linux alternatives or workarounds where possible.
- Provide parity in documentation by referencing Linux tools or environments where relevant, or by stating when a feature is not available on Linux.
- Consider adding a table or section summarizing feature support and instructions for both Windows and Linux environments.
Data Factory
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 page demonstrates a bias toward Windows by exclusively recommending Azure Storage Explorer (a GUI tool most commonly used on Windows) for file operations, without mentioning or providing examples for Linux-native tools or command-line alternatives. There are no Linux-specific instructions or CLI examples for creating/uploading files or managing Blob storage containers.
Recommendations
- Include examples using cross-platform command-line tools such as Azure CLI (az storage commands) and/or Azure PowerShell for all file and container operations.
- Explicitly mention that Azure Storage Explorer is available on Windows, macOS, and Linux, and provide download links for each platform.
- Provide Linux-native alternatives for file creation and upload, such as using the 'touch' and 'echo' commands to create files, and 'az storage blob upload' for uploading files.
- Add a section or callout for Linux/macOS users, outlining equivalent steps using terminal commands.
- Ensure screenshots and instructions do not assume a Windows environment; include examples or notes for other operating systems where relevant.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-improvements.md
...actory/continuous-integration-delivery-improvements.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation provides only Windows-style (DOS path) examples for npm commands (e.g., using C:\ paths), with no Linux or cross-platform path examples. This may confuse or exclude Linux/macOS users. While the YAML pipeline uses Ubuntu as the build agent, all explicit command-line examples and paths are Windows-centric, and Linux alternatives are not mentioned or shown.
Recommendations
- Provide Linux/macOS equivalent examples for all command-line instructions, especially for npm commands (e.g., use /home/user/DataFactories/DevDataFactory as a path example).
- When showing file paths, use both Windows (C:\...) and Linux (/home/...) formats, or use environment variables and relative paths where possible.
- Explicitly state that the npm package and commands are cross-platform, and clarify any OS-specific considerations.
- In the 'Export ARM template' and 'Validate' sections, add Linux/macOS command-line examples alongside the Windows ones.
- Consider using forward slashes in paths or note that both path styles are supported, depending on the OS.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/change-data-capture-troubleshoot.md
...icles/data-factory/change-data-capture-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively provides troubleshooting steps and examples for SQL Server (a Microsoft/Windows-centric database) using T-SQL queries and stored procedures. There are no examples or guidance for Linux-based or open-source databases, nor any mention of Linux command-line tools or environments. The focus on SQL Server and absence of cross-platform parity constitutes a Windows bias.
Recommendations
- Include troubleshooting steps and examples for popular Linux/open-source databases that support CDC, such as PostgreSQL or MySQL, where applicable.
- Provide equivalent command-line examples for Linux environments (e.g., using psql or mysql CLI tools) if CDC is supported.
- Mention any platform-specific limitations or differences explicitly, and offer guidance for users running Azure Data Factory with non-Windows sources.
- If SQL Server is the only supported source, clarify this early in the documentation and provide links or notes for Linux users seeking CDC solutions.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-incremental-copy-portal.md
...icles/data-factory/tutorial-incremental-copy-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by referencing Windows-specific tools (SQL Server Management Studio) for database operations and omitting Linux-friendly alternatives. There are no explicit PowerShell or command-line examples, but the only tool mentioned for SQL interaction is SSMS, which is primarily a Windows application. No Linux or cross-platform alternatives (such as Azure Data Studio, sqlcmd, or CLI tools) are suggested, and no Linux-specific instructions are provided.
Recommendations
- Mention and provide examples using cross-platform tools such as Azure Data Studio or sqlcmd for database operations, alongside SQL Server Management Studio.
- Explicitly state that users can perform SQL commands from any OS using Azure Data Studio, sqlcmd, or the Azure Portal's Query Editor.
- Where GUI instructions are given (e.g., 'right-click the database'), provide equivalent command-line or cross-platform steps.
- Add a note clarifying that all steps can be performed from Linux, macOS, or Windows, and link to relevant cross-platform tool documentation.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-roles-permissions.md
...in/articles/data-factory/concepts-roles-permissions.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Summary
The documentation references PowerShell and the SDK as methods for managing Data Factory resources, but does not mention or provide examples for equivalent Linux-native tools (such as Azure CLI or Bash scripting). There are no Linux-specific instructions or examples, and PowerShell is implicitly prioritized as the non-portal automation method.
Recommendations
- Explicitly mention Azure CLI as an alternative to PowerShell for managing Data Factory resources, and provide equivalent CLI command examples.
- Include Bash scripting examples where automation is discussed, especially for Linux users.
- Ensure that references to automation tools do not assume a Windows environment; mention both PowerShell and CLI equally and in parallel.
- Where SDKs are mentioned, clarify that they are cross-platform and provide links or examples for both Windows and Linux environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-concur.md
...cs/blob/main/articles/data-factory/connector-concur.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a Windows bias by explicitly stating that the connector supports only Windows versions for the self-hosted integration runtime, and by linking to Windows-specific prerequisites. There are no Linux examples or mention of Linux support for the self-hosted integration runtime, and no Linux command-line or configuration guidance is provided.
Recommendations
- Clearly state whether Linux is supported or not for the self-hosted integration runtime in this scenario. If Linux is not supported, explain the limitation and provide a roadmap or alternatives if possible.
- If Linux support is available or planned, provide equivalent Linux instructions, including prerequisites, installation, and configuration steps.
- Include Linux-specific examples or notes where relevant, such as environment setup, service management, and troubleshooting.
- Avoid language that implies Windows is the only or default platform unless it is a technical requirement, and make this explicit to avoid confusion.
Data Factory
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 highlights the Execute SSIS Package activity, which is a Windows-centric technology, alongside more cross-platform Data Factory activities. There is a notable emphasis on SSIS (a Windows-only tool), including screenshots and step-by-step lineage instructions, without mentioning Linux alternatives or clarifying platform support. The documentation does not provide Linux-specific examples or guidance, and the order of presentation places the Windows-only SSIS activity on equal footing with cross-platform activities.
Recommendations
- Clearly indicate that SSIS is a Windows-only technology and specify any platform limitations.
- Provide examples or mention of Linux-compatible activities or tools within Data Factory, if available.
- If possible, include Linux-specific guidance or alternatives for users who do not have access to SSIS.
- Reorder examples to present cross-platform activities (Copy, Data Flow) before Windows-only activities (SSIS), and clarify platform compatibility in each section.
- Add a note in the prerequisites or relevant sections about platform support for each activity type.
Data Factory
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
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias primarily by referencing Windows-specific tooling (Dynamics XRM tooling for Windows client applications) and omitting any mention of Linux or cross-platform alternatives. There are no PowerShell or CMD examples, but the only referenced SDK/tooling is Windows-centric. No Linux-specific instructions, tools, or parity notes are provided, and the documentation does not clarify cross-platform support or limitations.
Recommendations
- Explicitly state whether the Dynamics XRM tooling and connector are supported on Linux or cross-platform environments, or provide alternatives if available.
- If there are Linux-compatible SDKs, CLIs, or APIs for interacting with Dynamics 365/Dataverse, include references and examples.
- Add a section or note clarifying any platform dependencies or limitations, especially for users deploying self-hosted integration runtimes or custom connectors on Linux.
- If only Windows is supported for certain features, clearly document this and suggest workarounds or roadmap for Linux support.
- Where possible, provide parity in examples and tooling references for both Windows and Linux environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-http.md
...docs/blob/main/articles/data-factory/connector-http.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation exhibits a mild Windows bias, primarily in the authentication and certificate management sections. Windows-specific tools (e.g., MMC, certificate store instructions) are referenced exclusively for managing client certificates on self-hosted Integration Runtime. Additionally, Windows authentication is listed alongside other authentication types, but there is no mention of Linux equivalents or instructions for Linux environments. In the 'TIP' for testing HTTP requests, only Windows-centric tools (Visual Studio, PowerShell) are mentioned, with no Linux alternatives like curl or wget.
Recommendations
- Add Linux-equivalent tools and instructions wherever Windows tools are mentioned. For example, suggest using 'curl' or 'wget' for testing HTTP endpoints, alongside PowerShell and Visual Studio.
- Provide guidance for managing client certificates on Linux-based self-hosted Integration Runtime machines, including certificate storage locations and permission management.
- Clarify whether Windows authentication is supported only on Windows-based Integration Runtime, and if so, explicitly state this and suggest alternatives for Linux environments.
- Ensure that examples and troubleshooting steps are platform-neutral or provide both Windows and Linux variants where applicable.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-netezza.md
...s/blob/main/articles/data-factory/connector-netezza.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Windows versions as prerequisites for the self-hosted integration runtime, without mentioning Linux support or alternatives. There are no Linux-specific instructions, examples, or clarifications, and the only OS mentioned is Windows. No PowerShell or Windows command-line examples are present, but the lack of Linux parity in prerequisites and examples is notable.
Recommendations
- Explicitly state whether the self-hosted integration runtime supports Linux, and provide installation instructions for Linux if available.
- If Linux is not supported, clearly mention this limitation to set user expectations.
- Include Linux-specific examples or notes where relevant, such as environment setup, configuration, or troubleshooting.
- Where OS-specific requirements are listed, present both Windows and Linux options (if supported), or clarify support status for each.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/copy-clone-data-factory.md
.../main/articles/data-factory/copy-clone-data-factory.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references a pattern for sharing SelfHosted Integration Runtime that is published specifically for PowerShell, which is a Windows-centric tool. There are no equivalent examples or references for Linux or cross-platform command-line tools. Additionally, there are no command-line examples at all (neither Windows nor Linux), but the only tool-specific link is to a PowerShell-based guide.
Recommendations
- Provide equivalent documentation or examples for Linux users, such as using Azure CLI or Bash scripts for cloning or sharing SelfHosted Integration Runtime.
- When referencing patterns or guides, include both PowerShell and Azure CLI (or REST API) versions, and mention them together or in a platform-neutral order.
- Explicitly state if certain operations can be performed using cross-platform tools, and provide links or examples for those tools.
- Avoid referencing only Windows-specific tools (like PowerShell) without mentioning alternatives for other platforms.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-odbc.md
...docs/blob/main/articles/data-factory/connector-odbc.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation assumes the use of Windows environments by referencing tools and patterns specific to Windows, such as the Integration Runtime Configuration Manager and ODBC DSN setup, without mentioning Linux equivalents or providing Linux-specific guidance. There are no examples or troubleshooting steps for Linux-based Integration Runtime hosts.
Recommendations
- Add explicit instructions for installing and configuring 64-bit ODBC drivers on Linux-based Integration Runtime hosts, including common distributions and package managers.
- Document how to set up and reference ODBC DSNs on Linux (e.g., editing /etc/odbc.ini and /etc/odbcinst.ini), and provide example connection strings for Linux.
- Clarify whether the Integration Runtime Configuration Manager is available on Linux, and if not, provide alternative troubleshooting steps for Linux environments (such as using command-line tools like isql or unixODBC diagnostics).
- Include screenshots or terminal examples for Linux where UI or tool usage is described.
- Explicitly state OS requirements and limitations for self-hosted Integration Runtime, and link to cross-platform setup guides if available.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sap-business-warehouse-open-hub.md
...a-factory/connector-sap-business-warehouse-open-hub.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by requiring the installation of the SAP .NET Connector 3.0, which is only available for Windows, as a prerequisite for using the SAP BW Open Hub connector. There are no instructions or examples for Linux environments, nor are alternative cross-platform connectors mentioned. The documentation assumes the use of Windows-based Self-hosted Integration Runtime and does not address Linux users or provide parity guidance.
Recommendations
- Explicitly state the platform requirements and limitations (e.g., that the SAP .NET Connector 3.0 is Windows-only) at the beginning of the prerequisites section.
- If Linux is not supported, clearly mention this and, if possible, provide a roadmap or alternatives for Linux users.
- If any cross-platform or Linux-compatible SAP connectors exist (such as SAP Java Connector or ODBC/JDBC options), mention them and provide guidance or links.
- Provide example setups or troubleshooting notes for Linux users, or direct them to relevant resources if support is limited.
- Consider advocating for or documenting any future plans for Linux support in the Self-hosted Integration Runtime or SAP connector stack.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sap-business-warehouse.md
...icles/data-factory/connector-sap-business-warehouse.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the troubleshooting and prerequisites sections, where it instructs users to place SAP NetWeaver RFC SDK libraries in the %windir%\system32 folderβa Windows-specific path. There are no equivalent instructions or examples for Linux-based Self-hosted Integration Runtime setups, nor is there mention of Linux library paths or troubleshooting steps. All examples and configuration steps are platform-agnostic JSON or UI-based, but the only OS-specific guidance is for Windows.
Recommendations
- Add explicit instructions for installing and configuring the SAP NetWeaver RFC SDK libraries on Linux-based Self-hosted Integration Runtime machines, including typical library paths (e.g., /usr/lib, /opt/sap, etc.).
- Include troubleshooting tips for Linux environments, such as checking LD_LIBRARY_PATH and file permissions.
- Mention both Windows and Linux in all OS-specific guidance, or clarify when instructions are Windows-only.
- Provide example commands or steps for both Windows and Linux wherever file placement or environment configuration is discussed.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sap-table.md
...blob/main/articles/data-factory/connector-sap-table.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows environments by requiring the SAP Connector for Microsoft .NET (a Windows-only component) as a prerequisite for the self-hosted integration runtime. There are no instructions, examples, or guidance for Linux-based integration runtimes or SAP connectors. All setup steps, tooling, and screenshots implicitly assume a Windows environment, and there is no mention of Linux compatibility or alternatives.
Recommendations
- Explicitly state whether Linux-based self-hosted integration runtimes are supported or not for SAP table integration. If not supported, clarify this limitation early in the prerequisites section.
- If Linux support is possible (e.g., via Java connectors or other cross-platform SAP libraries), provide equivalent setup instructions and examples for Linux environments.
- Include a table or section comparing Windows and Linux support for SAP connectors, listing any differences in prerequisites, setup, or functionality.
- Where screenshots or instructions are Windows-specific, add notes or alternative steps for Linux users (if applicable).
- If only Windows is supported, suggest workarounds for Linux users, such as running the integration runtime in a Windows VM or container.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-shopify.md
...s/blob/main/articles/data-factory/connector-shopify.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references Windows support explicitly for the self-hosted integration runtime and does not mention Linux support or provide Linux-specific instructions or examples. There are no Linux equivalents or parity information, and no examples or guidance for Linux-based environments.
Recommendations
- Explicitly state whether Linux is supported for the self-hosted integration runtime and, if so, provide instructions or a link to Linux setup documentation.
- If Linux is not supported, clearly mention this limitation to inform users.
- Include Linux-specific examples or notes where relevant, especially in sections discussing prerequisites or environment setup.
- Ensure parity in tool and platform references by mentioning both Windows and Linux where applicable.