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 51-75 of 1000 flagged pages
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-11 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 exhibits Windows bias in several ways: it provides only PowerShell script examples for configuring UDRs, references Windows-specific tools and concepts (such as Windows firewall rules and RDP), and omits equivalent Linux/CLI/Bash examples or guidance. Additionally, Windows-centric terminology (like 'Windows firewall rule') and troubleshooting steps (RDP via port 3389) are presented without Linux alternatives. The page does not mention or demonstrate how to perform these tasks using cross-platform tools or Linux-native approaches, and Windows/PowerShell methods are presented first and exclusively.
Recommendations
  • Add equivalent Azure CLI and Bash script examples alongside PowerShell scripts for all configuration steps, especially for UDR and NSG management.
  • Include guidance for Linux users on how to access and troubleshoot Azure-SSIS IR nodes (e.g., using SSH if supported, or alternatives to RDP).
  • Clarify whether Windows firewall rules are relevant only to Windows-based nodes, and provide information on Linux firewall configuration if Linux nodes are supported.
  • Ensure that all references to management tools (e.g., Azure portal, PowerShell) are balanced with cross-platform alternatives (Azure CLI, REST API).
  • Explicitly state platform requirements and limitations (e.g., if only Windows nodes are supported, clarify this; if Linux is supported, provide parity in documentation).
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Several troubleshooting steps and automation recommendations reference PowerShell and Windows-centric tools (e.g., PowerShell API, Azure PowerShell tabs, Nunit for C#), but do not provide equivalent Linux or cross-platform examples. There are no explicit Bash, Linux shell, or platform-neutral CLI instructions, and the use of Windows tooling is assumed in some scenarios. Some SDK and automation examples mention .NET and PowerShell before Python, and there is a lack of parity in example scripts for Linux users.
Recommendations
  • Add equivalent Bash or Linux shell examples alongside PowerShell instructions, especially for ARM template deployment and CI/CD automation.
  • Where PowerShell is referenced, also provide Azure CLI commands and note cross-platform compatibility.
  • Include examples using Linux-native tools (e.g., shell scripts, pytest for Python) in unit testing and automation sections.
  • Ensure that references to SDKs and test frameworks mention Python and other cross-platform options before or alongside .NET/C#.
  • Clarify that Azure DevOps and GitHub actions can be run on both Windows and Linux agents, and provide sample YAML for both.
  • Review all troubleshooting steps to ensure Linux users are not excluded and have clear, actionable guidance.
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-11 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 primarily through its use of Windows-specific tooling and examples. The only explicit script example for custom DNS setup references a .cmd (batch) file and a PowerShell (.ps1) script, both Windows-centric formats, with no mention of Linux shell equivalents. The related content section highlights Azure PowerShell as the command-line method for joining Azure-SSIS IR to a virtual network, without reference to Azure CLI or other cross-platform tools. There are no Linux/bash examples or guidance for users operating in non-Windows environments.
Recommendations
  • Provide equivalent Linux/bash script examples for custom DNS setup, such as a shell script alternative to main.cmd and setupdnsserver.ps1.
  • Reference and document the use of Azure CLI for all operations currently described with Azure PowerShell, ensuring parity for Linux/macOS users.
  • Explicitly mention cross-platform compatibility and provide guidance for users on Linux or macOS, including any prerequisites or differences in workflow.
  • Where possible, use platform-neutral terminology and tooling, or provide side-by-side instructions for both Windows and Linux environments.
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-11 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 is heavily oriented toward Windows environments. All examples and instructions use Windows-specific tools such as SSMS, dtutil, cmdkey, net use, and DOS batch scripting. There are no Linux or cross-platform alternatives provided, and the workflow assumes access to Windows-only utilities and patterns. Linux users are not given guidance for managing SSIS packages or connecting to Azure Files, nor are any Linux-compatible tools or commands mentioned.
Recommendations
  • Provide equivalent instructions and examples for Linux environments, such as using Azure CLI, REST API, or other cross-platform tools for package management.
  • Document how to connect to Azure Files from Linux (e.g., using SMB mounting commands like 'mount -t cifs').
  • Clarify whether dtutil or SSMS functionality is available via Docker containers or remote desktop solutions for Linux users, or suggest alternatives.
  • Include notes on package management via Azure Data Factory portal or APIs, which are accessible from any OS.
  • Add explicit statements about OS requirements and alternatives for non-Windows users at the start of the documentation.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric: it specifies Windows Server 2019 as the only OS, lists only Windows-based drivers and providers, and all referenced components are designed for SSIS, which is a Windows-only technology. There are no Linux equivalents, examples, or mentions of cross-platform alternatives. The documentation does not acknowledge or provide guidance for Linux users, nor does it discuss compatibility or limitations for non-Windows environments.
Recommendations
  • Explicitly state that Azure-SSIS IR is Windows-only and clarify the lack of Linux support.
  • Provide a comparison table or section outlining alternatives for Linux users, such as Azure Data Factory Mapping Data Flows, DataBricks, or other ETL tools that run on Linux.
  • Add guidance or links for users seeking cross-platform data integration solutions.
  • If any components or tasks have cross-platform equivalents (e.g., Hadoop, FTP, HTTP), mention how those can be used or configured from Linux environments outside of SSIS.
  • Consider including a FAQ or note addressing the absence of Linux support and recommending next steps for Linux-centric workloads.
GitHub Create Pull Request
Data Factory Compute environments .../main/articles/data-factory/compute-linked-services.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation demonstrates some Windows bias, notably in the Azure Batch section, where PowerShell cmdlets and Windows-centric tools are referenced exclusively and before any Linux alternatives. The use of 'CMDLETs & APIS' in VM sizing also implies a Windows-first approach. There are no explicit Linux command-line examples or references to Linux-native tooling for cluster management or storage operations, and deletion of blob containers is suggested via Microsoft Azure Storage Explorer (a Windows-focused GUI tool) rather than cross-platform or Linux-native alternatives.
Recommendations
  • Provide Linux CLI (bash/azcli) examples alongside or before PowerShell cmdlets for Azure Batch and other services.
  • Reference cross-platform tools (e.g., azcopy, Azure CLI) for storage management and blob deletion, not just Microsoft Azure Storage Explorer.
  • Clarify that all JSON configuration examples are OS-agnostic and, where relevant, show how to perform equivalent operations from Linux environments.
  • Explicitly mention Linux support and parity in sections that discuss tooling, authentication, and integration runtimes.
  • Add links or examples for managing Azure resources from Linux/macOS, such as using Azure CLI, REST APIs, or Terraform.
GitHub Create Pull Request
Data Factory Datasets ...cles/data-factory/concepts-datasets-linked-services.md
High Priority View Details →
Scanned: 2026-01-11 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 listing PowerShell as a primary tool for creating datasets, both in the 'Create datasets' section and in the Quickstarts, without mentioning Linux-specific tools or providing CLI/bash examples. PowerShell is a Windows-centric tool, and its prominence suggests a preference for Windows environments. There are no Linux shell (bash) or cross-platform CLI examples, nor is the Azure CLI (which is cross-platform) mentioned. The ordering of tools (PowerShell before REST API and Azure portal) further reinforces the Windows-first approach.
Recommendations
  • Add Azure CLI examples for creating datasets, as Azure CLI is cross-platform and widely used on Linux.
  • Include bash shell script examples or references for Linux users.
  • Reorder the list of tools and quickstarts to avoid placing PowerShell first; consider alphabetical or usage-based ordering.
  • Explicitly mention that all SDKs and APIs are available on Linux and macOS, not just Windows.
  • Provide links to Linux-specific documentation or quickstarts where available.
GitHub Create Pull Request
Data Factory Pipeline parameters and variables ...articles/data-factory/concepts-parameters-variables.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias primarily through its exclusive use of PowerShell-based tutorials in the 'Related content' section. There are no examples or references to Linux tools, Bash, or cross-platform alternatives. The tutorials and quickstarts referenced are PowerShell-centric, which is most commonly used on Windows, and there is no mention of Linux command-line equivalents or parity.
Recommendations
  • Include Linux/Bash-based examples and tutorials alongside PowerShell ones.
  • Reference cross-platform tools (e.g., Azure CLI, REST API) in addition to PowerShell.
  • Ensure that quickstart and tutorial links cover both Windows and Linux environments.
  • Add explicit notes or sections about how to perform equivalent actions on Linux systems.
  • Review screenshots and UI instructions to confirm they are not Windows-specific, or provide Linux-specific guidance where relevant.
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-11 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 page demonstrates Windows bias in several ways: Azure PowerShell is featured prominently as a method for manual pipeline execution, with a full example command and a dedicated quickstart link. There are no equivalent CLI or shell examples for Linux users (e.g., Azure CLI, Bash, curl). The order of API/SDK methods lists PowerShell before REST API and Python SDK, and there is no mention of Linux-specific tools or cross-platform command-line usage. The documentation assumes familiarity with PowerShell and Windows-centric tooling, while omitting Linux-native or cross-platform alternatives.
Recommendations
  • Add Azure CLI examples for pipeline execution, showing equivalent commands to PowerShell.
  • Include Bash/curl examples for REST API usage, demonstrating manual pipeline runs from Linux/macOS.
  • Reorder the API/SDK methods to present cross-platform or OS-neutral options (e.g., REST API, Azure CLI, Python SDK) before Windows-specific tools.
  • Explicitly mention that all API/SDK methods are cross-platform, and clarify which tools are available on Linux/macOS.
  • Provide links to Linux/macOS setup guides for Azure CLI and Python SDK.
  • Avoid assuming PowerShell as the default scripting environment; offer parity for Bash and other shells.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based configuration examples, referencing Windows-centric tools and patterns, and omitting equivalent Linux or cross-platform instructions. There are no Bash, Azure CLI, or Linux shell examples, and the guidance assumes familiarity with Windows/PowerShell environments. This limits accessibility for users on Linux or macOS platforms.
Recommendations
  • Provide equivalent configuration examples using Azure CLI and Bash scripts alongside PowerShell.
  • Explicitly mention cross-platform support and clarify which steps are OS-agnostic.
  • Include references to Linux/macOS environments where relevant, such as using Azure CLI on those platforms.
  • Add a section or note on how to perform these configurations from Linux or macOS, including any prerequisites or differences.
  • Ensure that documentation links and referenced tutorials include both Windows and Linux instructions.
GitHub Create Pull Request
Data Factory Copy and transform data in Azure SQL Managed Instance ...s/data-factory/connector-azure-sql-managed-instance.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias primarily through exclusive references to SQL Server Management Studio (SSMS) for administrative tasks, such as creating logins and users, and does not mention or provide examples for Linux-based tools (e.g., sqlcmd, Azure Data Studio) or CLI alternatives. All step-by-step instructions for configuring authentication and permissions assume the use of SSMS, a Windows-only tool, and no Linux or cross-platform equivalents are suggested. There are no PowerShell-specific examples, but the overall pattern is Windows-centric, and Linux parity is lacking.
Recommendations
  • Include instructions and examples for performing administrative tasks (e.g., creating logins, users, granting permissions) using cross-platform tools such as sqlcmd, Azure Data Studio, or Azure CLI.
  • Explicitly mention that SSMS is Windows-only and suggest alternatives for users on Linux or macOS.
  • Provide sample commands for Linux environments, especially for authentication and connectivity setup.
  • Add a section or callout for Linux users, outlining any differences or additional steps required.
  • Ensure screenshots and UI references are supplemented with CLI or script-based alternatives where possible.
GitHub Create Pull Request
Data Factory Linked services ...main/articles/data-factory/concepts-linked-services.md
High Priority View Details →
Scanned: 2026-01-11 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 prominently featuring PowerShell as a primary automation tool, listing it before other SDKs/APIs, and omitting explicit Linux or cross-platform command-line examples (such as Azure CLI or bash scripting). The listed tooling (PowerShell, .NET) is Windows-centric, and there is no mention of Linux-native workflows or parity in example commands or instructions.
Recommendations
  • Add Azure CLI examples for creating linked services, as Azure CLI is cross-platform and widely used on Linux.
  • Include bash scripting or Linux shell examples where automation is discussed, alongside PowerShell.
  • Explicitly mention Linux support and provide instructions for Linux users, including any prerequisites or differences in experience.
  • Reorder tooling lists to avoid always listing Windows tools first; alternate or group by platform-neutral tools.
  • Reference cross-platform SDKs (such as Python) and provide example usage for creating linked services.
  • Ensure screenshots and UI instructions clarify that the web portal and REST API are platform-agnostic.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page references updating a data factory from PowerShell or the SDK, but does not mention or provide examples for Linux-native tools or command-line interfaces (such as Azure CLI or Bash scripting). PowerShell is primarily a Windows tool, and its mention without Linux alternatives suggests a Windows bias. No Linux-specific instructions or parity examples are provided.
Recommendations
  • Include examples for updating a data factory using Azure CLI, which is cross-platform and widely used on Linux.
  • Mention Bash scripting or other Linux-native automation methods alongside PowerShell.
  • Ensure that all instructions referencing PowerShell also provide equivalent steps for Linux users, or clarify platform compatibility.
  • Add explicit notes about SDK usage on Linux, including installation and usage examples.
GitHub Create Pull Request
Data Factory Pipelines and activities ...articles/data-factory/concepts-pipelines-activities.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its reliance on PowerShell-based walkthroughs and examples, both in the 'Related content' section and in references to quickstarts and tutorials. There is an absence of Linux or cross-platform CLI examples (e.g., Azure CLI, Bash), and the documentation does not mention Linux tools or provide parity for Linux users. The referenced guides and tutorials are PowerShell-centric, suggesting Windows as the default environment for automation and scripting.
Recommendations
  • Add equivalent walkthroughs and tutorials using Azure CLI and Bash scripts, ensuring Linux users have clear guidance.
  • In 'Related content', include links to quickstarts and tutorials for Linux and cross-platform environments, not just PowerShell.
  • Explicitly mention that pipelines and activities can be managed from Linux/macOS environments, and provide examples.
  • Where PowerShell is referenced, add parallel instructions for Azure CLI or REST API usage.
  • Review referenced sample code and ensure it is platform-agnostic or provide alternatives for Linux users.
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-11 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 demonstrates a bias toward Windows environments by referencing PowerShell, SSMS (SQL Server Management Studio), and Windows-centric orchestration tools and patterns. Examples and instructions are given primarily for Azure portal, ADF UI, SSMS, and PowerShell, with no mention of Linux-native tools or cross-platform alternatives. The scripting and job management sections rely on SSMS and T-SQL, both traditionally Windows-focused. There are no examples or guidance for Linux users, such as using Azure CLI, Data Studio, or other cross-platform tools.
Recommendations
  • Provide equivalent examples using Azure CLI for all steps currently shown with PowerShell or portal/ADF UI.
  • Include instructions for using cross-platform tools such as Azure Data Studio instead of or alongside SSMS.
  • Explicitly mention Linux compatibility and provide steps for Linux environments, including package installation and orchestration.
  • Add notes or sections for users operating from macOS or Linux, highlighting any differences or additional requirements.
  • Ensure all code snippets and automation scripts are runnable on Linux (e.g., bash scripts, CLI commands) and not just PowerShell.
  • Reference cross-platform documentation and tools where available, and avoid assuming SSMS or PowerShell as the default.
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-11 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 demonstrates a Windows bias in several areas. Windows authentication is presented as a primary option alongside SQL authentication, with examples and property tables. Troubleshooting steps and configuration instructions exclusively reference Windows tools (SQL Server Management Studio, SQL Server Configuration Manager, Windows Firewall), and all links for further configuration point to Windows-specific documentation. There are no Linux equivalents or cross-platform alternatives provided for connection setup, authentication, or troubleshooting, nor are Linux command-line tools (such as sqlcmd) or Linux firewall configuration steps mentioned.
Recommendations
  • Add Linux-specific examples for connecting to Amazon RDS for SQL Server, including authentication and connection string formats.
  • Include troubleshooting steps for Linux environments, such as using sqlcmd, configuring firewalls with iptables or ufw, and setting up remote connections via Linux tools.
  • Reference cross-platform SQL Server management tools (e.g., Azure Data Studio) and provide instructions for both Windows and Linux.
  • Ensure that links to further documentation include Linux-relevant resources, not just Windows-specific ones.
  • Present Windows and Linux options in parallel, rather than listing Windows first or exclusively.
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-11 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 its exclusive references to Windows-based tools (e.g., SQL Server Management Studio) for database administration and setup tasks. There are no examples or mentions of Linux-based tools (such as Azure Data Studio, sqlcmd, or other cross-platform alternatives) for connecting to or managing Azure SQL Database. Additionally, instructions for tasks like creating contained database users and provisioning administrators are given only with Windows-centric tooling, and no Linux command-line or GUI alternatives are provided. This may hinder Linux users or those on non-Windows platforms from following the documentation seamlessly.
Recommendations
  • Include examples using cross-platform tools such as Azure Data Studio and sqlcmd for database administration tasks.
  • Explicitly mention that SQL Server Management Studio is a Windows-only tool and provide Linux/macOS alternatives.
  • Provide PowerShell and Bash (Azure CLI) equivalents for any setup or configuration steps.
  • Add screenshots or walkthroughs for Linux/macOS environments where UI steps are described.
  • Ensure that all code snippets and instructions are platform-agnostic or offer alternatives for both Windows and Linux users.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only PowerShell commands for generating a Shared Access Signature (SAS) token, without offering equivalent Linux/CLI or cross-platform alternatives. There are no examples or instructions for Linux users, such as using Azure CLI or REST API, and the only scripting example for SAS generation is specific to PowerShell, a Windows-centric tool.
Recommendations
  • Provide equivalent Azure CLI commands for generating SAS tokens, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash shell or REST API examples for SAS generation to ensure parity for Linux and macOS users.
  • When referencing scripting tools, mention both PowerShell and Azure CLI (or Bash) options, and present them side-by-side or in tabs.
  • Review the documentation for other areas where only Windows tools or workflows are referenced, and add Linux/macOS alternatives where appropriate.
  • Explicitly state that the instructions are platform-agnostic where possible, or clearly indicate when a step is Windows-specific and provide alternatives.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits Windows bias primarily in its guidance for testing HTTP requests, where it recommends Windows-centric tools such as Visual Studio and PowerShell's Invoke-RestMethod, without mentioning Linux alternatives. Additionally, instructions for certificate management are written exclusively for Windows (MMC, cert store), with no mention of Linux or cross-platform approaches. The authentication examples and general workflow do not provide parity for Linux users, and Windows authentication is listed as a supported type before others.
Recommendations
  • Include Linux-friendly tools for testing HTTP requests, such as curl, wget, or httpie, alongside PowerShell and Visual Studio.
  • Add instructions for certificate management on Linux systems, such as using OpenSSL and managing certificates in common Linux locations.
  • Mention Linux authentication mechanisms and clarify how Windows authentication type behaves on non-Windows self-hosted integration runtimes.
  • Ensure examples and tool recommendations are presented in a cross-platform manner, or at least provide Linux equivalents in parallel.
  • Explicitly state any platform limitations or differences in supported features (e.g., Windows authentication only available on Windows hosts).
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-11 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 Windows bias primarily through exclusive references to Windows-specific tooling (Dynamics XRM tooling), lack of Linux or cross-platform alternatives, and omission of Linux-specific instructions or examples. All examples and setup steps are platform-agnostic JSON or Azure portal UI, but the underlying connector is described as being built on Windows-centric technology, and there is no mention of Linux compatibility, deployment, or troubleshooting. There are no PowerShell examples, but Windows tools are referenced first and exclusively.
Recommendations
  • Explicitly state platform compatibility (Windows, Linux, macOS) for the connector and integration runtime.
  • If the connector or integration runtime supports Linux, provide Linux-specific setup instructions and troubleshooting steps.
  • Reference cross-platform alternatives to Dynamics XRM tooling if available, or clarify if it is Windows-only.
  • Include examples or notes for deploying self-hosted integration runtime on Linux, if supported.
  • Add a section comparing Windows and Linux deployment scenarios, including any limitations or differences.
  • Avoid mentioning Windows tools exclusively; provide parity for Linux users where possible.
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-11 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 demonstrates a Windows bias in several ways: Windows file share paths and conventions (e.g., backslashes, UNC paths) are presented first and most prominently, with Linux support mentioned only briefly (via Samba). Examples and sample configurations use Windows-style paths exclusively, and instructions for enabling local access reference PowerShell commands without Linux equivalents. There are no Linux-specific examples or screenshots, and Windows terminology and tooling are assumed throughout.
Recommendations
  • Provide Linux-specific examples, including sample paths (e.g., /mnt/share/folder) and configuration steps for Samba shares.
  • Include screenshots or UI walkthroughs for Linux environments where relevant.
  • Offer equivalent command-line instructions for Linux (e.g., bash scripts or CLI commands) alongside PowerShell references.
  • Clarify cross-platform compatibility in all sections, and avoid presenting Windows conventions first or exclusively.
  • Explicitly document any differences or limitations when using Linux file shares, including authentication and path handling.
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-11 00:00
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, without mentioning Linux compatibility or providing Linux-specific instructions. There are no examples or guidance for installing the IBM Netezza ODBC driver on Linux, nor any mention of Linux-based integration runtime hosts. All tooling and setup instructions implicitly assume a Windows environment, and no Linux or cross-platform alternatives are discussed.
Recommendations
  • Explicitly state whether the self-hosted integration runtime and Netezza ODBC driver are supported on Linux, and provide installation instructions for Linux if supported.
  • Include Linux-specific examples for installing and configuring the IBM Netezza ODBC driver, such as using rpm/deb packages or tarballs.
  • Add guidance for running the self-hosted integration runtime on Linux, including any prerequisites, supported distributions, and troubleshooting tips.
  • Ensure parity in screenshots and UI walkthroughs by showing Linux environments where applicable.
  • Mention any limitations or differences in functionality when using Linux as the host for integration runtime or ODBC drivers.
GitHub Create Pull Request
Data Factory Mapping data flow script ...cs/blob/main/articles/data-factory/data-flow-script.md
High Priority View Details →
Scanned: 2026-01-11 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 PowerShell as the primary method for programmatically interacting with Data Flow Script outside the UI, without mentioning Linux or cross-platform alternatives. There are no examples or instructions for Linux users (e.g., Bash, curl, az CLI), and Windows/PowerShell tooling is mentioned first and exclusively in relevant sections.
Recommendations
  • Include examples for Linux users, such as using Bash scripts, curl, or the Azure CLI to interact with Data Flow Script.
  • Mention cross-platform alternatives alongside PowerShell, such as REST API usage from any OS.
  • Rephrase sections to avoid implying PowerShell is the only or primary method, and present Windows and Linux options equally.
  • Add notes or links to platform-agnostic documentation for programmatic access to Data Flow Script.
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
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits Windows bias primarily in its tooling recommendations and ordering. In the 'TIP' section, Windows-centric tools such as Visual Studio and PowerShell's Invoke-RestMethod are mentioned for API testing, with no mention of Linux-native equivalents (e.g., curl, wget, httpie). Windows tools are listed first and exclusively, suggesting a preference for Windows environments. No Linux-specific examples or tools are provided anywhere in the documentation.
Recommendations
  • Include Linux-native tools (e.g., curl, wget, httpie) alongside or before Windows tools when suggesting methods for testing REST APIs.
  • Provide example commands for both Windows (PowerShell) and Linux (bash/curl) environments where relevant.
  • Avoid listing Windows tools first or exclusively in general recommendations; strive for parity by mentioning cross-platform or Linux tools.
  • Add a note clarifying that all configuration and API testing steps can be performed on Linux, macOS, or Windows, and provide links to relevant documentation for each platform.
GitHub Create Pull Request
Data Factory Copy and transform data to and from SQL Server ...lob/main/articles/data-factory/connector-sql-server.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias in several areas: Windows authentication is described in detail and presented before any mention of Linux or cross-platform alternatives; configuration steps and troubleshooting rely heavily on Windows-specific tools (e.g., SQL Server Management Studio, SQL Server Configuration Manager, Windows Firewall), with no mention of Linux equivalents or instructions; there are no examples or guidance for connecting to SQL Server from Linux environments, nor any reference to Linux authentication mechanisms (such as Kerberos or integrated authentication via Linux domain join).
Recommendations
  • Add explicit instructions and examples for connecting to SQL Server from Linux environments, including authentication options (e.g., SQL authentication, Kerberos, or integrated authentication via Linux domain join).
  • Provide troubleshooting steps for Linux hosts, such as using sqlcmd, configuring firewalls with iptables or ufw, and enabling TCP/IP via configuration files.
  • Mention and link to cross-platform tools (e.g., Azure Data Studio, sqlcmd) alongside or before Windows-only tools like SQL Server Management Studio.
  • Clarify which features (such as Windows authentication) are only available on Windows, and suggest Linux alternatives or workarounds where possible.
  • Ensure parity in example code and screenshots by including Linux terminal commands and configuration steps where relevant.
GitHub Create Pull Request
← Previous Page 3 of 40 Next →