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 76-100 of 1000 flagged pages
Data Factory Troubleshoot the FTP, SFTP, and HTTP connectors ...s/data-factory/connector-troubleshoot-ftp-sftp-http.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page shows evidence of Windows bias, most notably by recommending WinSCP (a Windows SFTP client) as a troubleshooting tool without mentioning Linux alternatives. In code samples for base64 encoding, a third-party web tool is recommended before mentioning Linux-native command-line options. The documentation provides a Linux example for ssh-keygen, but only in one context, and does not offer parity for other troubleshooting steps or tools. There are no PowerShell examples, but the overall pattern is to mention Windows tools first and omit Linux equivalents in several places.
Recommendations
  • When recommending troubleshooting tools like WinSCP, also mention Linux alternatives such as FileZilla, lftp, or the native sftp command.
  • For base64 encoding, provide Linux command-line examples (e.g., 'base64 -w 0 < private_key_file') alongside C# and Python samples.
  • Wherever a tool or command is referenced, ensure both Windows and Linux equivalents are provided, or at least mention cross-platform options.
  • Review all troubleshooting steps to ensure Linux users are not left without guidance or examples.
  • Consider adding a section or table summarizing common troubleshooting tools for both Windows and Linux environments.
GitHub Create Pull Request
Data Factory Copy data from SAP BW ...icles/data-factory/connector-sap-business-warehouse.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the prerequisites and troubleshooting sections, where instructions and file paths are exclusively given for Windows environments (e.g., %windir%\system32), and there is no mention of Linux equivalents or guidance for Linux-based Self-hosted Integration Runtime setups. No Linux-specific examples, file paths, or troubleshooting steps are provided, and Windows tooling is referenced first and exclusively.
Recommendations
  • Add explicit instructions for installing SAP NetWeaver libraries on Linux-based Self-hosted Integration Runtime machines, including typical file paths (e.g., /usr/lib or /opt/sap).
  • Include troubleshooting steps for Linux environments, such as where to place dependency libraries and how to verify permissions.
  • Mention required ports and firewall configuration for Linux systems.
  • Provide example configuration snippets or commands for Linux, where applicable.
  • Clarify that Self-hosted Integration Runtime can run on both Windows and Linux, and link to platform-specific setup guides.
GitHub Create Pull Request
Data Factory Troubleshoot the Azure Blob Storage connector ...a-factory/connector-troubleshoot-azure-blob-storage.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by referencing Windows-specific tools (diawp.exe.config) and configuration patterns, such as disabling FIPS mode on Windows VMs. There are no Linux-specific troubleshooting steps or examples, nor is there mention of equivalent Linux configuration files or procedures for self-hosted integration runtime. The guidance assumes a Windows environment for runtime installation and troubleshooting.
Recommendations
  • Add troubleshooting steps for Linux environments, including how to disable FIPS mode or configure the self-hosted integration runtime on Linux.
  • Mention Linux equivalents for configuration files and runtime management (e.g., paths, config file names, commands).
  • Provide examples or notes for both Windows and Linux platforms when referencing system-level changes.
  • Clarify platform-specific instructions and explicitly state if a feature or issue only applies to Windows.
GitHub Create Pull Request
Data Factory Troubleshoot the file system connector ...les/data-factory/connector-troubleshoot-file-system.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides troubleshooting guidance for the file system connector in Azure Data Factory and Azure Synapse. It specifically recommends using PowerShell commands to configure the self-hosted integration runtime, without mentioning equivalent Linux commands or tools. There is no reference to Linux shell usage or cross-platform alternatives, and Windows/PowerShell is presented as the default or only option.
Recommendations
  • Include equivalent Linux shell (bash) commands for configuring self-hosted integration runtime.
  • Mention cross-platform tools or scripts where possible, not just PowerShell.
  • Explicitly state whether the troubleshooting steps apply to both Windows and Linux environments, or provide separate instructions for each.
  • Add examples using Linux command-line utilities for parity.
  • Clarify any platform-specific limitations or requirements.
GitHub Create Pull Request
Data Factory Troubleshoot connectors .../articles/data-factory/connector-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates Windows bias primarily in the FIPS troubleshooting section, which exclusively references Windows-specific paths (e.g., C:\Program Files\Microsoft Integration Runtime) and configuration files (diawp.exe.config) without mentioning Linux equivalents or providing guidance for Linux-based self-hosted integration runtime environments. No Linux-specific troubleshooting steps, file paths, or examples are given anywhere in the document, and Windows terminology appears first and exclusively where platform-specific details are required.
Recommendations
  • Add troubleshooting instructions for Linux-based self-hosted integration runtime environments, including typical installation paths and configuration file locations.
  • Clarify whether FIPS-related issues and configuration steps apply to Linux, and if so, provide Linux-specific guidance (e.g., modifying config files, service restart commands).
  • Where platform-specific steps are required, present both Windows and Linux instructions side-by-side to ensure parity.
  • Explicitly state platform requirements or limitations for each troubleshooting step, so users on Linux are aware of applicability.
  • Include examples of common Linux errors or issues encountered with connectors and how to resolve them.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias by providing only a PowerShell example (Test-NetConnection) for troubleshooting SAP connector issues, with no equivalent Linux command or guidance. The troubleshooting steps assume the use of Windows tools and do not mention Linux alternatives, which may hinder users operating integration runtimes on Linux-based systems.
Recommendations
  • Add equivalent Linux troubleshooting commands, such as using 'telnet', 'nc', or 'curl' to test connectivity to the SAP server port.
  • Explicitly mention that integration runtimes can be installed on both Windows and Linux, and provide platform-specific instructions where relevant.
  • Present troubleshooting steps for both Windows and Linux environments, ideally side-by-side, to ensure parity.
  • Avoid assuming the use of PowerShell or Windows tools as the default; clarify when instructions are OS-specific.
GitHub Create Pull Request
Data Factory Troubleshoot the SharePoint Online list connector ...ctory/connector-troubleshoot-sharepoint-online-list.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates a strong Windows bias by exclusively recommending the SharePoint Online Management Shell (a Windows-only tool) and providing only PowerShell command examples for troubleshooting. There are no equivalent instructions or examples for Linux or cross-platform environments, and Windows tools are mentioned first and exclusively.
Recommendations
  • Provide equivalent troubleshooting steps using cross-platform tools, such as Azure CLI or Microsoft Graph API, which work on Linux and macOS.
  • Include examples for Linux users, such as using REST APIs or PowerShell Core (pwsh) if supported on Linux.
  • Mention platform requirements explicitly and offer alternatives for non-Windows environments.
  • Add notes or links to official documentation for Linux/macOS users on how to perform the same operations without relying on Windows-only tools.
GitHub Create Pull Request
Data Factory Connector upgrade guidance ...in/articles/data-factory/connector-upgrade-guidance.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides programmatic guidance exclusively using PowerShell scripts, which are native to Windows environments. There are no examples or mentions of equivalent Linux-friendly tools (such as Bash, Azure CLI, or Python scripts). This creates a bias toward Windows users and may hinder Linux users from easily following the guidance.
Recommendations
  • Provide equivalent examples using Azure CLI, Bash, or Python scripts for Linux and cross-platform users.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, and clarify compatibility if the scripts work cross-platform.
  • Add notes or sections for Linux users, including troubleshooting or setup steps for running scripts on non-Windows platforms.
  • Ensure future documentation includes both Windows and Linux approaches side-by-side for parity.
GitHub Create Pull Request
Data Factory Continuous integration and delivery pre- and post-deployment scripts ...ctory/continuous-integration-delivery-sample-script.md
High Priority View Details →
Scanned: 2026-01-11 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 page exclusively uses Azure PowerShell and PowerShell scripts for pre- and post-deployment automation, with no mention of Bash, Azure CLI, or Linux-native scripting alternatives. All examples, instructions, and YAML pipeline tasks are centered on PowerShell, which is traditionally a Windows-centric tool, even though PowerShell Core is cross-platform. There are no Linux-specific examples or guidance, and Windows/PowerShell patterns are presented as the default and only option.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for pre- and post-deployment tasks.
  • Explicitly mention that PowerShell Core is cross-platform, but also offer Linux-native alternatives for users who prefer Bash or shell scripting.
  • Include YAML pipeline tasks that use AzureCLI@2 or Bash@3 for script execution, demonstrating Linux compatibility.
  • Add a section comparing PowerShell and Bash/Azure CLI approaches, and help users choose the best fit for their environment.
  • Reference documentation or samples for Linux users, ensuring parity in tooling and instructions.
GitHub Create Pull Request
Data Factory Wait activity ...in/articles/data-factory/control-flow-wait-activity.md
High Priority View Details →
Scanned: 2026-01-11 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 bias toward Windows by providing only PowerShell examples and walkthroughs for pipeline creation and execution. There are no equivalent examples or instructions for Linux users (e.g., Bash, Azure CLI), and Windows tooling is mentioned first and exclusively in the example and tutorial references.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for pipeline creation and execution.
  • Include references and walkthroughs for Linux and macOS environments alongside PowerShell instructions.
  • Ensure that tooling and examples are presented in a platform-neutral order, or provide parallel instructions for both Windows and Linux users.
  • Explicitly mention cross-platform compatibility and provide links to relevant documentation for non-Windows users.
GitHub Create Pull Request
Data Factory Copy data from Vertica ...s/blob/main/articles/data-factory/connector-vertica.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias, particularly in the section on installing the Vertica ODBC driver for version 2.0. All installation steps and screenshots are based on Windows, with references to Windows-specific tools (such as the ODBC Data Source Administrator and .exe installers). There are no instructions or examples for installing the ODBC driver on Linux or macOS, nor are there any screenshots or command-line examples for non-Windows environments.
Recommendations
  • Provide parallel instructions for installing the Vertica ODBC driver on Linux (and optionally macOS), including relevant commands (e.g., using .rpm or .deb packages, or tarballs).
  • Include Linux-specific screenshots or terminal output where appropriate, or at least describe the process in text.
  • Mention Linux tools and configuration files (such as odbcinst.ini and odbc.ini) for ODBC driver registration and configuration.
  • Clarify that the self-hosted integration runtime can run on both Windows and Linux, and provide guidance for both platforms.
  • Ensure that all examples and instructions are platform-neutral or provide both Windows and Linux/macOS variants where applicable.
GitHub Create Pull Request
Data Factory Automate continuous integration ...ntinuous-integration-delivery-automate-azure-pipelines.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates a strong Windows bias, primarily through exclusive use of PowerShell for scripting and automation tasks, references to Windows-centric tools (PowerShell modules, .ps1 scripts), and lack of any Linux or cross-platform alternatives. All example scripts and instructions assume a Windows environment, with no mention of Bash, CLI, or other Linux-native approaches. This can hinder Linux users or those running Azure DevOps agents on non-Windows platforms.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for all PowerShell scripts, especially for stopping and starting triggers.
  • Clarify which steps are platform-agnostic and which require Windows-specific tools, and offer alternatives where possible.
  • Explicitly mention support for Linux agents in Azure Pipelines and provide guidance for running tasks on Linux/macOS.
  • Reference cross-platform modules (e.g., PowerShell Core, Azure CLI) and show how to use them in both Windows and Linux environments.
  • Add notes or sections highlighting any limitations or differences when using Linux agents, and how to address them.
GitHub Create Pull Request
Data Factory Continuous integration and delivery ...ticles/data-factory/continuous-integration-delivery.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively recommending PowerShell scripts for pre- and post-deployment tasks, referencing a .ps1 script, and warning specifically about PowerShell Core usage. There are no examples or guidance for equivalent scripting or automation using Bash, shell scripts, or native Linux tools. This may hinder users working in Linux-based CI/CD environments or those preferring cross-platform solutions.
Recommendations
  • Provide equivalent Bash or shell script examples for pre- and post-deployment tasks, or reference cross-platform scripting approaches.
  • Clarify whether the provided PowerShell scripts are compatible with PowerShell Core on Linux/macOS, and if not, supply alternatives.
  • Mention and demonstrate how to run deployment automation from Linux-based agents in Azure Pipelines or other CI/CD systems.
  • Avoid assuming PowerShell as the default scripting language; offer parity for Linux-native tools and workflows.
  • Explicitly state platform compatibility for all scripts and tools referenced.
GitHub Create Pull Request
Data Factory If Condition activity ...les/data-factory/control-flow-if-condition-activity.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides extensive PowerShell-based instructions and examples for running Azure Data Factory pipelines, assuming the use of Windows paths (e.g., C:\ADF) and PowerShell commands. There are no equivalent examples for Linux or cross-platform CLI tools (such as Azure CLI or Bash scripts), and the workflow is described entirely in terms of Windows tooling and conventions.
Recommendations
  • Add equivalent Azure CLI (az datafactory) examples for pipeline creation, execution, and monitoring, suitable for Linux/macOS environments.
  • Include Bash script samples and use POSIX-compliant file paths (e.g., /home/user/ADF) in parallel with Windows paths.
  • Explicitly state that the workflow can be performed on Linux/macOS and provide links or sections for non-Windows users.
  • Where possible, use platform-neutral language and tooling in introductory and example sections.
  • Add a note clarifying that PowerShell commands are for Windows users and direct Linux/macOS users to alternative instructions.
GitHub Create Pull Request
Data Factory Until activity ...n/articles/data-factory/control-flow-until-activity.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias. All command-line examples use PowerShell, and file paths are given in Windows format (e.g., C:\ADF). There is no mention of Linux, Bash, or cross-platform alternatives for running pipelines or managing JSON files. The only tooling referenced for automation is Azure PowerShell, with no Azure CLI or REST API examples. This may make it harder for Linux or macOS users to follow the instructions or adapt them to their environments.
Recommendations
  • Add equivalent Azure CLI examples for pipeline creation, management, and execution.
  • Include Bash shell script samples for running pipelines and monitoring status.
  • Use platform-neutral file paths in examples (e.g., /home/user/ADF or ./ADF).
  • Explicitly mention cross-platform options for automation, such as REST API or SDKs.
  • Add notes or sections for Linux/macOS users, highlighting any differences or requirements.
  • Ensure that references to PowerShell are balanced with alternatives, or clarify that PowerShell Core is cross-platform.
GitHub Create Pull Request
Data Factory Create Azure integration runtime ...icles/data-factory/create-azure-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a detailed example for creating Azure Integration Runtime using Azure PowerShell, a Windows-centric tool, but does not offer equivalent examples for Linux users (e.g., Azure CLI, Bash, or REST API). The only command-line example is PowerShell, and there is no mention of Linux-friendly alternatives. This may disadvantage users on Linux or macOS platforms.
Recommendations
  • Add Azure CLI examples for creating and managing Azure Integration Runtime, as CLI is cross-platform and widely used on Linux.
  • Include REST API example or reference for users who prefer direct API calls, which are platform-agnostic.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, or provide installation guidance for non-Windows platforms.
  • Ensure that command-line examples are presented in parallel (e.g., PowerShell and CLI side-by-side) or alternate the order to avoid Windows-first bias.
  • Add a note or section clarifying tool availability and platform compatibility for all major operating systems.
GitHub Create Pull Request
Data Factory Create an Azure-SSIS integration runtime via Azure portal ...actory/create-azure-ssis-integration-runtime-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-centric tools (e.g., SSMS, UNC paths, Windows authentication), mentioning PowerShell as an alternative method for provisioning, and omitting Linux-specific examples or cross-platform alternatives. Windows patterns (such as UNC paths and SSMS usage) are presented as defaults, and there is no mention of Linux equivalents or guidance for Linux users.
Recommendations
  • Include Linux-specific instructions or alternatives for tasks such as connecting to file systems, managing package stores, and authentication.
  • Provide examples using Azure CLI and Bash scripts alongside PowerShell, especially in the 'Related content' section.
  • Clarify cross-platform compatibility for tools like SSMS, or suggest alternatives (e.g., Azure Data Studio) that run on Linux.
  • When referencing file paths, include both Windows (UNC) and Linux (NFS, SMB mount) formats.
  • Explicitly state which steps or tools are platform-agnostic and which are Windows-specific, and provide guidance for Linux/macOS users where appropriate.
GitHub Create Pull Request
Data Factory Migrate data from an on-premises Hadoop cluster to Azure Storage ...-factory/data-migration-guidance-hdfs-azure-storage.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively referencing Windows machines and Windows VMs as hosts for the Data Factory self-hosted integration runtime, both on-premises and in Azure. There are no examples, instructions, or recommendations for deploying the integration runtime on Linux systems, nor any mention of Linux compatibility. The pricing section also explicitly excludes Azure Windows VM costs, implying Windows as the default platform. This focus may mislead users into thinking Linux is unsupported or suboptimal, despite the prevalence of Linux in Hadoop environments.
Recommendations
  • Explicitly mention that the Data Factory self-hosted integration runtime can be installed on Linux machines if supported, and provide instructions or links for Linux installation.
  • Include Linux-based examples and architectures, especially for environments where Hadoop clusters are already running on Linux.
  • Clarify platform compatibility in solution architecture diagrams and text, showing both Windows and Linux options for hosting the integration runtime.
  • Update pricing examples to include both Windows and Linux VM cost scenarios.
  • Add troubleshooting and best practices for Linux deployments, such as service management, firewall configuration, and performance monitoring.
GitHub Create Pull Request
Data Factory Use an Azure Resource Manager template to create an integration runtime ...ure-ssis-integration-runtime-resource-manager-template.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell commands for deploying and managing Azure-SSIS integration runtimes. There are no examples or instructions for Linux users, such as using Azure CLI, Bash, or cross-platform tools. Windows-specific tools and patterns (PowerShell cmdlets) are mentioned both in the main steps and in related notes, with no mention of Linux alternatives or parity.
Recommendations
  • Add equivalent Azure CLI examples for template deployment and IR management, which are cross-platform and work on Linux, macOS, and Windows.
  • Explicitly mention that PowerShell examples are Windows-centric and provide links or instructions for Linux users.
  • Include Bash script examples for common operations, or reference automation via REST API for platform-neutral guidance.
  • Reorder or balance documentation so that Windows and Linux approaches are presented together or in parallel, rather than Windows-first.
  • In related content, add links to Linux-friendly guides or CLI documentation for provisioning and managing Azure-SSIS IR.
GitHub Create Pull Request
Data Factory Create an Azure-SSIS integration runtime in Azure Data Factory .../data-factory/create-azure-ssis-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows-centric tools (SSDT, SSMS, dtutil, PowerShell) for deploying and managing Azure-SSIS IR. There are no examples or mentions of Linux-native tools or workflows, and PowerShell is presented as the only command-line option for scripting the provisioning process. The documentation does not address Linux users or provide parity in instructions for non-Windows environments.
Recommendations
  • Include examples using Azure CLI for provisioning Azure-SSIS IR, as it is cross-platform and available on Linux and macOS.
  • Mention and provide guidance for connecting to Azure SQL Database using cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd) alongside SSMS.
  • Clarify whether dtutil and AzureDTExec are available or supported on Linux, and if not, suggest alternatives or workarounds for Linux users.
  • Add explicit instructions or notes for Linux/macOS users, including prerequisites and tool installation steps.
  • Reorder tool mentions to present cross-platform options first, or at least in parallel with Windows-specific tools.
GitHub Create Pull Request
Data Factory Create a shared self-hosted integration runtime with PowerShell ...eate-shared-self-hosted-integration-runtime-powershell.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based instructions for creating and managing a shared self-hosted integration runtime in Azure Data Factory. The prerequisites and examples focus on Windows PowerShell ISE and installation steps that implicitly assume a Windows environment. There are no equivalent Linux/bash examples, nor any mention of cross-platform alternatives for scripting or installation.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI and Bash, which are cross-platform and commonly used on Linux and macOS.
  • Clarify whether the self-hosted integration runtime installer is available for Linux, and if so, include installation and registration steps for Linux systems.
  • Replace references to 'Windows PowerShell ISE' with more generic or cross-platform scripting environments (e.g., VS Code, terminal).
  • Add notes or sections highlighting platform compatibility and any differences in process or tooling between Windows and Linux.
  • Ensure all code samples are available in both PowerShell and Bash/Azure CLI formats, presented side-by-side or with clear navigation.
GitHub Create Pull Request
Data Factory Create a self-hosted integration runtime ...data-factory/create-self-hosted-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. All installation instructions, prerequisites, and examples are exclusively for Windows operating systems. Only Windows versions are listed as supported, and all command-line and automation examples use PowerShell or Windows-specific tools (e.g., dmgcmd.exe, .msi installers, editing Windows config files, referencing Windows services and registry keys). There is no mention of Linux or macOS support, nor are there any examples or guidance for non-Windows environments.
Recommendations
  • Clearly state in the prerequisites and introduction whether Linux or macOS are supported or not. If not, explain why.
  • If Linux support is available or planned, provide equivalent installation, configuration, and automation instructions for Linux (e.g., using shell scripts, systemd services, Linux file paths).
  • Include Linux/macOS examples alongside PowerShell, such as Bash or CLI commands, and reference cross-platform tools where possible.
  • If the self-hosted integration runtime is Windows-only by design, make this explicit at the top of the documentation to set user expectations.
  • Review all references to Windows tools (e.g., registry, services, .NET Framework, MSI installers) and, where possible, offer platform-agnostic alternatives or note their Windows specificity.
  • Add a section addressing common questions about cross-platform support and provide links to any roadmap or feedback channels for non-Windows support.
GitHub Create Pull Request
Data Factory Using credentials ...re-docs/blob/main/articles/data-factory/credentials.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows-centric tools and patterns (Azure portal, PowerShell) for credential management, with no mention or examples of Linux-native tools or CLI usage. PowerShell is listed as a primary scripting option, and screenshots/instructions are focused on GUI workflows typical of Windows environments. There are no Bash, Azure CLI, or Linux-specific instructions or examples, and Windows tools are mentioned before any cross-platform alternatives.
Recommendations
  • Add explicit examples using Azure CLI (az) for all credential management steps, including creation and assignment of managed identities.
  • Include Bash script snippets for common operations alongside PowerShell examples.
  • Clarify that SDKs and REST APIs are cross-platform and provide sample usage in Linux environments.
  • Add screenshots or instructions for performing actions on Linux/macOS, or in cross-platform terminals.
  • Reorder or balance tool mentions so that cross-platform options (Azure CLI, REST API) are presented before or alongside Windows-specific tools (PowerShell, Azure portal).
GitHub Create Pull Request
Data Factory Managed identity ...articles/data-factory/data-factory-service-identity.md
High Priority View Details →
Scanned: 2026-01-11 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 providing detailed PowerShell examples for generating and retrieving managed identities, referencing PowerShell commands for obtaining application IDs, and mentioning the Azure portal and PowerShell as the primary creation methods before SDK and REST API. There are no equivalent examples or instructions for Linux users (e.g., Azure CLI, Bash), and no mention of cross-platform alternatives. The documentation assumes familiarity with Windows-centric tooling and omits Linux-native workflows.
Recommendations
  • Add Azure CLI examples for all operations currently shown only with PowerShell (e.g., creating, updating, retrieving managed identities).
  • Explicitly mention Azure CLI and Bash as supported methods alongside PowerShell and Azure portal.
  • Present cross-platform command-line examples (Azure CLI, Bash) before or alongside PowerShell examples to avoid Windows-first ordering.
  • Include notes or links for Linux users on how to perform equivalent tasks, ensuring parity in guidance and tooling.
  • Review all code samples and ensure each PowerShell example has a corresponding Azure CLI/Bash example.
GitHub Create Pull Request
Data Factory General Troubleshooting ...ticles/data-factory/data-factory-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows evidence of Windows bias in several areas. Powershell is used exclusively in example commands for Azure Batch troubleshooting (e.g., unzip commands), and Windows-specific tools and patterns (such as Fiddler and Windows zip behavior) are mentioned without Linux equivalents. In the troubleshooting for compressed files, the explanation focuses on how Windows creates zip files with 'deflate64', and does not mention Linux zip utilities or alternatives. Powershell and Windows-centric instructions are given before or instead of Linux options.
Recommendations
  • Provide equivalent Linux/bash commands alongside Powershell examples, especially for tasks like unzipping files in Azure Batch custom activities.
  • Mention Linux tools (e.g., tcpdump, curl, unzip, zip) alongside Windows tools like Fiddler, and provide usage instructions for both platforms.
  • When discussing file compression issues, include guidance for Linux users (e.g., how to create zip files with 'deflate' using the 'zip' command).
  • Ensure troubleshooting steps and examples are platform-neutral or include both Windows and Linux approaches.
  • Review all example commands and tool recommendations for platform parity, and add Linux-specific documentation where missing.
GitHub Create Pull Request
← Previous Page 4 of 40 Next →