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 276-300 of 1000 flagged pages
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/monitor-programmatically.md ...main/articles/data-factory/monitor-programmatically.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 exhibits a Windows bias by providing REST API examples exclusively in PowerShell, using Windows-specific tools and patterns (e.g., Invoke-RestMethod, Start-Sleep), and not offering equivalent Linux/bash/cURL examples. PowerShell is featured both in its own section and as the only scripting example for REST API usage, with no mention of Linux-native alternatives. This may disadvantage Linux users who expect bash or cURL examples for REST API calls.
Recommendations
  • Add REST API examples using bash and cURL to demonstrate parity for Linux users.
  • Include notes or code samples for Linux shell equivalents (e.g., using curl, jq, sleep) wherever PowerShell scripts are shown.
  • Reorder or balance examples so that Windows and Linux approaches are presented equally, or clarify which examples are platform-specific.
  • Explicitly mention cross-platform SDK usage and provide guidance for running scripts on both Windows and Linux environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/transform-data.md ...docs/blob/main/articles/data-factory/transform-data.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 Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. Windows is mentioned first in several places (e.g., 'Windows/Linux-based HDInsight cluster'), and SQL Server (a Windows-centric technology) is the only example given for stored procedure activities. The only tutorial linked is Spark with PowerShell, a Windows-specific tool, with no Linux/bash equivalent. There is a lack of Linux-specific examples or parity in tooling references.
Recommendations
  • When listing supported platforms (e.g., HDInsight clusters), alternate or randomize the order (e.g., 'Linux/Windows-based') or mention Linux first in some places.
  • Provide examples and tutorials using Linux-native tools (e.g., Bash, shell scripts) alongside PowerShell examples.
  • Include references to cross-platform or Linux-preferred database engines (e.g., PostgreSQL, MySQL) in addition to SQL Server for stored procedure activities.
  • Add explicit Linux usage scenarios and sample commands/scripts where applicable.
  • Ensure that tutorials are available for both PowerShell and Bash/CLI, and link to both.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-enable-remote-access-intranet-tls-ssl-certificate.md ...rial-enable-remote-access-intranet-tls-ssl-certificate.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 Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments. All command-line examples use PowerShell, and certificate management instructions rely on Windows-specific tools and UI (MMC snap-in, cert store locations, NT SERVICE accounts). There are no Linux or cross-platform instructions, and the requirements and troubleshooting steps assume Windows Server and its cryptographic providers.
Recommendations
  • Provide equivalent Linux instructions for obtaining FQDNs (e.g., using `hostname --fqdn` or `dnsdomainname`).
  • Include Linux-based certificate generation examples (e.g., using OpenSSL) and explain how to create SAN certificates.
  • Describe how to install certificates on Linux systems (e.g., using `update-ca-certificates` or placing certificates in `/etc/ssl/certs`).
  • Clarify how to set permissions for certificate private keys on Linux (e.g., using `chown`/`chmod`).
  • Mention Linux service accounts and how to ensure they can access certificate private keys.
  • Add troubleshooting steps relevant to Linux, such as verifying certificate installation and permissions.
  • Note any platform-specific limitations or requirements (e.g., CSP vs. CNG) and how they relate to Linux environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-hive-virtual-network-portal.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-hive-virtual-network-portal.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 demonstrates a Windows bias by exclusively referencing Azure PowerShell, Windows file paths (e.g., hosts file location), and Windows-centric instructions (e.g., installing integration runtime on an Azure VM without specifying OS, referencing C:\Windows\System32\drivers\etc for hosts file edits). There are no Linux-specific instructions, examples, or mentions of Linux tools or shell commands, even though HDInsight and self-hosted integration runtime can be used on Linux VMs. The tutorial assumes a Windows environment for VM setup and configuration steps, potentially excluding Linux users.
Recommendations
  • Provide equivalent instructions for Linux VMs, including how to install and configure the self-hosted integration runtime on Linux.
  • Include Linux-specific commands for editing the hosts file (e.g., /etc/hosts) and clarify OS-agnostic steps.
  • Mention and provide examples using Azure CLI (cross-platform) alongside Azure PowerShell.
  • Explicitly state that both Windows and Linux VMs are supported, and link to OS-specific setup guides.
  • Add screenshots or terminal examples for Linux environments where appropriate.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-hybrid-copy-data-tool.md ...rticles/data-factory/tutorial-hybrid-copy-data-tool.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 a bias toward Windows environments by exclusively referencing SQL Server Management Studio (SSMS), a Windows-only tool, for database setup and management. There are no instructions or examples for performing equivalent steps on Linux (e.g., using Azure Data Studio, sqlcmd, or other cross-platform tools). The integration runtime installation and setup steps do not mention Linux compatibility or provide Linux-specific guidance, and all screenshots and UI references assume a Windows desktop experience.
Recommendations
  • Include instructions for setting up the SQL Server database and table using cross-platform tools such as Azure Data Studio or sqlcmd, which are available on Linux and macOS.
  • Explicitly mention Linux compatibility for the self-hosted integration runtime, and provide installation steps for Linux (e.g., using shell commands, package managers, or manual setup).
  • Add Linux-specific notes or sections where relevant, such as how to obtain storage account keys or run the integration runtime installer on Linux.
  • Provide screenshots or terminal output examples for Linux environments alongside Windows examples.
  • Avoid assuming the use of Notepad or other Windows-specific editors; suggest cross-platform alternatives (e.g., VS Code, nano, vim).
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-spark-powershell.md ...ta-factory/tutorial-transform-data-spark-powershell.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 is heavily biased towards Windows and PowerShell. All command-line instructions use Azure PowerShell, with no mention of Azure CLI, Bash, or Linux-native workflows. There are no Linux/macOS shell examples, and the prerequisite section only references Azure PowerShell. The use of PowerShell cmdlets and terminology assumes a Windows environment, making it less accessible for Linux users.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell instructions, allowing Linux and macOS users to follow along without needing PowerShell.
  • Add a section on installing and configuring Azure CLI, and mention that all steps can be performed on Linux/macOS using CLI.
  • Where file operations are described (e.g., uploading files to Blob Storage), include examples using Azure CLI or azcopy, not just GUI or Windows-centric tools.
  • Clearly state that the HDInsight cluster can use Linux as its OS, and highlight cross-platform compatibility.
  • Reorder or parallelize instructions so that Linux/CLI options are presented alongside PowerShell, not only after or as an afterthought.
  • Add troubleshooting notes for common Linux-specific issues (e.g., file permissions, path formats) when working with Azure Data Factory and HDInsight.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-hybrid-copy-portal.md ...n/articles/data-factory/tutorial-hybrid-copy-portal.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 bias toward Windows environments by exclusively referencing Windows tools (SQL Server Management Studio), providing setup instructions that assume a Windows OS, and omitting Linux equivalents or alternatives. There are no examples or guidance for users running SQL Server on Linux or using Linux-based management tools. The instructions for installing and running the self-hosted integration runtime also implicitly target Windows, with no mention of Linux installation steps.
Recommendations
  • Include instructions for setting up SQL Server on Linux, including installation and management using sqlcmd or Azure Data Studio.
  • Provide Linux-specific steps for installing and configuring the self-hosted integration runtime, referencing the official Linux installation guide.
  • Mention cross-platform tools (e.g., Azure Data Studio) alongside SQL Server Management Studio, and provide examples for both.
  • Add notes or sections that clarify parity and differences between Windows and Linux environments for each major step.
  • Ensure screenshots and UI references do not assume a Windows-only context where not necessary.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-incremental-copy-overview.md ...les/data-factory/tutorial-incremental-copy-overview.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 a Windows bias by exclusively referencing PowerShell-based tutorials for incremental data copy scenarios. All step-by-step instructions link to PowerShell guides, with no mention of Linux shell, CLI, or cross-platform alternatives. Windows tools and patterns (PowerShell) are presented as the default, with no Linux or bash equivalents provided.
Recommendations
  • Provide equivalent tutorials using Azure CLI, Bash, or Python scripts that can be run on Linux and macOS.
  • Explicitly mention cross-platform options and tools in each scenario, not just PowerShell.
  • Add links to documentation or templates for Linux users, ensuring parity in guidance and examples.
  • Consider reordering or grouping examples so that Windows and Linux approaches are presented side-by-side, rather than Windows/PowerShell first or exclusively.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-hive-virtual-network.md ...actory/tutorial-transform-data-hive-virtual-network.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 is heavily biased towards Windows and PowerShell usage. All command-line examples use Azure PowerShell, with no mention of Azure CLI, Bash, or Linux-native tools. Instructions for editing the hosts file explicitly reference the Windows path (C:\Windows\System32\drivers\etc), and there are no Linux equivalents provided. The process for registering the self-hosted integration runtime is described only for Windows VMs, with no guidance for Linux VMs. The tutorial assumes the user is operating in a Windows environment throughout.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell commands, including resource creation, pipeline deployment, and monitoring.
  • Include instructions for editing the hosts file on Linux (e.g., /etc/hosts) when DNS is not available.
  • Clarify that self-hosted integration runtime can be installed on Linux, and provide steps or links for Linux installation and registration.
  • Mention Linux VM options when describing VM creation and integration runtime registration.
  • Add notes or sections that highlight cross-platform compatibility and any differences in steps for Linux users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/author-global-parameters.md ...main/articles/data-factory/author-global-parameters.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 Missing Linux Example
Summary
The documentation page references PowerShell scripts as the method for deploying global parameters in CI/CD, and does not mention or provide examples for Linux or cross-platform alternatives (such as Azure CLI, Bash, or other scripting environments). Windows-specific tools and patterns (PowerShell) are mentioned exclusively, with no parity for Linux users.
Recommendations
  • Add equivalent Linux-friendly examples using Azure CLI or Bash scripts for deploying global parameters.
  • Explicitly mention that ARM template deployment can be performed from Linux/macOS environments and provide guidance or links.
  • Clarify that PowerShell is not the only option and list cross-platform alternatives for CI/CD automation.
  • Where PowerShell is referenced, provide side-by-side examples for Azure CLI or Bash to ensure parity.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/apply-dataops.md ...-docs/blob/main/articles/data-factory/apply-dataops.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 Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Examples and tool recommendations for automated testing and CI/CD (e.g., NUnit with Visual Studio, PowerShell, Azure DevOps) are Windows-centric, with no mention of Linux alternatives or parity. PowerShell and Visual Studio are referenced as primary tools for testing and deployment, and Windows-based workflows are described before any cross-platform or Linux options. There are no explicit Linux shell, bash, or open-source cross-platform examples, and Linux-native tools or patterns are not discussed.
Recommendations
  • Include Linux-specific examples for CI/CD and testing, such as using bash scripts, shell commands, or Linux-native tools.
  • Mention and provide examples for cross-platform alternatives to PowerShell, such as Azure CLI usage in bash or zsh.
  • Reference open-source, cross-platform testing frameworks (e.g., pytest, JUnit) alongside NUnit/Visual Studio.
  • Clarify that Azure DevOps and GitHub workflows can be run on Linux agents and provide sample YAML for Linux runners.
  • Add guidance for setting up DataOps workflows on Linux environments, including installation and usage of required tools.
  • Ensure screenshots and UI references do not imply Windows-only usage, and note platform-agnostic access where applicable.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-package-store.md ...actory/azure-ssis-integration-runtime-package-store.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All management operations are described using Windows-only tools such as SQL Server Management Studio (SSMS), dtutil, cmdkey, and net use, with explicit references to Windows file paths and command prompt usage. There are no examples or guidance for performing these tasks from Linux or cross-platform environments, nor are Linux-compatible tools or workflows mentioned.
Recommendations
  • Provide equivalent instructions for Linux environments, including how to connect to Azure Files (e.g., using SMB mounting commands on Linux).
  • Mention cross-platform alternatives to SSMS, such as Azure Data Studio, and clarify their capabilities/limitations.
  • Offer dtutil usage examples on Linux, or clarify if dtutil is Windows-only and suggest alternatives if available.
  • Include notes on how to manage SSIS packages from Linux or macOS, or via REST APIs/ADF portal where possible.
  • Avoid assuming Windows file paths and command syntax; provide platform-agnostic or dual-platform examples.
  • Explicitly state platform requirements and limitations for each tool or workflow.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-express-virtual-network-injection.md ...-integration-runtime-express-virtual-network-injection.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 Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell scripts (setupdnsserver.ps1) and providing setup instructions that rely on Windows-centric tooling. There are no examples or instructions for Linux users, such as Bash scripts or Linux-compatible setup methods. The related content also highlights Azure PowerShell as a primary method for joining the integration runtime to a virtual network, with no mention of Azure CLI or Linux-native tools.
Recommendations
  • Provide equivalent Linux/Bash setup scripts alongside PowerShell examples, or clarify cross-platform compatibility.
  • Include instructions for using Azure CLI to join Azure-SSIS IR to a virtual network, in addition to PowerShell.
  • Explicitly mention whether the provided scripts (main.cmd, setupdnsserver.ps1) can be run on Linux-based integration runtime nodes, or offer alternatives.
  • Add examples and guidance for configuring custom DNS and other features from a Linux environment.
  • Ensure that all referenced tooling and setup steps have Linux equivalents or note any platform limitations.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-standard-virtual-network-injection.md ...integration-runtime-standard-virtual-network-injection.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 exhibits a Windows bias in several ways. PowerShell is the only scripting example provided for configuring UDRs, with no mention of Azure CLI, Bash, or Linux-native tools. The NSG section references Windows firewall rules and RDP (port 3389) for troubleshooting, which are Windows-specific concepts. There are no Linux-specific instructions or examples for network configuration, nor is there guidance for users who may be managing Azure resources from Linux or macOS environments. The related content and guidance consistently prioritize Windows-centric tools and patterns, such as Azure PowerShell and Windows firewall, without offering Linux alternatives.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell scripts for all configuration steps, especially for UDR and NSG setup.
  • Include instructions or notes for users managing Azure resources from Linux or macOS, such as using Azure CLI or REST API.
  • When referencing firewall rules, clarify how equivalent configurations can be made on Linux (e.g., using iptables, firewalld, or ufw).
  • Add troubleshooting guidance for Linux-based environments, such as SSH access instead of RDP.
  • Ensure that all sections mentioning Windows tools or patterns also mention Linux equivalents, or explicitly state when a step is Windows-only.
  • Review related content links to ensure parity between Windows and Linux documentation.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/built-in-preinstalled-components-ssis-integration-runtime.md ...lt-in-preinstalled-components-ssis-integration-runtime.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 exclusively describes Azure-SSIS Integration Runtime as running on Windows Server 2019, with all built-in and preinstalled components, connection managers, data sources/destinations, and tasks being Windows-centric. There is no mention of Linux support, equivalents, or examples, and all referenced technologies (e.g., .NET Framework, SQL Server Native Client, MSMQ, WMI) are Windows-specific. No Linux alternatives or cross-platform notes are provided.
Recommendations
  • Explicitly state the lack of Linux support, or clarify platform limitations at the top of the documentation.
  • If Linux support is planned or available in any form, provide equivalent lists/examples for Linux environments.
  • Where possible, mention cross-platform alternatives to Windows-only tools (e.g., alternatives to MSMQ, WMI, SQL Server Native Client) or note their absence.
  • Add guidance for users seeking Linux-native data integration solutions on Azure, such as links to Data Factory mapping data flows, Azure Databricks, or other ETL tools.
  • Consider providing a comparison table of features/components available on Windows vs. Linux (if/when Linux support is introduced).
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/choose-the-right-integration-runtime-configuration.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/choose-the-right-integration-runtime-configuration.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 referencing on-premises environments and tools in a way that implicitly assumes Windows as the default platform. Examples and linked articles (e.g., 'create-shared-self-hosted-integration-runtime-powershell.md') focus on PowerShell and Windows-centric management. There is no mention of Linux-specific installation, configuration, or troubleshooting steps for self-hosted integration runtime, nor are Linux tools or patterns (such as systemd, bash, or Linux firewall management) discussed. The diagnostic and maintenance tools referenced are not described in a cross-platform manner.
Recommendations
  • Add explicit instructions and examples for installing and managing self-hosted integration runtime on Linux systems, including supported distributions.
  • Provide Linux-specific troubleshooting steps and mention relevant tools (e.g., systemd for service management, bash scripts for automation).
  • Include parity in diagnostic tool usage and log collection for Linux environments.
  • Reference both PowerShell and Bash/CLI examples when discussing automation or configuration.
  • Clarify support for Linux-based on-premises environments and provide links to Linux-focused documentation where available.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/ci-cd-github-troubleshoot-guide.md ...ticles/data-factory/ci-cd-github-troubleshoot-guide.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 Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. PowerShell is mentioned as a method for changing integration runtime, but no equivalent Linux shell or cross-platform CLI example is provided. References to Azure PowerShell are present in linked template best practices, but there are no Bash, Azure CLI, or Linux-specific instructions or examples. The documentation omits Linux or macOS-specific troubleshooting steps and does not provide parity for non-Windows environments in automation or scripting scenarios.
Recommendations
  • Add equivalent examples using Bash and Azure CLI for operations currently described with PowerShell.
  • Explicitly mention cross-platform tools and approaches (e.g., Azure CLI, REST API) alongside PowerShell.
  • Where automation is discussed, provide both Windows (PowerShell) and Linux/macOS (Bash, CLI) sample scripts.
  • Review troubleshooting steps to ensure they are not Windows-centric and clarify when steps apply to all platforms.
  • Include notes or links for Linux/macOS users where platform-specific behavior or setup may differ.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-datasets-linked-services.md ...cles/data-factory/concepts-datasets-linked-services.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 Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a primary tool for creating datasets, referencing Windows-centric tools before cross-platform or Linux-native alternatives, and omitting explicit Linux or bash examples. Quickstart and tool references prioritize PowerShell and .NET, which are traditionally Windows-first technologies, without mentioning Linux CLI, Azure CLI, or bash scripting options.
Recommendations
  • Add explicit examples and quickstarts for Linux users, such as using Azure CLI, bash, or Python SDK.
  • List cross-platform tools (REST API, Azure CLI, Python SDK) before or alongside Windows-specific tools like PowerShell and .NET.
  • Include sample commands for dataset creation using Azure CLI and bash scripts.
  • Clarify which tools are cross-platform and provide guidance for Linux/macOS environments.
  • Ensure parity in screenshots and UI instructions for Linux/macOS users where applicable.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-parameters-variables.md ...articles/data-factory/concepts-parameters-variables.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 a Windows bias primarily through its exclusive use of PowerShell-based tutorials in the 'Related content' section. There are no examples or references to Linux tools, Bash, or cross-platform CLI usage. This may lead Linux users to perceive the documentation as less relevant or accessible for their workflows.
Recommendations
  • Add equivalent tutorials and quickstarts using Azure CLI and Bash scripts alongside PowerShell examples.
  • Explicitly mention cross-platform support and provide guidance for Linux/macOS users where applicable.
  • Ensure that references to tools and scripting languages are balanced, or at least include links to Linux-friendly alternatives.
  • Where screenshots or UI instructions are given, clarify any OS-specific differences or provide notes for Linux environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-pipelines-activities.md ...articles/data-factory/concepts-pipelines-activities.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 primarily through its use of PowerShell-based walkthroughs and examples. All referenced quickstarts and tutorials for creating and transforming pipelines point to PowerShell instructions, with no mention of Linux shell, CLI, or cross-platform alternatives. There are no Linux-specific examples, nor is there any indication of parity or alternative instructions for non-Windows environments. The documentation also references SQL Server and Azure SQL as primary data sources, which are more commonly associated with Windows environments, and does not mention open-source or Linux-native databases as examples.
Recommendations
  • Provide equivalent walkthroughs and tutorials using Azure CLI, Bash, or other cross-platform tools alongside PowerShell examples.
  • Explicitly mention Linux and macOS support in relevant sections, including any platform-specific requirements or differences.
  • Include examples that use open-source or Linux-native data sources (e.g., PostgreSQL, MySQL) in addition to SQL Server/Azure SQL.
  • Add links to documentation or quickstarts for pipeline creation and management using non-Windows environments.
  • Ensure that references to tools and commands do not assume a Windows environment by default.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-linked-services.md ...main/articles/data-factory/concepts-linked-services.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 Windows bias by listing PowerShell as a primary method for creating linked services, referencing Windows-centric tools (PowerShell, .NET), and omitting Linux-specific examples or CLI instructions. The order of tool presentation (PowerShell before REST API or ARM templates) and lack of Bash/Azure CLI examples further reinforce the bias.
Recommendations
  • Add Azure CLI and Bash examples for creating linked services to provide parity for Linux users.
  • Reorder tool and SDK lists to present platform-neutral or cross-platform options (e.g., REST API, ARM templates, Azure CLI) before Windows-specific tools like PowerShell.
  • Explicitly mention Linux support and provide links to Linux-compatible tutorials.
  • Include a note clarifying that all operations can be performed from Linux environments using Azure CLI, REST API, or SDKs.
  • Ensure screenshots and UI instructions do not imply Windows-only usage.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-pipeline-execution-triggers.md ...s/data-factory/concepts-pipeline-execution-triggers.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 page demonstrates Windows bias in several ways: Windows-specific tools (Azure PowerShell) are featured prominently and before cross-platform alternatives; PowerShell examples are provided without equivalent Linux shell (bash/CLI) examples; references to Windows-centric workflows (.NET SDK, PowerShell) appear before mentioning REST API or Python SDK; and there is no mention of Azure CLI or bash scripting, which are commonly used on Linux. No Linux-specific instructions or parity examples are present.
Recommendations
  • Add Azure CLI examples for pipeline execution and triggers, as CLI is cross-platform and widely used on Linux.
  • Include bash scripting examples for invoking REST API endpoints, demonstrating how Linux users can automate pipeline runs.
  • Reorder API/SDK sections to present cross-platform options (REST API, Python SDK, Azure CLI) before Windows-centric tools (PowerShell, .NET SDK).
  • Explicitly mention that Azure PowerShell is primarily a Windows tool and suggest Azure CLI or REST API for Linux users.
  • Provide links to Linux setup guides for Azure Data Factory/Synapse automation.
  • Ensure that all code samples (parameter passing, response handling) are shown in both PowerShell and bash/CLI formats.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-roles-permissions.md ...in/articles/data-factory/concepts-roles-permissions.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 Missing Linux Example
Summary
The documentation mentions updating a data factory from PowerShell or the SDK as a scenario, but does not provide equivalent examples or mention Linux-native tools (such as Azure CLI or Bash scripting). PowerShell is primarily a Windows tool, and its mention without Linux alternatives suggests a Windows bias. No Linux-specific instructions or parity examples are provided for role assignment or resource management.
Recommendations
  • Include examples using Azure CLI (az) for role assignment and resource management, which is cross-platform and widely used on Linux.
  • Mention Bash scripting or provide sample Bash commands for common tasks.
  • When referencing PowerShell, clarify that cross-platform PowerShell Core is available, or provide equivalent Linux-native instructions.
  • Ensure that all scenarios (such as updating a data factory) have both PowerShell and Azure CLI examples, and present them together or with equal prominence.
  • Add a note or section highlighting cross-platform tooling and usage, especially for Linux users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/configure-azure-ssis-integration-runtime-performance.md ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/configure-azure-ssis-integration-runtime-performance.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 a Windows bias by exclusively providing PowerShell-based configuration examples and referencing Windows-centric tools and patterns. There are no equivalent examples or instructions for Linux users (e.g., Bash, Azure CLI), and the use of PowerShell is presented as the default or only method for configuration. This may hinder Linux users or those working in cross-platform environments from easily following the documentation.
Recommendations
  • Provide equivalent configuration examples using Bash and Azure CLI, alongside PowerShell.
  • Explicitly mention cross-platform options for managing Azure-SSIS Integration Runtime, including links to Azure CLI documentation.
  • Add notes clarifying that PowerShell is one option and highlight Linux-compatible alternatives.
  • Ensure that any referenced scripts or automation can be run on Linux/macOS environments, or provide guidance for adapting them.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-amazon-rds-for-sql-server.md ...es/data-factory/connector-amazon-rds-for-sql-server.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page shows evidence of Windows bias. Windows authentication is presented as a primary authentication method alongside SQL authentication, with explicit examples and instructions. Troubleshooting steps and configuration instructions reference Windows-specific tools such as SQL Server Management Studio, SQL Server Configuration Manager, and Windows Firewall, with no mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for connecting from Linux environments, nor are Linux authentication patterns (e.g., Kerberos, integrated authentication on Linux) discussed.
Recommendations
  • Add examples and instructions for connecting from Linux environments, including relevant authentication methods (e.g., Kerberos, SQL authentication from Linux).
  • Provide troubleshooting steps for Linux, such as configuring remote access and enabling TCP/IP using Linux tools or command-line utilities.
  • Mention cross-platform SQL Server management tools (e.g., Azure Data Studio, sqlcmd) and provide usage examples.
  • Clarify which features (such as Windows authentication) are only available on Windows, and suggest alternatives for Linux users.
  • Include firewall configuration steps for Linux (e.g., using ufw or firewalld) alongside Windows Firewall instructions.
GitHub Create Pull Request
← Previous Page 12 of 40 Next →