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 426-450 of 1000 flagged pages
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-vertica.md ...s/blob/main/articles/data-factory/connector-vertica.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 page demonstrates a Windows bias in the Vertica ODBC driver installation instructions, which exclusively use Windows as the example platform. All screenshots and step-by-step guidance reference Windows tools (such as ODBC Data Source Administrator and .exe installers), with no mention of Linux or macOS equivalents. There are no instructions or examples for installing or configuring the Vertica ODBC driver on Linux, despite the self-hosted integration runtime being commonly deployed on Linux servers.
Recommendations
  • Add parallel instructions and screenshots for installing the Vertica ODBC driver on Linux (and optionally macOS), including package installation commands (e.g., rpm, deb, tar.gz extraction) and configuration steps.
  • Mention and demonstrate how to configure ODBC data sources on Linux (e.g., editing odbc.ini and odbcinst.ini files) and how to verify installation.
  • Where Windows-specific tools are referenced (such as ODBC Data Source Administrator), provide Linux alternatives (such as unixODBC's isql or odbcinst commands).
  • Ensure that all example code and configuration snippets are platform-neutral or provide platform-specific variants as appropriate.
  • Explicitly state platform requirements and supported operating systems for the self-hosted integration runtime and Vertica connector.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-automate-azure-pipelines.md ...ntinuous-integration-delivery-automate-azure-pipelines.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 Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based automation examples and instructions, referencing Windows-centric tools and patterns (e.g., .ps1 scripts, Azure PowerShell modules), and omitting equivalent Linux/bash or cross-platform alternatives. There are no bash, CLI, or YAML pipeline examples, and all scripting guidance assumes a Windows/PowerShell environment. The documentation also refers to downloading logs and running .ps1 files, which are not natively supported on Linux agents.
Recommendations
  • Provide equivalent examples using Azure CLI and bash scripts for Linux/macOS agents.
  • Include YAML pipeline snippets that are platform-agnostic, rather than relying solely on classic UI and PowerShell tasks.
  • Mention cross-platform agent support and clarify which steps are Windows-specific.
  • Add guidance for running deployments and managing triggers using Azure CLI or REST API, which work on Linux and macOS.
  • Reference both PowerShell and bash script samples for pre/post-deployment automation.
  • Explicitly state any platform requirements or limitations for the provided instructions.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-sap.md ...in/articles/data-factory/connector-troubleshoot-sap.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides troubleshooting guidance using a PowerShell command (Test-NetConnection), which is specific to Windows environments. No equivalent Linux command or example is provided, and only Windows tooling is mentioned for connectivity testing. This creates a bias toward Windows users and may hinder Linux users from following the troubleshooting steps.
Recommendations
  • Include equivalent Linux commands (e.g., 'nc', 'telnet', or 'curl') for testing SAP server connectivity.
  • Add a note clarifying that the provided PowerShell example is for Windows, and provide step-by-step instructions for Linux users.
  • Ensure future troubleshooting steps mention both Windows and Linux tools/patterns where applicable.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-if-condition-activity.md ...les/data-factory/control-flow-if-condition-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 demonstrates a strong Windows bias by providing only PowerShell command examples, referencing Windows file paths (C:\ADF), and omitting any Linux or cross-platform CLI equivalents. The tutorial and walkthrough are centered on Azure PowerShell, with no mention of Azure CLI, Bash, or other Linux-friendly tools. This may hinder Linux users or those working in cross-platform environments from following the instructions easily.
Recommendations
  • Add equivalent Azure CLI (az) command examples for all PowerShell commands shown.
  • Include Linux/Mac file path examples (e.g., /home/user/ADF) alongside Windows paths.
  • Explicitly mention that the steps can be performed on Linux/Mac using Azure CLI, and provide links to relevant tutorials.
  • Consider providing Bash script samples for pipeline deployment and monitoring.
  • Add a note clarifying platform compatibility and suggest alternatives for non-Windows users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime.md .../data-factory/create-azure-ssis-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools (SSDT, SSMS, dtutil, PowerShell) for deploying and managing Azure-SSIS IR. There are no examples or mentions of Linux-native tools or workflows, and PowerShell is presented as the primary scripting option without alternatives for Linux users. The documentation assumes familiarity with Windows environments and does not provide parity for Linux users.
Recommendations
  • Include examples using cross-platform tools such as Azure CLI, which is available on Linux, macOS, and Windows.
  • Mention and provide guidance for deploying SSIS packages from non-Windows environments, including Linux and macOS.
  • List Linux-compatible alternatives to dtutil and SSMS, or clarify their platform limitations.
  • Provide step-by-step instructions for provisioning Azure-SSIS IR using Azure CLI and REST API, not just PowerShell.
  • Explicitly state platform requirements for each tool and recommend cross-platform options where possible.
  • Add a section addressing Linux/macOS users, outlining supported workflows and any limitations.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias primarily in the authentication section, where only a PowerShell snippet is provided for base64-encoding a PFX file for client certificate authentication. No equivalent Linux or cross-platform method (such as OpenSSL or shell commands) is mentioned. The use of PowerShell and reference to PFX files (a Windows-centric format) further reinforces the bias. There are no Linux shell or cross-platform examples for certificate handling, and Windows tools/patterns are mentioned exclusively.
Recommendations
  • Add Linux and cross-platform examples for base64-encoding PFX files, such as using OpenSSL and base64 commands.
  • Mention alternative certificate formats and conversion tools available on Linux (e.g., PEM, OpenSSL).
  • Provide shell script snippets alongside PowerShell for common tasks (e.g., encoding certificates).
  • Clarify that the process can be performed on both Windows and Linux, and link to relevant cross-platform documentation.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-wait-activity.md ...in/articles/data-factory/control-flow-wait-activity.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 provides examples and walkthroughs primarily using Azure PowerShell, which is most commonly used on Windows. There is no mention of Linux command-line tools (such as Azure CLI or Bash), nor are there examples for Linux users. The tutorial link and sample commands focus on PowerShell, indicating a Windows-first approach and missing Linux parity.
Recommendations
  • Add equivalent examples using Azure CLI commands, which are cross-platform and commonly used on Linux and macOS.
  • Include step-by-step instructions for creating and running pipelines using Bash scripts or shell commands.
  • Explicitly mention that the Wait activity and pipeline orchestration are supported on all platforms, and provide links to Linux/macOS setup guides.
  • Balance references to PowerShell with references to CLI or other platform-agnostic tools in both examples and tutorial links.
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: 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 demonstrates a clear Windows bias by providing only PowerShell command examples for pipeline deployment and monitoring, referencing Windows file paths (e.g., C:\ADF), and omitting equivalent Linux/bash instructions. There is no mention of cross-platform tools or alternative CLI methods, and the use of Azure PowerShell is emphasized throughout, with no parity for Linux users.
Recommendations
  • Add equivalent Azure CLI (az) examples for pipeline creation, deployment, and monitoring, which work on both Windows and Linux.
  • Provide bash script examples and use cross-platform file paths (e.g., ~/ADF or /home/user/ADF) alongside Windows paths.
  • Explicitly mention that the JSON definitions and pipeline operations can be performed on Linux/macOS, not just Windows.
  • Include a note or section on cross-platform compatibility, listing both PowerShell and bash/CLI approaches.
  • Avoid using Windows-specific terminology or tools exclusively; present alternatives in parallel where possible.
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: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell script examples for programmatically finding impacted objects, which is a Windows-centric tool. There are no equivalent examples or guidance for Linux or cross-platform users (e.g., Bash, Azure CLI, Python). This may disadvantage users who operate in Linux environments or prefer non-Windows tooling.
Recommendations
  • Add equivalent Bash and/or Azure CLI examples for programmatically finding impacted objects.
  • Provide Python script samples, which are cross-platform and commonly used in automation.
  • Explicitly mention that the PowerShell scripts can be run on PowerShell Core on Linux/macOS, if applicable, and provide instructions for doing so.
  • Ensure future documentation includes both Windows and Linux approaches for all automation tasks.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-deploy-packages.md ...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-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 Windows bias by exclusively referencing Windows-based tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and running SSIS packages. There are no examples or guidance for Linux users, nor are cross-platform alternatives mentioned. Windows authentication and PowerShell are referenced in related content, further reinforcing the bias.
Recommendations
  • Provide explicit guidance or examples for deploying and running SSIS packages from Linux environments, if supported.
  • Mention cross-platform alternatives to SSDT, SSMS, dtutil, and AzureDTExec, or clarify their platform limitations.
  • Include CLI or REST API examples that can be executed from any OS.
  • Reorder sections or examples so that platform-neutral or cross-platform methods are presented before Windows-specific tools.
  • Clearly state any platform requirements or limitations for each tool or method.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery.md ...ticles/data-factory/continuous-integration-delivery.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 Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias, particularly in its reliance on PowerShell scripts for pre- and post-deployment tasks. It exclusively recommends PowerShell (and PowerShell Core) for automation, provides only PowerShell script examples, and does not mention or provide alternatives for Linux or cross-platform shell environments (such as Bash or CLI). The guidance assumes familiarity with Windows-centric tools and patterns, with no parity for Linux users.
Recommendations
  • Provide equivalent Bash or Azure CLI script examples for pre- and post-deployment tasks, alongside PowerShell.
  • Explicitly state that PowerShell Core is cross-platform, but also offer native Linux shell alternatives where possible.
  • Include guidance on running deployment automation from Linux/macOS environments, not just Windows.
  • Mention and link to Azure CLI documentation for relevant tasks, not just PowerShell.
  • Review all examples and recommendations to ensure Linux users are not excluded or forced to use Windows tools.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-integration-runtime.md ...icles/data-factory/create-azure-integration-runtime.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 demonstrates a Windows bias by exclusively providing Azure PowerShell examples for creating Azure Integration Runtime, with no mention of Linux CLI alternatives (such as Azure CLI or Bash). The only command-line procedure uses PowerShell, a Windows-centric tool, and does not offer parity for Linux or cross-platform users. There is no reference to Linux-specific tools or instructions, and the UI instructions are platform-neutral but do not address command-line needs for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI examples for creating and configuring Azure Integration Runtime, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that PowerShell is available on Linux and macOS, or provide installation guidance for non-Windows users if PowerShell is required.
  • Where possible, present both PowerShell and Azure CLI examples side-by-side to ensure parity and inclusivity for users on all platforms.
  • Include a short section or note addressing command-line options for Linux/macOS users, and link to relevant documentation for Azure CLI usage.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-factory-service-identity.md ...articles/data-factory/data-factory-service-identity.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 demonstrates a Windows bias by providing PowerShell-based examples for generating and retrieving managed identities, referencing Windows-specific command-line conventions (e.g., 'PS C:\>'), and omitting equivalent Linux/bash/CLI examples. PowerShell is presented as the primary or sole scripting tool, and there is no mention of Azure CLI or bash alternatives, which are more common on Linux and cross-platform environments. This may hinder Linux users or those working in non-Windows environments from easily following the instructions.
Recommendations
  • Add Azure CLI/bash examples alongside PowerShell for all operations (e.g., creating, updating, retrieving managed identities).
  • Present cross-platform tools (Azure CLI) before or alongside Windows-specific tools (PowerShell) to avoid Windows-first bias.
  • Explicitly mention that instructions apply to both Windows and Linux, and clarify any platform-specific differences.
  • Include screenshots or terminal output from Linux environments where relevant.
  • Review all code samples and ensure Linux parity by providing equivalent commands and usage patterns.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-portal.md ...actory/create-azure-ssis-integration-runtime-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and patterns, such as SSMS (SQL Server Management Studio), UNC paths, and PowerShell, without providing Linux equivalents or alternatives. Windows authentication and file system examples are mentioned, but there is no guidance for Linux users (e.g., using Azure CLI, Linux file paths, or Linux-compatible management tools). The related content also highlights PowerShell and Windows authentication, reinforcing the Windows-first approach.
Recommendations
  • Add examples and instructions for Linux users, such as using Azure CLI for provisioning and configuration.
  • Include guidance for managing SSIS packages and integration runtimes from Linux environments, e.g., using cross-platform tools or REST APIs.
  • Provide alternatives to SSMS for package management, such as Azure Data Studio or other cross-platform tools.
  • Clarify authentication and file system options for Linux, including how to connect to Azure Files or MSDB from non-Windows systems.
  • Balance references to PowerShell with Azure CLI or Bash examples, and mention these alternatives in related content.
  • Explicitly note any platform limitations and provide workarounds or links to Linux-specific documentation where applicable.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-self-hosted-integration-runtime.md ...data-factory/create-self-hosted-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools Windows Only
Summary
The documentation page exhibits a strong Windows bias. All installation instructions, prerequisites, and examples are exclusively for Windows environments. PowerShell is the only CLI tool shown for automation, and Windows-specific tools (such as registry edits, NT SERVICE accounts, and Windows Firewall) are referenced throughout. There is no mention of Linux support, nor are there any Linux-specific instructions, examples, or troubleshooting steps. The use of Windows Data Protection API (DPAPI) for credential encryption further reinforces the Windows-centric approach.
Recommendations
  • Explicitly state whether Linux is supported or not. If Linux is supported, provide parity in installation, configuration, and troubleshooting instructions for Linux environments.
  • Include Linux-based examples for installation, such as using shell scripts, systemd services, and Linux firewall configuration (e.g., iptables, firewalld, ufw).
  • Offer CLI automation examples using Bash or Azure CLI, not just PowerShell.
  • Document Linux-specific prerequisites (e.g., supported distributions, required libraries, .NET Core/Mono requirements if applicable).
  • Describe credential encryption and storage mechanisms for Linux, if different from DPAPI.
  • Reference Linux equivalents for service management (systemd, init.d) and account permissions.
  • If the self-hosted integration runtime is Windows-only, clarify this limitation early in the documentation and provide guidance for Linux users seeking alternatives.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-shared-self-hosted-integration-runtime-powershell.md ...eate-shared-self-hosted-integration-runtime-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 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based instructions and examples, referencing Windows-specific tools (PowerShell ISE), and omitting any Linux or cross-platform CLI alternatives. The installation instructions for the integration runtime do not clarify platform support or provide Linux-specific guidance, and all scripting is shown in PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Provide equivalent instructions using Azure CLI, which is cross-platform and commonly used on Linux and macOS.
  • Clarify whether the self-hosted integration runtime installer supports Linux and, if so, provide installation steps for Linux systems.
  • Include Bash or shell script examples for key steps, such as authentication, resource creation, and permission assignment.
  • Avoid referencing Windows-specific tools (e.g., PowerShell ISE) as the default; mention VS Code or other cross-platform editors.
  • Explicitly state platform compatibility for all tools and commands, and ensure parity in example coverage for Linux users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-migration-guidance-hdfs-azure-storage.md ...-factory/data-migration-guidance-hdfs-azure-storage.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by repeatedly specifying Windows as the required platform for installing the Data Factory self-hosted integration runtime, both on-premises and in Azure VMs. There are no examples or guidance for installing or running the integration runtime on Linux machines, nor is there mention of Linux-based alternatives. The pricing section also explicitly excludes the cost of Azure Windows VMs, reinforcing the assumption of Windows-only usage. No Linux-specific instructions, examples, or parity are provided.
Recommendations
  • Explicitly state whether the Data Factory self-hosted integration runtime supports Linux, and if so, provide installation and configuration instructions for Linux environments.
  • Include examples and architecture diagrams that show deployment on Linux VMs, both on-premises and in Azure.
  • If Linux is not supported, clarify this limitation early in the documentation and provide rationale or roadmap information.
  • In pricing and best practices sections, mention Linux VM options and compare their cost/performance to Windows VMs.
  • Ensure authentication and credential management guidance covers Linux-specific scenarios (e.g., Kerberos on Linux, service principals, etc.).
  • Add troubleshooting and operational guidance for Linux environments, if supported.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-movement-security-considerations.md .../data-factory/data-movement-security-considerations.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 demonstrates a Windows bias in several areas: it provides PowerShell cmdlet examples (Set-AzDataFactoryV2LinkedService, New-AzDataFactoryV2LinkedServiceEncryptedCredential) without Linux or cross-platform CLI alternatives, references Windows-specific technologies like DPAPI for credential encryption, and discusses Windows Firewall in detail while omitting Linux firewall equivalents (e.g., iptables, firewalld). The documentation also assumes the use of Windows tools and patterns for self-hosted integration runtime setup and credential management, with no mention of Linux-based deployment or configuration steps.
Recommendations
  • Provide equivalent examples using Azure CLI and/or REST API for credential management and linked service setup, which are cross-platform.
  • Document Linux-compatible methods for encrypting and storing credentials locally, including alternatives to DPAPI (e.g., using GnuPG, OpenSSL, or Azure Key Vault integration on Linux).
  • Include Linux firewall configuration guidance (e.g., iptables, firewalld, ufw) alongside Windows Firewall instructions.
  • Clarify whether the self-hosted integration runtime can be installed and operated on Linux, and if so, provide setup and security instructions for Linux environments.
  • Ensure that all port and network configuration instructions are applicable to both Windows and Linux, or highlight differences where necessary.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/enable-customer-managed-key.md ...n/articles/data-factory/enable-customer-managed-key.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 a Windows bias by referencing PowerShell and Azure CLI as the primary methods for configuring Key Vault properties, without providing explicit Linux shell (bash) examples or clarifying cross-platform parity. The instructions and screenshots focus on the Azure portal UI, which is platform-agnostic, but command-line examples and tool references (e.g., PowerShell) are presented without Linux alternatives. There is no mention of Linux-specific tools or patterns, and the order of presentation puts Windows-centric tools first.
Recommendations
  • Add explicit bash/Azure CLI examples for all command-line instructions, ensuring Linux users have clear guidance.
  • When referencing PowerShell, also provide equivalent bash commands, and clarify which commands are cross-platform.
  • Include notes or sections highlighting Linux compatibility and any platform-specific considerations.
  • Avoid using 'PowerShell or Azure CLI' as a combined option; instead, list both separately and provide examples for each.
  • Review screenshots and UI instructions to ensure terminology is neutral and not Windows-centric.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-factory-troubleshoot-guide.md ...ticles/data-factory/data-factory-troubleshoot-guide.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 Tools Windows First
Summary
The documentation demonstrates a Windows bias in several areas. Powershell is used exclusively in example commands for Azure Batch custom activities (e.g., for unzipping files), and Windows-specific tools and patterns (such as Fiddler and Windows zip behavior) are referenced without Linux alternatives. Troubleshooting steps and examples often mention or prioritize Windows tools and workflows, with no equivalent Linux commands or guidance provided.
Recommendations
  • Provide Linux shell (bash) equivalents for Powershell commands, especially for tasks like unzipping files in Azure Batch custom activities.
  • Include troubleshooting steps using Linux-native tools (e.g., tcpdump, curl, wget) alongside Windows tools like Fiddler.
  • When referencing Windows-specific behaviors (such as zip compression algorithms), clarify how Linux systems behave and offer guidance for Linux users.
  • Ensure that examples and instructions are presented in a cross-platform manner, with both Windows and Linux options given equal prominence.
  • Review all code snippets and tool recommendations to add Linux alternatives where missing.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/enable-aad-authentication-azure-ssis-ir.md ...ata-factory/enable-aad-authentication-azure-ssis-ir.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 Missing Linux Example Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or cross-platform alternatives. The use of SSMS (SQL Server Management Studio), a Windows-only tool, is required for several steps, and no Linux-compatible tools (such as Azure Data Studio or sqlcmd) are referenced. The documentation assumes the reader is using Windows environments and tools, and does not provide guidance for users on Linux or macOS platforms.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts alongside PowerShell commands.
  • Reference and provide instructions for using cross-platform tools such as Azure Data Studio and sqlcmd for database operations, in addition to SSMS.
  • Explicitly mention platform compatibility for each tool and step, and offer alternatives for Linux/macOS users.
  • Reorder sections or examples to present cross-platform solutions first, or in parallel with Windows-specific instructions.
  • Add notes or links to official documentation on how to perform these operations from Linux/macOS environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-create-tumbling-window-trigger.md .../data-factory/how-to-create-tumbling-window-trigger.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 Tools Windows First
Summary
The documentation page exhibits Windows bias primarily in the command-line examples section. The Azure PowerShell instructions are presented first and include explicit references to Windows-specific paths (e.g., C:\ADFv2QuickStartPSH\), and the PowerShell installation instructions link only to Windows installation. There is no mention of Linux or macOS alternatives for PowerShell, nor are there any Bash or shell script examples. The CLI section is more cross-platform, but the overall emphasis and ordering favor Windows and PowerShell. No Linux-specific tools, patterns, or examples are provided.
Recommendations
  • Add explicit instructions and examples for using Azure PowerShell on Linux and macOS, including installation links for those platforms.
  • Include Bash or shell script equivalents for file creation and command execution, especially for the JSON file creation and trigger management steps.
  • Avoid using Windows-specific file paths (e.g., C:\...) in examples; use generic or cross-platform paths (e.g., ./ADFv2QuickStart/).
  • Consider presenting Azure CLI examples before PowerShell, as CLI is natively cross-platform.
  • Add a note clarifying that both Azure PowerShell and Azure CLI are available on Windows, Linux, and macOS, and provide links to installation instructions for all platforms.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/encrypt-credentials-self-hosted-integration-runtime.md ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/encrypt-credentials-self-hosted-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses PowerShell cmdlets (New-AzDataFactoryV2LinkedServiceEncryptedCredential, Set-AzDataFactoryV2LinkedService) for credential encryption and management, which are Windows-centric. There is no mention of Linux-compatible alternatives, nor are Bash or cross-platform CLI examples provided. The prerequisites explicitly require PowerShell 7.0+, reinforcing a Windows-first approach and omitting guidance for Linux users.
Recommendations
  • Provide equivalent instructions using Azure CLI or REST API, which are cross-platform.
  • Clarify whether the credential encryption process can be performed on Linux or macOS, and document any limitations.
  • If PowerShell is required, note that PowerShell Core is available on Linux and macOS, and provide installation and usage guidance for those platforms.
  • Add Linux-specific examples or troubleshooting steps for common issues encountered on non-Windows systems.
  • Explicitly state platform requirements and alternatives for users who do not have access to Windows environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-configure-azure-ssis-ir-enterprise-edition.md ...y/how-to-configure-azure-ssis-ir-enterprise-edition.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 Windows bias by exclusively providing Azure PowerShell instructions and examples for provisioning the Enterprise Edition of Azure-SSIS Integration Runtime. There are no Linux or cross-platform CLI examples (such as Azure CLI or Bash), and Windows authentication patterns are referenced without alternatives for non-Windows environments.
Recommendations
  • Add equivalent Azure CLI instructions and examples for provisioning and managing Azure-SSIS IR, suitable for Linux/macOS users.
  • Reference cross-platform authentication methods (such as service principals or managed identities) alongside Windows Authentication.
  • Explicitly mention platform requirements and provide guidance for users on Linux/macOS, including any limitations or alternatives.
  • Ensure that all tooling instructions (installation, usage) are available for both Windows and Linux environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-create-schedule-trigger.md ...rticles/data-factory/how-to-create-schedule-trigger.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 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments. The Azure PowerShell section is presented before the Azure CLI, and PowerShell is described with explicit Windows installation instructions and Windows-style file paths (e.g., C:\ADFv2QuickStartPSH\). There are no Linux-specific instructions, examples, or notes for PowerShell or CLI usage, nor any mention of Linux shell equivalents or cross-platform considerations. The documentation assumes a Windows environment for scripting and tooling, and omits guidance for Linux users.
Recommendations
  • Add explicit Linux instructions for Azure PowerShell installation and usage, including Linux-compatible file paths and shell commands.
  • Include cross-platform notes for both PowerShell and CLI sections, clarifying usage on Linux, macOS, and Windows.
  • Present Azure CLI examples before or alongside PowerShell, as CLI is natively cross-platform.
  • Provide sample commands using Linux shell syntax (e.g., bash), and clarify any differences in file path handling.
  • Mention that JSON files and scripts can be created and used on Linux/macOS, not just Windows.
  • Add troubleshooting notes for common Linux issues (e.g., file permissions, path separators) when working with triggers.
  • Ensure screenshots and UI references do not assume a Windows look-and-feel exclusively.
GitHub Create Pull Request
← Previous Page 18 of 40 Next →