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 476-500 of 1000 flagged pages
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/source-control.md ...docs/blob/main/articles/data-factory/source-control.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page for Azure Data Factory source control demonstrates a subtle Windows bias. PowerShell is referenced as a method for publishing changes and updating configuration, but there are no equivalent examples or mentions of Linux shell commands or cross-platform CLI usage. Windows-specific tools (PowerShell, Azure Portal, Visual Studio) are mentioned, and troubleshooting steps reference PowerShell and SDK usage without alternatives for Linux users. There are no explicit Linux or macOS examples, nor is there guidance for using Azure CLI or other cross-platform tools. The ordering of examples and instructions also tends to prioritize Windows-centric workflows.
Recommendations
  • Include equivalent Linux/macOS command-line examples using Azure CLI or Bash where PowerShell is referenced.
  • Explicitly mention cross-platform compatibility for SDKs and provide sample commands for both Windows (PowerShell) and Linux/macOS (Bash, Azure CLI).
  • Add troubleshooting steps that use Azure CLI or REST API, not just PowerShell.
  • Clarify that the Azure Data Factory UX and Git integration work on all major platforms and browsers, and note any platform-specific limitations.
  • Where Visual Studio or Windows tools are referenced, suggest alternatives for Linux/macOS (e.g., VS Code, JetBrains IDEs).
  • Ensure that screenshots and instructions do not assume a Windows environment unless necessary, and provide parity for Linux/macOS users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/transform-data-using-hadoop-hive.md ...icles/data-factory/transform-data-using-hadoop-hive.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily by referencing a tutorial that uses PowerShell ('Tutorial: transform data'), which is a Windows-centric tool, as a prerequisite for understanding the Hive activity. There are no Linux shell or cross-platform CLI examples provided, nor is there mention of Linux tools or patterns for interacting with Azure Data Factory or Synapse Analytics. The syntax examples use Windows-style path separators (\) in 'scriptPath', further reinforcing a Windows-first approach.
Recommendations
  • Include equivalent Linux shell (bash) or Azure CLI examples for running Hive activities and managing pipelines.
  • Reference tutorials or guides that use cross-platform tools (e.g., Azure CLI, bash scripts) alongside PowerShell.
  • Use platform-neutral path separators (/) in documentation examples, or clarify cross-platform path conventions.
  • Explicitly mention that the features and steps are available and supported on Linux and macOS, not just Windows.
  • Provide troubleshooting or usage notes for non-Windows environments where relevant.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/ssis-integration-runtime-management-troubleshoot.md ...ry/ssis-integration-runtime-management-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing PowerShell cmdlets as the primary command-line interface for troubleshooting, mentioning SSMS (SQL Server Management Studio) as the tool to check SQL Database status (which is Windows-only), and using .cmd scripts (main.cmd) for custom setup, which are native to Windows. There are no examples or guidance for Linux users, such as using Azure CLI, cross-platform SQL tools, or bash scripts.
Recommendations
  • Provide equivalent troubleshooting steps using Azure CLI and/or Bash for Linux/macOS users, not just PowerShell.
  • Mention and give examples for cross-platform SQL tools (e.g., Azure Data Studio, sqlcmd) alongside or instead of SSMS.
  • Allow and document the use of bash or PowerShell Core scripts for custom setup, not just main.cmd (Windows batch).
  • Explicitly state whether the SSIS IR custom setup supports Linux shell scripts, and if not, clarify the Windows-only requirement.
  • When referencing tools or commands, present cross-platform options first or in parallel, rather than only or first mentioning Windows-specific tools.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-hybrid-copy-data-tool.md ...rticles/data-factory/tutorial-hybrid-copy-data-tool.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias toward Windows by exclusively referencing Windows tools (SQL Server Management Studio), omitting Linux equivalents for SQL Server management and integration runtime installation, and implicitly assuming a Windows environment for local setup steps. There are no examples or instructions for performing the same tasks on Linux, nor are cross-platform alternatives mentioned.
Recommendations
  • Include instructions for managing SQL Server from Linux, such as using Azure Data Studio or sqlcmd.
  • Provide guidance for installing and running the self-hosted integration runtime on Linux, including supported distributions and any prerequisites.
  • Add Linux-specific examples and screenshots where applicable, or clarify cross-platform compatibility for each step.
  • Mention alternative tools and workflows for users on macOS and Linux, ensuring parity in setup and troubleshooting guidance.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/transform-data-using-custom-activity.md ...s/data-factory/transform-data-using-custom-activity.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a strong Windows bias. PowerShell commands are exclusively used for Azure Batch account and pipeline management, with no mention of equivalent Azure CLI or Bash commands. Examples for executing commands on Batch nodes use Windows-specific tools (e.g., 'cmd /c', '.exe' applications) and do not provide Linux shell equivalents. Windows patterns and tooling are mentioned first and exclusively, while Linux options are missing throughout the page.
Recommendations
  • Add Azure CLI and Bash examples for creating and managing Azure Batch accounts and pipelines, alongside PowerShell.
  • Provide Linux shell command examples (e.g., '/bin/bash -c "echo hello world"') for the 'command' property in Custom Activity, and clarify OS-specific differences.
  • Include examples of running Linux executables (e.g., ELF binaries, Python scripts) in addition to Windows '.exe' files.
  • Explicitly document how to configure Azure Batch pools with Linux VM images, and note any differences in command syntax or file paths.
  • Ensure that references to Windows tools (cmd, .exe) are balanced with Linux equivalents (bash, .sh, etc.), and avoid presenting Windows options first or exclusively.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-incremental-copy-overview.md ...les/data-factory/tutorial-incremental-copy-overview.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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. All step-by-step instructions link to PowerShell guides, with no mention of Linux shell, CLI, or cross-platform alternatives. Windows-centric tools and patterns are presented first and exclusively, leaving out Linux-native approaches or examples.
Recommendations
  • Add equivalent tutorials using Azure CLI, Bash, or Python scripts to provide Linux-friendly options.
  • Explicitly mention cross-platform alternatives alongside PowerShell, clarifying which steps work on Linux/macOS.
  • Include sample commands and walkthroughs for Linux environments, such as using Azure CLI or REST API.
  • Ensure templates and solution guides are not dependent on Windows-only tooling.
  • Review related content and next steps to include Linux-compatible documentation links.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-control-flow.md ...ob/main/articles/data-factory/tutorial-control-flow.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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. All code samples and instructions use Visual Studio (Windows-only), C#/.NET SDK, and Azure Storage Explorer (primarily Windows). There are no Linux or cross-platform alternatives mentioned for project setup, development environment, or tooling. Package installation is shown only via NuGet/PowerShell, and there is no guidance for Linux users (e.g., using VS Code, .NET CLI, or alternative storage tools).
Recommendations
  • Provide instructions for setting up the project using cross-platform tools such as Visual Studio Code and the .NET CLI.
  • Include Linux/macOS equivalents for installing the Azure .NET SDK and required NuGet packages (e.g., using 'dotnet add package').
  • Mention and provide examples for using Azure Storage Explorer on Linux/macOS, or suggest alternatives like azcopy or Azure CLI.
  • Clarify that Azure Data Factory SDK and APIs can be used from any OS, and provide sample commands for Linux/macOS environments.
  • Add notes or sections for Linux users, including how to run, build, and monitor the pipeline from non-Windows systems.
  • Avoid assuming Visual Studio is the only development environment; offer alternatives for cross-platform development.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-deploy-ssis-packages-azure.md ...es/data-factory/tutorial-deploy-ssis-packages-azure.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-based tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and managing SSIS packages, with no mention of Linux-compatible alternatives or cross-platform usage. All examples and tool references assume a Windows environment, and there is no guidance for Linux users or parity in instructions for non-Windows platforms.
Recommendations
  • Explicitly state platform requirements and limitations for SSIS tooling (e.g., SSDT and SSMS are Windows-only).
  • Provide guidance for Linux users, such as using Azure Data Factory web UI or REST APIs for package deployment and management.
  • Mention any cross-platform command-line utilities or third-party tools (if available) for SSIS package deployment and execution.
  • Add examples or workflows for deploying and managing SSIS packages from Linux or macOS environments, where possible.
  • Clarify which steps are platform-agnostic (e.g., Azure portal usage) and which require Windows-specific tools.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-hive-virtual-network.md ...actory/tutorial-transform-data-hive-virtual-network.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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, with no mention of Azure CLI, Bash, or Linux shell equivalents. Instructions for editing the hosts file reference the Windows path only, and the self-hosted integration runtime registration is described for Windows VMs, with no guidance for Linux. There are no Linux-specific instructions or examples, and Windows tools and patterns are mentioned exclusively and first.
Recommendations
  • Provide equivalent Azure CLI and Bash examples for all PowerShell commands, especially for resource creation and pipeline management.
  • Include instructions for registering self-hosted integration runtime on Linux VMs, with download and installation steps for Linux.
  • When referencing file paths (e.g., hosts file), include both Windows and Linux locations (e.g., /etc/hosts for Linux).
  • Mention cross-platform editors and tools for creating JSON files, not just generic 'preferred editor'.
  • Clarify that Azure Data Factory and HDInsight support both Windows and Linux environments, and provide parity in troubleshooting and configuration steps.
  • Add screenshots or terminal outputs from Linux environments where appropriate.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-copy-data-dot-net.md ...in/articles/data-factory/tutorial-copy-data-dot-net.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased toward Windows environments. All code samples use C#/.NET and Visual Studio, with instructions tailored for Windows users. Tools like Notepad, Visual Studio, SQL Server Management Studio (SSMS), and PowerShell/NuGet Package Manager Console are referenced exclusively, with no mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for performing these steps on Linux or macOS, nor are CLI or Python SDK options provided.
Recommendations
  • Add instructions and code samples for using Azure Data Factory via Azure CLI, Python SDK, or REST API, which are cross-platform.
  • Include Linux/macOS equivalents for steps such as editing files (e.g., using nano/vim), installing packages, and running code.
  • Mention and provide examples for using VS Code or other cross-platform editors instead of only Visual Studio.
  • Reference Azure Storage Explorer's Linux/macOS versions and provide CLI alternatives (e.g., az storage commands).
  • Provide SQL table creation steps using cross-platform tools (e.g., Azure Data Studio, sqlcmd).
  • Avoid referencing PowerShell/NuGet Package Manager Console exclusively; include dotnet CLI and pip instructions for package management.
  • Explicitly state platform requirements and offer parity for Linux/macOS users throughout the tutorial.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-hive-virtual-network-portal.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-hive-virtual-network-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: it lists Azure PowerShell as a prerequisite without mentioning Bash/CLI alternatives, assumes the use of Windows VMs (e.g., referencing the Windows hosts file path), and omits instructions or examples for Linux-based environments. There are no Linux shell commands or guidance for Linux VM setup, and all tooling references (PowerShell, hosts file) are Windows-centric.
Recommendations
  • Add instructions for using Azure CLI and Bash as alternatives to Azure PowerShell.
  • Include steps for creating and configuring Linux VMs, including how to edit /etc/hosts for DNS resolution.
  • Provide Linux-specific examples for installing and registering the self-hosted integration runtime.
  • Clarify that both Windows and Linux VMs are supported, and offer parity in screenshots and walkthroughs.
  • Mention cross-platform tooling where possible, and avoid assuming a Windows-only environment.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-spark-portal.md ...s/data-factory/tutorial-transform-data-spark-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by listing Azure PowerShell as a prerequisite and linking only to PowerShell installation/configuration instructions. There are no references to Linux CLI tools (such as Azure CLI) or examples for Linux/macOS users. The instructions and screenshots are oriented around the Azure Portal UI, which is cross-platform, but the command-line guidance is Windows-centric.
Recommendations
  • Add Azure CLI as an alternative prerequisite for users on Linux/macOS, with a link to installation instructions.
  • Include examples for uploading files to Azure Blob Storage using Azure CLI or other cross-platform tools, not just PowerShell.
  • Explicitly mention that the steps can be performed on Linux/macOS and provide any necessary platform-specific notes.
  • Where PowerShell is referenced, offer equivalent Bash/Azure CLI commands in parallel.
  • Review screenshots and instructions to ensure terminology and steps are not Windows-specific.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-spark-powershell.md ...ta-factory/tutorial-transform-data-spark-powershell.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 usage. All command-line instructions for creating and deploying Azure Data Factory resources are provided exclusively using Azure PowerShell, with no mention of Azure CLI, Bash, or cross-platform alternatives. The prerequisites and workflow assume the reader is using PowerShell, which is most commonly used on Windows. There are no Linux/macOS-specific instructions, nor are there references to tools or patterns familiar to Linux users.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell instructions, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Add a section or notes on how to perform the same steps using Bash or in a Linux/macOS environment.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, and link to installation instructions for those platforms.
  • Where possible, use generic terminology (e.g., 'command-line interface') instead of assuming PowerShell.
  • Include screenshots or terminal output from Linux/macOS environments to demonstrate parity.
  • Add troubleshooting notes for common issues encountered on Linux/macOS (e.g., file path differences, authentication).
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-upgrade-guidance.md ...in/articles/data-factory/connector-upgrade-guidance.md
High Priority View Details →
Scanned: 2025-08-25 00:01
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell scripts for programmatic discovery of impacted objects, with no mention of Linux or cross-platform alternatives (such as Bash, Azure CLI, or Python). The guidance assumes the use of Windows tools and patterns, and does not address how Linux or macOS users can achieve the same tasks. There are no Linux-specific instructions or examples, and the only automation guidance is via PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Provide equivalent examples using Azure CLI, Bash scripts, or Python for programmatic discovery of impacted objects, ensuring Linux and macOS users are supported.
  • Explicitly mention whether the provided PowerShell scripts are compatible with PowerShell Core on Linux/macOS, and provide installation guidance if so.
  • Add a section or note addressing cross-platform usage, including any prerequisites or differences for Linux users.
  • Where possible, offer downloadable scripts or command snippets in both PowerShell and Bash/Azure CLI formats.
  • Review all automation and scripting guidance to ensure parity for users on non-Windows platforms.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/compute-linked-services.md .../main/articles/data-factory/compute-linked-services.md
High Priority View Details →
Scanned: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation demonstrates some Windows bias, particularly in the Azure Batch section, where PowerShell cmdlets (New-AzBatchAccount, New-AzBatchPool) are referenced as the primary method for resource creation and management, with no equivalent Linux/CLI examples. Windows tools such as Microsoft Azure Storage Explorer are mentioned for storage management, with no mention of Linux-native alternatives. The documentation also refers to 'CMDLETs & APIS' for VM sizing, which is a Windows-centric term. While the HDInsight examples specify Linux as the default OS, and the JSON configuration is platform-neutral, the overall pattern is to mention Windows tools and patterns first or exclusively.
Recommendations
  • Provide equivalent Azure CLI (az) commands alongside PowerShell cmdlets for Azure Batch and other resource management tasks, ensuring parity for Linux and macOS users.
  • When referencing tools like Microsoft Azure Storage Explorer, also mention cross-platform or Linux-native alternatives (e.g., AzCopy, Azure CLI storage commands, or third-party Linux-compatible tools).
  • Use neutral terminology such as 'commands' or 'APIs' instead of 'CMDLETs' when referring to resource configuration, or clarify that both PowerShell and CLI options are available.
  • Where possible, include Linux shell (bash) script examples or references, especially for common operational tasks (e.g., deleting storage containers, managing clusters).
  • Ensure that documentation sections referencing management or troubleshooting steps do not assume use of Windows-only tools or interfaces.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-upgrade-guidance.md ...in/articles/data-factory/connector-upgrade-guidance.md
High Priority View Details →
Scanned: 2025-07-17 00:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell script example for programmatically finding impacted objects, with no mention of Linux-compatible alternatives (such as Bash, Azure CLI, or Python). This suggests a bias toward Windows users and tools, potentially excluding users on Linux or macOS platforms.
Recommendations
  • Provide equivalent examples using Azure CLI and/or REST API calls, which are cross-platform and work natively on Linux and macOS.
  • Include a Bash or Python script example for finding impacted objects, or at least reference how to adapt the PowerShell logic for non-Windows environments.
  • Explicitly mention that the PowerShell script can be run using PowerShell Core (pwsh) on Linux/macOS, if applicable, and provide instructions for doing so.
  • Ensure that future documentation sections do not assume Windows as the default environment, and always offer cross-platform guidance where possible.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-switch-activity.md .../articles/data-factory/control-flow-switch-activity.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples are provided exclusively in PowerShell, with explicit references to Windows file paths (e.g., C:\ADF). There are no examples or instructions for running the same workflow on Linux or macOS, nor is there mention of cross-platform tools such as Azure CLI. The only automation walkthrough links and commands are for Azure PowerShell, reinforcing a Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, including pipeline deployment and execution.
  • Include Linux/macOS-friendly file path examples (e.g., ~/ADF) alongside Windows paths.
  • Explicitly mention that Azure CLI and PowerShell are both supported, and provide links to relevant CLI documentation.
  • Consider providing Bash script examples for automation, or at least note how the process would differ on non-Windows platforms.
  • Ensure that walkthroughs and tutorials referenced in the documentation include cross-platform coverage.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-web-activity.md ...ain/articles/data-factory/control-flow-web-activity.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing a PowerShell snippet for base64-encoding a PFX file, without offering a Linux/Unix equivalent (such as an OpenSSL or base64 command-line example). The only tool-specific guidance is for Windows/PowerShell users, and no Linux or cross-platform alternatives are mentioned. This may hinder Linux users from following the instructions seamlessly.
Recommendations
  • Add equivalent Linux/Unix shell commands for base64-encoding a PFX file, such as using 'base64' and 'openssl'.
  • Explicitly mention that the certificate conversion and encoding can be performed on any platform, and provide cross-platform examples.
  • Wherever PowerShell or Windows-specific tools are referenced, provide parallel instructions for Bash/Linux environments.
  • Review the documentation for other subtle Windows-first assumptions, ensuring parity in tool and workflow recommendations.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/built-in-preinstalled-components-ssis-integration-runtime.md ...lt-in-preinstalled-components-ssis-integration-runtime.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exclusively describes components and environments for Azure-SSIS Integration Runtime on Windows Server 2019, with no mention of Linux support, alternatives, or parity. All listed tools, drivers, and tasks are Windows-centric (e.g., Access Database Engine, WMI, MSMQ, SQL Server Native Client), and there are no Linux equivalents or cross-platform notes. The documentation assumes a Windows-only environment and does not acknowledge or provide guidance for Linux users.
Recommendations
  • Explicitly state in the introduction that Azure-SSIS IR currently only supports Windows, if that is the case, or clarify any Linux roadmap.
  • If Linux support is planned or available, provide a parallel table or section listing Linux-compatible components, drivers, and tasks.
  • For each Windows-specific tool or component (e.g., WMI, MSMQ, Access Database Engine), mention if a Linux equivalent exists or if the functionality is unavailable on Linux.
  • Add a section on cross-platform considerations, including any limitations or workarounds for Linux users.
  • Where possible, provide examples or documentation links for configuring or running SSIS packages on Linux (e.g., using containers, Mono/.NET Core, or alternative runtimes).
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/compute-linked-services.md .../main/articles/data-factory/compute-linked-services.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias, particularly in the Azure Batch section, where PowerShell cmdlets (New-AzBatchAccount, New-AzBatchPool) are referenced as primary methods for resource creation and management, with no equivalent CLI, Bash, or Linux-native instructions provided. Additionally, Microsoft Azure Storage Explorer (a Windows-centric tool) is recommended for blob storage management, and references to 'CMDLETs & APIS' for VM sizing reinforce a Windows-first approach. While the HDInsight examples are Linux-based and the JSON configuration is OS-agnostic, the overall pattern prioritizes Windows tools and workflows.
Recommendations
  • Provide equivalent Azure CLI and Bash script examples alongside PowerShell cmdlets, especially for Azure Batch and resource management tasks.
  • Mention and link to cross-platform or Linux-native tools for Azure Blob Storage management (e.g., Azure CLI, azcopy, or third-party Linux tools) in addition to Microsoft Azure Storage Explorer.
  • When referencing 'CMDLETs & APIS', clarify that Azure CLI commands and REST APIs are equally valid and provide sample usage.
  • Ensure that all example workflows and instructions are presented in a platform-neutral way, or explicitly include both Windows and Linux variants where differences exist.
  • Review all tool recommendations to ensure Linux users are not required to use Windows-only utilities for common tasks.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-concur.md ...cs/blob/main/articles/data-factory/connector-concur.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by explicitly stating that the connector supports only Windows versions for the self-hosted integration runtime, with no mention of Linux support or alternatives. There are no Linux-specific instructions, examples, or troubleshooting notes, and the only referenced prerequisites link is to a Windows-focused article. No Linux or cross-platform parity is addressed.
Recommendations
  • Clearly state whether Linux is supported or not for the self-hosted integration runtime in this context. If not, explain the limitation.
  • If Linux support is available or planned, provide equivalent instructions, examples, and prerequisites for Linux environments.
  • Where possible, avoid language that implies Windows is the only supported or primary platform unless this is a hard technical limitation.
  • If Windows-only support is a technical constraint, suggest workarounds or alternatives for Linux users (e.g., running the integration runtime in a Windows container or VM on Linux hosts).
  • Add troubleshooting notes or FAQs for users attempting to use Linux, clarifying expected behaviors and support boundaries.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-odata.md ...ocs/blob/main/articles/data-factory/connector-odata.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a mild Windows bias. Windows authentication is explicitly supported and documented, with an example provided, but there is no mention of Linux authentication equivalents (such as Kerberos or NTLM from a Linux host). The authentication examples and property tables list 'Windows' authentication as a primary option, but do not clarify cross-platform support or limitations. Additionally, the instructions for obtaining tenant information reference a Windows-centric UI pattern (hovering in the Azure portal), and no Linux command-line or open-source tool alternatives are mentioned. The only external tool referenced is Postman, which is cross-platform, but there are no CLI or Linux-native alternatives suggested for obtaining OAuth tokens.
Recommendations
  • Clarify whether 'Windows' authentication is supported from non-Windows/self-hosted integration runtimes running on Linux, and document any limitations.
  • If 'Windows' authentication is only supported on Windows hosts, explicitly state this and provide alternative authentication methods for Linux users.
  • Include examples or references for obtaining OAuth tokens using cross-platform tools (e.g., curl, httpie, Azure CLI) in addition to Postman.
  • When referencing UI actions (like retrieving tenant info), provide equivalent CLI or cross-platform instructions.
  • If Linux-specific configuration or troubleshooting steps exist for OData connectors, include them to ensure parity.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-azure-blob-storage.md ...a-factory/connector-troubleshoot-azure-blob-storage.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (e.g., diawp.exe.config) and configuration steps (disabling FIPS mode on the VM) without providing equivalent instructions for Linux environments. There are no Linux-specific troubleshooting steps or examples, and the language assumes a Windows context for the self-hosted integration runtime.
Recommendations
  • Provide equivalent instructions for disabling FIPS mode or handling MD5/FIPS issues on Linux-based self-hosted integration runtime installations.
  • Mention Linux configuration files or paths where relevant, alongside Windows examples.
  • Explicitly state whether the troubleshooting steps apply to both Windows and Linux, or provide separate sections/examples for each platform.
  • Include notes or links to Linux-specific documentation for common troubleshooting scenarios.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-until-activity.md ...n/articles/data-factory/control-flow-until-activity.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
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 command examples and referencing Windows file paths (e.g., C:\ADF). There are no examples or instructions for Linux or cross-platform command-line tools (such as Azure CLI or Bash). The only automation walkthrough is for Azure PowerShell, and no mention is made of how to perform equivalent tasks on Linux or macOS systems.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, using Bash syntax and Linux/macOS file paths (e.g., ~/ADF).
  • Include a section or note on cross-platform support, clarifying that all operations can be performed from Linux, macOS, or Windows.
  • When referencing file paths, provide both Windows (C:\ADF) and Linux/macOS (~/ADF) variants.
  • Consider providing sample scripts in both PowerShell and Bash where automation is discussed.
  • Explicitly mention that Azure Data Factory and Synapse pipelines can be managed from any OS, and link to cross-platform tooling documentation.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-linked-services.md ...main/articles/data-factory/concepts-linked-services.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as a primary tool for creating linked services, referencing it before cross-platform or Linux-native options, and omitting explicit Linux CLI or scripting examples. There is no mention of Azure CLI, Bash, or Linux-specific workflows, and the quickstart/tutorial links prioritize .NET and PowerShell, both of which are traditionally Windows-centric.
Recommendations
  • Add examples and quickstart links for Azure CLI and Bash scripts to create linked services, ensuring Linux users have clear, first-class guidance.
  • Reorder tool/SDK lists so that cross-platform options (Azure CLI, REST API, portal) appear before or alongside PowerShell and .NET.
  • Explicitly mention that PowerShell Core is cross-platform if referencing PowerShell, or clarify which instructions are Windows-only.
  • Include sample commands for creating linked services using Azure CLI and Bash, not just PowerShell or .NET.
  • Ensure that all tool references and tutorials are balanced between Windows and Linux environments, and avoid implying Windows is the default or preferred platform.
GitHub Create Pull Request
← Previous Page 20 of 40 Next →