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 801-825 of 1000 flagged pages
Data Factory Pipelines and activities ...articles/data-factory/concepts-pipelines-activities.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
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 primarily through its use of PowerShell-based walkthroughs and examples. All 'complete walkthrough' links for creating and transforming pipelines point to PowerShell tutorials, with no mention of Linux/macOS CLI, Bash, or cross-platform alternatives. The 'Related content' section also exclusively references PowerShell-based guides. There are no Linux/macOS-specific instructions or examples, nor is there any mention of Azure CLI, REST API, or other platform-neutral tools. This may create friction for users on non-Windows platforms.
Recommendations
  • Add equivalent walkthroughs and quickstarts using Azure CLI and Bash scripts, which are cross-platform.
  • Include references to REST API documentation for pipeline creation and management.
  • Explicitly mention that pipelines and activities can be managed from Linux/macOS using Azure CLI or REST API.
  • In 'Related content', link to non-Windows guides and tutorials.
  • When referencing code samples or automation, provide both PowerShell and Bash/Azure CLI examples.
GitHub Create Pull Request
Data Factory Configure performance for the Azure-SSIS Integration Runtime ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/configure-azure-ssis-integration-runtime-performance.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively provides PowerShell-based configuration examples and references, with no mention of Linux/macOS alternatives or cross-platform tools. All scripting and automation guidance is centered on PowerShell, which is natively available only on Windows (though PowerShell Core is cross-platform, this is not clarified). There are no Bash, CLI, or ARM template examples, and no guidance for Linux/macOS users.
Recommendations
  • Add equivalent Azure CLI and/or Bash examples for all configuration steps, especially for creating and managing Azure-SSIS IR.
  • Clarify whether PowerShell scripts are compatible with PowerShell Core on Linux/macOS, and provide installation guidance if so.
  • Reference cross-platform tools (e.g., Azure CLI, ARM templates) alongside PowerShell, and ensure documentation parity for Linux/macOS users.
  • Consider reordering or parallelizing examples so that Windows and Linux/macOS approaches are presented together.
GitHub Create Pull Request
Data Factory Linked services ...main/articles/data-factory/concepts-linked-services.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is listed as a primary method for creating linked services, and Windows-centric tools (PowerShell, .NET) are mentioned before cross-platform or Linux-native equivalents. There are no explicit Linux or macOS command-line examples (e.g., Bash, Azure CLI), nor are Linux-specific patterns or tools referenced. This may create friction for users on Linux/macOS who do not use PowerShell or .NET.
Recommendations
  • Add Azure CLI examples for creating linked services, as CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention Linux/macOS compatibility for all SDKs and tools, and provide links to relevant documentation.
  • Include Bash shell examples or scripts where appropriate.
  • Reorder tool/SDK lists to start with cross-platform options (e.g., REST API, Azure CLI) before Windows-centric ones.
  • Add a section or note clarifying how Linux/macOS users can perform equivalent tasks.
GitHub Create Pull Request
Data Factory Pipeline execution and triggers ...s/data-factory/concepts-pipeline-execution-triggers.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page provides examples for running Azure Data Factory pipelines using .NET SDK, Azure PowerShell, REST API, and Python SDK. However, the PowerShell example is the only command-line example shown, and it is presented before REST API and Python SDK. There is no mention of Bash, Azure CLI, or Linux-native tools, and no Linux/macOS-specific guidance is provided. The use of PowerShell and references to parameter files with Windows-style paths (e.g., .\PipelineParameters.json) further reinforce a Windows-centric approach.
Recommendations
  • Add Azure CLI examples for pipeline execution, which are cross-platform and widely used on Linux/macOS.
  • Include Bash/cURL examples for REST API usage, demonstrating how Linux/macOS users can trigger pipelines from the command line.
  • Present examples in a neutral order (e.g., REST API, Azure CLI, PowerShell, SDKs) rather than Windows-first.
  • Use platform-agnostic file paths in examples (e.g., ./PipelineParameters.json instead of .\PipelineParameters.json).
  • Explicitly mention that all SDKs and REST API methods are usable from Linux/macOS environments.
GitHub Create Pull Request
Data Factory Configure Azure-SSIS integration runtime for business continuity and disaster recovery (BCDR) ...ctory/configure-bcdr-azure-ssis-integration-runtime.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation demonstrates a moderate Windows bias. While most configuration steps are performed via the Azure portal or ADF UI (which are cross-platform), there are several references to Windows-centric tools and workflows, such as SQL Server Management Studio (SSMS) and PowerShell. SSMS is a Windows-only application, and PowerShell examples are referenced without Linux/macOS alternatives. Additionally, scripting and job management instructions are given using SSMS, with no mention of cross-platform SQL tools or alternatives. The documentation also lists PowerShell as the devlang and provides links to PowerShell-specific guides before any Linux/macOS equivalents.
Recommendations
  • Provide equivalent instructions using cross-platform SQL tools such as Azure Data Studio or sqlcmd, especially for scripting jobs and running T-SQL commands.
  • Include examples for Azure CLI where PowerShell is referenced, as Azure CLI is cross-platform.
  • Clarify that the Azure portal and ADF UI are accessible from any OS, and highlight any steps that require Windows-only tools.
  • Add notes or links for Linux/macOS users on how to perform SSMS-related steps using alternative tools.
  • Reorder examples to present cross-platform or OS-neutral options first, before Windows-specific tools.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides a PowerShell-only example for generating a service shared access signature (SAS) for Azure Table Storage, without mentioning or providing equivalent commands for Linux/macOS users (such as Azure CLI or REST API). This creates friction for non-Windows users who may not have access to PowerShell or prefer platform-agnostic tools. The rest of the documentation is generally platform-neutral, focusing on JSON configuration and Azure portal UI, but the authentication section is notably Windows-biased.
Recommendations
  • Add Azure CLI examples for generating SAS tokens alongside PowerShell commands.
  • Reference REST API methods for SAS generation for cross-platform usage.
  • Explicitly mention that PowerShell is Windows-centric and provide alternatives for Linux/macOS users.
  • Ensure all command-line instructions are available for both Windows and Linux/macOS environments.
GitHub Create Pull Request
Data Factory Copy and transform data to and from SQL Server ...lob/main/articles/data-factory/connector-sql-server.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
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 notable Windows bias. Windows authentication is described in detail and given equal prominence to SQL authentication, despite being unsupported in data flows and less relevant for Linux environments. Troubleshooting and configuration instructions are exclusively Windows-centric, referencing Windows-only tools (SQL Server Management Studio, SQL Server Configuration Manager, Windows Firewall) and providing no Linux/macOS equivalents or guidance. All screenshots and step-by-step instructions assume a Windows environment. There are no examples or instructions for connecting to SQL Server from Linux or macOS, nor any mention of Linux authentication patterns (e.g., Kerberos, integrated security via GSSAPI).
Recommendations
  • Add equivalent instructions for configuring SQL Server remote access and network protocols on Linux (e.g., using sqlservr.conf, systemctl, firewalld/iptables).
  • Include troubleshooting steps for Linux-based SQL Server installations, such as verifying TCP/IP settings and opening firewall ports.
  • Clarify that Windows authentication is not available on Linux/macOS and provide alternative authentication guidance for those platforms.
  • Add examples or references for connecting to SQL Server from Linux/macOS clients (e.g., using sqlcmd, Azure Data Studio, or ODBC with Kerberos).
  • Balance screenshots and UI walkthroughs with cross-platform tools where possible, or note platform limitations.
  • Explicitly state platform requirements and limitations for features that are Windows-only.
GitHub Create Pull Request
Data Factory Copy data from Amazon RDS for SQL Server ...es/data-factory/connector-amazon-rds-for-sql-server.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
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 notable Windows bias. Windows authentication is mentioned as a primary option alongside SQL authentication, with examples and property tables. Troubleshooting steps and configuration instructions reference Windows-specific tools such as SQL Server Management Studio, SQL Server Configuration Manager, and Windows Firewall, with no mention of Linux equivalents or cross-platform alternatives. All example code and UI screenshots are platform-neutral, but operational instructions (e.g., enabling remote connections, configuring network protocols, firewall rules) are exclusively Windows-focused. There are no instructions for Linux-based Amazon RDS for SQL Server management, nor are Linux authentication or tooling options discussed.
Recommendations
  • Add equivalent instructions for Linux environments, such as using sqlcmd, Azure Data Studio, or other cross-platform tools for managing SQL Server.
  • Include troubleshooting steps for configuring Amazon RDS for SQL Server connectivity from Linux hosts, such as adjusting firewalls (e.g., iptables, ufw) and network settings.
  • Clarify authentication options for Linux users, including Kerberos or other supported mechanisms if available.
  • Provide examples or links for managing SQL Server on Linux, if supported, or explicitly state platform limitations.
  • Where Windows-specific tools are referenced, add notes or alternatives for macOS/Linux users.
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 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation shows a moderate Windows bias. Windows file share patterns (UNC paths, backslash escaping) are presented first and most examples use Windows-style paths. The only explicit mention of Linux is a brief note about installing Samba, with no Linux-specific examples or UI screenshots. Instructions for enabling local machine access reference PowerShell commands, with no Linux CLI alternatives. Windows terminology and conventions dominate, and Linux/macOS users must infer how to adapt instructions.
Recommendations
  • Provide Linux/macOS-specific examples alongside Windows examples, including path formats (e.g., /mnt/share or smb://host/share).
  • Include screenshots or UI instructions for connecting to Linux file shares.
  • Offer Linux CLI commands (e.g., for mounting SMB shares, configuring permissions) in addition to PowerShell.
  • Clarify differences in authentication and file sharing between Windows and Linux environments.
  • Explicitly document any limitations or required steps for Linux/macOS users (e.g., Samba configuration, SELinux considerations).
GitHub Create Pull Request
Data Factory Copy and transform data from Microsoft 365 (Office 365) ...lob/main/articles/data-factory/connector-office-365.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
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, particularly in the section about converting certificates to base64, where only a PowerShell/Windows-based method is referenced. The linked article for certificate conversion is Windows/PowerShell-specific, and there are no equivalent instructions or references for Linux/macOS users. Additionally, the template for certificate conversion is likely tailored for Windows environments. While the main pipeline and JSON configuration content is cross-platform, the lack of Linux/macOS guidance for certificate handling creates friction for non-Windows users.
Recommendations
  • Provide Linux/macOS command-line examples for converting certificates to base64 (e.g., using openssl and base64 commands).
  • Include links to official documentation or community articles for certificate management on Linux/macOS.
  • Clarify in the documentation that the certificate conversion process can be performed on any OS, and provide OS-agnostic instructions where possible.
  • If templates or scripts are provided, ensure they are cross-platform or offer alternatives for Linux/macOS users.
GitHub Create Pull Request
Data Factory Copy and transform data in Dynamics 365 (Microsoft Dataverse) or Dynamics CRM ...cles/data-factory/connector-dynamics-crm-office-365.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It references 'Dynamics XRM tooling' (which is primarily a Windows/.NET SDK), and the authentication and configuration examples assume Azure portal and Microsoft Entra ID workflows, which are platform-agnostic but often more familiar to Windows users. There is no mention of Linux/macOS-specific tooling, nor are there any examples or guidance for command-line or automation scenarios outside the Azure portal UI. The documentation does not provide parity for Linux/macOS users in terms of alternative tools or workflows, and the underlying SDK referenced is Windows-centric.
Recommendations
  • Explicitly mention whether all features and SDKs (such as Dynamics XRM tooling) are supported on Linux/macOS, and provide links to cross-platform alternatives if available.
  • Add examples for creating and configuring linked services using Azure CLI, PowerShell, and REST API, with notes on platform compatibility.
  • Clarify whether the connector and its authentication flows (especially certificate/key handling) work seamlessly on Linux/macOS self-hosted integration runtimes.
  • If any features are Windows-only, call this out and suggest workarounds for Linux/macOS users.
  • Provide troubleshooting tips for Linux/macOS environments, especially for self-hosted integration runtime setup and connectivity.
GitHub Create Pull Request
Data Factory Copy data from an HTTP source ...docs/blob/main/articles/data-factory/connector-http.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias in its recommendations and instructions. In the 'TIP' section, it suggests using Visual Studio and PowerShell's Invoke-RestMethod to test HTTP requests, both of which are Windows-centric tools, without mentioning equivalent Linux/macOS tools (such as curl or wget). Additionally, the instructions for managing certificate permissions for ClientCertificate authentication are exclusively written for Windows (using MMC and Windows certificate stores), with no mention of how to perform similar tasks on Linux or macOS self-hosted integration runtime environments.
Recommendations
  • In the 'TIP' section, add Linux/macOS-friendly tools such as curl and wget as alternatives for testing HTTP requests.
  • For certificate management, provide instructions or references for installing and managing certificates on Linux and macOS self-hosted integration runtime hosts (e.g., using openssl, keytool, or system-specific certificate stores).
  • Where authentication examples reference Windows-specific mechanisms, clarify cross-platform support and provide guidance for non-Windows environments.
  • Ensure that any UI or tool recommendations are platform-neutral or include alternatives for all major operating systems.
GitHub Create Pull Request
Data Factory Copy data from SAP BW ...icles/data-factory/connector-sap-business-warehouse.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in the troubleshooting and prerequisites sections, where instructions reference placing SAP NetWeaver RFC SDK libraries in the %windir%\system32 folder—a Windows-specific location. No equivalent guidance is provided for Linux or macOS users, nor are there examples or troubleshooting steps for those platforms. The rest of the documentation is platform-neutral, focusing on Azure portal and JSON configuration.
Recommendations
  • Add explicit instructions for installing SAP NetWeaver RFC SDK libraries on Linux and macOS, including typical library paths (e.g., /usr/lib, /usr/local/lib) and environment variable setup.
  • Provide troubleshooting tips for connectivity issues on Linux/macOS, such as checking LD_LIBRARY_PATH and permissions.
  • Clarify that Self-hosted Integration Runtime is available for both Windows and Linux, and link to platform-specific installation guides.
  • Include example screenshots or commands for Linux/macOS where relevant.
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-13 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 Dynamics connectivity and data issues. No Linux/macOS alternatives or cross-platform CLI options are mentioned. There are no OS-specific command examples, but the exclusive mention of XrmToolBox creates friction for non-Windows users.
Recommendations
  • Include cross-platform alternatives to XrmToolBox, such as PowerShell modules that work on Linux/macOS, or REST API/CLI instructions for testing FetchXML and record counts.
  • Explicitly state platform requirements for XrmToolBox and suggest Docker or VM workarounds if no alternatives exist.
  • Add troubleshooting steps that can be performed using browser-based tools or Azure Portal, which are OS-agnostic.
  • Provide links to open-source or web-based Dynamics tools usable on Linux/macOS.
GitHub Create Pull Request
Data Factory Troubleshoot the SAP Table, SAP Business Warehouse Open Hub, and SAP ODP connectors ...in/articles/data-factory/connector-troubleshoot-sap.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a troubleshooting step using a PowerShell command (Test-NetConnection), which is only available on Windows. No equivalent Linux/macOS command or guidance is provided, making the instructions Windows-centric and potentially confusing or unusable for users on other platforms.
Recommendations
  • Add equivalent Linux/macOS troubleshooting commands (e.g., 'nc', 'telnet', or 'curl') for testing SAP server connectivity.
  • Explicitly state platform requirements or alternatives for each troubleshooting step.
  • Consider providing cross-platform scripts or guidance to ensure all users can follow the troubleshooting process.
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-13 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 section describing installation of the Vertica ODBC driver for version 2.0. All installation steps and screenshots use Windows as the example, referencing .exe installers and Windows-specific tools (ODBC Data Source Administrator, Start menu). There are no instructions or examples for Linux or macOS users, nor any mention of platform-specific differences or alternative installation methods.
Recommendations
  • Add explicit installation instructions for Linux (and optionally macOS), including commands for extracting and installing the Vertica ODBC driver on those platforms.
  • Provide screenshots or terminal output examples for Linux/macOS environments.
  • Mention platform-specific tools (e.g., unixODBC for Linux) and how to configure ODBC data sources outside of Windows.
  • Clarify any differences in driver download packages or setup steps for non-Windows systems.
  • Ensure parity in troubleshooting and verification steps (e.g., how to confirm ODBC installation on Linux).
GitHub Create Pull Request
Data Factory Troubleshoot the file system connector ...les/data-factory/connector-troubleshoot-file-system.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides troubleshooting steps for the file system connector in Azure Data Factory and Azure Synapse, but exclusively references PowerShell and Windows-centric tooling for configuration (specifically, setting up Self-hosted Integration Runtime via local PowerShell). There are no Linux or macOS equivalent instructions or examples, and Windows tools are mentioned first and exclusively.
Recommendations
  • Add equivalent instructions for configuring Self-hosted Integration Runtime access using Linux/macOS command line tools (e.g., Bash, shell scripts).
  • Reference cross-platform tools or clarify if the feature is Windows-only.
  • Explicitly state platform limitations if Linux/macOS are unsupported for this configuration.
  • Provide parity in troubleshooting examples for both Windows and Linux/macOS environments.
GitHub Create Pull Request
Data Factory Troubleshoot connectors .../articles/data-factory/connector-troubleshoot-guide.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits Windows bias primarily in the FIPS troubleshooting section, which exclusively references Windows file paths and configuration steps (e.g., editing diawp.exe.config in C:\Program Files). No equivalent instructions or notes are provided for Linux or macOS users running Self-hosted Integration Runtime (IR). Additionally, Windows terminology and tools are mentioned first and exclusively in this critical troubleshooting scenario.
Recommendations
  • Add explicit instructions for Linux/macOS environments where Self-hosted IR is supported, including file paths and configuration steps.
  • Clarify whether FIPS-related troubleshooting applies only to Windows, or provide Linux/macOS alternatives if relevant.
  • Where file paths or configuration files are referenced, include both Windows and Linux/macOS examples side-by-side.
  • Add a note at the beginning of the FIPS section specifying OS applicability.
  • Review other troubleshooting steps to ensure parity in examples and instructions for non-Windows platforms.
GitHub Create Pull Request
Data Factory Connector upgrade guidance ...in/articles/data-factory/connector-upgrade-guidance.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides programmatic guidance exclusively using PowerShell scripts, which are native to Windows. There are no examples or mentions of equivalent Linux/macOS tools (such as Azure CLI, Bash, or Python scripts), nor are cross-platform alternatives suggested. This creates friction for users on Linux or macOS who may not have access to PowerShell or prefer native tools.
Recommendations
  • Provide equivalent examples using Azure CLI, Bash, or Python scripts for Linux/macOS users.
  • Explicitly mention cross-platform options and clarify PowerShell availability on non-Windows platforms.
  • Include links or references to documentation for running PowerShell Core on Linux/macOS, if PowerShell is required.
  • Order examples so that cross-platform solutions are presented first or alongside Windows-specific ones.
GitHub Create Pull Request
Data Factory Continuous integration and delivery pre- and post-deployment scripts ...ctory/continuous-integration-delivery-sample-script.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows and PowerShell, with all examples using Azure PowerShell tasks and .ps1 scripts. There are no references to Bash, Linux shell, or cross-platform alternatives, and no Linux/macOS-specific instructions or examples are provided. The use of PowerShell is assumed throughout, and Windows-centric tools and patterns are presented exclusively and first.
Recommendations
  • Provide equivalent examples using Bash or Azure CLI for Linux/macOS users.
  • Clarify whether the PowerShell scripts are compatible with PowerShell Core on Linux/macOS, and provide instructions for running them in those environments.
  • Include YAML pipeline examples using Bash tasks or AzureCLI@2 tasks.
  • Add notes or sections explicitly addressing Linux/macOS usage and any required modifications.
  • List cross-platform options before or alongside Windows/PowerShell instructions.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page provides only PowerShell commands and Windows-centric file paths (e.g., C:\ADF) for pipeline deployment and execution, with no mention of Linux/macOS equivalents such as Azure CLI or Bash. The tutorial and examples assume a Windows environment and do not offer guidance for users on other platforms.
Recommendations
  • Add equivalent Azure CLI and Bash examples for pipeline deployment and execution.
  • Use platform-neutral file paths in examples (e.g., /home/user/ADF or ./ADF).
  • Explicitly mention cross-platform options and tools at the start of the tutorial.
  • Provide links or references to Linux/macOS setup guides for Azure Data Factory.
  • Ensure that step-by-step instructions are available for both Windows and Linux/macOS users.
GitHub Create Pull Request
Data Factory Automate continuous integration ...ntinuous-integration-delivery-automate-azure-pipelines.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, primarily through exclusive use of PowerShell for automation tasks (e.g., stopping and starting triggers), references to .ps1 scripts, and instructions to install Azure PowerShell modules. There are no examples or guidance for Linux/macOS users, such as using Bash, Azure CLI, or cross-platform scripting. The documentation assumes the user is familiar with Windows-centric tools and patterns, and does not mention alternatives or parity for non-Windows platforms.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for stopping/starting triggers and other automation tasks.
  • Clarify whether all tasks (e.g., ARM Template Deployment, Key Vault access) can be performed using cross-platform agents and tools, and document any platform-specific limitations.
  • Explicitly mention support for Linux/macOS agents in Azure Pipelines and link to relevant setup guides.
  • Add notes or sections for Linux/macOS users, including installation instructions for required tools (e.g., Azure CLI) and alternative scripting approaches.
  • Ensure sample scripts are available in both PowerShell and Bash/CLI formats.
GitHub Create Pull Request
Data Factory Continuous integration and delivery ...ticles/data-factory/continuous-integration-delivery.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a notable Windows bias, especially in the CI/CD best practices section. PowerShell scripts are recommended for pre- and post-deployment steps, with explicit references to .ps1 scripts and instructions to use PowerShell Core in Azure DevOps tasks. There are no examples or guidance for Linux/macOS users, such as using Bash, Azure CLI, or cross-platform scripting alternatives. The documentation assumes familiarity with Windows tooling and does not mention Linux equivalents or alternatives.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for pre- and post-deployment tasks, or clarify how Linux/macOS users can perform these steps.
  • Explicitly state that PowerShell Core is cross-platform, and provide installation and usage guidance for Linux/macOS environments.
  • Include examples or links for running deployment automation from Linux/macOS agents in Azure Pipelines.
  • Mention alternative scripting options (e.g., Python, Bash) where appropriate, and clarify any limitations.
  • Ensure that all critical automation steps can be completed from non-Windows environments.
GitHub Create Pull Request
Data Factory Switch activity in Azure Data Factory .../articles/data-factory/control-flow-switch-activity.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation provides only PowerShell command examples for pipeline deployment and execution, assumes Windows file paths (e.g., C:\ADF), and references a tutorial focused on Azure PowerShell. There are no CLI, Bash, or cross-platform instructions, nor are Linux/macOS equivalents mentioned or linked. This creates friction for non-Windows users who may prefer or require Azure CLI or REST API approaches.
Recommendations
  • Add Azure CLI examples for pipeline deployment and execution, including Linux/macOS shell commands.
  • Use platform-neutral file paths in examples or clarify how to adapt them for Linux/macOS (e.g., /home/user/ADF).
  • Reference tutorials or quickstarts for Azure CLI and REST API usage.
  • Explicitly state that the PowerShell approach is one of several options, and link to cross-platform alternatives.
  • Include notes or sections for Linux/macOS users on prerequisites and environment setup.
GitHub Create Pull Request
Data Factory Deploy SSIS packages ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-deploy-packages.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page references Windows-centric tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and running SSIS packages, without mentioning Linux/macOS alternatives or compatibility. There are no examples or guidance for Linux users, and Windows tools are presented as the default or only option.
Recommendations
  • Clarify whether SSDT, SSMS, dtutil, and AzureDTExec are available or supported on Linux/macOS, and provide installation or usage instructions for those platforms if possible.
  • If Linux/macOS support is not available for these tools, suggest alternative approaches (e.g., using Azure portal, REST APIs, or cross-platform command-line utilities) for deploying and running SSIS packages.
  • Include explicit examples or workflows for Linux/macOS users, or at least note platform limitations.
  • Reorder examples or tool mentions so that platform-neutral or cross-platform options are presented first.
GitHub Create Pull Request
← Previous Page 33 of 40 Next →