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 101-125 of 319 flagged pages
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-sqldb-to-cosmosdb.md ...main/articles/data-factory/how-to-sqldb-to-cosmosdb.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows by referencing the Adventure Works sample database with a link to SQL Server Management Studio (SSMS), a Windows-only tool, and by not providing any Linux-specific instructions or examples. There are no mentions of Linux-compatible tools (such as Azure Data Studio or sqlcmd), nor are there any command-line examples or guidance for users on Linux or macOS. The documentation assumes the use of Windows-based tools and patterns throughout.
Recommendations
  • Include instructions or links for installing and accessing the Adventure Works sample database using cross-platform tools such as Azure Data Studio or sqlcmd.
  • Provide examples or notes for users on Linux and macOS, especially for any steps that reference SSMS or other Windows-only tools.
  • Explicitly mention that Azure Data Factory and Azure Cosmos DB are accessible from any OS via the Azure Portal, and clarify that no step requires a Windows-only environment.
  • Wherever possible, use tool-agnostic language and provide parity in screenshots or command-line examples for Linux/macOS users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-create-install-integration-runtime.md ...des/data-factory-create-install-integration-runtime.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides PowerShell commands and instructions for Windows environments. All installation and configuration steps reference Windows tools (e.g., 'Add or Remove Programs', Windows installer, GUI setup wizards), and there is no mention of Linux or cross-platform alternatives. No Linux shell or CLI examples are provided, and the download link is for a Windows-only installer.
Recommendations
  • Provide equivalent instructions and examples for Linux environments, including bash/CLI commands where possible.
  • Clarify up front if the self-hosted integration runtime is only supported on Windows, or provide links to Linux support if available.
  • If Linux is supported, include installation steps for Linux (e.g., using .tar.gz packages, systemd services, etc.).
  • Mention Linux tools and patterns (such as package managers or command-line uninstall methods) alongside Windows tools.
  • Ensure that all code examples are available in both PowerShell and bash (or other relevant shells) where applicable.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-quickstart-prerequisites.md ...tory/includes/data-factory-quickstart-prerequisites.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits Windows bias by referencing Windows-specific tools and patterns (e.g., Notepad, C:\ paths), omitting Linux/macOS equivalents for file creation and storage paths, and not providing cross-platform instructions for tasks such as editing files or navigating the filesystem. All examples and instructions assume a Windows environment, with no mention of Linux or macOS alternatives.
Recommendations
  • Provide Linux/macOS equivalents for file creation (e.g., using nano, vim, or TextEdit instead of Notepad).
  • Use platform-agnostic or parallel file path examples (e.g., C:\ADFv2QuickStartPSH for Windows, ~/ADFv2QuickStart for Linux/macOS).
  • Explicitly mention that the Azure portal steps are cross-platform, but clarify any OS-specific steps.
  • Include notes or callouts for Linux/macOS users where instructions differ (e.g., uploading files from different local paths).
  • Avoid assuming the use of Windows-only tools or patterns unless necessary, and always provide alternatives.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-quickstart-verify-output-cleanup.md ...ludes/data-factory-quickstart-verify-output-cleanup.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
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 examples for Linux users, such as Azure CLI or Bash equivalents. This creates a bias towards Windows users and tools.
Recommendations
  • Add equivalent Azure CLI commands for deleting resource groups and data factories, as Azure CLI is cross-platform and commonly used on Linux and macOS.
  • Explicitly mention that PowerShell commands can be run on any platform with PowerShell Core, or provide guidance for installing PowerShell on Linux/macOS.
  • Reorder or parallelize examples so that both PowerShell and Azure CLI/Bash commands are shown together, ensuring parity for Linux users.
  • Include a note or section addressing cross-platform usage, clarifying that the steps can be performed on any OS with the appropriate tools.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-v2-connector-get-started.md ...tory/includes/data-factory-v2-connector-get-started.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page lists Azure PowerShell as a primary tool for performing copy activities, which is a Windows-centric technology. There is no mention of Linux-specific command-line tools (such as Azure CLI), and the order of tools places PowerShell before more cross-platform options. The examples and tool references lean towards Windows environments, with no explicit Linux examples or parity.
Recommendations
  • Include Azure CLI as a recommended tool, as it is cross-platform and widely used on Linux.
  • Provide explicit examples or links for Linux users, such as bash scripts or CLI commands.
  • Reorder the list to avoid implicit prioritization of Windows tools; group cross-platform tools together.
  • Add notes or sections clarifying tool availability and usage on Linux/macOS platforms.
  • Ensure parity in documentation by providing both PowerShell and CLI examples where applicable.
GitHub Create Pull Request
Data Factory Source control ...docs/blob/main/articles/data-factory/source-control.md
Medium Priority View Details →
Scanned: 2026-01-16 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Powershell Heavy
Summary
The documentation mentions PowerShell as a method for publishing changes and updating Data Factory configurations, but does not provide equivalent examples or explicit guidance for Linux/macOS users (e.g., Bash, Azure CLI). This may create friction for non-Windows users who do not use PowerShell.
Recommendations
  • Add explicit examples for Linux/macOS users using Azure CLI or Bash scripts for tasks currently described as being performed via PowerShell.
  • Clarify which operations can be performed using cross-platform tools and provide links or code samples.
  • Where PowerShell is mentioned, note the equivalent Azure CLI or REST API commands if available.
GitHub Create Pull Request
Data Factory Copy data from/to a file system ...ob/main/articles/data-factory/connector-file-system.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-style paths (backslashes, UNC paths) are shown first and exclusively in examples. References to enabling local machine access under Self-hosted Integration Runtime point to PowerShell commands, with no Linux equivalent or guidance. The use of Windows terminology (e.g., 'FileServer', '\\myserver\share') is prevalent, while Linux alternatives are only briefly mentioned (Samba) and lack concrete examples. There are no Linux-specific sample configurations, and the documentation does not clarify how to author paths for Linux shares or provide Linux command-line instructions.
Recommendations
  • Provide Linux-specific examples for file paths (e.g., /mnt/share, /srv/samba/share) alongside Windows UNC paths.
  • Include instructions and sample commands for configuring Self-hosted Integration Runtime access on Linux, such as using shell scripts or systemd, not just PowerShell.
  • Expand the Samba mention with a step-by-step guide or link to Azure-relevant Samba setup documentation.
  • Clarify how to format 'host' and 'folderPath' properties for Linux shares in both JSON and UI authoring.
  • Add troubleshooting tips for common Linux/Samba issues (permissions, SELinux, etc.).
  • Ensure all command-line references (e.g., enabling local access) have Linux equivalents.
GitHub Create Pull Request
Data Factory BCDR for Azure Data Factory and Azure Synapse Analytics Pipelines ...n/articles/data-factory/pipelines-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references Azure PowerShell for automation (e.g., disabling triggers, approving private endpoints) and links to PowerShell-based scripts without mentioning or providing equivalent Bash/CLI examples for Linux/macOS users. Automation steps and tooling are described primarily in terms of Windows-centric technologies, with no explicit Linux alternatives or parity.
Recommendations
  • Provide equivalent Azure CLI (az) and Bash script examples for all PowerShell automation tasks, such as disabling triggers and approving private endpoints.
  • Explicitly mention cross-platform support and clarify which steps can be completed on Linux/macOS, including links to relevant documentation.
  • Add notes or sections for Linux/macOS users, highlighting any differences or additional steps required.
  • Where possible, use platform-neutral language (e.g., 'use Azure CLI or PowerShell') and order examples so that neither platform is prioritized.
GitHub Create Pull Request
Data Factory Copy data to and from Azure Table storage ...articles/data-factory/connector-azure-table-storage.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell-only example for generating a service shared access signature (SAS) for Azure Table Storage, with no mention of Linux/macOS alternatives (such as Azure CLI or REST API). This creates friction for users on non-Windows platforms who may not have access to PowerShell or prefer cross-platform tools. The rest of the documentation is platform-neutral, focusing on JSON configuration and Azure portal UI.
Recommendations
  • Add equivalent Azure CLI commands for generating SAS tokens, which work on Linux/macOS and Windows.
  • Mention REST API methods for SAS generation as a platform-agnostic alternative.
  • Explicitly state that PowerShell is one option, and provide links or examples for other platforms.
  • Consider a 'Platform considerations' note in the authentication section to guide users on tool choice.
GitHub Create Pull Request
Data Factory Troubleshoot the Dynamics 365, Dataverse (Common Data Service), and Dynamics CRM connectors ...a-factory/connector-troubleshoot-dynamics-dataverse.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references XrmToolBox, a Windows-only tool, as a recommended troubleshooting method for connecting to Dynamics and testing FetchXML queries. No Linux/macOS alternatives or cross-platform instructions are provided, and there are no command-line or platform-neutral examples for troubleshooting tasks.
Recommendations
  • Provide cross-platform alternatives to XrmToolBox, such as REST API usage, PowerShell Core (which runs on Linux/macOS), or open-source tools that work on all platforms.
  • Include instructions or examples for troubleshooting using platform-neutral methods (e.g., using curl, Postman, or other cross-platform utilities).
  • Explicitly mention whether any recommended tools or steps are Windows-only, and offer Linux/macOS equivalents where possible.
  • Add a note about running XrmToolBox via Wine or virtualization for Linux/macOS users, if no alternatives exist.
GitHub Create Pull Request
Data Factory Copy data from Vertica ...s/blob/main/articles/data-factory/connector-vertica.md
Medium 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 page demonstrates a Windows bias in the 'Install Vertica ODBC driver' section, where only Windows installation steps and screenshots are provided. There are no instructions or examples for installing the Vertica ODBC driver on Linux or macOS, despite the self-hosted integration runtime being supported on those platforms. The use of Windows-specific tools (e.g., ODBC Data Source Administrator) is mentioned exclusively.
Recommendations
  • Add installation instructions and screenshots for Vertica ODBC driver on Linux and macOS, including command-line steps (e.g., using .rpm/.deb packages or tarballs).
  • Mention platform-specific configuration steps for verifying ODBC driver installation on Linux/macOS (e.g., using odbcinst, editing odbc.ini).
  • Clearly state that the self-hosted integration runtime can run on Linux and macOS, and provide parity in setup guidance.
  • Present Windows, Linux, and macOS instructions side-by-side or in tabs to avoid prioritizing one platform.
GitHub Create Pull Request
Data Factory If Condition activity ...les/data-factory/control-flow-if-condition-activity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides only PowerShell command examples for running Azure Data Factory pipelines, assumes file paths in Windows format (e.g., C:\ADF), and references a Windows-centric workflow. There are no CLI, Bash, or cross-platform instructions, nor are Linux/macOS file path conventions or tools mentioned.
Recommendations
  • Add equivalent Azure CLI examples for pipeline creation and execution, which work on Linux, macOS, and Windows.
  • Show file path examples using both Windows (C:\ADF) and Linux/macOS (/home/user/ADF) conventions.
  • Explicitly mention that the JSON definitions and pipeline steps can be executed on any OS using Azure CLI.
  • Consider providing Bash script examples for common tasks, or link to cross-platform tutorials.
  • Reorder examples so that cross-platform approaches (Azure CLI) are shown before or alongside PowerShell.
GitHub Create Pull Request
Data Factory Copy or clone a data factory in Azure Data Factory .../main/articles/data-factory/copy-clone-data-factory.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references a pattern for sharing SelfHosted Integration Runtime published in a PowerShell-specific article, implying a reliance on Windows tooling. No Linux/macOS equivalents or cross-platform CLI examples are provided, and the only external automation reference is Windows-centric.
Recommendations
  • Provide equivalent instructions or links for sharing SelfHosted Integration Runtime using Azure CLI, Bash, or cross-platform tools.
  • Explicitly mention whether the referenced PowerShell pattern can be run on PowerShell Core on Linux/macOS, or offer alternative scripts.
  • Add examples or links for ARM template deployment using Azure CLI or REST API, which are cross-platform.
  • Ensure automation and scripting guidance is not limited to Windows/PowerShell.
GitHub Create Pull Request
Data Factory Until activity ...n/articles/data-factory/control-flow-until-activity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides detailed PowerShell command examples for running Azure Data Factory pipelines, with explicit references to Windows file paths (e.g., C:\ADF) and no equivalent instructions for Linux/macOS users. The only CLI shown is PowerShell, and there are no Azure CLI, Bash, or cross-platform alternatives. This creates friction for non-Windows users, who must adapt the instructions themselves.
Recommendations
  • Add Azure CLI examples for pipeline creation, execution, and monitoring, which work on Linux/macOS/Windows.
  • Use platform-neutral file paths in examples (e.g., /home/user/ADF or ./ADF) or clarify how to adapt them.
  • Explicitly mention how Linux/macOS users can perform the same tasks, including installation and usage of Azure CLI.
  • Provide Bash script equivalents for monitoring pipeline runs.
  • Add a note clarifying cross-platform support and linking to relevant Azure CLI documentation.
GitHub Create Pull Request
Data Factory Mapping data flow script ...cs/blob/main/articles/data-factory/data-flow-script.md
Medium Priority View Details →
Scanned: 2026-01-12 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 primarily through its explicit mention of PowerShell as the main method for programmatically passing DFS scripts, without referencing Linux/macOS alternatives (such as Bash, Azure CLI, or REST API usage). Windows tooling is mentioned first and exclusively in the context of automation, and there are no examples or guidance for Linux/macOS users on how to perform equivalent tasks.
Recommendations
  • Add examples showing how to use DFS scripts with Azure CLI and REST API, which are cross-platform.
  • Explicitly mention that PowerShell is available on Linux/macOS, or provide Bash equivalents for script automation.
  • Rephrase sections to reference platform-neutral automation methods before or alongside PowerShell.
  • Include notes or links for Linux/macOS users on how to collapse/format scripts for API/CLI usage.
GitHub Create Pull Request
Data Factory Azure Private Link for Azure Data Factory ...ain/articles/data-factory/data-factory-private-link.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides explicit instructions and examples for creating a Windows Server virtual machine to host the self-hosted integration runtime (IR), with no mention of Linux-based alternatives or parity. The VM creation steps and image selection are Windows-centric, and there are no examples or guidance for deploying the self-hosted IR on Linux or macOS systems.
Recommendations
  • Add instructions and examples for deploying the self-hosted IR on Linux virtual machines, including supported distributions and setup steps.
  • Clarify whether the self-hosted IR supports Linux and macOS, and if so, provide parity in documentation for those platforms.
  • Include cross-platform guidance for firewall, DNS, and networking configuration, highlighting any platform-specific considerations.
  • Present OS options (Windows, Linux) side-by-side or in parallel, rather than Windows-first.
GitHub Create Pull Request
Data Factory Run SSIS package with Stored Procedure Activity - Azure ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-stored-procedure-activity.md
Medium 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 page demonstrates a notable Windows bias, especially in the 'Azure PowerShell' section, which exclusively uses PowerShell commands and Windows-style file paths (e.g., C:\ADF\RunSSISPackage). There are no examples or instructions for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform file system conventions. The PowerShell approach is presented as the only automation method, and Windows-centric tooling and patterns are referenced throughout, with no mention of Linux equivalents or alternatives.
Recommendations
  • Add equivalent Azure CLI or REST API examples for all PowerShell-based steps, enabling Linux/macOS users to automate tasks without PowerShell.
  • Use platform-neutral file paths in examples, or provide both Windows and Linux/macOS versions (e.g., C:\ADF\RunSSISPackage and ~/ADF/RunSSISPackage).
  • Explicitly mention that PowerShell Core is available cross-platform, and provide installation/usage guidance for Linux/macOS if PowerShell is required.
  • Reorder sections so that platform-neutral or cross-platform methods (e.g., Azure portal, Azure CLI) are presented before Windows-specific tools.
  • Include notes or links to documentation for Linux/macOS users on how to adapt the instructions.
GitHub Create Pull Request
Data Factory Review deployed resources ...ludes/data-factory-quickstart-verify-output-cleanup.md
Medium Priority View Details →
Scanned: 2026-01-12 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 Windows-centric. There are no examples or guidance for Linux/macOS users, such as using Azure CLI or Bash. This creates friction for non-Windows users who may not have access to PowerShell or prefer platform-agnostic tools.
Recommendations
  • Add equivalent Azure CLI commands for resource group and data factory deletion.
  • Include notes or examples for Bash/shell usage on Linux/macOS.
  • Clearly indicate platform requirements for the provided commands.
  • Present cross-platform options before or alongside Windows-specific instructions.
GitHub Create Pull Request
Data Factory Join Azure-SSIS integration runtime to a virtual network ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/join-azure-ssis-integration-runtime-virtual-network.md
Medium Priority View Details →
Scanned: 2026-01-12 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 Azure PowerShell as a primary method for provisioning Azure-SSIS IR and joining it to a virtual network, with no mention of Linux/macOS-compatible alternatives (such as Azure CLI or REST API). Example links and instructions are provided for Azure PowerShell and ADF UI, but there are no equivalent examples for Linux-friendly tools. This creates friction for users on non-Windows platforms.
Recommendations
  • Add instructions and examples for using Azure CLI to provision Azure-SSIS IR and join it to a virtual network.
  • Include REST API references or examples for cross-platform automation.
  • Clearly indicate which steps/tools are platform-agnostic (ADF UI, REST API) and which are Windows-specific (Azure PowerShell).
  • Where PowerShell is mentioned, provide parallel CLI commands or links to CLI documentation.
  • Review related content and tutorials to ensure Linux/macOS parity in step-by-step guides.
GitHub Create Pull Request
Data Factory Self-hosted integration runtime autoupdate and expire notification ...factory/self-hosted-integration-runtime-auto-update.md
Medium 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 page demonstrates a notable Windows bias by exclusively providing PowerShell-based examples and instructions for managing and checking self-hosted integration runtime versions and expiration. There are no Linux/macOS-specific examples or CLI alternatives, and the use of Windows-centric tools (PowerShell, screenshots of Windows clients) is prevalent throughout. This creates friction for users on Linux or macOS platforms who may not have access to PowerShell or the Windows client.
Recommendations
  • Provide equivalent examples using Bash and Azure CLI commands that work natively on Linux/macOS.
  • Clarify whether the self-hosted integration runtime client is available for Linux/macOS, and if so, include relevant screenshots and instructions.
  • List both Windows and Linux/macOS instructions side-by-side, or indicate platform-specific steps where relevant.
  • Avoid assuming PowerShell is available; use cross-platform tools (e.g., Azure CLI, REST API) for scripting examples.
GitHub Create Pull Request
Data Factory Troubleshoot SSIS Integration Runtime management ...ry/ssis-integration-runtime-management-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by referencing PowerShell cmdlets as the primary method for error reporting and troubleshooting, mentioning SSMS (SQL Server Management Studio, a Windows-only tool) for database checks, and lacking Linux/macOS-specific guidance or examples. No alternatives such as Azure CLI, cross-platform database tools, or shell scripting are provided for non-Windows users.
Recommendations
  • Include troubleshooting steps using Azure CLI, which is cross-platform, alongside or instead of PowerShell.
  • Mention and provide examples with cross-platform database tools (e.g., Azure Data Studio, sqlcmd) for checking SQL Database/Managed Instance status.
  • Explicitly state which steps/tools are Windows-only and offer Linux/macOS alternatives.
  • Add Linux/macOS-specific error reporting and troubleshooting examples, especially for custom setup script testing.
  • Reorder examples so that cross-platform or OS-neutral tools are presented before Windows-specific ones.
GitHub Create Pull Request
Data Factory Transform data using Hadoop Hive activity ...icles/data-factory/transform-data-using-hadoop-hive.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation references a tutorial that uses Spark with PowerShell, suggesting Windows-first orientation. No Linux/macOS-specific instructions, examples, or tool references are provided. The page avoids OS-specific command-line examples, but the only explicit workflow reference is to a PowerShell-based tutorial, which may create friction for non-Windows users.
Recommendations
  • Add links to equivalent Linux/macOS tutorials or instructions (e.g., using Bash or Azure CLI for pipeline creation and management).
  • Clarify that the Hive activity and HDInsight clusters are cross-platform and can be managed from Linux/macOS environments.
  • Provide example workflows or scripts for Linux/macOS users, such as using Azure CLI or Bash.
  • Avoid referencing only PowerShell-based tutorials; offer parity with Bash/CLI alternatives.
GitHub Create Pull Request
Data Factory Transform data using Hadoop Streaming activity .../data-factory/transform-data-using-hadoop-streaming.md
Medium 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 page demonstrates a Windows bias by exclusively using Windows-style executable names (e.g., MyMapper.exe, MyReducer.exe) in the JSON sample and file paths, without mentioning or providing examples for Linux-style scripts (e.g., .py, .sh). There are no Linux/macOS-specific examples or guidance, and the use of .exe implies a Windows-centric approach to Hadoop Streaming, which is typically more common with Linux shell scripts or Python scripts in Hadoop environments.
Recommendations
  • Include examples using Linux-style executables, such as Python (.py) or shell (.sh) scripts, in the JSON sample and file paths.
  • Add a note clarifying that both Windows and Linux executables are supported, and specify any platform-specific considerations.
  • Provide guidance or links for preparing mapper/reducer scripts for Linux/macOS users.
  • Show Linux/macOS examples alongside Windows examples to ensure parity.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page consistently references PowerShell-based tutorials for incremental data copy scenarios, with no mention of Linux/macOS alternatives or cross-platform tools. All step-by-step instructions link to PowerShell guides, and Windows-centric patterns are presented first and exclusively, leaving Linux users without clear guidance.
Recommendations
  • Add equivalent tutorials using Azure CLI, which is cross-platform and supported on Linux/macOS.
  • Include examples using REST API or SDKs (Python, .NET, etc.) for incremental copy operations.
  • Explicitly mention platform compatibility for each tutorial and provide Linux/macOS instructions where possible.
  • Reorder or parallelize example listings so that Windows and Linux approaches are presented equally.
GitHub Create Pull Request
Data Factory Configure a virtual network for express injection of Azure-SSIS integration runtime ...-integration-runtime-express-virtual-network-injection.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias, primarily in the section on configuring a custom DNS server. It instructs users to download and use a setup script (main.cmd) and an associated PowerShell script (setupdnsserver.ps1), both of which are Windows-centric tools. There are no equivalent Linux/bash examples or scripts provided, nor is there guidance for users on Linux/macOS platforms for performing the same configuration tasks. The related content also references Azure PowerShell as a method for joining the IR to a virtual network, without mentioning CLI or bash alternatives.
Recommendations
  • Provide equivalent bash or shell scripts for Linux/macOS users to configure custom DNS server settings.
  • Include instructions or references for using Azure CLI (az) for all configuration steps, especially for joining IR to a virtual network and granting permissions.
  • Clearly indicate platform requirements for provided scripts, and offer cross-platform alternatives where possible.
  • Add explicit Linux/macOS examples alongside Windows/PowerShell examples in all relevant sections.
GitHub Create Pull Request
← Previous Page 5 of 13 Next →