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 251-275 of 319 flagged pages
Data Factory Schedule an Azure-SSIS integration runtime ...tory/how-to-schedule-azure-ssis-integration-runtime.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 Tools Windows First
Summary
The documentation page exhibits a notable Windows bias, particularly in the sections covering monitoring and automation. PowerShell is the only scripting language provided for automation and monitoring examples, and Windows-centric tools such as SQL Server Management Studio are referenced for verification. There are no equivalent Linux/macOS CLI or automation examples, and alternative cross-platform tools are not mentioned. The order of presentation also places Windows/PowerShell approaches before any mention of REST APIs or other platform-neutral methods.
Recommendations
  • Provide equivalent examples using Azure CLI, which is cross-platform, for monitoring and managing pipelines and triggers.
  • Include Bash shell script samples for automation tasks alongside PowerShell scripts.
  • Mention and demonstrate usage of cross-platform database management tools (e.g., Azure Data Studio) for verifying SSIS package runs.
  • Clarify that REST API calls can be made from any OS and provide sample curl commands.
  • Add notes or sections for Linux/macOS users, outlining any differences or additional steps required.
  • Reorder examples so that platform-neutral methods (REST API, Azure portal, Azure CLI) are presented before Windows-specific tools.
GitHub Create Pull Request
Data Factory Assess your Azure Data Factory pipelines for migration to Fabric ...ur-azure-data-factory-to-fabric-data-factory-migration.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page repeatedly references the PowerShell upgrade tool as the primary method for migration, with no mention of Linux/macOS alternatives or cross-platform tools. There are no examples or guidance for users on non-Windows platforms, and PowerShell is presented as the default solution for early migration.
Recommendations
  • Include instructions or references for migration using cross-platform tools such as Azure CLI, REST API, or Fabric portal where possible.
  • Explicitly state whether the PowerShell upgrade tool can be used on Linux/macOS (via PowerShell Core), and provide installation and usage examples for those platforms.
  • Present migration options for Linux/macOS users alongside Windows options, rather than only referencing PowerShell.
  • Add a note clarifying platform compatibility for all recommended tools.
GitHub Create Pull Request
Data Factory Create schedule triggers ...rticles/data-factory/how-to-create-schedule-trigger.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, most notably in the Azure PowerShell section. PowerShell is presented with explicit instructions for installation on Windows, and file paths use Windows conventions (e.g., C:\ADFv2QuickStartPSH\). The PowerShell section appears before the Azure CLI section, which is more cross-platform. There are no explicit Linux/macOS CLI or shell examples, nor is there guidance for using PowerShell on non-Windows platforms. However, the Azure CLI, Python SDK, and .NET SDK sections are platform-agnostic, and the JSON schema is universal.
Recommendations
  • Add explicit instructions for installing and using Azure PowerShell on Linux/macOS, including cross-platform file path examples.
  • Mention that Azure PowerShell is available on Linux/macOS and provide a link to installation instructions for those platforms.
  • Provide Bash or shell script examples for common tasks, or clarify that Azure CLI commands work on all platforms.
  • When referencing file paths, use platform-neutral examples or show both Windows and Unix-style paths.
  • Consider presenting Azure CLI examples before PowerShell to emphasize cross-platform support.
GitHub Create Pull Request
Data Factory Create tumbling window triggers .../data-factory/how-to-create-tumbling-window-trigger.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 Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias, especially in the PowerShell sample section. The PowerShell instructions reference Windows-specific installation and file paths (e.g., C:\ADFv2QuickStartPSH\), and PowerShell is a Windows-centric tool. The CLI section is more cross-platform, but the PowerShell example is presented first and in greater detail, with explicit references to Windows environments and tools. There are no Linux/macOS-specific examples, nor any mention of Bash or shell scripting alternatives.
Recommendations
  • Add explicit Linux/macOS instructions for installing Azure PowerShell and running the CLI commands.
  • Include Bash shell script examples for creating and managing triggers using Azure CLI.
  • Use cross-platform file paths in examples (e.g., ~/ADFv2QuickStart or ./MyTrigger.json) instead of Windows-only paths.
  • Clarify that Azure CLI commands work on Linux/macOS and provide any necessary environment setup steps.
  • Consider presenting CLI examples before PowerShell, or side-by-side, to avoid Windows-first perception.
GitHub Create Pull Request
Data Factory How to ingest data into Fabric using the Azure Data Factory Copy activity ...how-to-ingest-data-into-fabric-from-azure-data-factory.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias, particularly in the authentication section. The only example for forcing a permissions refresh uses PowerShell commands, with no mention of Linux/macOS alternatives. Windows tooling (PowerShell) is referenced exclusively, and no Bash, CLI, or cross-platform methods are provided. The documentation implicitly assumes access to Windows environments, which may create friction for Linux/macOS users.
Recommendations
  • Provide equivalent instructions using Azure CLI, REST API, or Bash scripts for permissions refresh and other administrative tasks.
  • Explicitly note cross-platform options where available, and clarify which steps require Windows-only tools.
  • Add examples and screenshots for Linux/macOS environments where applicable.
  • Reference platform-agnostic tools before or alongside Windows-specific ones.
GitHub Create Pull Request
Data Factory Run SSIS package with Stored Procedure Activity - Azure ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-stored-procedure-activity.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 strong Windows bias, especially in the 'Azure PowerShell' section, which exclusively uses PowerShell scripts and Windows filesystem paths (e.g., C:\ADF\RunSSISPackage). There are no examples or instructions for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform file paths. The page assumes the user is on Windows, both in tooling and workflow, and does not mention alternatives or parity for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works on Linux/macOS.
  • Use generic or platform-neutral file paths in examples (e.g., ./ADF/RunSSISPackage), or provide both Windows and Linux/macOS path formats.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and provide instructions for installing and using it if PowerShell is required.
  • Include notes or sections for Linux/macOS users, outlining any differences or additional steps needed.
  • Where possible, provide Bash script examples for automation tasks.
  • Clarify that the Data Factory UI and Azure Portal are web-based and platform-agnostic, but call out any steps that may differ for non-Windows users.
GitHub Create Pull Request
Data Factory Review deployed resources ...ludes/data-factory-quickstart-verify-output-cleanup.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell commands for resource cleanup, which are primarily used on Windows. There are no equivalent examples for Linux/macOS users (e.g., Azure CLI or Bash), nor is there mention of cross-platform alternatives. This creates friction for non-Windows users who may not have PowerShell installed or prefer native Linux tools.
Recommendations
  • Add Azure CLI examples for deleting resource groups and data factories, as Azure CLI is cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that PowerShell commands require PowerShell Core, and provide installation guidance for non-Windows users if PowerShell is to be used.
  • Present both PowerShell and Azure CLI/Bash examples side-by-side, or indicate which commands are platform-specific.
  • Consider listing Azure CLI commands first or equally to avoid implicit prioritization of Windows tools.
GitHub Create Pull Request
Data Factory include file ...tory/includes/data-factory-quickstart-prerequisites.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (Notepad), using Windows-style file paths (C:\ADFv2QuickStartPSH), and omitting Linux/macOS equivalents for file creation and path conventions. All examples and instructions assume a Windows environment, with no mention of alternative editors or file system paths for Linux or macOS users.
Recommendations
  • Include instructions for creating the sample file using Linux/macOS tools (e.g., nano, vi, or TextEdit) and provide corresponding file paths (e.g., /home/user/ADFv2QuickStartPSH or ~/ADFv2QuickStartPSH).
  • Mention cross-platform text editors and clarify that any text editor can be used.
  • Add notes or examples for Linux/macOS users wherever file system paths or OS-specific tools are referenced.
  • Consider reordering instructions to present cross-platform options first, or side-by-side.
GitHub Create Pull Request
Data Factory Introduction to Azure Data Factory ...e-docs/blob/main/articles/data-factory/introduction.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 Tools Windows First
Summary
The documentation page for Azure Data Factory is generally platform-neutral in its main content, focusing on cloud-based workflows and concepts. However, there is a subtle Windows bias in the 'Related content' section, where PowerShell is listed as the first automation example, and there is no explicit mention of Linux shell (Bash) or CLI examples. Monitoring options mention PowerShell and Azure portal, but do not reference Linux-native tools or workflows. The page does not provide Linux/macOS-specific instructions or parity in automation tooling, which may create friction for non-Windows users.
Recommendations
  • Add Bash/CLI examples and quickstarts alongside PowerShell in the 'Related content' section.
  • Explicitly mention cross-platform support for automation (e.g., Azure CLI, Bash scripts) in relevant sections.
  • Ensure that monitoring and management instructions reference Linux/macOS-compatible tools and workflows.
  • Balance example ordering so that Windows and Linux/macOS options are presented equally or in parallel.
GitHub Create Pull Request
Data Factory Join Azure-SSIS integration runtime to a virtual network ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/join-azure-ssis-integration-runtime-virtual-network.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 Tools Missing Linux Example
Summary
The documentation page references Azure PowerShell as a primary method for provisioning and managing Azure-SSIS IR, and links to PowerShell-specific guides. There are no examples or mentions of Linux/macOS CLI tools (such as Azure CLI or Bash scripts), nor any cross-platform instructions. This creates friction for users on Linux or macOS who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent Azure CLI instructions and examples for all PowerShell-based steps.
  • Explicitly mention cross-platform options (e.g., Azure CLI, REST API) alongside PowerShell.
  • Provide links to Linux/macOS setup guides for Azure-SSIS IR where relevant.
  • Ensure that UI-based instructions clarify platform independence.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides a detailed PowerShell example for creating managed virtual networks and private endpoints in Azure Data Factory, but does not offer equivalent examples for Linux/macOS users (e.g., Azure CLI, REST API, or ARM templates). The only automation example is Windows-centric (PowerShell), and the documentation references Azure PowerShell in its metadata. This creates friction for users on Linux or macOS, who may not have access to or prefer not to use PowerShell.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands shown.
  • Include REST API or ARM template snippets for resource creation to provide platform-neutral options.
  • Explicitly mention that PowerShell is cross-platform, but clarify installation steps for Linux/macOS if PowerShell is required.
  • Present CLI and REST examples before or alongside PowerShell to avoid Windows-first perception.
  • Update metadata to reference Azure CLI if CLI examples are added.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools (SSMS, SSDT, SQL Server Agent) for querying and invoking SSIS package executions, and mentions Azure PowerShell as a method for checking SSIS IR status without offering Linux/macOS alternatives or CLI examples. There are no Linux-specific instructions, nor are cross-platform tools (like Azure CLI) highlighted. Windows tools are mentioned first and exclusively in several key sections.
Recommendations
  • Include Azure CLI examples for checking SSIS IR operational status, as Azure CLI is cross-platform.
  • Mention and provide instructions for querying SSIS logs using cross-platform tools (e.g., Azure Data Studio, Kusto Query Language via web portal).
  • Add notes or examples for invoking SSIS packages from non-Windows environments, if supported.
  • Ensure that references to tools like SSMS, SSDT, and SQL Server Agent are balanced with cross-platform alternatives or clarify their platform limitations.
  • Present examples in a platform-neutral order or explicitly call out platform-specific steps.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, primarily through the use of Azure PowerShell for automation and scripting examples, and by referencing Windows-centric tools (e.g., Visio file download, PowerShell approval API) without providing equivalent Linux/macOS alternatives or examples. There are no explicit Bash, CLI, or cross-platform scripting instructions, and automation steps are described with PowerShell links only.
Recommendations
  • Provide Azure CLI and Bash script examples alongside PowerShell for all automation and scripting tasks, especially for disabling triggers and managing private endpoints.
  • Reference cross-platform tools for architecture diagrams (e.g., SVG, PDF) in addition to Visio files.
  • Explicitly mention that all described procedures can be performed on Linux/macOS, and link to relevant documentation for those platforms.
  • Include notes or sections on how Linux/macOS users can perform the same tasks, especially for CI/CD and pipeline management.
  • Where APIs are referenced (e.g., approval API), provide REST API usage examples, not just PowerShell modules.
GitHub Create Pull Request
Data Factory Self-hosted integration runtime autoupdate and expire notification ...factory/self-hosted-integration-runtime-auto-update.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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 notable Windows bias by exclusively providing PowerShell commands and examples, referencing the 'self-hosted integration runtime client' (a Windows-only tool), and omitting Linux/macOS equivalents or instructions. There are no bash, shell, or cross-platform CLI examples, and Windows-centric tools and workflows are presented as the default or only option.
Recommendations
  • Provide equivalent bash or shell scripts for Linux/macOS users, especially for tasks currently demonstrated with PowerShell.
  • Clarify whether the 'self-hosted integration runtime client' is available on Linux/macOS, and if not, offer alternative methods (e.g., using Azure CLI, REST API, or portal) for those platforms.
  • Explicitly mention platform support and limitations for all tools and commands.
  • Reorder examples to present cross-platform or platform-neutral methods first, followed by platform-specific instructions.
  • Add notes or sections for Linux/macOS users describing how to achieve the same outcomes.
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-11 06:20
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 Windows-centric, with all instructions and examples assuming the use of Visual Studio on Windows. Package installation is shown only via the PowerShell-based NuGet Package Manager Console, and there are no references to Linux/macOS development environments or alternative .NET SDK workflows. The use of Windows-specific tools and terminology (Visual Studio, NuGet Package Manager Console) excludes Linux/macOS users, who may use VS Code, JetBrains Rider, or command-line .NET tools.
Recommendations
  • Add instructions for creating and running the .NET project using cross-platform tools such as the 'dotnet' CLI.
  • Provide package installation commands using 'dotnet add package' for Linux/macOS users.
  • Mention alternative IDEs (VS Code, Rider) and clarify that the .NET SDK and Azure SDKs are cross-platform.
  • Include explicit steps for Linux/macOS users, such as verifying .NET installation, running code from the terminal, and using platform-agnostic commands.
  • Avoid assuming Visual Studio or Windows-only workflows; present steps in a platform-neutral order.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
This documentation page demonstrates a strong Windows bias by exclusively using PowerShell for all command-line examples and instructions. It requires Azure PowerShell for REST API invocation, and all scripts are written in PowerShell syntax. There are no equivalent examples or guidance for Linux/macOS users, such as using Bash, curl, or Azure CLI. Windows tools like Azure Storage Explorer are mentioned without alternatives. The absence of cross-platform instructions creates friction for non-Windows users.
Recommendations
  • Provide equivalent Bash/curl or Azure CLI examples for all REST API operations.
  • Explicitly state that PowerShell is available on Linux/macOS, or provide installation instructions for those platforms.
  • Mention and demonstrate cross-platform tools for Azure Storage management (e.g., azcopy, Azure CLI, or web portal).
  • Reorganize sections so that cross-platform solutions are presented alongside or before Windows-specific instructions.
  • Add notes or links for Linux/macOS users to relevant documentation.
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-11 06:20
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 moderate Windows bias. Troubleshooting steps for network connectivity and DNS resolution use Windows-specific tools (PsPing.exe, Notepad, Windows hosts file path) and do not provide Linux/macOS equivalents. All example commands and file paths are Windows-centric, and instructions for editing the hosts file are only given for Windows. No Linux or macOS troubleshooting guidance is offered for these scenarios.
Recommendations
  • Provide Linux/macOS equivalents for all troubleshooting steps involving command-line tools (e.g., use 'ping', 'nc', or 'curl' for connectivity checks).
  • Include instructions for editing the hosts file on Linux (/etc/hosts) and macOS (/etc/hosts), with appropriate editor commands (e.g., 'sudo nano /etc/hosts').
  • Mention cross-platform alternatives to PsPing (such as 'nc' or 'telnet') and clarify which steps apply regardless of OS.
  • Where screenshots are Windows-specific, add notes or images for Linux/macOS environments.
  • Explicitly state that the troubleshooting applies to both Windows and Linux VMs, and highlight any OS-specific differences.
GitHub Create Pull Request
Data Factory Troubleshoot SSIS Integration Runtime management ...ry/ssis-integration-runtime-management-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. It references error messages returned from PowerShell cmdlets as a primary troubleshooting scenario, and recommends using SSMS (SQL Server Management Studio), a Windows-only tool, for database status checks. There are no Linux/macOS-specific troubleshooting instructions, nor are cross-platform alternatives (such as Azure CLI or Data Studio) mentioned. All example workflows and tool recommendations are Windows-centric, with no parity for Linux/macOS users.
Recommendations
  • Include troubleshooting steps using Azure CLI, which is cross-platform, alongside PowerShell examples.
  • Recommend Azure Data Studio as an alternative to SSMS for database management, as it is available on Windows, Linux, and macOS.
  • Explicitly mention that SSIS IR management tasks can be performed from Linux/macOS using Azure portal and CLI, and provide relevant examples.
  • Add notes or sections for Linux/macOS users, clarifying tool availability and alternative workflows.
  • Ensure that examples and tool recommendations are presented in a neutral, cross-platform order (not Windows-first).
GitHub Create Pull Request
Data Factory Transform data using Hadoop Hive activity ...icles/data-factory/transform-data-using-hadoop-hive.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references a tutorial that is PowerShell-focused and does not provide Linux/macOS-specific examples or guidance. The only referenced tutorial is 'Tutorial: transform data (Spark PowerShell)', which suggests a Windows-first approach. There are no CLI/bash examples or explicit Linux/macOS instructions, and no mention of Linux tools or patterns.
Recommendations
  • Add references to Linux/macOS-compatible tutorials, such as using Azure CLI or Bash for pipeline management.
  • Provide example commands and workflows for Linux/macOS users, including how to interact with HDInsight and Hive activities from non-Windows environments.
  • Ensure parity in documentation by listing cross-platform options (PowerShell, Bash, Azure CLI) side-by-side.
  • Explicitly mention that the steps are platform-agnostic where applicable, or provide alternative instructions for Linux/macOS users.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation explicitly lists Azure PowerShell as a prerequisite and links only to instructions for installing/configuring Azure PowerShell, with no mention of Azure CLI or Linux/macOS alternatives. There are no examples or guidance for uploading files to Azure Storage using Linux/macOS tools (e.g., Azure CLI, azcopy, or portal UI), nor is there any indication that the steps are cross-platform. This creates friction for non-Windows users, who may not have PowerShell installed or prefer platform-native tools.
Recommendations
  • Add instructions and examples for using Azure CLI and/or azcopy to upload files to Azure Storage, including installation steps for Linux/macOS.
  • Clarify that the Azure portal UI can be used from any OS and provide steps for uploading files via the portal.
  • Explicitly state that PowerShell is optional and provide parity for Linux/macOS users.
  • Where possible, show both PowerShell and CLI commands side-by-side, or link to relevant cross-platform documentation.
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-11 06:20
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 pipeline management, with no equivalent Bash, CLI, or Linux/macOS instructions. Examples for executing commands on Batch nodes use Windows-native commands (e.g., 'cmd /c dir', 'cmd /c echo hello world'), and custom applications are referenced as '.exe' files, implying Windows executables. There is no mention of Linux shell commands, scripts, or non-Windows application formats, nor guidance for users on Linux/macOS platforms.
Recommendations
  • Provide Azure CLI or Bash equivalents for all PowerShell commands, especially for creating Batch accounts, pools, and running pipelines.
  • Include examples of custom activities using Linux shell commands (e.g., 'sh', 'bash', 'ls', 'echo') and non-Windows executables (e.g., Python scripts, ELF binaries).
  • Clarify how to configure Azure Batch pools with Linux VM images and how to target Linux nodes for custom activities.
  • Add notes or sections explaining cross-platform support, including any differences in command syntax or application packaging for Linux/macOS users.
  • Ensure that examples and sample code are not exclusively Windows-centric, and alternate them or present them in parallel with Linux/macOS equivalents.
GitHub Create Pull Request
Data Factory Transform data using Hadoop Pig activity ...ticles/data-factory/transform-data-using-hadoop-pig.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references a tutorial that uses PowerShell for data transformation before introducing the Pig activity, implying a Windows-first approach. No Linux or cross-platform CLI examples are provided, and the only referenced tutorial is PowerShell-based, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent CLI examples using Bash or Azure CLI for Linux/macOS users.
  • Reference tutorials that use cross-platform tools, not just PowerShell.
  • Explicitly state that the steps can be performed on Linux/macOS and provide guidance for those platforms.
  • Include screenshots or instructions for non-Windows environments where relevant.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. It exclusively uses Visual Studio (Windows-only) and PowerShell/NuGet Package Manager Console for setup and package installation. There are no instructions or examples for Linux or macOS users, such as using VS Code, .NET CLI, or cross-platform package managers. The prerequisite tools and workflow steps assume a Windows desktop, creating friction for non-Windows users.
Recommendations
  • Add instructions for creating the project using VS Code or JetBrains Rider, which are cross-platform IDEs.
  • Provide .NET CLI commands (e.g., 'dotnet new console', 'dotnet add package ...') for project creation and package installation, instead of only Visual Studio and PowerShell/NuGet.
  • Mention that Azure Storage Explorer is available for Linux and macOS, and provide installation links for those platforms.
  • Clarify that the Azure .NET SDK can be used on Linux/macOS, and provide any platform-specific setup notes.
  • Include sample code snippets and terminal commands for Linux/macOS environments.
  • Reorder examples so that cross-platform solutions (e.g., .NET CLI) are presented 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
Medium Priority View Details →
Scanned: 2026-01-11 06:20
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-specific tools (SQL Server Management Studio), providing setup instructions that implicitly assume a Windows environment, and omitting any guidance or examples for Linux/macOS users. There are no alternative instructions for managing SQL Server or installing/running the self-hosted integration runtime on Linux/macOS, nor are cross-platform database management tools mentioned.
Recommendations
  • Include instructions for connecting to SQL Server from Linux/macOS using cross-platform tools such as Azure Data Studio or sqlcmd.
  • Clarify whether the self-hosted integration runtime can be installed on Linux/macOS, and provide installation steps for those platforms if supported.
  • Add examples and screenshots for Linux/macOS environments where applicable.
  • Mention alternative database management tools that are available on Linux/macOS.
  • Explicitly state platform requirements and limitations for critical steps.
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
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 tutorial is heavily oriented toward Windows environments, assuming the use of Visual Studio, Notepad, and Windows-specific tooling (NuGet Package Manager Console, SQL Server Management Studio). There are no instructions or examples for Linux/macOS users, such as using VS Code, CLI tools, or alternative editors. The .NET SDK is used exclusively, with no mention of cross-platform alternatives or how to adapt the workflow for non-Windows platforms.
Recommendations
  • Add instructions for Linux/macOS users, such as using VS Code or JetBrains Rider as alternatives to Visual Studio.
  • Provide command-line instructions for installing .NET SDK and NuGet packages on Linux/macOS.
  • Include examples using cross-platform editors (e.g., nano, vim) instead of Notepad.
  • Mention how to run the sample code using the .NET Core SDK, which is cross-platform.
  • Suggest alternatives to SQL Server Management Studio, such as Azure Data Studio, which is available on Linux/macOS.
  • Clarify that Azure Storage Explorer is available on Linux/macOS and provide installation instructions for those platforms.
  • Reorder examples so that Windows and Linux/macOS instructions are presented together or in parallel, rather than Windows-first.
GitHub Create Pull Request
← Previous Page 11 of 13 Next →