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 976-1000 of 1000 flagged pages
Data Factory Copy and transform data from Microsoft 365 (Office 365) ...lob/main/articles/data-factory/connector-office-365.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias, particularly in the section on converting certificates to base64, where only a PowerShell/Windows-centric method is referenced. The linked article for certificate conversion is PowerShell-specific, and no Linux/macOS alternatives are mentioned. Additionally, while Azure PowerShell is listed as a supported tool, there is no explicit mention or example of using Linux-native tools for certificate handling or automation, and no parity guidance for non-Windows environments.
Recommendations
  • Provide Linux/macOS command-line examples (e.g., using openssl and base64) for converting certificates to base64, alongside the PowerShell method.
  • Explicitly mention that all SDKs and REST APIs are cross-platform, and provide links or notes for Linux/macOS users where relevant.
  • When referencing external articles or templates, ensure that at least one is platform-agnostic or includes Linux/macOS instructions.
  • Add a note or section on how to perform prerequisite steps (such as certificate conversion and Azure CLI usage) on Linux/macOS.
  • Where Azure PowerShell is mentioned, also mention Azure CLI as a cross-platform alternative.
GitHub Create Pull Request
Data Factory Create an Azure-SSIS integration runtime via Azure portal ...actory/create-azure-ssis-integration-runtime-portal.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias. The only command-line automation example referenced is Azure PowerShell, with no mention of Azure CLI or Bash alternatives. The use of UNC paths and references to SSMS (SQL Server Management Studio) and Windows authentication patterns further reinforce Windows-centric workflows. Windows tools and terminology (e.g., UNC paths, SSMS, PowerShell) are mentioned without Linux/macOS equivalents or alternatives, and Windows-specific instructions (such as configuring backup storage redundancy via PowerShell) are provided before considering cross-platform options.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for command-line automation and configuration tasks.
  • Clarify how Linux/macOS users can perform equivalent operations, especially for tasks currently described with Windows tools (e.g., UNC paths, SSMS).
  • Include references to cross-platform database management tools (such as Azure Data Studio) where SSMS is mentioned.
  • Explicitly note platform compatibility for authentication and file access patterns, and provide guidance for Linux/macOS users where workflows differ.
  • Reorder examples so that platform-neutral or cross-platform methods are presented before Windows-specific ones.
GitHub Create Pull Request
Data Factory Introduction to Azure Data Factory ...e-docs/blob/main/articles/data-factory/introduction.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for Azure Data Factory shows mild Windows bias. PowerShell is mentioned as a primary monitoring tool, and the 'Related content' section lists PowerShell before other automation/programming options. There is no explicit mention of Linux/macOS CLI tools or shell scripting, nor are Linux-specific examples or tools referenced. The documentation assumes familiarity with Windows-centric tools and patterns, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit references to cross-platform CLI tools (e.g., Azure CLI) and provide examples for Linux/macOS environments.
  • Include shell scripting (bash) examples alongside PowerShell, especially for monitoring and automation tasks.
  • Ensure that automation and scripting sections do not prioritize Windows tools (like PowerShell) over platform-neutral or Linux-friendly options.
  • Clarify that Azure Data Factory can be managed from any OS via REST API, Azure CLI, and SDKs, and provide links to relevant documentation.
  • In 'Related content', list platform-neutral options (REST, Python, Azure CLI) before Windows-specific ones like PowerShell.
GitHub Create Pull Request
Data Factory Create an Azure Data Factory using Bicep ...s/data-factory/quickstart-create-data-factory-bicep.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows a mild Windows bias: it references Notepad as the example text editor, lists Azure PowerShell alongside Azure CLI throughout, and sometimes presents PowerShell examples before or equally with CLI. There are no explicit Linux/macOS command-line or tool references, and no mention of Linux-native editors or workflows. However, the use of Azure CLI (which is cross-platform) mitigates the impact for non-Windows users.
Recommendations
  • When suggesting a text editor, mention cross-platform options (e.g., 'a text editor such as Notepad (Windows), TextEdit (macOS), or nano/vi (Linux)').
  • In code tabs, consider listing Azure CLI first, as it is cross-platform, and clarify that PowerShell is primarily for Windows (or PowerShell Core for cross-platform).
  • Explicitly state that all CLI commands work on Linux/macOS and Windows.
  • Add notes or examples for Linux/macOS users where file paths or tool usage may differ.
  • Avoid referencing Windows-specific tools (like Notepad) without alternatives.
GitHub Create Pull Request
Data Factory Quickstart: Create an Azure Data Factory using Python .../data-factory/quickstart-create-data-factory-python.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation shows minor Windows bias. The instructions for creating the input file explicitly mention launching Notepad (a Windows-only application), and the use of Azure Storage Explorer is suggested multiple times, which is a cross-platform tool but often associated with Windows. The phrase 'Open a terminal or command prompt with administrator privileges' lists Windows terminology first. No Linux/macOS-specific instructions or examples are provided, but the Python code and Azure SDK usage are platform-agnostic.
Recommendations
  • Replace 'Launch Notepad' with 'Use a text editor (such as Notepad on Windows, TextEdit on macOS, or nano/vim on Linux) to create input.txt.'
  • When mentioning terminals, use 'Open a terminal or command prompt' and clarify that on Linux/macOS, a standard terminal is sufficient.
  • Explicitly state that Azure Storage Explorer is available for Windows, macOS, and Linux, and provide links or instructions for all platforms.
  • Add notes or examples for Linux/macOS users where file creation or command-line usage may differ.
  • Consider listing platform-neutral instructions first, or in parallel, to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Data Factory Transform data ...docs/blob/main/articles/data-factory/transform-data.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page is largely platform-neutral in its main content, referencing both Windows and Linux-based HDInsight clusters and focusing on cloud-based transformation activities. However, there are subtle signs of Windows bias: Windows is mentioned before Linux in cluster descriptions, the related tutorial specifically references PowerShell (a Windows-centric tool), and .NET custom activities are highlighted, which are more common in Windows environments.
Recommendations
  • Ensure Linux is mentioned before or alongside Windows when listing supported platforms (e.g., 'Windows/Linux-based HDInsight cluster').
  • Provide equivalent Linux/macOS command-line examples (e.g., Bash, CLI) in tutorials and related content, not just PowerShell.
  • Include examples or references for custom activities using cross-platform runtimes (e.g., Python, Java) in addition to .NET.
  • In the 'Related content' section, add tutorials using Bash or Azure CLI for Spark transformation, not just PowerShell.
GitHub Create Pull Request
Data Factory Troubleshoot the REST connector ...n/articles/data-factory/connector-troubleshoot-rest.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias by referencing 'Command Prompt' as the environment for running curl and recommending Fiddler (a Windows-only tool) for troubleshooting SSL issues. There are no explicit Linux/macOS examples or mentions of equivalent Linux tools/environments.
Recommendations
  • Mention that curl can be run in any terminal, including Linux and macOS, not just Windows Command Prompt.
  • Provide example curl commands for Bash or zsh shells (Linux/macOS).
  • Suggest cross-platform alternatives to Fiddler, such as mitmproxy or Wireshark, for SSL troubleshooting.
  • Avoid implying Windows is the default environment by using neutral language like 'terminal' instead of 'Command Prompt'.
GitHub Create Pull Request
Data Factory Transform data ...docs/blob/main/articles/data-factory/transform-data.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation is generally cross-platform, referencing both Windows and Linux-based HDInsight clusters and Spark environments. However, there is subtle Windows bias: the only tutorial linked is 'transform data using Spark (PowerShell)', which prioritizes Windows/PowerShell tooling over Linux/bash alternatives. No explicit Linux/macOS examples or CLI references are provided, and PowerShell is implicitly presented as the default automation tool.
Recommendations
  • Add equivalent tutorials using Bash or Azure CLI for Spark and other transformation activities.
  • Explicitly mention Linux/macOS compatibility and provide examples for those platforms where relevant.
  • Where PowerShell is referenced, offer parallel instructions for Bash or Azure CLI.
  • Ensure that links to tutorials and examples are balanced between Windows and Linux/macOS tooling.
GitHub Create Pull Request
Data Factory Compute environments .../main/articles/data-factory/compute-linked-services.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally cross-platform, with most examples and configurations explicitly referencing Linux-based clusters and generic Azure services. However, there is mild Windows bias in a few areas: Windows node OS is mentioned as an option, and references to Windows-specific tools (such as Microsoft Azure Storage Explorer) are present. Additionally, PowerShell cmdlets (New-AzBatchAccount, New-AzBatchPool) are referenced before alternatives, and links to Windows-centric articles are provided before mentioning portal or REST/API methods. No critical sections are Windows-only, and all main examples use Linux clusters.
Recommendations
  • When mentioning tools for managing Azure resources (e.g., deleting blob containers), include cross-platform alternatives such as Azure CLI, azcopy, or REST API, not just Microsoft Azure Storage Explorer.
  • When referencing PowerShell cmdlets for Azure Batch, also mention Azure CLI and portal methods, and provide links to their documentation.
  • Where OS type is configurable, clarify Linux is the default and recommended, and provide parity in documentation for both Linux and Windows (if supported).
  • If referencing Windows-specific patterns (e.g., CMDLETs/APIs), clarify their applicability to Linux/macOS users and provide equivalent cross-platform instructions.
GitHub Create Pull Request
Data Factory Copy and transform data from and to a REST endpoint ...docs/blob/main/articles/data-factory/connector-rest.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates mild Windows bias, notably in the 'TIP' section recommending Visual Studio and PowerShell's Invoke-RestMethod as tools for testing REST requests, with no mention of Linux/macOS alternatives. Windows tools are mentioned first and exclusively, which may cause friction for users on other platforms. The rest of the documentation is platform-neutral, focusing on Azure portal UI and JSON configuration.
Recommendations
  • Include Linux/macOS command-line tools (e.g., curl, httpie) alongside PowerShell and Visual Studio when suggesting ways to test REST APIs.
  • List cross-platform tools first or together, rather than Windows-specific tools.
  • Add example commands for curl or httpie to demonstrate REST API testing for non-Windows users.
  • Clarify that all configuration and examples are platform-agnostic unless otherwise noted.
GitHub Create Pull Request
Data Factory Troubleshoot the FTP, SFTP, and HTTP connectors ...s/data-factory/connector-troubleshoot-ftp-sftp-http.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page generally provides cross-platform troubleshooting guidance for FTP, SFTP, and HTTP connectors in Azure Data Factory and Synapse. However, there are subtle Windows biases: WinSCP (a Windows-only tool) is recommended for credential verification, and the only third-party base64 tool linked is a web service, with no mention of Linux CLI alternatives. In the code examples, Linux commands (openssl, ssh-keygen) are present, but the order of tool recommendations sometimes favors Windows. The HTTP status code documentation link points to IIS (Windows web server) documentation, which may not be relevant for Linux users.
Recommendations
  • When recommending tools for credential verification, include cross-platform options (e.g., FileZilla, Cyberduck) alongside WinSCP.
  • For base64 encoding, provide Linux/macOS CLI examples (e.g., 'base64 < keyfile > keyfile.b64') in addition to web tools.
  • When linking to HTTP status code documentation, use a vendor-neutral or RFC reference instead of IIS-specific docs.
  • Ensure that Linux/macOS examples are shown alongside or before Windows-specific ones, especially for common troubleshooting tasks.
GitHub Create Pull Request
Data Factory Copy activity ...b/main/articles/data-factory/copy-activity-overview.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page does not provide explicit Windows or PowerShell-heavy examples, nor does it mention Windows-specific tools. However, in the 'Related content' section, the only on-premises/hybrid example is 'Copy data from a SQL Server database to Azure' using PowerShell, which is typically associated with Windows environments. There are no Linux/macOS-specific examples, nor is there mention of Linux file systems or tools in example scenarios. The documentation generally avoids OS-specific instructions, but the example selection and tutorial links lean toward Windows-first scenarios.
Recommendations
  • Add Linux/macOS-specific examples, such as copying data from a Linux file system or using SFTP/HDFS as a source.
  • Include tutorials or quickstarts that demonstrate hybrid copy scenarios from Linux servers or file systems.
  • Ensure parity in example coverage for both Windows and Linux environments, especially in the 'Related content' section.
  • Explicitly mention that the Copy activity supports Linux/macOS file systems and provide configuration guidance if any differences exist.
GitHub Create Pull Request
Data Factory Introduction to Azure Data Factory ...e-docs/blob/main/articles/data-factory/introduction.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for Azure Data Factory is generally cross-platform, but there is a subtle Windows bias. PowerShell is mentioned as a primary monitoring tool and is listed before other automation options. The related content section highlights PowerShell as a quickstart, and there is no equivalent emphasis on Bash, CLI, or Linux-native tools. Windows-centric tools and patterns (PowerShell, Azure portal) are referenced before alternatives, and Linux/macOS users may need to infer parity or look elsewhere for native examples.
Recommendations
  • Add explicit Bash/Azure CLI examples and quickstarts alongside PowerShell, especially for monitoring and automation tasks.
  • Mention Linux/macOS compatibility and provide links to platform-specific guides.
  • List cross-platform tools (Python, REST API, Azure CLI) before or alongside Windows-centric tools in related content.
  • Clarify that PowerShell is available cross-platform, or recommend alternatives for Linux/macOS users.
  • Include a note or section on how Linux/macOS users can perform equivalent tasks, especially for scripting and automation.
GitHub Create Pull Request
Data Factory Quickstart: Create an Azure Data Factory using Python .../data-factory/quickstart-create-data-factory-python.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exhibits minor Windows bias by instructing users to 'Launch Notepad' to create the input file, which is a Windows-specific application, and by referencing 'terminal or command prompt with administrator privileges' without clarifying Linux/macOS equivalents. There are no explicit Linux/macOS instructions or examples for these steps, and the use of Azure Storage Explorer (a cross-platform tool) is mentioned neutrally. No PowerShell or Windows-only tools are required, and the Python code itself is cross-platform.
Recommendations
  • Replace 'Launch Notepad' with 'Use a text editor (such as Notepad on Windows, TextEdit on macOS, or nano/vim on Linux) to create input.txt.'
  • Clarify that 'terminal or command prompt' means Command Prompt/PowerShell on Windows, Terminal on macOS/Linux.
  • Explicitly state that all Python code and Azure SDK instructions work on Linux and macOS as well as Windows.
  • Add a note confirming Azure Storage Explorer is available for Windows, macOS, and Linux.
  • Where administrator privileges are mentioned, clarify if/when they are required on Linux/macOS (e.g., use 'sudo' if needed).
GitHub Create Pull Request
Data Factory Transform data using Hadoop Hive activity ...icles/data-factory/transform-data-using-hadoop-hive.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references a tutorial that is explicitly titled 'Tutorial: transform data (Spark Powershell)', which suggests a Windows/Powershell-centric approach for introductory learning. No Linux or cross-platform command-line examples are provided, nor is there mention of Linux tools or shell usage. The main content focuses on UI-based configuration and JSON syntax, which is platform-neutral, but the onboarding path is Windows-first.
Recommendations
  • Provide equivalent Linux/macOS onboarding tutorials, such as using Bash or CLI for Spark/Hive activities.
  • Reference cross-platform command-line tools (e.g., Azure CLI, Bash scripts) alongside Powershell.
  • Clarify that the pipeline and Hive activity configuration is platform-agnostic, and link to Linux/macOS-specific guides where available.
  • Avoid referencing Windows/Powershell tutorials as the sole prerequisite; offer alternatives for non-Windows users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/airflow-import-dags-blob-storage.md ...icles/data-factory/airflow-import-dags-blob-storage.md
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific command-line examples or tooling, but it also does not mention or demonstrate how to upload files to Azure Blob Storage from Linux or macOS environments. The only upload reference points to a portal-based guide, which is platform-agnostic but omits parity for CLI-based workflows common on Linux.
Recommendations
  • Add examples for uploading DAG files to Azure Blob Storage using cross-platform tools such as Azure CLI (az storage blob upload) and/or Python SDK, with explicit command-line examples that work on Linux, macOS, and Windows.
  • Include a section or note highlighting that the upload process can be performed from any OS, and provide links or code snippets for both GUI (portal) and CLI methods.
  • If screenshots or UI steps are shown, clarify that the process is not limited to Windows and that Linux users can follow equivalent steps using the Azure CLI or other supported tools.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-linked-templates.md ...ry/continuous-integration-delivery-linked-templates.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not explicitly show Windows bias in terms of mentioning Windows tools, PowerShell, or Windows-first patterns. However, it lacks any platform-specific examples or guidance, and does not provide Linux-specific instructions or examples for handling linked Resource Manager templates in CI/CD pipelines. This absence can be considered a subtle bias, as it assumes platform neutrality but does not confirm Linux parity or address potential differences in scripting, tooling, or environment setup.
Recommendations
  • Add explicit examples for both Windows (e.g., PowerShell, Azure CLI on Windows) and Linux (e.g., Bash, Azure CLI on Linux) for uploading linked templates and managing SAS tokens.
  • Include notes or sections on any platform-specific considerations (such as file path formats, environment variable handling, or script execution differences) that may affect Linux users.
  • Provide sample scripts or commands for common Linux CI/CD environments (e.g., Azure Pipelines with Ubuntu agents, GitHub Actions runners on Linux) to demonstrate parity.
  • Clarify that the instructions are platform-agnostic if that is the case, or explicitly state any limitations or differences for Linux users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/airflow-import-dags-blob-storage.md ...icles/data-factory/airflow-import-dags-blob-storage.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific commands or examples, but it also does not mention or demonstrate how to upload files to Azure Blob Storage using command-line tools or scripts. The only reference for uploading files is a link to a portal-based quickstart, which is typically Windows-centric and GUI-based. There are no examples for Linux users (e.g., using azcopy, Azure CLI, or Python scripts), which may leave Linux users without clear guidance.
Recommendations
  • Add explicit examples for uploading files to Azure Blob Storage using cross-platform tools such as Azure CLI, azcopy, or Python scripts.
  • Include both GUI (portal) and command-line instructions, making it clear which methods are OS-agnostic.
  • Where possible, provide sample commands for both Windows and Linux/macOS terminals to ensure parity.
  • Mention that the Azure portal is accessible from any OS, but also highlight CLI alternatives for users who prefer or require command-line operations.
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
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation page for Azure Data Factory's Copy activity does not display overt Windows bias in terms of language, tools, or ordering of examples. However, it lacks any platform-specific examples or instructions, such as how to set up or use the self-hosted integration runtime on Linux, or how to perform related tasks from a Linux environment. The only platform-specific reference in the 'Related content' section is a tutorial for hybrid copy using PowerShell, which is primarily a Windows tool, with no Linux or cross-platform equivalent tutorial linked.
Recommendations
  • Add explicit examples or references for Linux environments, such as how to install and configure the self-hosted integration runtime on Linux.
  • Include links to tutorials or quickstarts that use Linux-native tools (e.g., Bash, shell scripts) or cross-platform approaches (e.g., Azure CLI).
  • In the 'Related content' section, balance PowerShell/Windows-focused tutorials with Linux-focused or cross-platform guides.
  • Wherever platform-specific instructions are needed (e.g., setting up integration runtime, troubleshooting), provide both Windows and Linux steps or clearly indicate cross-platform compatibility.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-informix.md .../blob/main/articles/data-factory/connector-informix.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation assumes the use of a 'Self-hosted Integration Runtime machine' and instructs users to download and install the Informix 64-bit Client SDK to set up an ODBC connection, but does not specify or provide guidance for Linux environments. There are no explicit references to Windows, but the lack of Linux-specific instructions or examples (such as how to install the Informix Client SDK or configure ODBC on Linux) suggests a bias toward Windows environments.
Recommendations
  • Add explicit instructions for setting up the Informix Client SDK and ODBC connections on Linux-based Integration Runtime hosts, including package names, installation commands, and configuration file locations.
  • Include Linux-specific examples for configuring DSNs and environment variables.
  • Clarify in the prerequisites section that both Windows and Linux are supported, and provide links or references to official IBM documentation for Linux installation.
  • If there are limitations or differences in Linux support, document them clearly.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sftp.md ...docs/blob/main/articles/data-factory/connector-sftp.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation is largely cross-platform and neutral, but there is a subtle Windows bias in the SSH key conversion guidance: it mentions only the PuTTY tool (a Windows utility) for converting PPK to OpenSSH format, without referencing Linux or macOS alternatives. Additionally, the only explicit file path example for private keys uses a Windows-style path (D:\privatekey_openssh), with no Linux-style path shown. There are no PowerShell or Windows command-line examples, but the implicit assumption of Windows tooling and paths may disadvantage Linux users.
Recommendations
  • When mentioning conversion from PPK to OpenSSH format, include Linux/macOS alternatives such as 'use the ssh-keygen tool on Linux/macOS to convert keys' or provide a command-line example.
  • Provide both Windows and Linux-style file path examples for properties like privateKeyPath (e.g., 'D:\privatekey_openssh' and '/home/user/.ssh/id_rsa').
  • If referencing tools, mention cross-platform or platform-specific options equally, and avoid assuming the user is on Windows.
  • Consider adding a note or section clarifying that all features and configuration steps are supported on both Windows and Linux self-hosted integration runtimes, if applicable.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-azure-data-lake.md ...data-factory/connector-troubleshoot-azure-data-lake.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not display overt Windows bias such as PowerShell-heavy examples or exclusive mention of Windows tools. However, it references 'network monitor (netmon) trace' for troubleshooting, which is a Windows-specific tool, and does not provide equivalent instructions or tool suggestions for Linux environments. There are no command-line examples (Windows or Linux), but the troubleshooting steps assume familiarity with Windows-centric tooling.
Recommendations
  • When suggesting the use of 'network monitor (netmon) trace', also mention equivalent Linux tools such as 'tcpdump' or 'Wireshark', and provide brief instructions or links for capturing network traces on Linux.
  • Where troubleshooting steps require system-level diagnostics, ensure both Windows and Linux approaches are described.
  • Review the documentation for any other implicit assumptions of a Windows environment and add Linux alternatives where appropriate.
  • If providing JSON configuration or code snippets, clarify that these are platform-agnostic, or note any platform-specific considerations.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/format-delimited-text.md ...ob/main/articles/data-factory/format-delimited-text.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page exhibits a subtle 'windows_first' bias, primarily in the default values and terminology for row delimiters (e.g., '\r\n' as the default for writing, which is the Windows line ending). There is also a reference to file encodings with 'WINDOWS-' prefixes and a link to a .NET (Windows-centric) API for compression levels. However, there are no explicit Windows-only tools, PowerShell examples, or exclusive mention of Windows patterns. Linux/Unix equivalents are not omitted, but Windows conventions are presented as defaults or primary references.
Recommendations
  • Explicitly mention both Windows (\r\n) and Unix/Linux (\n) line endings as equally supported and clarify when each is used.
  • Provide examples or notes for common Linux/Unix usage patterns (e.g., using '\n' as a row delimiter, or file naming conventions).
  • When listing encodings, clarify that 'WINDOWS-' encodings are for compatibility and mention Linux/Unix equivalents.
  • Where documentation links to Windows/.NET APIs (e.g., compression), also reference cross-platform or Linux-relevant documentation if available.
  • Add a short section or note on cross-platform considerations, especially for users moving files between Windows and Linux environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/format-json.md ...re-docs/blob/main/articles/data-factory/format-json.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation page is largely platform-neutral and does not provide OS-specific examples or instructions. However, there is a subtle Windows bias in the encodingName property list, which includes several 'WINDOWS-xxxx' encodings and many IBM codepages, but does not explicitly mention Linux/Unix-specific encodings or reference their usage. Additionally, the only external reference for compression level points to the .NET API documentation, which is more familiar to Windows users.
Recommendations
  • When listing encoding options, clarify that the 'WINDOWS-xxxx' encodings are supported cross-platform and mention common Linux/Unix encodings (such as 'UTF-8', 'ISO-8859-1', etc.) explicitly as being supported.
  • Where external documentation is referenced (such as compression levels), provide links or context for equivalent concepts/tools on Linux (e.g., reference gzip/bzip2 CLI tools or man pages).
  • If mentioning codepages or encodings, briefly note their typical platform associations (e.g., 'WINDOWS-1252 (common on Windows), ISO-8859-1 (common on Linux/Unix)'), to help users from all platforms understand applicability.
  • If relevant, add examples or notes for using JSON files and compression with Linux tools (e.g., using jq, gzip, tar) in the context of Azure Data Factory pipelines.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/sap-change-data-capture-prepare-linked-service-source-dataset.md ...nge-data-capture-prepare-linked-service-source-dataset.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not display explicit Windows bias in terms of command-line examples, tools, or terminology. However, it omits any mention of Linux or cross-platform considerations for the self-hosted integration runtime, which is a critical component that can run on both Windows and Linux. There are no examples, screenshots, or instructions that clarify platform-specific steps or requirements, potentially leaving Linux users without guidance.
Recommendations
  • Add a section clarifying that the self-hosted integration runtime can be installed and run on both Windows and Linux, with links to relevant installation guides for each platform.
  • Include platform-specific notes or screenshots where differences exist (e.g., service installation, runtime configuration).
  • If any troubleshooting or log collection steps are referenced (such as in the related content), ensure Linux paths and commands are included alongside Windows equivalents.
  • Explicitly state that the instructions are platform-agnostic, or provide parallel instructions for both Windows and Linux where applicable.
GitHub Create Pull Request
← Previous Page 40 of 40 Next →