Data Factory

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

Bias Trend Over Time

Pages with Bias Issues

319 issues found
Showing 126-150 of 319 flagged pages
Data Factory Applying DataOps ...-docs/blob/main/articles/data-factory/apply-dataops.md
Medium Priority View Details →
Scanned: 2026-01-12 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 for 'Applying DataOps to Azure Data Factory' demonstrates moderate Windows bias. Automated testing examples reference NUnit with Visual Studio, and CI/CD steps mention PowerShell and AZ CLI, but do not provide Linux/macOS equivalents or examples. The focus on Windows-centric tools (Visual Studio, PowerShell) and lack of explicit Linux/macOS instructions or screenshots may create friction for non-Windows users.
Recommendations
  • Include Linux/macOS equivalents for CI/CD and testing workflows, such as Bash scripts, shell commands, and references to cross-platform tools (e.g., pytest, xUnit, Git CLI).
  • Provide explicit examples of using AZ CLI and PowerShell on Linux/macOS, or mention that AZ CLI is cross-platform.
  • Add screenshots or instructions for using Azure Data Factory Studio and related features on non-Windows platforms.
  • Reference open-source or cross-platform editors (e.g., VS Code) alongside Visual Studio.
  • Clarify that GitHub and Azure DevOps integration works from any OS, and provide links to platform-agnostic documentation.
GitHub Create Pull Request
Data Factory Global parameters ...main/articles/data-factory/author-global-parameters.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references deploying global parameters via a PowerShell script as the only explicit example for CI/CD automation, without mentioning Linux/macOS alternatives (such as Azure CLI, Bash, or cross-platform tools). This creates a bias toward Windows users and may leave Linux/macOS users unsure how to automate deployment of global parameters.
Recommendations
  • Provide equivalent examples for deploying global parameters using Azure CLI and Bash scripts.
  • Clarify whether PowerShell Core (pwsh) is supported on Linux/macOS, and provide cross-platform script samples if so.
  • Explicitly mention that ARM template deployment can be performed from any OS using Azure CLI or REST API, and link to relevant documentation.
  • Add notes or sections for Linux/macOS users to ensure parity in CI/CD automation steps.
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias, primarily through the exclusive use of PowerShell for automation examples and references to Windows-specific tools and concepts (e.g., Windows firewall, RDP, service tags only available via PowerShell/CLI). There are no Linux CLI (Azure CLI, Bash) equivalents provided for key automation tasks, and Windows-centric terminology and patterns (such as firewall rules and port usage) are referenced without Linux alternatives. While the core configuration steps are platform-agnostic, the lack of Linux/macOS parity in examples and tooling creates friction for non-Windows users.
Recommendations
  • Provide Azure CLI and Bash script equivalents for all PowerShell automation examples, especially for UDR and NSG configuration.
  • Explicitly mention cross-platform tools and workflows where possible (e.g., Azure CLI, REST API).
  • Clarify when steps or tools are Windows-specific and offer Linux/macOS alternatives or guidance.
  • Include examples of configuring firewall rules and network settings using Linux-native tools (e.g., iptables, ufw) where relevant.
  • Ensure that service tag discovery and management instructions are available for Linux/macOS users (e.g., via Azure CLI or REST API).
GitHub Create Pull Request
Data Factory Troubleshoot CI-CD, Azure DevOps, and GitHub issues ...ticles/data-factory/ci-cd-github-troubleshoot-guide.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a moderate Windows bias. PowerShell is mentioned as an API option for automation and changing integration runtime, but there are no explicit Linux/macOS shell (bash, CLI) examples or references. Where command-line automation is discussed, only PowerShell is named, and no Linux equivalents (e.g., Azure CLI, bash scripts) are provided. There are no explicit instructions or examples for Linux/macOS users, and Windows-centric tools are referenced without alternatives.
Recommendations
  • Add Azure CLI and bash script examples alongside PowerShell for automation tasks.
  • Explicitly mention that SDKs and REST APIs are cross-platform and provide sample usage for Linux/macOS environments.
  • Where PowerShell is referenced, also provide equivalent commands for Azure CLI or bash.
  • Clarify that the npm package and YAML pipelines are platform-agnostic and can be used on Linux/macOS agents.
  • Include troubleshooting steps or notes relevant to Linux/macOS users, especially for integration runtime setup and CI/CD automation.
GitHub Create Pull Request
Data Factory Datasets ...cles/data-factory/concepts-datasets-linked-services.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. PowerShell is listed prominently as a tool for creating datasets, both in the main body and in the Quickstarts section, with no mention of Linux/macOS equivalents (e.g., Azure CLI or Bash scripting). Windows-centric tools and patterns (PowerShell, .NET) are mentioned before cross-platform or Linux-friendly options. There are no explicit Linux/macOS examples or guidance, which may create friction for non-Windows users.
Recommendations
  • Add Azure CLI examples and quickstart links for dataset creation, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that REST API and Azure portal are cross-platform, and provide example usage from Linux/macOS environments.
  • Reorder tool/SDK lists to start with cross-platform options (REST API, Azure CLI, Azure portal) before Windows-specific tools (PowerShell, .NET).
  • Include a note or section on how Linux/macOS users can perform equivalent tasks, with sample commands or scripts.
  • Consider adding Bash or shell script examples for common operations.
GitHub Create Pull Request
Data Factory Linked services ...main/articles/data-factory/concepts-linked-services.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is prominently listed as a primary method for creating linked services, and Windows-centric tools (PowerShell, .NET) are mentioned before cross-platform or Linux-native alternatives. There are no explicit Linux/macOS CLI examples (such as Azure CLI or Bash), and the quickstart/tutorial links prioritize Windows tools. This may create friction for Linux/macOS users, though most tasks can still be completed via REST API or portal.
Recommendations
  • Add Azure CLI and Bash examples for creating linked services, as these are cross-platform and widely used on Linux/macOS.
  • List cross-platform tools (Azure CLI, REST API) before or alongside Windows-specific tools (PowerShell, .NET) in tool/SDK lists.
  • Include explicit instructions or links for Linux/macOS users, such as installing and using Azure CLI.
  • Ensure quickstart/tutorial sections include parity for Linux/macOS environments, not just PowerShell/.NET.
GitHub Create Pull Request
Data Factory Pipeline parameters and variables ...articles/data-factory/concepts-parameters-variables.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page references PowerShell-based tutorials for pipeline creation and data transformation, which are primarily Windows-centric. There are no equivalent examples or links for Linux/macOS users (e.g., Bash, Azure CLI, or Python SDK). This creates friction for non-Windows users who may not use PowerShell or Windows tools.
Recommendations
  • Add equivalent tutorials and examples using Azure CLI, Bash scripts, or Python SDK for pipeline creation and data transformation.
  • Explicitly mention cross-platform options and provide links to Linux/macOS-friendly documentation.
  • List Linux/macOS examples alongside or before Windows/PowerShell examples to ensure parity.
  • Clarify which steps or tools are platform-agnostic and which are Windows-specific.
GitHub Create Pull Request
Data Factory Pipeline execution and triggers ...s/data-factory/concepts-pipeline-execution-triggers.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias, particularly in the 'Manual execution with other APIs/SDKs' section. Azure PowerShell is highlighted with a full example, and PowerShell is mentioned before Python and REST API. There is no mention of Linux/macOS CLI equivalents (such as Azure CLI), and no Linux-specific instructions or examples are provided. The focus on PowerShell and .NET SDK (both Windows-centric) may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI examples for pipeline execution, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Ensure Python SDK examples are shown with actual code snippets, not just links.
  • Present cross-platform methods (REST API, Python SDK, Azure CLI) before or alongside Windows-centric tools like PowerShell.
  • Explicitly note that PowerShell is available on Linux/macOS, or provide installation guidance for non-Windows users.
  • Include a table or section comparing all available automation methods, indicating platform compatibility.
GitHub Create Pull Request
Data Factory Roles and permissions for Azure Data Factory ...in/articles/data-factory/concepts-roles-permissions.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references updating a data factory from PowerShell or the SDK as a custom scenario, but does not mention or provide examples for Linux/macOS equivalents (such as Azure CLI or Bash scripting). PowerShell is a Windows-centric tool, and its mention without parity for Linux/macOS users introduces a bias. No Linux-specific tools, patterns, or examples are provided, and the only command-line scenario is described in terms of PowerShell.
Recommendations
  • Include Azure CLI examples alongside PowerShell for command-line operations, as Azure CLI is cross-platform.
  • Explicitly mention that SDKs and Azure CLI are available on Linux/macOS and provide sample commands for those platforms.
  • Where PowerShell is referenced, add a note or section for Bash/CLI usage to ensure Linux/macOS users have clear guidance.
  • Review other sections for implicit tool bias and ensure parity in instructions and examples.
GitHub Create Pull Request
Data Factory Copy data from Amazon RDS for SQL Server ...es/data-factory/connector-amazon-rds-for-sql-server.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a Windows bias primarily in the troubleshooting section, where all instructions and screenshots reference Windows-only tools (SQL Server Management Studio, SQL Server Configuration Manager, Windows Firewall), and links point to Windows-specific configuration guides. Windows authentication is described and exemplified before Linux alternatives, and there is no mention of Linux/macOS equivalents or guidance for those platforms. No PowerShell scripts are present, but the overall troubleshooting and configuration guidance is Windows-centric.
Recommendations
  • Add troubleshooting steps for Linux and macOS environments, including how to configure remote connections, enable TCP/IP, and open firewall ports using Linux tools (e.g., using 'ufw', 'iptables', or editing configuration files).
  • Include examples of connecting to Amazon RDS for SQL Server from Linux/macOS clients (e.g., using sqlcmd, Azure Data Studio, or other cross-platform tools).
  • Provide guidance on using SQL authentication as a cross-platform alternative, and clarify any limitations for Windows authentication on non-Windows integration runtimes.
  • Where screenshots or instructions reference Windows-only tools, add equivalent steps for Linux/macOS or note platform limitations.
  • Explicitly state platform requirements or limitations for features that are Windows-only (e.g., Windows authentication, use of Windows Management tools).
GitHub Create Pull Request
Data Factory Copy and transform data in Dynamics 365 (Microsoft Dataverse) or Dynamics CRM ...cles/data-factory/connector-dynamics-crm-office-365.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation exhibits Windows bias primarily through its reliance on Dynamics XRM tooling, which is explicitly described as being for building Windows client applications. There is no mention of Linux or macOS alternatives, nor any guidance for non-Windows environments. The documentation also references Active Directory authentication and domain concepts, which are traditionally Windows-centric, and does not clarify cross-platform support or provide parity guidance for Linux/macOS users.
Recommendations
  • Clarify whether the Dynamics connector and XRM tooling are supported on Linux/macOS, and provide explicit instructions or alternatives for those platforms.
  • If Windows-only tooling is required, state this limitation clearly at the top of the documentation.
  • Add examples or guidance for Linux and macOS users, including any required dependencies, authentication methods, or integration runtime setup steps that differ from Windows.
  • Reference cross-platform tools or SDKs if available, or suggest workarounds for non-Windows environments.
  • Ensure screenshots and UI instructions are not Windows-specific unless unavoidable; consider adding notes for Linux/macOS users where UI or workflow differs.
GitHub Create Pull Request
Data Factory Pipelines and activities ...articles/data-factory/concepts-pipelines-activities.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias, primarily through its reliance on PowerShell-based quickstart and tutorial links (e.g., 'quickstart-create-data-factory-powershell.md', 'tutorial-transform-data-spark-powershell.md') for walkthroughs. No Linux or cross-platform CLI (such as Azure CLI or Bash) examples are provided, and Windows/PowerShell tooling is referenced exclusively for step-by-step guidance. The main content is otherwise platform-neutral, but Linux/macOS users may encounter friction due to the lack of alternative instructions.
Recommendations
  • Provide equivalent walkthroughs and tutorials using Azure CLI and/or Bash scripts alongside PowerShell examples.
  • Explicitly mention cross-platform tooling options and link to Linux/macOS-specific guides where available.
  • Ensure that all referenced quickstarts and tutorials have Linux/macOS parity or alternatives.
  • Add a note clarifying that PowerShell is Windows-specific and suggest alternatives for other platforms.
GitHub Create Pull Request
Data Factory Configure performance for the Azure-SSIS Integration Runtime ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/configure-azure-ssis-integration-runtime-performance.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only PowerShell-based configuration examples and references a PowerShell tutorial for deploying SSIS packages to Azure. There are no examples or guidance for Linux/macOS users (e.g., using Azure CLI, Bash, or REST API), and Windows tooling is assumed throughout. This creates friction for users on non-Windows platforms who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add equivalent Azure CLI and/or Bash script examples for all configuration steps.
  • Reference tutorials or documentation for deploying SSIS packages using Azure CLI or REST API.
  • Explicitly state platform requirements and alternatives for Linux/macOS users.
  • Ensure that all critical configuration and deployment steps can be performed using cross-platform tools.
GitHub Create Pull Request
Data Factory Configure Azure-SSIS integration runtime for business continuity and disaster recovery (BCDR) ...ctory/configure-bcdr-azure-ssis-integration-runtime.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation demonstrates a moderate Windows bias. It references Windows-centric tools such as SSMS (SQL Server Management Studio) for scripting and job management, and Azure PowerShell for IR management. The orchestration/scheduling section focuses on SSMS and T-SQL scripts, which are primarily Windows tools. Azure portal and ADF UI are platform-neutral, but PowerShell and SSMS are not. No Linux/macOS alternatives or CLI examples are provided, and Windows tools are mentioned before any cross-platform options.
Recommendations
  • Provide equivalent instructions using Azure CLI, which is cross-platform, for all steps currently covered by Azure PowerShell.
  • Include alternatives to SSMS, such as Azure Data Studio, which is available on Linux/macOS, for scripting and job management.
  • Explicitly mention that Azure portal and ADF UI are accessible from any OS/browser.
  • Add notes or examples for Linux/macOS users, especially for scripting and orchestration tasks.
  • Where T-SQL scripts are used, clarify that they can be run from any SQL client, not just SSMS.
GitHub Create Pull Request
Data Factory Copy data from/to a file system ...ob/main/articles/data-factory/connector-file-system.md
Medium Priority View Details →
Scanned: 2026-01-12 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 moderate Windows bias. Windows terminology, paths, and escape patterns are used throughout, with examples and explanations referencing UNC paths (\\server\share), backslash escaping, and Windows-style user IDs (<domain>\<user>). The only explicit Linux guidance is a brief mention to install Samba for Linux file shares, but no Linux-specific examples, screenshots, or command-line instructions are provided. References to enabling local machine access point to PowerShell commands, with no Linux/macOS equivalents. The documentation assumes familiarity with Windows file sharing conventions and tools, potentially creating friction for Linux/macOS users.
Recommendations
  • Add Linux/macOS-specific examples for file paths, user IDs, and authentication (e.g., /mnt/share, user@host, etc.).
  • Include screenshots or UI walkthroughs using Linux file shares.
  • Provide equivalent Linux/macOS command-line instructions (e.g., using shell scripts, mounting shares with smbclient or mount.cifs) where PowerShell is referenced.
  • Clarify escape character usage for Linux paths (forward slash, no need for backslash escaping).
  • Expand the Samba section with step-by-step setup and integration instructions.
  • Explicitly state cross-platform differences in path formats, permissions, and user identity handling.
GitHub Create Pull Request
Data Factory Copy data from an HTTP source ...docs/blob/main/articles/data-factory/connector-http.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation exhibits mild Windows bias by mentioning Windows-specific tools (PowerShell's Invoke-RestMethod and Visual Studio) as primary options for testing HTTP requests, without referencing equivalent Linux/macOS tools. Additionally, certificate management instructions are exclusively described using Windows MMC and certificate stores, with no mention of Linux/macOS alternatives.
Recommendations
  • Include Linux/macOS equivalents for testing HTTP requests, such as curl, wget, or httpie.
  • Add instructions for managing client certificates on Linux/macOS, e.g., using OpenSSL, PEM files, and relevant file system permissions.
  • When listing tools or examples, present cross-platform options together or alternate their order to avoid Windows-first presentation.
  • Clarify that the integration runtime can run on Linux and provide links or notes about platform-specific setup for authentication and certificate management.
GitHub Create Pull Request
Data Factory Copy data from SAP BW ...icles/data-factory/connector-sap-business-warehouse.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily in the troubleshooting and prerequisites sections. It instructs users to place SAP NetWeaver RFC SDK libraries in the %windir%\system32 folder, which is specific to Windows. There is no mention of Linux or macOS equivalents, nor guidance for installing or configuring the libraries on non-Windows platforms. All examples and instructions assume a Windows environment for the Self-hosted Integration Runtime, with no parity for Linux users.
Recommendations
  • Add instructions for installing SAP NetWeaver RFC SDK libraries on Linux and macOS, including typical library paths (e.g., /usr/lib, /usr/local/lib).
  • Provide troubleshooting steps for connectivity issues on Linux/macOS, such as setting LD_LIBRARY_PATH and checking port access.
  • Clarify whether the Self-hosted Integration Runtime supports Linux/macOS and, if so, provide platform-specific setup guidance.
  • Include notes or examples for cross-platform compatibility wherever Windows-specific paths or tools are mentioned.
GitHub Create Pull Request
Data Factory Troubleshoot the Azure Blob Storage connector ...a-factory/connector-troubleshoot-azure-blob-storage.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation contains a notable Windows bias in the troubleshooting section for FIPS mode, referencing Windows-specific tools (diawp.exe.config) and configuration steps. There are no Linux or macOS equivalents or instructions provided for users running self-hosted integration runtime on non-Windows platforms.
Recommendations
  • Add troubleshooting steps for disabling FIPS mode or handling MD5 requirements on Linux/macOS hosts.
  • Clarify whether self-hosted integration runtime is supported on Linux/macOS and, if so, provide relevant configuration guidance.
  • Where Windows-specific tools or files are referenced, mention alternatives or note platform limitations explicitly.
  • Consider including example error messages or resolutions for Linux/macOS environments if applicable.
GitHub Create Pull Request
Data Factory Copy and transform data to and from SQL Server ...lob/main/articles/data-factory/connector-sql-server.md
Medium Priority View Details →
Scanned: 2026-01-12 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 exhibits a Windows bias in several areas: authentication examples and terminology prioritize Windows authentication, troubleshooting steps and configuration instructions rely on Windows-only tools (SQL Server Management Studio, SQL Server Configuration Manager, Windows Firewall), and links to supporting articles are Windows-centric. There are no Linux/macOS equivalents or instructions, nor are cross-platform alternatives mentioned for critical setup steps.
Recommendations
  • Add Linux/macOS equivalents for troubleshooting and configuration steps, such as instructions for configuring SQL Server on Linux (using systemctl, sqlcmd, firewall-cmd/ufw).
  • Include examples for connecting to SQL Server from Linux/macOS clients (e.g., using sqlcmd, Azure Data Studio, or ODBC tools).
  • Mention and link to documentation for SQL Server on Linux, including authentication options and network configuration.
  • Clarify which features (such as Windows authentication) are Windows-only, and provide alternatives or guidance for Linux environments.
  • Reorder sections or provide parity so that SQL authentication (cross-platform) is presented before or alongside Windows authentication.
  • Add troubleshooting steps for Linux-based SQL Server installations, including service management and firewall configuration.
GitHub Create Pull Request
Data Factory Troubleshoot the file system connector ...les/data-factory/connector-troubleshoot-file-system.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page provides troubleshooting guidance for the file system connector in Azure Data Factory and Azure Synapse. The only example for configuring access uses PowerShell, a Windows-centric tool, and references a setup guide that is Windows/PowerShell-specific. No Linux or macOS equivalents or instructions are provided, nor are cross-platform alternatives mentioned.
Recommendations
  • Add equivalent Linux/macOS instructions for configuring Self-hosted Integration Runtime (SHIR) file system access, such as using Bash, shell scripts, or relevant CLI tools.
  • Explicitly mention whether the configuration can be performed on non-Windows platforms, and provide guidance or links if possible.
  • Present cross-platform examples side-by-side or clarify platform limitations in the troubleshooting steps.
  • Reference any available REST API, Azure CLI, or portal-based configuration methods that are platform-agnostic.
GitHub Create Pull Request
Data Factory Troubleshoot the REST connector ...n/articles/data-factory/connector-troubleshoot-rest.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates Windows bias by referencing 'Command Prompt' as the environment for running curl, suggesting Fiddler (a Windows-only tool) for troubleshooting SSL issues, and omitting explicit Linux/macOS terminal instructions or alternative tools. No Linux/macOS-specific troubleshooting guidance or examples are provided.
Recommendations
  • Mention both Windows (Command Prompt) and Linux/macOS (Terminal) environments when providing curl instructions.
  • Provide example curl commands for Linux/macOS, noting any syntax or quoting differences.
  • Suggest cross-platform alternatives to Fiddler, such as Wireshark or mitmproxy, for SSL troubleshooting.
  • Explicitly state that curl is available on Linux/macOS by default, and provide installation guidance for Windows users if needed.
  • Ensure troubleshooting steps and tool recommendations are inclusive of all major platforms.
GitHub Create Pull Request
Data Factory Automate continuous integration ...ntinuous-integration-delivery-automate-azure-pipelines.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias, primarily through exclusive use of PowerShell for deployment automation and trigger management. All scripting examples and instructions reference PowerShell, with no mention of Bash, CLI, or cross-platform alternatives. The guidance for managing Azure Key Vault permissions and Data Factory triggers is centered on .ps1 scripts and Azure PowerShell modules, which are Windows-centric. There are no Linux/macOS-specific instructions or examples, and Windows tooling is referenced first and exclusively throughout critical automation steps.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for deployment and trigger management tasks.
  • Explicitly state cross-platform compatibility for Azure Pipelines tasks and clarify when PowerShell Core (cross-platform) can be used.
  • Add instructions for installing and using Azure CLI on Linux/macOS, and reference CLI commands for common operations.
  • Include notes or sections highlighting differences or considerations for Linux/macOS users, such as file paths, shell environments, and agent setup.
  • Ensure that all automation steps can be completed using cross-platform tools, not just Windows/PowerShell.
GitHub Create Pull Request
Data Factory Troubleshoot connectors .../articles/data-factory/connector-troubleshoot-guide.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation shows a moderate Windows bias, particularly in the FIPS troubleshooting section. It references Windows-specific paths (e.g., C:\Program Files\Microsoft Integration Runtime) and configuration files (diawp.exe.config), with instructions that only apply to Windows environments. There are no equivalent instructions or notes for Linux or macOS users running Self-hosted Integration Runtime. The rest of the documentation is generally platform-neutral, but the critical troubleshooting step for FIPS issues is Windows-only.
Recommendations
  • Add explicit guidance for Linux/macOS users regarding FIPS-related troubleshooting, including whether FIPS mode or equivalent cryptographic settings exist and how to configure them.
  • Clarify if Self-hosted Integration Runtime is supported on Linux/macOS, and if so, provide parallel instructions or note any platform limitations.
  • Where file paths or configuration steps are given, specify platform differences or provide alternative steps for non-Windows environments.
  • Add a note at the start of the troubleshooting section indicating which steps are platform-specific and provide links to platform-specific documentation if available.
GitHub Create Pull Request
Data Factory Troubleshoot the SAP Table, SAP Business Warehouse Open Hub, and SAP ODP connectors ...in/articles/data-factory/connector-troubleshoot-sap.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The troubleshooting documentation provides only a PowerShell example (Test-NetConnection) for testing SAP server connectivity, which is specific to Windows. There are no equivalent Linux/macOS commands or instructions, and Windows tooling is mentioned exclusively and first. This creates friction for Linux/macOS users attempting to follow the troubleshooting steps.
Recommendations
  • Add equivalent Linux/macOS command examples, such as using 'nc', 'telnet', or 'curl' to test port connectivity.
  • Explicitly mention cross-platform alternatives and clarify which commands are OS-specific.
  • Consider reordering examples so that both Windows and Linux/macOS instructions are presented together or in parallel.
GitHub Create Pull Request
Data Factory Connector upgrade guidance ...in/articles/data-factory/connector-upgrade-guidance.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell script examples for programmatically finding impacted objects, which is a Windows-centric tool. There are no equivalent examples or guidance for Linux/macOS users (e.g., Bash, Azure CLI, Python), nor is there mention of cross-platform alternatives. This creates friction for users on non-Windows platforms.
Recommendations
  • Provide equivalent Bash or Azure CLI script examples for Linux/macOS users.
  • Mention cross-platform tools (e.g., Python SDK, REST API) that can achieve the same results.
  • Clarify whether the PowerShell scripts can run on PowerShell Core on Linux/macOS, and provide guidance if so.
  • Add explicit notes or sections for Linux/macOS users to ensure parity.
GitHub Create Pull Request
← Previous Page 6 of 13 Next →