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 251-275 of 1000 flagged pages
Data Factory Copy data from Azure Blob Storage to Azure SQL Database ...in/articles/data-factory/tutorial-copy-data-dot-net.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a strong Windows bias: it exclusively uses Visual Studio (Windows-only) for development, relies on .NET SDK and C# examples, and instructs users to use Windows tools such as Notepad and SQL Server Management Studio (SSMS). There are no Linux or cross-platform alternatives mentioned for project setup, code execution, or database management. Package installation is shown via NuGet Package Manager Console (PowerShell-based), with no mention of dotnet CLI or other Linux-friendly methods. The next tutorial is explicitly a PowerShell guide, further reinforcing the Windows-centric approach.
Recommendations
  • Add instructions for setting up the project using cross-platform tools such as VS Code or JetBrains Rider, and include dotnet CLI commands for package management.
  • Provide equivalent code samples and setup steps for Linux/macOS environments, including terminal commands for file creation (e.g., using 'echo' or 'nano' instead of Notepad).
  • Mention and demonstrate database management using Azure Data Studio, which is cross-platform, instead of only SSMS.
  • Include guidance for running the tutorial on Linux/macOS, such as installing the .NET SDK and running the application from the terminal.
  • Reference cross-platform alternatives for Azure Storage Explorer (which is available for Linux/macOS) and clarify its availability.
  • Balance the order of tool mentions so that Windows and Linux options are presented together or Linux-first where appropriate.
  • Provide links to documentation for Linux/macOS setup and troubleshooting.
GitHub Create Pull Request
Data Factory Provision the Azure-SSIS integration runtime ...es/data-factory/tutorial-deploy-ssis-packages-azure.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows-based tools (SSDT, SSMS, dtutil, AzureDTExec), mentioning PowerShell for firewall configuration, and omitting Linux alternatives or examples. There are no instructions or examples for Linux users, nor are cross-platform command-line tools or patterns discussed. Windows-centric tools and patterns are presented as the default or only option, with no mention of Linux-compatible workflows.
Recommendations
  • Include instructions and examples for Linux users, such as using Azure CLI or Bash for configuration tasks (e.g., firewall rules).
  • Mention and provide guidance for cross-platform tools (e.g., Azure Data Studio, az CLI) where possible.
  • Clarify which steps and tools are Windows-only and suggest Linux alternatives where available.
  • Provide explicit examples of deploying and managing SSIS packages from Linux environments, including command-line usage and authentication.
  • Reorder tool mentions so that cross-platform options are listed before or alongside Windows-specific tools.
GitHub Create Pull Request
Data Factory Copy on-premises data using the Azure Copy Data tool ...rticles/data-factory/tutorial-hybrid-copy-data-tool.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 Windows tools (SQL Server Management Studio), omitting Linux equivalents for SQL Server management and integration runtime installation, and implicitly assuming a Windows-first workflow for on-premises setup and tooling. No examples or instructions are provided for Linux users, nor are cross-platform alternatives mentioned.
Recommendations
  • Include instructions for managing SQL Server from Linux, such as using Azure Data Studio, sqlcmd, or other cross-platform tools.
  • Provide guidance for installing and running the self-hosted integration runtime on Linux, including prerequisites and supported distributions.
  • Add explicit notes or sections for Linux users, outlining any differences in setup or troubleshooting steps.
  • Mention cross-platform alternatives before or alongside Windows-specific tools to ensure parity.
  • Clarify any limitations or requirements for Linux environments in the prerequisites section.
GitHub Create Pull Request
Data Factory Transform data ...docs/blob/main/articles/data-factory/transform-data.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias. The only tutorial linked at the end is for Spark using PowerShell, which is a Windows-centric tool. SQL Server and .NET custom activities are highlighted, both of which are traditionally Windows technologies. While HDInsight activities mention both Windows and Linux clusters, the overall pattern is to mention Windows tools and technologies first or exclusively, with no Linux shell or cross-platform examples provided.
Recommendations
  • Add Linux shell (bash) and cross-platform CLI examples alongside PowerShell tutorials.
  • Include references to open-source or Linux-native tools where possible (e.g., PostgreSQL stored procedures, Python custom activities).
  • Ensure that examples and tutorials are balanced between Windows and Linux environments.
  • Explicitly mention Linux compatibility and provide guidance for Linux users in relevant sections.
  • Add links to tutorials using Linux tools or environments, such as Spark with Bash or Databricks with Linux CLI.
GitHub Create Pull Request
Data Factory Branching in Azure Data Factory pipeline ...ob/main/articles/data-factory/tutorial-control-flow.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All code examples use C#/.NET and Visual Studio, with explicit instructions for Visual Studio 2019 and NuGet Package Manager (PowerShell-based). The prerequisites and workflow steps exclusively mention Windows tools (Visual Studio, Azure Storage Explorer), with no mention of Linux equivalents or cross-platform alternatives. There are no instructions or examples for running the tutorial on Linux or macOS, nor for using cross-platform SDKs or editors.
Recommendations
  • Add instructions and code samples for running the tutorial on Linux and macOS, including using .NET Core/SDK and cross-platform editors like VS Code.
  • Include alternative steps for installing required packages using dotnet CLI (e.g., 'dotnet add package ...') instead of NuGet Package Manager.
  • Mention and provide examples for using Azure CLI or REST API for Data Factory operations, which are platform-agnostic.
  • List cross-platform tools for interacting with Azure Storage, such as AzCopy, Azure CLI, or web portal, alongside Azure Storage Explorer.
  • Clarify that Azure Data Factory SDKs and APIs are available for multiple languages and platforms, and link to relevant documentation.
GitHub Create Pull Request
Data Factory Enable remote access from intranet with TLS/SSL certificate (Advanced) ...rial-enable-remote-access-intranet-tls-ssl-certificate.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 steps rely on Windows-specific tools (MMC snap-in, Windows certificate stores, NT SERVICE accounts). There are no Linux or cross-platform instructions or examples provided, and the prerequisites and requirements reference Windows Server compatibility and CSP certificates only.
Recommendations
  • Provide equivalent Linux command-line examples using OpenSSL, certtool, or other standard Linux utilities for generating and managing certificates.
  • Include instructions for installing certificates on Linux systems (e.g., using update-ca-certificates, copying to /etc/ssl/certs, etc.).
  • Document how to retrieve FQDNs on Linux (e.g., using `hostname -f`).
  • Clarify whether the integration runtime supports Linux nodes, and if so, provide parity in configuration and troubleshooting steps.
  • Mention Linux-compatible certificate formats and providers (e.g., PEM, PKCS#12) and any platform-specific requirements.
  • Add troubleshooting steps for Linux, such as checking permissions and certificate validity using Linux tools.
GitHub Create Pull Request
Data Factory Copy data from SQL Server to Blob storage using Azure portal ...n/articles/data-factory/tutorial-hybrid-copy-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing Windows tools (SQL Server Management Studio), providing setup instructions that assume a Windows OS, and omitting any Linux equivalents or instructions for Linux users. There are no examples or guidance for performing the same tasks on Linux, such as using Azure Data Studio, sqlcmd, or other cross-platform tools.
Recommendations
  • Include instructions and examples for Linux users, such as using Azure Data Studio or sqlcmd to create databases and tables.
  • Mention cross-platform alternatives to SQL Server Management Studio, and provide download links or installation steps for Linux.
  • Clarify that the self-hosted integration runtime can be installed on Linux, and provide steps or references for Linux installation.
  • Ensure screenshots and UI references are not Windows-specific, or provide Linux equivalents where applicable.
  • Add a section or callout for Linux prerequisites and troubleshooting.
GitHub Create Pull Request
Data Factory Incrementally copy data from a source data store to a destination data store ...les/data-factory/tutorial-incremental-copy-overview.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by 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-centric tools and workflows are presented first and exclusively, leaving Linux users without direct guidance.
Recommendations
  • Provide equivalent step-by-step tutorials using Azure CLI, Bash scripts, or other Linux-friendly tools alongside PowerShell examples.
  • Explicitly mention cross-platform options and clarify which instructions are platform-specific.
  • Add links to documentation or templates for Linux users, ensuring parity in guidance and tooling.
  • Where possible, use platform-neutral language and examples, or present Windows and Linux approaches side-by-side.
GitHub Create Pull Request
Data Factory Copy data from SQL Server to Blob storage using PowerShell ...ticles/data-factory/tutorial-hybrid-copy-powershell.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
This documentation page exhibits strong Windows bias. All command-line examples use PowerShell, and the workflow assumes a Windows environment throughout. The installation of the self-hosted integration runtime is described only for Windows, with no mention of Linux or cross-platform alternatives. Windows-specific tools (SQL Server Management Studio, PowerShell, Notepad, C:\ paths) are referenced exclusively, and there are no Linux shell, Azure CLI, or cross-platform instructions. The documentation does not provide parity for Linux users or those using non-Windows environments.
Recommendations
  • Provide equivalent instructions using Azure CLI and/or Bash shell for all steps, including resource creation, pipeline management, and monitoring.
  • Include guidance for installing and running the self-hosted integration runtime on Linux (where supported), or explicitly state platform limitations.
  • Offer SQL Server setup instructions using cross-platform tools (e.g., Azure Data Studio, sqlcmd) and avoid exclusive reliance on SQL Server Management Studio.
  • Use generic file paths and editors (e.g., ~/ADFv2Tutorial, nano, vi) alongside Windows examples.
  • Clearly indicate any steps or components that are Windows-only, and suggest alternatives or workarounds for Linux/macOS users.
  • Add a section or callouts for Linux/macOS users, outlining differences and providing links to relevant documentation.
GitHub Create Pull Request
Data Factory Transform data using Spark in Azure Data Factory ...ta-factory/tutorial-transform-data-spark-powershell.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All command-line instructions for deploying and managing Azure Data Factory resources are provided exclusively using Azure PowerShell, with no mention of Azure CLI, Bash, or cross-platform alternatives. The prerequisites and workflow assume the reader is using PowerShell, a tool most commonly associated with Windows, and do not offer Linux/macOS-friendly equivalents or guidance. This creates a barrier for users on Linux or macOS, who may prefer or require Bash or Azure CLI. There is no mention of how to perform these steps using other tools, nor any cross-platform notes.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Add a section or callouts indicating how Linux/macOS users can perform each step, including installation and authentication.
  • Explicitly state that Azure PowerShell is available on Linux/macOS, if relevant, and provide installation instructions for those platforms.
  • Consider reordering examples so that cross-platform tools (Azure CLI, REST API) are mentioned before or alongside PowerShell.
  • Include Bash script examples for file operations (such as uploading files to Blob Storage) using Azure CLI or azcopy.
  • Add a note at the beginning clarifying that the tutorial is suitable for users on all major operating systems, and provide links to platform-specific guidance where needed.
GitHub Create Pull Request
Data Factory Transform data using Hive in Azure Virtual Network using Azure portal ...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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Azure PowerShell for prerequisites, instructing users to edit the Windows hosts file, and guiding installation of the self-hosted integration runtime on an Azure VM without specifying OS type (implicitly Windows). There are no Linux or cross-platform alternatives provided for key steps such as uploading files, configuring network settings, or installing/running the integration runtime. Windows tools and patterns are mentioned exclusively and first, with no parity for Linux users.
Recommendations
  • Provide Linux equivalents for all steps involving Azure PowerShell, such as using Azure CLI or Bash scripts.
  • Include instructions for editing the hosts file on Linux (e.g., /etc/hosts) alongside the Windows path.
  • Clarify that the self-hosted integration runtime can be installed on Linux VMs, and provide installation steps for Linux.
  • Offer cross-platform examples for uploading Hive scripts to Blob Storage (e.g., using azcopy, Azure CLI, or Storage Explorer on Linux).
  • Explicitly state OS requirements and options for each step, ensuring parity for Linux and macOS users.
  • Where possible, use platform-neutral language and tools, or provide side-by-side instructions for Windows and Linux.
GitHub Create Pull Request
Data Factory Transform data by using Spark in Azure Data Factory ...s/data-factory/tutorial-transform-data-spark-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by requiring Azure PowerShell for setup, referencing only PowerShell installation instructions, and omitting any Linux or cross-platform CLI alternatives (such as Azure CLI or Bash). No Linux-specific instructions or examples are provided for uploading files or managing resources, and the prerequisites section assumes a Windows environment by default.
Recommendations
  • Provide equivalent instructions using Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
  • Include Bash shell examples for file uploads to Azure Blob Storage (e.g., using az storage blob upload or Azure Storage Explorer).
  • Mention that Azure PowerShell is available on Linux and macOS, or clarify that users can choose between PowerShell and CLI.
  • Add a note or section for Linux/macOS users, outlining any differences or additional steps required.
  • Ensure that all command-line instructions are presented in both PowerShell and Bash/CLI formats, or link to relevant cross-platform documentation.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/compute-linked-services.md .../main/articles/data-factory/compute-linked-services.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias, primarily through the exclusive or prioritized mention of Windows tools and PowerShell cmdlets for Azure Batch account and pool creation. The references to 'CMDLETs & APIS' and links to PowerShell-based management articles appear before or instead of Linux CLI alternatives. There are no explicit Linux shell or CLI examples for Azure Batch or VM sizing, and Windows-centric tooling (e.g., Microsoft Azure Storage Explorer) is recommended for storage management. However, HDInsight examples are explicitly Linux-based, and the documentation does not restrict compute environments to Windows OS, indicating some Linux parity.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell for Azure Batch account and pool creation.
  • Mention cross-platform tools (e.g., azcopy, Azure CLI, REST API) for storage management and container deletion, not just Microsoft Azure Storage Explorer.
  • Clarify that both Linux and Windows users can perform management tasks, and link to platform-neutral documentation where possible.
  • When referencing VM sizes and configuration, include instructions or examples for both PowerShell and Azure CLI.
  • Ensure that any references to 'CMDLETs & APIS' are accompanied by equivalent Linux/CLI commands.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/configure-bcdr-azure-ssis-integration-runtime.md ...ctory/configure-bcdr-azure-ssis-integration-runtime.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 demonstrates a Windows bias by exclusively referencing Windows-centric tools and workflows such as SSMS (SQL Server Management Studio), PowerShell, and Windows-style scripting for job management. All examples and instructions for orchestration, job scripting, and IR management use Windows tools or interfaces (Azure portal, SSMS, PowerShell), with no mention of Linux-native equivalents or cross-platform alternatives. There are no examples using Linux CLI, Azure CLI, or other non-Windows tools, and the documentation assumes the reader is familiar with Windows environments and patterns.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI and/or REST API for all steps currently covered with PowerShell or portal UI.
  • Include guidance for managing SSIS jobs and schedules using cross-platform tools, such as Azure Data Studio (which runs on Linux/Mac), or T-SQL scripts that can be executed from any OS.
  • Add explicit Linux/macOS workflow examples for starting/stopping IRs, managing failover, and scripting job migration.
  • Reference and link to documentation for Linux-compatible tools where possible (e.g., Azure CLI, Data Studio).
  • Clarify which steps require Windows-only tools and suggest alternatives or workarounds for non-Windows users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-dynamics-crm-office-365.md ...cles/data-factory/connector-dynamics-crm-office-365.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 demonstrates a Windows bias primarily through exclusive references to Windows-centric tooling (Dynamics XRM tooling for Windows client applications), lack of Linux-specific instructions or parity, and the absence of any Linux or cross-platform command-line examples. All authentication, configuration, and scripting examples are platform-neutral JSON, but underlying references and guidance assume a Windows environment and do not mention Linux alternatives or compatibility.
Recommendations
  • Explicitly state whether the connector and its dependencies (such as Dynamics XRM tooling) are supported on Linux and provide guidance for Linux users.
  • Include examples or instructions for Linux environments, such as using Azure CLI, REST API, or other cross-platform tools for authentication and configuration.
  • If any features are Windows-only, clearly document limitations and suggest alternatives for Linux users.
  • Add troubleshooting or setup notes for Linux environments, especially for self-hosted integration runtime scenarios.
  • Review and update references to Windows client tooling to clarify cross-platform support or provide Linux equivalents if available.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-azure-blob-storage.md ...a-factory/connector-troubleshoot-azure-blob-storage.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 displays Windows bias by referencing Windows-specific tools (diawp.exe.config) and policies (FIPS mode) without mentioning Linux equivalents or providing troubleshooting steps for Linux environments. The guidance for disabling FIPS mode is Windows-centric, and there are no examples or instructions for Linux users running self-hosted integration runtime.
Recommendations
  • Include troubleshooting steps for disabling FIPS mode on Linux systems, such as instructions for modifying relevant configuration files or environment variables.
  • Mention Linux-specific paths, tools, or commands where applicable, especially for self-hosted integration runtime installations.
  • Provide parity in examples and recommendations by explicitly stating differences or additional steps for Linux users.
  • Add a note clarifying platform-specific behavior and linking to platform-specific documentation for both Windows and Linux.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-vertica.md ...s/blob/main/articles/data-factory/connector-vertica.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 in several areas. The ODBC driver installation instructions and screenshots exclusively use Windows as the example, with no mention of Linux or macOS alternatives. The installation steps reference Windows-specific tools (e.g., ODBC Data Source Administrator via Start menu) and do not provide parity for Linux environments, which are common for self-hosted integration runtimes. There are no Linux-specific instructions, examples, or screenshots, and Windows is presented as the default/primary platform for setup.
Recommendations
  • Add Linux installation instructions for the Vertica ODBC driver, including command-line steps and configuration locations.
  • Include Linux-specific screenshots or terminal output for ODBC driver installation and verification.
  • Mention and provide guidance for ODBC configuration tools on Linux (e.g., editing odbc.ini, using unixODBC).
  • Clearly indicate platform differences and provide side-by-side instructions for Windows and Linux wherever setup steps are required.
  • Ensure examples and troubleshooting steps cover both Windows and Linux environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-switch-activity.md .../articles/data-factory/control-flow-switch-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 PowerShell, with explicit references to Windows file paths (e.g., C:\ADF), and there are no equivalent examples for Linux or cross-platform CLI tools. The tutorial and walkthrough are centered around Azure PowerShell, with no mention of Azure CLI or bash scripting alternatives. This may hinder accessibility for users on Linux or macOS systems.
Recommendations
  • Provide equivalent Azure CLI (az) examples for all PowerShell commands, including pipeline creation, linked service setup, dataset definition, and pipeline execution.
  • Use cross-platform file path conventions (e.g., /home/user/ADF or ./ADF) in examples, or clarify that paths should be adapted to the user's OS.
  • Explicitly mention that the steps can be performed on Linux/macOS and provide bash script samples where appropriate.
  • Add a section or note highlighting cross-platform tooling and usage, including links to Azure CLI documentation.
  • Review and update tutorials to ensure parity between Windows and Linux/macOS environments, avoiding exclusive reliance on Windows tools.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/credentials.md ...re-docs/blob/main/articles/data-factory/credentials.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 primarily referencing Windows-centric tools and workflows. PowerShell is mentioned explicitly as a scripting option, and the Azure portal (a GUI often used on Windows) is the only interface shown in screenshots. There are no examples or instructions for using Linux-native tools (such as Azure CLI or Bash scripts), nor are Linux workflows or screenshots provided. The order of tool mentions (portal, SDK, PowerShell, REST API) also places Windows tools before cross-platform or Linux-friendly alternatives.
Recommendations
  • Add explicit examples using Azure CLI and Bash scripts for credential management, alongside PowerShell.
  • Include screenshots or instructions for using the Azure portal on Linux or via browser, clarifying platform neutrality.
  • Reorder tool mentions to highlight cross-platform options (e.g., Azure CLI, REST API) before Windows-specific tools like PowerShell.
  • Provide parity in scripting examples, ensuring both PowerShell and Bash/CLI are covered for all major actions.
  • Note any platform-specific limitations or differences, if applicable, to help users on Linux.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime.md .../data-factory/create-azure-ssis-integration-runtime.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 Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by referencing only Windows-centric tools (SSDT, SSMS, dtutil, PowerShell) for deploying and managing Azure-SSIS IR. There are no examples or mentions of Linux-compatible alternatives or cross-platform tools. PowerShell is presented as the only command-line provisioning option, and Windows tools are listed first and exclusively, with no parity for Linux users.
Recommendations
  • Include examples using Azure CLI for provisioning Azure-SSIS IR, as it is cross-platform and works on Linux, macOS, and Windows.
  • Mention and provide guidance for using cross-platform database management tools (e.g., Azure Data Studio) alongside SSMS.
  • Clarify whether dtutil and AzureDTExec have Linux-compatible versions or suggest alternatives for Linux users.
  • Add explicit notes or sections for Linux/macOS users, detailing any limitations and available options.
  • Ensure that command-line instructions are available for both PowerShell and Bash/Azure CLI.
  • List cross-platform tools before or alongside Windows-specific tools to avoid 'windows_first' bias.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-movement-security-considerations.md .../data-factory/data-movement-security-considerations.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 notable Windows bias in its security guidance for Azure Data Factory data movement. It relies heavily on PowerShell cmdlets (e.g., Set-AzDataFactoryV2LinkedService, New-AzDataFactoryV2LinkedServiceEncryptedCredential) for credential management and encryption, and references Windows-specific technologies such as DPAPI for local encryption. Firewall configuration examples and port requirements are described in terms of Windows Firewall, with no mention of Linux equivalents (e.g., iptables, firewalld) or cross-platform alternatives. There are no Linux or cross-platform command-line examples or guidance for credential encryption, integration runtime setup, or firewall configuration.
Recommendations
  • Provide equivalent Linux examples for credential encryption and management, using bash scripts or cross-platform tools where possible.
  • Reference Linux firewall tools (e.g., iptables, ufw, firewalld) alongside Windows Firewall when describing port requirements and configuration.
  • Document how to install and configure the self-hosted integration runtime on Linux, including credential storage and encryption mechanisms.
  • Offer cross-platform alternatives to PowerShell cmdlets, such as Azure CLI or REST API examples, for managing linked services and credentials.
  • Clarify whether DPAPI is required or if there are alternative encryption mechanisms available on Linux.
  • Ensure that all configuration steps (including port management and credential encryption) are described for both Windows and Linux environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-configure-azure-ssis-ir-custom-setup.md ...factory/how-to-configure-azure-ssis-ir-custom-setup.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 is heavily Windows-centric, with all examples, scripts, and tool references assuming a Windows environment. Only Windows/Powershell commands and tools (e.g., .cmd, .bat, .exe, msiexec.exe, cmdkey, Azure PowerShell, Windows environment variables) are mentioned, and there are no Linux or cross-platform alternatives provided. The express custom setup options are exclusively for Windows commands and components. The documentation does not acknowledge or provide guidance for Linux-based scenarios, nor does it clarify that Azure-SSIS IR is Windows-only, which could mislead users seeking Linux support.
Recommendations
  • Explicitly state early in the documentation that Azure-SSIS IR is a Windows-based runtime and does not support Linux. This helps set expectations for cross-platform users.
  • Where possible, clarify that all examples and scripts are for Windows, and note the lack of Linux support.
  • If any future Linux support is planned, provide a roadmap or guidance for users.
  • Consider adding a section explaining why Linux examples are not provided, and link to alternatives for Linux-based data integration in Azure (e.g., Azure Data Factory Mapping Data Flows, Azure Databricks, etc.).
  • Review and update related documentation to ensure cross-platform parity is addressed, or Windows bias is clearly explained.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-schedule-azure-ssis-integration-runtime.md ...tory/how-to-schedule-azure-ssis-integration-runtime.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. All scripting and automation examples are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or other cross-platform tools. The monitoring and scheduling sections rely on PowerShell cmdlets and Azure Automation runbooks using PowerShell, which are Windows-centric. SQL Server Management Studio (SSMS), a Windows-only tool, is referenced for testing and verification. There are no Linux or macOS alternatives or examples, and Windows tools and patterns are mentioned before any cross-platform options (if any).
Recommendations
  • Provide equivalent examples using Azure CLI and REST API calls that can be run from Linux/macOS terminals.
  • Include Bash scripts for starting/stopping Azure-SSIS IR and monitoring pipeline/trigger runs.
  • Reference cross-platform database tools (e.g., Azure Data Studio) for SSIS package verification, not just SSMS.
  • Explicitly state platform requirements and offer guidance for non-Windows users.
  • Add notes or sections highlighting how Linux/macOS users can accomplish the same tasks, including module installation and authentication.
  • Where PowerShell is used, mention that PowerShell Core is available cross-platform and provide installation instructions.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-develop-azure-ssis-ir-licensed-components.md ...ry/how-to-develop-azure-ssis-ir-licensed-components.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 exhibits a strong Windows bias. All examples and instructions reference Windows-specific tools and patterns, such as Windows environment variables, Windows Registry keys, and installation paths (e.g., C:\Program Files). There are no examples or instructions for Linux environments, nor is there any mention of Linux equivalents or cross-platform considerations. The documentation assumes the use of Windows throughout and does not address how to perform similar tasks on Linux or other platforms.
Recommendations
  • Add explicit statements clarifying platform support (e.g., whether Azure-SSIS IR or self-hosted IR can run on Linux, and if not, state this clearly).
  • If Linux is supported, provide equivalent instructions for Linux environments, including environment variable access, file system paths, and installation procedures.
  • Mention any limitations or differences when using non-Windows platforms, or provide guidance for cross-platform scenarios.
  • Where possible, use platform-neutral terminology and examples, or present Windows and Linux instructions side-by-side.
  • Include references to Linux tools or patterns (e.g., environment variable access via bash, file locations under /opt or /usr/local, etc.) if applicable.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-v2-connector-get-started.md ...tory/includes/data-factory-v2-connector-get-started.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation lists Azure PowerShell as a primary tool for performing copy activities, which is strongly associated with Windows environments. There is no mention of Linux-specific tools or command-line interfaces such as Azure CLI, and PowerShell is listed before REST API and ARM templates, suggesting a Windows-first approach. No explicit Linux examples or parity tools are referenced.
Recommendations
  • Add Azure CLI as an option for performing copy activities, with links to relevant quickstart guides.
  • Include examples or references for performing tasks on Linux/macOS environments.
  • Reorder the list to avoid prioritizing Windows-centric tools (such as PowerShell) before cross-platform or Linux-friendly options.
  • Explicitly mention platform compatibility for each tool, clarifying which are cross-platform.
GitHub Create Pull Request
← Previous Page 11 of 40 Next →