Data Factory

1123
Total Pages
968
Linux-Friendly Pages
155
Pages with Bias
13.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

319 issues found
Showing 1-25 of 319 flagged pages
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-12 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 Azure-SSIS Integration Runtime as running on Windows Server 2019 and lists only Windows-based components, drivers, and tools. There is no mention of Linux/macOS support, alternatives, or examples, and all built-in/preinstalled components are Windows-centric. This creates a strong Windows bias and may mislead or exclude Linux/macOS users.
Recommendations
  • Explicitly state that Azure-SSIS IR is Windows-only, and clarify lack of Linux/macOS support.
  • Add a section addressing cross-platform considerations, including alternatives for Linux/macOS users (e.g., Data Factory Mapping Data Flows, Azure DataBricks, or other ETL tools).
  • Provide guidance or links for users seeking Linux/macOS-compatible data integration solutions in Azure.
  • If partial Linux support exists (e.g., via containers or custom setups), document the limitations and setup steps.
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-12 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, Windows file paths) and providing instructions and examples that assume a Windows OS. There are no Linux/macOS equivalents or examples, and the installation and configuration steps rely on Windows-only mechanisms.
Recommendations
  • Add explicit statements clarifying OS support (e.g., whether Azure-SSIS IR or self-hosted IR can run on Linux/macOS).
  • If Linux/macOS support exists, provide equivalent instructions for those platforms (e.g., environment variable management, file paths, component installation, GAC alternatives).
  • If only Windows is supported, state this clearly at the top of the documentation to set user expectations.
  • Consider including cross-platform notes or links to relevant documentation for non-Windows users.
GitHub Create Pull Request
Data Factory Copy data from Azure Blob Storage to Azure SQL Database ...in/articles/data-factory/tutorial-copy-data-dot-net.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows environments, with all instructions and code samples based on Visual Studio, .NET, and Windows-specific tools. There are no Linux/macOS equivalents or alternative instructions, and Windows tools (Notepad, Visual Studio, SSMS) are referenced exclusively. This creates friction for Linux/macOS users, who cannot follow the tutorial as written without significant adaptation.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as using VS Code or JetBrains Rider for .NET development.
  • Include .NET CLI commands for project creation and NuGet package installation, which work cross-platform.
  • Mention alternative text editors (e.g., nano, vim) for creating input files.
  • Reference Azure Data Studio as a cross-platform alternative to SSMS for SQL Database verification.
  • Clarify that Azure Storage Explorer is available on Linux/macOS and provide installation instructions.
  • Add a note or section explicitly addressing Linux/macOS development environments and any required setup.
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-12 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 oriented toward Windows environments, with all examples and instructions relying on Windows-only tools (SSMS, dtutil, cmdkey, net use, batch scripting, T-SQL in SSMS). There are no Linux/macOS equivalents or alternatives mentioned, and the workflow assumes access to Windows-specific utilities and GUI applications. This creates significant friction for users on Linux or macOS, who cannot follow the documented procedures without a Windows system.
Recommendations
  • Provide instructions for managing SSIS packages using cross-platform tools or Azure portal where possible.
  • Document any available command-line or REST API alternatives for package management that work on Linux/macOS.
  • If dtutil or SSMS is required, clarify that these are Windows-only and suggest using a Windows VM or container as a workaround.
  • Include notes or links to any open-source or third-party tools that can help Linux/macOS users interact with Azure-SSIS IR.
  • Explicitly state platform requirements at the start of the documentation.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The troubleshooting steps for enabling ACS in SharePoint Online are exclusively presented using the SharePoint Online Management Shell, a Windows-only PowerShell tool. All example commands are PowerShell-based, and there is no mention of Linux/macOS alternatives or cross-platform approaches. The documentation assumes access to Windows tools and does not provide guidance for non-Windows environments.
Recommendations
  • Provide equivalent steps using cross-platform tools such as Azure CLI, Microsoft Graph API, or REST API calls that can be run on Linux/macOS.
  • Explicitly state platform requirements for the SharePoint Online Management Shell and suggest alternatives for Linux/macOS users.
  • Include example commands for Linux/macOS environments, or clarify if the task cannot be completed outside Windows.
  • Add a note about remote administration options (e.g., using a Windows VM or cloud shell) if no native Linux/macOS solution exists.
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-12 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, with all installation instructions, prerequisites, and examples assuming Windows OS. Only Windows versions are listed as supported, and all command-line and automation examples use PowerShell and Windows-specific tools (e.g., dmgcmd.exe, registry edits, .NET Framework, Windows DPAPI). There is no mention of Linux or macOS support, nor any alternative instructions or examples for non-Windows platforms. This bias makes the documentation inaccessible to users on Linux or macOS, who cannot follow the steps or complete the setup.
Recommendations
  • Explicitly state OS support: If only Windows is supported, clarify this at the top of the documentation. If Linux/macOS support is planned or available, provide equivalent instructions.
  • Add Linux/macOS parity: If the self-hosted integration runtime can run on Linux/macOS, include installation steps, prerequisites, and command-line examples for those platforms.
  • Provide cross-platform automation: Offer examples using Bash, Azure CLI, or other cross-platform tools, not just PowerShell.
  • Document limitations: If Linux/macOS are not supported, explain why and suggest alternatives for those users.
  • Avoid Windows-first language: Structure sections so that platform support is clear, and avoid implying Windows is the default or only option unless it truly is.
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-12 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 towards Windows environments, with all command-line examples provided in PowerShell and all database management steps requiring SQL Server Management Studio (SSMS), a Windows-only tool. There are no examples or guidance for Linux/macOS users (e.g., using Azure CLI, cross-platform SQL tools, or alternatives to SSMS). Windows tools and patterns are mentioned exclusively and appear before any cross-platform alternatives (which are not present).
Recommendations
  • Provide Azure CLI equivalents for PowerShell commands, especially for group and managed identity management.
  • Include instructions for using cross-platform SQL clients (such as Azure Data Studio, sqlcmd, or other database management tools) for T-SQL steps instead of only SSMS.
  • Add explicit notes or sections for Linux/macOS users, outlining supported workflows and tools.
  • Reorder examples to present cross-platform options first or alongside Windows-specific tools.
  • Clarify any limitations or differences for non-Windows environments.
GitHub Create Pull Request
Data Factory Encrypt credentials in Azure Data Factory ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/encrypt-credentials-self-hosted-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-12 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, which is a Windows-specific technology. All example commands are given in PowerShell, with no mention of Linux/macOS alternatives or cross-platform tools. Prerequisites specify PowerShell 7.0+, but do not clarify Linux/macOS support or provide bash/CLI examples. The documentation assumes a Windows environment for credential encryption and storage.
Recommendations
  • Clarify whether the cmdlets and DPAPI encryption are supported on Linux/macOS self-hosted integration runtime nodes.
  • If Linux/macOS are supported, provide equivalent examples using Azure CLI, bash, or other cross-platform tools.
  • Explicitly state platform limitations and provide guidance for Linux/macOS users if Windows is required.
  • If only Windows is supported, add a prominent note about platform requirements.
  • Consider referencing cross-platform credential storage/encryption patterns if available.
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-12 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 oriented toward Windows, both in its examples and tooling. All sample scripts, commands, and setup instructions reference Windows-specific tools (.cmd, .bat, .exe, .msi, PowerShell, Windows environment variables, Windows command-line utilities, and Windows-only drivers). There are no examples or guidance for Linux or macOS users, nor any mention of cross-platform alternatives. The express custom setup options and PowerShell instructions are Windows-centric, and all component installation samples assume a Windows environment.
Recommendations
  • Explicitly state that Azure-SSIS IR is a Windows-based runtime, if that is the case, and clarify platform limitations up front.
  • If any cross-platform or Linux/macOS options exist (for example, for scripting, automation, or component installation), provide equivalent examples and instructions.
  • Where possible, mention or link to Linux/macOS alternatives for Azure Storage management (e.g., azcopy, Azure CLI, REST API usage) instead of only Azure Storage Explorer.
  • For PowerShell instructions, provide Azure CLI or REST API equivalents for users on Linux/macOS.
  • Clarify whether custom setup scripts must be Windows batch files, or if other scripting languages (e.g., Python, Bash) are supported.
  • Add a section addressing Linux/macOS users, outlining what is and is not possible, and any workarounds.
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-12 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 Windows-centric, requiring SQL Server Management Studio (SSMS) for installation and configuration, which is only available on Windows. All examples use Windows paths and command-line conventions, with no mention of Linux or macOS alternatives. There is no guidance for running AzureDTExec or SSIS packages from non-Windows platforms, nor any discussion of cross-platform compatibility.
Recommendations
  • Explicitly state platform requirements and limitations at the top of the page.
  • Provide guidance or alternatives for Linux/macOS users, such as using Azure Data Factory web portal, REST APIs, or cross-platform tools.
  • If AzureDTExec is Windows-only, suggest equivalent workflows for non-Windows platforms.
  • Include examples using Linux/macOS command-line conventions where possible.
  • Clarify whether SSIS package execution in Azure can be managed without Windows-only tools.
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-12 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-specific instructions for installing and configuring the self-hosted integration runtime. All examples use PowerShell, and installation steps reference Windows-only tools and UI dialogs. There are no Linux/macOS command examples, nor any mention of cross-platform alternatives or parity.
Recommendations
  • Provide equivalent command-line examples for Linux/macOS environments (e.g., Azure CLI, Bash).
  • Clarify whether the integration runtime can be installed on Linux/macOS, and if not, explicitly state Windows-only support.
  • If Linux/macOS support exists, include installation and configuration steps for those platforms.
  • If only Windows is supported, add a prominent note at the beginning to inform non-Windows users.
  • Reference cross-platform tools or APIs where possible, rather than only Windows GUIs.
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-12 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-specific tools and workflows, such as the Runtime Configuration Manager UI and the dmgcmd.exe command-line utility, without mentioning Linux/macOS equivalents or providing cross-platform instructions. All screenshots and examples are Windows-centric, and there is no indication that the diagnostic tool is available or usable on non-Windows platforms.
Recommendations
  • Clarify platform support for the diagnostic tool (Windows, Linux, macOS).
  • If Linux/macOS are supported, provide equivalent installation and usage instructions, including command-line examples for those platforms.
  • Include screenshots or descriptions of the diagnostic tool on Linux/macOS, if applicable.
  • If the tool is Windows-only, explicitly state this limitation early in the documentation.
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-12 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 oriented towards Windows environments, with exclusive references to Windows tools (PowerShell, Local Security Policy, Visual Studio/SSDT), Windows authentication, and Windows file paths. There are no examples or instructions for Linux or macOS users, and all command-line and configuration guidance assumes a Windows OS. This creates significant friction for users wishing to deploy self-hosted IR on Linux or macOS, or those who prefer cross-platform tools.
Recommendations
  • Clearly state OS requirements and limitations at the beginning of the documentation.
  • If self-hosted IR is Windows-only, make this explicit and provide rationale.
  • If Linux/macOS support exists or is planned, add equivalent instructions for those platforms (e.g., bash scripts, Linux service management, alternative authentication methods).
  • Provide cross-platform alternatives for PowerShell commands, such as Azure CLI or REST API examples.
  • Clarify whether Visual Studio/SSDT is required for package design or if alternatives exist for non-Windows users.
  • Mention where logs are stored on non-Windows platforms, if supported.
  • Add a section summarizing platform support and any workarounds for Linux/macOS users.
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-12 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 Windows-centric: all examples and instructions assume a Windows environment, including PowerShell commands, Windows-specific file paths, and installation steps for the SAP .NET Connector (which is Windows-only). There are no Linux/macOS equivalents or guidance, making it difficult or impossible for non-Windows users to follow the setup.
Recommendations
  • Explicitly state that the self-hosted integration runtime and SAP .NET Connector require Windows, if true. If Linux/macOS are supported, provide equivalent instructions and examples for those platforms.
  • Offer alternative connectivity test commands for Linux/macOS (e.g., using nc or telnet instead of PowerShell).
  • Clarify file path and host file editing steps for Linux/macOS (e.g., /etc/hosts).
  • If the runtime is Windows-only, mention this limitation clearly at the beginning of the documentation.
  • If future support for Linux/macOS is planned, provide guidance or a roadmap.
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-12 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 towards Windows environments. All troubleshooting steps, examples, and tool references are Windows-centric, including usage of Windows Event Viewer, MMC, Registry Editor, Windows file paths, Windows services, and PowerShell commands. There are no Linux or macOS-specific instructions, examples, or tool alternatives provided, even though self-hosted integration runtime can be run on non-Windows platforms (e.g., via Docker). This bias makes it difficult or impossible for Linux/macOS users to follow the troubleshooting steps or resolve issues without significant additional research.
Recommendations
  • Add equivalent troubleshooting steps and examples for Linux (and macOS where applicable), such as using syslog/journalctl for logs, OpenSSL for certificate management, and Linux file paths.
  • Provide cross-platform commands for connectivity checks (e.g., curl, wget, openssl s_client) alongside PowerShell/Windows commands.
  • Document how to access and manage IR logs on Linux-based installations (including Docker containers).
  • Include instructions for managing service accounts, permissions, and certificates on Linux (e.g., using chown, chmod, keytool, etc.).
  • Clearly indicate which steps are Windows-only and provide alternatives or links for Linux/macOS users.
  • Reference Linux troubleshooting tools (e.g., strace, lsof, netstat, Wireshark) where appropriate.
  • Add a section or callouts for Docker-based deployments, which are common for Linux environments.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows environments, providing only PowerShell commands and using Windows-specific tools and terminology (MMC snap-in, certificate stores like 'Local Machine' and 'Personal', NT SERVICE accounts). There are no Linux/macOS equivalents or instructions, making it difficult for non-Windows users to follow or replicate the steps.
Recommendations
  • Add equivalent Linux/macOS instructions for obtaining FQDNs (e.g., using `hostname -f` or `dnsdomainname`).
  • Provide OpenSSL commands for generating and exporting certificates, including SANs, and explain how to install them on Linux/macOS systems.
  • Describe how to manage certificate permissions and stores on Linux/macOS (e.g., using `chown`, `chmod`, and system trust stores).
  • Clarify whether the integration runtime supports Linux/macOS nodes, and if so, provide platform-specific setup steps.
  • Include troubleshooting steps for Linux/macOS, such as verifying certificate installation and permissions.
GitHub Create Pull Request
Data Factory Transform data using Hive in Azure Virtual Network ...actory/tutorial-transform-data-hive-virtual-network.md
High Priority View Details →
Scanned: 2026-01-12 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 focused on Windows and PowerShell, with all command-line instructions provided exclusively in PowerShell. There are no examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI). Instructions for editing the hosts file reference only the Windows path. The self-hosted integration runtime registration steps assume use of a Windows VM, with no mention of Linux alternatives.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell commands.
  • Include instructions for editing the hosts file on Linux (e.g., /etc/hosts) alongside the Windows path.
  • Clarify whether the self-hosted integration runtime can be installed and registered on Linux VMs, and provide steps if supported.
  • Add notes or sections for macOS users where relevant.
  • Consider presenting cross-platform command examples side-by-side or in tabs.
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-12 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 exclusively for Windows. There are no instructions or examples for Linux or macOS users, nor any mention of cross-platform alternatives for the integration runtime or command-line tools. Windows-specific tools and patterns (e.g., SSMS, C:\ paths, PowerShell cmdlets) are used throughout, making it difficult for non-Windows users to follow the tutorial.
Recommendations
  • Provide equivalent instructions and examples for Linux/macOS users, including using Azure CLI or REST API for Data Factory operations.
  • Clarify whether the self-hosted integration runtime can be installed on Linux/macOS, and provide installation steps if supported.
  • Offer alternatives to Windows-only tools (e.g., suggest Azure Data Studio instead of SSMS, use platform-agnostic folder paths).
  • Explicitly state platform requirements and limitations at the beginning of the tutorial.
  • Where PowerShell is used, show how to perform the same steps with Azure CLI or other cross-platform tools.
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-11 06:20
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 a Windows OS, with explicit references to Windows versions, Windows-only tools (PowerShell, registry edits, Windows Firewall, NT SERVICE accounts), and Windows-specific configuration steps. There is no mention of Linux or macOS support, nor any examples or guidance for non-Windows platforms. The use of Windows Data Protection API (DPAPI) for credential encryption further cements the Windows-only approach. All automation and scripting examples use PowerShell, and the installer is distributed as a Windows MSI. The documentation does not clarify whether Linux/macOS are unsupported or simply omitted.
Recommendations
  • Explicitly state OS support: If self-hosted integration runtime is Windows-only, clarify this early in the documentation. If Linux/macOS support is planned or available, provide equivalent instructions.
  • Provide Linux/macOS installation guidance: If supported, add sections for installing and configuring on Linux/macOS, including prerequisites, service management, and credential storage.
  • Offer cross-platform automation examples: Include Bash/shell scripts and CLI instructions alongside PowerShell for automation.
  • Reference Linux/macOS equivalents for configuration: For steps involving Windows tools (e.g., registry edits, Windows Firewall), provide Linux/macOS alternatives or note their absence.
  • Clarify tool requirements: If only Windows tools are supported (e.g., dmgcmd.exe, Configuration Manager), state this and suggest alternatives or workarounds for other platforms.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias throughout. Troubleshooting steps, log collection, and configuration instructions almost exclusively reference Windows tools (Event Viewer, MMC, certutil, regedit, Control Panel, Windows service panel, etc.), and provide only Windows-specific examples (e.g., PowerShell commands, registry edits, folder paths). There is little to no mention of Linux or macOS equivalents, and no alternative instructions for users running self-hosted IR on non-Windows platforms. Even when Linux is referenced (e.g., TTL values), it is only as a network peer, not as a host for IR itself.
Recommendations
  • Explicitly state platform requirements for self-hosted IR (if Windows-only, clarify early; if Linux/macOS are supported, provide parity in troubleshooting steps).
  • For each troubleshooting step involving Windows tools (Event Viewer, MMC, certutil, regedit, Control Panel, etc.), add equivalent instructions for Linux (e.g., journalctl, openssl, systemd, file system paths) and macOS.
  • Provide Linux/macOS examples for log collection, certificate management, service management, and network troubleshooting (e.g., using system logs, openssl, systemctl, netstat, tcpdump, Wireshark).
  • Where PowerShell is used, offer Bash or shell script alternatives.
  • Clarify file paths and environment variables for Linux/macOS (e.g., /var/log, /etc/ssl/certs, JAVA_HOME).
  • If self-hosted IR is not supported on Linux/macOS, state this clearly at the start of the documentation.
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-11 06:20
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 oriented toward Windows environments, with exclusive references to Windows tools (Visual Studio, SSDT, SSMS), Windows authentication, and Windows file paths. All command-line examples use PowerShell, and there are no instructions or examples for Linux or macOS users. The installation steps, debugging, and configuration all assume a Windows OS, and there is no mention of Linux-compatible alternatives or parity.
Recommendations
  • Explicitly state OS requirements and limitations up front, clarifying that self-hosted IR and SSIS proxy features are Windows-only if true.
  • If Linux/macOS support exists or is planned, provide equivalent installation, configuration, and debugging instructions for those platforms.
  • Offer command-line examples using Bash or cross-platform tools where possible, or clarify that PowerShell examples are only for Windows.
  • Mention alternatives for non-Windows users, such as running self-hosted IR in a Windows VM on Linux/macOS hosts.
  • Add notes about the lack of support for Linux/macOS if applicable, to set user expectations.
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-11 06:20
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 oriented towards Windows environments, with all examples and tooling based on Windows-only utilities (SSMS, dtutil, cmdkey, net use, DOS batch scripting). There are no Linux/macOS equivalents or instructions, and all workflows assume access to Windows tools and patterns. This creates significant friction for users on non-Windows platforms.
Recommendations
  • Provide guidance for Linux/macOS users, including alternative tools or methods for package management (e.g., Azure CLI, REST API, or cross-platform SQL clients).
  • Document how to interact with Azure Files from Linux/macOS (e.g., using SMB mounts, azcopy, or other supported utilities).
  • Clarify whether dtutil or SSMS can be run in a container or via Wine, or suggest alternatives for non-Windows environments.
  • Add explicit notes about platform requirements and limitations, so non-Windows users are aware of what is and isn't supported.
  • Where possible, offer cross-platform scripts or workflows, or link to official Microsoft guidance for Linux/macOS users.
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-11 06:20
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 and .NET Framework as the underlying OS and runtime. All built-in/preinstalled components are Windows-based, with no mention of Linux/macOS alternatives or cross-platform support. The page assumes Windows as the default and does not provide guidance or parity for Linux/macOS users.
Recommendations
  • Explicitly state that Azure-SSIS IR is Windows-only and clarify platform limitations early in the documentation.
  • If any cross-platform or Linux/macOS support exists (e.g., via containers or alternative runtimes), provide clear guidance and examples.
  • For users seeking Linux/macOS solutions, suggest alternative Azure Data Factory runtimes or integration approaches.
  • Add a comparison table or section outlining platform support and limitations for SSIS IR versus other ADF runtimes.
  • Include links or references to documentation for Linux/macOS-compatible data integration tools.
GitHub Create Pull Request
Data Factory Copy and transform data to and from SQL Server ...lob/main/articles/data-factory/connector-sql-server.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: authentication options and examples prioritize Windows authentication, troubleshooting and configuration steps are exclusively described using Windows tools (SQL Server Management Studio, SQL Server Configuration Manager, Windows Firewall), and links to further configuration are Windows-centric. There are no Linux/macOS equivalents or instructions for connecting to SQL Server from non-Windows environments, nor are cross-platform tools (e.g., sqlcmd, Azure CLI, ODBC) mentioned. Linux users are left without guidance for critical setup and troubleshooting steps.
Recommendations
  • Add equivalent instructions and screenshots for configuring SQL Server remote access and network protocols using cross-platform tools (e.g., sqlcmd, Azure CLI, direct T-SQL commands).
  • Provide troubleshooting steps for Linux environments, such as configuring firewalls (iptables, ufw) and verifying connectivity using Linux-native tools.
  • Include examples of connecting to SQL Server from Linux/macOS clients, such as using sqlcmd, FreeTDS, or ODBC.
  • Mention authentication options relevant to Linux, such as Kerberos or SQL authentication, and clarify limitations of Windows authentication on non-Windows platforms.
  • Clearly indicate which steps are Windows-only and provide alternative guidance for other operating systems.
  • Reference official Microsoft documentation for SQL Server on Linux where appropriate.
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-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively recommends using the SharePoint Online Management Shell (a Windows-only PowerShell tool) for troubleshooting, with all example commands in PowerShell and no mention of Linux/macOS alternatives. There are no instructions for performing the same steps on non-Windows platforms, and Windows tooling is presented as the only option.
Recommendations
  • Provide equivalent instructions for Linux/macOS users, such as using cross-platform PowerShell Core or Microsoft Graph API via CLI or REST.
  • Mention whether the required actions (e.g., Set-SPOTenant) can be performed via browser-based admin portals or other cross-platform tools.
  • Clarify platform requirements and offer links to alternative tooling for non-Windows environments.
  • Include example commands for Linux/macOS environments where possible.
GitHub Create Pull Request
← Previous Page 1 of 13 Next →