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 401-425 of 1000 flagged pages
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/apply-dataops.md
...-docs/blob/main/articles/data-factory/apply-dataops.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools and workflows. Examples include the use of PowerShell and Visual Studio/NUnit for automated testing, and the lack of explicit Linux or cross-platform alternatives. Windows tools are mentioned before any Linux equivalents, and there are no examples or guidance for Linux shell scripting, Linux-native CI/CD tools, or non-Windows development environments. The documentation assumes familiarity with Windows-based workflows and omits instructions for Linux users.
Recommendations
- Include Linux shell (bash) and cross-platform CLI examples alongside PowerShell commands for CI/CD and testing.
- Reference Linux-compatible testing frameworks (e.g., pytest for Python, or other .NET Core cross-platform test runners) in addition to NUnit/Visual Studio.
- Explicitly mention that Azure CLI is cross-platform and provide sample commands for both Windows and Linux environments.
- Add instructions or screenshots for configuring Azure Data Factory from Linux or macOS environments, not just via Azure Portal or Windows-based Studio.
- Highlight cross-platform editors (e.g., VS Code) and workflows that work on Linux, macOS, and Windows.
- Ensure that all automation and scripting examples are provided in both PowerShell and bash (or other common Linux shells).
Create Pull Request
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/choose-the-right-integration-runtime-configuration.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/choose-the-right-integration-runtime-configuration.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. References to self-hosted integration runtime installation and management implicitly assume Windows environments, with linked articles and examples (e.g., sharing via PowerShell) focused on Windows tooling. There is no mention of Linux installation, management, or troubleshooting, nor are Linux-specific examples or tools provided. The diagnostic and management tools referenced are typically Windows-centric, and there is no guidance for Linux users.
Recommendations
- Add explicit instructions and examples for installing and managing the self-hosted integration runtime on Linux machines.
- Include Linux-specific troubleshooting steps and diagnostic tool usage, or clarify cross-platform compatibility of existing tools.
- Provide parity in examples (e.g., Bash scripts, Linux service management) alongside PowerShell/Windows examples.
- Reference Linux equivalents for network configuration, monitoring, and certificate management (e.g., using systemd, iptables, Linux-based monitoring tools).
- Clarify any platform limitations or differences in features between Windows and Linux for self-hosted integration runtime.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-pipeline-execution-triggers.md
...s/data-factory/concepts-pipeline-execution-triggers.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several ways: Windows-specific tools (Azure PowerShell) are highlighted with explicit examples, and PowerShell is listed before cross-platform alternatives (Python SDK, REST API). There are no Linux-specific command-line examples (such as Azure CLI or Bash), and no mention of Linux-native tooling or shell usage. The .NET SDK and PowerShell are both Windows-centric, and the documentation does not provide parity for Linux users in terms of example commands or workflow.
Recommendations
- Add Azure CLI examples for pipeline execution and trigger creation, as Azure CLI is cross-platform and widely used on Linux.
- Include Bash shell script examples for REST API calls, demonstrating how Linux users can manually trigger pipelines.
- Reorder the API/SDK section to present cross-platform tools (Python SDK, REST API, Azure CLI) before Windows-specific tools (PowerShell, .NET SDK).
- Explicitly mention that PowerShell examples are for Windows and provide equivalent Linux/Bash alternatives.
- Reference Linux-friendly quickstart guides or tutorials alongside Windows/PowerShell ones.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-standard-virtual-network-injection.md
...integration-runtime-standard-virtual-network-injection.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a Windows bias in several ways. PowerShell is the only scripting example provided for configuring UDRs, with no equivalent Bash, Azure CLI, or Linux shell example. The NSG section references Windows firewall rules and RDP (port 3389), which are Windows-specific concepts, and troubleshooting guidance is oriented toward Windows tools. There is no mention of Linux-based management or configuration approaches, nor are Linux tools or patterns (such as Bash scripts, Azure CLI, or SSH) referenced. The related content also prioritizes Azure PowerShell and UI methods, with no Linux-centric alternatives.
Recommendations
- Provide equivalent Azure CLI and Bash examples for all PowerShell scripts, especially for UDR and NSG configuration.
- Include guidance for Linux administrators, such as using SSH for troubleshooting instead of RDP, and referencing Linux firewall management (e.g., iptables, firewalld) where appropriate.
- Mention cross-platform tools and patterns (e.g., Azure CLI, Terraform) alongside or before Windows-specific tools.
- Add explicit notes or sections for Linux environments, clarifying any differences in configuration or management steps.
- Ensure that troubleshooting and advanced access instructions include Linux-compatible options, not just Windows (e.g., remote desktop alternatives).
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-express-virtual-network-injection.md
...-integration-runtime-express-virtual-network-injection.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates Windows bias primarily through exclusive use of Windows tooling and scripting examples (notably, use of .ps1 PowerShell scripts and main.cmd batch files for custom setup), and by referencing Azure PowerShell in related content without mention of Linux-native alternatives. There are no Linux shell (bash), cross-platform CLI, or Linux-specific instructions or examples provided, and Windows-centric patterns (such as PowerShell scripts) are presented as the default or only option.
Recommendations
- Provide equivalent Linux/bash shell scripts for custom setup, alongside the existing PowerShell and batch file examples.
- Include instructions for using Azure CLI (az) for all configuration steps, especially in related content and examples.
- Reference Linux-compatible tools and workflows (e.g., bash scripts, cloud-init, or Ansible) for automation and setup.
- Explicitly mention cross-platform support and clarify which steps or scripts are Windows-only, offering alternatives for Linux users.
- Add a section or notes on how to perform each configuration step from a Linux environment, including file formats and command syntax.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-amazon-rds-for-sql-server.md
...es/data-factory/connector-amazon-rds-for-sql-server.md
High Priority
View Details →
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 examples provided for authentication, configuration, or troubleshooting, nor is there mention of Linux tools or patterns for managing Amazon RDS for SQL Server connections.
Recommendations
- Add explicit Linux authentication guidance, including Kerberos or other supported mechanisms, if available.
- Provide troubleshooting and configuration steps using Linux tools (e.g., sqlcmd, firewall-cmd, ufw) and reference Linux-based documentation.
- Include examples for connecting from Linux environments, such as using ODBC or JDBC drivers on Linux, and clarify any platform-specific requirements.
- Mention cross-platform management options (e.g., Azure Data Studio, which runs on Windows, Linux, and macOS) as alternatives to Windows-only tools.
- Clarify any limitations or differences when connecting from Linux hosts, especially for self-hosted integration runtime scenarios.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-parameters-variables.md
...articles/data-factory/concepts-parameters-variables.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a 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 command-line approaches. The tutorials and quickstarts referenced are PowerShell-focused, which is typically associated with Windows environments, and there is no mention of alternatives for Linux or macOS users.
Recommendations
- Add equivalent tutorials and quickstarts using Bash or Azure CLI to ensure Linux and macOS users have clear guidance.
- Explicitly mention cross-platform options and clarify which steps or tools are available on Windows, Linux, and macOS.
- Where PowerShell is referenced, provide parallel examples for Bash or Azure CLI, or link to those resources.
- Review screenshots and UI instructions to ensure they do not assume a Windows environment (e.g., file paths, shell usage).
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/ci-cd-github-troubleshoot-guide.md
...ticles/data-factory/ci-cd-github-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is mentioned as a tool for making changes (e.g., 'You can use PowerShell API to change as well'), but there are no equivalent Linux shell (bash, CLI) examples or references. Where automation is discussed, Windows-centric tools and patterns (PowerShell, Azure Portal UI) are referenced, and Linux alternatives are missing. No troubleshooting steps or code samples use bash, Linux CLI, or cross-platform scripting. The documentation assumes familiarity with Windows tools and does not provide parity for Linux users.
Recommendations
- Include Linux shell (bash) and Azure CLI examples alongside PowerShell instructions wherever automation or scripting is discussed.
- Explicitly mention cross-platform tools (e.g., Azure CLI, REST API) and provide usage examples for both Windows and Linux environments.
- When referencing automation, provide sample scripts for both PowerShell and bash, and clarify which steps are OS-agnostic.
- Add troubleshooting steps and code samples that demonstrate how to perform tasks on Linux systems, not just via Windows tools.
- Review all references to Windows-specific tools and ensure Linux equivalents are mentioned and documented with equal prominence.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/configure-bcdr-azure-ssis-integration-runtime.md
...ctory/configure-bcdr-azure-ssis-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools (Azure PowerShell, SSMS), providing examples and instructions only for these, and omitting any mention of Linux alternatives or CLI parity. The orchestration and management steps assume the use of SSMS (a Windows-only tool) and PowerShell, with no guidance for Linux users or cross-platform command-line tools. The order of presentation also favors Windows tools and patterns, with no Linux-first or parity approach.
Recommendations
- Include equivalent instructions using Azure CLI for all steps currently described with Azure PowerShell.
- Provide guidance for managing SSIS jobs and failover using cross-platform tools, such as Azure Data Studio or direct T-SQL scripts, instead of relying solely on SSMS.
- Add explicit examples and notes for Linux/macOS users, including how to perform orchestration, monitoring, and failover tasks without Windows-only tools.
- Where possible, reference cross-platform management options before or alongside Windows-specific tools.
- Clarify which steps require Windows-only tools and suggest alternatives or workarounds for non-Windows environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-datasets-linked-services.md
...cles/data-factory/concepts-datasets-linked-services.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates several forms of Windows bias. PowerShell is prominently listed as a recommended tool for creating datasets, both in the main text and in the quickstart links, without mention of Linux-native alternatives (e.g., Bash, CLI). Windows-centric tools and patterns (PowerShell, .NET) are mentioned before cross-platform or Linux-friendly options. There are no examples or instructions tailored for Linux users, and no explicit mention of Bash, Azure CLI, or Linux shell scripting. This may make the documentation less accessible or welcoming to users on Linux or macOS platforms.
Recommendations
- Add explicit examples and quickstart links for Azure CLI and Bash scripting, which are cross-platform and widely used on Linux.
- When listing tools or SDKs, mention cross-platform options (e.g., Azure CLI, Python SDK) before or alongside Windows-specific tools like PowerShell.
- Provide sample commands for dataset creation using Azure CLI and Bash, in addition to PowerShell and .NET.
- Clarify that REST API and Azure Resource Manager templates are platform-agnostic, and provide usage examples from Linux/macOS terminals.
- Consider adding a section or tab for Linux/macOS users, outlining recommended workflows and tools.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/built-in-preinstalled-components-ssis-integration-runtime.md
...lt-in-preinstalled-components-ssis-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exclusively describes Azure-SSIS Integration Runtime as running on Windows Server 2019, with all built-in and preinstalled components, drivers, and tasks being Windows-centric (e.g., OLEDB, MSMQ, WMI, SQL Server Native Client, Excel, Access Database Engine). There is no mention of Linux support, alternatives, or examples, nor any cross-platform considerations. All tooling and patterns referenced are specific to the Windows ecosystem.
Recommendations
- Explicitly state that Azure-SSIS IR is Windows-only, and clarify the lack of Linux support.
- If Linux support is planned or available in any form, add equivalent lists/examples for Linux environments.
- Provide guidance or links for users seeking cross-platform ETL/data integration solutions on Azure (e.g., Data Factory Mapping Data Flows, Apache NiFi, Azure Databricks).
- Where possible, mention open-source or cross-platform alternatives to Windows-only components (e.g., ODBC drivers, file formats, scripting tasks).
- Add a comparison table or section highlighting differences between Windows and Linux runtimes for data integration on Azure.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-linked-services.md
...main/articles/data-factory/concepts-linked-services.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell and .NET API as primary methods for creating linked services, with no mention of Linux-native tools or CLI examples. Windows-centric tools (PowerShell, .NET) are referenced before cross-platform or Linux-friendly alternatives. There are no Bash, Azure CLI, or Linux shell script examples, nor is there guidance for Linux users on how to perform equivalent tasks.
Recommendations
- Add Azure CLI examples for creating linked services, as Azure CLI is cross-platform and widely used on Linux.
- Include Bash or shell script snippets demonstrating REST API usage for linked service creation.
- Explicitly mention Linux support and provide instructions for Linux users, such as using Azure CLI or REST API from a Linux terminal.
- Reorder tool references to present cross-platform options (Azure CLI, REST API) before Windows-specific tools (PowerShell, .NET).
- Add a section or note clarifying that all functionality is available on Linux and macOS, not just Windows.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-azure-sql-database.md
.../articles/data-factory/connector-azure-sql-database.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive mention of Windows-based tools (SQL Server Management Studio) for database user and permission management, and by referencing Azure PowerShell for Always Encrypted configuration without mentioning Linux alternatives. There are no examples or instructions for using Linux-native tools (such as sqlcmd, Azure CLI, or Data Studio) for these tasks, nor is there guidance for Linux users on managing SQL authentication or permissions. The documentation assumes the use of Windows environments for administrative tasks and omits Linux parity in tool recommendations and examples.
Recommendations
- Include instructions and examples for using Linux-compatible tools (e.g., sqlcmd, Azure Data Studio, Azure CLI) for database user creation, permission management, and other administrative tasks.
- When referencing Azure PowerShell, also provide equivalent Azure CLI commands and links, which are cross-platform.
- Explicitly mention that tasks such as running T-SQL can be performed from Linux/macOS using sqlcmd or Azure Data Studio, not just SQL Server Management Studio.
- Add screenshots or walkthroughs for Linux environments where UI steps are shown for Windows.
- Review all sections for implicit assumptions of Windows usage and clarify cross-platform compatibility where applicable.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/configure-azure-ssis-integration-runtime-performance.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/configure-azure-ssis-integration-runtime-performance.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by exclusively providing PowerShell-based configuration examples and scripts, which are native to Windows environments. There are no equivalent examples or instructions for Linux users (e.g., Bash, Azure CLI, or ARM templates). The only referenced automation and scripting method is PowerShell, and Windows-centric terminology and tools are used throughout, with no mention of Linux alternatives or cross-platform approaches.
Recommendations
- Add equivalent configuration examples using Azure CLI and Bash scripts to support Linux and cross-platform users.
- Reference ARM templates or REST API methods for configuration, which are platform-agnostic.
- Explicitly state that PowerShell examples are for Windows and provide links or sections for Linux/macOS users.
- Ensure that any tool or pattern mentioned (e.g., PowerShell) is accompanied by its Linux-friendly counterpart.
- Review related tutorials and linked articles to ensure Linux parity in automation and configuration guidance.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-roles-permissions.md
...in/articles/data-factory/concepts-roles-permissions.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page references PowerShell as a method for updating a data factory, but does not mention or provide examples for Linux or cross-platform alternatives such as Azure CLI, Bash, or REST API. There is a lack of parity in tooling examples, with Windows-centric tools (PowerShell) being mentioned exclusively, and no Linux-specific or platform-neutral instructions provided.
Recommendations
- Include Azure CLI examples alongside PowerShell for resource management tasks, as Azure CLI is cross-platform and widely used on Linux.
- Mention Bash scripting and REST API as alternatives for automation and management, with sample commands or links to relevant documentation.
- Explicitly state that PowerShell is available on Linux and macOS, or clarify platform requirements for each tool.
- Add a section or note highlighting cross-platform options for managing Azure Data Factory resources, ensuring Linux users are equally supported.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-azure-table-storage.md
...articles/data-factory/connector-azure-table-storage.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias primarily through the exclusive use of PowerShell commands for generating Shared Access Signatures (SAS) and by referencing Windows-centric tools and patterns. There are no equivalent Linux/CLI examples provided, and the PowerShell approach is presented as the default method for SAS generation, which may disadvantage users on Linux or macOS.
Recommendations
- Provide equivalent Azure CLI (az) commands for generating SAS tokens, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention both PowerShell and CLI options side-by-side, or use tabs to allow users to select their preferred environment.
- Avoid presenting Windows/PowerShell tools as the only or primary method; ensure parity by including Linux-friendly approaches in all procedural sections.
- Where screenshots or UI instructions are given, clarify if there are any differences for users on non-Windows platforms, or confirm that the experience is the same.
- Review all code snippets and command-line instructions to ensure at least one Linux-compatible example is present for each Windows/PowerShell example.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-file-system.md
...ob/main/articles/data-factory/connector-file-system.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-style paths and escape characters are used throughout examples and explanations, with double backslashes and references to UNC paths (\\server\share). The only explicit command-line reference for enabling local machine access under Self-hosted Integration Runtime is a link to a PowerShell command, with no Linux equivalent or mention of Linux shell commands. Windows file sharing is assumed as the default, with Linux file shares only mentioned briefly as requiring Samba, but no further guidance or examples for Linux environments are provided. All screenshots and UI examples use Windows-style paths, and there are no Linux-specific configuration samples or troubleshooting notes.
Recommendations
- Provide equivalent Linux shell commands (e.g., Bash scripts) for operations currently only documented with PowerShell.
- Include Linux-specific examples for file paths, such as /mnt/share or /home/user/data, alongside Windows UNC paths.
- Expand the section on Linux file shares to include step-by-step instructions for configuring Samba, mounting shares, and setting permissions.
- Add troubleshooting notes for common Linux issues (e.g., SELinux, firewall, permissions) when connecting to file shares.
- Ensure screenshots and UI examples alternate between Windows and Linux environments, or annotate them to clarify cross-platform applicability.
- Explicitly state platform differences in authentication, path formats, and integration runtime setup, and provide parity in documentation coverage.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-dynamics-crm-office-365.md
...cles/data-factory/connector-dynamics-crm-office-365.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tooling (Dynamics XRM tooling), mentioning Windows patterns and terminology (Active Directory, domain, etc.), and omitting Linux-specific examples or guidance. All authentication and configuration examples use generic Azure and Dynamics concepts, but do not provide parity for Linux environments, such as how to perform equivalent tasks on Linux or with Linux-native tools. The documentation also references Windows-centric authentication (Active Directory, domain) and does not mention alternatives for Linux-based self-hosted integration runtimes or service principal setup from Linux.
Recommendations
- Add explicit instructions and examples for configuring and using the connector from Linux environments, including how to set up self-hosted integration runtime on Linux.
- Reference cross-platform or Linux-native tools where possible, or clarify which steps are OS-agnostic.
- If any steps require Windows-only tooling (such as Dynamics XRM tooling), provide alternatives or workarounds for Linux users.
- Include notes or sections on differences when deploying or managing integration runtimes or authentication from Linux vs. Windows.
- Ensure parity in screenshots and UI walkthroughs by showing Linux or web-based interfaces where applicable.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-office-365.md
...lob/main/articles/data-factory/connector-office-365.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias through several patterns: PowerShell is referenced for certificate conversion, and Windows-centric tools and templates are mentioned (e.g., PowerShell blog, Azure portal UI). There are no explicit Linux or cross-platform CLI examples for key steps such as certificate conversion or pipeline creation. The order of tool presentation puts Azure portal and PowerShell before other SDKs, and the certificate conversion instructions exclusively reference PowerShell, omitting Linux alternatives.
Recommendations
- Add Linux and cross-platform CLI examples for certificate conversion (e.g., using OpenSSL).
- Include instructions for managing certificates and secrets in Azure Key Vault from Linux/macOS environments.
- Present tool options in a neutral order or explicitly mention cross-platform alternatives (e.g., Azure CLI, REST API, Python SDK) before or alongside Windows tools.
- Provide sample commands and walkthroughs for pipeline creation and management using Linux-friendly tools (e.g., Azure CLI, Bash scripts).
- Reference documentation or tutorials for Linux users where appropriate, especially for steps currently covered only by PowerShell.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-rest.md
...docs/blob/main/articles/data-factory/connector-rest.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation exhibits Windows bias primarily through its explicit mention of Windows-centric tools (Visual Studio, PowerShell's Invoke-RestMethod) as recommended options for testing REST API requests, without referencing equivalent Linux/macOS tools. PowerShell is highlighted as a method for certificate conversion, and no Linux alternatives (such as OpenSSL or curl) are provided. The order of tool presentation also places Windows tools first, suggesting a Windows-first approach.
Recommendations
- Include Linux/macOS equivalents (e.g., curl, wget, OpenSSL, Postman CLI) alongside Windows tools when suggesting how to test REST APIs or manipulate certificates.
- When providing code snippets or tool recommendations, present cross-platform options together or alternate the order to avoid implicit prioritization.
- Add explicit instructions or examples for certificate conversion using OpenSSL (Linux/macOS) in addition to PowerShell.
- Mention that the Azure portal UI and Data Factory features are accessible from any OS via browser, to reinforce platform neutrality.
- Where screenshots or tool references are given, clarify that steps are OS-agnostic or provide parallel examples for Linux/macOS environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sap-business-warehouse.md
...icles/data-factory/connector-sap-business-warehouse.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily in the prerequisites and troubleshooting sections. It instructs users to place SAP NetWeaver RFC SDK libraries in the %windir%\system32 folder, which is specific to Windows environments, and does not mention Linux equivalents or provide guidance for Linux-based Integration Runtime hosts. No Linux-specific examples, file paths, or troubleshooting steps are provided, and Windows terminology appears first and exclusively.
Recommendations
- Add instructions for installing SAP NetWeaver RFC SDK libraries on Linux hosts, including typical file paths (e.g., /usr/lib, /opt/sap, etc.).
- Include troubleshooting tips for Linux environments, such as verifying library placement, permissions, and environment variables.
- Mention supported Linux distributions for Self-hosted Integration Runtime and SAP BW connector, if applicable.
- Provide example commands or configuration steps for both Windows and Linux platforms, ensuring parity.
- Clarify any platform-specific limitations or requirements in the prerequisites section.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-sharepoint-online-list.md
...ctory/connector-troubleshoot-sharepoint-online-list.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a clear Windows bias. Troubleshooting steps for enabling ACS in SharePoint Online exclusively reference the SharePoint Online Management Shell (a Windows-only tool) and provide only PowerShell commands. There are no equivalent instructions or examples for Linux or cross-platform environments, nor is there mention of alternative approaches for non-Windows users. The documentation assumes access to Windows tools and environments, leaving Linux users without guidance.
Recommendations
- Provide equivalent troubleshooting steps using cross-platform tools, such as Azure CLI, Microsoft Graph API, or REST API calls that can be executed from Linux or macOS.
- Explicitly mention whether the required actions (e.g., enabling ACS) can be performed via browser-based admin portals or other non-Windows interfaces.
- Add Linux/macOS examples or clarify platform requirements for each step.
- If PowerShell is required, mention PowerShell Core and its availability on Linux/macOS, and provide instructions for installing and using it on those platforms.
- Include a note about platform limitations and suggest alternatives for users who do not have access to Windows environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sql-server.md
...lob/main/articles/data-factory/connector-sql-server.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: Windows authentication is discussed in detail and presented before any mention of Linux alternatives; configuration steps and troubleshooting focus exclusively on Windows tools (e.g., SQL Server Management Studio, SQL Server Configuration Manager, Windows Firewall), with no mention of Linux equivalents; and there are no examples or guidance for connecting to SQL Server from Linux hosts or using Linux authentication mechanisms. The page lacks parity for Linux users, both in terms of authentication and server management.
Recommendations
- Add explicit guidance and examples for connecting to SQL Server from Linux hosts, including authentication options such as Kerberos or SQL authentication from Linux.
- Include troubleshooting steps and configuration instructions for SQL Server running on Linux, referencing tools like sqlcmd, systemctl, and Linux firewall configuration.
- Present authentication options in a platform-neutral order (e.g., SQL, Windows, Kerberos, Managed Identity), and clarify which are available on each OS.
- Where Windows-specific tools are mentioned (e.g., SQL Server Management Studio, Configuration Manager), provide Linux alternatives (e.g., sqlcmd, Azure Data Studio, command-line configuration).
- Add notes or sections on differences and limitations when using SQL Server on Linux, including supported features and configuration steps.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-guide.md
.../articles/data-factory/connector-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates Windows bias in several ways. The FIPS troubleshooting section exclusively references Windows-specific paths (e.g., C:\Program Files\Microsoft Integration Runtime) and configuration files (diawp.exe.config), with no mention of Linux equivalents or instructions. There are no examples or troubleshooting steps for Linux-based self-hosted integration runtime environments. The guidance assumes the reader is operating on Windows, and does not provide parity for Linux users.
Recommendations
- Add troubleshooting instructions for Linux-based self-hosted integration runtime environments, including relevant file paths and configuration steps.
- Where Windows-specific tools or paths are mentioned, provide equivalent Linux examples (e.g., location of IR installation, config file editing commands).
- Explicitly state OS requirements or differences in the relevant troubleshooting steps.
- Ensure that all examples and recommendations are presented for both Windows and Linux, or clarify when a step is OS-specific.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-ftp-sftp-http.md
...s/data-factory/connector-troubleshoot-ftp-sftp-http.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows tools (WinSCP) are mentioned as recommended for credential validation, and the only third-party tool suggested for base64 encoding is a web-based one, with no mention of Linux CLI alternatives. While some Linux commands (openssl, ssh-keygen) are included, Windows tools are referenced first or exclusively in some troubleshooting steps. There are no explicit Linux/POSIX shell examples for common tasks like base64 encoding or SFTP troubleshooting, and no mention of Linux-native GUI tools (e.g., FileZilla, Nautilus).
Recommendations
- Include Linux shell examples for base64 encoding (e.g., 'base64 -w 0 < private_key_file').
- Mention Linux-native SFTP/FTP clients (e.g., FileZilla, Nautilus) alongside WinSCP for credential validation.
- Provide troubleshooting steps using Linux command-line tools (e.g., 'sftp', 'ftp', 'curl', 'nc') where relevant.
- List both Windows and Linux tools in recommendations, or group them by platform.
- Ensure parity in example order: present Linux and Windows options together, or alternate which is listed first.