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 701-725 of 1000 flagged pages
Data Factory Transform data using Hadoop Hive activity ...icles/data-factory/transform-data-using-hadoop-hive.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references a tutorial that uses PowerShell for data transformation before introducing the Hive activity, suggesting a Windows-centric onboarding path. There are no explicit Linux/macOS examples or CLI alternatives mentioned, and the initial learning path prioritizes Windows tools.
Recommendations
  • Include Linux/macOS onboarding tutorials alongside or before the PowerShell-based tutorial.
  • Reference cross-platform tools such as Azure CLI or Bash scripts for pipeline creation and management.
  • Add explicit examples or links for Linux/macOS users to perform equivalent tasks.
  • Clarify that the UI and JSON syntax are platform-agnostic, and provide guidance for non-Windows environments.
GitHub Create Pull Request
Data Factory Incrementally copy data from a source data store to a destination data store ...les/data-factory/tutorial-incremental-copy-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell-based tutorials for incremental data copy scenarios. All step-by-step instructions link to PowerShell guides, with no mention of Linux/macOS-friendly alternatives (e.g., Azure CLI, Bash, Python SDK). Windows tools and patterns are presented first and exclusively, creating friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent step-by-step tutorials using Azure CLI, Bash scripts, or Python SDK for each scenario.
  • Explicitly mention cross-platform options and tools at the start of each section.
  • Add notes or links for Linux/macOS users on how to perform the same tasks without PowerShell.
  • Reorder or parallelize examples so that Windows and Linux/macOS approaches are presented equally.
GitHub Create Pull Request
Data Factory Applying DataOps ...-docs/blob/main/articles/data-factory/apply-dataops.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates moderate Windows bias. While the core Azure Data Factory features are platform-agnostic, examples and tooling references for CI/CD and automated testing disproportionately favor Windows-centric tools (PowerShell, Visual Studio/NUnit), and Windows workflows are mentioned before or instead of Linux/macOS alternatives. There are no explicit Linux/macOS examples or equivalent open-source tool recommendations, which may create friction for non-Windows users.
Recommendations
  • Add explicit examples for Linux/macOS users, such as using Bash scripts and cross-platform CLI commands for CI/CD and testing.
  • Mention and provide examples for running automated tests with open-source, cross-platform frameworks (e.g., pytest for Python, Mocha for Node.js) alongside NUnit/Visual Studio.
  • Include guidance for using Azure CLI in Bash/zsh environments, not just PowerShell.
  • When referencing PowerShell or Visual Studio, always provide a Linux/macOS equivalent or clarify that the steps are cross-platform.
  • List cross-platform tools and workflows before or alongside Windows-specific ones to avoid implicit prioritization.
GitHub Create Pull Request
Data Factory Configure a virtual network for standard injection of Azure-SSIS integration runtime ...integration-runtime-standard-virtual-network-injection.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. The only explicit code example provided is a PowerShell script, with no equivalent Azure CLI, Bash, or cross-platform alternative. The NSG configuration section references Windows firewall rules and port 3389 (RDP), which is a Windows-specific remote access protocol. Additionally, the mention of Azure PowerShell and links to PowerShell-based guides appear before any cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the documentation assumes familiarity with Windows-centric tools and patterns.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples alongside PowerShell scripts for all automation and configuration tasks.
  • Clarify which steps and tools are cross-platform, and explicitly mention support for Linux/macOS where applicable.
  • Include references to Linux/macOS firewall management (e.g., iptables, ufw) when discussing NSG and network security.
  • Avoid assuming RDP (port 3389) as the only remote troubleshooting method; mention SSH as an alternative for Linux-based environments.
  • Ensure that links to cross-platform guides (e.g., Azure CLI, REST API) are given equal prominence as PowerShell-based instructions.
GitHub Create Pull Request
Data Factory Global parameters ...main/articles/data-factory/author-global-parameters.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation references PowerShell scripts as the method for deploying global parameters in CI/CD, without mentioning or providing equivalent examples for Linux/macOS users (e.g., Azure CLI, Bash). This creates friction for non-Windows users, especially in automation scenarios.
Recommendations
  • Add Azure CLI and Bash script examples for deploying global parameters in CI/CD workflows.
  • Explicitly mention cross-platform alternatives to PowerShell for ARM template deployment.
  • Clarify that ARM templates can be deployed from any OS and provide links to relevant cross-platform documentation.
GitHub Create Pull Request
Data Factory Configure a virtual network for express injection of Azure-SSIS integration runtime ...-integration-runtime-express-virtual-network-injection.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the section on configuring a custom DNS server, where only Windows-centric tools and scripts (main.cmd and setupdnsserver.ps1) are referenced. There are no Linux/macOS equivalents or examples provided for custom setup scripts, nor is there guidance for users who may need to perform these tasks on non-Windows platforms. Additionally, the related content references Azure PowerShell specifically, without mentioning cross-platform alternatives such as Azure CLI or Bash scripts.
Recommendations
  • Provide Linux/macOS-compatible setup script examples (e.g., Bash or Python) for custom DNS configuration.
  • Reference and link to Azure CLI documentation and examples alongside PowerShell, especially for tasks like joining Azure-SSIS IR to a virtual network.
  • Clarify whether the provided scripts (main.cmd, setupdnsserver.ps1) can be adapted for Linux/macOS environments, or offer alternative instructions.
  • Add explicit notes or sections for users operating in Linux/macOS environments, outlining any differences or additional steps required.
GitHub Create Pull Request
Data Factory Linked services ...main/articles/data-factory/concepts-linked-services.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prominently listing PowerShell and .NET as primary tools for creating linked services, with no mention of Linux/macOS-friendly alternatives (such as Azure CLI or Python SDK) in the main 'Create linked services' section or the related tutorials. PowerShell is highlighted as a key method, which is Windows-centric, and Windows tools are mentioned before REST API or cross-platform options. No Linux-specific examples or parity guidance are provided.
Recommendations
  • Add Azure CLI examples for creating linked services, as CLI is cross-platform and widely used on Linux/macOS.
  • Include Python SDK usage for linked service creation, which is platform-agnostic.
  • Reorder tool lists to start with cross-platform options (REST API, CLI, Python SDK) before Windows-centric tools (PowerShell, .NET).
  • Explicitly state that REST API, Azure CLI, and Python SDK are supported and provide links to their documentation.
  • Add a note clarifying that PowerShell and .NET examples are Windows-centric and suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Data Factory Pipelines and activities ...articles/data-factory/concepts-pipelines-activities.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, primarily through its use of PowerShell-based walkthroughs and examples. The 'Related content' and sample pipeline walkthroughs consistently reference PowerShell guides (e.g., 'quickstart-create-data-factory-powershell.md', 'tutorial-transform-data-spark-powershell.md'), with no mention of Linux/macOS CLI, Bash, or cross-platform alternatives. There are no explicit Windows-only tools or patterns, but the examples and tutorials are Windows-centric, creating friction for Linux/macOS users who may prefer Bash or Azure CLI.
Recommendations
  • Add equivalent walkthroughs and quickstarts using Azure CLI and Bash scripts, and link to them alongside PowerShell guides.
  • Explicitly mention cross-platform options for pipeline creation and management, clarifying that Azure CLI and REST API are available on Linux/macOS.
  • In 'Related content', include links to Linux/macOS-friendly tutorials, such as 'Quickstart: create a Data Factory (Azure CLI)' or 'Quickstart: create a Data Factory (REST API)'.
  • Where PowerShell is referenced, add notes or callouts for Linux/macOS users, pointing to alternative commands or documentation.
GitHub Create Pull Request
Data Factory Roles and permissions for Azure Data Factory ...in/articles/data-factory/concepts-roles-permissions.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions updating a data factory from PowerShell or the SDK as an example scenario, but does not provide equivalent Linux/macOS command-line examples (e.g., Azure CLI, Bash). The only tool specifically referenced for automation is PowerShell, which is Windows-centric. There is no mention of cross-platform alternatives or parity in examples, which may create friction for Linux/macOS users.
Recommendations
  • Include Azure CLI and Bash examples alongside PowerShell for automation tasks.
  • Explicitly mention that Azure CLI is cross-platform and provide links to relevant documentation.
  • Where PowerShell is referenced, clarify that PowerShell Core is available on Linux/macOS, or suggest Azure CLI as an alternative.
  • Add a note or section on how Linux/macOS users can perform equivalent tasks, especially for automation and scripting.
GitHub Create Pull Request
Data Factory Datasets ...cles/data-factory/concepts-datasets-linked-services.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is listed as a primary tool for creating datasets, both in the 'Create datasets' section and in the Quickstarts, with no mention of Linux/macOS equivalents such as Azure CLI or Bash scripting. Windows-centric tools and patterns (PowerShell, .NET) are mentioned before cross-platform options (REST API, Azure portal), and there are no examples or guidance for Linux users. This may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI and Bash scripting examples for dataset creation, as these are cross-platform and widely used on Linux/macOS.
  • In the 'Create datasets' and Quickstarts sections, mention Azure CLI and REST API before or alongside PowerShell and .NET to avoid Windows-first ordering.
  • Explicitly state which tools are cross-platform and provide links to their documentation.
  • Consider adding a note or section for Linux/macOS users, clarifying supported tools and providing parity in examples.
GitHub Create Pull Request
Data Factory Pipeline parameters and variables ...articles/data-factory/concepts-parameters-variables.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references PowerShell-based tutorials for pipeline creation and data transformation, which are Windows-centric. There are no equivalent examples or links for Linux/macOS users (such as Bash, Azure CLI, or Python SDK). The related content section lists PowerShell tutorials first and exclusively, reinforcing a Windows-first approach and leaving Linux users without direct guidance.
Recommendations
  • Add equivalent tutorials using Azure CLI, Bash, or Python SDK for pipeline creation and data transformation.
  • Include links to cross-platform tools and documentation in the 'Related content' section.
  • Explicitly state platform compatibility for each example and tutorial.
  • Consider reordering examples so that cross-platform options are presented before or alongside PowerShell.
GitHub Create Pull Request
Data Factory Pipeline execution and triggers ...s/data-factory/concepts-pipeline-execution-triggers.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. In the 'Manual execution with other APIs/SDKs' section, Azure PowerShell is given a dedicated example and is listed before Python and REST API methods. The PowerShell example uses Windows-specific syntax and tools, with no mention of Linux alternatives (such as Azure CLI or Bash scripting). The .NET SDK is also highlighted, which is more commonly used on Windows. There are no explicit Linux/macOS examples or parity notes, and Windows tools (PowerShell) are presented before cross-platform options.
Recommendations
  • Add Azure CLI examples for pipeline execution, which are cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples for REST API calls, demonstrating usage on Linux/macOS.
  • Explicitly state that PowerShell Core is available on Linux/macOS, or clarify platform compatibility.
  • Reorder examples to present cross-platform methods (REST API, Python SDK, Azure CLI) before Windows-specific tools.
  • Add notes or links for Linux/macOS users on how to install and use Azure CLI and PowerShell Core.
GitHub Create Pull Request
Data Factory Configure performance for the Azure-SSIS Integration Runtime ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/configure-azure-ssis-integration-runtime-performance.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively provides PowerShell-based configuration examples and references, which are native to Windows. There are no equivalent examples or instructions for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform scripting. The page assumes familiarity with Windows tools and patterns, creating friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI and Bash examples for all configuration steps, especially for creating and managing Azure-SSIS Integration Runtime.
  • Explicitly mention cross-platform options and tools, and provide links to relevant Azure CLI documentation.
  • Reorder examples so that cross-platform (CLI/Bash) options are presented alongside or before PowerShell, or clarify that PowerShell Core is available cross-platform.
  • Include notes on how Linux/macOS users can perform the same tasks, and highlight any platform-specific considerations.
GitHub Create Pull Request
Data Factory Configure Azure-SSIS integration runtime for business continuity and disaster recovery (BCDR) ...ctory/configure-bcdr-azure-ssis-integration-runtime.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias. It references PowerShell and SSMS (SQL Server Management Studio) for key operations, such as stopping integration runtimes and scripting jobs, without mentioning Linux/macOS alternatives. Windows-centric tools and patterns (PowerShell, SSMS) are assumed, and examples for these are provided before or instead of cross-platform options. No explicit Linux/macOS CLI or tool guidance is given for these steps.
Recommendations
  • Provide equivalent instructions using Azure CLI and/or REST API for stopping/starting Azure-SSIS IRs and other management tasks, which are cross-platform.
  • Include guidance for using Azure Data Studio (which is cross-platform) instead of or alongside SSMS for T-SQL scripting and job management.
  • Explicitly state which steps can be completed from Linux/macOS and provide links or examples for those environments.
  • Avoid referencing PowerShell or SSMS as the only options; mention alternatives and parity.
  • Add a section or callouts for Linux/macOS users, highlighting any differences or additional requirements.
GitHub Create Pull Request
Data Factory Copy data from an HTTP source ...docs/blob/main/articles/data-factory/connector-http.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page exhibits Windows bias primarily in the 'TIP' section, which suggests using Visual Studio and PowerShell's Invoke-RestMethod to test HTTP requests, with no mention of equivalent Linux/macOS tools (such as curl or wget). Additionally, the instructions for managing certificate permissions are written exclusively for Windows environments, referencing Microsoft Management Console (MMC) and Windows certificate stores, without guidance for Linux/macOS certificate management. Windows authentication is listed as a supported method, but there is no discussion of Linux-specific authentication scenarios.
Recommendations
  • Include Linux/macOS equivalents (e.g., curl, wget, httpie) alongside PowerShell and Visual Studio for testing HTTP requests.
  • Add instructions for managing client certificates on Linux/macOS, such as using OpenSSL or updating certificate stores.
  • Clarify how authentication types (especially Windows authentication) behave or are supported on non-Windows self-hosted integration runtimes.
  • Present cross-platform tools and examples in parallel or in a neutral order, rather than listing Windows tools first.
GitHub Create Pull Request
Data Factory Copy data from Amazon RDS for SQL Server ...es/data-factory/connector-amazon-rds-for-sql-server.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows authentication is presented as a primary option alongside SQL authentication, with examples and property tables for both. Troubleshooting steps and configuration instructions rely heavily on Windows-specific tools such as SQL Server Management Studio, SQL Server Configuration Manager, and Windows Firewall. All screenshots and UI references are Windows-centric. There are no Linux/macOS equivalents or instructions for managing Amazon RDS for SQL Server from non-Windows environments, nor are alternative tools (e.g., sqlcmd, Azure CLI, Linux firewall configuration) mentioned.
Recommendations
  • Add Linux/macOS-specific instructions for connecting to Amazon RDS for SQL Server, including examples using sqlcmd, Azure CLI, or other cross-platform tools.
  • Provide troubleshooting steps for Linux environments, such as configuring firewalls (iptables, ufw) and enabling TCP/IP via command line or AWS Console.
  • Include notes on authentication options available on Linux/macOS, clarifying limitations and alternatives to Windows authentication.
  • Offer screenshots or walkthroughs for cross-platform tools and interfaces, not just Windows-only GUIs.
  • Explicitly state any platform limitations (e.g., Windows authentication only supported on Windows IR) and suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Data Factory Copy data from/to a file system ...ob/main/articles/data-factory/connector-file-system.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows file share patterns (UNC paths, backslash notation) are presented first and most prominently in examples and explanations. References to Windows-specific tools and patterns (e.g., UNC paths, PowerShell, backslash escaping) are frequent, while Linux equivalents are only briefly mentioned (e.g., Samba) and lack detailed examples. There are no step-by-step Linux setup instructions or Linux-specific configuration samples, making it harder for Linux/macOS users to follow along.
Recommendations
  • Provide explicit Linux/macOS examples alongside Windows ones, including sample paths (e.g., /mnt/share, /home/user/data) and configuration JSON/UI screenshots.
  • Include step-by-step instructions for setting up a Linux file share (e.g., Samba configuration, permissions), not just a link to Samba.
  • When referencing command-line setup (e.g., enabling local access via PowerShell), offer Linux/macOS alternatives (e.g., Bash scripts, relevant commands).
  • Clarify cross-platform differences in path notation, escaping, and authentication, with concrete examples for each OS.
  • Ensure parity in troubleshooting and best practices for both Windows and Linux environments.
GitHub Create Pull Request
Data Factory Copy data from Netezza ...s/blob/main/articles/data-factory/connector-netezza.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a subtle Windows bias by referencing 'Windows versions' as prerequisites for the self-hosted integration runtime, and by not mentioning Linux as a supported platform for the integration runtime or for installing the Netezza ODBC driver. There are no explicit Linux/macOS instructions or examples, and no mention of Linux compatibility for the self-hosted integration runtime or driver installation.
Recommendations
  • Explicitly state whether the self-hosted integration runtime and Netezza ODBC driver are supported on Linux and macOS, and provide relevant documentation links.
  • If Linux is supported, add Linux-specific prerequisites and installation instructions for the Netezza ODBC driver.
  • Include examples or notes for Linux/macOS users where relevant, such as environment setup or troubleshooting.
  • If Linux is not supported, clearly state this limitation to set expectations for non-Windows users.
GitHub Create Pull Request
Data Factory Copy and transform data to and from SQL Server ...lob/main/articles/data-factory/connector-sql-server.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows authentication is described in detail, with examples and configuration steps. Troubleshooting and configuration sections reference Windows-only tools (SQL Server Management Studio, SQL Server Configuration Manager, Windows Firewall), and links point to Windows-specific documentation. There are no equivalent instructions or examples for Linux-based SQL Server installations, nor are Linux authentication patterns (e.g., Kerberos, integrated auth via Linux) discussed. All screenshots and step-by-step guides assume a Windows environment.
Recommendations
  • Add equivalent instructions for configuring SQL Server connectivity on Linux, including enabling remote connections, configuring TCP/IP, and managing firewall rules using Linux tools (e.g., firewalld, ufw, iptables).
  • Include examples for Linux authentication patterns, such as Kerberos or SQL authentication from Linux hosts.
  • Reference cross-platform tools (e.g., Azure Data Studio, sqlcmd) alongside or before Windows-only tools like SSMS.
  • Provide troubleshooting steps for common Linux deployment issues (e.g., SELinux, systemd service management).
  • Clarify which steps are Windows-specific and offer Linux/macOS alternatives where possible.
GitHub Create Pull Request
Data Factory Copy and transform data from and to a REST endpoint ...docs/blob/main/articles/data-factory/connector-rest.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits Windows bias primarily in its troubleshooting and testing recommendations. In the 'TIP' for testing REST requests, Windows-centric tools (Visual Studio, PowerShell's Invoke-RestMethod) are mentioned explicitly and before any cross-platform or Linux-native alternatives. No Linux/macOS equivalents (e.g., curl, httpie) are suggested, and Visual Studio is a Windows-only tool. This may lead Linux/macOS users to feel unsupported or unsure about recommended approaches for testing REST endpoints.
Recommendations
  • Include Linux/macOS-friendly tools such as curl and httpie alongside PowerShell and Visual Studio in the 'TIP' for testing REST requests.
  • List cross-platform tools first or together (e.g., 'You can use tools like curl, httpie, PowerShell's Invoke-RestMethod, Visual Studio, or a web browser to validate.').
  • Where PowerShell is mentioned, clarify that it is available on Linux/macOS, or suggest alternatives for those platforms.
  • Add example commands for curl or httpie for REST endpoint testing.
  • Review other sections for implicit Windows-first assumptions and ensure parity in tool recommendations.
GitHub Create Pull Request
Data Factory Copy data from SAP BW ...icles/data-factory/connector-sap-business-warehouse.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific system folders (e.g., %windir%\system32) for placing SAP NetWeaver RFC SDK libraries, without mentioning Linux equivalents or providing Linux installation guidance. No Linux-specific troubleshooting, file paths, or examples are given, which may hinder Linux/macOS users setting up the Self-hosted Integration Runtime.
Recommendations
  • Add instructions for installing SAP NetWeaver RFC SDK libraries on Linux/macOS, including typical library paths (e.g., /usr/lib, /opt/sap, etc.).
  • Provide troubleshooting tips for Linux/macOS environments, such as verifying library placement and permissions.
  • Include explicit notes on cross-platform compatibility of the Self-hosted Integration Runtime and SAP libraries.
  • Show example commands or file locations for both Windows and Linux/macOS when referencing dependency setup.
GitHub Create Pull Request
Data Factory Troubleshoot the file system connector ...les/data-factory/connector-troubleshoot-file-system.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references PowerShell and Windows-centric tooling for configuring the file system connector, with no mention of Linux/macOS alternatives or command-line instructions. The primary troubleshooting recommendation is to use PowerShell, and there are no examples or guidance for users on other platforms.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as using Bash or relevant CLI tools.
  • Explicitly state whether the configuration can be performed on non-Windows platforms, and if not, clarify this limitation.
  • Add cross-platform examples or links to platform-specific setup guides.
  • Mention any GUI or web-based alternatives if available.
GitHub Create Pull Request
Data Factory Troubleshoot connectors .../articles/data-factory/connector-troubleshoot-guide.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias primarily in the FIPS troubleshooting section, where instructions and file paths are exclusively Windows-specific (e.g., C:\Program Files\Microsoft Integration Runtime). There are no equivalent instructions or file paths for Linux/macOS users, nor is there any mention of how to perform similar troubleshooting steps on those platforms. The rest of the page is generally platform-neutral, but the critical FIPS section assumes a Windows environment for Self-hosted Integration Runtime.
Recommendations
  • Add explicit instructions for Linux/macOS environments, including file paths and configuration steps for disabling FIPS or equivalent settings.
  • Clarify whether Self-hosted Integration Runtime is supported on non-Windows platforms, and if not, state this clearly at the beginning of the troubleshooting guide.
  • If Linux/macOS support exists, provide parity in troubleshooting steps, screenshots, and examples for those platforms.
  • Where file paths or tools are mentioned, include both Windows and Linux/macOS equivalents, or note platform-specific differences.
GitHub Create Pull Request
Data Factory Troubleshoot the SAP Table, SAP Business Warehouse Open Hub, and SAP ODP connectors ...in/articles/data-factory/connector-troubleshoot-sap.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The troubleshooting documentation provides only a PowerShell example (Test-NetConnection) for testing SAP server connectivity, which is specific to Windows. There are no equivalent Linux/macOS commands or guidance, and the only tool mentioned is Windows-specific.
Recommendations
  • Add Linux/macOS equivalent commands, such as using 'nc', 'telnet', or 'curl' to test port connectivity.
  • Explicitly mention cross-platform alternatives and provide example commands for each major OS.
  • Clarify that the integration runtime can be installed on Windows and Linux, and tailor troubleshooting steps accordingly.
GitHub Create Pull Request
Data Factory Troubleshoot the Dynamics 365, Dataverse (Common Data Service), and Dynamics CRM connectors ...a-factory/connector-troubleshoot-dynamics-dataverse.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references XrmToolBox, a Windows-only tool, as a troubleshooting aid in multiple sections. There are no Linux/macOS alternatives or cross-platform instructions provided. No command-line or platform-agnostic examples are given, and troubleshooting steps do not mention Linux-specific considerations for network, authentication, or proxy/firewall configuration.
Recommendations
  • Provide cross-platform alternatives to XrmToolBox, such as REST API usage, PowerShell Core (which is cross-platform), or other open-source tools available on Linux/macOS.
  • Include troubleshooting steps and examples for Linux/macOS environments, especially for network, authentication, and proxy/firewall configuration.
  • Explicitly state platform requirements for referenced tools and suggest alternatives where possible.
  • Add notes or sections for Linux/macOS users outlining any differences or additional steps needed.
GitHub Create Pull Request
← Previous Page 29 of 40 Next →