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 201-225 of 1000 flagged pages
Data Factory Create an Azure-SSIS integration runtime in Azure Data Factory .../data-factory/create-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
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools (SSDT, SSMS, dtutil, PowerShell) for deploying and managing Azure-SSIS IR, without mentioning or providing Linux alternatives or cross-platform equivalents. PowerShell is highlighted as the primary scripting method, and there are no examples or guidance for Linux users (e.g., Bash, Azure CLI). Windows tools and patterns are mentioned first and exclusively, leaving Linux users without clear instructions.
Recommendations
  • Add examples and instructions for provisioning Azure-SSIS IR using Azure CLI and Bash scripts, which are cross-platform and widely used on Linux.
  • Mention and provide guidance for using cross-platform database tools (e.g., Azure Data Studio) alongside SSMS.
  • Clarify which steps and tools are Windows-only and offer Linux-compatible alternatives where possible.
  • Include explicit Linux setup instructions for prerequisites, such as configuring firewall rules or authentication using CLI tools.
  • Ensure that all command-line utility references (such as dtutil) specify platform compatibility and suggest alternatives for Linux environments.
GitHub Create Pull Request
Data Factory Create a shared self-hosted integration runtime with PowerShell ...eate-shared-self-hosted-integration-runtime-powershell.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 by providing only PowerShell-based instructions for command-line setup, explicitly referencing Windows PowerShell ISE, and linking to Windows-centric installation guides. There are no equivalent examples or instructions for Linux or macOS users, nor any mention of cross-platform CLI alternatives such as Azure CLI or Bash scripts. The installer instructions do not clarify OS compatibility, and the documentation assumes a Windows environment throughout.
Recommendations
  • Provide equivalent instructions using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Include Bash script examples for Linux/macOS environments where appropriate.
  • Clarify whether the self-hosted integration runtime installer is available for Linux/macOS, and provide installation steps for those platforms if supported.
  • Avoid referencing Windows-specific tools (e.g., PowerShell ISE) as the default; mention cross-platform alternatives first or alongside.
  • Add explicit notes about OS compatibility and requirements for all steps.
  • Ensure screenshots and UI references are not Windows-specific unless necessary, and provide parity for other platforms.
GitHub Create Pull Request
Data Factory Using credentials ...re-docs/blob/main/articles/data-factory/credentials.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 Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools and workflows such as PowerShell and the Azure portal (which is most commonly used on Windows). Scripted management mentions PowerShell and SDKs, but does not provide examples for Linux-native tools (e.g., Azure CLI, Bash). No Linux or cross-platform command-line examples are given, and the order of tool mention (PowerShell before REST API, CLI omitted) further reinforces the bias. Screenshots and instructions focus on GUI workflows typical of Windows environments.
Recommendations
  • Add Azure CLI examples for all scripted steps, including creating and assigning managed identities, and credential management.
  • Explicitly mention cross-platform compatibility of SDKs and REST APIs, and provide sample commands for Linux/macOS users.
  • Include screenshots or instructions for using the Azure portal on non-Windows platforms, or clarify that the portal is web-based and OS-agnostic.
  • Reorder tool mentions to avoid prioritizing Windows tools (e.g., list Azure CLI before PowerShell, or group them together).
  • Add a section or tab for Linux/macOS command-line workflows, ensuring parity with Windows instructions.
GitHub Create Pull Request
Data Factory Managed identity ...articles/data-factory/data-factory-service-identity.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 demonstrates a Windows bias by providing PowerShell-based examples for generating and retrieving managed identities, referencing Windows-specific tools (PowerShell), and omitting equivalent Linux/CLI examples. The PowerShell approach is presented first and in detail, while cross-platform alternatives such as Azure CLI are not mentioned. This may disadvantage users on Linux or macOS who do not use PowerShell.
Recommendations
  • Add Azure CLI examples for all operations currently shown only with PowerShell (e.g., generating and retrieving managed identities).
  • Present cross-platform tools (Azure CLI, REST API) before or alongside Windows-specific tools like PowerShell.
  • Explicitly mention that PowerShell examples are for Windows and provide parity for Linux/macOS users.
  • Include bash shell and Azure CLI command snippets where appropriate.
  • Review and update screenshots and instructions to ensure they are not Windows-centric (e.g., avoid showing Windows file paths or PowerShell prompts exclusively).
GitHub Create Pull Request
Data Factory Mapping data flow script ...cs/blob/main/articles/data-factory/data-flow-script.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 First Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the primary method for programmatically interacting with Data Flow Script, without mentioning Linux or cross-platform alternatives. Windows tooling (PowerShell cmdlet) is presented as the default or only option for script automation, and no Linux shell or CLI examples are provided. This may hinder discoverability and usability for Linux users.
Recommendations
  • Include equivalent examples using Azure CLI, Bash, or other cross-platform tools for generating and submitting Data Flow Scripts.
  • Explicitly mention that Data Flow Script can be used from Linux/macOS environments and provide guidance or links for those platforms.
  • Where PowerShell is referenced, add parallel instructions for Bash or Azure CLI, and clarify platform compatibility.
  • Review related articles and ensure Linux parity in automation and scripting sections.
GitHub Create Pull Request
Data Factory Migrate data from an on-premises Hadoop cluster to Azure Storage ...-factory/data-migration-guidance-hdfs-azure-storage.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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, without mentioning Linux as an option. All architectural diagrams and implementation steps reference Windows VMs exclusively, and the pricing section explicitly excludes Azure Windows VM costs, implying Windows is the default or only supported platform. There are no examples or guidance for deploying the integration runtime on Linux, nor any mention of Linux-specific considerations, tools, or patterns.
Recommendations
  • Explicitly state whether the Data Factory self-hosted integration runtime supports Linux, and if so, provide equivalent instructions and examples for Linux deployments.
  • Include architectural diagrams and implementation steps that show both Windows and Linux VM options for hosting the integration runtime.
  • Update pricing examples to include both Windows and Linux VM cost scenarios, or clarify platform support.
  • Where authentication or system integration is discussed (e.g., Kerberos), clarify any platform-specific differences and provide Linux configuration guidance.
  • Add troubleshooting and best practices sections for Linux environments, if supported.
  • If Linux is not supported, clearly document this limitation and provide rationale or roadmap information.
GitHub Create Pull Request
Data Factory General Troubleshooting ...ticles/data-factory/data-factory-troubleshoot-guide.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 Windows bias in several areas. Powershell is used exclusively in custom activity troubleshooting examples (e.g., for unzipping files in Azure Batch), and Windows-specific tools such as Fiddler are recommended for network troubleshooting without mention of Linux alternatives. Additionally, the explanation of unsupported compression algorithms references Windows default behavior first, and does not mention Linux zip utilities or patterns. There are no Linux shell (bash) or cross-platform CLI examples provided alongside the Windows-centric instructions.
Recommendations
  • Provide equivalent bash or Linux shell commands for file operations (e.g., unzip) in Azure Batch troubleshooting, alongside Powershell examples.
  • Mention and provide instructions for Linux-compatible network troubleshooting tools (e.g., tcpdump, Wireshark, curl) in addition to Fiddler.
  • When discussing compression algorithms, include information about how Linux zip utilities behave and how to create compatible zip files on Linux.
  • Ensure examples and tool recommendations are presented in a cross-platform manner, or at least include both Windows and Linux options.
  • Review all troubleshooting steps to ensure parity for users operating in Linux environments, especially for integration runtime and cluster access scenarios.
GitHub Create Pull Request
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-10 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 Windows bias by exclusively recommending and describing installation of self-hosted Integration Runtime on Azure Windows VMs, with no mention of Linux VM support or examples. Configuration and scaling guidance is given only for Windows VMs, and there are no Linux-specific instructions, examples, or parity notes. This may lead Linux users to believe their platform is unsupported or suboptimal for this scenario.
Recommendations
  • Explicitly state whether self-hosted Integration Runtime supports installation on Linux VMs. If supported, provide equivalent instructions and recommendations for Linux VM deployment, configuration, and scaling.
  • Include Linux-based examples and best practices alongside Windows examples, such as recommended VM sizes, monitoring tools, and troubleshooting steps for Linux environments.
  • Clarify any platform-specific limitations or differences in performance, management, or security between Windows and Linux deployments.
  • Where possible, provide cross-platform guidance (e.g., generic VM requirements, OS-agnostic steps) to avoid unnecessary platform bias.
GitHub Create Pull Request
Data Factory Security considerations .../data-factory/data-movement-security-considerations.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 clear Windows bias in its hybrid/on-premises sections. It exclusively references Windows-specific technologies such as PowerShell cmdlets (Set-AzDataFactoryV2LinkedService, New-AzDataFactoryV2LinkedServiceEncryptedCredential), Windows DPAPI for credential encryption, and Windows Firewall for local firewall configuration. There are no Linux or cross-platform equivalents mentioned, nor are there examples for Linux-based deployments of the self-hosted integration runtime. The port requirements and credential management instructions are tailored to Windows environments, with no guidance for Linux users.
Recommendations
  • Provide Linux-specific instructions for installing and configuring the self-hosted integration runtime, including credential encryption and storage.
  • Include examples using Linux command-line tools (e.g., bash scripts, OpenSSL, systemd services) for credential management and runtime configuration.
  • Document how credential encryption is handled on Linux (e.g., using libsecret, GnuPG, or other secure storage mechanisms) instead of or in addition to Windows DPAPI.
  • Mention Linux firewall configuration (e.g., iptables, firewalld, ufw) alongside Windows Firewall, and provide port opening instructions for both platforms.
  • Offer parity in PowerShell and bash/CLI examples for all credential and runtime management tasks.
  • Clarify any platform-specific limitations or differences in security features between Windows and Linux deployments.
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-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 are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. The use of SSMS (SQL Server Management Studio), a Windows-only application, is required for several steps, and no alternatives (such as Azure Data Studio or sqlcmd) are suggested. The documentation does not provide Linux or cross-platform instructions, and Windows-centric tools and patterns are mentioned first and exclusively throughout the page.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for all PowerShell commands.
  • Suggest cross-platform SQL management tools such as Azure Data Studio or sqlcmd alongside SSMS, and provide instructions for their use.
  • Explicitly note which steps can be performed from Linux/macOS and provide guidance for those platforms.
  • Reorder sections or add parallel instructions so that Linux-compatible approaches are presented alongside or before Windows-specific ones.
  • Indicate any limitations or differences for users on non-Windows platforms, and offer workarounds where possible.
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-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 exclusively uses PowerShell cmdlets (New-AzDataFactoryV2LinkedServiceEncryptedCredential, Set-AzDataFactoryV2LinkedService) and references DPAPI, a Windows-specific encryption technology. There are no examples or instructions for Linux or cross-platform alternatives, and prerequisites specifically require PowerShell 7.0+ without mentioning Linux compatibility or alternatives. The workflow and tooling described are Windows-centric, with no parity for Linux users.
Recommendations
  • Provide equivalent instructions and examples for Linux environments, including supported command-line tools or scripts.
  • Clarify whether the cmdlets and DPAPI-based encryption are supported on Linux, and if not, suggest alternative secure credential storage/encryption methods for Linux.
  • Explicitly mention platform requirements and limitations, and offer guidance for users running self-hosted integration runtime on Linux.
  • If PowerShell is cross-platform, demonstrate usage on Linux (e.g., with bash or Linux file paths), and note any differences in behavior or prerequisites.
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-10 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 by exclusively referencing Windows-centric tools such as SQL Server Management Studio (SSMS) and SQL Server Agent, and by providing step-by-step instructions for these tools without mentioning or providing alternatives for Linux users. There are no examples using Linux-native tools (e.g., Azure Data Studio on Linux, sqlcmd, or cross-platform scripting), nor is there guidance for users who may be managing SSISDB from non-Windows platforms.
Recommendations
  • Include instructions for connecting to SSISDB and configuring log clean-up properties using cross-platform tools such as Azure Data Studio, sqlcmd, or Azure CLI, which are available on Linux and macOS.
  • Provide examples of scheduling SSISDB log clean-up using cron jobs with sqlcmd or Azure CLI on Linux, as an alternative to SQL Server Agent and SSMS.
  • Mention and demonstrate how to perform equivalent operations (e.g., invoking stored procedures, monitoring jobs) from Linux or macOS environments.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and offer parity for Linux users wherever possible.
  • Add a section or note explicitly addressing Linux/macOS users, outlining supported workflows and tools for SSISDB management.
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-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 repeatedly references the PowerShell upgrade tool as the primary or sole migration method, with no mention of Linux-compatible alternatives (such as Bash scripts, Azure CLI, or cross-platform tools). There are no examples or guidance for users on Linux or macOS, and the migration workflow is described only in terms of PowerShell usage, which is traditionally Windows-centric.
Recommendations
  • Add instructions and examples for using Azure CLI or REST API for migration, which are cross-platform.
  • Explicitly mention whether the PowerShell upgrade tool can be used on Linux/macOS (via PowerShell Core), and provide installation/setup guidance for those platforms.
  • Include sample migration workflows or scripts for Bash or other Linux-native environments.
  • List alternative tools or approaches for users who do not have access to Windows or prefer non-PowerShell solutions.
  • Ensure parity in documentation by presenting Linux/macOS options alongside Windows/PowerShell, not only as an afterthought.
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-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 is heavily Windows-centric, with all examples, tools, and setup scripts referencing Windows commands, file formats, and utilities (e.g., .cmd, .bat, .exe, msiexec.exe, cmdkey, PowerShell). There is no mention of Linux equivalents, nor any guidance for users who might want to use Linux-based tooling or scripts. The express custom setup options and all sample scenarios are exclusively Windows-based, and PowerShell is the only CLI example provided.
Recommendations
  • Explicitly state that Azure-SSIS IR is Windows-only, if that is the case, to clarify the platform scope for users.
  • If Linux support is possible or planned, provide equivalent instructions, examples, and tooling for Linux environments (e.g., bash scripts, Linux utilities).
  • Where possible, mention cross-platform alternatives for tasks like credential management, environment variable setup, and component installation.
  • Add a section comparing Windows and Linux support for Azure-SSIS IR, including limitations and future roadmap.
  • If PowerShell is the only supported scripting language, clarify this early in the documentation and suggest alternatives for non-Windows users (such as Azure CLI, REST API, or other cross-platform tools).
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-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 Windows bias in several ways. The Azure PowerShell section is presented before the Azure CLI section, and PowerShell is described with explicit instructions for installation on Windows. File path examples use Windows-style paths (e.g., C:\ADFv2QuickStartPSH\), and there is no mention of Linux or macOS alternatives for PowerShell installation or file paths. The documentation does not provide Linux-specific instructions or examples, nor does it discuss cross-platform considerations for command-line usage or file system paths. The CLI section is more platform-neutral, but the overall ordering and example choices favor Windows users.
Recommendations
  • Add explicit instructions and examples for Linux and macOS users, including file path formats and PowerShell installation steps for those platforms.
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is more platform-agnostic.
  • Use platform-neutral file paths in code samples, or provide both Windows and Linux/macOS variants (e.g., C:\path vs. /home/user/path).
  • Mention cross-platform compatibility for tools and commands, and link to relevant installation guides for each OS.
  • Clarify that Azure PowerShell and CLI are available on multiple platforms, and provide guidance for non-Windows environments.
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-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 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, reinforcing a Windows-first approach. No Linux-specific guidance or parity is offered for provisioning or configuring the Azure-SSIS Integration Runtime.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and widely used on Linux.
  • Explicitly state platform compatibility for all tools and steps, and provide guidance for Linux/macOS users.
  • Reference authentication methods that work on non-Windows platforms, or clarify Windows-only requirements.
  • Where PowerShell is used, offer alternative scripts or commands for Bash/CLI environments.
  • Include notes or sections highlighting any limitations or differences for Linux users.
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-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 several signs of Windows bias. The Azure PowerShell section is prominent and includes explicit instructions for installing Azure PowerShell on Windows with PowerShellGet. The sample code for PowerShell assumes a Windows file path (C:\ADFv2QuickStartPSH\), and there are no equivalent instructions or examples for using PowerShell on Linux or macOS. The CLI section is present, but the PowerShell instructions are listed first and in greater detail. There are no examples showing Linux-specific tools, shell environments, or file path conventions, nor any mention of cross-platform considerations for PowerShell or CLI usage.
Recommendations
  • Add explicit instructions and examples for running Azure PowerShell on Linux and macOS, including installation steps and file path conventions.
  • Include sample file paths using Linux/macOS conventions (e.g., /home/user/ADFv2QuickStartPSH/MyTrigger.json) alongside Windows examples.
  • Clarify that Azure PowerShell and Azure CLI are cross-platform, and provide guidance for users on non-Windows systems.
  • Ensure that CLI and PowerShell examples are given equal prominence, and consider listing CLI examples first to avoid implicit Windows-first bias.
  • Mention alternative editors and environments (e.g., VS Code, nano, vim) for creating JSON files on Linux/macOS.
  • Add troubleshooting notes or tips for common issues encountered on Linux/macOS (e.g., file permissions, path separators).
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-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 demonstrates a bias toward Windows environments by providing only PowerShell commands for permission refresh, referencing Windows-specific tools, and omitting equivalent Linux or cross-platform instructions. No examples are given for Linux shells or CLI alternatives, and Windows-centric patterns (such as 'Open PowerShell as Administrator') are presented as the default approach.
Recommendations
  • Provide equivalent Linux/bash commands for permission refresh, such as using Azure CLI or REST API calls via curl.
  • Mention cross-platform tools (e.g., Azure CLI, REST API) before or alongside PowerShell, clarifying that PowerShell is available on Linux but not always preferred.
  • Add explicit instructions for Linux/macOS users, including how to install and use PowerShell Core if needed, or alternatives using native shell tools.
  • Where screenshots or steps reference Windows-only dialogs or tools, add notes or images for Linux/macOS environments.
  • Review all command-line examples to ensure parity and accessibility for non-Windows users.
GitHub Create Pull Request
Data Factory Run SSIS package with Stored Procedure Activity - Azure ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-stored-procedure-activity.md
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 demonstrates a strong Windows bias. All command-line examples use PowerShell, with explicit references to Windows file paths (e.g., C:\ADF\RunSSISPackage) and no mention of Linux-compatible alternatives (such as Bash, Azure CLI, or cross-platform scripting). The PowerShell section is extensive and presented as the only automation option, with no Linux or macOS guidance. Windows tools and patterns (PowerShell cmdlets, .json files in Windows folders) are referenced exclusively and before any Linux equivalents (which are absent).
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for Linux/macOS users.
  • Use cross-platform file paths in examples, or note how to adapt them for Linux/macOS (e.g., /home/user/ADF/RunSSISPackage).
  • Explicitly state that Azure Data Factory and SSIS can be managed from Linux/macOS, and link to relevant cross-platform tooling.
  • Add a section on running and monitoring pipelines using Azure CLI, including creation of linked services, pipelines, and triggers.
  • Where PowerShell is referenced, clarify that it is available on Linux/macOS, or offer alternatives for users who prefer native shell environments.
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-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 exhibits a strong Windows bias. All instructions and examples are tailored exclusively to Windows environments, referencing Windows-specific tools (Registry, environment variables, GAC, Windows file paths) and omitting any mention of Linux equivalents or cross-platform considerations. There are no examples or guidance for Linux users, and Windows patterns are presented as the default or only option.
Recommendations
  • Provide equivalent instructions for Linux environments, including how to set environment variables, manage file paths, and handle component installation.
  • Clarify whether Azure-SSIS IR and self-hosted IR support Linux nodes, and if not, explicitly state the platform limitations.
  • If Linux is supported, include examples for Linux shell commands, configuration files, and installation steps.
  • Mention cross-platform compatibility considerations for ISVs developing custom components.
  • Add a section comparing Windows and Linux setup processes, highlighting any differences or limitations.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, referencing Windows-specific tools (SSMS, dtexec, AzureDTExec.exe), installation paths, and administrative actions (Run as administrator, UAC prompts). All examples and configuration steps assume Windows, with no mention of Linux equivalents, cross-platform usage, or alternative tooling for non-Windows systems.
Recommendations
  • Clarify whether AzureDTExec is available or supported on Linux/macOS, and if not, state this explicitly.
  • If cross-platform support exists, provide installation and usage instructions for Linux/macOS, including example commands and file paths.
  • Mention any alternative tools or approaches for running SSIS packages in Azure from Linux/macOS environments.
  • Avoid assuming Windows-only administrative actions (e.g., UAC, Run as administrator) unless the tool is strictly Windows-only; otherwise, provide platform-specific guidance.
  • Include notes on how to access Azure Files, UNC paths, and other resources from Linux environments, if supported.
GitHub Create Pull Request
Data Factory Use the Execute SSIS Package activity from the portal ...ta-factory/how-to-invoke-ssis-package-ssis-activity.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. It exclusively references Windows authentication, UNC paths, Azure Files (with Windows-style paths), SQL Server Management Studio (SSMS), and SQL Server Data Tools (SSDT)—all Windows-centric tools and patterns. There are no Linux-specific examples, nor is there any mention of Linux-compatible alternatives for authentication, file access, or package management. The related content also highlights PowerShell, a Windows-first automation tool, without mention of Bash or cross-platform scripting. The documentation assumes a Windows environment for SSIS package development, deployment, and execution.
Recommendations
  • Add explicit notes about Linux support or limitations for Azure-SSIS IR and SSIS package execution.
  • Provide examples or guidance for accessing packages and configuration files from Linux-based systems, such as using SMB mounts or Azure CLI.
  • Mention cross-platform alternatives to SSMS and SSDT, such as Azure Data Studio or VS Code extensions, if available.
  • Include authentication options beyond Windows authentication, such as SQL authentication or managed identities, and clarify their applicability in non-Windows environments.
  • Offer PowerShell and Bash/CLI examples side-by-side for common automation tasks.
  • Clarify whether UNC paths and Azure Files can be accessed from Linux, and provide Linux-specific instructions if possible.
  • Highlight any limitations or requirements for running SSIS packages in Azure Data Factory from Linux-hosted environments.
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-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 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. There are no examples or guidance for Linux users, nor are Linux-compatible tools or command-line alternatives mentioned. Additionally, advanced troubleshooting references Windows-specific access (RDP, Windows Firewall), and PowerShell is mentioned as a means to configure certain settings, with no mention of Bash, CLI, or Linux-native workflows.
Recommendations
  • Include examples using Azure CLI and Bash scripts for provisioning and configuration steps, alongside or instead of PowerShell.
  • Mention cross-platform tools (e.g., Azure Data Studio) as alternatives to SSMS for managing SSIS workloads.
  • Provide guidance on how Linux users can schedule SSIS package executions, such as using Azure Automation or Logic Apps, instead of relying solely on SQL Agent jobs.
  • Clarify which steps are platform-agnostic and which require Windows-specific tooling, and offer Linux-friendly alternatives where possible.
  • Add troubleshooting steps that do not rely on RDP or Windows Firewall, or explain how Linux users can perform equivalent diagnostics.
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-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 scripting and automation examples use PowerShell, with no mention of Bash, Azure CLI, or Linux-native tools. Monitoring and automation sections exclusively use PowerShell and Windows-centric tools (e.g., SQL Server Management Studio), with no Linux alternatives provided. The documentation assumes familiarity with Windows patterns and tools, and does not offer parity for Linux users or cross-platform scripting approaches.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for starting, stopping, and monitoring Azure-SSIS IRs.
  • Include instructions for using cross-platform tools (e.g., Azure Portal, REST API via curl) that work on Linux and macOS.
  • Offer guidance on monitoring pipelines and triggers using Azure CLI or REST API, not just PowerShell.
  • Mention alternatives to SQL Server Management Studio, such as Azure Data Studio, which is cross-platform.
  • Clearly indicate which steps are platform-agnostic and which are Windows-specific, and add Linux/macOS alternatives where needed.
  • Add a section or callouts for Linux users, highlighting any differences or additional requirements.
GitHub Create Pull Request
Data Factory Create a self-hosted integration runtime ...des/data-factory-create-install-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 strong Windows bias. All command-line examples use PowerShell, which is native to Windows. The installation instructions and tool downloads are exclusively for Windows, referencing Windows-specific UI elements and installation steps (e.g., 'Add or Remove Programs', Windows setup wizards). There are no Linux or cross-platform instructions, nor any mention of Linux-compatible tools or CLI alternatives. The documentation assumes the user is operating on a Windows machine throughout.
Recommendations
  • Provide equivalent command-line examples using Bash or Azure CLI for Linux users.
  • Include installation instructions for Linux (and macOS if supported), specifying prerequisites and steps for those platforms.
  • Mention whether the self-hosted integration runtime is supported on Linux, and if not, clarify this limitation early in the documentation.
  • If the integration runtime is Windows-only, suggest alternative approaches for Linux environments or link to relevant resources.
  • Avoid Windows-specific terminology (e.g., 'Add or Remove Programs') or provide Linux/macOS equivalents where possible.
  • Add a platform support matrix or note at the top of the documentation to clarify OS compatibility.
GitHub Create Pull Request
← Previous Page 9 of 40 Next →