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 301-325 of 1000 flagged pages
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-http.md ...docs/blob/main/articles/data-factory/connector-http.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation demonstrates Windows bias primarily in its recommendations and instructions. It suggests using Windows-specific tools (Visual Studio, PowerShell's Invoke-RestMethod, MMC for certificate management) for testing and configuration, and describes authentication using Windows credentials. Windows tools are mentioned before any cross-platform or Linux alternatives, and no Linux-specific examples or tools (such as curl, wget, or OpenSSL) are provided for equivalent tasks.
Recommendations
  • Include Linux/macOS command-line examples for testing HTTP endpoints (e.g., curl, wget).
  • Mention cross-platform certificate management tools (e.g., OpenSSL, certutil) and provide instructions for managing certificates on Linux.
  • Provide parity in authentication examples, such as how to use Basic or ClientCertificate authentication on Linux.
  • List alternative tools for API testing (e.g., Postman, curl) alongside Windows tools.
  • Avoid mentioning Windows tools exclusively or first; present cross-platform options together.
  • Clarify that the integration runtime can be hosted on Linux and provide relevant configuration guidance.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-office-365.md ...lob/main/articles/data-factory/connector-office-365.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. PowerShell is referenced for certificate conversion, and the only explicit example for converting certificates to base64 links to a PowerShell-based tutorial. The list of tools for pipeline creation includes Azure PowerShell before REST API and ARM templates, and no Linux-specific CLI (e.g., Azure CLI) or cross-platform alternatives are mentioned for key steps. There are no Linux shell or OpenSSL examples for certificate handling, and the documentation assumes familiarity with Windows-centric tools and workflows.
Recommendations
  • Add Linux shell (bash) and OpenSSL examples for certificate conversion, alongside the PowerShell example.
  • Include Azure CLI instructions for pipeline creation and management, not just Azure PowerShell.
  • When listing tools or SDKs, present cross-platform options (e.g., Azure CLI, Python SDK) before or alongside Windows-specific tools.
  • Explicitly mention that all steps can be performed on Linux and macOS, and provide links or examples for those platforms.
  • Review all referenced external articles and templates to ensure they are not Windows-only, or provide equivalent Linux/macOS alternatives.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-azure-table-storage.md ...articles/data-factory/connector-azure-table-storage.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias primarily in the authentication section for generating a Shared Access Signature (SAS). It provides only PowerShell commands (a Windows-centric tool) for generating SAS tokens, without offering equivalent CLI or scripting examples for Linux/macOS users. No Linux-native tools or cross-platform command-line examples (such as Azure CLI or REST API) are mentioned, and PowerShell is presented as the default method. This may hinder Linux users or those working in cross-platform environments.
Recommendations
  • Provide Azure CLI examples for generating SAS tokens, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include REST API examples for SAS generation, which are platform-agnostic.
  • When referencing command-line tools, mention both PowerShell and Azure CLI, and present them in parallel or with equal prominence.
  • Explicitly state that PowerShell is one option and provide guidance for users on other operating systems.
  • Review other sections for similar tool-specific instructions and ensure Linux parity throughout the documentation.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-file-system.md ...ob/main/articles/data-factory/connector-file-system.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows-first bias, with Windows file share patterns and escape characters (backslash) presented as defaults throughout. Powershell is referenced as the primary method for enabling local machine access, with no Linux CLI or shell alternatives. Windows-style paths (\\server\share) are used in examples, and instructions for Linux (Samba) are brief and secondary. There are no explicit Linux file share configuration or usage examples, and Linux tools or conventions are not discussed in detail.
Recommendations
  • Provide equivalent Linux examples for file share paths, using forward slashes and typical Linux mount points (e.g., /mnt/share).
  • Include Linux shell (bash) commands for enabling local access, alongside Powershell instructions.
  • Expand the Samba section with step-by-step guidance for setting up and connecting to Linux file shares.
  • Clarify escape character usage for Linux environments, noting differences from Windows.
  • Ensure all sample JSON and UI screenshots show both Windows and Linux path formats.
  • Mention and link to Linux-specific troubleshooting and best practices for file system connectors.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-netezza.md ...s/blob/main/articles/data-factory/connector-netezza.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by explicitly referencing Windows versions as prerequisites for the self-hosted integration runtime, while omitting mention of Linux support or instructions. There are no Linux-specific examples, nor is there guidance for installing the IBM Netezza ODBC driver or running the integration runtime on Linux. Windows is the only OS referenced for runtime setup, and no parity is provided for Linux users.
Recommendations
  • Explicitly state whether the self-hosted integration runtime and Netezza ODBC driver are supported on Linux, and provide supported Linux distributions if applicable.
  • Add Linux-specific installation instructions for the IBM Netezza ODBC driver, including package dependencies and configuration steps.
  • Include examples and screenshots for setting up the self-hosted integration runtime on Linux, alongside the Windows instructions.
  • Reference Linux tools and patterns (e.g., systemd for service management, shell commands for installation) where appropriate.
  • Ensure that prerequisites and supported platforms sections mention Linux equally with Windows, or clarify any limitations.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-oracle-responsys.md ...in/articles/data-factory/connector-oracle-responsys.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as a primary method for pipeline creation, referencing Azure portal UI (which is most commonly used on Windows), and omitting explicit Linux CLI or shell examples. There are no Linux-specific instructions or parity for command-line usage, and PowerShell is mentioned before REST API or ARM templates. No mention is made of Bash, Azure CLI, or Linux-based automation patterns.
Recommendations
  • Add explicit examples using Azure CLI (az) for pipeline and linked service creation, alongside PowerShell.
  • Include instructions or screenshots for using the Azure portal UI from Linux or cross-platform browsers.
  • Provide sample scripts for Linux shell environments (e.g., Bash) to complement PowerShell examples.
  • Mention cross-platform SDK usage (Python, .NET) with clear notes on Linux compatibility.
  • Ensure REST API and ARM template examples are presented before or alongside PowerShell, not after.
  • State that all features are available and supported on Linux, and clarify any platform-specific limitations.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-rest.md ...docs/blob/main/articles/data-factory/connector-rest.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 its recommendations for testing REST endpoints. It mentions Visual Studio and PowerShell's Invoke-RestMethod as example tools for validating API requests, with no mention of Linux-native or cross-platform alternatives. Windows tools are referenced first and exclusively in this context, potentially leaving Linux users without clear guidance. The rest of the documentation is platform-neutral, focusing on Azure Data Factory configuration and JSON examples.
Recommendations
  • Include Linux-native and cross-platform tools for REST API testing, such as curl, httpie, or Postman, alongside Visual Studio and PowerShell.
  • Rephrase tool recommendations to avoid listing Windows tools first or exclusively. For example: 'You can use tools like curl, httpie, PowerShell's Invoke-RestMethod, Visual Studio, or a web browser to validate.'
  • Add brief example commands for curl or httpie to demonstrate REST API testing on Linux.
  • Ensure screenshots and UI instructions do not assume a Windows environment unless strictly necessary.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sql-server.md ...lob/main/articles/data-factory/connector-sql-server.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas: authentication options and examples prioritize Windows authentication, troubleshooting and configuration steps exclusively reference Windows tools (SQL Server Management Studio, SQL Server Configuration Manager, Windows Firewall), and there are no Linux-specific instructions or examples for connecting to SQL Server or configuring the environment. Linux equivalents for remote access, firewall configuration, and service management are absent.
Recommendations
  • Add Linux-specific instructions and examples for connecting to SQL Server, including using tools like sqlcmd, Azure Data Studio, or ODBC.
  • Include troubleshooting steps for Linux environments, such as configuring SQL Server on Linux, managing firewall rules with iptables or firewalld, and enabling TCP/IP via mssql-conf.
  • Provide authentication examples relevant to Linux (e.g., using SQL authentication, Kerberos, or managed identity where supported).
  • Reference cross-platform tools (Azure Data Studio, sqlcmd) before or alongside Windows-only tools (SSMS, Configuration Manager).
  • Clearly indicate when a feature or step is Windows-only, and provide Linux alternatives where possible.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-file-system.md ...les/data-factory/connector-troubleshoot-file-system.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively referencing PowerShell for configuration steps and omitting any mention of Linux or cross-platform alternatives. The troubleshooting recommendation directs users to use PowerShell commands, with no equivalent instructions for Linux environments or shell scripting. This suggests an assumption that users are on Windows, potentially excluding Linux users from clear guidance.
Recommendations
  • Provide equivalent Linux instructions using bash or shell commands for configuring Self-hosted Integration Runtime (SHIR) file system access.
  • Mention cross-platform tools or clarify if the PowerShell steps can be run on Linux via PowerShell Core.
  • Explicitly state platform requirements or limitations for the troubleshooting steps.
  • Add examples or links for Linux users to ensure parity and inclusivity in troubleshooting guidance.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sap-business-warehouse.md ...icles/data-factory/connector-sap-business-warehouse.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 primarily in the prerequisites and troubleshooting sections. It references Windows-specific paths (e.g., %windir%\system32) for library installation and troubleshooting, and does not mention Linux equivalents or provide Linux-specific guidance. There are no examples or instructions for setting up the SAP NetWeaver library or troubleshooting on Linux-based Self-hosted Integration Runtime machines, nor are Linux file paths or commands provided.
Recommendations
  • Add instructions for installing SAP NetWeaver RFC SDK on Linux-based Self-hosted Integration Runtime machines, including typical file paths (e.g., /usr/lib, /opt/sap).
  • Include troubleshooting steps for Linux environments, such as verifying library placement and permissions.
  • Mention both Windows and Linux platforms explicitly when discussing prerequisites and supported environments.
  • Provide examples of environment variables and configuration relevant to Linux (e.g., LD_LIBRARY_PATH).
  • Ensure all dependency library references include both Windows and Linux file locations.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-ftp-sftp-http.md ...s/data-factory/connector-troubleshoot-ftp-sftp-http.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Windows-specific tools such as WinSCP are recommended for credential validation, and a third-party base64 tool is suggested without mention of Linux-native alternatives. While some Linux commands (e.g., openssl, ssh-keygen) are included, Windows tools and patterns are mentioned first or exclusively in some troubleshooting steps. There are no explicit Linux example workflows or tool recommendations for key validation, file transfer, or troubleshooting, and the documentation does not provide parity in example commands or tool references for Linux users.
Recommendations
  • Include Linux-native tool recommendations (e.g., FileZilla, command-line sftp, scp) alongside WinSCP for credential validation and file transfer troubleshooting.
  • Provide Linux shell command examples for base64 encoding (e.g., 'base64 < private_key_file > encoded.txt') and other relevant operations.
  • Ensure that troubleshooting steps reference both Windows and Linux tools and workflows, giving equal prominence to each.
  • Add explicit Linux example workflows for common troubleshooting scenarios, such as verifying credentials, transferring files, and checking permissions.
  • Where third-party tools are suggested, mention both web-based and command-line alternatives for Linux and Windows.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-rest.md ...n/articles/data-factory/connector-troubleshoot-rest.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias by referencing 'Command Prompt' as the environment for running curl, omitting Linux/macOS terminal examples. It also recommends Fiddler, a Windows-centric tool, without mentioning Linux alternatives. There are no Linux-specific troubleshooting patterns or parity in tool recommendations.
Recommendations
  • Include Linux/macOS terminal examples alongside Windows Command Prompt for curl usage.
  • Mention Linux-native troubleshooting tools (e.g., Wireshark, mitmproxy) as alternatives to Fiddler.
  • Use neutral language such as 'terminal' or 'shell' instead of 'Command Prompt' when describing command-line instructions.
  • Add explicit notes or examples for Linux users where command syntax or environment may differ.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-sap.md ...in/articles/data-factory/connector-troubleshoot-sap.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 guidance for SAP connectors in Azure Data Factory and Azure Synapse, but exclusively recommends using the PowerShell Test-NetConnection command to test connectivity. This command is only available on Windows, and no equivalent Linux or cross-platform example is provided. The troubleshooting steps assume a Windows environment and do not mention Linux tools or alternatives.
Recommendations
  • Include Linux equivalent commands, such as using 'nc', 'telnet', or 'curl' to test port connectivity (e.g., 'nc -zv <sap server> 3300').
  • Explicitly mention that the integration runtime can be installed on both Windows and Linux, if supported, and provide troubleshooting steps for both platforms.
  • Add a note clarifying which commands are platform-specific and offer alternatives for non-Windows users.
  • Where possible, use cross-platform tools or scripts in examples, or provide both Windows and Linux versions side-by-side.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-guide.md .../articles/data-factory/connector-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several ways. The FIPS troubleshooting section exclusively references Windows-specific paths and configuration files (e.g., C:\Program Files\Microsoft Integration Runtime, diawp.exe.config), with no mention of Linux equivalents or instructions for Linux-based self-hosted IR. All configuration and troubleshooting steps assume a Windows environment, and there are no examples or guidance for users running Self-hosted Integration Runtime on Linux. This may leave Linux users without clear instructions for resolving similar issues.
Recommendations
  • Include equivalent troubleshooting steps for Linux-based Self-hosted Integration Runtime, such as file paths, configuration file names, and commands.
  • Explicitly state whether FIPS issues and configuration changes apply to Linux environments, and provide Linux-specific guidance if applicable.
  • When referencing file paths or configuration changes, provide both Windows and Linux examples side by side.
  • Audit other troubleshooting steps to ensure they are not Windows-centric and add Linux alternatives where needed.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-sharepoint-online-list.md ...ctory/connector-troubleshoot-sharepoint-online-list.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 macOS users, nor are alternative cross-platform tools or approaches mentioned. The troubleshooting steps assume access to Windows environments and do not address how users on other operating systems can perform the same tasks.
Recommendations
  • Provide equivalent troubleshooting steps using cross-platform tools, such as Azure CLI or Microsoft Graph API, which are available on Linux and macOS.
  • Include examples for Linux and macOS environments, or clarify platform requirements at the start of the troubleshooting section.
  • Mention and link to any web-based or REST API alternatives for managing SharePoint Online settings.
  • If PowerShell is required, note that PowerShell Core is available on Linux/macOS and provide installation and usage instructions for those platforms.
  • Clearly indicate when a step is Windows-specific and offer guidance for users on other operating systems.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-upgrade-guidance.md ...in/articles/data-factory/connector-upgrade-guidance.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell script examples for programmatically finding impacted objects, with no mention of Linux-friendly alternatives such as Bash, Azure CLI, or Python. This creates a Windows bias by assuming users are on Windows or using PowerShell, and omits guidance for Linux or cross-platform users.
Recommendations
  • Include equivalent examples using Azure CLI, Bash, or Python for Linux and cross-platform users.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell must be used.
  • Add notes or links to cross-platform scripting options for Azure Data Factory management.
  • Ensure future documentation provides both Windows and Linux approaches side-by-side.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-sample-script.md ...ctory/continuous-integration-delivery-sample-script.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 using Azure PowerShell and PowerShell scripts for all examples and instructions. There are no references to Bash, Azure CLI, or Linux-native scripting approaches. The only tool mentioned for script execution is Azure PowerShell, and all YAML pipeline examples use the AzurePowerShell task. No Linux or cross-platform alternatives are provided or discussed.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for pre- and post-deployment tasks.
  • Include instructions for running scripts on Linux agents in Azure DevOps pipelines.
  • Mention cross-platform compatibility considerations, such as using PowerShell Core or Bash.
  • Provide sample YAML pipeline tasks using the AzureCLI@2 task for Linux environments.
  • Clarify which scripts and approaches are supported on both Windows and Linux agents.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-if-condition-activity.md ...les/data-factory/control-flow-if-condition-activity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides detailed PowerShell command examples for running Azure Data Factory pipelines, assumes file paths in Windows format (e.g., C:\ADF), and references a Windows-centric workflow. There are no equivalent examples for Linux or cross-platform CLI tools (such as Azure CLI or Bash), nor guidance for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI (az datafactory) examples for all PowerShell commands, with sample Bash scripts and Linux/macOS file paths.
  • Include notes or sections on how to run the pipeline from Linux/macOS, including any prerequisites or differences.
  • Use neutral file path examples (e.g., /home/user/ADF or ./ADF) alongside Windows paths.
  • Explicitly mention cross-platform support and link to relevant documentation for Linux/macOS users.
  • Consider reordering examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-automate-azure-pipelines.md ...ntinuous-integration-delivery-automate-azure-pipelines.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 bias toward Windows environments, primarily through exclusive use of PowerShell for scripting and automation tasks, references to Windows-centric tools and patterns, and a lack of equivalent Linux/bash examples. All automation and scripting instructions are provided using PowerShell, with no mention of Bash, CLI, or cross-platform alternatives. The documentation assumes the reader is using Windows or PowerShell, and does not provide guidance for users on Linux or macOS.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for deployment and trigger management tasks.
  • Explicitly mention cross-platform compatibility of Azure Pipelines agents and tasks, and clarify when PowerShell Core (which runs on Linux/macOS) can be used.
  • Add instructions for installing and using Azure CLI on Linux/macOS, and show how to perform key operations (e.g., stopping/starting triggers) using CLI commands.
  • Ensure that references to script files and automation steps include both PowerShell and Bash/CLI alternatives, or note when a step is platform-agnostic.
  • Review all task instructions to confirm that Linux users can follow them without needing to switch to Windows or PowerShell.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery.md ...ticles/data-factory/continuous-integration-delivery.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by exclusively recommending and referencing PowerShell scripts for pre- and post-deployment tasks, with no mention of Bash, shell scripts, or cross-platform alternatives. The provided script is a .ps1 PowerShell script, and there are explicit instructions to use PowerShell Core in Azure DevOps tasks. There are no Linux or macOS-specific examples or guidance, and no mention of equivalent tools or patterns for non-Windows environments.
Recommendations
  • Provide equivalent Bash or shell script examples for pre- and post-deployment tasks, or clarify how to adapt the PowerShell script for Linux/macOS environments.
  • Explicitly mention that PowerShell Core is cross-platform, and provide tested instructions for running the script on Linux/macOS agents.
  • Include references to common Linux tools (e.g., Azure CLI, Bash) where appropriate, and show parity in examples.
  • Reorder or balance documentation sections so that Linux/macOS options are mentioned alongside Windows/PowerShell, not only after or as an afterthought.
  • Add a note or section addressing cross-platform CI/CD agent support, including any limitations or best practices for Linux-based agents.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-until-activity.md ...n/articles/data-factory/control-flow-until-activity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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. All command-line examples use Azure PowerShell, with explicit references to Windows file paths (e.g., C:\ADF), and no mention of Linux or cross-platform alternatives such as Azure CLI or Bash. The tutorial and walkthroughs are centered around PowerShell, and there are no instructions or examples for Linux users, nor any guidance for running these pipelines from non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, with sample Bash scripts and Linux-friendly file paths.
  • Include notes or sections on how to run pipelines and manage resources from Linux/macOS environments.
  • Use cross-platform file path conventions in examples, or show both Windows and Linux paths.
  • Explicitly mention that Azure Data Factory and Synapse can be managed from any OS, and link to cross-platform tooling documentation.
  • Balance the documentation by alternating or combining PowerShell and Azure CLI/Bash examples in tutorials and walkthroughs.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-web-activity.md ...ain/articles/data-factory/control-flow-web-activity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias primarily in the authentication section, where only a PowerShell snippet is provided for base64-encoding a PFX certificate file, with no equivalent Linux or cross-platform example. The mention of 'your favorite utility' for PFX conversion is vague and does not offer Linux-specific guidance. No Linux shell (e.g., Bash/OpenSSL) examples are given for certificate handling, and the only concrete tooling instruction is Windows-centric.
Recommendations
  • Add Linux/Bash/OpenSSL examples for base64-encoding PFX files and certificate conversion.
  • Explicitly mention cross-platform tools (e.g., OpenSSL) for certificate handling and provide command-line examples for both Windows and Linux.
  • Where PowerShell is used, also provide equivalent Bash or Linux shell commands.
  • Clarify that the process can be performed on both Windows and Linux, and link to relevant documentation for Linux users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-wait-activity.md ...in/articles/data-factory/control-flow-wait-activity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for the Wait activity in Azure Data Factory and Synapse Analytics demonstrates Windows bias by providing sample PowerShell commands and referencing a PowerShell-based tutorial, with no equivalent examples or walkthroughs for Linux users (e.g., Bash, Azure CLI). Windows tooling is mentioned exclusively, and Linux alternatives are missing.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts for running pipelines and managing Data Factory resources.
  • Reference tutorials for creating and running pipelines on Linux/macOS platforms, not just Windows/PowerShell.
  • Ensure that step-by-step instructions are available for both Windows and Linux environments, ideally side-by-side.
  • Mention cross-platform tools (such as Azure CLI) before or alongside Windows-specific tools like PowerShell.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/copy-activity-overview.md ...b/main/articles/data-factory/copy-activity-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page for Azure Data Factory & Synapse Copy activity demonstrates a Windows bias in several ways. SQL Server and PowerShell are mentioned as primary examples and tools, with no equivalent Linux or cross-platform examples provided. The 'Related content' section features a PowerShell tutorial and SQL Server scenarios, both of which are traditionally Windows-centric. There is a lack of explicit Linux or open-source tool examples, and no mention of Linux-specific patterns or shell scripting alternatives.
Recommendations
  • Add Linux-based examples, such as copying data from PostgreSQL, MySQL, or using Linux file systems.
  • Include tutorials or quickstarts that use Bash, shell scripts, or other Linux-native tools instead of PowerShell.
  • Provide parity in connector documentation, ensuring that Linux and open-source data sources and sinks are equally represented.
  • Mention cross-platform considerations when discussing self-hosted integration runtimes, including installation and usage on Linux systems.
  • Balance SQL Server examples with open-source database examples (e.g., PostgreSQL, MySQL) and highlight their usage in Copy activity pipelines.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-deploy-packages.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-deploy-packages.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows-centric tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and running SSIS packages. There are no examples or mentions of Linux-compatible alternatives or cross-platform deployment methods. Windows tools and patterns are presented as the default or only option, with no guidance for Linux users.
Recommendations
  • Include information about cross-platform or Linux-compatible SSIS deployment tools, if available.
  • Explicitly state platform requirements and limitations for each tool (e.g., SSDT and SSMS are Windows-only).
  • Provide guidance or workarounds for Linux users, such as using Azure portal, REST APIs, or Data Factory pipeline activities.
  • Add examples or references for deploying and running SSIS packages from non-Windows environments, if supported.
  • Clarify whether dtutil and AzureDTExec can be run in Linux containers or via Mono/.NET Core, and provide instructions if possible.
GitHub Create Pull Request
← Previous Page 13 of 40 Next →