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 201-225 of 319 flagged pages
Data Factory Wait activity ...in/articles/data-factory/control-flow-wait-activity.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides sample PowerShell commands and refers to a walkthrough using Azure PowerShell, which is primarily a Windows-centric tool. There are no equivalent examples or walkthroughs for Linux/macOS users (e.g., using Azure CLI or REST API), and PowerShell is mentioned before any cross-platform alternatives.
Recommendations
  • Add examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Include instructions or links for running the same pipeline using REST API or SDKs (Python, .NET, etc.).
  • Explicitly note that PowerShell is available on Linux/macOS, or clarify any platform-specific limitations.
  • Present cross-platform examples (CLI, REST) before or alongside PowerShell examples to avoid Windows-first bias.
GitHub Create Pull Request
Data Factory Create an Azure-SSIS integration runtime in Azure Data Factory .../data-factory/create-azure-ssis-integration-runtime.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools (SSDT, SSMS, dtutil, PowerShell) as the 'familiar tools' for deploying and running SSIS packages, and provides explicit instructions and links for using Azure PowerShell to provision resources. There is no mention of Linux/macOS alternatives or cross-platform command-line tools, and Windows tools are listed first and exclusively.
Recommendations
  • Include cross-platform alternatives for SSIS package deployment and management, such as Azure CLI or REST API examples.
  • Clarify which tools (if any) are available on Linux/macOS, and provide guidance for non-Windows users.
  • Add explicit instructions or links for provisioning Azure-SSIS IR using Azure CLI or ARM templates from Linux/macOS.
  • Note any limitations for Linux/macOS users and suggest workarounds where possible.
GitHub Create Pull Request
Data Factory Copy or clone a data factory in Azure Data Factory .../main/articles/data-factory/copy-clone-data-factory.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references a PowerShell-based pattern for sharing SelfHosted Integration Runtime, but does not mention or provide equivalent guidance for Linux/macOS users. No command-line examples (such as Azure CLI or Bash) are given, and the only tool referenced for advanced scenarios is PowerShell, which is Windows-centric.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI, which is cross-platform.
  • Explicitly mention whether the referenced PowerShell pattern can be executed on Linux/macOS (e.g., via PowerShell Core), or provide alternative scripts.
  • Add notes or links for Linux/macOS users to ensure parity in all steps, especially for SelfHosted Integration Runtime sharing.
  • Where possible, show both Windows and Linux/macOS workflows side-by-side.
GitHub Create Pull Request
Data Factory Managed identity ...articles/data-factory/data-factory-service-identity.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by providing detailed PowerShell examples for generating and retrieving managed identities, while omitting equivalent CLI or Bash examples that would be more accessible to Linux/macOS users. PowerShell commands are presented first and in greater detail, with no mention of Azure CLI or cross-platform alternatives. This may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for all operations currently shown with PowerShell (e.g., creating, updating, and retrieving managed identities).
  • Present CLI/Bash examples alongside PowerShell, or even before PowerShell, to ensure parity and accessibility for Linux/macOS users.
  • Explicitly mention that Azure CLI is cross-platform and provide links to CLI documentation.
  • Review all code samples and ensure that every PowerShell example has a CLI/Bash equivalent.
GitHub Create Pull Request
Data Factory Provision Enterprise Edition for the Azure-SSIS Integration Runtime ...y/how-to-configure-azure-ssis-ir-enterprise-edition.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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively provides instructions and examples using Azure PowerShell, a Windows-centric tool, and does not mention or provide alternatives for Linux/macOS users (such as Azure CLI or REST API). Windows authentication and tooling are referenced without Linux equivalents, making the process less accessible for non-Windows users.
Recommendations
  • Add instructions and examples using Azure CLI, which is cross-platform and supported on Linux/macOS.
  • Mention REST API options for provisioning and configuring Azure-SSIS IR.
  • Clarify which steps require Windows-only tools and suggest workarounds or alternatives for Linux/macOS users.
  • Where Windows authentication is referenced, note any Linux-compatible approaches or limitations.
GitHub Create Pull Request
Data Factory Programmatically monitor an Azure Data Factory ...main/articles/data-factory/monitor-programmatically.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 page demonstrates notable Windows bias, especially in the REST API and PowerShell sections. REST API usage is shown exclusively with PowerShell scripts, which are native to Windows and not directly usable on Linux/macOS. There are no Linux/macOS shell (e.g., Bash, curl) examples for REST API calls. PowerShell is given a dedicated section, and Windows tools (PowerShell cmdlets) are referenced throughout. No equivalent Linux command-line examples (e.g., Bash, curl, or Azure CLI) are provided, making it harder for Linux/macOS users to follow along.
Recommendations
  • Add REST API examples using Bash and curl, demonstrating equivalent functionality for Linux/macOS users.
  • Include Azure CLI examples where possible, as CLI is cross-platform.
  • When showing REST API usage, present both PowerShell and Bash/curl examples side-by-side.
  • Clarify in the REST API section that PowerShell is Windows-native and suggest alternatives for Linux/macOS.
  • Consider reordering examples so that cross-platform methods (Python, REST API via curl, Azure CLI) appear before Windows-specific tools.
GitHub Create Pull Request
Data Factory Reconfigure the Azure-SSIS integration runtime .../data-factory/manage-azure-ssis-integration-runtime.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 page demonstrates a notable Windows bias by exclusively providing Azure PowerShell examples for command-line operations, with no mention of Bash, Azure CLI, or cross-platform alternatives. The use of PowerShell cmdlets and references to Windows-centric tooling is prevalent, and there are no Linux/macOS-specific instructions or parity. The ordering also places PowerShell before any mention of other command-line options.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation guidance.
  • Include Bash script examples or instructions for performing the same operations using REST API or Azure CLI.
  • Reorder sections so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell examples.
  • Add a note clarifying platform compatibility for all command-line instructions.
GitHub Create Pull Request
Data Factory Use Azure SQL Managed Instance with Azure-SQL Server Integration Services (SSIS) in Azure Data Factory ...ata-factory/how-to-use-sql-managed-instance-with-ir.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools like SQL Server Management Studio (SSMS) as the 'familiar tool' for managing SSIS projects and packages, without mentioning cross-platform alternatives. There are no examples or guidance for Linux/macOS users, such as using Azure Data Studio or command-line tools. Additionally, when discussing network configuration, the documentation refers to Azure PowerShell and Azure CLI only in the context of a specific NSG rule, and does not provide explicit Linux/macOS instructions or examples. The overall flow assumes a Windows-centric workflow and omits Linux/macOS parity in tooling and step-by-step examples.
Recommendations
  • Mention and provide examples for cross-platform tools such as Azure Data Studio and Azure CLI for managing SSIS and Azure SQL resources.
  • Include explicit instructions and screenshots for Linux/macOS users, especially for steps involving network configuration and resource management.
  • Add notes or sections clarifying which steps are platform-agnostic and which require Windows-only tools, with suggested alternatives where possible.
  • Ensure that any references to PowerShell are accompanied by Azure CLI equivalents, and provide sample commands for both Windows and Linux/macOS environments.
GitHub Create Pull Request
Data Factory Transform data using Hadoop Streaming activity .../data-factory/transform-data-using-hadoop-streaming.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias toward Windows by exclusively using Windows-style executable names (e.g., MyMapper.exe, MyReducer.exe) in its JSON sample and file paths. There are no examples or mentions of Linux-style scripts (e.g., .py, .sh) or guidance for non-Windows users. This may lead Linux/macOS users to believe only Windows executables are supported, despite Hadoop Streaming's cross-platform nature.
Recommendations
  • Provide examples using Linux-compatible scripts (e.g., Python .py files, Bash .sh scripts) in addition to Windows executables.
  • Clarify in the documentation that both Windows and Linux executables/scripts are supported, if applicable.
  • Add notes or sections addressing platform-specific considerations for mapper and reducer programs.
  • Ensure that file path examples and naming conventions do not imply exclusivity to Windows.
  • If there are platform limitations, explicitly document them.
GitHub Create Pull Request
Data Factory Provision the Azure-SSIS integration runtime ...es/data-factory/tutorial-deploy-ssis-packages-azure.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 page exhibits Windows bias by exclusively referencing Windows-centric tools (SSDT, SSMS, dtutil, AzureDTExec), mentioning PowerShell for firewall configuration, and omitting Linux/macOS alternatives or examples. No cross-platform deployment or management tools are discussed, and all instructions assume Windows environments and tooling.
Recommendations
  • Include examples for deploying and managing SSIS packages using cross-platform tools (e.g., Azure CLI, REST API, or Data Factory UI) where possible.
  • Mention and provide instructions for using Azure Data Studio, which is available on Linux/macOS, as an alternative to SSMS for some tasks.
  • Provide Linux/macOS equivalents for command-line utilities (if available), or clarify platform limitations.
  • When referencing PowerShell, also provide Azure CLI commands for firewall rule configuration and other administrative tasks.
  • Explicitly state platform requirements and limitations for each tool, and recommend alternatives for non-Windows users.
GitHub Create Pull Request
Data Factory Global parameters ...main/articles/data-factory/author-global-parameters.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias in the CI/CD section, where deploying global parameters via a PowerShell script is mentioned as the only explicit scripting example. No equivalent Linux/macOS deployment method (such as Azure CLI, Bash, or cross-platform tools) is provided or referenced. The rest of the page is UI-focused and platform-neutral.
Recommendations
  • Add Linux/macOS-compatible deployment instructions, such as using Azure CLI or Bash scripts, for managing global parameters in CI/CD.
  • Explicitly mention that PowerShell is available cross-platform, or provide links to cross-platform PowerShell installation and usage.
  • Include example commands for both Windows (PowerShell) and Linux/macOS (Azure CLI/Bash) when discussing automation or scripting.
  • Clarify that ARM template deployment can be performed from any OS, and provide sample workflows for non-Windows environments.
GitHub Create Pull Request
Data Factory Applying DataOps ...-docs/blob/main/articles/data-factory/apply-dataops.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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, especially in the CI/CD and automated testing sections. PowerShell and Visual Studio/NUnit are mentioned as primary tools for automated testing and deployment, with no Linux/macOS alternatives or examples provided. The use of Windows-centric tools is referenced before any cross-platform options (e.g., AZ CLI), and there is an assumption of familiarity with Windows development environments. There are no explicit Linux/macOS examples or instructions, and no mention of Bash, shell scripting, or other non-Windows automation tools.
Recommendations
  • Add explicit examples for Linux/macOS users, such as Bash scripts for deployment and testing.
  • Include references to cross-platform CI/CD tools (e.g., GitHub Actions, Azure CLI usage on Linux/macOS).
  • Provide parity in automated testing instructions, such as using pytest or other non-Windows frameworks.
  • Mention that AZ CLI is cross-platform and provide sample commands for Linux/macOS.
  • Avoid assuming Visual Studio or PowerShell as the default environment; offer alternatives for non-Windows users.
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-11 06:20
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, with no mention of Linux/macOS equivalents. The related content also highlights Azure PowerShell as a primary method for joining Azure-SSIS IR to a virtual network, without referencing cross-platform CLI alternatives. No Linux or bash examples are provided for custom setup or network configuration tasks.
Recommendations
  • Provide equivalent bash or shell scripts for custom DNS setup, and reference them alongside the Windows scripts.
  • Include instructions or examples using Azure CLI (az), which is cross-platform, for all network configuration and resource management tasks.
  • Explicitly mention Linux/macOS compatibility for all setup steps, and note any platform-specific considerations.
  • Add links to documentation or samples for Linux/macOS users where relevant.
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-11 06:20
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, primarily through the exclusive use of PowerShell scripts for automation and references to Windows-specific firewall rules. There are no CLI, Bash, or Linux/macOS examples provided for key configuration tasks, such as adding UDRs. Additionally, the NSG section references Windows firewall rules for port management, and the troubleshooting guidance assumes familiarity with Windows networking concepts.
Recommendations
  • Provide equivalent Azure CLI and/or Bash examples for all PowerShell scripts, especially for UDR and NSG configuration.
  • Explicitly mention cross-platform tools and workflows, clarifying that all steps can be performed on Linux/macOS using Azure CLI.
  • Where Windows firewall rules are referenced, add notes or examples for managing firewall rules on Linux (e.g., using iptables or firewalld).
  • Reorder or balance examples so that Linux/macOS approaches are presented alongside or before Windows-specific ones.
  • Add a section or FAQ entry addressing common Linux/macOS user concerns and workflows.
GitHub Create Pull Request
Data Factory Troubleshoot CI-CD, Azure DevOps, and GitHub issues ...ticles/data-factory/ci-cd-github-troubleshoot-guide.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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. Several troubleshooting steps and automation recommendations reference PowerShell and Windows-centric tools (e.g., PowerShell API, Nunit for .NET, Azure PowerShell tabs in linked templates), but do not provide equivalent Linux/macOS examples or alternatives. There are no explicit Linux shell (bash) or cross-platform CLI examples, and Windows tooling is mentioned without parity for Linux users. This may create friction for users on Linux or macOS, especially when automating or scripting CI/CD tasks.
Recommendations
  • Add Linux/macOS-specific examples for automation and scripting tasks (e.g., bash, Azure CLI, Python SDK).
  • When referencing PowerShell, also provide equivalent Azure CLI or REST API commands usable on Linux/macOS.
  • Include cross-platform test automation examples (e.g., PyTest for Python, xUnit for .NET Core, etc.) alongside Nunit and PowerShell.
  • Where documentation links reference 'Azure PowerShell', add tabs or sections for 'Azure CLI' and clarify cross-platform usage.
  • Explicitly state which steps are platform-agnostic and which require Windows, and provide alternatives where possible.
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-11 06:20
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, but does not provide equivalent examples or mention cross-platform command-line tools (e.g., Azure CLI, Bash). PowerShell is primarily associated with Windows, and its mention without Linux/macOS alternatives suggests a Windows bias. There are no explicit Linux/macOS examples or references to tools commonly used on those platforms.
Recommendations
  • Include Azure CLI examples for updating a data factory, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell is to be used, and provide platform-agnostic instructions.
  • Add Bash or shell script examples where relevant.
  • Ensure that all instructions referencing command-line tools provide both Windows and Linux/macOS alternatives.
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-11 06:20
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. While most configuration steps are performed via the Azure portal or ADF UI (which are cross-platform), there is a notable emphasis on Windows-centric tools and workflows. SQL Server Management Studio (SSMS), a Windows-only tool, is referenced for scripting and job management. Azure PowerShell is mentioned as an alternative for stopping IRs, but no CLI or Bash examples are provided. The only code samples are T-SQL, which are platform-neutral, but the orchestration and job management examples assume SSMS and do not mention Linux/macOS alternatives. Windows tools and patterns are presented first and exclusively, with no guidance for Linux/macOS users.
Recommendations
  • Provide equivalent instructions using Azure CLI and/or Bash scripts for all steps currently described with Azure PowerShell.
  • Reference cross-platform SQL tools (such as Azure Data Studio or sqlcmd) alongside SSMS for database scripting and job management.
  • Explicitly state which steps can be performed on Linux/macOS and provide links or examples for those platforms.
  • Add a section or callouts for Linux/macOS users, clarifying any limitations and offering alternatives where possible.
  • Ensure that all screenshots and UI references are not Windows-specific, or provide alternatives.
GitHub Create Pull Request
Data Factory Linked services ...main/articles/data-factory/concepts-linked-services.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 Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is listed as a primary method for creating linked services, and Windows-centric tools (PowerShell, .NET) are mentioned before cross-platform or Linux-native options. There are no explicit Linux or macOS command-line examples (e.g., Bash, Azure CLI), nor are Linux-specific instructions or parity tools referenced. This may create friction for users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for creating linked services, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that REST API and ARM templates are platform-agnostic and provide sample usage from Bash or other non-Windows shells.
  • Reorder tool/SDK lists so that cross-platform options (Azure CLI, REST API) are listed before or alongside Windows-specific tools (PowerShell, .NET).
  • Include a section or note on how Linux/macOS users can perform equivalent tasks, with links to relevant documentation.
  • Provide sample scripts or walkthroughs for Linux/macOS environments where appropriate.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits moderate Windows bias in the 'Manual execution with other APIs/SDKs' section. Azure PowerShell is highlighted as a primary method for pipeline execution, with a full example provided, while Linux/macOS equivalents (such as Azure CLI or Bash scripting) are not mentioned or demonstrated. PowerShell is a Windows-centric tool, and its example appears before REST API and Python SDK, which are more cross-platform. There is no explicit Azure CLI example, nor guidance for Linux/macOS users on running pipelines from their environments.
Recommendations
  • Add Azure CLI examples for pipeline execution, as CLI is cross-platform and widely used on Linux/macOS.
  • Include Bash or shell script examples for invoking REST API endpoints, demonstrating how Linux/macOS users can trigger pipelines.
  • Reorder the examples so that cross-platform methods (REST API, Python SDK, Azure CLI) appear before Windows-specific tools like PowerShell.
  • Explicitly mention that PowerShell examples are primarily for Windows, and provide links or guidance for Linux/macOS users.
  • Ensure all referenced quickstarts/tutorials have Linux/macOS instructions or alternatives.
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-11 06:20
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 described in detail and provided as a primary option alongside SQL authentication, with examples using domain\username formats. Troubleshooting steps and configuration instructions reference Windows-specific tools (SQL Server Management Studio, SQL Server Configuration Manager, Windows Firewall) and link to Microsoft documentation focused on Windows environments. There are no Linux/macOS equivalents or instructions for performing these tasks on non-Windows platforms, nor is there guidance for Linux-based integration runtimes or authentication methods.
Recommendations
  • Add explicit instructions and examples for Linux/macOS environments, including how to configure Amazon RDS for SQL Server connectivity from those platforms.
  • Provide troubleshooting steps using Linux tools (e.g., sqlcmd, firewall-cmd/iptables) and reference relevant Linux documentation.
  • Clarify which features (such as Windows authentication) are only available on Windows-based integration runtimes, and suggest alternatives for Linux users.
  • Include parity in example code and UI screenshots for Linux/macOS where applicable.
  • Mention limitations or required workarounds for Linux/macOS users upfront in the prerequisites section.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation exhibits mild Windows bias, primarily in the authentication and certificate management sections. Windows-specific tools (MMC, certificate store instructions) are referenced exclusively for managing client certificates on self-hosted Integration Runtime. Additionally, the only example tool for testing HTTP requests mentioned in the 'TIP' is PowerShell's Invoke-RestMethod, with no mention of Linux/macOS equivalents like curl or wget. No Linux/macOS certificate management guidance is provided.
Recommendations
  • Add Linux/macOS equivalents for testing HTTP requests, such as curl and wget, alongside PowerShell.
  • Provide instructions for installing and managing client certificates on Linux/macOS self-hosted Integration Runtime hosts (e.g., using openssl, update-ca-certificates, or keytool).
  • Clarify whether Windows-specific certificate instructions apply only to Windows-based Integration Runtime, and provide parity for other platforms.
  • Where tools are listed, present cross-platform options together or in alphabetical order, rather than Windows-first.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the troubleshooting section, where it instructs users to place SAP NetWeaver RFC SDK libraries in the %windir%\system32 folder—a Windows-specific path and pattern. There are no equivalent instructions or examples for Linux or macOS environments, nor any mention of alternative library locations or setup steps for non-Windows platforms. All configuration examples are platform-neutral JSON, but the critical runtime setup guidance is Windows-centric.
Recommendations
  • Add instructions for installing and configuring the SAP NetWeaver RFC SDK libraries on Linux and macOS, including typical library paths (e.g., /usr/lib, /usr/local/lib).
  • Clarify whether the Self-hosted Integration Runtime supports Linux/macOS, and if so, provide platform-specific troubleshooting steps.
  • Include notes or examples for non-Windows environments wherever file paths or system configuration is discussed.
  • Explicitly state platform requirements and limitations for the connector and runtime.
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-11 06:20
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 moderate Windows bias. Windows terminology, path syntax, and tools (such as PowerShell and UNC paths) are presented first and most examples use Windows-style paths. Linux support is mentioned (e.g., via Samba), but Linux-specific instructions, examples, or screenshots are missing. References to enabling local access point to PowerShell commands, with no Linux shell equivalent. The documentation assumes familiarity with Windows file sharing conventions and tools, and does not provide parity for Linux/macOS users.
Recommendations
  • Add explicit Linux/macOS examples for file paths, dataset definitions, and connector configuration (e.g., /mnt/share, /home/user/data).
  • Include Linux shell commands (such as mounting SMB shares with 'mount -t cifs') alongside PowerShell instructions for enabling local access.
  • Provide screenshots or UI walkthroughs using Linux-style paths.
  • Expand the Samba section with step-by-step instructions for setting up and sharing folders on Linux.
  • Clarify cross-platform differences in path escaping and authentication.
  • Ensure all examples and notes mention both Windows and Linux/macOS scenarios where applicable.
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-11 06:20
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. The only example for configuring security controls references using local PowerShell, a Windows-centric tool, with no mention of Linux or macOS alternatives. There are no bash, shell, or cross-platform instructions, and Windows tooling is presented as the default approach.
Recommendations
  • Add equivalent instructions for Linux/macOS environments, such as using bash scripts or command-line tools.
  • Explicitly mention whether the configuration can be performed on Linux/macOS, and provide steps if possible.
  • If PowerShell is required, clarify if PowerShell Core (cross-platform) is supported and provide installation guidance.
  • Present cross-platform options first, or at least alongside Windows-specific instructions.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides troubleshooting steps that exclusively use Windows-specific tools and commands (PowerShell's Test-NetConnection) to verify SAP server connectivity. There are no equivalent Linux/macOS commands or instructions, and Windows tooling is referenced first and exclusively, creating friction for users on non-Windows platforms.
Recommendations
  • Add Linux/macOS equivalent commands (e.g., 'nc <sap server> 3300' or 'telnet <sap server> 3300') for connectivity testing.
  • Explicitly mention cross-platform alternatives and clarify which steps are OS-specific.
  • Consider reordering or grouping troubleshooting steps by platform to improve clarity.
  • Provide guidance on installing required tools on Linux/macOS if needed.
GitHub Create Pull Request
← Previous Page 9 of 13 Next →