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 101-125 of 1000 flagged pages
Data Factory Migrate data from Amazon S3 to Azure Storage ...ta-factory/data-migration-guidance-s3-azure-storage.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in its guidance for deploying self-hosted Integration Runtime (IR) for Azure Data Factory. Specifically, it only mentions installing the IR on Windows VMs and provides configuration recommendations exclusively for Windows (e.g., Standard_D32s_v3 VM type). There are no examples, instructions, or references for deploying IR on Linux VMs or using Linux-based tools, despite the fact that Linux is a common platform for enterprise workloads. This may lead Linux users to believe that Windows is required for self-hosted IR, which is not accurate.
Recommendations
  • Explicitly mention that self-hosted Integration Runtime can be installed on both Windows and Linux VMs, if supported.
  • Provide step-by-step instructions or links for installing and configuring IR on Linux VMs.
  • Include Linux-specific best practices for monitoring and scaling IR (e.g., using Linux-native monitoring tools).
  • Offer example VM sizes and configurations for Linux, similar to the Windows VM recommendations.
  • Ensure that any references to OS-specific requirements or limitations are clearly stated.
GitHub Create Pull Request
Data Factory Enable Microsoft Entra authentication for Azure SSIS integration runtime ...ata-factory/enable-aad-authentication-azure-ssis-ir.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows environments, with all command-line examples using PowerShell, and all database management steps requiring SQL Server Management Studio (SSMS), a Windows-only tool. There are no examples or instructions for Linux users, such as using Azure CLI, Bash, or cross-platform database tools. Windows-centric tools and patterns are mentioned exclusively and before any alternatives, if any.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell commands, especially for group and managed identity management.
  • Include instructions for using cross-platform database tools (e.g., Azure Data Studio, sqlcmd) for T-SQL operations instead of only SSMS.
  • Clearly indicate which steps require Windows-only tools and offer Linux/macOS alternatives where possible.
  • Add a section or callouts for Linux users, outlining supported workflows and any limitations.
  • Ensure parity in example scripts and screenshots for both Windows and Linux environments.
GitHub Create Pull Request
Data Factory Encrypt credentials in Azure Data Factory ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/encrypt-credentials-self-hosted-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell cmdlets (New-AzDataFactoryV2LinkedServiceEncryptedCredential, Set-AzDataFactoryV2LinkedService) and references DPAPI, a Windows-specific encryption technology. All examples and prerequisites assume a Windows environment, with no mention of Linux equivalents, cross-platform alternatives, or guidance for non-Windows users. The documentation implicitly prioritizes Windows tooling and patterns, omitting Linux support or parity.
Recommendations
  • Provide equivalent instructions and examples for Linux environments, including supported tools and workflows.
  • Clarify whether DPAPI-based encryption is supported or available on Linux, and offer alternatives if not.
  • Mention cross-platform PowerShell (pwsh) usage and any differences in behavior or prerequisites on Linux/macOS.
  • If the cmdlets or features are Windows-only, explicitly state this limitation and suggest workarounds or alternatives for Linux users.
  • Include a section or note on how to perform credential encryption and linked service setup on Linux, or link to relevant resources.
GitHub Create Pull Request
Data Factory Install licensed components for Azure-SSIS integration runtime ...ry/how-to-develop-azure-ssis-ir-licensed-components.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All instructions, environment variables, and examples are specific to Windows (e.g., registry edits, use of Windows environment variables, Windows file paths, and GAC). There are no Linux equivalents or cross-platform guidance, and the documentation assumes a Windows operating environment throughout.
Recommendations
  • Add explicit statements about platform support, clarifying whether Linux is supported or not.
  • If Linux is supported, provide equivalent instructions for Linux environments (e.g., environment variable management, file paths, component installation, and activation key storage).
  • Include Linux-specific examples or note limitations for Linux users.
  • Mention cross-platform alternatives for Windows-only tools (e.g., registry, GAC) or provide guidance for Linux deployment scenarios.
  • If only Windows is supported, make this clear early in the documentation to set expectations.
GitHub Create Pull Request
Data Factory Security considerations .../data-factory/data-movement-security-considerations.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: PowerShell cmdlets are used exclusively for credential management and encryption examples, Windows-specific tools like DPAPI and Windows Firewall are referenced without Linux equivalents, and instructions for port management and credential encryption focus on Windows environments. There are no examples or guidance for Linux-based self-hosted integration runtime installations, nor are Linux-native tools or firewall configurations discussed.
Recommendations
  • Provide equivalent Linux examples for credential encryption and management, including command-line tools and scripts (e.g., bash, OpenSSL, GPG).
  • Document how credential storage and encryption are handled on Linux-based self-hosted integration runtime installations, including which encryption mechanisms are used.
  • Include Linux firewall configuration instructions (e.g., using iptables, firewalld, or ufw) alongside Windows Firewall guidance.
  • Mention Linux-specific port management and security practices where relevant.
  • Clarify whether PowerShell cmdlets are required for Linux installations, or provide alternative methods for Linux users.
  • Add notes or sections explicitly addressing Linux support and parity for all security-related operations.
GitHub Create Pull Request
Data Factory How to clean up SSISDB logs automatically ...ctory/how-to-clean-up-ssisdb-logs-with-elastic-jobs.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments and tooling. It exclusively references SQL Server Management Studio (SSMS) for configuration steps, which is a Windows-only application, and does not mention or provide guidance for Linux or cross-platform alternatives (such as Azure Data Studio or command-line tools). All configuration and management steps are described using SSMS and T-SQL, with no examples for Linux-native workflows or tools. PowerShell is used for automation, but Bash or other Linux scripting options are not discussed. The documentation assumes the reader is using Windows-based tools and does not address Linux users' needs.
Recommendations
  • Provide equivalent instructions using Azure Data Studio, which is cross-platform, for configuring SSISDB log clean-up properties.
  • Include examples using Bash scripts and sqlcmd for invoking SSISDB stored procedures and automating log clean-up on Linux.
  • Mention and demonstrate how to perform relevant tasks using the Azure CLI, which is available on Linux, macOS, and Windows.
  • Add guidance for connecting to SSISDB from Linux environments, including authentication and connectivity tips.
  • Ensure that all screenshots and step-by-step instructions are available for both Windows and Linux tools where possible.
GitHub Create Pull Request
Data Factory Create schedule triggers ...rticles/data-factory/how-to-create-schedule-trigger.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. The Azure PowerShell section is presented before the Azure CLI, and PowerShell is described with explicit instructions for installation on Windows. The sample code for PowerShell uses Windows-style file paths (e.g., C:\ADFv2QuickStartPSH\) and refers to Windows-specific tooling. There are no Linux-specific instructions or examples for PowerShell, nor is there mention of cross-platform compatibility for PowerShell. The CLI section is present and cross-platform, but is introduced after PowerShell, reinforcing a Windows-first pattern. No explicit Linux shell (bash) examples or Linux file path conventions are provided.
Recommendations
  • Provide explicit instructions for installing and using Azure PowerShell on Linux and macOS, including platform-agnostic installation links.
  • Include PowerShell examples using Linux/macOS file paths (e.g., /home/user/ADFv2QuickStartPSH/) and clarify that PowerShell is cross-platform.
  • Add bash or shell script examples for common tasks, especially for creating and managing triggers via Azure CLI.
  • Present Azure CLI examples before PowerShell, or in parallel, to emphasize cross-platform support.
  • Add notes or sections highlighting Linux/macOS usage, including troubleshooting or differences in behavior.
  • Where file paths are mentioned, show both Windows and Linux/macOS conventions.
GitHub Create Pull Request
Data Factory Assess your Azure Data Factory pipelines for migration to Fabric ...ur-azure-data-factory-to-fabric-data-factory-migration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by exclusively referencing the PowerShell upgrade tool for migration, without mentioning Linux-compatible alternatives (such as Azure CLI or REST API). All migration tool examples and recommendations are centered on PowerShell, a Windows-centric technology, and there are no examples or guidance for Linux or cross-platform users. The tool is mentioned multiple times as the primary or sole migration method, reinforcing Windows-first patterns.
Recommendations
  • Include instructions and examples for migration using Azure CLI and/or REST API, which are cross-platform and work on Linux and macOS.
  • Explicitly mention whether the PowerShell upgrade tool can be run on Linux/macOS (e.g., via PowerShell Core), and provide installation guidance if so.
  • Provide parity in examples: for every PowerShell example, add an equivalent Azure CLI or REST API example.
  • Add a section addressing migration for users on Linux/macOS, including troubleshooting and tool compatibility notes.
  • Avoid recommending Windows-centric tools as the only or primary migration path; present alternatives equally.
GitHub Create Pull Request
Data Factory Provision Enterprise Edition for the Azure-SSIS Integration Runtime ...y/how-to-configure-azure-ssis-ir-enterprise-edition.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively provides instructions using Azure PowerShell, a Windows-centric tool, and does not mention or provide examples for Linux or cross-platform alternatives such as Azure CLI. Windows authentication is referenced for SSAS connectivity, further reinforcing a Windows-first approach. There are no Linux-specific instructions or parity in tooling or examples.
Recommendations
  • Add equivalent Azure CLI instructions and examples for provisioning and configuring Azure-SSIS IR, as Azure CLI is cross-platform.
  • Explicitly mention platform compatibility for all tools and components, clarifying if steps can be performed on Linux or macOS.
  • Provide guidance for Linux users, including any prerequisites or limitations for running SSIS IR-related tasks on non-Windows platforms.
  • Reference authentication methods that work across platforms, or clarify Windows-only requirements.
  • Ensure that documentation sections do not assume a Windows environment by default, and offer alternatives where possible.
GitHub Create Pull Request
Data Factory Customize the setup for an Azure-SSIS Integration Runtime ...factory/how-to-configure-azure-ssis-ir-custom-setup.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric: all examples, scripts, and tooling references assume a Windows environment (e.g., .cmd, .bat, .exe, .msi, PowerShell, Windows commands like cmdkey and set). There are no Linux or cross-platform examples, and all instructions and sample setups reference Windows-only tools and patterns. Even the express custom setup options are exclusively for Windows commands/components. No mention is made of Linux equivalents or how to perform similar tasks on non-Windows platforms.
Recommendations
  • Clarify early in the documentation that Azure-SSIS IR is Windows-only, or explicitly state platform limitations.
  • If Linux support is possible or planned, provide equivalent examples for Linux (e.g., bash scripts, Linux service management, Linux environment variables).
  • Where possible, use cross-platform tooling (e.g., Azure CLI instead of PowerShell) and provide examples for both Windows and Linux.
  • For custom setup scripts, mention if .sh or other Linux script types are supported, or explicitly state that only Windows scripting is allowed.
  • For express custom setups, consider adding options for Linux commands or configurations if the underlying platform supports it.
  • In sample setups, note which components are Windows-specific and suggest alternatives or workarounds for Linux environments if applicable.
GitHub Create Pull Request
Data Factory Create tumbling window triggers .../data-factory/how-to-create-tumbling-window-trigger.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias, particularly in the PowerShell sample section. The PowerShell instructions specifically reference installing Azure PowerShell on Windows and saving files to Windows-style paths (e.g., C:\ADFv2QuickStartPSH\MyTrigger.json). The prerequisites and examples for PowerShell are tailored to Windows users, with no mention of Linux or macOS alternatives. While the Azure CLI section is cross-platform, the PowerShell section is presented first and more extensively, and there is no explicit guidance for Linux users regarding PowerShell or file paths.
Recommendations
  • Add explicit instructions for running Azure PowerShell on Linux and macOS, including installation steps and any platform-specific considerations.
  • Use platform-neutral file paths in examples (e.g., ./MyTrigger.json) or provide both Windows and Linux/macOS path examples.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Consider presenting Azure CLI examples before PowerShell, or side-by-side, to avoid implicit prioritization of Windows tools.
  • Include notes or links for users who may be using Bash, zsh, or other shells on Linux/macOS, especially for scripting and automation.
GitHub Create Pull Request
Data Factory Execute SQL Server Integration Services (SSIS) packages with the Azure-enabled dtexec utility ...ory/how-to-invoke-ssis-package-azure-enabled-dtexec.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias. It exclusively references Windows tools (SSMS, AzureDTExec.exe), provides only Windows command-line examples, and relies on Windows-specific patterns such as UNC paths and 'Run as administrator'. There is no mention of Linux support, installation, or usage, nor are any Linux-specific examples or alternatives provided.
Recommendations
  • Clarify whether AzureDTExec and SSMS are available or supported on Linux or via cross-platform means (e.g., Azure CLI, Docker).
  • If Linux is supported, provide installation and usage instructions for Linux environments, including command-line examples.
  • If not supported, explicitly state that AzureDTExec is Windows-only and suggest Linux alternatives for running SSIS packages in Azure (if any).
  • Avoid Windows-specific terminology (e.g., 'Run as administrator', UNC paths) or provide Linux equivalents where possible.
  • Consider including cross-platform orchestration options and examples, such as using Azure Data Factory REST API or Azure CLI from Linux.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools such as SQL Server Management Studio (SSMS) and SQL Managed Instance Agent jobs, with no mention of Linux alternatives or cross-platform tools. There are no examples or instructions for Linux environments, and the documentation assumes familiarity with Windows networking concepts (e.g., NSG, Windows Firewall). The use of Windows terminology and tools is presented as the default or only option, with no parity for Linux users.
Recommendations
  • Include examples and instructions for managing Azure SQL Managed Instance and SSIS workloads from Linux environments, such as using Azure CLI, Data Factory REST API, or cross-platform SQL tools.
  • Mention cross-platform alternatives to SSMS, such as Azure Data Studio, and provide guidance for their use.
  • Clarify which steps or tools are Windows-specific and provide Linux equivalents where possible (e.g., firewall configuration, agent job scheduling).
  • Add explicit notes or sections for Linux users, including troubleshooting and setup steps relevant to non-Windows platforms.
  • Ensure that references to tools and patterns do not assume a Windows-first audience, and present cross-platform options alongside Windows ones.
GitHub Create Pull Request
Data Factory include file ...tory/includes/data-factory-quickstart-prerequisites.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates 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 or home directories), and all file path references use Windows conventions. The instructions implicitly assume a Windows environment, omitting guidance for Linux or macOS users.
Recommendations
  • Include Linux/macOS equivalents for file creation (e.g., using nano, vim, or TextEdit).
  • Provide example file paths for Linux/macOS (e.g., ~/ADFv2QuickStart or /home/user/ADFv2QuickStart).
  • Mention cross-platform text editors and folder creation commands.
  • Add notes clarifying that instructions apply to all platforms, or provide platform-specific instructions where necessary.
  • Ensure screenshots and examples do not exclusively show Windows environments.
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-11 00:00
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 demonstrates mild Windows bias. PowerShell is mentioned as a primary monitoring and management tool, and is listed before other automation interfaces (API, Azure Monitor logs, portal). The related content section features a PowerShell quickstart link before .NET, Python, and REST, suggesting a Windows-first approach. There is no explicit mention of Linux-specific tools, shell scripting, or cross-platform command-line usage. The documentation assumes familiarity with Windows-centric tools and patterns, potentially making it less approachable for Linux users.
Recommendations
  • Add explicit examples and references for Linux users, such as Bash scripting and CLI usage for Data Factory management.
  • Ensure parity in quickstart and tutorial links by including Linux shell and Azure CLI guides alongside PowerShell.
  • When listing automation or monitoring options, avoid putting PowerShell first; instead, present options in a neutral or alphabetical order.
  • Mention cross-platform compatibility for tools and clarify which are available on Linux, macOS, and Windows.
  • Include references to Linux-native tools and workflows where applicable, such as integration with cron jobs, shell scripts, or Linux-based CI/CD pipelines.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a bias towards Windows environments, particularly in the section on forcing a refresh of user permissions, where only PowerShell commands are provided and referenced. There are no equivalent Linux or cross-platform CLI examples (such as Azure CLI, Bash, or REST API usage from non-Windows environments). The documentation assumes the use of Windows tools and patterns, and does not mention or prioritize Linux alternatives.
Recommendations
  • Provide equivalent instructions for Linux/macOS environments, such as using Azure CLI, Bash, or REST API calls directly.
  • Include examples for cross-platform tools (e.g., curl for REST API calls) alongside PowerShell commands.
  • Explicitly state platform requirements or clarify that steps can be performed from any OS where the necessary tools are available.
  • Where screenshots or instructions reference Windows-only tools, add notes or alternatives for Linux users.
  • Consider reordering or balancing examples so that Windows and Linux approaches are presented with equal prominence.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All code automation and scripting examples are provided exclusively using Azure PowerShell, which is most commonly used on Windows. File paths and folder creation instructions use Windows-style paths (e.g., C:\ADF\RunSSISPackage), and there is no mention of Linux-compatible alternatives such as Bash, Azure CLI, or cross-platform scripting. The documentation does not provide Linux or macOS-specific instructions, nor does it acknowledge how to perform these steps on non-Windows platforms.
Recommendations
  • Add equivalent examples using Azure CLI and Bash scripts, which are cross-platform and widely used on Linux and macOS.
  • Include Linux/macOS file path conventions and instructions for creating and managing files and folders.
  • Explicitly mention cross-platform compatibility of Azure Data Factory and SSIS, and provide guidance for users on non-Windows systems.
  • Where PowerShell is used, note that it is available on Linux/macOS and provide installation instructions or alternatives.
  • Reorder sections so that platform-neutral or cross-platform methods (e.g., Azure portal, REST API, Azure CLI) are presented before or alongside Windows/PowerShell methods.
GitHub Create Pull Request
Data Factory Schedule an Azure-SSIS integration runtime ...tory/how-to-schedule-azure-ssis-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias, primarily through the exclusive use of PowerShell for scripting and automation examples, reliance on Windows-centric tools such as SQL Server Management Studio (SSMS), and the absence of any Linux or cross-platform alternatives. All code samples and automation workflows are provided in PowerShell, with no mention of Bash, Azure CLI, or other Linux-friendly options. The monitoring and scheduling sections also focus on PowerShell and SSMS, both of which are Windows-native tools. There are no instructions or examples for users on Linux or macOS platforms, nor are there references to platform-agnostic approaches.
Recommendations
  • Include equivalent examples using Azure CLI and Bash scripts for starting, stopping, and monitoring Azure-SSIS IR, alongside PowerShell.
  • Provide instructions for connecting to and managing SSIS packages using cross-platform tools (e.g., Azure Data Studio, REST API via curl, or other SQL clients available on Linux/macOS).
  • Add notes or sections clarifying platform compatibility, and explicitly mention how Linux/macOS users can perform the same tasks.
  • Where PowerShell is used, offer alternative command-line snippets for Bash or Azure CLI, and reference official documentation for those tools.
  • Highlight any limitations or differences in experience for non-Windows users, and suggest workarounds or best practices for Linux/macOS environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-v2-connector-get-started.md ...tory/includes/data-factory-v2-connector-get-started.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation lists Azure PowerShell as a primary tool for performing the copy activity, which is strongly associated with Windows environments. The order of tools places PowerShell before REST API and ARM templates, and there is no mention of Linux-native command-line tools (such as Azure CLI) or bash examples. The examples and tool references lean towards Windows-centric patterns, potentially making it less approachable for Linux users.
Recommendations
  • Add Azure CLI as a recommended tool for performing the copy activity, with links to relevant quickstart guides.
  • Include bash or shell script examples alongside PowerShell examples to ensure Linux users have parity.
  • Reorder the list to avoid implicit prioritization of Windows tools; consider grouping by platform or listing cross-platform tools first.
  • Explicitly mention cross-platform compatibility for each tool, clarifying which ones work natively on 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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by frequently referencing Azure PowerShell as a primary method for provisioning and configuring Azure-SSIS IR, listing PowerShell-based instructions and links before alternatives. There is a lack of explicit Linux CLI (Azure CLI) examples or parity, and the tooling and patterns described (such as PowerShell and SSIS) are traditionally Windows-centric, with no mention of Linux-native workflows or tools.
Recommendations
  • Add explicit Azure CLI examples and instructions alongside or before Azure PowerShell references to ensure Linux users have clear guidance.
  • Include notes or sections on how to perform key tasks (such as joining Azure-SSIS IR to a virtual network) using cross-platform tools, highlighting any differences or limitations.
  • Where PowerShell is referenced, clarify if the steps are available via Azure CLI or other Linux-friendly methods, and provide links or examples.
  • Review related content and tutorials to ensure Linux parity, adding Linux-specific instructions where necessary.
  • Consider mentioning SSIS alternatives or integration runtimes that are more Linux-friendly, if applicable, or clarify the Windows-centric nature of SSIS.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing Azure PowerShell examples for command-line operations, which are primarily used on Windows. There are no equivalent examples for Linux users (e.g., Azure CLI or Bash scripts), and the only automation tooling referenced is PowerShell. The structure also places PowerShell instructions before any mention of cross-platform alternatives, reinforcing a Windows-first approach.
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/macOS, if PowerShell must be used, and provide installation instructions.
  • Include Bash script examples where appropriate, especially for automation scenarios.
  • Reorganize the documentation so that cross-platform tools (Azure CLI, REST API) are presented alongside or before Windows-specific tools.
  • Clearly indicate which tools and commands are platform-agnostic and which are Windows-specific.
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-11 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 exhibits a strong Windows bias, primarily through exclusive use of PowerShell commands for monitoring integration runtimes, repeated references to Windows-based nodes for self-hosted integration runtime, and lack of Linux or cross-platform CLI examples. Windows tools and patterns (PowerShell, SSMS, SSDT) are mentioned throughout, with no mention of Linux equivalents or alternatives. There are no Bash, Azure CLI, or Linux-specific instructions or examples, and the documentation assumes self-hosted IR nodes are Windows machines.
Recommendations
  • Add Azure CLI examples for all monitoring tasks alongside PowerShell, ensuring parity for Linux and macOS users.
  • Clarify that self-hosted integration runtime can be installed on Linux (if supported), and provide instructions/examples for Linux deployments.
  • Include Bash script samples and Linux command-line monitoring approaches where relevant.
  • Mention and link to cross-platform tools (e.g., Azure Data Studio) in addition to Windows-only tools like SSMS and SSDT.
  • Explicitly state platform requirements and alternatives for each tool or command, ensuring users on non-Windows platforms are not excluded.
  • Review and update language to avoid assuming Windows as the default environment for self-hosted IR nodes.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (Azure PowerShell, SSMS, SSDT, SQL Server Agent) exclusively or before any cross-platform or Linux alternatives. There are no Linux-specific examples, nor is there mention of Linux command-line tools or monitoring approaches. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users.
Recommendations
  • Include examples using Azure CLI, which is cross-platform and commonly used on Linux.
  • Mention and provide instructions for monitoring SSIS IR status and logs using REST API calls, which are platform-agnostic.
  • Reference or link to Linux-compatible SQL client tools (e.g., Azure Data Studio, DBeaver) for querying SSISDB or logs.
  • Add explicit notes or sections for Linux users, outlining how to perform equivalent monitoring and querying tasks without relying on Windows-only tools.
  • Ensure that examples and screenshots are not exclusively from Windows environments (e.g., avoid only showing SSMS or PowerShell interfaces).
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only Azure PowerShell examples for creating managed virtual networks and managed private endpoints, with no equivalent examples for Linux users (e.g., Azure CLI, REST API, or ARM templates). Windows-centric tooling (PowerShell, New-AzResource) is presented as the default and only method, and there is no mention of Linux-friendly alternatives. This prioritizes Windows workflows and may hinder Linux users from easily following the instructions.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, ensuring Linux and macOS users have clear guidance.
  • Include REST API and ARM template snippets for resource creation to provide platform-neutral options.
  • Explicitly mention that PowerShell instructions are for Windows and provide links or inline examples for Linux/macOS users.
  • Review screenshots and instructions to ensure they do not assume a Windows environment (e.g., avoid showing only Windows UIs or PowerShell terminals).
  • Add a section comparing available tooling (PowerShell, CLI, REST, Portal) and recommend options for different platforms.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page mentions PowerShell as a primary programmatic monitoring method and lists it before Python and REST API. There are no explicit Linux-specific examples or references to Linux command-line tools (such as Bash, CLI, or shell scripting). The documentation does not provide parity for Linux users in terms of examples or tooling, and the ordering suggests a Windows-first approach.
Recommendations
  • Add explicit examples for Linux users, such as using Azure CLI or Bash scripts for monitoring Data Factory.
  • When listing programmatic options, alternate or balance the order (e.g., mention Python, Azure CLI, and REST API before or alongside PowerShell).
  • Include references to Linux-compatible tools and workflows, such as shell scripting, cron jobs, or integration with Linux monitoring solutions.
  • Provide sample commands for both Windows (PowerShell) and Linux (Bash/Azure CLI) in relevant sections.
  • Review linked articles to ensure Linux parity in code samples and instructions.
GitHub Create Pull Request
← Previous Page 5 of 40 Next →