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 351-375 of 1000 flagged pages
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-quickstart-verify-output-cleanup.md ...ludes/data-factory-quickstart-verify-output-cleanup.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows-centric. There are no examples or instructions for performing the same actions using cross-platform tools such as Azure CLI, Bash, or Cloud Shell, nor are Linux/macOS alternatives mentioned.
Recommendations
  • Add equivalent Azure CLI commands for deleting resource groups and data factories, which work on Linux, macOS, and Windows.
  • Mention that Azure CLI and Cloud Shell are cross-platform options for managing Azure resources.
  • Provide Bash script examples or instructions for Linux/macOS users.
  • Clearly indicate that PowerShell commands are primarily for Windows and suggest alternatives for other platforms.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/introduction.md ...e-docs/blob/main/articles/data-factory/introduction.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 mentioned as a primary monitoring and management tool, and is listed in the 'Related content' section before Linux-native alternatives. There is a lack of explicit Linux CLI or Bash examples, and Windows-centric tools (PowerShell, Azure portal) are referenced without mention of Linux equivalents or parity. The documentation does not provide examples or guidance for Linux users, such as Bash, Azure CLI, or Linux-based automation patterns.
Recommendations
  • Add explicit examples and guidance for Linux users, including Bash and Azure CLI commands for common tasks (e.g., creating and managing Data Factory resources, monitoring pipelines).
  • Mention Linux-native tools and automation patterns alongside PowerShell, ensuring parity in documentation and examples.
  • Reorder or balance the 'Related content' section to include Linux and cross-platform options (e.g., Azure CLI, Bash scripts) before or alongside PowerShell.
  • Include references to Linux-based development and deployment workflows, such as using CI/CD with Azure DevOps agents running on Linux.
  • Clarify that Azure Data Factory can be managed from both Windows and Linux environments, and provide links to relevant Linux documentation.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/manage-azure-ssis-integration-runtime.md .../data-factory/manage-azure-ssis-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples and cmdlets for reconfiguring and deleting Azure-SSIS integration runtimes. There are no equivalent examples or instructions for Linux users (e.g., using Azure CLI, Bash, or REST API). The use of PowerShell and references to Windows-centric tools are presented as the default and only automation method, with no mention of cross-platform alternatives.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell cmdlets shown, as Azure CLI is cross-platform and commonly used on Linux and macOS.
  • Include REST API examples for advanced users who may wish to automate tasks from any platform.
  • Explicitly state that PowerShell Core is available cross-platform, but also clarify any limitations or differences for Linux/macOS users.
  • Reorganize sections so that cross-platform methods (Azure CLI, REST API) are presented alongside or before Windows-specific tools.
  • Add a note or table summarizing which management tools are available on which platforms, and link to installation guides for each.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/monitor-data-factory.md ...lob/main/articles/data-factory/monitor-data-factory.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page mentions PowerShell as a primary programmatic monitoring method and lists it before Python and REST API, which may indicate a Windows-first bias. There are no explicit Linux or bash examples, nor are Linux-specific tools or patterns mentioned. The absence of Linux command-line examples or references to cross-platform CLI tools (such as Azure CLI) further suggests a lack of Linux parity.
Recommendations
  • Add Azure CLI examples for monitoring and configuring diagnostics, as Azure CLI is cross-platform and widely used on Linux.
  • Include bash or shell script examples alongside PowerShell to demonstrate Linux compatibility.
  • Explicitly mention that monitoring can be performed from Linux environments and provide links or references to Linux-specific documentation where relevant.
  • Ensure that references to programmatic monitoring methods do not prioritize Windows-centric tools (e.g., list Azure CLI and REST API before PowerShell, or present them together).
  • Add troubleshooting or usage notes for Linux users, such as file path conventions or authentication differences.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/join-azure-ssis-integration-runtime-virtual-network.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/join-azure-ssis-integration-runtime-virtual-network.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page shows evidence of Windows bias by repeatedly referencing Azure PowerShell as a primary method for provisioning and configuring Azure-SSIS IR, both in the main text and in related links. There is no mention of Linux-native tools (such as Azure CLI or Bash scripting), nor are Linux-specific examples provided. The ordering of examples and tooling references consistently places Windows-centric tools (PowerShell, ADF UI) before any alternatives, and Linux parity is not addressed.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and commonly used on Linux.
  • Explicitly mention that all operations can be performed from Linux or macOS using Azure CLI or REST API, not just PowerShell.
  • Provide example commands for joining Azure-SSIS IR to a virtual network using Azure CLI and Bash.
  • Reorder documentation sections to present cross-platform tools (Azure CLI, REST API) before or alongside Windows-centric tools.
  • Include a note clarifying that PowerShell is available on Linux, but Azure CLI is often preferred for Linux environments.
  • Ensure that all referenced tutorials and related articles also offer Linux-compatible instructions.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/managed-virtual-network-private-endpoint.md ...ta-factory/managed-virtual-network-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias primarily through exclusive use of Azure PowerShell for resource creation examples, with no equivalent CLI or REST API instructions. The only code sample provided is in PowerShell, a Windows-centric tool, and there is no mention of Linux-native tools or cross-platform alternatives. This may disadvantage users on Linux or macOS, who would typically use Azure CLI or ARM templates. Additionally, the documentation references PowerShell before any other automation or scripting approach.
Recommendations
  • Provide equivalent examples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Include REST API or ARM template examples for resource creation to ensure platform neutrality.
  • Add notes or links to documentation for Linux/macOS users on how to perform the same tasks without PowerShell.
  • Avoid referencing Windows-specific tools (like PowerShell) as the default or only method; present cross-platform options first or alongside.
  • Review screenshots and UI instructions to ensure they are not Windows-centric (e.g., Azure Portal screenshots are generally fine, but avoid showing Windows-only tools).
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/monitor-integration-runtime.md ...n/articles/data-factory/monitor-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All command-line examples use PowerShell, with no mention of Bash, CLI, or Linux-native tools. The self-hosted integration runtime is described as running on 'on-premises Windows machine,' with no reference to Linux support. Windows-centric tools (PowerShell, SSMS, SSDT) are mentioned exclusively or before any cross-platform alternatives. There are no Linux or macOS examples, nor guidance for users on those platforms.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all command-line operations.
  • Clarify whether self-hosted integration runtime supports Linux hosts; if so, provide Linux installation and monitoring instructions.
  • Mention cross-platform tools (e.g., Azure Data Studio) where SSMS or SSDT are referenced.
  • Explicitly state platform requirements and alternatives for non-Windows users.
  • Ensure parity in troubleshooting and monitoring guidance for Linux environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/monitor-ssis.md ...e-docs/blob/main/articles/data-factory/monitor-ssis.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (Azure PowerShell, SSMS, SSDT, SQL Server Agent) for monitoring and querying SSIS operations, without mentioning or providing Linux equivalents or examples. The only command-line example is Azure PowerShell, and all operational tooling references are Windows-first or Windows-only. There are no instructions or examples for Linux users, nor are cross-platform alternatives discussed.
Recommendations
  • Include Azure CLI examples for monitoring SSIS IR operational status, as Azure CLI is cross-platform and runs on Linux, macOS, and Windows.
  • Mention and provide examples for querying logs using cross-platform tools such as Azure Data Explorer Web UI or REST APIs.
  • Clarify whether SSIS monitoring and package execution can be managed from Linux environments, and if not, explicitly state the limitation.
  • If possible, reference or provide guidance for using open-source SQL clients (e.g., DBeaver, Azure Data Studio) that run on Linux for querying SSISDB or Log Analytics.
  • Ensure that all step-by-step instructions and screenshots are not exclusively tied to Windows-only tools or interfaces.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/pipelines-disaster-recovery.md ...n/articles/data-factory/pipelines-disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 referencing Azure PowerShell for automation tasks (such as disabling triggers and approving private endpoints) and linking to PowerShell-specific modules and scripts. There are no equivalent examples or references for Linux-native tools (such as Azure CLI or Bash scripting), nor are cross-platform alternatives mentioned. This may hinder Linux users or those working in non-Windows environments from easily following the guidance.
Recommendations
  • Provide Azure CLI examples alongside PowerShell instructions for all automation and scripting tasks.
  • Reference Bash scripting or other cross-platform automation approaches where relevant.
  • Explicitly mention that both PowerShell and Azure CLI are supported, and link to documentation for both.
  • Where possible, include screenshots or code snippets for both Windows and Linux environments.
  • Review linked resources to ensure Linux parity and add links to Linux-focused guides if missing.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/quickstart-create-data-factory-dot-net.md ...data-factory/quickstart-create-data-factory-dot-net.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 exclusively referencing Visual Studio (a Windows-centric IDE), using PowerShell commands for NuGet package installation, and omitting any Linux or cross-platform development instructions. There are no examples or guidance for using .NET SDK on Linux (e.g., via VS Code, JetBrains Rider, or CLI tools), nor are alternative package management commands (like 'dotnet add package') provided. The workflow assumes a Windows environment throughout.
Recommendations
  • Add instructions for setting up a .NET project using cross-platform tools such as VS Code or JetBrains Rider.
  • Include Linux/macOS-specific steps for project creation and execution, such as using the 'dotnet' CLI.
  • Provide alternative NuGet package installation commands (e.g., 'dotnet add package Azure.ResourceManager.DataFactory') instead of only PowerShell.
  • Clarify that the .NET SDK and Azure Data Factory APIs are cross-platform, and explicitly support Linux/macOS development.
  • Mention and link to resources for running and debugging .NET applications on Linux/macOS.
  • Avoid assuming Visual Studio as the only development environment; present it as one option among several.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/quickstart-create-data-factory-rest-api.md ...ata-factory/quickstart-create-data-factory-rest-api.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows and PowerShell usage. All code examples use PowerShell, and the instructions assume the use of Azure PowerShell modules and Windows-centric tools (e.g., Azure Storage Explorer). There are no examples or guidance for Linux/macOS users, such as using Bash, curl, or cross-platform Azure CLI. The documentation does not mention or demonstrate how to perform the same REST API operations from a Linux shell or using platform-agnostic tools, making it less accessible for non-Windows users.
Recommendations
  • Provide equivalent examples using Bash and curl for REST API calls.
  • Include instructions for using Azure CLI, which is cross-platform, for authentication and resource management.
  • Mention that Azure PowerShell is available on Linux/macOS, but also offer native shell examples.
  • List Linux/macOS prerequisites and installation steps for Azure CLI and PowerShell.
  • Show how to use platform-agnostic tools (e.g., curl, jq) to interact with the REST API.
  • Reference Linux-compatible alternatives to Azure Storage Explorer, or clarify its cross-platform availability.
  • Reorder sections so that cross-platform tools and examples are presented before or alongside Windows/PowerShell instructions.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/security-and-access-control-troubleshoot-guide.md ...tory/security-and-access-control-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias in several areas. Troubleshooting steps for connectivity and DNS issues reference Windows-specific tools (PsPing, Notepad, editing C:\Windows\System32\drivers\etc\hosts), and provide instructions and screenshots only for Windows environments. There are no equivalent examples or instructions for Linux-based VMs, such as using ping, nc, or editing /etc/hosts. Windows tools and patterns are mentioned exclusively and before any cross-platform alternatives, making the documentation less accessible for Linux users.
Recommendations
  • Provide Linux equivalents for all troubleshooting steps, such as using 'ping', 'nc', or 'curl' for connectivity checks, and instructions for editing /etc/hosts.
  • Include screenshots or terminal examples for Linux environments alongside Windows examples.
  • Mention cross-platform tools and commands first, or at least in parallel with Windows-specific ones.
  • Clarify that steps apply to both Windows and Linux VMs, and specify any differences in procedure.
  • Avoid assuming the use of Windows-only tools (e.g., PsPing, Notepad) and offer alternatives for Linux.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/quickstart-create-data-factory-bicep.md ...s/data-factory/quickstart-create-data-factory-bicep.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. It references Notepad as the example text editor, lists Azure PowerShell alongside Azure CLI throughout, and sometimes presents PowerShell examples before CLI. There is no mention of Linux-specific editors (e.g., nano, vim), nor are there instructions for uploading files via Linux command-line tools (e.g., azcopy, curl, or CLI blob commands). The file creation step assumes a Windows environment, and PowerShell is given equal prominence to CLI, which may not reflect Linux user patterns.
Recommendations
  • Include Linux-friendly text editor examples (e.g., nano, vim) alongside Notepad.
  • Clarify that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
  • Add instructions for uploading files to blob storage using Azure CLI (az storage blob upload) or azcopy, which work on Linux.
  • Present CLI examples before PowerShell, as CLI is more universal across platforms.
  • Explicitly mention that all CLI commands work on Linux/macOS and Windows.
  • Avoid referencing Windows-specific tools (e.g., Notepad) without alternatives.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/sap-change-data-capture-shir-preparation.md ...ta-factory/sap-change-data-capture-shir-preparation.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools and patterns. All examples and instructions assume a Windows environment, such as using PowerShell for connectivity testing and editing the Windows hosts file. There are no Linux equivalents or cross-platform guidance provided.
Recommendations
  • Include Linux-specific instructions for installing and configuring the self-hosted integration runtime, if supported.
  • Provide a Linux alternative for connectivity testing, such as using 'nc' (netcat) or 'telnet' commands.
  • Add guidance for editing the '/etc/hosts' file on Linux systems.
  • Clarify platform requirements and explicitly state if only Windows is supported, or highlight cross-platform options if available.
  • Where screenshots or examples are given, provide Linux equivalents or note differences in procedure.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/self-hosted-integration-runtime-auto-update.md ...factory/self-hosted-integration-runtime-auto-update.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell commands and examples, referencing the 'self-hosted integration runtime client' (a Windows-only tool), and omitting any Linux-specific instructions or CLI examples. There is no mention of how to perform these tasks on Linux, nor are Linux-compatible tools or shell commands provided. The documentation implicitly assumes a Windows environment throughout.
Recommendations
  • Add equivalent Bash/Azure CLI examples for all PowerShell commands, demonstrating usage on Linux/macOS.
  • Clarify whether the 'self-hosted integration runtime client' is available on Linux, and if not, provide alternative methods for Linux users (e.g., portal, REST API, CLI).
  • Explicitly state platform requirements and provide parity in instructions for both Windows and Linux environments.
  • Include screenshots or descriptions of Linux-compatible workflows where possible.
  • Mention any limitations or differences in auto-update and expire notification handling on Linux hosts.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/self-hosted-integration-runtime-diagnostic-tool.md ...ory/self-hosted-integration-runtime-diagnostic-tool.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references Windows-specific tools and workflows, such as the use of 'dmgcmd.exe' and the Configuration Manager UI, without mentioning Linux equivalents or providing Linux command-line examples. There is no indication that the diagnostic tool is available or usable on Linux systems, nor are any Linux troubleshooting patterns or commands discussed.
Recommendations
  • Clarify whether the diagnostic tool is available for Linux environments. If so, provide Linux-specific installation and usage instructions.
  • Include Linux command-line examples (e.g., shell commands) alongside Windows examples.
  • Mention any Linux dependencies or troubleshooting steps relevant to self-hosted integration runtime on Linux.
  • If the tool is Windows-only, explicitly state this limitation to avoid confusion for Linux users.
  • Ensure parity in screenshots and UI walkthroughs for both Windows and Linux platforms if supported.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/self-hosted-integration-runtime-troubleshoot-guide.md ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/self-hosted-integration-runtime-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. Troubleshooting steps, log collection, and configuration instructions almost exclusively reference Windows tools (Event Viewer, MMC, Registry Editor, Control Panel, Windows folders, Windows services, etc.), and use Windows-specific commands (Certutil, dmgcmd.exe, PowerShell). There are no Linux-specific examples or instructions, even though self-hosted IR can be run on Linux (via Docker). Linux tools and troubleshooting patterns (e.g., systemd, journalctl, Linux file paths, shell commands) are absent, and Windows methods are always presented first or exclusively.
Recommendations
  • Add Linux-specific troubleshooting sections for self-hosted IR running on Linux (e.g., Docker), including log collection, service management, and certificate handling.
  • Provide equivalent Linux commands and tools (journalctl, systemctl, openssl, file system paths) alongside Windows instructions.
  • Include examples for accessing logs, managing certificates, and resolving connectivity issues on Linux systems.
  • Clarify which troubleshooting steps apply only to Windows and which are cross-platform.
  • Where PowerShell is used, offer bash/shell alternatives for Linux environments.
  • Reference Linux documentation and community resources for IR troubleshooting.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/ssis-integration-runtime-management-troubleshoot.md ...ry/ssis-integration-runtime-management-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell cmdlets as the primary CLI interface for troubleshooting, recommending the use of SSMS (SQL Server Management Studio, a Windows-only tool), and providing no Linux or cross-platform command-line examples. There are no mentions of Linux-native tools or instructions for users on non-Windows platforms, and the troubleshooting steps assume a Windows environment.
Recommendations
  • Provide equivalent troubleshooting steps using Azure CLI and/or Azure Cloud Shell, which are cross-platform.
  • Include examples using sqlcmd (available on both Windows and Linux) for connecting to SQL Database or SQL Managed Instance.
  • Mention and provide guidance for using Azure Data Studio, which is cross-platform, as an alternative to SSMS.
  • Clarify that custom setup scripts can be tested on both Windows and Linux, and provide example scripts for each.
  • Avoid assuming the use of Windows VMs; suggest using Linux VMs where appropriate and provide parity in instructions.
  • Explicitly state when a tool or step is Windows-only, and offer alternatives for Linux/macOS users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/transform-data-using-custom-activity.md ...s/data-factory/transform-data-using-custom-activity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias in several ways: PowerShell commands are used exclusively for Azure Batch and Data Factory management, with no equivalent CLI or Bash examples for Linux users. Command examples for custom activities use Windows-specific tools (e.g., 'cmd /c', '.exe' files) and mention Windows-native commands before any cross-platform alternatives. There is no guidance or sample for running Linux shell scripts or using Linux-based tools in custom activities, nor is there mention of Linux VM pool configuration or parity in workflow. References to Windows tools and patterns are prevalent, while Linux equivalents are absent.
Recommendations
  • Provide Azure CLI and Bash examples alongside PowerShell commands for managing Azure Batch and Data Factory resources.
  • Include sample custom activity definitions that execute Linux shell scripts (e.g., 'bash script.sh') or Linux-native binaries, and clarify how to target Linux pool nodes.
  • Explicitly document how to configure Azure Batch pools with Linux VM images and how custom activities differ on Linux vs. Windows nodes.
  • Mention cross-platform considerations for custom applications (e.g., .NET Core, Python) and provide code samples for both Windows and Linux environments.
  • Ensure references to Windows tools (e.g., 'cmd /c', '.exe') are balanced with Linux equivalents (e.g., '/bin/bash', '.sh'), and clarify OS-specific behaviors.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/self-hosted-integration-runtime-proxy-ssis.md ...-factory/self-hosted-integration-runtime-proxy-ssis.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias: all command-line examples use PowerShell, Windows-specific tools and paths (e.g., Local Security Policy, NT SERVICE accounts, C:\ProgramData), and references to Visual Studio/SSDT. There is no mention of Linux support, nor are any Linux-specific instructions, tools, or examples provided. The documentation assumes the self-hosted IR is installed on a Windows machine and omits guidance for Linux environments.
Recommendations
  • Explicitly state platform support for self-hosted IR (e.g., clarify if Linux is supported or not).
  • If Linux is supported, provide equivalent Linux instructions for installation, configuration, and authentication (e.g., using bash, systemd service accounts, Linux file paths).
  • Include Linux command-line examples (e.g., Bash, CLI) alongside PowerShell.
  • Reference cross-platform tools where possible, or note Windows-only requirements.
  • Provide guidance for configuring authentication and permissions on Linux (e.g., using PAM, sudoers, etc.).
  • Document log file locations and troubleshooting steps for Linux installations.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/source-control.md ...docs/blob/main/articles/data-factory/source-control.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 source control demonstrates a mild Windows bias. PowerShell is mentioned as a primary method for publishing changes and updating configuration, with no equivalent Linux shell or CLI examples provided. Windows-specific tools (PowerShell, Azure Portal, Visual Studio) are referenced throughout, and troubleshooting steps mention PowerShell before REST API or SDK alternatives. There are no explicit Linux or cross-platform command-line examples, nor is there mention of using Azure CLI or Bash for common tasks. The overall workflow assumes a Windows-centric environment, especially for administrative and automation tasks.
Recommendations
  • Add equivalent examples using Azure CLI and Bash for tasks currently described with PowerShell.
  • Explicitly mention cross-platform compatibility for all command-line operations, including REST API usage from Linux/macOS.
  • Include troubleshooting steps and configuration instructions using Linux-native tools and environments.
  • Reference Visual Studio Code (cross-platform) alongside Visual Studio (Windows-only) where appropriate.
  • Clarify that all repository operations (Git, Azure DevOps, GitHub) can be performed from any OS, and provide links to platform-agnostic documentation.
  • Where browser-specific issues are mentioned (e.g., Microsoft Edge), include notes about Chrome/Firefox and Linux/macOS compatibility.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/transform-data-using-hadoop-hive.md ...icles/data-factory/transform-data-using-hadoop-hive.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation references a tutorial that specifically uses Spark with PowerShell, suggesting a Windows-first approach and omitting Linux/bash alternatives. No Linux-specific tools, shell commands, or examples are provided, and the only referenced scripting environment is PowerShell, which is primarily associated with Windows. The documentation does not mention how to perform equivalent operations from Linux environments or with bash, nor does it provide parity in example commands or tooling.
Recommendations
  • Add equivalent Linux/bash examples alongside PowerShell instructions, especially in referenced tutorials.
  • Explicitly mention that the Hive activity can be orchestrated from Linux environments and provide sample bash scripts or CLI commands.
  • Where PowerShell is referenced, also provide Azure CLI or bash alternatives for cross-platform parity.
  • Clarify that Azure Data Factory and Synapse Analytics are accessible from both Windows and Linux, and link to documentation for both environments.
  • Avoid implying Windows as the default platform by listing cross-platform options first or equally.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-copy-data-dot-net.md ...in/articles/data-factory/tutorial-copy-data-dot-net.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively using Visual Studio, Notepad, and .NET SDK for the walkthrough, with all code samples in C#. The prerequisites and instructions assume a Windows development environment, referencing Windows-specific tools (Visual Studio, SSMS, Notepad) and omitting any Linux alternatives or cross-platform instructions. There are no examples for Linux users (e.g., using VS Code, CLI, or Python SDK), and the only tool mentioned for blob upload is Azure Storage Explorer, which is cross-platform but is presented in a Windows-centric workflow. The 'Related content' section advances to a PowerShell tutorial, further reinforcing the Windows-first approach.
Recommendations
  • Provide parallel instructions for Linux and macOS users, such as using VS Code or JetBrains Rider instead of Visual Studio.
  • Include examples using Azure Data Factory's Python SDK or REST API, which are platform-agnostic.
  • Demonstrate how to upload files to Blob Storage using Azure CLI or azcopy, both of which are cross-platform.
  • Show how to connect to Azure SQL Database using cross-platform tools (e.g., Azure Data Studio, sqlcmd).
  • Avoid referencing Notepad and SSMS as the only editors/tools; suggest alternatives available on Linux.
  • Add a section or callouts for running the tutorial on Linux, including package installation and environment setup.
  • Balance the 'Related content' links by including tutorials that use CLI, Python, or other cross-platform approaches, not just PowerShell.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-spark-portal.md ...s/data-factory/tutorial-transform-data-spark-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by listing Azure PowerShell as a prerequisite without mentioning Azure CLI or Bash alternatives, and by not providing Linux/macOS-specific instructions or examples for uploading files or managing resources. All tooling and setup instructions assume a Windows-centric workflow, with no parity for Linux users.
Recommendations
  • Add instructions for installing and using Azure CLI as an alternative to Azure PowerShell, including links to relevant documentation.
  • Provide example commands for uploading files to Azure Blob Storage using Azure CLI and Bash, alongside the PowerShell examples.
  • Explicitly mention that the tutorial can be followed on Linux/macOS and clarify any platform-specific differences.
  • Ensure that screenshots and UI references do not assume a Windows environment (e.g., avoid showing only Windows-style dialogs or paths).
  • Include troubleshooting notes for common Linux/macOS issues (e.g., file permissions, path formats).
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-control-flow.md ...ob/main/articles/data-factory/tutorial-control-flow.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively using Windows tools (Visual Studio, Azure Storage Explorer) and providing only C#/.NET examples with PowerShell/NuGet commands. There are no Linux or cross-platform alternatives mentioned for development, tooling, or workflow. The instructions assume a Windows environment throughout, omitting guidance for Linux or macOS users.
Recommendations
  • Add instructions for developing Azure Data Factory pipelines using cross-platform tools such as VS Code, JetBrains Rider, or command-line editors.
  • Include .NET CLI commands (dotnet new, dotnet add package) as alternatives to Visual Studio and NuGet Package Manager for Linux/macOS users.
  • Mention and provide examples for using Azure CLI or REST API for pipeline creation and management, which are platform-agnostic.
  • Suggest alternatives to Azure Storage Explorer, such as azcopy or Azure CLI storage commands, which are available on Linux.
  • Clarify that the .NET SDK and Azure Data Factory APIs can be used from any OS, and provide sample instructions for Linux/macOS environments.
  • Consider including sample code in Python (using Azure SDK for Python) or other languages that are popular on Linux.
GitHub Create Pull Request
← Previous Page 15 of 40 Next →