Data Factory

1123
Total Pages
968
Linux-Friendly Pages
155
Pages with Bias
13.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

319 issues found
Showing 176-200 of 319 flagged pages
Data Factory Use Azure SQL Managed Instance with Azure-SQL Server Integration Services (SSIS) in Azure Data Factory ...ata-factory/how-to-use-sql-managed-instance-with-ir.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. It references Windows-centric tools such as SQL Server Management Studio (SSMS) and Windows Firewall, and mentions Azure PowerShell before Azure CLI for certain operations. There are no explicit Linux/macOS examples or guidance, and troubleshooting steps reference Windows-specific firewall rules. While most instructions are platform-neutral (focused on Azure portal and networking), the lack of Linux/macOS parity in tooling and examples may create friction for non-Windows users.
Recommendations
  • Include examples and guidance for using Azure CLI alongside Azure PowerShell, especially for network and NSG configuration.
  • Mention cross-platform SQL management tools (e.g., Azure Data Studio) in addition to SSMS.
  • Clarify that most operations can be performed from Linux/macOS via Azure portal or CLI, and provide links to relevant documentation.
  • Add troubleshooting notes for Linux/macOS environments, especially regarding firewall and connectivity.
  • Ensure screenshots and step-by-step instructions do not assume Windows-only environments.
GitHub Create Pull Request
Data Factory include file ...tory/includes/data-factory-quickstart-prerequisites.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools and patterns, such as using Notepad and saving files in a C:\ directory. There are no examples or instructions tailored for Linux or macOS users, such as alternative text editors or file paths. The instructions assume a Windows environment, which may create confusion or friction for non-Windows users.
Recommendations
  • Include instructions for Linux/macOS users, such as using nano, vim, or TextEdit as alternative text editors.
  • Provide example file paths for Linux/macOS (e.g., /home/user/ADFv2QuickStartPSH/emp.txt).
  • Clarify that the folder creation and file saving steps can be performed on any OS, and provide OS-agnostic guidance.
  • Add screenshots or notes indicating differences in file dialogs or navigation for Linux/macOS users.
GitHub Create Pull Request
Data Factory Reconfigure the Azure-SSIS integration runtime .../data-factory/manage-azure-ssis-integration-runtime.md
Medium Priority View Details →
Scanned: 2026-01-12 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 provides extensive PowerShell-based instructions for reconfiguring and deleting Azure-SSIS integration runtimes, which are Windows-centric. No equivalent examples are provided for Linux/macOS users (e.g., Azure CLI, Bash, or REST API). The reliance on PowerShell and lack of cross-platform command-line alternatives creates friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform.
  • Include REST API instructions or references for users who prefer scripting outside PowerShell.
  • Explicitly mention platform compatibility for each method (e.g., PowerShell is available on Linux/macOS, but Azure CLI is more common).
  • Reorder examples so that cross-platform methods (Azure CLI, REST API) are presented before or alongside PowerShell.
  • Add notes or links for installing PowerShell on Linux/macOS if PowerShell must be used.
GitHub Create Pull Request
Data Factory Monitor integration runtime in Azure Data Factory ...n/articles/data-factory/monitor-integration-runtime.md
Medium Priority View Details →
Scanned: 2026-01-12 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 page demonstrates a notable Windows bias. All command-line examples use PowerShell cmdlets, with no mention of Bash, Azure CLI, or cross-platform alternatives. The self-hosted integration runtime is described as being installed on 'on-premises Windows machines,' with no reference to Linux support or installation. Windows-centric tools and patterns (PowerShell, SSMS, SSDT) are referenced exclusively or before any cross-platform equivalents. There are no Linux/macOS-specific instructions or examples, making it challenging for non-Windows users to follow or replicate the monitoring steps.
Recommendations
  • Add equivalent Azure CLI examples for all monitoring commands, as Azure CLI is cross-platform.
  • Clarify whether self-hosted integration runtime can be installed and monitored on Linux/macOS, and provide instructions if supported.
  • Include Bash shell examples and/or REST API usage for monitoring integration runtimes.
  • Reference cross-platform tools (e.g., Azure Data Studio, VS Code) alongside or instead of Windows-only tools like SSMS and SSDT.
  • Explicitly state platform requirements and alternatives for each tool or command.
  • Reorder examples so that cross-platform solutions are presented before or alongside Windows-specific ones.
GitHub Create Pull Request
Data Factory Monitor SSIS operations with Azure Monitor ...e-docs/blob/main/articles/data-factory/monitor-ssis.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 by referencing Windows-centric tools (SSMS, SSDT, SQL Server Agent, T-SQL) for SSIS package invocation and log analysis, without mentioning Linux/macOS alternatives or providing cross-platform examples. The only command-line example given is Azure PowerShell, which is predominantly used on Windows. There are no explicit Linux or macOS instructions, nor is there guidance for using cross-platform tools or interfaces.
Recommendations
  • Include examples using Azure CLI, which is cross-platform, for checking SSIS IR operational status.
  • Mention and provide instructions for using Azure Data Studio (available on Windows, Linux, and macOS) as an alternative to SSMS for querying SSISDB and analyzing logs.
  • Clarify whether SSIS package invocation and monitoring can be performed from Linux/macOS environments, and provide relevant steps or limitations.
  • Ensure that any references to PowerShell are accompanied by Azure CLI equivalents.
  • Add notes or sections specifically addressing Linux/macOS users, including any prerequisites or platform-specific considerations.
GitHub Create Pull Request
Data Factory Managed virtual network and managed private endpoints ...ta-factory/managed-virtual-network-private-endpoint.md
Medium Priority View Details →
Scanned: 2026-01-12 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 provides only Azure PowerShell examples for creating managed virtual networks and private endpoints, with no equivalent Azure CLI, REST API, or ARM template instructions. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. The documentation also references PowerShell-specific patterns (e.g., referenceName 'default' only for PowerShell), and the example is placed prominently in its own section, with no Linux-friendly alternatives.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands.
  • Include REST API and ARM template instructions for resource creation.
  • Clearly indicate cross-platform options and recommend tools available on Linux/macOS.
  • Reorder examples so that cross-platform methods (CLI, REST) are presented before or alongside PowerShell.
  • Add a note clarifying that PowerShell is available on Linux/macOS, but CLI is often preferred.
GitHub Create Pull Request
Data Factory Programmatically monitor an Azure Data Factory ...main/articles/data-factory/monitor-programmatically.md
Medium Priority View Details →
Scanned: 2026-01-12 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 page exhibits a notable Windows bias, especially in the REST API and PowerShell sections, where only PowerShell scripts are provided for monitoring Azure Data Factory pipelines. PowerShell is a Windows-centric tool, and no equivalent Linux/macOS shell (e.g., Bash, curl, Python) examples are given for REST API usage. Additionally, PowerShell is referenced first and exclusively for programmatic monitoring, which may create friction for Linux/macOS users.
Recommendations
  • Provide REST API examples using cross-platform tools such as curl, HTTPie, or Python requests, alongside PowerShell.
  • Add Bash shell script examples for monitoring pipelines and retrieving activity run details.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, or clarify compatibility.
  • Reorder or balance the presentation of examples so that Windows and Linux/macOS users are equally supported.
  • Include troubleshooting notes for common platform-specific issues.
GitHub Create Pull Request
Data Factory BCDR for Azure Data Factory and Azure Synapse Analytics Pipelines ...n/articles/data-factory/pipelines-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-12 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, primarily in its use of Azure PowerShell for automation examples (e.g., disabling triggers, automating private endpoint creation) and references to PowerShell modules and scripts. There are no CLI (az), Bash, or Linux/macOS-specific examples or guidance, and automation steps are described only in terms of PowerShell, which is most familiar to Windows users. No Linux/macOS alternatives or parity are provided for these critical automation tasks.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands for disabling triggers, automating private endpoint creation, and other deployment/automation steps.
  • Provide Bash script samples or cross-platform automation guidance alongside PowerShell examples.
  • Explicitly mention that all automation steps can be performed from Linux/macOS using Azure CLI or REST API, and link to relevant documentation.
  • Where PowerShell modules are referenced, also reference the corresponding Azure CLI commands or REST API endpoints.
GitHub Create Pull Request
Data Factory Create Azure Data Factory using .NET SDK ...data-factory/quickstart-create-data-factory-dot-net.md
Medium Priority View Details →
Scanned: 2026-01-12 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 page exhibits a notable Windows bias. All instructions assume the use of Visual Studio (a Windows-centric IDE), and the only example for installing NuGet packages uses PowerShell commands via the Visual Studio Package Manager Console. There are no instructions or examples for Linux/macOS users, such as using VS Code, JetBrains Rider, or the dotnet CLI. The documentation also references Windows-specific tools and patterns first and exclusively, making it difficult for Linux/macOS users to follow along without adaptation.
Recommendations
  • Add instructions for creating and running .NET projects using cross-platform tools like VS Code and the dotnet CLI.
  • Provide NuGet installation commands using the dotnet CLI (e.g., 'dotnet add package ...') alongside PowerShell examples.
  • Clarify that the .NET SDK and Azure SDK are cross-platform and can be used on Linux/macOS.
  • Mention alternative IDEs (VS Code, Rider) and provide setup steps for those environments.
  • Ensure all code samples and steps are not dependent on Windows-only features or tools.
  • Add a section or callout for Linux/macOS users with relevant commands and troubleshooting tips.
GitHub Create Pull Request
Data Factory Create an Azure Data Factory using REST API ...ata-factory/quickstart-create-data-factory-rest-api.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
This documentation is heavily biased towards Windows and PowerShell. All code examples use Azure PowerShell cmdlets, with no mention of Linux/macOS alternatives such as Bash, curl, or cross-platform Azure CLI. Tools like Azure Storage Explorer are referenced without noting their cross-platform availability. The documentation assumes the reader is using PowerShell, which is natively available only on Windows (though installable elsewhere), and does not provide Linux/macOS-specific guidance or examples.
Recommendations
  • Add equivalent examples using Azure CLI and/or Bash/curl for REST API calls, which are natively available on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and provide installation instructions or links.
  • Provide guidance for authenticating and managing Azure resources using cross-platform tools.
  • List cross-platform alternatives for Azure Storage Explorer and clarify its OS support.
  • Present examples for both Windows and Linux/macOS users, or use neutral, cross-platform tools first (e.g., Azure CLI, curl).
GitHub Create Pull Request
Data Factory Troubleshoot security and access control issues ...tory/security-and-access-control-troubleshoot-guide.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation demonstrates a moderate Windows bias, particularly in troubleshooting steps for DNS and connectivity issues. Windows-specific tools (PsPing.exe), file paths (C:\Windows\System32\drivers\etc), and editors (Notepad) are referenced exclusively, with no Linux/macOS equivalents or instructions. Examples and screenshots are Windows-centric, and Linux alternatives (e.g., using ping, editing /etc/hosts) are not mentioned. This may create friction for users running self-hosted IR on Linux VMs or macOS.
Recommendations
  • Provide Linux/macOS equivalents for all Windows-specific instructions, such as using 'ping' and editing '/etc/hosts' with nano or vi.
  • Mention cross-platform tools (e.g., 'ping' is available on all platforms; suggest 'nc' or 'curl' for port checks on Linux/macOS).
  • Include Linux/macOS file paths and commands alongside Windows examples.
  • Add screenshots or command-line examples for Linux environments where relevant.
  • Clarify that self-hosted IR can run on Linux and provide parity in troubleshooting steps.
GitHub Create Pull Request
Data Factory Branching in Azure Data Factory pipeline ...ob/main/articles/data-factory/tutorial-control-flow.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows users. All code examples use Visual Studio and the .NET SDK, with explicit instructions for Visual Studio 2019 and NuGet Package Manager (PowerShell-based). There are no examples or guidance for Linux/macOS users, such as using .NET Core/SDK on Linux, VS Code, or CLI alternatives. Azure Storage Explorer is cross-platform, but its installation instructions are not platform-specific. The lack of Linux/macOS instructions may prevent non-Windows users from following the tutorial easily.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as using .NET Core SDK and VS Code.
  • Include CLI-based package installation (e.g., 'dotnet add package') rather than only NuGet Package Manager Console.
  • Clarify that Azure Storage Explorer is available for Linux/macOS and link to platform-specific installation guides.
  • Offer sample scripts and project setup steps for cross-platform environments.
  • Mention alternative editors (VS Code, JetBrains Rider) and how to run the code outside Visual Studio.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., authentication, SDK compatibility).
GitHub Create Pull Request
Data Factory Use custom activities in a pipeline ...s/data-factory/transform-data-using-custom-activity.md
Medium Priority View Details →
Scanned: 2026-01-12 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 page exhibits a notable Windows bias. PowerShell commands are used exclusively for Azure Batch account and pool creation, as well as for pipeline execution and monitoring. Windows-specific tools and patterns (e.g., .exe applications, cmd commands) are referenced throughout, with no equivalent Bash, Linux shell, or cross-platform examples. The documentation assumes the use of Windows executables and command syntax, and does not provide guidance for Linux/macOS users on running shell scripts or using non-Windows tooling.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for all PowerShell commands, especially for creating Batch accounts/pools and running pipelines.
  • Include examples of custom activities that execute Linux shell scripts (e.g., .sh files) or commands (e.g., bash -c 'echo hello world') in addition to Windows .exe and cmd examples.
  • Clarify that Azure Batch pools can use Linux VM images, and provide sample configurations and commands for Linux-based pools.
  • Explicitly mention cross-platform considerations for custom applications, including how to deploy and run Python, Java, or shell scripts.
  • Reorder examples to present Windows and Linux options side by side, or alternate which platform is shown first.
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
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias by exclusively referencing Windows tools (SQL Server Management Studio), omitting Linux/macOS alternatives for SQL Server management, and implicitly assuming a Windows environment for the self-hosted integration runtime setup. No Linux or cross-platform instructions are provided for key steps, such as creating the SQL Server database/table or installing the integration runtime, which may create friction for non-Windows users.
Recommendations
  • Include instructions for managing SQL Server from Linux/macOS, such as using Azure Data Studio, sqlcmd, or other cross-platform tools.
  • Explicitly mention and link to the self-hosted integration runtime installation guides for Linux and macOS, if supported, or clarify platform requirements.
  • Provide example commands for database/table creation using sqlcmd or Azure Data Studio, not just SQL Server Management Studio.
  • Add notes or sections highlighting any platform-specific limitations or requirements.
  • Ensure screenshots and UI references are not Windows-centric where possible.
GitHub Create Pull Request
Data Factory Provision the Azure-SSIS integration runtime ...es/data-factory/tutorial-deploy-ssis-packages-azure.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias by referencing Windows-centric tools (SSDT, SSMS, dtutil, AzureDTExec) as the primary or only means to deploy and manage SSIS packages. PowerShell is mentioned for firewall configuration without Linux CLI alternatives. There are no explicit Linux/macOS examples or guidance, and Windows tools are presented as the default/familiar approach, with no mention of cross-platform or Linux-native options.
Recommendations
  • Include instructions and examples for using Azure CLI and Bash for tasks currently described with PowerShell (e.g., configuring firewall rules).
  • Clarify which tools (SSDT, SSMS, dtutil, AzureDTExec) are available on Linux/macOS, and provide alternatives or workarounds for users on those platforms.
  • Reference cross-platform management options (such as Azure Data Studio, which is available on Linux/macOS) for deploying and managing SSIS packages.
  • Explicitly state platform requirements and provide links to installation guides for Linux/macOS where possible.
  • Reorder examples so that platform-neutral or cross-platform approaches are shown first, or in parallel with Windows-specific instructions.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation assumes the use of SQL Server Management Studio (SSMS) for database setup, which is a Windows-only tool, and does not mention or provide alternatives for Linux/macOS users (such as Azure Data Studio or command-line tools). All examples and instructions for setting up the SQL Server source are Windows-centric, with no guidance for non-Windows environments. The installation of the self-hosted integration runtime is described generically, but screenshots and instructions imply a Windows workflow. There is no mention of Linux/macOS compatibility or alternative steps.
Recommendations
  • Add instructions and examples for setting up the SQL Server source using cross-platform tools like Azure Data Studio, sqlcmd, or other Linux/macOS-compatible clients.
  • Explicitly mention that the self-hosted integration runtime is available for Linux and macOS, and provide installation steps and screenshots for those platforms.
  • Ensure that all prerequisites and setup steps are platform-agnostic or provide parallel instructions for Linux/macOS users.
  • List platform compatibility for all required tools at the start of the tutorial.
GitHub Create Pull Request
Data Factory Transform data using Spark in Azure Data Factory ...ta-factory/tutorial-transform-data-spark-powershell.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively uses Azure PowerShell for all deployment, pipeline creation, and monitoring steps, with no mention of cross-platform alternatives such as Azure CLI, Bash, or REST API. All command-line examples are PowerShell scripts, and the prerequisites section only references Azure PowerShell, which is most commonly used on Windows. There are no Linux/macOS-specific instructions or examples, and no guidance on how to perform these tasks on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI commands for all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS and provide installation instructions for those platforms.
  • Include Bash script examples or REST API alternatives for key steps such as resource creation, pipeline deployment, and monitoring.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
  • Add a section or callout for Linux/macOS users, clarifying any differences or additional steps.
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
Medium Priority View Details →
Scanned: 2026-01-12 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 demonstrates a notable Windows bias by exclusively referencing Azure PowerShell, Windows file paths, and Windows-specific configuration steps (such as editing C:\Windows\System32\drivers\etc\hosts). There are no Linux/macOS equivalents or instructions for key steps like installing Azure PowerShell, editing the hosts file, or running the self-hosted integration runtime installer. This creates friction for Linux/macOS users attempting to follow the tutorial.
Recommendations
  • Provide Linux/macOS equivalents for Azure PowerShell installation and usage, or mention Azure CLI as an alternative.
  • Include instructions for editing the hosts file on Linux/macOS (e.g., /etc/hosts) when DNS changes are needed.
  • Clarify whether the self-hosted integration runtime can be installed on Linux VMs, and if so, provide installation steps.
  • Avoid referencing only Windows file paths; use OS-agnostic language or provide both Windows and Linux/macOS examples.
  • Explicitly state OS requirements or compatibility for each major step.
GitHub Create Pull Request
Data Factory Transform data by using Spark in Azure Data Factory ...s/data-factory/tutorial-transform-data-spark-portal.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the prerequisites section, where only Azure PowerShell is mentioned for interacting with Azure resources and no Linux/macOS alternatives (such as Azure CLI or cross-platform upload instructions) are provided. The rest of the tutorial is focused on the Azure Portal UI, which is cross-platform, but the initial setup may create friction for non-Windows users.
Recommendations
  • Add instructions for using Azure CLI to upload files to Azure Blob Storage, which works on Linux, macOS, and Windows.
  • Explicitly mention that Azure PowerShell is optional and provide links to Azure CLI installation/configuration guides.
  • Include example commands for uploading files using Azure CLI and/or azcopy, and note that these tools are cross-platform.
  • Clarify that the Azure Portal UI steps are platform-independent.
GitHub Create Pull Request
Data Factory Datasets ...cles/data-factory/concepts-datasets-linked-services.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is highlighted as a primary automation tool, and Windows-centric tools (PowerShell, .NET) are listed before cross-platform or Linux-friendly options. There are no explicit Linux/macOS CLI examples (e.g., Bash, Azure CLI), and the quickstart/tutorial links prioritize Windows tools. This may create friction for Linux/macOS users seeking parity.
Recommendations
  • Add Azure CLI and Bash examples for dataset creation and management, alongside PowerShell and .NET.
  • Explicitly mention cross-platform support for REST API and Azure portal, and clarify which tools work on Linux/macOS.
  • Reorder tool lists to present cross-platform options (REST API, Azure CLI, portal) before Windows-specific tools.
  • Include quickstart/tutorial links for Azure CLI and Bash, if available.
  • Add a note on platform compatibility for each tool/SDK mentioned.
GitHub Create Pull Request
Data Factory Pipeline parameters and variables ...articles/data-factory/concepts-parameters-variables.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a Windows bias primarily in the 'Related content' section, where all step-by-step tutorials reference PowerShell, a Windows-centric tool, without mention of Linux/macOS alternatives (such as Bash, Azure CLI, or cross-platform SDKs). No Linux-specific examples or instructions are provided, and Windows tools are referenced first and exclusively.
Recommendations
  • Add equivalent tutorials using Azure CLI or Bash for Linux/macOS users.
  • Explicitly mention cross-platform options and provide links to relevant documentation.
  • Where PowerShell is referenced, note its availability on Linux/macOS or provide alternative commands.
  • Ensure that screenshots and UI instructions are not Windows-specific, or clarify cross-platform parity.
GitHub Create Pull Request
Data Factory Pipelines and activities ...articles/data-factory/concepts-pipelines-activities.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, primarily through its reliance on PowerShell-based walkthroughs and examples. References to 'Quickstart' and 'Tutorial' guides consistently point to PowerShell instructions, with no mention of Linux/macOS CLI equivalents (such as Bash or Azure CLI). The absence of Linux/macOS-specific examples or guidance may create friction for non-Windows users, although the core concepts and JSON samples are platform-neutral.
Recommendations
  • Provide equivalent walkthroughs and tutorials using Azure CLI and Bash scripts, and link to them alongside PowerShell guides.
  • Explicitly mention that pipelines and activities can be managed from Linux/macOS environments, and provide instructions for those platforms.
  • Add sample commands and screenshots for Linux/macOS users where UI or scripting is discussed.
  • Ensure that references to external guides (Quickstart, Tutorial) include both PowerShell and cross-platform CLI options.
GitHub Create Pull Request
Data Factory Configure performance for the Azure-SSIS Integration Runtime ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/configure-azure-ssis-integration-runtime-performance.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exclusively provides PowerShell-based configuration examples and references, with no mention of Linux/macOS CLI alternatives (such as Bash, Azure CLI, or ARM templates). The scripting and automation guidance is Windows-centric, potentially creating friction for users on Linux or macOS platforms who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent configuration examples using Azure CLI and/or Bash scripts, which are cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, if PowerShell must be used, and provide installation guidance.
  • Reference ARM template or REST API options for configuration, which are platform-agnostic.
  • Ensure that links to tutorials or further reading include Linux/macOS instructions where relevant.
GitHub Create Pull Request
Data Factory Troubleshoot connectors .../articles/data-factory/connector-troubleshoot-guide.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias primarily in the FIPS troubleshooting section, where instructions and file paths are exclusively for Windows (e.g., C:\Program Files\Microsoft Integration Runtime). There are no equivalent instructions or file paths for Linux or macOS users. The page generally avoids OS-specific commands elsewhere, but when platform details are given, Windows is assumed and Linux is omitted.
Recommendations
  • Add troubleshooting steps and file paths for Linux/macOS installations of Self-hosted Integration Runtime, if supported.
  • Explicitly state OS support and limitations for Self-hosted IR, including any differences in configuration or error resolution.
  • Where file edits or configuration changes are required, provide parallel instructions for Linux (e.g., typical install paths, config file locations, restart commands).
  • If Self-hosted IR is Windows-only, clarify this early in the documentation to set expectations for Linux/macOS users.
GitHub Create Pull Request
Data Factory Copy data from Vertica ...s/blob/main/articles/data-factory/connector-vertica.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 the Vertica ODBC driver installation section, where only Windows installation steps and screenshots are provided. There are no instructions or examples for installing the Vertica ODBC driver on Linux or macOS, nor is there mention of equivalent Linux tools or processes. This omission may create friction for users running self-hosted integration runtime on non-Windows platforms.
Recommendations
  • Add explicit instructions and screenshots for installing the Vertica ODBC driver on Linux (and macOS if supported), including relevant commands and package manager usage.
  • Mention Linux-specific tools (e.g., unixODBC) and configuration steps, such as editing odbc.ini and odbcinst.ini.
  • Clarify platform compatibility for the self-hosted integration runtime and Vertica ODBC driver, and provide troubleshooting tips for non-Windows environments.
  • Present installation examples for both Windows and Linux/macOS side by side, or clearly indicate platform-specific sections.
GitHub Create Pull Request
← Previous Page 8 of 13 Next →