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 226-250 of 1000 flagged pages
Data Factory Review deployed resources ...ludes/data-factory-quickstart-verify-output-cleanup.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 users, such as Azure CLI or Bash commands. This creates a bias toward Windows users and may hinder Linux users from following the instructions easily.
Recommendations
  • Add Azure CLI examples for deleting resource groups and data factories, which are cross-platform and commonly used on Linux.
  • Include Bash command snippets for resource management where applicable.
  • Explicitly mention that PowerShell commands can be run on Linux and macOS, or provide links to instructions for installing PowerShell Core on non-Windows platforms.
  • Present both Windows and Linux command options side-by-side to ensure parity.
GitHub Create Pull Request
Data Factory Introduction to Azure Data Factory ...e-docs/blob/main/articles/data-factory/introduction.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias. PowerShell is mentioned as a primary monitoring tool, and the 'Related content' section lists PowerShell before other automation options (Python, REST, .NET). Windows-centric tools (PowerShell, Azure portal UI) are referenced without explicit mention of Linux CLI or Bash alternatives. There are no Linux-specific examples or explicit parity for Linux users, and Windows tools are presented first or exclusively in some cases.
Recommendations
  • Add explicit examples using Azure CLI and Bash scripts for common tasks, such as pipeline creation and monitoring.
  • Mention Linux-compatible tools and workflows (e.g., Azure CLI, Bash, Python) alongside PowerShell and Azure portal UI.
  • Ensure that automation and scripting examples are provided for both Windows and Linux environments, and alternate the order of presentation to avoid Windows-first bias.
  • Include links to Linux-specific quickstarts or tutorials where available.
  • Clarify that Azure Data Factory is fully usable from Linux environments and provide guidance for Linux users in relevant sections.
GitHub Create Pull Request
Data Factory Reconfigure the Azure-SSIS integration runtime .../data-factory/manage-azure-ssis-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell examples for command-line operations, which are native to Windows and require either Windows or PowerShell Core. There are no equivalent examples using Bash, Azure CLI, or other Linux-friendly tools. The command-line section is titled 'Azure PowerShell' and does not mention or provide parity for Linux users, making it difficult for those on non-Windows platforms to follow the instructions. Additionally, the documentation refers to PowerShell cmdlets before any alternative tooling.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, and provide installation guidance or links.
  • Include Bash script examples where appropriate, especially for automation scenarios.
  • Reorganize command-line sections to present Azure CLI and PowerShell examples side-by-side, or at least mention both options.
  • Clarify tool prerequisites for each example, including OS compatibility.
GitHub Create Pull Request
Data Factory include file ...tory/includes/data-factory-quickstart-prerequisites.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns, such as Notepad and the C:\ADFv2QuickStartPSH folder, without mentioning Linux equivalents. There are no examples or instructions for Linux users (e.g., using nano/vim, home directories, or Linux file paths), and Windows conventions are presented as defaults.
Recommendations
  • Include Linux-specific instructions alongside Windows ones, such as using nano or vim to create files and saving them in ~/ADFv2QuickStartPSH.
  • Use platform-neutral language when referring to file paths and editors, or provide parallel examples for both Windows and Linux.
  • Explicitly mention that the steps apply to both Windows and Linux, and clarify any differences in file system structure or tool usage.
  • Add screenshots or terminal commands for Linux users where appropriate (e.g., using the Azure CLI or uploading files from Linux).
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by repeatedly referencing Azure PowerShell as a primary method for provisioning and managing Azure-SSIS IR, and by listing PowerShell-based instructions and links before or alongside UI-based methods. There is no mention of Linux-native tools (such as Azure CLI or Bash scripting), nor are Linux-specific examples or instructions provided. The documentation assumes familiarity with Windows-centric tooling and patterns, potentially excluding Linux users or those preferring cross-platform solutions.
Recommendations
  • Add equivalent Azure CLI examples and instructions for all operations currently described with Azure PowerShell.
  • Explicitly mention cross-platform options (such as Azure CLI, REST API, or Terraform) alongside PowerShell and UI methods.
  • Ensure that references to provisioning and management tools do not prioritize Windows tools (e.g., PowerShell) over cross-platform alternatives.
  • Include sample commands and walkthroughs for Linux environments, and clarify any platform-specific requirements or limitations.
  • Review related content and tutorials to ensure Linux parity in examples and tool recommendations.
GitHub Create Pull Request
Data Factory Managed virtual network and managed private endpoints ...ta-factory/managed-virtual-network-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for creating managed virtual networks and private endpoints, with no equivalent instructions or code samples for Linux users (e.g., Azure CLI, REST API, or ARM templates). The use of PowerShell and references to Windows-centric tooling and patterns are presented exclusively, and there is no mention of Linux command-line alternatives or cross-platform approaches. This may hinder Linux users or those working in non-Windows environments from easily following the documentation.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell code snippets to ensure Linux and macOS users can follow along.
  • Include REST API and/or ARM template instructions for resource creation to provide platform-agnostic options.
  • Explicitly mention cross-platform tooling (e.g., Azure CLI, Bicep, Terraform) in relevant sections.
  • Where screenshots or UI instructions are given, clarify that the Azure portal is accessible from any OS.
  • Review and update any references to Windows-specific tools or patterns to ensure Linux parity and inclusivity.
GitHub Create Pull Request
Data Factory Monitor Azure Data Factory ...lob/main/articles/data-factory/monitor-data-factory.md
High Priority View Details →
Scanned: 2026-01-10 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 mild Windows bias. Programmatic monitoring lists .NET and PowerShell before Python and REST API, suggesting a Windows-first approach. There are no Linux-specific examples, tools, or command-line instructions (e.g., Bash, CLI) for configuring or monitoring Data Factory, and PowerShell is mentioned as a primary method for automation, which is more common on Windows. No Linux equivalents or parity are provided for monitoring tasks.
Recommendations
  • Add explicit Linux/Bash/Azure CLI examples alongside PowerShell and .NET for programmatic monitoring.
  • Ensure Python and REST API examples are given equal prominence and detail as Windows-centric tools.
  • Mention cross-platform tools and workflows (e.g., Azure CLI, Bash scripts) for configuring diagnostics and monitoring.
  • Include guidance for Linux users on setting up monitoring, especially for self-hosted integration runtimes.
  • Review referenced articles to ensure Linux parity in code samples and instructions.
GitHub Create Pull Request
Data Factory Programmatically monitor an Azure Data Factory ...main/articles/data-factory/monitor-programmatically.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by providing REST API examples exclusively in PowerShell, which is primarily a Windows tool. There are no equivalent Linux shell (bash/curl) examples for REST API usage, and PowerShell is featured both in its own section and as the scripting language for REST API examples. This focus on PowerShell and lack of Linux-native command-line examples may disadvantage users on Linux or macOS platforms.
Recommendations
  • Add REST API examples using bash and curl to demonstrate how to monitor pipelines from Linux/macOS environments.
  • Include notes or code samples for using cross-platform tools (e.g., Python requests, curl) alongside PowerShell scripts.
  • Ensure that scripting examples are provided for both Windows and Linux environments, especially in sections where PowerShell is used.
  • Reorder or parallelize examples so that Linux/macOS tools are presented alongside Windows tools, rather than Windows-first.
  • Explicitly mention platform compatibility for each example, clarifying when a tool is Windows-specific.
GitHub Create Pull Request
Data Factory BCDR for Azure Data Factory and Azure Synapse Analytics Pipelines ...n/articles/data-factory/pipelines-disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by providing PowerShell-based automation examples and referencing Windows-centric tools (such as Azure PowerShell and Visio). There are no equivalent Linux shell (Bash/CLI) examples or references to Linux-native tools for automation, deployment, or architecture visualization. The use of PowerShell for trigger management and private endpoint approval is presented without alternative CLI or Bash scripts, and the downloadable architecture diagram is in Visio format, which is less accessible to Linux users.
Recommendations
  • Provide equivalent Azure CLI (az) and Bash script examples for all PowerShell automation tasks, such as disabling triggers and approving private endpoints.
  • Mention and link to cross-platform alternatives for architecture diagrams, such as SVG, PNG, or draw.io, in addition to Visio files.
  • Ensure that references to automation or scripting cover both Windows and Linux environments, ideally presenting examples side-by-side.
  • Explicitly state that all CI/CD and Git integration steps can be performed from Linux/macOS environments, and provide links to relevant documentation.
  • Review and update any references to Windows-only tools or patterns to include their Linux equivalents, ensuring parity in guidance.
GitHub Create Pull Request
Data Factory Create Azure Data Factory using .NET SDK ...data-factory/quickstart-create-data-factory-dot-net.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows by exclusively referencing Visual Studio (a Windows-centric IDE), using PowerShell commands for NuGet package installation, and omitting any mention of Linux development environments or cross-platform alternatives. There are no instructions or examples for Linux users, such as using VS Code, .NET CLI, or Bash for package management and project creation.
Recommendations
  • Add instructions for creating and running the .NET project using cross-platform tools like VS Code and the .NET CLI.
  • Include NuGet package installation examples using the dotnet CLI (e.g., 'dotnet add package ...') alongside PowerShell commands.
  • Mention Linux and macOS compatibility, and provide steps for setting up the development environment on those platforms.
  • Clarify that the .NET SDK and Azure Data Factory APIs are cross-platform, and provide troubleshooting tips for non-Windows environments.
  • Avoid assuming Visual Studio as the default IDE; suggest alternatives like VS Code or JetBrains Rider.
GitHub Create Pull Request
Data Factory Troubleshoot SSIS Integration Runtime management ...ry/ssis-integration-runtime-management-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page displays a Windows bias by referencing Windows-specific tools (SSMS), using Windows-centric terminology (main.cmd), and omitting Linux equivalents or examples. Troubleshooting steps and recommendations are tailored to Windows environments, with no mention of Linux-compatible tools or scripts, which may hinder users operating in Linux-based environments.
Recommendations
  • Provide Linux-specific troubleshooting examples and commands alongside Windows/PowerShell instructions.
  • Mention and demonstrate use of cross-platform SQL management tools (e.g., Azure Data Studio, sqlcmd) in addition to SSMS.
  • Clarify that custom setup scripts can use .sh (shell scripts) for Linux environments, not just main.cmd (batch files).
  • Include guidance for testing and executing custom setup scripts on Linux VMs, not only Windows.
  • Explicitly state platform requirements and compatibility for SSIS IR management tasks.
  • Where PowerShell is referenced, offer Bash/Azure CLI equivalents for Linux users.
GitHub Create Pull Request
Data Factory Monitor integration runtime in Azure Data Factory ...n/articles/data-factory/monitor-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-10 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 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 being installed on 'on-premises Windows machines,' with no reference to Linux support or deployment. Windows-centric tools (PowerShell, SSMS, SSDT) are mentioned exclusively or first, and there are no examples or instructions for Linux environments or cross-platform scenarios.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for all PowerShell commands, especially for monitoring integration runtimes.
  • Clarify whether self-hosted integration runtime can be installed on Linux machines; if so, include instructions and examples for Linux deployment and monitoring.
  • Mention and demonstrate cross-platform tools (e.g., Azure CLI, REST API) for monitoring and managing integration runtimes.
  • Avoid language that assumes Windows as the default (e.g., 'Node is an on-premises Windows machine'), and instead use inclusive phrasing or specify platform requirements.
  • Include references to Linux-compatible database management tools (e.g., Azure Data Studio) alongside SSMS/SSDT.
  • Add troubleshooting and operational guidance for Linux environments where applicable.
GitHub Create Pull Request
Data Factory Monitor SSIS operations with Azure Monitor ...e-docs/blob/main/articles/data-factory/monitor-ssis.md
High Priority View Details →
Scanned: 2026-01-10 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 page demonstrates Windows bias by referencing Windows-centric tools (SSMS, SSDT, SQL Server Agent, Azure PowerShell) exclusively, and omitting Linux alternatives or examples. All operational instructions and examples assume the use of Windows tools, with no mention of Linux-compatible methods for monitoring or querying SSIS operations. The order of presentation also places Windows tools and patterns before any general or cross-platform approaches.
Recommendations
  • Include examples using Azure CLI for monitoring SSIS IR operational status, as Azure CLI is cross-platform and works on Linux.
  • Mention and provide instructions for querying SSIS logs and metrics using REST APIs or SDKs that are available on Linux.
  • Reference Linux-compatible database management tools (e.g., Azure Data Studio) alongside SSMS for querying SSISDB.
  • Clarify whether SSIS package execution and monitoring is supported from Linux environments, and if so, provide guidance.
  • Add explicit notes or sections for Linux users, detailing any limitations or alternative workflows.
  • Ensure that all examples and tool recommendations are presented in a platform-neutral order, or provide parity between Windows and Linux instructions.
GitHub Create Pull Request
Data Factory Create an Azure Data Factory using Bicep ...s/data-factory/quickstart-create-data-factory-bicep.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Examples for deploying and managing resources are provided for both Azure CLI and Azure PowerShell, but PowerShell (a Windows-centric tool) is given equal prominence to CLI, which is cross-platform. The instructions for creating a sample file specifically mention Notepad, a Windows-only editor, without suggesting Linux alternatives. There are no explicit Linux shell or editor examples, nor any mention of Linux-specific patterns or tools.
Recommendations
  • When instructing users to create a text file, mention cross-platform editors such as nano, vim, or gedit for Linux/Mac users, alongside Notepad.
  • Consider providing bash shell commands for file creation (e.g., echo 'John, Doe' > emp.txt) as an alternative to manual editing.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and Mac.
  • If mentioning PowerShell, note that PowerShell Core is available on Linux and Mac, or provide bash equivalents for Linux users.
  • Where UI screenshots are shown, clarify that the Azure portal experience is the same across platforms.
GitHub Create Pull Request
Data Factory Transform data using Hadoop Streaming activity .../data-factory/transform-data-using-hadoop-streaming.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page shows evidence of Windows bias in its examples and terminology. The JSON sample exclusively uses Windows-style executables (e.g., MyMapper.exe, MyReducer.exe), which are not portable to Linux-based Hadoop clusters. There are no examples or mentions of Linux-compatible scripts (e.g., Python, Bash, or Java JARs), nor is there guidance for users running on Linux clusters, which are the default for HDInsight. The tutorial link references PowerShell, a Windows-centric tool, before any cross-platform alternatives.
Recommendations
  • Provide Linux-compatible examples, such as Python scripts, shell scripts, or Java JARs for mapper and reducer.
  • Explicitly mention that HDInsight clusters are Linux-based by default and clarify executable requirements.
  • Include cross-platform instructions and examples (e.g., using Bash, Python, or Java) alongside any Windows-specific ones.
  • Reference cross-platform tools (e.g., Azure CLI, Bash) before or alongside PowerShell in tutorials and guidance.
  • Add notes about file permissions and script execution for Linux environments.
GitHub Create Pull Request
Data Factory Set up a self-hosted integration runtime for the SAP CDC connector ...ta-factory/sap-change-data-capture-shir-preparation.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All installation and configuration steps assume a Windows environment, including references to installing assemblies to the GAC, editing the Windows hosts file, and using PowerShell for connectivity testing. There are no examples or instructions for Linux environments, nor are Linux tools or commands mentioned.
Recommendations
  • Provide equivalent instructions for Linux environments, including installation steps for the SAP .NET Connector (if supported) or alternative connectors.
  • Include Linux commands for connectivity testing (e.g., using 'nc' or 'telnet' instead of PowerShell).
  • Describe how to edit the hosts file on Linux (typically /etc/hosts) and provide example commands.
  • Clarify platform requirements and limitations early in the documentation, specifying if only Windows is supported or if Linux is also possible.
  • If the self-hosted integration runtime is Windows-only, make this explicit and explain why.
GitHub Create Pull Request
Data Factory Self-hosted integration runtime autoupdate and expire notification ...factory/self-hosted-integration-runtime-auto-update.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell, and the instructions reference the self-hosted integration runtime client, which is a Windows application. There are no Linux-specific examples, nor any mention of Linux tools or shell commands. The documentation assumes the user is operating in a Windows environment, with no guidance for Linux users.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux environments alongside PowerShell commands.
  • Clarify whether the self-hosted integration runtime client and features (such as autoupdate and expire notification) are supported on Linux, and document any differences.
  • Mention and link to Linux installation and management instructions if available.
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
  • If Linux is not supported, clearly communicate this to avoid confusion.
GitHub Create Pull Request
Data Factory Use custom activities in a pipeline ...s/data-factory/transform-data-using-custom-activity.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. Most command-line examples use PowerShell, and Windows tools (e.g., cmd, .exe files) are referenced exclusively or before any Linux equivalents. There are no Linux shell (bash/sh) examples, nor are Linux-native tools or patterns (such as .sh scripts or bash commands) mentioned. The documentation implies Windows as the default environment for custom activities, with commands like 'cmd /c dir' and references to .exe applications, and does not provide parity for Linux users or guidance for running custom activities on Linux Batch pool nodes.
Recommendations
  • Provide equivalent examples for Linux environments, such as bash/sh commands (e.g., 'bash -c "echo hello world"') and .sh scripts.
  • Mention and demonstrate how to use Linux-based Batch pool nodes, including specifying OS type in pool configuration.
  • Include sample custom applications as .sh or Python scripts, not just .exe files.
  • Show how to execute and monitor pipelines using Azure CLI or REST API, not only PowerShell.
  • Clarify that both Windows and Linux are supported as Batch pool node operating systems, and highlight any differences in command syntax or file handling.
  • Add notes or tables comparing Windows and Linux usage patterns for custom activities, including environment setup, file paths, and command execution.
GitHub Create Pull Request
Data Factory Create an Azure Data Factory using REST API ...ata-factory/quickstart-create-data-factory-rest-api.md
High Priority View Details →
Scanned: 2026-01-10 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 biased towards Windows and PowerShell. All command-line examples use Azure PowerShell cmdlets, with no mention of Linux-native tools, Bash, or cross-platform alternatives. The instructions assume the reader is using PowerShell, and even the authentication and REST API invocation steps rely on PowerShell-specific modules. Azure Storage Explorer is suggested as a GUI tool, which is cross-platform, but no CLI alternatives (such as azcopy or Azure CLI) are mentioned. There are no Bash, curl, or Azure CLI examples, and no guidance for Linux or macOS users.
Recommendations
  • Provide equivalent examples using Azure CLI (az) for all steps, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API invocation examples using curl or httpie, which are standard tools on Linux/macOS.
  • Add Bash script examples for setting variables and authenticating, alongside PowerShell.
  • Mention azcopy as a CLI alternative to Azure Storage Explorer for file operations.
  • Explicitly state platform requirements and offer guidance for both Windows and Linux/macOS users.
  • Reorganize the documentation so that cross-platform tools (Azure CLI, REST API via curl) are presented before or alongside PowerShell.
GitHub Create Pull Request
Data Factory Troubleshoot security and access control issues ...tory/security-and-access-control-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-10 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 exhibits a Windows bias in several areas. Troubleshooting steps and examples frequently reference Windows-specific tools (e.g., PsPing.exe), commands, and file paths (e.g., editing C:\Windows\System32\drivers\etc\hosts). There are no equivalent Linux examples or instructions (such as using ping, nc, or editing /etc/hosts). Windows tools and patterns are mentioned exclusively or before any cross-platform alternatives, and the documentation assumes the use of Windows-based Azure VMs without acknowledging Linux scenarios.
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 examples and screenshots for both Windows and Linux environments when referencing file paths, commands, or configuration changes.
  • Mention cross-platform tools (e.g., PowerShell Core, curl) where possible, and clarify when a step is OS-specific.
  • Order troubleshooting instructions so that cross-platform or OS-neutral steps are presented first, followed by OS-specific details.
  • Explicitly state when a solution applies only to Windows, and offer alternative steps for Linux users.
GitHub Create Pull Request
Data Factory Self-hosted integration runtime diagnostic tool ...ory/self-hosted-integration-runtime-diagnostic-tool.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references Windows tools and workflows, such as the use of 'dmgcmd.exe' and the Configuration Manager UI, without mentioning Linux equivalents or providing Linux-specific instructions. There are no examples or guidance for running the diagnostic tool on Linux systems, and the documentation implicitly assumes a Windows environment.
Recommendations
  • Add explicit information about Linux support: clarify whether the diagnostic tool is available for Linux, and if so, provide installation and usage instructions for Linux environments.
  • Provide Linux command-line examples alongside Windows examples, or state clearly if the tool is Windows-only.
  • Mention any Linux-specific requirements or limitations, and include screenshots or terminal output relevant to Linux if supported.
  • If the tool is not available for Linux, state this clearly at the beginning of the documentation and suggest alternative troubleshooting steps for Linux users.
GitHub Create Pull Request
Data Factory Troubleshoot self-hosted integration runtime ...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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
This documentation page exhibits a strong Windows bias. Troubleshooting steps, examples, and tool references are almost exclusively Windows-centric, with frequent use of Windows-specific tools (Event Viewer, MMC, Registry Editor, Certutil, Process Monitor, PowerShell, etc.), and instructions are written for Windows environments. There are no Linux-specific troubleshooting steps, examples, or tool alternatives provided, even though self-hosted IR can be run on Linux (via Docker) in some scenarios. Windows methods are presented first and often exclusively, with no parity for Linux users.
Recommendations
  • Add Linux-specific troubleshooting steps and examples for all major scenarios, especially for log collection, certificate management, service management, and connectivity.
  • Include equivalent Linux commands (e.g., using journalctl, systemctl, openssl, curl, wget, netstat, telnet, etc.) alongside Windows commands.
  • Reference Linux tools (such as syslog, dmesg, systemd, OpenSSL, Wireshark, etc.) where Windows tools like Event Viewer, MMC, or Process Monitor are mentioned.
  • Provide guidance for managing IR services and permissions on Linux (e.g., using systemd, file permissions, Docker container logs).
  • Ensure all registry-related instructions have Linux environment variable or configuration file equivalents.
  • Where PowerShell is used, offer Bash or shell script alternatives for Linux environments.
  • Clarify which troubleshooting steps are OS-specific and provide clear sections for both Windows and Linux users.
  • Add screenshots or terminal output examples from Linux environments where only Windows screenshots are currently shown.
GitHub Create Pull Request
Data Factory Configure a self-hosted integration runtime as a proxy for SSIS ...-factory/self-hosted-integration-runtime-proxy-ssis.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All command-line examples use PowerShell, and references to configuration and debugging (such as Local Security Policy, NT SERVICE accounts, and file paths like C:\ProgramData) are Windows-centric. There is no mention of Linux or cross-platform alternatives for installing, configuring, or running the self-hosted IR. Tools and patterns (Visual Studio, SSMS, Windows authentication, etc.) are exclusively or primarily Windows-based, and Linux equivalents are not discussed or provided.
Recommendations
  • Provide Linux-specific instructions for installing and configuring the self-hosted IR, including supported distributions and prerequisites.
  • Include command-line examples using Bash or shell scripts in addition to PowerShell, or clarify if PowerShell Core is supported on Linux.
  • Document how to manage service accounts, authentication, and permissions on Linux (e.g., systemd service configuration, user/group management).
  • Specify log file locations and troubleshooting steps for Linux environments.
  • Clarify whether features like Windows authentication are supported or have alternatives on Linux.
  • Mention any limitations or differences when running self-hosted IR on Linux, and provide guidance for cross-platform scenarios.
  • Add references to Linux-compatible tools for package development and deployment, if available.
GitHub Create Pull Request
Data Factory Source control ...docs/blob/main/articles/data-factory/source-control.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page displays a moderate Windows bias. PowerShell is referenced as a primary method for making changes to the Data Factory service, and troubleshooting steps mention updating properties via PowerShell or the REST API. There is a lack of explicit Linux or cross-platform CLI examples, and Windows-centric tools (PowerShell, Azure Portal) are mentioned without alternatives or parity for Linux users. No Linux-specific instructions, shell commands, or references to cross-platform tools (e.g., Azure CLI) are provided, and Windows/PowerShell methods are mentioned before any Linux equivalents (which are absent).
Recommendations
  • Add explicit Azure CLI examples for all operations currently described with PowerShell, ensuring parity for Linux/macOS users.
  • Include references to cross-platform tools and workflows (e.g., Bash, Azure CLI, VS Code on Linux/macOS) alongside Windows/PowerShell instructions.
  • Where PowerShell is mentioned, clarify that equivalent operations can be performed using Azure CLI or REST API from any OS, and provide example commands.
  • Review troubleshooting and configuration sections to ensure Linux users are not excluded, and add notes or links for Linux/macOS environments.
  • Consider adding a section or callouts for Linux/macOS users, highlighting any differences or additional steps required.
GitHub Create Pull Request
Data Factory Transform data using Hadoop Hive activity ...icles/data-factory/transform-data-using-hadoop-hive.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing a tutorial that uses PowerShell ('Tutorial: transform data'), which is typically Windows-centric, and does not provide equivalent Linux/bash examples or mention cross-platform alternatives. The page also uses Windows-style path separators (backslashes) in the example ('MyAzureStorage\HiveScripts\MyHiveScript.hql'), which may confuse Linux users. There is no mention of Linux command-line tools or workflows, and no guidance for users working on Linux or macOS environments.
Recommendations
  • Add Linux/bash examples alongside PowerShell instructions, or provide cross-platform CLI guidance (e.g., Azure CLI, Bash).
  • Use platform-neutral path separators (forward slashes) in examples, or clarify path conventions for both Windows and Linux.
  • Explicitly mention that the Hive activity can be configured and managed from Linux/macOS environments, and link to relevant tutorials.
  • Ensure that referenced tutorials (such as 'Tutorial: transform data') have Linux/bash equivalents or alternatives.
  • Where UI screenshots are shown, clarify that the UI is accessible from any OS via browser, and highlight any OS-specific considerations.
GitHub Create Pull Request
← Previous Page 10 of 40 Next →