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 151-175 of 1000 flagged pages
Data Factory Applying DataOps ...-docs/blob/main/articles/data-factory/apply-dataops.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows, such as PowerShell, Visual Studio, and .NET (NUnit), for CI/CD and automated testing examples. Linux-native alternatives (e.g., Bash, shell scripting, Linux-based CI/CD runners) are not mentioned, and there are no examples or guidance for users working in Linux environments. The documentation assumes the use of Windows tooling and does not provide parity for Linux users.
Recommendations
  • Include Linux-specific examples for CI/CD, such as using Bash scripts, shell commands, or Linux-based runners in GitHub Actions or Azure Pipelines.
  • Provide guidance on using cross-platform tools (e.g., Python, Node.js, Docker) for automated testing and deployment, in addition to .NET/Visual Studio.
  • Add examples of using AZ CLI commands in Bash or other Linux shells, not just PowerShell.
  • Mention and link to Linux-compatible editors (e.g., VS Code, JetBrains IDEs) for editing and testing ARM templates and JSON artifacts.
  • Explicitly state that all features and workflows are supported on Linux and provide troubleshooting tips for common Linux issues.
  • Balance references to Windows tools (PowerShell, Visual Studio) with Linux alternatives (Bash, Vim, nano, etc.) throughout the documentation.
GitHub Create Pull Request
Data Factory Configure a virtual network for express injection of Azure-SSIS integration runtime ...-integration-runtime-express-virtual-network-injection.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows environments, primarily through the use of PowerShell scripts for custom setup and the absence of Linux/bash examples. The instructions for configuring custom DNS servers reference a setup script that includes a .ps1 (PowerShell) file, with no mention of Linux shell scripts or cross-platform alternatives. Related content also highlights Azure PowerShell as a method for joining the integration runtime to a virtual network, without equivalent coverage for Azure CLI or bash scripting. There is no guidance for users operating in Linux environments.
Recommendations
  • Provide equivalent Linux/bash examples for custom setup, such as a bash script alternative to setupdnsserver.ps1.
  • Include instructions for using Azure CLI to join Azure-SSIS IR to a virtual network, alongside PowerShell examples.
  • Reference cross-platform tools and patterns where possible, and clarify which steps are OS-agnostic.
  • Explicitly state platform requirements or limitations for provided scripts, and offer guidance for Linux users.
  • Ensure that all downloadable resources (e.g., setup scripts) have both Windows and Linux versions, or are written in a cross-platform language (e.g., Python).
GitHub Create Pull Request
Data Factory Configure a virtual network for standard injection of Azure-SSIS integration runtime ...integration-runtime-standard-virtual-network-injection.md
High Priority View Details →
Scanned: 2026-01-10 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 bias toward Windows environments and tooling. PowerShell is the only scripting example provided for configuring UDRs, and references to Windows firewall rules and RDP troubleshooting are present. There are no Linux CLI (e.g., Bash, Azure CLI) examples or mentions of Linux-native tools or patterns. The use of Windows-centric terminology and tooling is prevalent, and alternative Linux approaches are not discussed.
Recommendations
  • Provide equivalent Azure CLI (az) or Bash script examples alongside PowerShell for all automation and configuration tasks.
  • Mention Linux firewall management (e.g., iptables, firewalld) where Windows firewall rules are referenced, especially for outbound/inbound port control.
  • Clarify that Azure-SSIS IR nodes can be managed from Linux environments and provide guidance for Linux users where relevant.
  • Include troubleshooting steps and remote access options for Linux (e.g., SSH) in addition to RDP and Windows tools.
  • Review terminology to ensure it is platform-neutral, and avoid assuming users are on Windows by default.
  • Add explicit notes or sections for Linux users, especially in areas like DNS configuration, NSG management, and scripting.
GitHub Create Pull Request
Data Factory Troubleshoot CI-CD, Azure DevOps, and GitHub issues ...ticles/data-factory/ci-cd-github-troubleshoot-guide.md
High Priority View Details →
Scanned: 2026-01-10 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 subtle Windows bias, primarily through references to PowerShell and Windows-centric tooling (e.g., PowerShell API, Azure PowerShell tabs, and patterns). There are no explicit Linux or bash examples, nor are cross-platform alternatives (such as Azure CLI or bash scripting) mentioned alongside PowerShell. This may make it less accessible for users working on Linux or macOS environments, or those preferring non-Windows automation tools.
Recommendations
  • Add equivalent Linux/bash/Azure CLI examples wherever PowerShell is referenced, especially in troubleshooting and automation sections.
  • Explicitly mention cross-platform tools (e.g., Azure CLI, bash scripts) and provide sample commands for both Windows and Linux environments.
  • Where the documentation refers to 'PowerShell API', clarify if Azure CLI or REST API alternatives exist and provide examples.
  • Ensure that troubleshooting steps and automation recommendations do not assume a Windows environment by default.
  • Include notes or links to platform-specific guidance (Windows, Linux, macOS) for common DevOps tasks.
GitHub Create Pull Request
Data Factory Manage packages with Azure-SSIS Integration Runtime package store ...actory/azure-ssis-integration-runtime-package-store.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows environments. All examples and instructions use Windows-specific tools (SSMS, dtutil, cmdkey, net use), Windows file paths, and command prompt syntax. There are no Linux or cross-platform alternatives mentioned, and the workflow assumes the user is operating in a Windows environment. Linux users are not provided with equivalent steps or tools, making the documentation inaccessible for non-Windows platforms.
Recommendations
  • Provide Linux-compatible instructions for connecting to Azure Files (e.g., using smbclient, mount.cifs, or Azure CLI).
  • Include dtutil usage examples on Linux, or clarify if dtutil is unavailable and suggest alternatives (such as Azure Data Factory REST API, Azure CLI, or PowerShell Core on Linux).
  • Mention cross-platform tools for managing SSIS packages, or clarify platform limitations.
  • Add notes about SSMS alternatives for Linux (such as Azure Data Studio, if applicable), or clarify that SSMS is Windows-only.
  • Reorder sections or add explicit notes to avoid assuming Windows as the default platform.
  • Where Windows command prompt syntax is used, offer Bash equivalents for Linux/macOS.
GitHub Create Pull Request
Data Factory Built-in and preinstalled components on Azure-SSIS Integration Runtime ...lt-in-preinstalled-components-ssis-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively describes Azure-SSIS Integration Runtime as running on Windows Server 2019 and lists only Windows-based components, drivers, and tasks. There is no mention of Linux support, alternatives, or examples. All built-in/preinstalled tools are Windows-centric, and the documentation does not provide parity or guidance for Linux environments.
Recommendations
  • Explicitly state the lack of Linux support and clarify platform limitations early in the documentation.
  • If possible, provide information about Linux alternatives or similar Azure services that support Linux workloads.
  • Offer guidance or links for users seeking cross-platform data integration solutions.
  • Consider adding a comparison table or section that highlights differences between Windows and Linux support for SSIS in Azure.
  • If future Linux support is planned, mention it and provide a roadmap or preview.
GitHub Create Pull Request
Data Factory Choose the right integration runtime configuration for your scenario ...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/choose-the-right-integration-runtime-configuration.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell in the context of creating and sharing self-hosted integration runtimes, and by omitting explicit Linux examples or instructions for installation, management, or troubleshooting. The documentation assumes the reader is familiar with Windows-centric tools and patterns, such as referencing 'customer managed machine' without specifying OS options, and linking to PowerShell-based guides before mentioning any cross-platform alternatives. There is no mention of Linux-specific installation steps, tools, or considerations, nor are there examples for Linux users.
Recommendations
  • Include explicit Linux installation and configuration instructions for self-hosted integration runtime, alongside Windows guides.
  • Provide Linux shell (bash) examples for common tasks such as setup, diagnostics, and sharing, in addition to PowerShell.
  • Reference cross-platform tools and patterns (e.g., systemd for service management on Linux, Linux firewall configuration) where appropriate.
  • Clarify that self-hosted integration runtime can be installed on both Windows and Linux machines, and highlight any OS-specific considerations.
  • Ensure parity in troubleshooting and maintenance documentation for both Windows and Linux environments.
GitHub Create Pull Request
Data Factory Compute environments .../main/articles/data-factory/compute-linked-services.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the Azure Batch section, which references PowerShell cmdlets (New-AzBatchAccount, New-AzBatchPool) and links to Windows-centric articles before mentioning the Azure portal. The use of Microsoft Azure Storage Explorer as a recommended tool for managing blob storage containers is also a Windows-oriented choice, as it is a Microsoft product with a Windows-first user base. There are no explicit Linux command-line examples, nor are Linux-native tools or patterns suggested. However, the HDInsight examples do default to Linux-based clusters, and the JSON configuration samples specify 'osType': 'Linux', which helps balance the bias. Overall, the documentation is Azure-centric but leans toward Windows tools and patterns in certain sections.
Recommendations
  • Include Linux-native command-line examples (e.g., using Azure CLI or Bash scripts) alongside or before PowerShell examples for Azure Batch and other services.
  • Mention cross-platform or Linux-friendly tools for blob storage management (such as azcopy, Azure CLI, or third-party tools) in addition to Microsoft Azure Storage Explorer.
  • When referencing articles or guides, provide links to both PowerShell and Azure CLI documentation, and clarify which commands are cross-platform.
  • Explicitly state platform compatibility for all tools and commands, and highlight Linux usage patterns where relevant.
  • Add troubleshooting steps or examples that use SSH and Linux utilities for cluster management, not just Windows-centric approaches.
GitHub Create Pull Request
Data Factory Linked services ...main/articles/data-factory/concepts-linked-services.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias by listing PowerShell as a primary automation tool for creating linked services, referencing Windows-centric tools (PowerShell, .NET), and omitting Linux-native equivalents (such as Bash, CLI, or Python SDK). Examples and quickstarts prioritize Windows tools, with no mention or examples for Linux command-line usage or scripting. This may hinder discoverability and usability for Linux users.
Recommendations
  • Add examples for creating linked services using Azure CLI and Bash scripts, which are platform-agnostic and widely used on Linux.
  • Include references and quickstarts for Python SDK, which is cross-platform and popular among Linux users.
  • Ensure that all tool and SDK lists mention Linux-compatible options before or alongside Windows-specific tools.
  • Provide explicit instructions or links for Linux users, such as installing and using Azure CLI or Python SDK on Linux.
  • Balance PowerShell examples with equivalent Bash/CLI examples to ensure parity and inclusivity.
GitHub Create Pull Request
Data Factory Pipelines and activities ...articles/data-factory/concepts-pipelines-activities.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily through its references and links to PowerShell-based quickstarts and tutorials (e.g., 'quickstart-create-data-factory-powershell.md', 'tutorial-transform-data-spark-powershell.md'), with no mention of Linux shell, CLI, or cross-platform alternatives. The sample walkthroughs and related content exclusively use PowerShell, which is traditionally associated with Windows environments. There are no examples or guidance for Linux users, such as using Azure CLI, Bash, or other Linux-native tools.
Recommendations
  • Add equivalent walkthroughs and quickstarts using Azure CLI and Bash scripts, ensuring Linux users have clear guidance.
  • Include links to documentation or tutorials for creating and managing pipelines using cross-platform tools (e.g., Azure CLI, REST API, SDKs).
  • When referencing sample pipelines or activities, provide examples for both PowerShell and CLI/Bash, or note that the steps apply equally to Linux environments.
  • Explicitly mention platform neutrality where applicable, and avoid implying PowerShell is the only or preferred method.
  • In 'Related content', add links to Linux/CLI-based tutorials and resources.
GitHub Create Pull Request
Data Factory Roles and permissions for Azure Data Factory ...in/articles/data-factory/concepts-roles-permissions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page references PowerShell as an example tool for updating a data factory, without mentioning Linux equivalents such as Azure CLI or Bash scripting. There are no examples or instructions for Linux or cross-platform command-line tools, and the only tooling mentioned is PowerShell, which is traditionally associated with Windows environments.
Recommendations
  • Add Azure CLI examples for managing Data Factory resources, alongside or instead of PowerShell.
  • Explicitly mention that Azure CLI and SDKs are cross-platform and provide sample commands for Linux/macOS users.
  • Where PowerShell is referenced, clarify that PowerShell Core is available on Linux/macOS, or provide alternative instructions using Bash/CLI.
  • Ensure that all tooling guidance is platform-neutral or includes both Windows and Linux/macOS options.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Examples and instructions frequently reference Windows-centric tools such as PowerShell and SQL Server Management Studio (SSMS), and scripting examples are provided only for T-SQL (typically used with SSMS on Windows). There are no explicit Linux CLI or cross-platform alternatives mentioned for key operations, and PowerShell is referenced in the metadata and instructions before any Linux equivalents. The documentation assumes the use of Windows-based management tools and does not provide parity for Linux users.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash for all steps currently described with PowerShell or SSMS.
  • Include instructions for managing Azure-SSIS IR and failover groups using cross-platform tools (e.g., Azure CLI, Data Studio) alongside Windows tools.
  • Explicitly mention that SSMS is Windows-only and suggest Azure Data Studio or other cross-platform alternatives for T-SQL scripting.
  • Add notes or sections for Linux/macOS users, clarifying how to perform each step without Windows-specific tools.
  • Ensure that all code samples and UI instructions are platform-neutral or provide alternatives for both Windows and Linux environments.
GitHub Create Pull Request
Data Factory Datasets ...cles/data-factory/concepts-datasets-linked-services.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 prominently listing PowerShell as a primary tool for creating datasets, both in the main text and in the quickstart section. There are no Linux-specific examples, nor is there mention of Linux-native tools (such as Bash, Azure CLI, or scripting patterns) for dataset creation. The ordering of examples and quickstarts places PowerShell before REST API and omits Linux parity, suggesting a Windows-first approach.
Recommendations
  • Add examples and quickstarts for Azure CLI, which is cross-platform and widely used on Linux.
  • Include Bash scripting examples for dataset creation, especially for REST API usage.
  • Reorder the list of tools and quickstarts to avoid placing PowerShell first; consider grouping by platform-neutral tools (REST API, .NET, Azure CLI) before platform-specific ones.
  • Explicitly mention that all SDKs and APIs can be used from Linux environments, and provide guidance or links for Linux users.
  • Where PowerShell is referenced, add a parallel example using Bash or Azure CLI.
GitHub Create Pull Request
Data Factory Pipeline parameters and variables ...articles/data-factory/concepts-parameters-variables.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 only PowerShell-based tutorials in the 'Related content' section, which implies a preference for Windows tooling and workflows. There are no Linux or cross-platform CLI examples, nor are Linux tools or patterns mentioned. This may make it harder for Linux users to follow or adapt the instructions.
Recommendations
  • Add equivalent tutorials using Azure CLI and/or Bash scripts for pipeline creation and management.
  • Explicitly mention cross-platform options for automation, such as Azure CLI, REST API, or SDKs, alongside PowerShell.
  • Ensure that examples and screenshots do not assume a Windows environment; provide Linux/macOS alternatives where relevant.
  • In the 'Related content' section, balance PowerShell links with links to Linux-friendly guides.
GitHub Create Pull Request
Data Factory Pipeline execution and triggers ...s/data-factory/concepts-pipeline-execution-triggers.md
High Priority View Details →
Scanned: 2026-01-10 00:00
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 Windows bias in several ways: PowerShell is the only CLI example provided for manual pipeline execution, and it is listed before REST API and Python SDK options. There is no mention of Linux-native tools (such as Azure CLI or Bash), nor are there any Linux shell examples. The documentation references Windows-centric tooling (PowerShell) and omits equivalent Linux command-line workflows, which may disadvantage users on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for pipeline execution, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Provide Bash or shell script examples for invoking REST API endpoints, demonstrating how Linux users can trigger pipelines.
  • Reorder API/SDK sections so that platform-neutral options (REST API, Python SDK, Azure CLI) appear before Windows-specific tools like PowerShell.
  • Explicitly mention that all API/SDK methods are available on Linux, and provide links or instructions for installing and using them on Linux.
  • Include notes or examples for macOS users where relevant.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based configuration examples and referencing Windows-centric tools and patterns (e.g., SSIS, PowerShell scripts). There are no examples or instructions for configuring Azure-SSIS IR using Linux-native tools, shells, or cross-platform CLI methods. This may hinder Linux users or those preferring non-Windows environments from easily following the guidance.
Recommendations
  • Provide equivalent configuration examples using Azure CLI (az), which is cross-platform and widely used on Linux.
  • Include bash shell script snippets for common configuration tasks, alongside PowerShell examples.
  • Explicitly mention that PowerShell Core is available on Linux, and clarify any platform-specific differences.
  • Reference Linux-compatible tools and workflows where possible, such as using environment variables and file paths in Linux format.
  • Add a section or note on configuring Azure-SSIS IR from Linux/macOS environments, including troubleshooting tips for non-Windows platforms.
GitHub Create Pull Request
Data Factory Copy data from Amazon RDS for SQL Server ...es/data-factory/connector-amazon-rds-for-sql-server.md
High Priority View Details →
Scanned: 2026-01-10 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 Windows bias in several areas: authentication methods prioritize Windows authentication, troubleshooting steps and configuration instructions are exclusively based on Windows tools (SQL Server Management Studio, Configuration Manager, Windows Firewall), and references to enabling features or remote access link to Windows-specific documentation. There are no Linux equivalents or examples provided for connecting, configuring, or troubleshooting Amazon RDS for SQL Server from Linux environments.
Recommendations
  • Add Linux-based connection and troubleshooting instructions, such as using sqlcmd, Azure Data Studio, or other cross-platform tools.
  • Include examples for configuring Amazon RDS for SQL Server connectivity and authentication from Linux environments (e.g., using Kerberos for Windows authentication on Linux, or using SQL authentication from Linux).
  • Provide guidance for managing firewalls and network access on Linux (e.g., using iptables, ufw) alongside Windows Firewall instructions.
  • Reference cross-platform documentation and tools where possible, and avoid linking exclusively to Windows-specific docs.
  • Clearly indicate when a step or tool is Windows-only, and offer Linux alternatives in parallel.
GitHub Create Pull Request
Data Factory Copy and transform data in Azure SQL Database .../articles/data-factory/connector-azure-sql-database.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through exclusive references to Windows-based tools (such as SQL Server Management Studio) for database user and permission management, and by omitting equivalent Linux tooling or command-line alternatives. All examples and instructions for connecting to Azure SQL Database, managing users, and configuring authentication reference SQL Server Management Studio, which is a Windows-only application. There are no examples using cross-platform tools (e.g., Azure CLI, sqlcmd, or Data Studio), nor are Linux-specific instructions or screenshots provided. This may hinder Linux users or those working in non-Windows environments from following the documentation seamlessly.
Recommendations
  • Include examples using cross-platform tools such as Azure CLI, sqlcmd, or Azure Data Studio for database management tasks (e.g., creating users, granting permissions).
  • Provide instructions and screenshots for performing key steps (such as running T-SQL commands) on Linux and macOS environments.
  • Mention and link to installation guides for cross-platform tools where appropriate.
  • Where SQL Server Management Studio is referenced, add alternative steps using command-line or GUI tools available on Linux.
  • Explicitly state that all operations can be performed from Linux environments and clarify any differences in workflow or prerequisites.
GitHub Create Pull Request
Data Factory Copy data to and from Azure Table storage ...articles/data-factory/connector-azure-table-storage.md
High Priority View Details →
Scanned: 2026-01-10 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 bias toward Windows by providing only PowerShell commands for generating a Shared Access Signature (SAS) token and not mentioning or providing equivalent Linux/CLI commands. There are no examples or guidance for Linux users, such as Azure CLI or cross-platform scripting, in any authentication or setup steps. The only explicit command-line example is Windows PowerShell, and no Linux tools or workflows are referenced.
Recommendations
  • Provide equivalent Azure CLI commands for generating SAS tokens, alongside or before PowerShell examples.
  • Explicitly mention that both Windows and Linux users are supported, and provide cross-platform instructions where possible.
  • Where PowerShell is used, add a corresponding Bash/Azure CLI example to ensure Linux parity.
  • Review other sections for implicit Windows-first assumptions (such as screenshots or terminology) and ensure cross-platform language and visuals.
  • Add a short section or note for Linux/macOS users, referencing relevant tools and commands.
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
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Dynamics XRM tooling (which is historically Windows/.NET-centric), focusing on Active Directory authentication (primarily a Windows technology), and omitting any Linux-specific instructions or examples. No Linux command-line, shell, or configuration examples are provided; all authentication and integration patterns assume Windows-based infrastructure and tools. The documentation does not mention cross-platform alternatives, nor does it address Linux deployment scenarios or integration runtimes on Linux hosts.
Recommendations
  • Add explicit instructions and examples for Linux environments, such as using Azure Integration Runtime on Linux or self-hosted IR on Linux servers.
  • Reference cross-platform tools and SDKs (e.g., REST API, Python SDK) for interacting with Dynamics, rather than only XRM tooling.
  • Include authentication patterns that work in Linux environments, such as service principal and managed identity, and clarify how to configure these on Linux.
  • Provide parity in examples: for every Windows/Active Directory/PowerShell example, include a Linux/bash/CLI equivalent.
  • Clarify which features or connectors are platform-agnostic and which require Windows, and suggest alternatives for Linux users.
  • Mention any limitations or requirements for Linux deployments, especially for self-hosted integration runtime.
GitHub Create Pull Request
Data Factory Copy data from an HTTP source ...docs/blob/main/articles/data-factory/connector-http.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation demonstrates Windows bias primarily in the tools and patterns mentioned for testing HTTP requests, such as Visual Studio and PowerShell's Invoke-RestMethod, without mentioning Linux or cross-platform alternatives. The certificate management instructions are exclusively Windows-centric, referencing MMC and Windows certificate stores, with no guidance for Linux environments. Windows authentication is listed as a supported authentication type, but there is no discussion of Linux equivalents or considerations.
Recommendations
  • Include Linux and cross-platform tools for testing HTTP requests, such as curl, wget, or httpie, alongside PowerShell and Visual Studio.
  • Add instructions for managing client certificates on Linux, such as using OpenSSL, PEM files, and configuring permissions for the integration runtime on Linux hosts.
  • Clarify how 'Windows' authentication type behaves on non-Windows self-hosted integration runtimes, and provide guidance or alternatives for Linux environments.
  • Ensure that examples and tool recommendations are presented in a platform-neutral order, or explicitly provide both Windows and Linux options.
  • Where possible, link to documentation for Linux certificate stores and authentication mechanisms relevant to Azure Data Factory/Synapse integration runtime.
GitHub Create Pull Request
Data Factory Transform data using Hive in Azure Virtual Network ...actory/tutorial-transform-data-hive-virtual-network.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All command-line instructions use Azure PowerShell, with no mention of Azure CLI, Bash, or Linux shell alternatives. Instructions for editing system files (e.g., hosts file) reference Windows paths only, and the setup of self-hosted integration runtime assumes use of Windows VMs. There are no examples or guidance for performing these steps on Linux systems, nor is there mention of Linux-compatible tools or workflows.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell examples, and indicate which commands work on Linux/Mac.
  • Include instructions for setting up self-hosted integration runtime on Linux VMs, with download and registration steps for Linux.
  • When referencing system file edits (e.g., hosts file), include Linux paths (e.g., /etc/hosts) and syntax.
  • Add notes or sections highlighting cross-platform compatibility and any OS-specific considerations.
  • Mention and demonstrate use of Bash or other Linux shells for file operations and scripting where applicable.
GitHub Create Pull Request
Data Factory Copy data from/to a file system ...ob/main/articles/data-factory/connector-file-system.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several ways. Windows-style paths and conventions (e.g., backslashes, UNC paths) are used throughout, with examples and explanations tailored to Windows file shares. References to enabling local access under Self-hosted Integration Runtime point to PowerShell commands, with no Linux equivalent or parity. Linux is mentioned only briefly (suggesting Samba installation), but no Linux-specific configuration, path examples, or troubleshooting are provided. All sample JSON and UI screenshots use Windows conventions, and there is no demonstration of Linux file system integration beyond the Samba note.
Recommendations
  • Provide Linux-specific examples for file paths (e.g., /mnt/share, /home/user/data) alongside Windows examples.
  • Include instructions and screenshots for configuring Linux file shares (e.g., Samba setup, permissions, mounting) in Azure Data Factory/Synapse.
  • Offer Linux command-line equivalents (e.g., bash scripts, systemctl commands) for tasks currently documented only with PowerShell.
  • Clarify differences in authentication, path syntax, and integration runtime setup between Windows and Linux environments.
  • Add troubleshooting and best practices sections for common Linux file system issues (e.g., SELinux, NFS, Samba configuration).
  • Ensure parity in documentation structure, so Linux users can follow step-by-step guides as easily as Windows users.
GitHub Create Pull Request
Data Factory Copy and transform data from Microsoft 365 (Office 365) ...lob/main/articles/data-factory/connector-office-365.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several ways: Windows-centric tools such as Azure PowerShell are listed among the main options for creating pipelines, with no mention of Linux-specific command-line tools or shell scripting. The only example for converting certificates to base64 references a PowerShell-based method and links to a PowerShell-focused blog, with no alternative for Linux (e.g., using OpenSSL). There are no Linux shell or CLI examples, and Windows tools/patterns are mentioned before or instead of Linux equivalents throughout the page.
Recommendations
  • Add Linux shell (bash) and OpenSSL examples for certificate conversion, alongside the PowerShell method.
  • Include references to cross-platform CLI tools (e.g., Azure CLI) and provide examples for both Windows and Linux environments.
  • Ensure that tutorials and quickstarts mention Linux compatibility and provide parity in step-by-step instructions for Linux users.
  • Explicitly state platform requirements or limitations where relevant, and offer guidance for Linux users where Windows-specific tools are referenced.
  • Balance the order of tool presentation so that Windows and Linux options are listed together, or alternate which is mentioned first.
GitHub Create Pull Request
Data Factory Copy data from Netezza ...s/blob/main/articles/data-factory/connector-netezza.md
High Priority View Details →
Scanned: 2026-01-10 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 by explicitly mentioning Windows versions as prerequisites for the self-hosted integration runtime, while omitting Linux equivalents or guidance. There are no Linux-specific instructions, examples, or screenshots. The installation instructions for the IBM Netezza ODBC driver do not specify OS, but the prerequisite section links only to Windows documentation. No Linux shell or configuration examples are provided, and the documentation does not address Linux compatibility or troubleshooting.
Recommendations
  • Add explicit instructions and prerequisites for Linux environments, including supported distributions and versions for self-hosted integration runtime.
  • Provide Linux-specific examples for installing the IBM Netezza ODBC driver, including shell commands and package requirements.
  • Include troubleshooting steps and configuration notes for Linux users.
  • Update references and links to include both Windows and Linux documentation where applicable.
  • Add screenshots or terminal output examples for Linux environments alongside Windows UI images.
GitHub Create Pull Request
← Previous Page 7 of 40 Next →