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 26-50 of 1000 flagged pages
Data Factory Create a self-hosted integration runtime ...des/data-factory-create-install-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 is heavily biased toward Windows environments. All command-line examples use PowerShell, and installation instructions are exclusively for Windows, referencing Windows-specific tools (e.g., 'Add or Remove Programs') and a Windows-only installer. There are no instructions or examples for Linux or macOS users, nor any mention of cross-platform alternatives.
Recommendations
  • Provide equivalent command-line instructions for Linux/macOS using Azure CLI or REST API.
  • Clarify whether the self-hosted integration runtime can be installed on Linux/macOS, and if so, provide installation steps for those platforms.
  • If the integration runtime is Windows-only, explicitly state this limitation at the beginning of the documentation.
  • Include troubleshooting and configuration guidance for non-Windows environments, if supported.
  • Offer parity in example order (e.g., show Linux/macOS steps alongside or before Windows steps where possible).
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-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 biased towards Windows environments. All examples and instructions (e.g., PowerShell cmdlets, editing C:\Windows\System32\drivers\etc\hosts, installing the SAP .NET Connector) are Windows-specific. There are no Linux or macOS equivalents provided for connectivity testing, host file editing, or runtime installation, making it difficult for non-Windows users to follow the guide.
Recommendations
  • Provide Linux/macOS equivalents for connectivity testing, such as using 'nc' or 'telnet' instead of PowerShell.
  • Include instructions for editing the hosts file on Linux/macOS (typically /etc/hosts).
  • Clarify whether the self-hosted integration runtime can be installed on Linux/macOS, and if so, provide installation steps.
  • If the SAP .NET Connector is Windows-only, explicitly state this limitation; if alternatives exist for Linux, mention them.
  • Present examples for both platforms, or clearly indicate platform requirements at the beginning of the documentation.
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-13 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 is heavily biased towards Windows and PowerShell. All command-line examples use Azure PowerShell cmdlets, with no mention or examples of equivalent Bash, Azure CLI, or curl commands that would be more natural for Linux/macOS users. The only tool recommended for interacting with Azure Blob Storage is Azure Storage Explorer, which is a GUI tool but is most commonly used on Windows. There is no guidance for Linux/macOS users on how to perform the same REST API operations, authenticate, or manage resources using cross-platform tools.
Recommendations
  • Provide equivalent examples using Azure CLI, curl, or Bash scripts for all REST API operations, alongside PowerShell.
  • Explicitly mention that Azure CLI and REST API calls can be performed on Linux/macOS, and provide setup instructions.
  • Offer authentication instructions using Azure CLI (az login, az account set, etc.) and how to obtain access tokens with CLI or curl.
  • Recommend cross-platform tools for interacting with Azure Blob Storage, such as azcopy or CLI commands, not just Azure Storage Explorer.
  • Reorder examples so that cross-platform (CLI/curl) options are shown first or side-by-side with PowerShell.
  • Add notes or sections for Linux/macOS users, highlighting any differences or requirements.
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-13 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 tool, without mentioning Linux or macOS equivalents or providing cross-platform instructions. There are no examples or guidance for running diagnostics on non-Windows systems, and Windows terminology and screenshots are used throughout.
Recommendations
  • Explicitly state platform support (Windows, Linux, macOS) for the diagnostic tool.
  • If Linux/macOS are supported, provide equivalent command-line instructions and tool names for those platforms.
  • Include screenshots or UI descriptions for Linux/macOS if applicable.
  • If only Windows is supported, clarify this early in the documentation to set expectations for non-Windows users.
  • Consider developing and documenting Linux/macOS versions of the diagnostic tool if not currently available.
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-13 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 troubleshooting steps, examples, and tool references almost exclusively for Windows environments. Windows tools (Event Viewer, MMC, certutil, Process Monitor, Registry Editor, Control Panel, Windows Installer, PowerShell) are mentioned throughout, and all example commands and screenshots are Windows-based. There is no guidance for Linux or macOS users, nor any mention of equivalent tools or procedures for those platforms. Even where Linux is referenced (TTL values), it's only as an external system, not as a supported platform for running self-hosted IR.
Recommendations
  • Explicitly state platform support for self-hosted IR (Windows-only or cross-platform).
  • If Linux/macOS are supported, provide equivalent troubleshooting steps, tool references, and example commands for those platforms (e.g., using journalctl/syslog, openssl, systemd, Linux file paths, etc.).
  • Add notes or sections for Linux/macOS users, or clarify that the product is Windows-only if that is the case.
  • Where PowerShell or Windows-specific tools are used, offer alternatives (e.g., Bash, Linux CLI tools) or explain how to achieve similar results on other platforms.
  • Include screenshots and examples for non-Windows environments if supported.
GitHub Create Pull Request
Data Factory Branching in Azure Data Factory pipeline ...ob/main/articles/data-factory/tutorial-control-flow.md
High Priority View Details →
Scanned: 2026-01-13 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 users, with all code samples and setup instructions based on Visual Studio (Windows-only), .NET Framework, and PowerShell/NuGet commands. There are no examples or guidance for Linux/macOS users, such as using .NET Core/SDK, VS Code, or CLI alternatives. Windows tools like Azure Storage Explorer and Visual Studio are mentioned exclusively, and Linux equivalents or cross-platform alternatives are not provided.
Recommendations
  • Provide instructions for setting up the development environment on Linux/macOS, including using .NET Core/SDK and VS Code.
  • Include CLI-based package installation commands (e.g., 'dotnet add package') alongside NuGet/PowerShell examples.
  • Mention and provide examples for using cross-platform editors (VS Code, JetBrains Rider) instead of only Visual Studio.
  • Clarify that Azure Storage Explorer is cross-platform, and provide installation instructions for Linux/macOS.
  • Add sample code and workflow for running the tutorial on Linux/macOS, including any required changes to project files or dependencies.
  • Explicitly state platform requirements and alternatives at the start of the tutorial.
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-13 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 oriented toward Windows users, with all examples and instructions based on Visual Studio, Notepad, and PowerShell/NuGet Package Manager Console. There are no Linux/macOS equivalents or alternative instructions for cross-platform development environments. The use of Windows-specific tools and patterns is pervasive throughout the tutorial, making it difficult for Linux/macOS users to follow or replicate the steps without significant adaptation.
Recommendations
  • Provide instructions for setting up the development environment on Linux/macOS, such as using VS Code or JetBrains Rider instead of Visual Studio.
  • Include .NET CLI commands for package installation (e.g., 'dotnet add package ...') alongside NuGet Package Manager Console commands.
  • Offer guidance for creating and editing files using cross-platform editors (e.g., nano, vim, VS Code) instead of Notepad.
  • Mention and provide examples for uploading blobs using Azure CLI or azcopy, which are available on Linux/macOS.
  • Clarify that the .NET SDK and Azure Data Factory APIs can be used on Linux/macOS, and link to relevant cross-platform setup guides.
  • Add notes or sections for Linux/macOS users, highlighting any differences or additional steps required.
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-13 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 environments. All command-line examples use PowerShell, certificate management instructions reference Windows-specific stores and MMC snap-in, and screenshots show Windows UI. There are no instructions or examples for Linux or macOS users, making it difficult or impossible for them to follow the tutorial.
Recommendations
  • Provide equivalent Linux/macOS instructions for obtaining FQDNs (e.g., using `hostname -f`).
  • Include OpenSSL commands for generating and exporting certificates with SANs.
  • Describe how to install certificates on Linux (e.g., using `update-ca-certificates` or placing 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-13 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 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 instructions or examples for Linux or macOS users, and Windows-specific tools and file paths are referenced throughout. This creates significant friction for non-Windows users, who cannot follow the tutorial as written.
Recommendations
  • Provide equivalent instructions and examples for Linux and macOS, including command-line steps using Azure CLI or REST API.
  • Clarify platform requirements for the self-hosted integration runtime and, if possible, provide alternatives or note Linux support status.
  • Include cross-platform file path examples and avoid hardcoding Windows paths (e.g., C:\ADFv2Tutorial).
  • Explicitly state any platform limitations early in the prerequisites section.
  • If PowerShell is required, mention how to install and use PowerShell Core on Linux/macOS, or offer Azure CLI alternatives.
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-13 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, with all command-line instructions using Azure PowerShell and references to Windows-specific tools and paths (e.g., editing C:\Windows\System32\drivers\etc\hosts). There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or Linux file paths. The instructions for registering the self-hosted integration runtime and editing the hosts file are Windows-centric, and Linux alternatives are not mentioned.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell commands.
  • Include instructions for editing the hosts file on Linux/macOS (e.g., /etc/hosts) when DNS is not available.
  • Clarify that the self-hosted integration runtime can be installed on Linux and provide steps for Linux installation and registration.
  • Indicate cross-platform compatibility for JSON authoring and deployment steps.
  • Explicitly mention any platform limitations or requirements for the self-hosted integration runtime and Data Factory pipeline tasks.
GitHub Create Pull Request
Data Factory Choose the right integration runtime configuration for your scenario ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/choose-the-right-integration-runtime-configuration.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments. References to self-hosted integration runtime installation and management are made in the context of customer-managed machines, but examples and linked articles (e.g., sharing self-hosted integration runtime) specifically mention PowerShell, a Windows-centric tool. There is no mention of Linux-specific installation, management, or troubleshooting procedures, nor are Linux tools or patterns (such as bash scripts or systemd services) referenced. The diagnostic and monitoring recommendations focus on Azure Monitor and Azure Log Analytics, which are platform-agnostic, but the lack of Linux parity in operational examples and tooling is notable.
Recommendations
  • Include explicit instructions and examples for installing and managing self-hosted integration runtime on Linux machines, including supported distributions.
  • Provide Linux-specific troubleshooting and diagnostic procedures, referencing tools such as bash, systemd, or relevant Linux logs.
  • Offer parity in automation examples, e.g., bash scripts or CLI commands alongside PowerShell for sharing and configuring self-hosted integration runtimes.
  • Clarify platform support in all referenced articles, ensuring that Linux users know which features and tools are available to them.
  • Add links to Linux-focused documentation or tutorials where available, and ensure that all operational guidance is cross-platform.
GitHub Create Pull Request
Data Factory Copy and transform data from Microsoft 365 (Office 365) ...lob/main/articles/data-factory/connector-office-365.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several ways: PowerShell is referenced for certificate conversion, and Windows-centric tools and patterns (e.g., Azure PowerShell, Windows-style certificate management) are mentioned without Linux equivalents. The order of tooling examples places Azure PowerShell before REST API and ARM templates, and there are no Linux-specific instructions or examples for certificate management, integration runtime setup, or SDK usage. No bash, Linux CLI, or cross-platform alternatives are provided for key steps like certificate conversion or pipeline creation.
Recommendations
  • Add Linux and macOS equivalents for certificate conversion (e.g., using OpenSSL and bash commands) alongside PowerShell instructions.
  • Include Azure CLI examples for pipeline creation and management, and reference them before or alongside Azure PowerShell.
  • Provide cross-platform guidance for saving secrets in Azure Key Vault (e.g., using Azure CLI or REST API).
  • Ensure all SDK and tool examples (Python, .NET, REST, ARM) are presented before or alongside Windows-specific tools.
  • Explicitly mention that all steps can be performed on Linux and macOS, and link to relevant cross-platform documentation.
  • Add sample scripts and screenshots for Linux environments where UI or command-line steps are shown.
GitHub Create Pull Request
Data Factory Troubleshoot the REST connector ...n/articles/data-factory/connector-troubleshoot-rest.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias by referencing 'Command Prompt' as the environment for running curl, omitting mention of Linux/macOS terminals. It recommends Fiddler, a Windows-only tool, without suggesting Linux alternatives. No Linux-specific troubleshooting examples or tool recommendations are provided.
Recommendations
  • Explicitly mention that curl commands can be run in Linux/macOS terminals as well as Windows Command Prompt.
  • Provide example curl usage for Linux/macOS, including common shell syntax.
  • Recommend cross-platform alternatives to Fiddler, such as mitmproxy or Wireshark, for SSL troubleshooting.
  • Add troubleshooting steps or notes relevant to Linux environments, such as checking permissions or using Linux-native diagnostic tools.
GitHub Create Pull Request
Data Factory Web Activity ...ain/articles/data-factory/control-flow-web-activity.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias primarily in the authentication section, where only a PowerShell snippet is provided for base64-encoding a PFX certificate file, with no equivalent Linux or cross-platform example. The mention of 'your favorite utility' for PFX conversion is vague and does not offer parity for Linux users. No Linux-specific tools or commands (e.g., OpenSSL) are referenced, and the only concrete example uses PowerShell, a Windows-centric tool.
Recommendations
  • Add Linux and cross-platform examples for base64-encoding PFX files, such as using OpenSSL and base64 commands.
  • Explicitly mention Linux tools (e.g., OpenSSL) for PFX conversion and encoding, with sample commands.
  • Provide guidance for both Windows and Linux users in all code snippets and tool recommendations.
  • Where PowerShell is referenced, offer an alternative using Bash or other common Linux shells.
GitHub Create Pull Request
Data Factory Deploy SSIS packages ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-deploy-packages.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and running SSIS packages. There are no examples or mentions of Linux-compatible tools or workflows, nor any guidance for users on non-Windows platforms. Windows authentication and PowerShell are referenced in related content, further reinforcing the Windows-first approach.
Recommendations
  • Provide equivalent Linux-compatible instructions or clarify platform limitations for SSIS deployment and execution.
  • Mention whether tools like dtutil and AzureDTExec are available or supported on Linux, and suggest alternatives if not.
  • Include examples using cross-platform tools (e.g., Azure CLI, REST API) for provisioning and managing Azure-SSIS IR.
  • Add notes or sections explicitly addressing Linux/macOS users, including any required workarounds or platform-specific guidance.
  • Balance references to PowerShell with Azure CLI or other cross-platform automation options.
GitHub Create Pull Request
Data Factory Switch activity in Azure Data Factory .../articles/data-factory/control-flow-switch-activity.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell commands for pipeline deployment and execution, referencing Windows file paths (e.g., C:\ADF), and omitting equivalent instructions for Linux/macOS environments. No Bash, Azure CLI, or cross-platform guidance is offered, and Windows-centric tooling is assumed throughout.
Recommendations
  • Add equivalent Azure CLI and Bash examples for pipeline deployment and execution, suitable for Linux/macOS users.
  • Use cross-platform file path conventions in examples (e.g., /home/user/ADF or relative paths) or clarify path differences.
  • Explicitly mention that PowerShell commands can be run on Linux/macOS via PowerShell Core, or provide alternative instructions.
  • Include a section comparing PowerShell and Azure CLI usage for Data Factory, highlighting platform compatibility.
  • Review and update tutorials and quickstarts to ensure Linux parity and avoid assuming a Windows environment by default.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell, which is native to Windows. The installation instructions and tooling are exclusively for Windows, referencing 'Add or Remove Programs' and providing a Windows-only download link. There are no Linux or cross-platform alternatives mentioned for installing or managing the integration runtime, nor are there CLI or script examples for Linux environments. The documentation assumes the user is operating on a Windows machine throughout.
Recommendations
  • Provide equivalent command-line examples using Azure CLI or REST API, which are cross-platform.
  • Include installation instructions for Linux environments, if supported, or explicitly state platform limitations.
  • Mention and link to any Linux-compatible integration runtime installers or container images, if available.
  • Clarify platform requirements early in the documentation to set user expectations.
  • If PowerShell is required, note that PowerShell Core is available on Linux and provide installation guidance.
  • Offer troubleshooting and configuration steps for Linux environments, including common patterns for service management and connectivity testing.
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-11 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 page exhibits a strong Windows bias. It exclusively references Windows authentication, Windows file paths (UNC), Windows-specific tools (SSDT, SSMS), and Windows-centric configuration patterns. There are no examples or guidance for Linux environments, nor any mention of Linux-compatible alternatives for authentication, file access, or package management. The related content also points to PowerShell usage, further reinforcing the Windows-centric approach.
Recommendations
  • Add explicit statements about Azure-SSIS IR support for Linux, if any, or clarify Windows-only requirements.
  • Provide examples of accessing packages and configuration files from Linux-based storage or using Linux-compatible authentication methods.
  • Include guidance for users who may be running Data Factory pipelines from Linux environments, such as using SMB/CIFS mounts, or alternatives to UNC paths.
  • Mention cross-platform tools for SSIS package creation and management, or clarify the limitations of SSDT/SSMS on non-Windows platforms.
  • Balance references to PowerShell with examples using Bash, Azure CLI, or other cross-platform scripting environments.
  • Clearly state any platform restrictions or prerequisites (e.g., 'Windows-only features') at the beginning of the documentation.
GitHub Create Pull Request
Data Factory Review deployed resources ...ludes/data-factory-quickstart-verify-output-cleanup.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell commands for resource cleanup, which are primarily used on Windows. There are no equivalent examples for Linux users, such as Azure CLI or Bash commands. The documentation implicitly assumes a Windows environment and does not mention cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for resource group and data factory deletion, which work on Linux, macOS, and Windows.
  • Explicitly mention that PowerShell commands are for Windows and provide Bash/CLI alternatives for Linux/macOS users.
  • Include a note or section on cross-platform command usage to improve accessibility for non-Windows 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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for Windows environments. It references Windows-specific tools (PowerShell, GAC, Windows hosts file path), omits Linux equivalents, and does not mention Linux support or alternatives for key steps such as connectivity testing, SAP .NET Connector installation, and hosts file editing.
Recommendations
  • Add Linux-specific instructions and examples for each step, including installation paths, commands, and tools.
  • Provide a Linux alternative for testing connectivity (e.g., using 'nc' or 'telnet' instead of PowerShell).
  • Clarify whether the SAP .NET Connector and the self-hosted integration runtime support Linux, and if so, provide installation steps.
  • Include hosts file editing instructions for Linux (e.g., '/etc/hosts').
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
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 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 exhibits a strong Windows bias. Troubleshooting steps, log collection, and configuration instructions almost exclusively reference Windows tools (Event Viewer, MMC, Registry Editor, Windows folders, Windows services, Control Panel, etc.), and provide PowerShell and Command Prompt examples. There is little to no mention of Linux equivalents or guidance for users running self-hosted IR on Linux systems. In several sections, Windows methods are presented as the only or default approach, and Linux troubleshooting is only referenced indirectly (e.g., TTL values in network traces).
Recommendations
  • Add explicit troubleshooting instructions for self-hosted IR running on Linux, including log collection, service management, and certificate handling.
  • Provide Linux equivalents for all Windows tool references (e.g., Event Viewer → journalctl/syslog, Registry Editor → config files/environment variables, MMC → certtool/openSSL, Control Panel → systemctl/service commands).
  • Include bash/shell script examples alongside PowerShell/Command Prompt commands for connectivity checks, file operations, and service management.
  • Clarify which steps are Windows-specific and which are applicable to Linux, and reorganize sections to present both platforms equally.
  • Reference Linux file paths and service names where appropriate (e.g., /var/log/, systemd services, etc.).
  • Add guidance for installing dependencies (e.g., JRE, .NET) on Linux, including package manager commands.
  • Ensure screenshots and UI references are supplemented with CLI or text-based alternatives for Linux environments.
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-11 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 use of 'dmgcmd.exe' and the Configuration Manager UI, with no mention of Linux equivalents or support. There are no Linux command-line examples or references to Linux compatibility, suggesting the tool is either Windows-only or the documentation is biased toward Windows environments.
Recommendations
  • Explicitly state whether the diagnostic tool is Windows-only or if Linux is supported.
  • If Linux is supported, provide equivalent Linux command-line examples (e.g., using ./dmgcmd or a shell script).
  • Mention Linux installation and troubleshooting steps if applicable.
  • If the tool is not available for Linux, clarify this limitation early in the documentation.
  • Consider adding screenshots or instructions for Linux environments if supported.
GitHub Create Pull Request
Data Factory Incrementally copy data from a source data store to a destination data store ...les/data-factory/tutorial-incremental-copy-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell-based tutorials for incremental data copy scenarios, without mentioning or providing equivalent examples for Linux users (e.g., Bash, CLI, or Python). Windows-centric tools and patterns (PowerShell) are presented as the default or only option, and there is no guidance for performing these tasks on Linux or cross-platform environments.
Recommendations
  • Add equivalent step-by-step tutorials using Azure CLI, Bash scripts, or Python for Linux and cross-platform users.
  • Explicitly mention cross-platform alternatives alongside PowerShell examples, ensuring parity in instructions and tooling.
  • Include links to documentation or templates that demonstrate incremental copy scenarios using non-Windows tools.
  • Clarify which steps or tools are platform-specific and provide guidance for adapting them to Linux environments.
  • Ensure that examples and templates are available for both Windows and Linux users, and avoid presenting Windows tools as the default.
GitHub Create Pull Request
Data Factory Global parameters ...main/articles/data-factory/author-global-parameters.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page references PowerShell scripts as the method for deploying global parameters in CI/CD, without mentioning Linux equivalents such as Bash, Azure CLI, or cross-platform deployment options. Windows tooling (PowerShell) is presented as the default or only option for automation, and no Linux-specific or cross-platform examples are provided.
Recommendations
  • Add examples for deploying global parameters using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Provide Bash script examples for ARM template deployment to demonstrate Linux parity.
  • Explicitly mention that PowerShell is one option and highlight alternatives for users on non-Windows platforms.
  • Include a table or section comparing deployment options across Windows and Linux environments.
  • Ensure screenshots and instructions do not assume a Windows environment unless necessary, and clarify any platform-specific steps.
GitHub Create Pull Request
Data Factory Applying DataOps ...-docs/blob/main/articles/data-factory/apply-dataops.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools such as PowerShell and Visual Studio/NUnit for automated testing, and examples or tutorials are given for these tools without mentioning Linux alternatives. The use of PowerShell and .NET/NUnit is highlighted for CI/CD and testing, while Linux-native tools (e.g., Bash, shell scripts, pytest) are not mentioned. Additionally, Windows tools and patterns are presented first or exclusively, and there are no explicit examples or guidance for Linux users.
Recommendations
  • Include Linux-native examples for CI/CD and testing, such as using Bash scripts, shell commands, or Python-based testing frameworks (e.g., pytest).
  • Mention cross-platform alternatives to PowerShell, such as Azure CLI commands that work on Linux, and provide sample usage.
  • Reference Linux-compatible editors and development environments (e.g., VS Code, JetBrains IDEs) alongside Visual Studio.
  • Add explicit notes or sections for Linux users, clarifying that all steps can be performed on Linux and providing any necessary adaptations.
  • Ensure that any referenced open-source utilities or frameworks are cross-platform, and provide installation and usage instructions for Linux.
GitHub Create Pull Request
← Previous Page 2 of 40 Next →