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 1-25 of 1000 flagged pages
Data Factory Manage packages with Azure-SSIS Integration Runtime package store ...actory/azure-ssis-integration-runtime-package-store.md
High Priority View Details →
Scanned: 2026-01-14 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 is heavily biased towards Windows environments. All examples and instructions rely on Windows-only tools such as SQL Server Management Studio (SSMS), dtutil.exe, cmdkey, net use, and DOS batch scripting. There are no Linux or macOS equivalents or alternatives mentioned, nor is there guidance for users on those platforms. The documentation assumes the user is operating in a Windows environment throughout, making it difficult or impossible for Linux/macOS users to follow the procedures.
Recommendations
  • Provide guidance for managing SSIS packages from Linux/macOS environments, if supported, or explicitly state platform limitations.
  • Include cross-platform alternatives for dtutil (e.g., Docker containers, Azure CLI, REST APIs, or PowerShell Core on Linux/macOS if available).
  • Document any Azure portal or Data Factory web-based workflows that do not require Windows-only tools.
  • If SSMS is required, clarify that it is Windows-only and suggest remote desktop or cloud VM solutions for non-Windows users.
  • Reorder examples to mention platform requirements up front and avoid assuming Windows as the default.
  • Where possible, provide PowerShell Core or Azure CLI examples that work cross-platform.
GitHub Create Pull Request
Data Factory Built-in and preinstalled components on Azure-SSIS Integration Runtime ...lt-in-preinstalled-components-ssis-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is heavily Windows-centric, listing only Windows Server as the OS and exclusively referencing Windows-based components, drivers, and frameworks. There is no mention of Linux/macOS support, alternatives, or parity, and all tooling and examples are inherently Windows-specific.
Recommendations
  • Explicitly state that Azure-SSIS IR is Windows-only, if that is the case, to avoid confusion for Linux/macOS users.
  • If Linux/macOS support is possible or planned, provide a roadmap or guidance for those platforms.
  • Offer alternative Azure data integration runtimes or services that support Linux/macOS, and link to their documentation.
  • Add a comparison table or section outlining platform limitations and supported environments.
  • Where possible, mention cross-platform alternatives for data movement and transformation tasks.
GitHub Create Pull Request
Data Factory Troubleshoot the SharePoint Online list connector ...ctory/connector-troubleshoot-sharepoint-online-list.md
High Priority View Details →
Scanned: 2026-01-14 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 provides troubleshooting steps using the SharePoint Online Management Shell, a Windows-only PowerShell tool, with no mention of Linux/macOS alternatives or cross-platform approaches. All example commands are PowerShell-based, and there is no guidance for users on non-Windows systems.
Recommendations
  • Provide equivalent steps using cross-platform tools such as Azure CLI or PowerShell Core (pwsh), which are available on Linux/macOS.
  • Explicitly mention platform requirements and offer alternatives for Linux/macOS users.
  • Include example commands for Linux/macOS environments where possible.
  • Clarify whether the SharePoint Online Management Shell functionality can be replicated using REST APIs or other cross-platform methods.
GitHub Create Pull Request
Data Factory Create a self-hosted integration runtime ...data-factory/create-self-hosted-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-14 00:00
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 is heavily biased toward Windows environments. All installation instructions, prerequisites, and examples assume Windows OS (Windows 10/11/Server only), with no mention of Linux or macOS support or alternatives. All command-line and automation examples use PowerShell, and required tools (such as dmgcmd.exe, diahost.exe.config, and the MSI installer) are Windows-specific. The use of Windows DPAPI for credential encryption further cements the Windows-only approach. There are no Linux/macOS equivalents, nor any guidance for non-Windows users.
Recommendations
  • Explicitly state OS support: If self-hosted IR is Windows-only, clarify this early in the documentation. If Linux/macOS support is possible, provide installation instructions and examples for those platforms.
  • Provide Linux/macOS alternatives: If feasible, offer equivalent steps for Linux/macOS, including supported tools, configuration files, and automation scripts (e.g., Bash, systemd).
  • Include cross-platform CLI examples: Use Azure CLI or REST API examples in addition to PowerShell, and clarify which commands are OS-agnostic.
  • Document limitations: Clearly outline any features or steps that are unavailable on non-Windows platforms.
  • Mention platform requirements in prerequisites: State explicitly that only Windows is supported, and provide rationale if possible.
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-14 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 oriented toward Windows environments, with all command-line examples using PowerShell and Microsoft Entra PowerShell modules. SSMS (SQL Server Management Studio), a Windows-only tool, is required for critical steps. There are no Linux/macOS CLI alternatives, and Windows tools and patterns are mentioned exclusively and/or first.
Recommendations
  • Provide Azure CLI and/or Microsoft Graph API examples for group and managed identity operations, which are cross-platform.
  • Include instructions for using Azure Data Studio (cross-platform) instead of or in addition to SSMS for SQL queries.
  • Clarify which steps can be performed via the Azure portal, which is OS-agnostic.
  • Add notes or sections for Linux/macOS users, including any limitations or alternative workflows.
  • Reorder examples so that cross-platform methods (Azure CLI, portal) are presented before or alongside Windows-specific tools.
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-14 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 and references DPAPI, both of which are Windows-centric technologies. There are no examples or guidance for performing the same credential encryption tasks on Linux or macOS, nor is there mention of cross-platform alternatives. The prerequisites explicitly require PowerShell 7.0+, but do not clarify Linux/macOS support or provide parity instructions.
Recommendations
  • Clarify whether the cmdlets and DPAPI-based encryption are supported on Linux/macOS self-hosted integration runtime nodes.
  • If supported, provide explicit Linux/macOS examples, including command-line usage and any required dependencies.
  • If not supported, state the limitation clearly and suggest alternative approaches for Linux/macOS users.
  • Consider mentioning cross-platform credential management tools or patterns if available.
  • Reorder examples or add parallel Linux/macOS instructions to avoid Windows-first bias.
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-14 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 is heavily Windows-centric, with all examples, tools, and setup scripts based on Windows technologies (cmd, PowerShell, .exe, .msi). There is no mention of Linux or macOS equivalents, nor any guidance for users on those platforms. Windows commands and tools are referenced exclusively and repeatedly, and PowerShell is the only CLI method described.
Recommendations
  • Explicitly state that Azure-SSIS IR is Windows-only, if that is the case, to clarify expectations for Linux/macOS users.
  • If any cross-platform or Linux/macOS options exist (such as running setup scripts from a non-Windows machine, or using Azure CLI), provide examples and instructions.
  • Add a section addressing Linux/macOS users, outlining any limitations and possible workarounds (e.g., using a Windows VM or container for setup tasks).
  • Where possible, mention alternative tools (such as Azure CLI) and provide parity in instructions.
  • Clarify in prerequisites and introduction that all setup scripts and components must be compatible with Windows 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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily oriented toward Windows environments, referencing Windows-specific tools (Registry, environment variables, GAC), file paths, and setup patterns. There are no Linux/macOS equivalents or examples, and all instructions and code samples assume a Windows OS. This creates friction for users who may want to deploy or manage SSIS components in non-Windows environments.
Recommendations
  • Clarify that Azure-SSIS IR nodes are Windows-only, if true, or provide Linux/macOS instructions if supported.
  • Explicitly state OS requirements and limitations at the top of the documentation.
  • If Linux/macOS support is planned or possible, provide parallel instructions and examples for those platforms.
  • Where possible, abstract instructions away from Windows-specific tools (e.g., Registry, GAC) and offer alternatives.
  • Include notes or links for users who need to integrate with Linux/macOS environments, even if only for management or proxying.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. It assumes the use of SQL Server Management Studio (SSMS), a Windows-only tool, for installation and configuration of AzureDTExec. All examples use Windows paths and command prompts, with no mention of Linux/macOS equivalents or alternatives. There are no instructions or examples for running AzureDTExec on Linux or macOS, nor any guidance for users who do not have access to SSMS.
Recommendations
  • Clarify whether AzureDTExec is available or supported on Linux/macOS, and if not, explicitly state this limitation.
  • If AzureDTExec can be run on Linux/macOS (e.g., via .NET Core or Mono), provide installation and usage instructions for those platforms.
  • Offer command-line examples using Linux/macOS syntax (e.g., bash shell, forward slashes, environment variable setting).
  • Describe alternative configuration methods for users who cannot run SSMS (such as editing configuration files directly or using cross-platform tools).
  • Mention any cross-platform orchestration options or third-party tools that can be used in non-Windows environments.
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-14 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 exclusively provides PowerShell commands and Windows-centric installation instructions for creating and registering a self-hosted integration runtime. All examples, tool references, and screenshots are specific to Windows, with no mention of Linux/macOS equivalents or alternatives. The download link and installation steps are for a Windows installer, and there is no guidance for non-Windows platforms.
Recommendations
  • Provide equivalent CLI examples using Azure CLI or REST API that work on Linux/macOS.
  • Clarify platform requirements and explicitly state if the integration runtime is Windows-only, or provide alternatives for Linux/macOS.
  • If Linux/macOS support exists, include installation and registration instructions for those platforms.
  • If only Windows is supported, add a prominent note at the beginning to inform non-Windows users.
  • Consider providing Docker-based deployment options if available, which can run on Linux/macOS.
GitHub Create Pull Request
Data Factory Set up a self-hosted integration runtime for the SAP CDC connector ...ta-factory/sap-change-data-capture-shir-preparation.md
High Priority View Details →
Scanned: 2026-01-14 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 exhibits a strong Windows bias. All examples and instructions assume the use of Windows, such as PowerShell cmdlets for connectivity testing, references to the Windows hosts file path, and installation of the SAP .NET Connector (which is Windows-only). There are no Linux/macOS equivalents or instructions, making it difficult for non-Windows users to follow the setup process.
Recommendations
  • Provide Linux/macOS alternatives for connectivity testing (e.g., using nc or telnet instead of PowerShell).
  • Include instructions for editing the hosts file on Linux/macOS (e.g., /etc/hosts).
  • Clarify if the self-hosted integration runtime can be installed on Linux/macOS, and if not, state this explicitly.
  • If possible, suggest cross-platform tools or approaches for steps currently covered only with Windows tools.
  • Add a note about SAP .NET Connector's platform requirements and alternatives for non-Windows environments.
GitHub Create Pull Request
Data Factory Create an Azure Data Factory using REST API ...ata-factory/quickstart-create-data-factory-rest-api.md
High Priority View Details →
Scanned: 2026-01-14 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 for all REST API invocations and setup steps, with no mention of Linux/macOS alternatives such as Bash, curl, or Azure CLI. Azure PowerShell is required, and Windows-centric tools like Azure Storage Explorer are referenced without cross-platform context. No Linux or macOS command-line examples are provided, and Windows/PowerShell instructions are presented first and only.
Recommendations
  • Add equivalent Bash/curl examples for REST API calls, demonstrating how to authenticate and interact with Azure Data Factory from Linux/macOS.
  • Include Azure CLI commands for resource management and REST API invocation, which are cross-platform.
  • Clarify that Azure Storage Explorer is available for Windows, macOS, and Linux, or suggest alternatives like az storage commands.
  • Add a 'Platform notes' section explaining how Linux/macOS users can follow the tutorial using their native shells and tools.
  • Where PowerShell is used for authentication, provide guidance for obtaining tokens using Azure CLI or curl.
  • Present cross-platform examples side-by-side or indicate which commands work on all platforms.
GitHub Create Pull Request
Data Factory Self-hosted integration runtime diagnostic tool ...ory/self-hosted-integration-runtime-diagnostic-tool.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references Windows tools and workflows, such as the Runtime Configuration Manager and the dmgcmd.exe command, with no mention of Linux/macOS equivalents or support. All examples and screenshots are Windows-centric, and there is no guidance for users on other platforms.
Recommendations
  • Clarify whether the diagnostic tool is available for Linux/macOS or is Windows-only.
  • If Linux/macOS support exists, provide equivalent command-line examples and screenshots for those platforms.
  • If the tool is Windows-only, explicitly state this limitation early in the documentation.
  • Consider offering or documenting alternative troubleshooting steps for Linux/macOS users if the tool is unavailable.
GitHub Create Pull Request
Data Factory Configure a self-hosted integration runtime as a proxy for SSIS ...-factory/self-hosted-integration-runtime-proxy-ssis.md
High Priority View Details →
Scanned: 2026-01-14 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 assumes a Windows environment throughout, with exclusive references to Windows tools (PowerShell, Local Security Policy, NT SERVICE accounts, Visual Studio/SSDT, SSMS), Windows file paths, and no mention of Linux or macOS alternatives. All command-line examples are in PowerShell, and required software (self-hosted IR, drivers, SSDT) is Windows-only. There are no instructions or guidance for Linux/macOS users, nor any indication that cross-platform usage is supported or unsupported.
Recommendations
  • Explicitly state platform requirements and clarify if self-hosted IR and related tooling are Windows-only.
  • If Linux/macOS support is not available, add a prominent note at the top of the documentation.
  • If partial Linux/macOS support exists (e.g., for some drivers or components), provide equivalent setup and configuration instructions for those platforms.
  • Provide command-line examples using cross-platform tools (e.g., Azure CLI, REST API) where possible, or clarify that only PowerShell is supported.
  • Reference cross-platform alternatives to Visual Studio/SSDT if available, or clarify their absence.
  • Where Windows-specific steps are required (e.g., Local Security Policy), explain the rationale and possible workarounds for non-Windows users.
GitHub Create Pull Request
Data Factory Troubleshoot self-hosted integration runtime ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/self-hosted-integration-runtime-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-14 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 is heavily biased toward Windows environments. Troubleshooting steps, examples, and tool references are almost exclusively Windows-centric, with frequent mentions of Windows Event Viewer, Registry Editor, Control Panel, MMC, Windows Services, and PowerShell commands. There is little to no guidance for Linux or macOS users, and alternative tools or commands for those platforms are missing. Even in sections where Linux is mentioned (e.g., TTL analysis), the troubleshooting workflow and examples remain Windows-focused.
Recommendations
  • Add equivalent troubleshooting steps and examples for Linux/macOS environments, including log collection, certificate management, and service management.
  • Provide Linux/macOS commands (e.g., using systemctl, journalctl, openssl, and bash scripts) alongside Windows/PowerShell examples.
  • Reference cross-platform tools (e.g., Wireshark, OpenSSL, netstat, lsof) and clarify how to perform key actions on non-Windows systems.
  • Explicitly state platform requirements and limitations for self-hosted IR, and if Windows is required, make this clear early in the documentation.
  • Where possible, restructure examples so that Windows and Linux/macOS instructions are presented in parallel tabs or sections.
GitHub Create Pull Request
Data Factory Enable remote access from intranet with TLS/SSL certificate (Advanced) ...rial-enable-remote-access-intranet-tls-ssl-certificate.md
High Priority View Details →
Scanned: 2026-01-14 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 is heavily Windows-centric, providing only PowerShell commands and referencing Windows-specific certificate stores, MMC snap-in, and service accounts. There are no examples or instructions for Linux or macOS environments, and all tooling and UI references are for Windows. This creates significant friction for non-Windows users attempting to follow the tutorial.
Recommendations
  • Provide equivalent Linux/macOS instructions for obtaining FQDNs (e.g., using `hostname -f` or `dnsdomainname`).
  • Include certificate generation steps using OpenSSL, which is cross-platform.
  • Describe how to install certificates on Linux (e.g., using `update-ca-certificates` or placing them in `/etc/ssl/certs`).
  • Explain how to verify certificate installation and permissions on Linux/macOS.
  • Clarify whether the integration runtime supports Linux/macOS nodes, and if not, state this explicitly.
GitHub Create Pull Request
Data Factory Copy data from SQL Server to Blob storage using PowerShell ...ticles/data-factory/tutorial-hybrid-copy-powershell.md
High Priority View Details →
Scanned: 2026-01-14 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 is heavily biased towards Windows and PowerShell. All command-line examples use PowerShell, and the installation and usage of the self-hosted integration runtime is described only for Windows. There are no Linux/macOS equivalents or alternative instructions, and Windows tools (SQL Server Management Studio, Notepad, C:\ paths) are referenced exclusively and/or first.
Recommendations
  • Provide equivalent instructions and examples for Linux/macOS users, such as using Azure CLI or REST API instead of PowerShell.
  • Document how to install and run the self-hosted integration runtime on Linux (if supported), or clearly state Windows-only limitations.
  • Offer alternatives to Windows-specific tools (e.g., suggest Azure Data Studio or sqlcmd for SQL Server setup on non-Windows platforms).
  • Use platform-neutral file paths and editors in examples, or provide both Windows and Linux/macOS variants.
  • Clearly indicate any steps that are Windows-only and suggest workarounds or alternatives for other platforms.
GitHub Create Pull Request
Data Factory Built-in and preinstalled components on Azure-SSIS Integration Runtime ...lt-in-preinstalled-components-ssis-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exclusively describes components and runtime environments for Azure-SSIS Integration Runtime, which is based on Windows Server 2019 and .NET Framework. All listed built-in and preinstalled components are Windows-centric, with no mention of Linux or macOS equivalents, support, or examples. The documentation assumes a Windows environment and does not provide guidance or parity for Linux/macOS users.
Recommendations
  • Explicitly state that Azure-SSIS IR is Windows-only and clarify lack of Linux/macOS support.
  • If possible, provide information about alternatives for Linux/macOS users (e.g., Data Factory Mapping Data Flows, Azure DataBricks, or other ETL tools).
  • Add a comparison table or section outlining cross-platform options for data integration in Azure.
  • Include links to documentation for Linux/macOS-compatible Azure data integration services.
  • If future support for Linux/macOS is planned, note this and provide guidance for current workarounds.
GitHub Create Pull Request
Data Factory Configure a self-hosted integration runtime as a proxy for SSIS ...-factory/self-hosted-integration-runtime-proxy-ssis.md
High Priority View Details →
Scanned: 2026-01-13 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 oriented toward Windows environments, assuming the use of Windows-only tools (PowerShell, SSMS, Visual Studio/SSDT, Windows authentication, Windows file paths, and Windows services). There are no instructions or examples for Linux or macOS users, and the self-hosted IR is implicitly treated as a Windows-only component. This creates significant friction for non-Windows users.
Recommendations
  • Explicitly state the platform requirements for self-hosted IR (e.g., if it is Windows-only, clarify this early in the documentation).
  • If Linux/macOS support is available or planned, provide equivalent setup, configuration, and management instructions for those platforms.
  • Where PowerShell is used, offer CLI or REST API alternatives that are cross-platform.
  • Clarify whether tools like SSMS, Visual Studio/SSDT, and Microsoft Integration Runtime Configuration Manager are required, and if so, suggest alternatives or workarounds for non-Windows users.
  • For file paths and log locations, note the platform-specific defaults or equivalents.
  • Provide a summary table of supported platforms and any limitations for Linux/macOS users.
GitHub Create Pull Request
Data Factory Manage packages with Azure-SSIS Integration Runtime package store ...actory/azure-ssis-integration-runtime-package-store.md
High Priority View Details →
Scanned: 2026-01-13 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 is heavily biased towards Windows environments. All examples and workflows rely on Windows-only tools such as SQL Server Management Studio (SSMS), dtutil, cmdkey, and net use. There are no instructions or examples for Linux or macOS users, nor any mention of cross-platform alternatives. The documentation assumes the user is running Windows and has access to Windows-specific utilities and GUIs.
Recommendations
  • Provide instructions for managing SSIS packages using Azure Data Factory portal or REST APIs, which are accessible from any OS.
  • Include examples for connecting to Azure Files from Linux/macOS (e.g., using smbclient, mount.cifs, or Azure CLI).
  • Document how to run dtutil or equivalent operations in a containerized or cloud-hosted environment, or provide PowerShell Core/CLI alternatives that work cross-platform.
  • Clarify which steps are Windows-only and suggest Linux/macOS workarounds or alternatives where possible.
  • Mention that SSMS is Windows-only and suggest Azure Data Studio or other cross-platform tools if applicable.
GitHub Create Pull Request
Data Factory Troubleshoot the SharePoint Online list connector ...ctory/connector-troubleshoot-sharepoint-online-list.md
High Priority View Details →
Scanned: 2026-01-13 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 provides troubleshooting steps using the SharePoint Online Management Shell, a Windows-only PowerShell tool. All example commands are PowerShell-based, with no mention of Linux/macOS alternatives or cross-platform approaches. This creates friction for non-Windows users attempting to follow the guidance.
Recommendations
  • Provide equivalent steps using cross-platform tools such as Azure CLI, Microsoft Graph API, or PowerShell Core (if supported on Linux/macOS).
  • Explicitly state platform requirements for the SharePoint Online Management Shell, and offer alternatives for Linux/macOS users.
  • Add Linux/macOS-specific instructions or note any limitations for those platforms.
  • Consider referencing web-based admin portals or REST API methods where possible.
GitHub Create Pull Request
Data Factory Create a self-hosted integration runtime ...data-factory/create-self-hosted-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-13 00:00
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. Only Windows OS versions are listed as supported, and all command-line automation is shown using PowerShell and Windows-specific tools (e.g., dmgcmd.exe, registry edits, .NET Framework requirements, Windows DPAPI encryption). There are no instructions, examples, or mentions of Linux or macOS support, nor any cross-platform alternatives. This creates a significant barrier for users on non-Windows platforms.
Recommendations
  • Explicitly state platform support: If self-hosted IR is Windows-only, clarify this early in the documentation. If Linux/macOS support is planned or possible, provide equivalent instructions.
  • Add Linux/macOS sections: If supported, include installation, configuration, and automation steps for Linux/macOS, using appropriate tools (e.g., Bash, systemd, OpenSSL for encryption).
  • Provide cross-platform automation examples: Offer CLI examples using Azure CLI, REST API, or other platform-neutral tools.
  • Mention limitations: If certain features (e.g., DPAPI encryption, registry edits) are Windows-specific, note what Linux/macOS users should do instead.
  • List prerequisites for all platforms: Include OS requirements for Linux/macOS if supported, or state that only Windows is supported.
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-13 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/macOS users, nor mention of cross-platform alternatives. Prerequisites specify PowerShell 7+, but do not clarify Linux support or provide Linux-specific guidance.
Recommendations
  • Explicitly state whether the cmdlets and DPAPI encryption are supported on Linux/macOS self-hosted integration runtime nodes.
  • If Linux/macOS support exists, provide equivalent command-line examples (e.g., PowerShell Core on Linux, Azure CLI, or REST API usage).
  • If Windows-only, clearly indicate this limitation and suggest alternatives or workarounds for Linux/macOS users.
  • Mention any differences in credential encryption/storage mechanisms for non-Windows platforms.
  • Reorder or supplement examples so Linux/macOS usage is shown alongside or before Windows examples.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation is heavily Windows-centric, referencing Windows environment variables, Windows Registry keys, Windows file paths, and Windows-only installation patterns (such as use of .exe installers and GAC). There are no Linux or macOS examples, nor any mention of how to perform equivalent tasks on non-Windows platforms. All instructions and code samples assume a Windows environment, making it difficult or impossible for Linux/macOS users to follow the guidance.
Recommendations
  • Clarify whether Azure-SSIS IR and self-hosted IR support Linux/macOS nodes, and if not, state this explicitly.
  • If Linux/macOS support is possible, provide equivalent instructions for environment variable access, file paths, and installation steps.
  • Offer examples using cross-platform tools (e.g., bash scripts, .NET Core) where possible.
  • Document any limitations or workarounds for non-Windows users.
  • Include a note at the beginning of the article about platform requirements and parity.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation is heavily biased towards Windows environments. It assumes the use of SQL Server Management Studio (SSMS), a Windows-only tool, for installation and configuration of AzureDTExec. All examples and instructions reference Windows paths, Windows administrative actions, and Windows-specific concepts (e.g., UNC paths, Run as administrator, User Account Control). There are no instructions or examples for Linux or macOS users, nor any mention of cross-platform alternatives.
Recommendations
  • Clarify whether AzureDTExec is available or supported on Linux/macOS. If not, explicitly state this limitation.
  • If AzureDTExec is Windows-only, suggest alternative approaches for Linux/macOS users to run SSIS packages in Azure Data Factory (e.g., REST API, Azure Data Factory UI, or other command-line tools).
  • If cross-platform support exists or is planned, provide installation, configuration, and usage instructions for Linux/macOS environments.
  • Include examples using Linux/macOS file paths and shell commands where applicable.
  • Avoid Windows-specific terminology (e.g., Run as administrator, UAC) or provide equivalent steps for other platforms.
GitHub Create Pull Request
← Previous Page 1 of 40 Next →