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 326-350 of 1000 flagged pages
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-resource-manager-template.md ...ure-ssis-integration-runtime-resource-manager-template.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 strong Windows bias by exclusively providing PowerShell-based deployment and management examples for Azure Resource Manager templates and Azure-SSIS integration runtime. There are no examples or guidance for Linux or cross-platform CLI tools (such as Azure CLI), and Windows-centric tools and patterns (PowerShell cmdlets) are mentioned first and exclusively. The related links also reinforce PowerShell and Windows-centric workflows, with no mention of Linux or macOS alternatives.
Recommendations
  • Add equivalent Azure CLI examples for deploying and managing Azure-SSIS IR, which work on Linux, macOS, and Windows.
  • Explicitly mention cross-platform options and clarify that PowerShell is not required for these operations.
  • Provide guidance or links for users working on Linux or macOS, including any prerequisites or differences.
  • Ensure that documentation sections do not assume a Windows environment by default; present cross-platform tools first or alongside Windows-specific ones.
  • Include notes on how to perform these tasks in Bash or other common shells.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-shared-self-hosted-integration-runtime-powershell.md ...eate-shared-self-hosted-integration-runtime-powershell.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 demonstrates a strong Windows bias by providing only PowerShell-based instructions and examples, explicitly referencing Windows tools such as Windows PowerShell ISE, and omitting any Linux or cross-platform command-line alternatives. The installation instructions and scripting guidance are tailored exclusively to Windows environments, with no mention of Bash, Azure CLI, or Linux-specific steps.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Provide instructions for installing and running the self-hosted integration runtime on Linux machines, if supported.
  • Replace references to 'Windows PowerShell ISE' with more generic editors or mention alternatives (e.g., VS Code, terminal) for non-Windows users.
  • Clarify platform requirements for the integration runtime installer and note any Linux/macOS support or limitations.
  • Ensure all prerequisite steps (such as authentication and resource creation) have both PowerShell and Azure CLI/Bash examples.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-integration-runtime.md ...icles/data-factory/create-azure-integration-runtime.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 provides a command-line example only for Azure PowerShell (Windows-centric), with no mention of Azure CLI or Bash alternatives that are commonly used on Linux and macOS. The use of PowerShell cmdlets as the sole scripting example demonstrates a bias toward Windows users and tools. There is no guidance or parity for Linux users who may prefer or require Azure CLI or Bash scripting.
Recommendations
  • Add equivalent Azure CLI examples for creating and configuring Azure Integration Runtime, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that Azure PowerShell is available on Linux and macOS, or provide installation instructions for non-Windows platforms.
  • Include Bash script examples or references for users who prefer shell scripting.
  • Where possible, present CLI and PowerShell examples side-by-side, or indicate both options in headings and instructions.
  • Review related documentation links to ensure Linux-friendly tools and workflows are represented.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-portal.md ...actory/create-azure-ssis-integration-runtime-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation exhibits a Windows bias by referencing Windows-centric tools and concepts (e.g., SSMS, UNC paths, SQL Server Agent, PowerShell), prioritizing Windows authentication and management patterns, and omitting Linux-specific instructions or examples. The only CLI example referenced is PowerShell, with no mention of Bash, Azure CLI, or Linux-native workflows. File system examples use UNC paths, which are Windows-specific, and there is no guidance for Linux-based package management or access. The documentation assumes familiarity with Windows environments and does not provide parity for Linux users.
Recommendations
  • Add Azure CLI and Bash examples for provisioning and managing Azure-SSIS IR, alongside PowerShell.
  • Include instructions for accessing Azure Files and file systems from Linux, using SMB/CIFS mounts or Azure CLI.
  • Provide guidance for managing SSIS packages and integration runtimes from Linux environments, including alternative tools to SSMS.
  • Clarify authentication options for Linux users, such as using managed identities or service principals, and document any limitations.
  • Review all file system references to ensure Linux-compatible paths and access methods are included.
  • Explicitly state platform requirements and offer links to Linux setup guides where relevant.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-self-hosted-integration-runtime.md ...data-factory/create-self-hosted-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits strong Windows bias. All installation instructions, prerequisites, and examples are exclusively for Windows environments. PowerShell is the only scripting language shown for automation and setup. Windows-specific tools (Microsoft Integration Runtime Configuration Manager, registry edits, NT SERVICE accounts, Windows Firewall) are referenced throughout, with no mention of Linux equivalents or cross-platform support. There are no examples or guidance for installing or running the self-hosted integration runtime on Linux or macOS, nor are alternative command-line tools or shell scripts provided.
Recommendations
  • Clearly state platform support at the top of the documentation (e.g., 'Windows only' or 'Windows and Linux supported').
  • If Linux/macOS are supported, provide installation instructions, prerequisites, and examples for those platforms (e.g., using .tar.gz installers, systemd services, bash scripts).
  • Include Linux-specific configuration guidance (e.g., firewall setup with iptables/ufw, service management via systemd, environment variable configuration).
  • Offer cross-platform automation examples (e.g., Bash, Python, Azure CLI) alongside PowerShell.
  • Reference Linux equivalents for Windows tools (e.g., mention how to manage service accounts, configure proxies, and handle credentials on Linux).
  • If only Windows is supported, make this explicit and suggest alternatives for Linux users (such as using Azure-hosted IR or other integration methods).
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-factory-service-identity.md ...articles/data-factory/data-factory-service-identity.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 for managed identity in Azure Data Factory demonstrates a Windows bias. PowerShell is the only CLI tool shown in command examples, and all programmatic instructions for generating and retrieving managed identities use PowerShell first or exclusively. There are no examples using Azure CLI (which is cross-platform), Bash, or Linux-native tools. The instructions for retrieving application IDs and assigning roles also rely on PowerShell, with no Linux or Azure CLI equivalents provided.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, including creating, updating, and retrieving managed identities.
  • Provide Bash script samples for REST API calls, using curl or httpie, to illustrate Linux usage.
  • Explicitly mention that Azure CLI and REST API are cross-platform and suitable for Linux/macOS users.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
  • Include notes or sections on how Linux/macOS users can perform these tasks without PowerShell.
  • Ensure screenshots and UI instructions are not Windows-specific, or clarify their cross-platform applicability.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-flow-script.md ...cs/blob/main/articles/data-factory/data-flow-script.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 page demonstrates a Windows bias by referencing PowerShell as the primary method for programmatically interacting with Data Flow Script outside the UI, without mentioning Linux or cross-platform alternatives. Windows tooling (PowerShell cmdlet) is presented as the default, and there are no examples or instructions for Linux users (e.g., Bash, Azure CLI, REST API usage from Linux). This may hinder Linux users' ability to follow or replicate the documented workflows.
Recommendations
  • Add examples for generating and submitting Data Flow Scripts using Bash, Azure CLI, or REST API from Linux environments.
  • Mention cross-platform tools and approaches alongside PowerShell, rather than presenting PowerShell first or exclusively.
  • Clarify that PowerShell is available on Linux, but also provide native Linux shell examples for parity.
  • Include explicit instructions or code snippets for Linux users to format and submit scripts, ensuring equal accessibility.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-migration-guidance-hdfs-azure-storage.md ...-factory/data-migration-guidance-hdfs-azure-storage.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by repeatedly specifying that the Data Factory self-hosted integration runtime must be installed on a Windows machine or VM, with no mention of Linux support or examples. Windows is presented as the default or only platform for hosting the integration runtime, and pricing estimates explicitly reference Azure Windows VMs. There are no Linux-based instructions, examples, or recommendations for running the integration runtime, nor is there guidance for Linux users who may wish to participate in Hadoop-to-Azure migrations.
Recommendations
  • Explicitly state whether the Data Factory self-hosted integration runtime supports Linux, and if so, provide installation and configuration instructions for Linux hosts.
  • Include Linux-based examples and architectures alongside Windows, especially for environments where Hadoop clusters are commonly Linux-based.
  • Update pricing and scaling guidance to include Linux VM options and cost comparisons.
  • Clarify any platform-specific limitations or advantages (e.g., performance, security) for both Windows and Linux hosts.
  • Ensure that authentication and credential management sections address Linux scenarios (e.g., Kerberos on Linux, Linux service accounts).
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/enable-aad-authentication-azure-ssis-ir.md ...ata-factory/enable-aad-authentication-azure-ssis-ir.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 strong Windows bias by exclusively providing PowerShell commands for scripting tasks, referencing Windows-only tools such as SQL Server Management Studio (SSMS), and omitting any Linux or cross-platform alternatives for key operations (e.g., group management, database access, IR provisioning). The workflow assumes the use of Windows environments and tools, with no mention of equivalent Linux commands, Azure CLI, or cross-platform database clients. Windows-centric instructions are presented first and exclusively, leaving Linux users without guidance.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands, especially for Microsoft Entra group and member management, and Data Factory IR provisioning.
  • Include instructions for connecting to Azure SQL Database/Managed Instance using cross-platform tools such as Azure Data Studio or sqlcmd, alongside SSMS.
  • Add Linux-specific examples for installing required modules, authenticating, and running scripts.
  • Explicitly state platform requirements and offer parity guidance for Linux/macOS users.
  • Ensure all steps that currently use Windows-only tools have cross-platform alternatives documented.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-factory-troubleshoot-guide.md ...ticles/data-factory/data-factory-troubleshoot-guide.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 shows evidence of Windows bias, particularly in the Azure Batch troubleshooting section, where PowerShell is used exclusively for unzip commands and file extraction examples. Windows tools such as PowerShell and Fiddler are referenced without mentioning Linux alternatives. The documentation also references Windows-specific compression behavior ('deflate64') before mentioning third-party or cross-platform tools. Linux equivalents for command-line operations, troubleshooting, and tool usage are missing or not given equal prominence.
Recommendations
  • Provide Linux/bash equivalents for PowerShell commands, especially for file extraction and zip/unzip operations in Azure Batch troubleshooting.
  • Mention cross-platform or Linux-native tools (e.g., tcpdump, curl, unzip, Wireshark) alongside Windows tools like Fiddler for network troubleshooting.
  • When discussing compression issues, reference Linux zip utilities and clarify how to avoid unsupported formats on both Windows and Linux.
  • Ensure troubleshooting steps and examples are presented for both Windows and Linux environments, or clarify platform-specific instructions.
  • Add explicit notes or sections for Linux users where workflows or commands differ from Windows, to improve parity and inclusiveness.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-migration-guidance-s3-azure-storage.md ...ta-factory/data-migration-guidance-s3-azure-storage.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 a Windows bias in several areas. It exclusively recommends installing the self-hosted Integration Runtime (IR) on Azure Windows VMs, with no mention of Linux VM support or examples. Configuration details, scaling recommendations, and best practices are all described in the context of Windows VMs. There are no Linux-specific instructions, examples, or parity notes, and Windows is presented as the default and only supported platform for self-hosted IR scenarios.
Recommendations
  • Explicitly state whether self-hosted Integration Runtime supports installation on Linux VMs. If supported, provide equivalent instructions and best practices for Linux environments.
  • Include Linux VM configuration examples, including recommended VM sizes, scaling, and monitoring guidance.
  • If Windows is required for self-hosted IR, clarify this limitation early in the documentation and provide rationale.
  • Add parity notes or a comparison table showing platform support (Windows vs. Linux) for self-hosted IR.
  • Where possible, provide cross-platform examples for authentication, monitoring, and scaling, or link to relevant Linux documentation.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/encrypt-credentials-self-hosted-integration-runtime.md ...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-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 strong Windows bias by exclusively using PowerShell cmdlets (New-AzDataFactoryV2LinkedServiceEncryptedCredential, Set-AzDataFactoryV2LinkedService) and referencing DPAPI, a Windows-specific encryption technology. All examples and instructions assume the use of PowerShell and Windows tooling, with no mention of Linux equivalents, Bash, or cross-platform alternatives. Prerequisites specifically require PowerShell 7.0+, but do not clarify Linux support or provide Linux-specific guidance.
Recommendations
  • Provide equivalent instructions and examples for Linux environments, including Bash or cross-platform CLI usage if available.
  • Clarify whether the cmdlets and DPAPI-based encryption are supported on Linux self-hosted integration runtime nodes, or provide alternative approaches for Linux.
  • Explicitly state platform requirements and limitations for credential encryption, including any differences in behavior or support between Windows and Linux.
  • If PowerShell is required, include installation and usage instructions for PowerShell on Linux, and test/confirm that the cmdlets work as described.
  • Mention or link to any cross-platform tools or APIs that can be used for credential encryption in Azure Data Factory.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-assess-your-azure-data-factory-to-fabric-data-factory-migration.md ...ur-azure-data-factory-to-fabric-data-factory-migration.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 repeatedly references the PowerShell upgrade tool as the primary or sole method for migrating pipelines, without mentioning or providing examples for Linux/macOS users or alternative cross-platform tools. No Linux-specific instructions, shell script examples, or CLI alternatives are provided, and Windows/PowerShell tooling is suggested first and exclusively.
Recommendations
  • Include migration instructions and examples using Azure CLI, which is cross-platform and available on Linux/macOS.
  • Mention and provide sample Bash shell scripts for exporting/importing pipeline data, where applicable.
  • Explicitly state PowerShell Core compatibility and provide installation guidance for Linux/macOS users if PowerShell is required.
  • Add a section comparing available migration tools for Windows and Linux, listing pros/cons and usage for each.
  • Ensure that all tool references are platform-neutral or that Linux/macOS equivalents are presented alongside Windows options.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-create-tumbling-window-trigger.md .../data-factory/how-to-create-tumbling-window-trigger.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 page exhibits Windows bias primarily through its heavy use of PowerShell for automation examples, explicit references to Windows file paths (e.g., C:\ADFv2QuickStartPSH\), and installation instructions for Azure PowerShell that are Windows-centric. The PowerShell section appears before the Azure CLI section, and there are no explicit Linux shell (bash) or cross-platform scripting examples. The instructions for creating JSON files and running commands assume a Windows environment, and there is no mention of Linux-specific considerations or alternative workflows.
Recommendations
  • Add explicit bash/Linux shell examples for creating, starting, and monitoring triggers using the Azure CLI, including file path conventions (e.g., ~/ADFv2QuickStartCLI/).
  • Include instructions for installing Azure PowerShell and Azure CLI on Linux and macOS, not just Windows.
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform parity.
  • Avoid hardcoding Windows file paths in example commands; use environment-agnostic or platform-specific alternatives.
  • Add notes or sections highlighting any differences or considerations when running these commands on Linux/macOS (e.g., file permissions, path separators).
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/enable-customer-managed-key.md ...n/articles/data-factory/enable-customer-managed-key.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 demonstrates a Windows bias by referencing PowerShell and Azure CLI as the primary methods for configuring Key Vault properties, without providing explicit Linux shell or cross-platform CLI examples. The instructions and screenshots focus on the Azure portal UI, which is platform-agnostic, but when command-line tools are mentioned, PowerShell is listed first and exclusively. There are no bash or Linux-specific examples, nor is there guidance for users on Linux systems for equivalent operations.
Recommendations
  • Include explicit bash/Azure CLI examples for all command-line operations, especially for enabling Key Vault properties and managing identities.
  • When listing command-line options, present Azure CLI (which is cross-platform) before PowerShell, or provide both side-by-side.
  • Add notes or sections clarifying that all Azure CLI commands work equally on Linux, macOS, and Windows, and provide sample commands for each.
  • Avoid language that implies PowerShell is the default or preferred method unless necessary, and ensure parity in instructions for Linux users.
  • Where screenshots are used, consider including CLI output or terminal screenshots from Linux environments, not just portal UI.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-clean-up-ssisdb-logs-with-elastic-jobs.md ...ctory/how-to-clean-up-ssisdb-logs-with-elastic-jobs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows-centric tools and workflows, such as SQL Server Management Studio (SSMS) and SQL Server Agent, for configuring and scheduling SSISDB log clean-up. All GUI instructions and screenshots are based on SSMS, which is primarily a Windows application. There are no examples or guidance for performing these tasks using Linux-native tools, cross-platform SQL clients, or command-line alternatives. PowerShell is mentioned for Elastic Database Jobs, but Bash or other Linux shell equivalents are not provided. The documentation assumes the reader is using Windows environments and tools, with no mention of Linux or macOS support or alternatives.
Recommendations
  • Add instructions for configuring SSISDB log clean-up using cross-platform SQL clients (e.g., Azure Data Studio, DBeaver) that run on Linux and macOS.
  • Provide CLI-based examples using sqlcmd or Azure CLI for connecting to SSISDB and modifying properties, in addition to SSMS GUI steps.
  • Include Bash script examples for Elastic Database Jobs alongside PowerShell, highlighting how Linux users can automate these tasks.
  • Explicitly mention platform requirements and alternatives for users on Linux or macOS, including any limitations or workarounds.
  • Add screenshots and step-by-step guides for non-Windows environments where possible, or clarify which steps are Windows-specific.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-configure-azure-ssis-ir-enterprise-edition.md ...y/how-to-configure-azure-ssis-ir-enterprise-edition.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 demonstrates a strong Windows bias by exclusively providing Azure PowerShell instructions for provisioning the Azure-SSIS Integration Runtime Enterprise Edition. There are no examples or guidance for Linux users (e.g., using Azure CLI or REST API), and Windows authentication and tooling are referenced without mention of Linux alternatives. This may hinder accessibility for users on non-Windows platforms.
Recommendations
  • Add equivalent instructions and sample scripts for provisioning Azure-SSIS IR using Azure CLI and/or REST API, which are cross-platform.
  • Reference Linux-compatible tools and workflows where possible, such as Azure CLI installation and usage.
  • Clarify platform requirements and limitations, and provide guidance for users on macOS and Linux.
  • If certain features require Windows-only components, explicitly state this and suggest alternatives or workarounds for Linux users.
  • Ensure authentication examples include both Windows and non-Windows scenarios.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-create-schedule-trigger.md ...rticles/data-factory/how-to-create-schedule-trigger.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 displays a Windows bias in several ways: PowerShell is presented before Azure CLI, and the PowerShell section explicitly references installation on Windows and uses Windows-style file paths (e.g., C:\ADFv2QuickStartPSH\). There are no Linux-specific instructions or examples for PowerShell or CLI usage (e.g., bash, Linux file paths, or shell environments). The prerequisites and sample code for PowerShell are Windows-centric, and there is no mention of Linux equivalents or cross-platform considerations in those sections.
Recommendations
  • Add explicit instructions for installing and using Azure PowerShell on Linux and macOS, including links to cross-platform installation guides.
  • Provide sample PowerShell commands using Linux/macOS file paths (e.g., /home/user/ADFv2QuickStartPSH/) alongside Windows examples.
  • In the Azure CLI section, clarify that the CLI is cross-platform and show examples of usage in bash/zsh environments, including Linux/macOS file system paths.
  • Reorder sections so that cross-platform tools (Azure CLI, SDKs) are presented before Windows-specific tools (PowerShell), or present them in parallel.
  • Add notes or callouts highlighting platform differences and considerations for Linux/macOS users, such as file path formats and shell environments.
  • Ensure that screenshots and UI references are not Windows-specific unless necessary, and provide alternatives or clarifications for other platforms.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-ingest-data-into-fabric-from-azure-data-factory.md ...how-to-ingest-data-into-fabric-from-azure-data-factory.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 demonstrates a bias toward Windows environments, particularly in the authentication section. PowerShell is presented as the only method to force a permissions refresh, with no mention of Linux or cross-platform alternatives. Windows tools and patterns (PowerShell, running as Administrator) are referenced exclusively, and there are no equivalent CLI or script examples for Linux/macOS users. The documentation implicitly assumes a Windows-first workflow and omits guidance for non-Windows platforms.
Recommendations
  • Provide equivalent Linux/macOS instructions for refreshing permissions, such as using Azure CLI, REST API calls via curl, or cross-platform scripting.
  • Include examples using Bash or other cross-platform shells alongside PowerShell.
  • Clarify which steps are platform-agnostic and which require Windows-specific tools, and offer alternatives where possible.
  • Explicitly state that PowerShell commands can be run on Linux/macOS (if true), or provide installation guidance for PowerShell Core on those platforms.
  • Add notes or sections for Linux users, especially for steps involving command-line operations or administrative tasks.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-azure-enabled-dtexec.md ...ory/how-to-invoke-ssis-package-azure-enabled-dtexec.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. It exclusively references Windows tools (SSMS, AzureDTExec.exe), Windows installation paths, and Windows-specific configuration steps (such as 'Run as administrator', UAC prompts, and UNC paths). There are no examples or guidance for Linux users, nor is there mention of cross-platform alternatives or usage patterns.
Recommendations
  • Clarify whether AzureDTExec is available or supported on Linux or macOS, and if not, explicitly state this limitation.
  • If AzureDTExec is Windows-only, suggest alternative approaches for Linux users (such as using Azure Data Factory REST APIs, PowerShell Core, or other cross-platform tools).
  • Provide equivalent command-line examples for Linux (if possible), including installation and invocation steps.
  • Discuss how SSIS packages can be managed or executed from non-Windows environments, or link to relevant documentation.
  • Mention file path conventions for Linux (e.g., /mnt/...) and clarify UNC path usage in cross-platform scenarios.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-stored-procedure-activity.md ...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-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 strong Windows bias. All command-line automation and scripting examples are provided exclusively using Azure PowerShell, with explicit references to Windows file paths (e.g., C:\ADF\RunSSISPackage) and no mention of Linux or cross-platform alternatives such as Azure CLI, Bash, or PowerShell Core on Linux/macOS. The documentation assumes a Windows environment for scripting and file management, and does not provide parity for Linux users.
Recommendations
  • Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and commonly used on Linux/macOS.
  • Use platform-agnostic file paths or provide both Windows (C:\...) and Linux/macOS (~/ADF/RunSSISPackage) path examples.
  • Mention and demonstrate how to use PowerShell Core (pwsh), which is available on Linux and macOS, instead of assuming Windows PowerShell.
  • Explicitly state that the instructions are applicable to all platforms, or provide separate sections for Windows and Linux/macOS users.
  • Include notes or links for installing and using Azure PowerShell or Azure CLI on Linux/macOS.
  • Avoid assuming the user is operating from a Windows environment; clarify any platform-specific requirements.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-create-install-integration-runtime.md ...des/data-factory-create-install-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 Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell, and installation instructions exclusively reference Windows tools and UI patterns (e.g., 'Add or Remove Programs', Windows installer dialogs). The download link and instructions are explicitly for a Windows machine, with no mention of Linux or cross-platform alternatives. There are no Linux shell or CLI examples, nor any guidance for installing or running the integration runtime on Linux systems.
Recommendations
  • Provide equivalent Linux instructions, including supported distributions and installation methods (e.g., .deb/.rpm packages, tarballs, or Docker containers).
  • Include bash or shell script examples for command-line operations, alongside PowerShell.
  • Clarify platform support for the integration runtime, and explicitly state if Linux is not supported or provide links to Linux-specific documentation.
  • If a GUI installer is not available for Linux, document command-line registration and configuration steps.
  • Mention Linux-specific troubleshooting or configuration steps where relevant.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-quickstart-prerequisites.md ...tory/includes/data-factory-quickstart-prerequisites.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 demonstrates a Windows bias by referencing Windows-specific tools and patterns, such as Notepad and the C:\ADFv2QuickStartPSH folder, without providing equivalent instructions for Linux or macOS users. There are no examples or guidance for Linux text editors, file paths, or alternative workflows, and Windows conventions are presented as the default.
Recommendations
  • Include instructions for creating the emp.txt file using common Linux/macOS text editors (e.g., nano, vim, gedit) and save paths (e.g., /home/user/ADFv2QuickStart).
  • Mention cross-platform file path conventions and provide examples for both Windows and Linux/macOS.
  • Avoid referencing Windows-specific folders or tools exclusively; offer alternatives for other operating systems.
  • Add a note clarifying that the steps can be performed on any OS, and link to platform-specific guidance where appropriate.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-ssis-activity.md ...ta-factory/how-to-invoke-ssis-package-ssis-activity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows Authentication First Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias. It exclusively references Windows authentication, Windows file paths (UNC), Windows-centric tools (SQL Server Data Tools, SQL Server Management Studio), and patterns (domain/username/password for Windows authentication). There are no Linux-specific examples, nor is there any mention of Linux file paths, authentication mechanisms, or tooling. The guidance assumes a Windows environment for SSIS package creation, storage, and execution, and does not address Linux alternatives or cross-platform considerations.
Recommendations
  • Add explicit notes on Linux support or limitations for Azure-SSIS IR and SSIS package execution.
  • Include examples using Linux-compatible authentication (e.g., SQL authentication, managed identity) and clarify when Windows authentication is required.
  • Provide guidance for storing and accessing SSIS packages from Linux-based file shares (e.g., NFS, SMB/CIFS from Linux clients), including path formats and credential handling.
  • Mention cross-platform tools for SSIS package development and management, or clarify that SSDT and SSMS are Windows-only and suggest alternatives if available.
  • Clarify whether UNC paths and Windows-style credentials are required, and offer Linux equivalents or workarounds where possible.
  • Add a section on troubleshooting or considerations for users running pipelines from Linux environments, including any Azure Data Factory Studio limitations.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-use-sql-managed-instance-with-ir.md ...ata-factory/how-to-use-sql-managed-instance-with-ir.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 page demonstrates a Windows bias by exclusively referencing Windows-centric tools and patterns such as SQL Server Management Studio (SSMS), SQL Managed Instance Agent jobs, and Windows Firewall rules. There are no examples or guidance for Linux-based management tools, nor are cross-platform alternatives mentioned. The documentation assumes familiarity with Windows networking concepts and troubleshooting tools, and does not provide parity for Linux users or administrators.
Recommendations
  • Include examples and instructions for managing Azure SQL Managed Instance and SSIS workloads using cross-platform tools such as Azure Data Studio, Azure CLI, and REST APIs.
  • Mention Linux-compatible alternatives to SSMS, such as Azure Data Studio, and provide links or examples for their use.
  • Describe how to configure network security and troubleshoot connectivity using Linux tools (e.g., iptables, firewalld, netstat, curl) alongside Windows Firewall and PowerShell.
  • Add guidance for scheduling and automating SSIS package execution using cross-platform solutions (e.g., Azure Automation, cron jobs with Azure CLI) in addition to SQL Agent jobs.
  • Ensure that troubleshooting steps and advanced scenarios do not assume Windows-only environments, and provide Linux-specific notes where relevant.
GitHub Create Pull Request
← Previous Page 14 of 40 Next →