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 126-150 of 1000 flagged pages
Data Factory Programmatically monitor an Azure Data Factory ...main/articles/data-factory/monitor-programmatically.md
High Priority View Details →
Scanned: 2026-01-11 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 provides extensive PowerShell and Windows-centric examples for monitoring Azure Data Factory pipelines, especially in the REST API and PowerShell sections. REST API usage is demonstrated exclusively with PowerShell scripts, and there are no equivalent Linux shell (bash/curl) examples. Windows tools (PowerShell, Write-Host, Get-Date) are used without mention of cross-platform alternatives. The ordering and emphasis on PowerShell and Windows tools may make the documentation less accessible for Linux or macOS users.
Recommendations
  • Add bash/curl examples for REST API usage alongside PowerShell scripts.
  • Explicitly mention that PowerShell examples are primarily for Windows, and provide Linux/macOS alternatives where possible.
  • Include cross-platform command-line examples (e.g., using Python, bash, curl) for monitoring pipelines.
  • Clarify tool requirements and platform compatibility in each section.
  • Balance the ordering so that Windows and Linux examples are presented with equal prominence.
GitHub Create Pull Request
Data Factory BCDR for Azure Data Factory and Azure Synapse Analytics Pipelines ...n/articles/data-factory/pipelines-disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-11 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 bias toward Windows environments by providing automation examples and references primarily using Azure PowerShell and Windows-centric tooling. There are no equivalent examples or instructions for Linux or cross-platform CLI tools (such as Azure CLI or Bash scripting). Automation of private endpoint creation and trigger management is described only with PowerShell, and no Linux-native or cross-platform alternatives are mentioned.
Recommendations
  • Provide equivalent examples using Azure CLI (az), which is cross-platform and works on Linux, macOS, and Windows.
  • Include Bash scripting samples for automation tasks, such as disabling triggers or creating private endpoints.
  • Explicitly mention that all automation steps can be performed on Linux and macOS, and link to relevant documentation.
  • When referencing scripts or APIs, offer both PowerShell and CLI/Bash alternatives, and present them side-by-side or in parallel sections.
  • Avoid referencing Windows-only tools (such as Visio) without offering open formats or alternatives (e.g., SVG, PNG, or draw.io files).
GitHub Create Pull Request
Data Factory Create an Azure Data Factory using Bicep ...s/data-factory/quickstart-create-data-factory-bicep.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: Notepad is suggested as the text editor for file creation, which is a Windows-specific tool; Azure PowerShell examples are provided alongside Azure CLI, with PowerShell listed as a primary option throughout; file paths and commands use Windows conventions; and there is no mention of Linux-specific editors or shell environments. The documentation does not offer Linux-specific alternatives or examples for file creation, nor does it acknowledge cross-platform differences in command usage or tooling.
Recommendations
  • Suggest cross-platform text editors (e.g., VS Code, nano, vim) alongside Notepad for file creation.
  • Explicitly mention that Azure CLI and PowerShell are available on both Windows and Linux, and clarify any platform-specific differences.
  • Provide Linux shell examples (e.g., using touch, echo, or nano to create files) in addition to Windows instructions.
  • Avoid Windows-centric terminology and tools unless necessary, or ensure Linux/macOS equivalents are given equal prominence.
  • Include notes or tabs for Linux/macOS users where file paths, command syntax, or tooling may differ.
GitHub Create Pull Request
Data Factory Troubleshoot security and access control issues ...tory/security-and-access-control-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias in several areas: troubleshooting steps and examples consistently reference Windows tools (e.g., PsPing, editing the Windows hosts file), and do not provide equivalent Linux commands or instructions. The only OS-specific example for host file modification is for Windows, with no mention of Linux or macOS. Windows command-line tools are referenced first and exclusively, and there is no parity for Linux troubleshooting scenarios.
Recommendations
  • Provide Linux equivalents for all Windows-specific troubleshooting steps, such as using 'ping' and 'nc' (netcat) or 'curl' for connectivity tests, and instructions for editing '/etc/hosts' on Linux.
  • Include screenshots or command examples for Linux and macOS environments where applicable.
  • When referencing tools like PsPing, mention cross-platform alternatives or clarify OS requirements.
  • Structure troubleshooting steps so that Windows and Linux instructions are presented together, or clearly indicate which steps apply to which OS.
  • Add notes or links to official Microsoft documentation for Linux-specific integration runtime setup and troubleshooting.
GitHub Create Pull Request
Data Factory Transform data using Hadoop Hive activity ...icles/data-factory/transform-data-using-hadoop-hive.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing a tutorial that uses PowerShell ('Tutorial: transform data') as a prerequisite for understanding the Hive activity. There are no Linux shell (bash) or cross-platform CLI examples, and the only example of script path uses Windows-style backslashes. There is no mention of Linux tools or patterns, nor are Linux equivalents presented alongside or before Windows-centric instructions.
Recommendations
  • Provide Linux/bash examples for running Hive activities, including CLI commands and script path conventions (use forward slashes).
  • Reference tutorials that use cross-platform tools (e.g., Azure CLI, bash) in addition to or instead of PowerShell.
  • Clarify that both Windows and Linux environments are supported, and ensure examples are platform-neutral or offer both variants.
  • Avoid using Windows-style path separators in examples unless specifically discussing Windows environments; use forward slashes for platform neutrality.
  • Add explicit instructions or links for users working from Linux/macOS environments.
GitHub Create Pull Request
Data Factory Create Azure Data Factory using .NET SDK ...data-factory/quickstart-create-data-factory-dot-net.md
High Priority View Details →
Scanned: 2026-01-11 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 is heavily oriented towards Windows development environments. It exclusively references Visual Studio (Windows-only), provides instructions for using the NuGet Package Manager Console (PowerShell-based), and omits any mention of Linux or cross-platform alternatives for project creation, package management, or running the code. No Linux-specific tools or workflows (such as VS Code, dotnet CLI, or Bash) are mentioned, and all examples assume a Windows setup.
Recommendations
  • Add instructions for creating and running the .NET project using the cross-platform dotnet CLI (e.g., 'dotnet new console', 'dotnet add package').
  • Include guidance for using VS Code or other cross-platform editors, not just Visual Studio.
  • Provide Linux and macOS-specific notes for prerequisites, project setup, and running the code.
  • Replace or supplement PowerShell/NuGet Package Manager Console commands with Bash or dotnet CLI equivalents.
  • Mention cross-platform tools for verifying output (e.g., Azure Storage Explorer is cross-platform, but clarify installation for Linux/macOS).
  • Explicitly state that the .NET SDK and Azure libraries are cross-platform and can be used on Linux/macOS, not just Windows.
GitHub Create Pull Request
Data Factory Create an Azure Data Factory using REST API ...ata-factory/quickstart-create-data-factory-rest-api.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a strong Windows bias by exclusively using PowerShell for all command-line examples and automation steps. It requires Azure PowerShell to be installed and assumes the use of Windows tools such as Azure Storage Explorer, with no mention of Linux-native alternatives or cross-platform command-line tools. There are no bash, curl, or az CLI examples, nor any guidance for Linux or macOS users. Windows-specific patterns (e.g., PowerShell scripting, Windows authentication prompts) are presented as the default and only workflow.
Recommendations
  • Add equivalent bash/curl examples for REST API calls, suitable for Linux and macOS users.
  • Include az CLI commands for all major steps (authentication, resource creation, pipeline management) to provide a cross-platform alternative.
  • Mention and demonstrate Linux-compatible tools for Azure Blob Storage management, such as azcopy or CLI commands, alongside Azure Storage Explorer.
  • Clearly indicate that PowerShell is not required and provide instructions for Linux/macOS environments.
  • Reorder sections or provide parallel workflows so that Windows and Linux/macOS users are equally supported from the start.
  • Add a note at the beginning clarifying platform support and linking to cross-platform documentation.
GitHub Create Pull Request
Data Factory Configure a self-hosted integration runtime as a proxy for SSIS ...-factory/self-hosted-integration-runtime-proxy-ssis.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a clear Windows bias. All examples and instructions assume a Windows environment, referencing Windows-specific tools (PowerShell, Local Security Policy, NT SERVICE accounts, Visual Studio/SSDT, SSMS), file paths (C:\ProgramData), and authentication mechanisms (Windows Authentication). There are no Linux or cross-platform alternatives provided for installation, configuration, or debugging. The use of PowerShell is exclusive, and no Bash or Linux CLI equivalents are mentioned. The documentation does not address how to set up or operate a self-hosted IR proxy for SSIS on Linux, nor does it clarify platform limitations.
Recommendations
  • Explicitly state platform requirements and limitations at the beginning of the documentation, clarifying if self-hosted IR proxy for SSIS is Windows-only.
  • If Linux support exists or is planned, provide equivalent instructions for Linux environments, including installation, configuration, and troubleshooting steps.
  • Offer Bash or cross-platform CLI examples alongside PowerShell commands.
  • Reference Linux authentication and service management equivalents (e.g., systemd service accounts, PAM policies) where applicable.
  • Clarify whether tools like SSDT, SSMS, and Visual Studio are required and if there are Linux alternatives or workarounds.
  • Provide guidance on log locations and debugging for Linux (e.g., /var/log/...) if supported.
  • If Linux is not supported, make this explicit to avoid confusion for cross-platform users.
GitHub Create Pull Request
Data Factory Troubleshoot SSIS Integration Runtime management ...ry/ssis-integration-runtime-management-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by referencing PowerShell cmdlets and recommending the use of SSMS (SQL Server Management Studio), both of which are traditionally Windows-centric tools. There are no Linux-specific troubleshooting examples or alternative tool suggestions (e.g., Azure CLI, sqlcmd, Data Studio). The guidance assumes the reader is using Windows environments and tools, with no mention of Linux equivalents or cross-platform approaches.
Recommendations
  • Provide troubleshooting examples using Azure CLI and/or Bash scripts alongside PowerShell cmdlets.
  • Mention cross-platform tools such as Azure Data Studio and sqlcmd for SQL Server access and troubleshooting.
  • Clarify that SSIS IR management can be performed from Linux or macOS environments, and provide relevant steps or caveats.
  • Include explicit Linux troubleshooting steps or references where applicable (e.g., connecting to SQL Database from a Linux VM).
  • Balance tool recommendations by listing both Windows and Linux options, and avoid assuming SSMS or PowerShell as the default.
GitHub Create Pull Request
Data Factory Self-hosted integration runtime autoupdate and expire notification ...factory/self-hosted-integration-runtime-auto-update.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a Windows bias by exclusively providing PowerShell-based examples and commands for managing self-hosted integration runtime updates and expiration notifications. All tooling references (client screenshots, PowerShell, and Azure CLI usage within PowerShell scripts) assume a Windows environment, with no mention of Linux equivalents, shell scripts, or cross-platform alternatives. The documentation does not address how Linux users should perform these tasks, nor does it clarify whether the self-hosted integration runtime client is available or supported on Linux.
Recommendations
  • Provide equivalent examples using Bash shell scripts and native Azure CLI commands for Linux/macOS users.
  • Clarify platform support for the self-hosted integration runtime client and portal features (e.g., is there a Linux client?).
  • Add explicit instructions or notes for Linux users on how to check versions, schedule updates, and handle expiration notifications.
  • Where possible, use cross-platform tooling (e.g., pure Azure CLI, REST API) in examples, or offer both Windows and Linux variants side-by-side.
  • Review screenshots and UI references to ensure they are not Windows-specific, or provide Linux alternatives if available.
GitHub Create Pull Request
Data Factory Source control ...docs/blob/main/articles/data-factory/source-control.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is referenced as a primary method for interacting with Azure Data Factory outside of the UI, and troubleshooting sections mention updating properties via PowerShell or the REST API, but do not provide equivalent Linux shell or cross-platform CLI examples. Windows tools and patterns (such as Visual Studio, Azure Portal, and PowerShell) are mentioned, while Linux alternatives (e.g., Bash, Azure CLI) are not discussed. Windows-specific browser issues (Microsoft Edge) are called out, but no mention is made of Linux browsers. The order of presentation also tends to favor Windows-centric tools and workflows before mentioning alternatives.
Recommendations
  • Add Linux/Bash/Azure CLI examples alongside PowerShell commands for configuration and troubleshooting tasks.
  • Mention cross-platform tools (e.g., Azure CLI, REST API via curl) wherever PowerShell is referenced.
  • Include notes or troubleshooting steps for popular Linux browsers (e.g., Firefox, Chrome) in addition to Microsoft Edge.
  • Explicitly state that all configuration steps can be performed on Linux, macOS, and Windows, and provide parity in instructions.
  • Where Visual Studio or Windows-specific URLs/tools are referenced, offer equivalent guidance for Linux users (e.g., VS Code, CLI).
GitHub Create Pull Request
Data Factory Use custom activities in a pipeline ...s/data-factory/transform-data-using-custom-activity.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates a strong Windows bias. PowerShell commands are used exclusively for Azure Batch account and pipeline management, with no mention of equivalent Azure CLI or Bash commands. Examples of custom activities use Windows executables (.exe) and Windows command syntax (e.g., 'cmd /c dir', 'cmd /c echo hello world'), with no Linux shell or cross-platform examples. Windows tools and patterns are referenced first and exclusively, while Linux alternatives are absent.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all management tasks (e.g., creating Batch accounts, pools, running pipelines, retrieving outputs).
  • Provide sample custom activities using Linux executables (e.g., shell scripts, Python scripts) and Linux command syntax (e.g., '/bin/bash -c "echo hello world"').
  • Explicitly mention how to configure Azure Batch pools with Linux VM images and provide examples for both Windows and Linux pool configurations.
  • Clarify cross-platform support for custom activities, including any OS-specific considerations for command syntax, file paths, and application packaging.
  • Ensure that references to Windows tools (e.g., .exe, cmd) are balanced with Linux equivalents (e.g., .sh, bash), and provide guidance for users on both platforms.
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-11 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 by exclusively using Windows-based tools (Visual Studio, Azure Storage Explorer) and providing only C#/.NET examples for pipeline creation and management. There are no Linux or cross-platform alternatives mentioned, nor are there instructions for using Linux-native tools or SDKs (such as Python or CLI). Installation and workflow steps assume a Windows environment, and PowerShell is referenced for NuGet package installation without Linux equivalents.
Recommendations
  • Provide equivalent instructions for Linux users, such as using VS Code or JetBrains Rider for .NET development, or using the Azure CLI and Python SDK for Data Factory operations.
  • Include examples for creating and managing Data Factory pipelines using Python, Azure CLI, or REST API, which are cross-platform.
  • Mention Linux-compatible tools for interacting with Azure Blob Storage, such as azcopy, Azure CLI, or third-party file managers.
  • Add notes or sections on how to install and use the Azure .NET SDK on Linux (e.g., via .NET Core), and clarify any platform-specific requirements.
  • Offer alternative package management instructions for Linux, such as using dotnet CLI for NuGet packages instead of PowerShell.
  • Explicitly state that the tutorial is Windows-centric and provide links or references to Linux/macOS tutorials where available.
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-11 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 Windows bias by exclusively referencing Windows-based tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and managing SSIS packages, with no mention of Linux-compatible alternatives or cross-platform usage. All examples and tool recommendations assume a Windows environment, and there are no instructions or guidance for Linux users. PowerShell is mentioned for firewall configuration, but Bash or CLI alternatives are not provided. The documentation implicitly assumes readers are using Windows, both in tool selection and workflow descriptions.
Recommendations
  • Include instructions and examples for using Azure Data Factory and SSIS from Linux environments, such as Azure CLI or Bash scripts for provisioning and configuration tasks.
  • Mention cross-platform alternatives to SSMS and SSDT, or clarify their availability (e.g., Azure Data Studio, which is available on Linux and macOS).
  • Provide dtutil and AzureDTExec usage notes for Linux, or clarify their platform support and recommend alternatives if not available.
  • When referencing PowerShell for tasks like firewall rule creation, also provide equivalent Azure CLI or REST API examples.
  • Explicitly state platform requirements and limitations for each tool, and guide Linux/macOS users to supported workflows.
  • Consider reordering tool mentions so that cross-platform or cloud-native options are listed before or alongside Windows-specific tools.
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-11 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). There are no instructions or examples for Linux systems, such as using OpenSSL, Linux certificate stores, or Linux service accounts. The prerequisites and requirements also reference Windows Server and CSP, with no mention of Linux equivalents.
Recommendations
  • Add Linux-specific instructions for generating and installing certificates, such as using OpenSSL and managing certificates in /etc/ssl or with update-ca-certificates.
  • Provide command-line examples for Linux (bash) alongside PowerShell, e.g., retrieving FQDNs with 'hostname -f'.
  • Include steps for configuring integration runtime nodes on Linux, including certificate permissions and service account management.
  • Clarify which features are Windows-only and provide alternatives or workarounds for Linux environments.
  • Mention Linux-supported key formats and providers, and note any limitations or requirements for Linux deployments.
GitHub Create Pull Request
Data Factory Transform data ...docs/blob/main/articles/data-factory/transform-data.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates subtle Windows bias. Windows is mentioned before Linux in several places (e.g., 'Windows/Linux-based HDInsight cluster'), and SQL Server (a Windows-centric technology) is the only example given for stored procedures. The only tutorial linked is for Spark using PowerShell, a Windows-native tool, with no Linux/bash equivalent. There is a general lack of Linux-specific examples, and Windows tools/patterns are referenced first or exclusively.
Recommendations
  • Provide Linux/bash examples alongside PowerShell tutorials, especially in the 'Related content' section.
  • Mention Linux before or alongside Windows when listing supported platforms (e.g., 'Linux/Windows-based HDInsight cluster').
  • Include examples for non-Windows databases (e.g., PostgreSQL, MySQL) in the stored procedure section.
  • Add references to Linux-native tools and workflows where appropriate.
  • Ensure parity in example scripts and walkthroughs for both Windows and Linux users.
GitHub Create Pull Request
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-11 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 is heavily oriented toward Windows environments. It exclusively uses Visual Studio and .NET SDK for the walkthrough, with no mention of Linux-compatible alternatives (such as VS Code, CLI, or Python SDK). All tooling instructions (e.g., using Notepad, SQL Server Management Studio, Visual Studio, NuGet Package Manager Console) are Windows-centric. There are no Linux or cross-platform code samples, nor guidance for users on Linux or macOS. The only reference to further tutorials is a PowerShell-based page, reinforcing the Windows-first approach.
Recommendations
  • Add equivalent instructions for Linux and macOS users, such as using VS Code or JetBrains Rider instead of Visual Studio.
  • Provide examples using Azure Data Factory's Python SDK and Azure CLI, which are cross-platform.
  • Include instructions for installing required packages via pip (for Python) or dotnet CLI (for .NET Core), not just NuGet Package Manager Console.
  • Replace Notepad with a generic text editor (e.g., nano, vim, VS Code) for file creation.
  • Mention SQL management tools available on Linux/macOS (e.g., Azure Data Studio) instead of only SSMS and Visual Studio.
  • Ensure all code samples and steps are runnable on Linux and macOS, or provide parallel sections for those platforms.
  • Link to cross-platform tutorials and avoid referencing only PowerShell-based next steps.
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-11 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 clear Windows bias. It exclusively references Windows tools such as SQL Server Management Studio (SSMS) for database setup, and the instructions for installing the self-hosted integration runtime assume a Windows environment (e.g., 'express setup for this computer', running a downloaded application). There are no examples or guidance for Linux users, such as using sqlcmd or Azure Data Studio, nor is there mention of Linux-compatible installation steps for the integration runtime. The documentation also introduces Windows tools and patterns before any cross-platform alternatives, if any exist.
Recommendations
  • Add instructions for setting up the SQL Server database using Linux-compatible tools (e.g., sqlcmd, Azure Data Studio).
  • Include guidance on installing and registering the self-hosted integration runtime on Linux machines, with explicit steps and screenshots.
  • Mention cross-platform alternatives to SSMS early in the prerequisites section.
  • Where possible, provide parity in examples and screenshots for both Windows and Linux environments.
  • Clarify any platform-specific limitations or requirements for the integration runtime and the Copy Data tool.
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-11 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. It exclusively references SQL Server Management Studio (SSMS), a Windows-only tool, for database setup and management, with no mention of Linux alternatives (such as Azure Data Studio or command-line tools). Instructions for installing and running the self-hosted integration runtime are written generically but implicitly assume a Windows desktop experience, with no explicit guidance for Linux users. There are no Linux-specific examples or troubleshooting notes, and Windows conventions (e.g., domain\user notation) are used without Linux equivalents.
Recommendations
  • Add instructions for setting up the SQL Server database using cross-platform tools such as Azure Data Studio or sqlcmd, including Linux installation steps.
  • Provide explicit guidance for installing and running the self-hosted integration runtime on Linux, including screenshots and troubleshooting notes.
  • Include Linux-specific examples for authentication, file paths, and environment setup.
  • Reference Linux-compatible browsers (such as Firefox) for accessing the Azure Data Factory UI.
  • Where Windows conventions are used (e.g., domain\user), add Linux equivalents or clarifying notes.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools and workflows. Azure PowerShell is listed as a prerequisite with no mention of Azure CLI or Bash alternatives. Instructions for editing the hosts file are given only for Windows (C:\Windows\System32\drivers\etc), with no Linux equivalent. The process for installing and registering the self-hosted integration runtime is described in a way that assumes a Windows VM, with no guidance for Linux VMs. There are no Linux-specific examples, commands, or screenshots, and Windows terminology and paths are used throughout.
Recommendations
  • Add instructions for using Azure CLI and Bash as alternatives to Azure PowerShell for all relevant steps.
  • Include guidance for editing the hosts file on Linux VMs (e.g., /etc/hosts) alongside the Windows instructions.
  • Provide explicit steps and screenshots for installing and registering the self-hosted integration runtime on Linux VMs.
  • Use OS-agnostic terminology and file paths where possible, or present both Windows and Linux variants in parallel.
  • Ensure that all code samples, configuration steps, and troubleshooting tips are available for both Windows and Linux environments.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All command-line instructions are provided exclusively using Azure PowerShell, with no mention of Azure CLI, Bash, or cross-platform alternatives. The prerequisites and workflow assume the use of PowerShell, which is native to Windows and only recently available on Linux/macOS. There are no Linux-specific instructions, nor any guidance for users on non-Windows platforms. The documentation does not mention or demonstrate how to perform the same steps using Azure CLI, which is more commonly used on Linux/macOS.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands, including resource group, data factory, linked service, and pipeline creation and deployment.
  • Include notes or sections for Linux/macOS users, specifying any differences in setup or command usage.
  • Mention that PowerShell Core is available cross-platform, but clarify installation steps for Linux/macOS.
  • Add Bash script examples for file uploads to Azure Blob Storage, using tools like azcopy or Azure CLI.
  • Reorder sections or add side-by-side examples so that both Windows (PowerShell) and Linux/macOS (CLI/Bash) users are equally supported.
  • Explicitly state platform requirements and alternatives in the prerequisites section.
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-11 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, with all examples and instructions using PowerShell and Windows-specific tools. The integration runtime installation is described only for Windows, and there are no Linux or cross-platform alternatives mentioned. All command-line examples use PowerShell, and file paths are Windows-style. The use of SQL Server Management Studio and Windows authentication further reinforces the Windows-centric approach.
Recommendations
  • Provide equivalent instructions and examples for Linux environments, including Bash/Azure CLI commands.
  • Document how to install and register the self-hosted integration runtime on Linux (if supported), or clarify platform limitations.
  • Include Linux file path examples and note differences in file system structure.
  • Mention and demonstrate use of cross-platform tools (e.g., Azure CLI, Data Factory REST API) where possible.
  • Clarify authentication options for non-Windows environments and provide examples.
  • Add a section explicitly addressing Linux/macOS users, outlining any differences or limitations.
GitHub Create Pull Request
Data Factory Transform data using Hive in Azure Virtual Network ...actory/tutorial-transform-data-hive-virtual-network.md
High Priority View Details →
Scanned: 2026-01-11 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 focused on Windows and PowerShell, with all command-line examples provided exclusively in PowerShell. Instructions for registering the self-hosted integration runtime reference downloading and installing software on an Azure VM, implicitly assuming a Windows environment (e.g., editing C:\Windows\System32\drivers\etc\hosts). There are no examples or guidance for performing these steps on Linux VMs, nor are cross-platform alternatives (such as Azure CLI or Bash) mentioned. Windows-specific tools and file paths are referenced before any Linux equivalents, which are absent.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell commands.
  • Include instructions for registering the self-hosted integration runtime on Linux VMs, including how to edit /etc/hosts for DNS resolution.
  • Explicitly mention cross-platform compatibility and note any differences in procedure between Windows and Linux environments.
  • Add screenshots or terminal output from Linux environments where relevant.
  • Reference Linux tools and file paths alongside Windows ones, ensuring parity in documentation.
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-11 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 prerequisites, referencing only PowerShell installation instructions, and omitting any mention of Linux or cross-platform CLI alternatives (such as Azure CLI or Bash). There are no examples or guidance for Linux or macOS users, nor are there instructions for uploading files using non-Windows tools.
Recommendations
  • Add instructions for installing and using Azure CLI (az), which is cross-platform, as an alternative to Azure PowerShell.
  • Provide examples for uploading files to Azure Blob Storage using both Azure CLI and PowerShell, and clarify which commands work on Windows, Linux, and macOS.
  • Explicitly mention that the tutorial can be followed from Linux and macOS, and provide any OS-specific notes if necessary.
  • Wherever PowerShell is referenced, add equivalent Bash or shell commands for Linux/macOS users.
  • Review all screenshots and UI instructions to ensure they are not Windows-specific, or add notes/screenshots for other platforms if UI differs.
GitHub Create Pull Request
Data Factory Global parameters ...main/articles/data-factory/author-global-parameters.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 Tools Missing Linux Example
Summary
The documentation references PowerShell scripts as the method for deploying global parameters in CI/CD, without mentioning Linux equivalents (such as Azure CLI, Bash, or cross-platform automation). Windows tooling (PowerShell) is presented as the default or only option, and no Linux/macOS-specific instructions or examples are provided.
Recommendations
  • Add examples for deploying global parameters using Azure CLI, which is cross-platform and works on Linux/macOS.
  • Include Bash script samples for ARM template deployment to demonstrate Linux compatibility.
  • Explicitly mention that PowerShell is one option and provide parity for Linux/macOS users.
  • Clarify that ARM template deployment can be performed from any OS, and link to cross-platform deployment guides.
  • Where screenshots or instructions reference Windows-specific tools, add notes or alternatives for Linux/macOS users.
GitHub Create Pull Request
← Previous Page 6 of 40 Next →