Data Factory

1123
Total Pages
968
Linux-Friendly Pages
155
Pages with Bias
13.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

319 issues found
Showing 301-319 of 319 flagged pages
Data Factory Encrypt Azure Data Factory with customer-managed key ...n/articles/data-factory/enable-customer-managed-key.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by referencing PowerShell and Azure CLI for enabling Key Vault properties, with PowerShell mentioned first. There are no explicit Linux/macOS command-line examples, nor are Linux-specific tools or shell commands provided. All screenshots and UI walkthroughs are based on the Azure portal, which is cross-platform, but command-line instructions lack parity for Linux users.
Recommendations
  • Provide explicit bash/Azure CLI examples for Linux/macOS users alongside PowerShell commands.
  • When listing command-line options, alternate the order or present Linux/macOS and Windows examples together.
  • Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux/macOS (bash).
  • Include notes or links to platform-specific documentation where relevant.
GitHub Create Pull Request
Data Factory Create schedule triggers ...rticles/data-factory/how-to-create-schedule-trigger.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page exhibits mild Windows bias, primarily in the Azure PowerShell section. PowerShell is a Windows-centric tool, and the instructions for installing Azure PowerShell specifically reference Windows and PowerShellGet, with no mention of Linux/macOS alternatives. The sample code for PowerShell uses Windows-style file paths (e.g., C:\ADFv2QuickStartPSH\), and the PowerShell section precedes the Azure CLI section, which is more cross-platform. However, the page does provide Azure CLI, Python, and .NET examples, which are cross-platform, and does not omit Linux/macOS-compatible instructions for the core task.
Recommendations
  • In the Azure PowerShell prerequisites, clarify that Azure PowerShell can be installed on Linux/macOS and provide a link to cross-platform installation instructions.
  • Use neutral file paths in examples (e.g., ./ADFv2QuickStartPSH/MyTrigger.json) or provide both Windows and Linux/macOS path variants.
  • Consider presenting Azure CLI instructions before PowerShell, as CLI is more universally available across platforms.
  • Explicitly state that all SDK and CLI examples work on Linux/macOS, and link to relevant installation guides.
  • Add a note that PowerShell Core is available on Linux/macOS, and provide installation guidance.
GitHub Create Pull Request
Data Factory Introduction to Azure Data Factory ...e-docs/blob/main/articles/data-factory/introduction.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for Azure Data Factory demonstrates mild Windows bias. PowerShell is mentioned as a monitoring tool, and a PowerShell quickstart is listed before Python and REST. There is no explicit mention of Linux/macOS command-line tools or shell scripting alternatives, nor are Linux-specific examples or tools highlighted. While most of the content is platform-neutral, the emphasis on PowerShell and the ordering of quickstart links may create friction for Linux/macOS users.
Recommendations
  • Add explicit references to Linux/macOS-compatible tools for monitoring and automation, such as Bash, Azure CLI, or shell scripting.
  • Provide examples or quickstart guides for Linux/macOS users, especially for common tasks like pipeline creation and monitoring.
  • Reorder quickstart links to present platform-neutral or cross-platform options (e.g., Python, REST, Azure CLI) before platform-specific ones like PowerShell.
  • Clarify that PowerShell is available cross-platform, or suggest alternatives for users who prefer native Linux/macOS environments.
GitHub Create Pull Request
Data Factory Create an Azure Data Factory using Bicep ...s/data-factory/quickstart-create-data-factory-bicep.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation shows a mild Windows bias. The only text editor suggested is Notepad, a Windows tool, with no mention of Linux/macOS alternatives. While deployment and resource management examples are provided for both Azure CLI and Azure PowerShell (the latter being Windows-centric), the CLI examples are present, ensuring Linux parity. However, the order consistently presents Windows tools or concepts first (e.g., Notepad, PowerShell), and does not mention Linux/macOS editors or shell environments explicitly.
Recommendations
  • Suggest cross-platform text editors (e.g., VS Code, nano, vim) alongside Notepad.
  • Clarify that Azure CLI works on Linux/macOS and provide shell-specific notes if needed.
  • When listing tools or commands, alternate or randomize the order, or explicitly state parity.
  • Add a note that PowerShell Core is available on Linux/macOS, or link to installation instructions.
GitHub Create Pull Request
Data Factory Quickstart: Create an Azure Data Factory using Python .../data-factory/quickstart-create-data-factory-python.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation shows minor Windows bias by instructing users to 'Launch Notepad' to create the input file, which is a Windows-specific tool, and does not provide equivalent instructions for Linux/macOS users (e.g., using nano, vim, or touch). Additionally, the phrase 'Open a terminal or command prompt with administrator privileges' lists Windows terminology first and does not clarify Linux/macOS equivalents. No PowerShell or Windows-only tools are required, and the Python code and Azure tools are cross-platform.
Recommendations
  • When instructing users to create a text file, mention cross-platform options, e.g., 'Use Notepad (Windows), nano/vim (Linux/macOS), or any text editor to create input.txt.'
  • Clarify that 'terminal or command prompt' refers to Command Prompt/PowerShell on Windows, Terminal on macOS, and shell on Linux.
  • Explicitly state that all steps and tools (Python, Azure SDK, Azure Storage Explorer) are cross-platform.
  • Add notes or examples for Linux/macOS users where terminology or steps differ.
GitHub Create Pull Request
Data Factory Source control ...docs/blob/main/articles/data-factory/source-control.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias, primarily through repeated references to PowerShell and Windows-specific tools for interacting with Azure Data Factory. PowerShell is mentioned as a method for publishing changes and updating configuration, but equivalent Linux/macOS CLI examples (such as Azure CLI or Bash) are not provided. There are also references to browser compatibility issues (Microsoft Edge) and Visual Studio, which are more common on Windows. However, the core instructions for Git integration and source control are platform-agnostic and do not prevent Linux/macOS users from completing the tasks.
Recommendations
  • Add explicit examples using Azure CLI or Bash for tasks currently described with PowerShell.
  • Clarify that all Git integration steps can be performed from any OS, and provide cross-platform instructions where relevant.
  • Mention Linux/macOS compatible browsers and tools when discussing compatibility issues.
  • Where Visual Studio or Microsoft Edge are referenced, provide alternatives for Linux/macOS users (e.g., VS Code, Chrome, Firefox).
GitHub Create Pull Request
Data Factory Transform data ...docs/blob/main/articles/data-factory/transform-data.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias. The only tutorial linked at the end is for Spark transformation using PowerShell, a Windows-centric tool, with no equivalent Bash or Linux shell tutorial. References to SQL Server Stored Procedure activity prioritize SQL Server (a Microsoft/Windows-first technology) and Azure SQL Database, with no mention of open-source or Linux-native databases. The HDInsight activities mention both Windows and Linux clusters, but do not provide examples or guidance for Linux users. The page generally lists Windows tools and patterns first or exclusively.
Recommendations
  • Add equivalent Linux/Bash shell tutorials for transformation activities, especially for Spark.
  • Provide examples using Linux-native tools and environments where possible.
  • Mention and provide guidance for open-source databases (e.g., PostgreSQL, MySQL) in the Stored Procedure activity section.
  • Ensure that examples and walkthroughs are platform-neutral or include both Windows and Linux/macOS instructions.
  • Clarify when features or activities are available cross-platform, and highlight any platform-specific limitations.
GitHub Create Pull Request
Data Factory Copy and transform data from Microsoft 365 (Office 365) ...lob/main/articles/data-factory/connector-office-365.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the certificate conversion instructions, which reference PowerShell and link to a PowerShell-based tutorial for converting certificates to base64. Additionally, the template for certificate conversion is likely Windows-centric. While the main Azure Data Factory and Synapse workflows are cross-platform, Windows/PowerShell tools are mentioned first and exclusively for certain steps, with no Linux/macOS alternatives provided.
Recommendations
  • Provide Linux/macOS-compatible instructions for converting certificates to base64, such as using OpenSSL commands.
  • Include explicit examples or links for certificate management on non-Windows platforms.
  • When referencing external tutorials or templates, clarify platform compatibility and offer alternatives for Linux/macOS users.
  • Avoid assuming PowerShell is the default tool; mention cross-platform options where possible.
GitHub Create Pull Request
Data Factory Compute environments .../main/articles/data-factory/compute-linked-services.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias, primarily through the exclusive mention of Windows-centric tools (such as Microsoft Azure Storage Explorer) and PowerShell cmdlets (e.g., New-AzBatchAccount, New-AzBatchPool) for Azure Batch setup. These tools and patterns are referenced without Linux/macOS alternatives or parity, and Windows tools are mentioned before any cross-platform or Linux-native options. However, the core configuration and examples for HDInsight clusters are Linux-based, and most JSON configuration is platform-agnostic.
Recommendations
  • Include Linux/macOS alternatives for tools like Azure Storage Explorer (e.g., CLI commands for az storage container delete).
  • Provide Bash/Azure CLI examples alongside PowerShell cmdlets for Azure Batch setup and management.
  • Clarify that most operations (e.g., authentication, cluster management) can be performed cross-platform, and link to relevant Linux/macOS documentation.
  • Avoid referencing Windows tools exclusively or first; present cross-platform options in parallel.
  • Explicitly mention that the JSON configuration is platform-agnostic and can be used from any OS.
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
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits a mild Windows bias by referencing Windows-specific tooling (Dynamics XRM tooling for Windows client applications) and mentioning Windows patterns first. However, the actual configuration and usage instructions are platform-neutral, focusing on Azure portal UI, JSON, and FetchXML, which are accessible from Linux/macOS. No PowerShell or Windows-only examples are present, and Linux/macOS users can complete all described tasks.
Recommendations
  • Clarify that Dynamics XRM tooling is not required for Azure Data Factory/Synapse usage, or provide equivalent cross-platform SDK/tooling references if relevant.
  • If any client-side scripting or automation is needed, include examples for Linux/macOS (e.g., using Azure CLI, REST API, or Python SDK).
  • Explicitly state that all configuration steps can be performed from any OS via the Azure portal or REST API.
  • Avoid referencing Windows client development guides unless directly relevant to the Azure Data Factory/Synapse connector usage.
GitHub Create Pull Request
Data Factory Copy data from Netezza ...s/blob/main/articles/data-factory/connector-netezza.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Windows versions as prerequisites for the self-hosted integration runtime and linking to a Windows-focused prerequisites article. There is no explicit mention of Linux or macOS support or installation steps for the IBM Netezza ODBC driver on those platforms. However, most configuration and code examples are platform-agnostic JSON and do not rely on Windows-specific tools or PowerShell.
Recommendations
  • Explicitly document Linux and macOS support for the self-hosted integration runtime, including prerequisites and installation steps.
  • Provide links or instructions for installing the IBM Netezza ODBC driver on Linux and macOS, not just Windows.
  • Reference cross-platform compatibility in the prerequisites section, and avoid language that implies Windows is the only supported OS.
  • If there are platform-specific limitations, clearly state them and offer guidance or alternatives for Linux/macOS users.
GitHub Create Pull Request
Data Factory Copy and transform data from and to a REST endpoint ...docs/blob/main/articles/data-factory/connector-rest.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the 'TIP' section where PowerShell's Invoke-RestMethod and Visual Studio are suggested as tools to validate REST API requests, with no mention of Linux/macOS equivalents like curl or httpie. Windows tools are mentioned first and exclusively, which may create friction for Linux/macOS users unfamiliar with these options.
Recommendations
  • Include Linux/macOS command-line examples using curl or httpie for REST API validation alongside PowerShell.
  • Mention cross-platform tools (e.g., Postman, curl, httpie) before or alongside Windows-specific tools.
  • Add notes or examples for certificate conversion using OpenSSL (common on Linux/macOS) in addition to PowerShell.
  • Ensure that tool recommendations are platform-neutral or provide parity for all major OSes.
GitHub Create Pull Request
Data Factory Troubleshoot the FTP, SFTP, and HTTP connectors ...s/data-factory/connector-troubleshoot-ftp-sftp-http.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation generally maintains cross-platform neutrality, but there are subtle signs of Windows bias. For example, WinSCP (a Windows-only tool) is recommended for credential verification, while no Linux/macOS alternatives are mentioned. Additionally, the HTTP status code documentation link points to IIS (a Windows web server) management docs, which may not be relevant for Linux-based HTTP servers. However, most code samples and troubleshooting steps use platform-neutral tools (e.g., openssl, ssh-keygen, Python), and Linux commands are included where appropriate.
Recommendations
  • When recommending tools for credential verification (e.g., WinSCP), also mention Linux/macOS equivalents such as FileZilla, Cyberduck, or command-line sftp.
  • For HTTP status code references, provide links to platform-neutral resources (e.g., MDN Web Docs) rather than IIS-specific documentation.
  • Where examples or troubleshooting steps involve platform-specific tools, offer alternatives for all major platforms.
  • Explicitly state that commands like openssl and ssh-keygen are available on Linux/macOS and provide installation guidance if needed.
GitHub Create Pull Request
Data Factory Create an Azure-SSIS integration runtime via Azure portal ...actory/create-azure-ssis-integration-runtime-portal.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias, primarily through references to PowerShell for backup configuration and the use of Windows-centric terminology (e.g., UNC paths, SSMS, SQL authentication). Windows tools and patterns are mentioned (PowerShell, SSMS) without equivalent Linux/macOS alternatives, and the only explicit CLI example referenced is PowerShell. However, the main workflow is via the Azure portal, which is cross-platform, and most steps do not require Windows-only tools.
Recommendations
  • Provide CLI examples using Azure CLI and/or Bash scripts alongside PowerShell, especially for tasks like configuring backup storage redundancy.
  • Mention cross-platform alternatives to SSMS, such as Azure Data Studio, and clarify which steps can be performed from Linux/macOS.
  • When referencing file paths, include examples for Linux/macOS (e.g., NFS paths) where relevant.
  • Explicitly state platform requirements for any step that is Windows-only, and provide workarounds or alternatives for Linux/macOS users.
GitHub Create Pull Request
Data Factory Create an Azure Data Factory using Bicep ...s/data-factory/quickstart-create-data-factory-bicep.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation shows a mild Windows bias: it suggests Notepad as the text editor, which is Windows-specific, and lists Azure PowerShell examples alongside CLI, with PowerShell examples shown after CLI but without explicit Linux/macOS alternatives for file creation or PowerShell usage. However, the core deployment and resource management instructions use Azure CLI, which is cross-platform, and all PowerShell commands are optional alternatives. There are no critical Windows-only tools or patterns, but the file creation step could be clearer for Linux/macOS users.
Recommendations
  • Suggest cross-platform text editors (e.g., VS Code, nano, vim) alongside Notepad for file creation.
  • Clarify that Azure CLI is cross-platform and recommend it as the primary method for Linux/macOS users.
  • Add explicit instructions or examples for creating the emp.txt file on Linux/macOS (e.g., using 'echo' or 'nano').
  • Note that Azure PowerShell is available on Linux/macOS, or clarify its usage context.
  • Ensure that all steps can be completed on Linux/macOS without ambiguity.
GitHub Create Pull Request
Data Factory Quickstart: Create an Azure Data Factory using Python .../data-factory/quickstart-create-data-factory-python.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation shows minor Windows bias by instructing users to 'Launch Notepad' to create a text file, which is a Windows-specific tool, and by mentioning 'command prompt with administrator privileges' before 'terminal'. There are no explicit Linux/macOS instructions or examples for creating files or using alternative tools, and no mention of Linux-specific equivalents for Azure Storage Explorer or file creation.
Recommendations
  • Replace 'Launch Notepad' with a cross-platform instruction such as 'Use a text editor (e.g., Notepad on Windows, nano or vim on Linux/macOS) to create input.txt.'
  • Clarify that 'terminal or command prompt' applies to all platforms, and remove or qualify 'administrator privileges' as it may not apply to Linux/macOS.
  • Mention that Azure Storage Explorer is available for Windows, Linux, and macOS, and provide links or notes for Linux/macOS users.
  • Add explicit Linux/macOS examples or notes where file creation or command-line usage is described.
GitHub Create Pull Request
Data Factory Source control ...docs/blob/main/articles/data-factory/source-control.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page for Azure Data Factory source control exhibits mild Windows bias. PowerShell is referenced as a method for publishing changes and updating configuration, with no mention of Linux/macOS equivalents (e.g., Bash, Azure CLI). Troubleshooting and certain examples mention PowerShell or SDK, but do not provide parity for Linux users. There is also a subtle preference for Windows tools (e.g., PowerShell, Microsoft Edge browser) and terminology (e.g., 'Publish All' button, which is a UI concept but may be more familiar to Windows users). However, the core Git integration instructions are platform-agnostic, and most steps can be performed from any OS using the web UI.
Recommendations
  • Add examples for Linux/macOS users, such as using Azure CLI or Bash scripts to interact with Azure Data Factory, alongside PowerShell examples.
  • Explicitly mention cross-platform alternatives wherever PowerShell or Windows-specific tools are referenced.
  • Include troubleshooting steps for Linux/macOS environments (e.g., using Azure CLI, curl, or other tools).
  • Clarify that all Git operations can be performed from any OS, and provide links to platform-agnostic tools.
  • Avoid browser-specific recommendations unless necessary, and offer alternatives for non-Windows browsers.
GitHub Create Pull Request
Data Factory Transform data ...docs/blob/main/articles/data-factory/transform-data.md
Low Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates mild Windows bias. The only tutorial linked at the end is for Spark transformation using PowerShell, which is Windows-centric and does not mention Linux or Bash alternatives. References to SQL Server Stored Procedure activity and .NET custom activities also reflect a Windows-first approach, as these technologies are traditionally Windows-oriented. However, the main content generally mentions both Windows and Linux HDInsight clusters, and most transformation activities are platform-agnostic.
Recommendations
  • Provide equivalent Linux/Bash examples or tutorials alongside PowerShell-based instructions, especially in the 'Related content' section.
  • Explicitly mention cross-platform compatibility for .NET custom activities and SQL Server stored procedures, and provide examples for Linux/macOS environments where possible.
  • Include links to tutorials or documentation that use Linux-native tools and workflows (e.g., Bash, Python scripts, etc.) for transformation activities.
  • Ensure that references to Windows tools (PowerShell, .NET, SQL Server) are balanced with Linux/macOS alternatives or clarifications.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/airflow-get-ip-airflow-cluster.md ...rticles/data-factory/airflow-get-ip-airflow-cluster.md
Low Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides instructions and screenshots for retrieving the IP address of a Workflow Orchestration Manager cluster, but does not include any command-line examples or instructions specific to Linux or macOS environments. There are no references to Linux tools, shell commands, or cross-platform CLI usage; all examples are either UI-based or use REST API calls shown in screenshots, which may implicitly assume a Windows-centric workflow (e.g., using Azure Portal or tools commonly accessed from Windows environments).
Recommendations
  • Add explicit command-line examples using curl or wget for REST API calls, demonstrating how to retrieve the access token and cluster IP address from Linux/macOS terminals.
  • Include sample scripts or commands for both PowerShell (Windows) and Bash (Linux/macOS) to show parity.
  • Reference cross-platform tools such as Azure CLI or az rest commands, and provide examples for their usage.
  • Clarify that the steps can be performed from any operating system, and provide guidance for users on Linux/macOS where applicable.
GitHub Create Pull Request
← Previous Page 13 of 13 Next →