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 376-400 of 1000 flagged pages
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-deploy-ssis-packages-azure.md ...es/data-factory/tutorial-deploy-ssis-packages-azure.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation page exhibits Windows bias by exclusively referencing Windows-based tools (SSDT, SSMS, dtutil, AzureDTExec), providing PowerShell instructions for firewall configuration, and omitting Linux equivalents or examples. Windows tools and patterns are mentioned first and exclusively, with no guidance for Linux users or cross-platform alternatives.
Recommendations
  • Include examples and instructions for deploying and managing SSIS packages from Linux/macOS environments, such as using Azure CLI, REST API, or cross-platform tools.
  • Mention and document any cross-platform alternatives to SSDT, SSMS, dtutil, and AzureDTExec, or clarify their platform limitations.
  • Provide equivalent steps for configuring Azure SQL Database firewall rules using Azure CLI or portal, not just PowerShell.
  • Explicitly state platform requirements and limitations for each tool, and recommend best practices for Linux users.
  • Add notes or sections addressing how Linux users can interact with Azure Data Factory and Azure-SSIS IR, including package deployment and management.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-hybrid-copy-powershell.md ...ticles/data-factory/tutorial-hybrid-copy-powershell.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments, with all examples and instructions using PowerShell and Windows-specific tools. The tutorial assumes the use of Windows for installing and running the self-hosted integration runtime, and does not provide any guidance or examples for Linux users. There are no Bash, Azure CLI, or Linux-native instructions, and Windows tools (such as SQL Server Management Studio and PowerShell) are mentioned exclusively and before any alternatives.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI and Bash for Linux users.
  • Clarify whether the self-hosted integration runtime can be installed on Linux, and provide installation steps if supported.
  • Include guidance for connecting to SQL Server from Linux (e.g., using sqlcmd or Azure Data Studio).
  • Mention and demonstrate cross-platform tools where possible (e.g., Azure Data Studio instead of SSMS, Notepad alternatives).
  • Add notes or sections that explicitly address Linux and macOS users, including any limitations or required workarounds.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/compute-linked-services.md .../main/articles/data-factory/compute-linked-services.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation demonstrates a mild Windows bias, primarily through the exclusive mention of Windows-specific tools (such as PowerShell cmdlets) and the prioritization of Windows-centric patterns. For example, Azure Batch account creation is described using PowerShell cmdlets before mentioning the Azure portal, and references to 'CMDLETs & APIS' for VM sizing are made without Linux CLI equivalents. There is also a reliance on Microsoft Azure Storage Explorer for blob management, which is a Windows-first tool, with no mention of Linux alternatives. However, most configuration examples and cluster OS types default to Linux, and there is no outright omission of Linux support in the core service descriptions.
Recommendations
  • Provide equivalent Azure CLI or Bash examples alongside PowerShell cmdlets for Azure Batch and VM sizing operations.
  • Mention cross-platform tools for blob storage management, such as azcopy or Azure CLI, in addition to Microsoft Azure Storage Explorer.
  • When referencing VM sizing, link to documentation for both PowerShell and Azure CLI, and clarify that the APIs and naming conventions are consistent across platforms.
  • Explicitly state Linux support and provide Linux-specific troubleshooting steps or tool recommendations where relevant.
  • Ensure that any references to scripting, automation, or management include both Windows and Linux options, especially in sections discussing cluster management and integration runtimes.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-pipelines-activities.md ...articles/data-factory/concepts-pipelines-activities.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 primarily through its use of PowerShell-based walkthroughs and examples. References to pipeline creation and transformation tutorials consistently point to PowerShell guides, with no mention of Linux shell, Bash, or cross-platform CLI alternatives. The 'Related content' and sample pipeline walkthroughs exclusively reference PowerShell, and there is no parity for Linux or macOS users. No Linux-specific tools or examples (such as Azure CLI or Bash scripts) are provided, nor are they mentioned as alternatives.
Recommendations
  • Add equivalent walkthroughs and tutorials using Azure CLI and Bash scripts for pipeline creation and management.
  • Reference Linux/macOS-compatible tools and provide sample commands for those platforms alongside PowerShell examples.
  • Update 'Related content' to include links to Linux and cross-platform guides, not just PowerShell-based documentation.
  • Explicitly mention that Azure Data Factory and Synapse can be managed from Linux/macOS environments and provide guidance for those users.
  • Ensure all examples and code snippets are platform-agnostic or provide alternatives for both Windows and Linux users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-netezza.md ...s/blob/main/articles/data-factory/connector-netezza.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 exhibits Windows bias by referencing Windows versions as prerequisites for the self-hosted integration runtime, not mentioning Linux compatibility or setup. There are no Linux-specific instructions, examples, or screenshots, and the installation guidance for the IBM Netezza ODBC driver does not clarify Linux support. All examples and tooling references are platform-neutral but omit any mention of Linux environments, which may lead users to assume Windows is required.
Recommendations
  • Explicitly state Linux support for self-hosted integration runtime and IBM Netezza ODBC driver, including supported distributions.
  • Provide step-by-step instructions for installing and configuring the IBM Netezza ODBC driver on Linux.
  • Include Linux-specific examples, such as shell commands for setup, and clarify any differences in configuration or troubleshooting.
  • Add screenshots or references to Linux environments in UI or command-line examples.
  • Mention any Linux-specific prerequisites or considerations alongside Windows references.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-azure-blob-storage.md ...a-factory/connector-troubleshoot-azure-blob-storage.md
High Priority View Details →
Scanned: 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 displays Windows bias by referencing Windows-specific tools (diawp.exe.config) and configuration steps, particularly in the FIPS mode troubleshooting section. There are no Linux-specific troubleshooting steps or examples, and the guidance assumes a Windows environment for the self-hosted integration runtime. Linux equivalents or instructions are absent, and Windows is mentioned as the default or recommended platform.
Recommendations
  • Include troubleshooting steps for Linux environments, such as how to disable FIPS mode or configure the integration runtime on Linux.
  • Provide examples or references for both Windows and Linux platforms when discussing configuration files or system policies.
  • Explicitly mention platform differences and offer parity in guidance for non-Windows users.
  • Reference Linux tools or commands (e.g., systemd, config file locations) where appropriate.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-rest.md ...n/articles/data-factory/connector-troubleshoot-rest.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 demonstrates Windows bias by referencing 'Command Prompt' as the environment for running curl, omitting mention of Linux/macOS terminals. It also recommends Fiddler, a Windows-centric tool, without suggesting Linux alternatives. No Linux-specific troubleshooting examples or tool recommendations are provided.
Recommendations
  • Explicitly mention that curl can be run in Linux and macOS terminals, not just Windows Command Prompt.
  • Provide example curl commands for Bash or other common Linux shells.
  • Suggest cross-platform or Linux-native alternatives to Fiddler, such as Wireshark or mitmproxy.
  • Add troubleshooting steps or notes relevant to Linux environments, including handling SSL certificate issues on Linux.
  • Ensure tool recommendations and examples are balanced between Windows and Linux platforms.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-file-system.md ...les/data-factory/connector-troubleshoot-file-system.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 exhibits Windows bias by exclusively referencing PowerShell for configuring the self-hosted integration runtime (SHIR) and omitting any mention of Linux or cross-platform alternatives. The troubleshooting recommendation directs users to use a Windows-specific tool (PowerShell) without providing equivalent instructions for Linux environments, which may alienate users running SHIR on Linux or other platforms.
Recommendations
  • Include Linux-specific instructions for configuring SHIR file system access, such as using Bash scripts or command-line tools.
  • Provide cross-platform examples, clearly indicating how to perform the same configuration on both Windows (PowerShell) and Linux (Bash/CLI).
  • Mention platform requirements and alternatives explicitly, so users know if certain steps are Windows-only and what to do on Linux.
  • Consider referencing generic command-line methods or REST API calls if available, to ensure parity for all supported operating systems.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-switch-activity.md .../articles/data-factory/control-flow-switch-activity.md
High Priority View Details →
Scanned: 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. All command-line examples use Azure PowerShell, with explicit references to Windows file paths (e.g., C:\ADF). There are no equivalent examples for Linux or cross-platform tools such as Azure CLI, nor any mention of Linux-specific patterns or considerations. The tutorial and walkthrough links also focus on Azure PowerShell, reinforcing the Windows-centric approach.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, using Linux/macOS-friendly file paths and shell syntax.
  • Include notes or sections on running the pipeline and managing files on Linux/macOS environments.
  • Use generic or cross-platform file paths (e.g., /home/user/ADF or ./ADF) in examples, or clarify that paths should be adapted for the user's OS.
  • Mention cross-platform compatibility explicitly, and provide links to Linux/macOS setup guides where relevant.
  • Ensure tutorials and walkthroughs are available for both PowerShell and Azure CLI, and reference both equally.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/continuous-integration-delivery-sample-script.md ...ctory/continuous-integration-delivery-sample-script.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 is heavily biased towards Windows and PowerShell usage. All examples, instructions, and tooling references are exclusively for Azure PowerShell (.ps1 scripts), with no mention of Bash, Azure CLI, or Linux-compatible alternatives. The page assumes the use of PowerShell Core but does not provide parity for users on Linux or macOS, nor does it offer cross-platform scripting guidance.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for pre- and post-deployment tasks.
  • Explicitly mention how Linux/macOS users can run these scripts, including any necessary modifications or prerequisites.
  • Add guidance on using cross-platform tools (e.g., Azure CLI, Python SDK) for CI/CD scripting in Azure Data Factory.
  • Reorder sections to present cross-platform options before or alongside Windows/PowerShell instructions.
  • Include notes on script compatibility and how to adapt PowerShell scripts for non-Windows environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/credentials.md ...re-docs/blob/main/articles/data-factory/credentials.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 referencing Windows-centric tools (Azure portal, PowerShell) and providing no explicit Linux or cross-platform CLI examples. PowerShell is mentioned as a primary scripting option, while Linux-friendly alternatives like Azure CLI are not discussed. The workflow and screenshots are focused on the Azure portal, which is most commonly used on Windows, and there is no mention of Linux shell commands or guidance for Linux users.
Recommendations
  • Add Azure CLI examples for all major actions (creating managed identities, assigning them, managing credentials) alongside PowerShell references.
  • Include screenshots or instructions for using the Azure portal from non-Windows platforms, or clarify cross-platform compatibility.
  • Explicitly mention Linux/macOS support and provide guidance for users on those platforms.
  • List scripting options in a neutral order (e.g., 'SDK, Azure CLI, PowerShell, REST API') rather than leading with PowerShell.
  • Provide parity in examples and documentation for both Windows and Linux users to ensure inclusivity.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-resource-manager-template.md ...ure-ssis-integration-runtime-resource-manager-template.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 exclusively providing PowerShell commands for deploying and managing Azure-SSIS integration runtimes. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or cross-platform tools. Windows tools and patterns (PowerShell, Windows authentication) are mentioned without Linux equivalents, and the workflow assumes a Windows environment by default.
Recommendations
  • Add equivalent Azure CLI examples for deploying and managing Azure-SSIS IR, which can be run on Linux, macOS, and Windows.
  • Provide Bash script samples for template deployment and IR management.
  • Include notes or sections explicitly addressing cross-platform usage, clarifying that PowerShell Core is available on Linux/macOS, or recommending Azure CLI for those platforms.
  • Mention any platform-specific limitations or considerations for Linux/macOS users.
  • Reorder examples so that cross-platform tools (Azure CLI) are presented before or alongside PowerShell to avoid implicit Windows-first bias.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-flow-script.md ...cs/blob/main/articles/data-factory/data-flow-script.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary method for programmatically interacting with Data Flow Scripts, without mentioning Linux or cross-platform alternatives. Windows tooling (PowerShell cmdlet) is presented as the default, and there are no examples or guidance for Linux users (e.g., Bash, Azure CLI, REST API usage from Linux). This may make Linux users feel unsupported or unclear about how to achieve parity.
Recommendations
  • Add examples and instructions for using Data Flow Scripts with Azure CLI and REST API, which are cross-platform and commonly used on Linux.
  • Explicitly mention that PowerShell is available on Linux and macOS, or provide Bash script equivalents for common tasks.
  • Rephrase sections to avoid implying PowerShell is the only or primary method; present cross-platform options first or alongside PowerShell.
  • Include sample commands for generating and submitting scripts from Linux environments.
  • Add a note or section on platform compatibility, clarifying that all features are accessible from Windows, Linux, and macOS.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-v2-connector-get-started.md ...tory/includes/data-factory-v2-connector-get-started.md
High Priority View Details →
Scanned: 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 lists Azure PowerShell as a primary tool for performing copy activities, which is typically associated with Windows environments. There is no mention of Linux-specific tools (e.g., Azure CLI), and the ordering places PowerShell before REST API and ARM templates, potentially indicating a Windows-first approach. The absence of explicit Linux command-line examples or references to Linux-friendly tools suggests a bias toward Windows users.
Recommendations
  • Add Azure CLI as a recommended tool for performing copy activities, with links to relevant quickstart guides.
  • Include explicit examples or references for Linux environments, such as Bash scripts or Linux terminal usage.
  • Reorder the list to avoid prioritizing Windows-centric tools; consider grouping cross-platform tools (REST API, SDKs, CLI) before platform-specific ones like PowerShell.
  • Clarify that all listed tools (where applicable) are available on both Windows and Linux, or specify platform compatibility.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-quickstart-prerequisites.md ...tory/includes/data-factory-quickstart-prerequisites.md
High Priority View Details →
Scanned: 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 by referencing Windows-specific tools and patterns, such as Notepad and the C:\ADFv2QuickStartPSH folder path, without providing Linux equivalents. There are no examples or instructions for Linux users (e.g., using nano/vim, or ~/ADFv2QuickStartPSH), and the file path conventions are exclusively Windows-style. The instructions for creating and uploading files assume a Windows environment, and there is no mention of Linux or cross-platform alternatives.
Recommendations
  • Add Linux-specific instructions alongside Windows ones, such as using nano or vim to create files and using Linux file paths (e.g., ~/ADFv2QuickStartPSH).
  • Include screenshots or terminal commands for Linux environments where appropriate.
  • Mention cross-platform text editors (e.g., VS Code) and provide guidance for both Windows and Linux users.
  • Clarify that the steps can be performed on both Windows and Linux, and provide parity in examples and terminology.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-schedule-azure-ssis-integration-runtime.md ...tory/how-to-schedule-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
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits a strong Windows bias. All code examples for automation and monitoring use PowerShell, a Windows-centric scripting language, with no mention of Bash, CLI, or cross-platform alternatives. The only tool referenced for interacting with SSIS packages is SQL Server Management Studio (SSMS), which is primarily a Windows application. There are no Linux or macOS equivalents or instructions provided, and no cross-platform command-line examples (e.g., Azure CLI, REST API via curl). The documentation also assumes the use of Microsoft Edge or Google Chrome, but only in the context of Data Factory UI support, not automation. Overall, the guidance prioritizes Windows tools and patterns, omitting Linux-native or cross-platform approaches.
Recommendations
  • Provide equivalent Azure CLI examples for all PowerShell scripts, especially for starting/stopping and monitoring Azure-SSIS IR.
  • Include REST API usage examples with curl or httpie for pipeline management and monitoring, demonstrating cross-platform automation.
  • Mention and provide instructions for using Azure Data Studio (which is cross-platform) for SSIS package management, or clarify limitations.
  • Add notes or sections on how Linux/macOS users can perform the same tasks, including scheduling and automation (e.g., using cron jobs with Azure CLI or REST API calls).
  • Where PowerShell modules are referenced, provide links and instructions for installing and running PowerShell Core on Linux/macOS, or suggest alternatives.
  • Explicitly state platform requirements and offer parity guidance for non-Windows environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-quickstart-verify-output-cleanup.md ...ludes/data-factory-quickstart-verify-output-cleanup.md
High Priority View Details →
Scanned: 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 commands for resource cleanup, which are primarily used on Windows. There are no equivalent examples for Linux users, such as Azure CLI or Bash commands. The documentation assumes familiarity with Windows tooling and does not mention or prioritize cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for resource group and data factory deletion, which work on Linux, macOS, and Windows.
  • Explicitly mention that PowerShell commands are for Windows and provide cross-platform alternatives.
  • Include Bash script examples for common operations where appropriate.
  • Add a section or note highlighting cross-platform options for managing Azure resources.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/monitor-integration-runtime.md ...n/articles/data-factory/monitor-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 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples and cmdlets for monitoring integration runtimes in Azure Data Factory. All command-line instructions use PowerShell syntax, with no mention of Linux-native tools, Bash, or cross-platform alternatives. The self-hosted integration runtime is described as being installed on 'on-premises Windows machines,' and there is no guidance for Linux deployments or monitoring. Windows-centric tools and patterns (PowerShell, SSMS, SSDT) are referenced throughout, while Linux equivalents are absent.
Recommendations
  • Provide equivalent Bash/CLI examples for all PowerShell commands, using Azure CLI or REST API where possible.
  • Explicitly mention and document support for self-hosted integration runtime on Linux, including installation, monitoring, and troubleshooting steps.
  • Reference Linux-compatible tools (e.g., Azure CLI, curl, jq) alongside Windows tools like PowerShell, SSMS, and SSDT.
  • Rephrase sections that imply self-hosted integration runtime is only for Windows, clarifying cross-platform capabilities.
  • Add troubleshooting and monitoring guidance for Linux environments, including log file locations and system resource monitoring commands.
  • Ensure all sample outputs and instructions are platform-neutral or provide both Windows and Linux variants.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/quickstart-create-data-factory-dot-net.md ...data-factory/quickstart-create-data-factory-dot-net.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 is heavily oriented toward Windows development environments. It exclusively references Visual Studio (a Windows-centric IDE) for project creation and management, and all package installation instructions use PowerShell commands in the NuGet Package Manager Console, which is only available in Visual Studio on Windows. There are no instructions or examples for Linux or cross-platform development environments (such as VS Code, JetBrains Rider, or CLI-based workflows). The documentation does not mention .NET CLI commands or alternative editors, nor does it provide guidance for Linux users.
Recommendations
  • Add instructions for creating and managing .NET projects using the .NET CLI (e.g., 'dotnet new console', 'dotnet add package ...') that work on Linux, macOS, and Windows.
  • Include examples for installing NuGet packages via the CLI, not just PowerShell/Visual Studio.
  • Mention and provide steps for using cross-platform editors such as Visual Studio Code or JetBrains Rider.
  • Clarify that the .NET SDK and Azure SDK are cross-platform and can be used on Linux and macOS, not just Windows.
  • Provide troubleshooting notes or links for Linux/macOS users regarding authentication and environment setup.
  • Reorder sections so that cross-platform instructions are presented before or alongside Windows-specific instructions.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/transform-data.md ...docs/blob/main/articles/data-factory/transform-data.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 Powershell Heavy
Summary
The documentation demonstrates mild Windows bias. Windows-based tools and environments (e.g., SQL Server Stored Procedure, .NET custom activity) are mentioned without explicit Linux alternatives. The HDInsight activities mention both Windows and Linux clusters, but Windows is listed first. The related tutorial references Spark with PowerShell, a Windows-centric automation tool, without mentioning Bash or Linux equivalents. There are no Linux-specific examples or tools highlighted, and the documentation leans toward Windows-native technologies and patterns.
Recommendations
  • Provide Linux/Bash examples alongside PowerShell, especially in tutorials and code samples.
  • Explicitly mention Linux-compatible alternatives for custom activities (e.g., Python, Java, or shell scripts) and highlight cross-platform compatibility.
  • List Linux and Windows options in a neutral order (e.g., 'Windows/Linux-based HDInsight cluster' could be 'Linux/Windows-based HDInsight cluster').
  • Include references to Linux-native data transformation tools and patterns where applicable.
  • Ensure that documentation for .NET activities clarifies cross-platform support (e.g., .NET Core on Linux).
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-enable-remote-access-intranet-tls-ssl-certificate.md ...rial-enable-remote-access-intranet-tls-ssl-certificate.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 is heavily biased towards Windows environments. All command-line examples use PowerShell, and certificate management steps rely on Windows-specific tools and UI (MMC snap-in, cert store locations, NT SERVICE accounts). There are no Linux or cross-platform instructions, nor are Linux equivalents mentioned for certificate generation, installation, or runtime configuration.
Recommendations
  • Provide equivalent Linux instructions for certificate generation (e.g., using OpenSSL) and installation (e.g., using update-ca-certificates or certutil).
  • Include Linux command-line examples for obtaining FQDNs (e.g., `hostname -f`).
  • Document how to configure integration runtime nodes on Linux, if supported, including certificate trust and permissions.
  • Mention cross-platform certificate formats and storage locations.
  • Clarify platform support and, if Windows-only, explicitly state this at the beginning of the documentation.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-hybrid-copy-portal.md ...n/articles/data-factory/tutorial-hybrid-copy-portal.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 bias towards Windows environments. It exclusively references Windows tools such as SQL Server Management Studio (SSMS), assumes the use of Windows for installing the self-hosted integration runtime, and provides no guidance or examples for Linux users. There are no instructions for using Linux-compatible SQL Server clients, nor any mention of Linux installation steps for the integration runtime.
Recommendations
  • Add instructions and examples for setting up the SQL Server source and integration runtime on Linux, including supported distributions.
  • Mention and provide examples for Linux-compatible SQL Server clients (e.g., sqlcmd, Azure Data Studio) alongside SSMS.
  • Clarify whether the self-hosted integration runtime can be installed on Linux, and provide step-by-step guidance if supported.
  • Ensure that screenshots and tool references are not exclusively Windows-centric, and include Linux equivalents where possible.
  • Explicitly state platform requirements and alternatives in the prerequisites section to inform users of cross-platform options.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-hybrid-copy-powershell.md ...ticles/data-factory/tutorial-hybrid-copy-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 is heavily biased toward Windows and PowerShell. All command-line examples use Windows PowerShell, and there is no mention of Linux or cross-platform alternatives. The installation and usage of the Azure Data Factory Integration Runtime is described only for Windows, with explicit instructions and screenshots for Windows dialogs. The tutorial assumes the use of Windows directories (e.g., C:\ADFv2Tutorial) and Windows-specific tools (SQL Server Management Studio, PowerShell). There are no Linux or macOS equivalents or instructions provided.
Recommendations
  • Add equivalent instructions and examples for Linux and macOS users, including use of Azure CLI and Bash scripts.
  • Document how to install and use the self-hosted integration runtime on Linux (if supported), or clearly state platform limitations.
  • Provide cross-platform alternatives for file and directory management (e.g., using ~/ADFv2Tutorial on Linux/macOS).
  • Include SQL Server connection instructions using cross-platform tools (e.g., Azure Data Studio, sqlcmd).
  • Explicitly mention platform requirements and limitations at the beginning of the tutorial.
  • Where PowerShell is used, offer Azure CLI or REST API equivalents for all steps.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-package-store.md ...actory/azure-ssis-integration-runtime-package-store.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 Windows First Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All examples and instructions rely on Windows-specific tools (SSMS, dtutil, net use, cmdkey), Windows file paths, and Windows command prompt syntax. There are no Linux equivalents or cross-platform alternatives provided, and the workflow assumes the user is operating from a Windows machine with SQL Server Management Studio installed.
Recommendations
  • Provide Linux-compatible instructions for connecting to Azure Files (e.g., using smbclient, mount.cifs, or Azure CLI).
  • Include examples of deploying SSIS packages using cross-platform tools or containers, if available.
  • Clarify which steps require Windows and suggest alternatives or workarounds for Linux/Mac users.
  • Mention the lack of SSMS on Linux and suggest using Azure Data Studio or other cross-platform management tools where possible.
  • If dtutil is Windows-only, note this limitation and suggest any available REST APIs, Azure CLI, or PowerShell Core alternatives that work on Linux.
  • Add a section explicitly addressing Linux/Mac users and guiding them through the process with platform-appropriate tools.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/author-global-parameters.md ...main/articles/data-factory/author-global-parameters.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 Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its CI/CD section by exclusively referencing PowerShell scripts for deploying global parameters and not mentioning or providing examples for Linux/macOS equivalents (such as Bash, Azure CLI, or cross-platform automation tools). There is no guidance for non-Windows users, and Windows tooling is assumed as the default.
Recommendations
  • Add examples for deploying global parameters using Azure CLI, which is cross-platform and works on Linux/macOS.
  • Provide Bash script samples for ARM template deployment to illustrate Linux workflows.
  • Explicitly mention that PowerShell is one option and highlight alternatives for non-Windows environments.
  • Clarify that ARM template deployment can be performed from any OS and link to platform-agnostic deployment documentation.
  • Review all CI/CD guidance to ensure parity between Windows and Linux/macOS tooling and workflows.
GitHub Create Pull Request
← Previous Page 16 of 40 Next →