Data Factory

1123
Total Pages
968
Linux-Friendly Pages
155
Pages with Bias
13.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

319 issues found
Showing 276-300 of 319 flagged pages
Data Factory Copy data from SQL Server to Blob storage using Azure portal ...n/articles/data-factory/tutorial-hybrid-copy-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. It exclusively references SQL Server Management Studio (SSMS), a Windows-only tool, for database setup and query execution, without mentioning Linux-compatible alternatives. There are no instructions or examples for performing equivalent steps on Linux or macOS, such as using Azure Data Studio, sqlcmd, or other cross-platform tools. The setup and installation steps for the self-hosted integration runtime also assume a Windows environment, with no guidance for Linux or macOS users.
Recommendations
  • Add instructions for setting up the SQL Server database and running queries using cross-platform tools like Azure Data Studio or sqlcmd.
  • Include explicit steps for installing and configuring the self-hosted integration runtime on Linux and macOS, referencing official guides.
  • Where screenshots or UI steps are shown, clarify any platform-specific differences and provide alternatives for non-Windows users.
  • Mention that SQL Server can be run on Linux and provide links or steps for Linux installation if relevant.
  • Ensure parity in troubleshooting and validation steps for Linux/macOS environments.
GitHub Create Pull Request
Data Factory Transform data using Hive in Azure Virtual Network using Azure portal ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-hive-virtual-network-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exhibits a notable Windows bias. It references Azure PowerShell as a prerequisite, provides instructions for editing the Windows hosts file, and assumes the use of Windows-based Azure VMs for installing the self-hosted integration runtime. There are no examples or guidance for performing these steps on Linux or macOS systems, nor is there mention of cross-platform alternatives such as Azure CLI or Linux file paths.
Recommendations
  • Include instructions for installing and configuring the self-hosted integration runtime on Linux VMs.
  • Provide Azure CLI commands as alternatives to Azure PowerShell for all relevant steps.
  • When editing the hosts file, include Linux/macOS paths (e.g., /etc/hosts) and syntax.
  • Explicitly state that the tutorial can be followed on Linux or macOS, and highlight any platform-specific differences.
  • Add screenshots or terminal examples for Linux environments where applicable.
GitHub Create Pull Request
Data Factory Transform data using Spark in Azure Data Factory ...ta-factory/tutorial-transform-data-spark-powershell.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell. All command-line instructions use Azure PowerShell cmdlets, with no mention of Azure CLI or Bash alternatives. The prerequisite section explicitly requires Azure PowerShell, and all deployment, pipeline management, and monitoring steps are provided only in PowerShell syntax. There are no Linux/macOS-specific instructions or examples, and no guidance for users who prefer Bash, Azure CLI, or cross-platform tools. The documentation assumes the user is familiar with PowerShell and Windows conventions, creating friction for Linux/macOS users.
Recommendations
  • Add equivalent instructions and examples using Azure CLI (az) commands, which are cross-platform and work natively on Linux/macOS.
  • Include notes or sections for Bash shell usage, especially for file operations and scripting.
  • Clarify that Azure PowerShell can be installed and used on Linux/macOS, but provide explicit installation instructions for those platforms.
  • Present both PowerShell and Azure CLI examples side-by-side, or allow users to select their preferred shell in the documentation.
  • Avoid language that implies PowerShell is the only option; mention alternatives up front in the prerequisites.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-virtual-network-configuration.md ...ssis-integration-runtime-virtual-network-configuration.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows by exclusively referencing the Azure portal UI and, in the related content, linking to a PowerShell-based guide for joining Azure-SSIS IR to a virtual network. There are no examples or instructions for performing these tasks using Linux-friendly tools such as Azure CLI, nor are there references to Bash scripting or cross-platform automation methods.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all portal-based steps, ensuring Linux and macOS users can follow along without relying on PowerShell.
  • Include references or links to documentation for performing these tasks using cross-platform tools (e.g., Azure CLI, REST API).
  • Where PowerShell is mentioned in related content, provide parity by linking to or creating guides for Azure CLI and/or Bash.
  • Explicitly state that all operations can be performed on Linux, macOS, and Windows, and clarify any platform-specific limitations.
  • Consider including screenshots or terminal output from Linux environments to reinforce cross-platform support.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows/SQL Server bias by exclusively providing troubleshooting steps and examples for SQL Server (a Microsoft/Windows-centric database), using T-SQL and system stored procedures (e.g., sys.sp_cdc_enable_db), and referencing Azure SQL Database as a sink. There are no examples or guidance for Linux-based databases (e.g., PostgreSQL, MySQL) or for using command-line tools common on Linux. No Linux-specific troubleshooting or parity is addressed.
Recommendations
  • Include troubleshooting steps and examples for popular Linux-based databases that support CDC, such as PostgreSQL or MySQL.
  • Provide equivalent command-line examples using Linux tools (e.g., psql, mysql CLI) where applicable.
  • Mention and link to documentation for enabling CDC on non-SQL Server sources, especially open-source databases commonly used on Linux.
  • Clarify in the introduction if the CDC resource only supports SQL Server, or expand support and documentation to other platforms.
  • Add notes or sections for Linux users, including any differences in setup, permissions, or troubleshooting steps.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by explicitly stating that the connector supports only Windows versions for the self-hosted integration runtime, with no mention of Linux support or alternatives. There are no Linux-specific instructions, examples, or parity guidance for non-Windows users.
Recommendations
  • Clearly state whether Linux-based self-hosted integration runtime is supported or not. If not, provide a roadmap or alternatives for Linux users.
  • If possible, add instructions or references for setting up the integration runtime on Linux (if/when supported).
  • Include explicit notes or guidance for users on non-Windows platforms, such as using Docker containers or other cross-platform solutions.
  • Ensure that all examples and prerequisites mention both Windows and Linux (or clarify platform limitations) to avoid excluding Linux users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-informix.md .../blob/main/articles/data-factory/connector-informix.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation assumes the Integration Runtime host is a Windows machine by referencing ODBC DSN setup and the Informix Client SDK, but does not clarify or provide guidance for Linux-based Integration Runtime hosts. There are no Linux-specific instructions or examples for setting up the ODBC driver or DSN, and all setup steps implicitly target Windows environments.
Recommendations
  • Explicitly state whether Self-hosted Integration Runtime is supported on Linux, and if so, provide equivalent setup instructions for Linux hosts.
  • Add Linux-specific guidance for downloading and installing the Informix ODBC driver and configuring DSN on Linux (e.g., editing odbc.ini).
  • Include example connection strings and troubleshooting tips relevant to Linux environments.
  • Clarify any platform limitations or differences in supported features between Windows and Linux Integration Runtime hosts.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-hubspot.md ...s/blob/main/articles/data-factory/connector-hubspot.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows evidence of Windows bias by referencing Windows support for the self-hosted integration runtime and linking to a Windows-specific prerequisites article. There are no explicit Linux or cross-platform instructions, and no Linux-specific examples or parity notes are provided.
Recommendations
  • Explicitly state whether the self-hosted integration runtime supports Linux, and if so, provide a link to Linux installation instructions.
  • If Linux is supported, add Linux-specific prerequisites and troubleshooting notes alongside the Windows references.
  • Include examples or screenshots for Linux environments where relevant (e.g., service installation, configuration).
  • If Linux is not supported, clearly state this limitation to set user expectations.
  • Review and update all references to ensure parity in tool and OS support, mentioning Linux and macOS where applicable.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows evidence of Windows bias by exclusively referencing Windows-centric tools and patterns, such as requiring a 64-bit ODBC driver and using system DSN setup on the Integration Runtime machine, without mentioning Linux equivalents or providing Linux-specific instructions. The troubleshooting section refers to Integration Runtime Configuration Manager, which is a Windows-only tool, and there are no examples or guidance for Linux environments, such as using unixODBC or configuring DSNs on Linux.
Recommendations
  • Add explicit instructions and examples for installing and configuring ODBC drivers and DSNs on Linux (e.g., using unixODBC).
  • Clarify whether Self-hosted Integration Runtime is supported on Linux and provide setup steps if so.
  • Include troubleshooting guidance for Linux environments, such as using command-line tools (isql, odbcinst) for testing connections.
  • Mention cross-platform considerations for connection strings and authentication, noting any OS-specific differences.
  • Ensure screenshots and UI references are not exclusively Windows-centric, or provide Linux alternatives where applicable.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by requiring the installation of the SAP .NET Connector (a Windows-only component) and does not mention or provide guidance for Linux-based integration runtimes. There are no Linux-specific instructions, examples, or troubleshooting steps, and all setup steps implicitly assume a Windows environment.
Recommendations
  • Provide guidance for Linux users, including supported alternatives to the SAP .NET Connector or clarify platform limitations.
  • If Linux is not supported, explicitly state this early in the prerequisites section to set user expectations.
  • If possible, document cross-platform options (e.g., Java connectors, ODBC/JDBC alternatives) for SAP BW integration.
  • Add troubleshooting and setup steps relevant to Linux environments if/when support is available.
  • Ensure future examples and instructions are platform-agnostic or include both Windows and Linux variants where applicable.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page shows a mild Windows bias by referencing 'network monitor (netmon) trace', which is a Windows-specific tool, and does not provide equivalent Linux troubleshooting guidance or examples. There are no command-line examples, but the only tool mentioned for network tracing is Windows-based, and no Linux alternatives are suggested.
Recommendations
  • When suggesting network tracing, mention cross-platform tools such as Wireshark or tcpdump, and provide instructions or links for both Windows and Linux environments.
  • If referencing a tool like 'netmon', clarify that it is Windows-specific and suggest Linux equivalents.
  • Include troubleshooting steps or examples that are applicable to both Windows and Linux self-hosted integration runtime scenarios.
  • Review the documentation for other implicit Windows assumptions and ensure Linux users are equally supported.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-dynamics-dataverse.md ...a-factory/connector-troubleshoot-dynamics-dataverse.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references XrmToolBox, a Windows-only tool, as a recommended troubleshooting utility without mentioning Linux alternatives or providing cross-platform guidance. No command-line examples or troubleshooting steps are given for Linux or macOS users. The documentation assumes access to Windows tools and does not address Linux environments.
Recommendations
  • Provide alternative troubleshooting tools or methods that are available on Linux (e.g., using curl, Postman, or cross-platform SDKs) for testing Dynamics connections.
  • Explicitly state the platform requirements for XrmToolBox and suggest equivalent steps for Linux users.
  • Include command-line examples for common troubleshooting tasks using PowerShell (for Windows) and Bash/curl (for Linux/macOS) where relevant.
  • Add a section addressing troubleshooting from non-Windows environments, including any limitations or workarounds.
GitHub Create Pull Request
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 →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides command-line examples using Windows-style paths (e.g., C:\DataFactories\DevDataFactory) and does not offer equivalent Linux/macOS examples (e.g., /home/user/DataFactories/DevDataFactory). All explicit CLI examples use Windows path conventions, which may confuse or exclude Linux users. However, the YAML pipeline example does specify 'ubuntu-latest' as the build agent, indicating Linux compatibility, but this is not reflected in the CLI usage examples.
Recommendations
  • Provide CLI examples using both Windows (C:\...) and Linux/macOS (/home/... or ~/...) path formats for all commands.
  • Explicitly state that the npm commands work cross-platform and mention any OS-specific considerations.
  • Add a note or section clarifying how Linux/macOS users should adapt the examples (e.g., path separators, environment variables).
  • Where screenshots or images show Windows UI or file paths, consider adding Linux equivalents or clarifying that the process is OS-agnostic.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-manual-promotion.md ...ry/continuous-integration-delivery-manual-promotion.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively describes manual promotion of Resource Manager templates using the Azure Portal GUI, which is a platform-agnostic web interface but is often associated with Windows-centric workflows. There are no examples or mentions of command-line alternatives (such as Azure CLI or PowerShell), and no explicit Linux/macOS guidance or parity. The lack of CLI examples may disadvantage Linux users who prefer or require non-GUI automation.
Recommendations
  • Add Azure CLI examples for exporting and deploying Resource Manager templates, as Azure CLI is cross-platform and widely used on Linux.
  • If PowerShell examples are added, ensure Azure CLI or Bash equivalents are also provided.
  • Explicitly mention that the Azure Portal is accessible from any OS, to clarify platform neutrality.
  • Include links or references to automation approaches (e.g., using az deployment group create) for users who prefer scripting or non-GUI workflows.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-migration-guidance-overview.md ...icles/data-factory/data-migration-guidance-overview.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation mentions Windows Installer (MSI) as a method for secured service-to-service integration but does not mention Linux equivalents or alternatives. No Linux-specific tools, authentication mechanisms, or examples are provided. The documentation lacks parity in describing how Linux users would perform the same secured integration or installation steps.
Recommendations
  • Include Linux-specific installation and authentication options (e.g., using .tar.gz packages, systemd services, or Linux service principals).
  • Mention cross-platform alternatives to Windows Installer (MSI), such as scripts or package managers (apt, yum) for Linux environments.
  • Provide examples or references for Linux-based deployments and authentication flows.
  • Ensure that all platform-specific tools or methods are presented together, or that Linux options are mentioned alongside Windows ones.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/enable-customer-managed-key.md ...n/articles/data-factory/enable-customer-managed-key.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell and Azure CLI for enabling Key Vault properties, but does not provide any Linux-specific examples or mention Linux tools explicitly. The UI instructions and screenshots are all based on the Azure Portal, which is platform-agnostic, but there is no parity in command-line examples for Linux users. The only command-line tools mentioned (PowerShell and Azure CLI) are listed together, but PowerShell is mentioned first, which may imply a Windows-first approach. There are no bash or shell script examples, and no explicit guidance for Linux users.
Recommendations
  • Provide explicit bash/Azure CLI examples for Linux users, especially for enabling Key Vault properties and managing permissions.
  • When listing command-line options, alternate the order (e.g., mention Azure CLI before PowerShell in some sections) or clarify that both are cross-platform.
  • Include notes or sections that highlight Linux/macOS compatibility and any platform-specific considerations.
  • Where possible, add screenshots or terminal snippets from Linux environments to demonstrate parity.
  • Explicitly mention that Azure CLI is cross-platform and provide installation links for Linux/macOS.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/guidance-for-byod-approach.md ...in/articles/data-factory/guidance-for-byod-approach.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively references the Self-Hosted Integration Runtime (SHIR), which is only available for Windows, and provides no mention of Linux support, alternatives, or examples. All installation and configuration steps implicitly assume a Windows environment, and there are no Linux equivalents or guidance for cross-platform scenarios.
Recommendations
  • Explicitly state that SHIR is only available on Windows, and clarify platform limitations at the start of the documentation.
  • If possible, provide guidance or references for Linux-based alternatives (such as Azure IR, or third-party integration runtimes) for users on non-Windows platforms.
  • Include a comparison table or section outlining platform support for SHIR and connectors.
  • If Linux support is planned or available in preview, mention this and link to relevant resources.
  • For each step involving installation or configuration, specify the platform context (e.g., 'On your Windows machine...') to avoid ambiguity.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-change-data-capture-resource-with-schema-evolution.md ...-to-change-data-capture-resource-with-schema-evolution.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for using Azure Data Factory's UI and Azure SQL Database as a source, with all examples and screenshots referencing Azure Data Studio and T-SQL. There are no explicit references to Windows-specific tools like PowerShell, but the only SQL client shown is Azure Data Studio (which is cross-platform but often associated with Windows), and there are no examples or guidance for Linux command-line tools, scripting, or alternative SQL clients. No Linux-specific instructions or parity examples are provided.
Recommendations
  • Add explicit examples for performing schema changes using Linux-native tools, such as running T-SQL via sqlcmd in a Linux shell.
  • Mention that Azure Data Studio is available on Linux and macOS, or provide alternative client options (e.g., DBeaver, Beekeeper Studio) for non-Windows users.
  • Include command-line examples for validating Delta Lake files using tools like Azure CLI, Databricks CLI, or Python scripts, which are common on Linux.
  • Clarify that all steps can be performed from Linux environments and provide screenshots or terminal snippets from Linux where appropriate.
  • If any step requires a Windows-only tool, suggest equivalent Linux alternatives or note cross-platform compatibility.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/domain-and-outbound-port-requirements-external.md ...udes/domain-and-outbound-port-requirements-external.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page references only Azure services and patterns that are closely associated with Windows environments (e.g., *.core.windows.net, *.database.windows.net), without mentioning Linux-specific tools, commands, or considerations. There are no examples or guidance for Linux users, nor are there references to Linux networking tools or configuration steps.
Recommendations
  • Add examples or notes for configuring outbound ports and domain access on Linux systems (e.g., using iptables, firewalld, or ufw).
  • Mention any Linux-specific considerations for self-hosted integration runtime, such as service management commands (systemctl) or log file locations.
  • If the integration runtime supports Linux, explicitly state so and provide parity in setup and troubleshooting instructions.
  • Include cross-platform command examples (e.g., both PowerShell and Bash) for common tasks related to the documented features.
GitHub Create Pull Request
Data Factory Transform data using Hadoop Pig activity ...ticles/data-factory/transform-data-using-hadoop-pig.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references a tutorial that is explicitly PowerShell-based, which is a Windows-centric tool. No Linux or macOS command-line examples or equivalent tutorials are mentioned. The rest of the page is platform-neutral, focusing on UI and JSON syntax, but the introductory guidance steers users toward Windows-first patterns.
Recommendations
  • Add references to Linux/macOS equivalents for the tutorial, such as Bash or Azure CLI.
  • Explicitly mention that the Pig activity can be configured and managed from non-Windows platforms.
  • Provide example workflows or command-line snippets for Linux/macOS users.
  • Ensure that future tutorials linked from this page offer parity for Linux/macOS environments.
GitHub Create Pull Request
Data Factory Compute environments .../main/articles/data-factory/compute-linked-services.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page shows mild Windows bias, primarily in the Azure Batch section, where PowerShell cmdlets (New-AzBatchAccount, New-AzBatchPool) and Windows-centric tools are referenced before alternatives. The use of Microsoft Azure Storage Explorer as a recommended tool for blob management is also Windows-focused, though it is cross-platform. However, most examples and configurations (especially for HDInsight) are Linux-based, and there are no exclusive Windows-only instructions or examples. No PowerShell-heavy or missing Linux example bias is present.
Recommendations
  • When referencing tools like Azure Storage Explorer, clarify its cross-platform availability and suggest CLI alternatives (e.g., Azure CLI, azcopy) for Linux/macOS users.
  • In the Azure Batch section, provide equivalent Azure CLI commands and links to Linux/macOS instructions alongside PowerShell cmdlets.
  • Avoid listing Windows tools or patterns before their Linux equivalents unless contextually necessary; present both options equally.
  • Explicitly mention OS compatibility for all tools and commands referenced.
GitHub Create Pull Request
Data Factory Copy data from Netezza ...s/blob/main/articles/data-factory/connector-netezza.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page displays mild Windows bias by referencing Windows versions as prerequisites for the self-hosted integration runtime, and by linking to a Windows-focused article for prerequisites. There is no explicit mention of Linux or macOS support, nor are Linux-specific instructions or examples provided for installing the IBM Netezza ODBC driver or running the integration runtime. However, the core configuration and code samples are platform-agnostic JSON, and there are no PowerShell-heavy or Windows-only command examples.
Recommendations
  • Explicitly mention Linux and macOS support for the self-hosted integration runtime and the Netezza ODBC driver.
  • Provide installation instructions or links for the IBM Netezza ODBC driver on Linux and macOS.
  • Reference Linux/macOS prerequisites and compatibility in the relevant sections.
  • Add troubleshooting notes or caveats for non-Windows platforms if applicable.
GitHub Create Pull Request
Data Factory Copy and transform data from Microsoft 365 (Office 365) ...lob/main/articles/data-factory/connector-office-365.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the certificate conversion instructions, which reference PowerShell and link to a PowerShell-based guide for converting certificates to base64. Additionally, the template for certificate conversion is likely tailored for environments where PowerShell is available, and no Linux/macOS alternatives are mentioned. The order of SDK/tool examples lists Azure PowerShell before REST API and ARM templates, which may subtly prioritize Windows-centric workflows.
Recommendations
  • Provide explicit Linux/macOS instructions for certificate conversion, such as using OpenSSL to convert PFX to base64.
  • Include CLI/bash examples alongside PowerShell, especially for steps involving certificate management.
  • Add notes or links to cross-platform tools for all steps currently described with Windows/PowerShell tools.
  • Reorder tool lists or clarify that all listed SDKs/tools are cross-platform where applicable.
  • Ensure screenshots and UI instructions do not assume Windows-only environments.
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
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation exhibits mild Windows bias, primarily in the 'TIP' section where Windows-centric tools (Visual Studio, PowerShell's Invoke-RestMethod) are mentioned for API validation, with no equivalent Linux/macOS tools referenced. Windows tools are listed first and exclusively, which may leave Linux/macOS users uncertain about alternatives.
Recommendations
  • Mention cross-platform tools such as curl, httpie, or Postman alongside or before Windows-specific tools for API validation.
  • Provide example commands for Linux/macOS (e.g., curl or wget) when discussing API testing.
  • Avoid listing Windows tools first or exclusively in generic guidance sections.
  • Add a note clarifying that all features and configuration steps are platform-agnostic unless otherwise stated.
GitHub Create Pull Request
Data Factory Troubleshoot the FTP, SFTP, and HTTP connectors ...s/data-factory/connector-troubleshoot-ftp-sftp-http.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias, notably in the SFTP troubleshooting section where WinSCP (a Windows-only tool) is recommended for credential validation, and a third-party base64 conversion tool is suggested before mentioning Linux command-line alternatives. While some Linux commands (e.g., openssl, ssh-keygen) are provided, Windows tools are referenced first or exclusively in certain cases. There are no explicit PowerShell examples, but Linux/macOS users may experience minor friction due to the order and selection of tools.
Recommendations
  • When recommending tools for credential validation, include cross-platform options such as FileZilla or command-line SSH clients alongside WinSCP.
  • When suggesting base64 encoding, provide explicit Linux/macOS command-line examples (e.g., `base64 <keyfile>`), not just third-party web tools.
  • Ensure that Linux/macOS commands are presented with equal prominence and, where possible, before or alongside Windows tools.
  • Add notes clarifying that all provided troubleshooting steps and commands are applicable on Linux/macOS, and highlight any platform-specific differences.
GitHub Create Pull Request
← Previous Page 12 of 13 Next →