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 751-775 of 1000 flagged pages
Data Factory Create schedule triggers ...rticles/data-factory/how-to-create-schedule-trigger.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation exhibits a moderate Windows bias, especially in the Azure PowerShell section. PowerShell is presented before Azure CLI, and the PowerShell instructions assume Windows paths (e.g., C:\ADFv2QuickStartPSH\MyTrigger.json) and reference 'Install Azure PowerShell on Windows with PowerShellGet' without mentioning cross-platform installation. There are no explicit Linux/macOS examples for PowerShell, and Windows-centric tooling and patterns are referenced first. However, the Azure CLI and SDK sections are cross-platform, and the JSON schema and portal instructions are neutral.
Recommendations
  • Add explicit instructions for installing and using Azure PowerShell on Linux/macOS, including example commands and paths.
  • Provide PowerShell sample code using POSIX-style paths (e.g., /home/user/ADFv2QuickStartPSH/MyTrigger.json) alongside Windows paths.
  • Clarify that Azure PowerShell and Azure CLI are both cross-platform, and provide parity in examples for both.
  • Consider presenting Azure CLI instructions before PowerShell, as CLI is more commonly used on Linux/macOS.
  • Add a note or section highlighting cross-platform compatibility for all command-line tools.
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-14 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, especially in the 'Sample for Azure PowerShell and the Azure CLI' section. PowerShell is presented first, with explicit instructions for installing Azure PowerShell on Windows and creating files in Windows-style paths (e.g., C:\ADFv2QuickStartPSH\). There are no Linux/macOS-specific instructions or examples for installing Azure PowerShell, nor any mention of Linux file paths or shell environments. The CLI section is more cross-platform, but the overall ordering and details favor Windows users.
Recommendations
  • Add explicit instructions for installing and using Azure PowerShell on Linux and macOS, including platform-appropriate commands and file paths.
  • Provide sample file paths using both Windows (C:\...) and Linux/macOS (/home/user/...) conventions.
  • Include notes clarifying that Azure CLI is fully cross-platform and can be used on Windows, Linux, and macOS.
  • Consider presenting CLI examples before PowerShell, or interleave them, to avoid implicit prioritization of Windows tooling.
  • Where screenshots or instructions reference the Azure portal, clarify that the experience is identical across operating systems.
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-14 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 notable Windows bias, particularly in the authentication section. PowerShell is exclusively used and recommended for refreshing permissions, with no equivalent Linux/macOS CLI or REST API example provided. Windows tools and patterns (PowerShell, running as Administrator) are mentioned without alternatives. No Linux/macOS-specific instructions or parity examples are present, and Windows-centric steps appear first and exclusively.
Recommendations
  • Provide equivalent instructions using Azure CLI, Bash, or REST API calls that work on Linux/macOS for refreshing permissions and other tasks.
  • Include explicit notes or examples for Linux/macOS users, such as how to install and use required modules or tools.
  • Where PowerShell is referenced, add alternative commands using cross-platform tools.
  • Clarify that the steps can be performed on non-Windows platforms, or specify any limitations.
  • Reorder examples or provide parallel instructions so Windows and Linux/macOS users are equally supported.
GitHub Create Pull Request
Data Factory Use the Execute SSIS Package activity from the portal ...ta-factory/how-to-invoke-ssis-package-ssis-activity.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows Authentication Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. It heavily references Windows authentication, UNC paths, and Windows-centric tools (SSDT, SSMS, dtutil). All file path examples use Windows UNC format, and there is no mention of Linux/macOS equivalents or how to perform similar tasks on those platforms. The use of Windows authentication is presented as the default, and Windows tools are referenced exclusively for package creation and management. There are no Linux/macOS-specific instructions, nor is there guidance for users working outside the Windows ecosystem.
Recommendations
  • Include explicit guidance for Linux/macOS users, such as how to access Azure Files from those platforms (e.g., using SMB/CIFS mounts, azcopy, or REST APIs).
  • Provide examples of file paths in Linux/macOS format where applicable, or clarify cross-platform compatibility of UNC paths.
  • Mention alternatives to Windows authentication (such as Azure AD, OAuth, or local credentials) and clarify their support and configuration.
  • Reference cross-platform tools for SSIS package creation and management, or clarify if Windows-only tools are required.
  • Add a section or notes addressing platform limitations and workarounds for non-Windows users.
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-14 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 strong bias toward Windows environments, especially in the 'Azure PowerShell' section. All CLI examples use PowerShell, and file paths are Windows-style (e.g., C:\ADF\RunSSISPackage). There are no Bash, Azure CLI, or cross-platform scripting examples, nor any guidance for Linux/macOS users. The use of PowerShell-specific cmdlets and instructions assumes the reader is on Windows, making it difficult for Linux/macOS users to follow or replicate the steps without significant adaptation.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell commands.
  • Use cross-platform file paths and note where Windows-specific paths are used.
  • Include instructions for running scripts on Linux/macOS, such as using Bash or Azure CLI.
  • Explicitly state platform requirements and alternatives at the start of the PowerShell section.
  • Add notes or links to documentation on installing and using Azure PowerShell on Linux/macOS, if PowerShell is required.
GitHub Create Pull Request
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing Windows-centric tools (SQL Server Management Studio, SQL Agent jobs) and patterns. There are no examples or mentions of Linux/macOS alternatives for managing SSIS packages, nor are cross-platform tools or command-line options discussed. The use of Windows terminology (e.g., Windows Firewall, PowerShell for NSG configuration) is present, and Windows-specific troubleshooting steps are referenced before any Linux equivalents (which are absent).
Recommendations
  • Include instructions or examples for managing SSIS packages using cross-platform tools (e.g., Azure CLI, Azure Data Studio) where possible.
  • Explicitly mention whether tasks can be performed from Linux/macOS environments and provide guidance for those platforms.
  • Add references to SQL package deployment and management via command-line tools available on Linux/macOS.
  • Clarify when Windows-only features (e.g., SSMS, Windows Firewall) are required and suggest alternatives or workarounds for non-Windows users.
  • Provide PowerShell and Azure CLI examples side-by-side, and indicate which are supported on Linux/macOS.
GitHub Create Pull Request
Data Factory Schedule an Azure-SSIS integration runtime ...tory/how-to-schedule-azure-ssis-integration-runtime.md
Medium Priority View Details →
Scanned: 2026-01-14 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 significant Windows bias, primarily through exclusive use of PowerShell scripts and Windows-centric tools (e.g., SQL Server Management Studio) for monitoring and automation. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform alternatives. The monitoring and automation sections are entirely PowerShell-focused, and Windows tools are mentioned without Linux equivalents.
Recommendations
  • Add equivalent Azure CLI and Bash script examples for starting/stopping and monitoring Azure-SSIS IRs.
  • Mention and provide examples for cross-platform tools (e.g., Azure Data Studio) instead of only SQL Server Management Studio.
  • Clarify which steps are platform-agnostic (e.g., REST API calls) and provide explicit instructions for Linux/macOS users.
  • Include notes or sections on how to perform these tasks from Linux/macOS environments, including automation via cron or other schedulers.
  • Reorder examples so platform-neutral or cross-platform approaches appear before Windows-specific ones.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page provides detailed instructions and examples exclusively using Azure PowerShell cmdlets, which are most commonly used and best supported on Windows. There are no equivalent examples or guidance for Linux/macOS users, such as using Azure CLI, REST API, or cross-platform scripting. The PowerShell section is prominent and the only automation approach described, creating friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention REST API options for reconfiguring and managing Azure-SSIS IR, with sample requests.
  • Explicitly state platform compatibility for PowerShell scripts and provide guidance for installing and using PowerShell Core on Linux/macOS if PowerShell must be used.
  • Present cross-platform options before or alongside Windows-specific tools to avoid Windows-first bias.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools 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. Windows tools and patterns (PowerShell, SSMS, SSDT) are mentioned exclusively or before any cross-platform equivalents. There are no Linux/macOS-specific instructions or examples, which may create friction for non-Windows users.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all monitoring tasks.
  • Clarify whether self-hosted integration runtime can be installed on Linux/macOS, and provide instructions if supported.
  • Mention and demonstrate cross-platform tools (e.g., Azure Portal, REST API, Azure CLI) for monitoring and management.
  • Reorder examples or explicitly state platform parity to avoid implying Windows is required.
  • Include notes or links for Linux/macOS users regarding any limitations or alternative approaches.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits 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. No Linux-specific tools, shell commands, or cross-platform instructions are provided, and Windows tools are mentioned first and exclusively in relevant sections.
Recommendations
  • Include Azure CLI examples for checking SSIS IR status, as Azure CLI is cross-platform.
  • Mention and provide instructions for using Data Studio (cross-platform) as an alternative to SSMS for querying SSISDB.
  • Clarify which steps can be performed from the Azure Portal (browser-based, OS-agnostic) and highlight parity.
  • Provide examples of parsing CSV logs using common Linux/macOS tools (e.g., grep, awk, Python scripts).
  • Explicitly state which tools and steps are available on Linux/macOS, and offer alternatives where possible.
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-14 00:00
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 provides links to PowerShell-specific guides. There is no mention of Linux/macOS command-line alternatives (such as Azure CLI or REST API), nor are there examples or instructions for non-Windows environments. This creates friction for users on Linux/macOS who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Explicitly mention REST API options for advanced users who may wish to automate tasks without PowerShell.
  • Where PowerShell is referenced, clarify platform compatibility and provide links to installation guides for PowerShell on Linux/macOS if relevant.
  • Ensure that all critical tasks (provisioning, joining virtual networks, managing IR) have Linux/macOS-friendly examples and workflows.
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-14 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 examples. PowerShell is a Windows-centric tool, and its exclusive use creates friction for Linux/macOS users. The page also references PowerShell in metadata and does not mention cross-platform alternatives, implicitly prioritizing Windows workflows.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform.
  • Include REST API and ARM template snippets for resource creation to support automation and platform neutrality.
  • Explicitly mention that Azure CLI and REST API can be used from Linux/macOS and provide links or examples.
  • Reorder examples so that cross-platform options (CLI, REST) are shown before or alongside PowerShell.
  • Update metadata to reference Azure CLI where appropriate.
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-14 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 REST API examples exclusively in PowerShell, a Windows-centric scripting language, and omits equivalent Linux/macOS shell (e.g., Bash, curl) examples. The prominence of PowerShell and Windows tools creates friction for Linux/macOS users, who must adapt or rewrite examples. The REST API section is notably Windows-biased, and PowerShell is presented as a primary automation tool throughout.
Recommendations
  • Add REST API examples using Bash and curl to demonstrate cross-platform usage.
  • Include notes or code samples for Linux/macOS users, especially in sections currently using PowerShell.
  • Balance the order of examples so that Windows and Linux/macOS approaches are presented equally.
  • Explicitly mention cross-platform alternatives where Windows tools are referenced.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a moderate Windows bias, primarily through exclusive references to Azure PowerShell for automation tasks (such as disabling triggers and creating private endpoints), and by linking only to PowerShell-based sample scripts. There are no examples or guidance for performing equivalent operations using Linux/macOS tools (such as Azure CLI, Bash, or REST API), nor are cross-platform alternatives mentioned. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts alongside PowerShell examples for all automation tasks.
  • Explicitly mention that operations can be performed on Linux/macOS and link to relevant cross-platform documentation.
  • Include REST API references or examples for tasks like disabling triggers and automating private endpoint creation.
  • Where PowerShell is referenced, add a note or section for Linux/macOS users describing alternative approaches.
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-14 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 troubleshooting steps. Diagnostic commands (PsPing, Ping) and host file editing instructions are given only for Windows (Azure VM), with explicit references to Windows paths and tools. There are no Linux/macOS equivalents or instructions, and Windows-specific tools (psping.exe, Notepad, C:\Windows\System32\drivers\etc) are mentioned exclusively. This may hinder Linux/macOS users attempting similar troubleshooting.
Recommendations
  • Provide Linux/macOS equivalents for all diagnostic commands (e.g., use 'ping', 'nc', or 'curl' for connectivity checks).
  • Include instructions for editing the /etc/hosts file on Linux/macOS, with appropriate permissions and editors.
  • Mention cross-platform tools (e.g., 'nmap', 'telnet', 'curl') where possible, rather than Windows-only utilities.
  • When showing examples, alternate or parallelize Windows and Linux/macOS instructions.
  • Clarify that troubleshooting steps apply to both Windows and Linux, and specify any platform-specific caveats.
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-14 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 users, specifically those using Visual Studio and PowerShell. All setup and tooling instructions assume Visual Studio (a Windows-centric IDE) and use PowerShell commands for package installation, with no mention of Linux/macOS alternatives (e.g., VS Code, dotnet CLI, or bash). There are no instructions or examples for Linux/macOS users, nor is there guidance on cross-platform development environments.
Recommendations
  • Add instructions for creating and running the .NET project using cross-platform tools like VS Code and the dotnet CLI.
  • Provide NuGet package installation examples using the dotnet CLI (e.g., 'dotnet add package ...') alongside PowerShell.
  • Clarify that the .NET SDK and Azure Data Factory APIs are cross-platform, and explicitly mention Linux/macOS compatibility.
  • Include notes or sections for Linux/macOS users, such as how to install .NET SDK, run the sample, and verify results using platform-agnostic tools.
  • Mention alternatives to Azure Storage Explorer (which is cross-platform, but the doc implies Windows usage) and provide links to Linux/macOS downloads.
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-14 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 notable Windows bias. All command-line examples use PowerShell syntax and Windows-centric tools, with no mention of Linux/macOS alternatives. The instructions and screenshots reference the 'self-hosted integration runtime client', which is a Windows application, and there are no examples or guidance for managing integration runtime from Linux or macOS environments. This creates friction for non-Windows users who may need to perform similar tasks.
Recommendations
  • Provide equivalent command-line examples using Bash and Azure CLI for Linux/macOS users.
  • Clarify whether the self-hosted integration runtime client is available for Linux/macOS, and if not, offer alternatives for checking version and update status (e.g., via Azure Portal or REST API).
  • Include screenshots or instructions for accessing relevant information from the Azure Portal, which is platform-agnostic.
  • Explicitly state platform requirements and limitations for the self-hosted integration runtime client.
  • Add a section or note for Linux/macOS users outlining supported workflows and tools.
GitHub Create Pull Request
Data Factory Transform data using Hive in Azure Virtual Network ...actory/tutorial-transform-data-hive-virtual-network.md
Medium Priority View Details →
Scanned: 2026-01-14 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. All command-line examples use Azure PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS alternatives. Instructions for editing the hosts file reference the Windows path only, and the self-hosted integration runtime registration steps are described for Windows VMs. There are no examples or guidance for performing these steps on Linux or macOS, nor is there any mention of cross-platform tooling.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell commands for resource creation and management.
  • Include instructions for editing the hosts file on Linux/macOS (e.g., /etc/hosts), not just Windows.
  • Clarify whether the self-hosted integration runtime can be installed and registered on Linux VMs, and provide steps if supported.
  • Add notes or sections indicating which steps are platform-agnostic and which are Windows-specific.
  • Consider reordering examples so that cross-platform options are presented first or equally.
GitHub Create Pull Request
Data Factory Source control ...docs/blob/main/articles/data-factory/source-control.md
Medium Priority View Details →
Scanned: 2026-01-14 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 SDK/PowerShell are mentioned as ways to publish changes directly to the service. There is no mention of Linux/macOS equivalents (such as Azure CLI or Bash scripting) for these tasks. Additionally, troubleshooting and advanced configuration steps reference PowerShell and SDK without providing parity examples for Linux/macOS users. Windows-specific tools and browser compatibility notes (e.g., Microsoft Edge) are present, and Windows-centric terminology (e.g., 'PowerShell') appears before any cross-platform alternatives.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all tasks that reference PowerShell.
  • Explicitly mention cross-platform support for SDKs and provide code snippets for Linux/macOS environments.
  • Include troubleshooting steps using Azure CLI or REST API, not just PowerShell.
  • Clarify browser compatibility for non-Windows browsers and platforms.
  • Review all sections for implicit Windows-first language and rephrase to be platform-neutral where possible.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references a tutorial that is explicitly for Spark with PowerShell, which is a Windows-centric tool, and does not provide equivalent Linux/macOS command-line examples or mention cross-platform alternatives. The examples and instructions are otherwise platform-neutral, but the initial guidance may lead Linux/macOS users to feel unsupported.
Recommendations
  • Add links to tutorials using Bash or cross-platform CLI tools for Spark and Pig activities.
  • Explicitly mention that Azure Data Factory and Synapse Analytics can be used from Linux/macOS environments, and provide examples or references for those platforms.
  • Ensure that all referenced tutorials (e.g., 'Tutorial: transform data') have Linux/macOS equivalents or note any platform-specific requirements.
  • Avoid recommending PowerShell as the sole automation method; include Azure CLI, Bash, or Python SDK examples where possible.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the prerequisites section, where Azure PowerShell is listed as a requirement and only instructions for installing/configuring Azure PowerShell are referenced. There are no mentions of Linux/macOS equivalents (such as Azure CLI or cross-platform upload tools), nor are alternative upload methods (e.g., using azcopy, Azure CLI, or portal UI) described. The remainder of the tutorial is platform-neutral, focusing on the Azure portal UI, but the initial setup may create friction for Linux/macOS users.
Recommendations
  • Add instructions for using Azure CLI (cross-platform) to upload files to Blob storage.
  • Mention that users can use the Azure portal UI to upload files, which is OS-agnostic.
  • Include azcopy as an alternative tool for file uploads, with links to installation and usage guides for all platforms.
  • Clarify that PowerShell is not strictly required and provide parity for Linux/macOS users in the prerequisites section.
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-14 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 a Windows bias by referencing PowerShell cmdlets as a primary troubleshooting interface and recommending the use of SQL Server Management Studio (SSMS) for diagnostics, both of which are Windows-centric tools. No equivalent Linux/macOS tools or command-line examples (such as Azure CLI, sqlcmd, or cross-platform alternatives) are provided. The guidance assumes access to Windows environments and tools, which may create friction for Linux/macOS users.
Recommendations
  • Include troubleshooting steps using Azure CLI and/or REST API, which are cross-platform.
  • Provide examples using sqlcmd or Azure Data Studio, both of which are available on Linux/macOS, instead of or alongside SSMS.
  • Mention alternative ways to check SQL Database connectivity from Linux/macOS (e.g., using telnet, nc, or sqlcmd).
  • Clarify that PowerShell cmdlets are Windows-specific and offer Azure CLI equivalents for provisioning/deprovisioning SSIS IR.
  • Ensure that all steps referencing Windows tools have Linux/macOS equivalents or links to relevant 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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a notable Windows bias. PowerShell and Windows-specific tools (e.g., .exe files, cmd commands) are used exclusively in code examples and instructions. There are no Linux/macOS shell or tool equivalents provided, and Windows patterns (such as referencing .exe files and using cmd) are presented as the default or only option. This could create friction for Linux/macOS users attempting to follow the guide.
Recommendations
  • Provide equivalent Bash or shell command examples alongside PowerShell, especially for pipeline execution and monitoring.
  • Include examples using Linux-compatible executables (e.g., .sh scripts or ELF binaries) in the 'command' property, not just .exe files.
  • Clarify that Azure Batch pools can run both Windows and Linux VMs, and provide guidance or links for selecting and configuring Linux pools.
  • When referencing commands like 'cmd /c', also show the Linux equivalent (e.g., '/bin/bash -c').
  • Explicitly mention cross-platform considerations and any differences in behavior or setup between Windows and Linux Batch pools.
GitHub Create Pull Request
Data Factory Transform data using Hadoop Streaming activity .../data-factory/transform-data-using-hadoop-streaming.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias towards Windows by using .exe files (MyMapper.exe, MyReducer.exe, MyCombiner.exe) as examples for mapper, reducer, and combiner programs. There are no examples or mentions of Linux-compatible formats (e.g., Python scripts, shell scripts, or Linux binaries), and the only executable format shown is Windows-specific. This may lead Linux/macOS users to believe that only Windows executables are supported, or create confusion about how to use their own scripts.
Recommendations
  • Provide examples using Linux-compatible scripts (e.g., Python, Bash, or compiled Linux binaries) for mapper and reducer.
  • Explicitly state that both Windows and Linux executables are supported, if true, and clarify any platform restrictions.
  • Show parallel examples for both Windows (.exe) and Linux (e.g., .py, .sh) in the JSON sample and file path descriptions.
  • Include a note or section addressing cross-platform compatibility and best practices for users on Linux/macOS.
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-14 00:00
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, using Visual Studio and .NET SDK for all steps, and referencing Windows-specific tools (Notepad, SSMS, Visual Studio) without mentioning Linux/macOS alternatives. There are no instructions or code samples for Linux/macOS users, nor guidance on using cross-platform tools or SDKs. The only tool mentioned for uploading blobs (Azure Storage Explorer) is cross-platform, but all development and execution steps assume Windows.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as using VS Code or JetBrains Rider for .NET development.
  • Include .NET CLI commands for project creation and NuGet package installation, which work on all platforms.
  • Mention alternative text editors (e.g., nano, vim, gedit) for creating input files.
  • Add instructions for running the sample code on Linux/macOS, including any prerequisites (e.g., installing .NET SDK).
  • Reference cross-platform database tools (e.g., Azure Data Studio) for verifying results in Azure SQL Database.
  • Explicitly state that Azure Storage Explorer is available for Linux/macOS, and provide download links.
GitHub Create Pull Request
← Previous Page 31 of 40 Next →