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 601-625 of 1000 flagged pages
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-postgresql.md
...lob/main/articles/data-factory/connector-postgresql.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation displays a Windows bias in its guidance for configuring SSL verification with the ODBC driver on Self-hosted Integration Runtime (SHIR). It references only Windows file paths (e.g., C:\Windows\ServiceProfiles\DIAHostService\AppData\Roaming\postgresql\root.crt) and does not mention Linux equivalents or provide Linux-specific instructions. There are no Linux or cross-platform examples for setting up ODBC DSNs or certificate locations, and the only operating system-specific details are for Windows. This may hinder users running SHIR on Linux or other non-Windows environments.
Recommendations
- Add equivalent instructions and file paths for configuring SSL certificates and DSNs on Linux-based SHIR hosts (e.g., ~/.postgresql/root.crt or /etc/ssl/certs/).
- Explicitly state whether SHIR is supported on Linux, and if so, provide parity in setup steps for both Windows and Linux environments.
- Where file paths or OS-specific steps are mentioned, include both Windows and Linux variants side by side.
- Provide examples or references for configuring ODBC DSNs and certificates on Linux, not just Windows.
- Review the documentation for other implicit Windows assumptions and ensure cross-platform applicability is clear.
Create Pull Request
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-integration-runtime.md
...icles/data-factory/create-azure-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page provides only a Windows PowerShell example for creating an Azure Integration Runtime via command line, with no equivalent example for Linux users (e.g., Azure CLI or Bash). The use of the Set-AzDataFactoryV2IntegrationRuntime PowerShell cmdlet and lack of mention of cross-platform tools or scripts indicates a Windows-centric approach. No Linux or macOS command-line alternatives are provided.
Recommendations
- Add equivalent Azure CLI examples for creating and configuring Azure Integration Runtime, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that PowerShell examples are for Windows and provide Bash or shell script alternatives where possible.
- Include a section or note on how to perform the same actions on Linux/macOS environments, referencing Azure CLI or REST API.
- Ensure parity in documentation by presenting cross-platform command-line options before or alongside Windows-specific tools.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-spark-portal.md
...s/data-factory/tutorial-transform-data-spark-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation requires Azure PowerShell for setup and references only PowerShell installation instructions, with no mention of Linux/Unix alternatives (such as Azure CLI or Bash). There are no examples or instructions for Linux/macOS users for uploading files or managing resources, and the only prerequisite for automation is Azure PowerShell. This creates a bias toward Windows users and omits parity for Linux environments.
Recommendations
- Provide equivalent instructions using Azure CLI (az) for all steps currently described with Azure PowerShell, including installation and usage.
- Include Bash or cross-platform shell examples for uploading files to Azure Blob Storage (e.g., using az storage blob upload or Azure Storage Explorer).
- Explicitly mention that all steps can be performed from Linux/macOS as well as Windows, and provide links to relevant cross-platform tools.
- In the prerequisites, list both Azure PowerShell and Azure CLI as options, with links to their respective installation guides.
- Where automation or scripting is referenced, offer both PowerShell and Bash/CLI script snippets.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-deploy-packages.md
...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-deploy-packages.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-based tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and running SSIS packages, with no mention of Linux-compatible alternatives or cross-platform tooling. There are no examples or guidance for Linux users, and the documentation assumes the use of Windows environments and tools throughout.
Recommendations
- Explicitly state the platform requirements and whether deployment and management of SSIS packages is supported from Linux or macOS environments.
- If possible, provide guidance or alternatives for Linux users, such as using Azure Data Factory web UI, REST APIs, or cross-platform command-line tools.
- Include examples or documentation links for deploying SSIS packages from non-Windows environments, or clarify if such scenarios are not supported.
- Avoid assuming the use of Windows tools by default; mention cross-platform options first if available, or clearly indicate when only Windows tools are supported.
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
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation exhibits mild Windows bias, primarily in its recommendations and tooling references. In the 'TIP' section about testing REST APIs, only Windows-centric tools (Visual Studio, PowerShell's Invoke-RestMethod, web browser) are mentioned, with PowerShell called out explicitly. Additionally, when describing how to convert a certificate to base64, the only linked guide uses PowerShell, a Windows-first tool. There is no mention of Linux-native tools or cross-platform alternatives for these common tasks, and Windows tools are listed first and exclusively.
Recommendations
- When suggesting tools for testing REST APIs, include cross-platform and Linux-native options such as curl, httpie, or Postman, alongside PowerShell and Visual Studio.
- When referencing certificate conversion, provide Linux/Unix command-line alternatives (e.g., openssl) and link to relevant documentation or examples.
- Avoid listing Windows tools first or exclusively; present cross-platform or platform-neutral options where possible.
- Explicitly state that all examples and tooling recommendations are applicable to both Windows and Linux, or provide platform-specific instructions as needed.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sap-hana.md
.../blob/main/articles/data-factory/connector-sap-hana.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing 'SAP HANA CLIENT for Windows' as the ODBC driver to install, without mentioning Linux or cross-platform alternatives. No Linux installation instructions or examples are provided for the ODBC driver or integration runtime setup. The authentication examples and terminology (e.g., 'Windows authentication') are Windows-centric, and there is no guidance for Linux environments.
Recommendations
- Explicitly mention and provide instructions for installing the SAP HANA ODBC driver on Linux (and macOS, if supported), including links to relevant SAP documentation.
- Clarify that the Self-hosted Integration Runtime can be installed on both Windows and Linux, and provide platform-specific setup instructions or references.
- Include Linux-based examples for connection strings and authentication, noting any differences (e.g., Kerberos or other authentication mechanisms on Linux).
- Avoid using 'Windows authentication' as the only named authentication method; instead, describe all supported authentication types and their applicability to different operating systems.
- Where screenshots or UI steps are shown, note any differences for Linux users if applicable, or clarify if the experience is the same across platforms.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-sap.md
...in/articles/data-factory/connector-troubleshoot-sap.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation provides only a PowerShell (Windows-specific) command (Test-NetConnection) for troubleshooting connectivity to the SAP server, without offering equivalent Linux/macOS commands or guidance. This prioritizes Windows tools and patterns, and omits Linux alternatives, making the instructions less accessible for users running integration runtime on Linux or macOS.
Recommendations
- Include equivalent Linux/macOS troubleshooting commands, such as using 'nc', 'telnet', or 'curl' to test port connectivity.
- Present both Windows and Linux/macOS examples side by side, or at least mention alternatives for non-Windows users.
- Avoid assuming the integration runtime is always installed on a Windows machine; clarify platform support and provide guidance accordingly.
- Consider a table or section that lists commands for multiple operating systems to improve parity and inclusivity.
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 exclusively provides troubleshooting steps using the SharePoint Online Management Shell, a Windows-only tool, and PowerShell commands. There are no equivalent instructions or examples for Linux or cross-platform environments. The guidance assumes the user is on Windows, with no mention of alternatives for Linux or macOS users.
Recommendations
- Provide equivalent troubleshooting steps using cross-platform tools such as Azure CLI, Microsoft Graph API, or PowerShell Core (pwsh) where possible.
- Explicitly state platform requirements for the SharePoint Online Management Shell and offer alternatives or workarounds for Linux/macOS users.
- Include Linux/macOS command-line examples or scripts, or reference official Microsoft documentation for performing these tasks on non-Windows platforms.
- Consider restructuring the troubleshooting steps to present cross-platform solutions first, or at least alongside Windows-specific instructions.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-square.md
...cs/blob/main/articles/data-factory/connector-square.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by explicitly stating support for Windows versions of the self-hosted integration runtime and linking only to Windows prerequisites. There are no mentions of Linux support, nor are there any Linux-specific instructions or examples. The documentation does not clarify whether Linux is unsupported or simply omitted, and no Linux tools or command-line examples are provided.
Recommendations
- Clarify whether the self-hosted integration runtime supports Linux, and if so, provide explicit instructions and prerequisites for Linux environments.
- If Linux is not supported, state this clearly to avoid ambiguity.
- Include Linux-specific examples or references where relevant, such as installation steps, configuration, or troubleshooting.
- Ensure parity in documentation structure and examples for both Windows and Linux users, including screenshots or command-line snippets as appropriate.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime.md
.../data-factory/create-azure-ssis-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (SSDT, SSMS, dtutil), providing PowerShell as the only command-line automation example, and omitting Linux-native tooling or instructions. There are no examples or guidance for Linux users, and the documentation assumes familiarity with Windows-based administrative patterns.
Recommendations
- Include equivalent instructions and examples for Linux users, such as using Azure CLI for provisioning and configuration tasks instead of only PowerShell.
- Mention cross-platform tools (e.g., Azure Data Studio) alongside or before Windows-only tools like SSMS and SSDT.
- Provide command-line examples using Bash or Azure CLI where PowerShell is referenced.
- Clarify which tools are cross-platform and which are Windows-only, and suggest alternatives for non-Windows environments.
- Add a section or notes specifically addressing Linux/macOS users, outlining supported workflows and toolchains.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-portal.md
...actory/create-azure-ssis-integration-runtime-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by referencing PowerShell for advanced configuration (e.g., backup storage redundancy), mentioning Windows-specific tools (e.g., SSMS, UNC paths), and omitting Linux-specific examples or guidance. There are no Linux command-line examples, and file system integration assumes Windows-style paths and authentication. The documentation does not address Linux users' needs or provide parity in instructions for non-Windows environments.
Recommendations
- Provide equivalent CLI examples using Azure CLI and Bash scripts for all PowerShell instructions, especially for tasks like configuring backup storage redundancy.
- Clarify how Linux users can interact with Azure Files and file system package stores, including mounting instructions and authentication methods suitable for Linux.
- Mention cross-platform tools (e.g., Azure Data Studio) alongside SSMS for managing SSIS packages.
- Include examples of file paths and access patterns for both Windows (UNC paths) and Linux (NFS/Samba mounts or Azure Files via SMB/NFS).
- Explicitly state any platform limitations or differences in experience between Windows and Linux users.
- Ensure all referenced tools and workflows are accessible or have documented alternatives for Linux users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-sybase.md
...cs/blob/main/articles/data-factory/connector-sybase.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing 'Windows authentication' as a primary authentication method, omitting mention of Linux authentication patterns. It also assumes the installation of Sybase providers on the Integration Runtime without clarifying Linux support or providing Linux-specific instructions. There are no examples or guidance for Linux environments, and Windows terminology appears before or instead of cross-platform alternatives.
Recommendations
- Explicitly state whether the Sybase connector and required providers are supported on Linux-based Self-hosted Integration Runtime, and provide installation instructions for Linux if supported.
- Include Linux authentication options or clarify the authentication mechanisms available on Linux hosts.
- Provide examples and troubleshooting tips for both Windows and Linux environments, including any differences in setup or configuration.
- Avoid listing 'Windows authentication' before or instead of cross-platform authentication methods unless it is the only supported option, and clarify platform-specific limitations.
- If Linux is not supported, clearly state this in the prerequisites section to avoid confusion.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-file-system.md
...les/data-factory/connector-troubleshoot-file-system.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing PowerShell for configuring the self-hosted integration runtime (SHIR) and omitting any mention of Linux command-line tools or configuration methods. There are no Linux or cross-platform examples provided, and the only setup instructions link to a PowerShell-based workflow.
Recommendations
- Include equivalent Linux command-line instructions (e.g., Bash scripts or CLI commands) for configuring SHIR file system access.
- Mention cross-platform tools or provide guidance for both Windows and Linux environments.
- Explicitly state platform requirements or limitations if certain features are only available on Windows.
- Add examples or links for Linux users to ensure parity and inclusivity in troubleshooting steps.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-teradata.md
.../blob/main/articles/data-factory/connector-teradata.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows bias in several areas: Windows authentication is consistently listed before other authentication types, and Windows-specific dependencies (such as Visual C++ Redistributable) are referenced without Linux equivalents or guidance. There are no examples or instructions for Linux environments, such as installing the Teradata .NET Data Provider or drivers on Linux-based self-hosted integration runtimes. All examples and troubleshooting steps implicitly assume a Windows environment.
Recommendations
- Add explicit guidance and examples for Linux-based self-hosted integration runtimes, including how to install required Teradata drivers and dependencies on Linux.
- When listing authentication types or configuration options, avoid putting 'Windows' first unless it is the most common or only supported option; otherwise, use a neutral or alphabetical order.
- For prerequisites, provide Linux equivalents or alternatives to Windows-only dependencies (e.g., Visual C++ Redistributable), or clarify if the connector is only supported on Windows-based runtimes.
- Include troubleshooting tips and environment setup steps for both Windows and Linux platforms.
- Clearly state platform support limitations (if any) early in the documentation, so Linux users can quickly determine applicability.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-self-hosted-integration-runtime.md
...data-factory/create-self-hosted-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. All installation instructions, prerequisites, and examples assume or require Windows OS. Only Windows versions are listed as supported, and all command-line automation is shown using PowerShell or Windows batch tools. There are no instructions or examples for Linux or macOS, nor any mention of cross-platform support. Windows-specific tools (e.g., registry editing, Windows DPAPI, Notepad, Windows Firewall, NT SERVICE accounts) are referenced throughout, and Linux equivalents are not discussed.
Recommendations
- Clearly state early in the document whether Linux or macOS are supported or not. If not, make this explicit in the prerequisites.
- If Linux is supported, add a dedicated section for Linux installation, including supported distributions, dependencies (e.g., .NET Core/Mono), and step-by-step instructions.
- Provide Linux/macOS equivalents for all PowerShell and Windows command-line examples (e.g., Bash scripts, CLI commands).
- Reference Linux-native tools and configuration files (e.g., systemd for services, iptables/firewalld for firewall, environment variables for JAVA_HOME).
- If Windows-only features (such as DPAPI or registry edits) are required, explain the Linux/macOS alternatives or limitations.
- For proxy and firewall configuration, include Linux-specific instructions (e.g., editing /etc/hosts, /etc/environment, or using ufw/firewalld).
- Mention any differences in credential storage, service accounts, or permissions models between Windows and Linux.
- If the product is Windows-only, consider renaming the article or adding a prominent note to clarify this, and avoid implying cross-platform support.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-resource-manager-template.md
...ure-ssis-integration-runtime-resource-manager-template.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively provides PowerShell-based deployment and management commands for Azure-SSIS IR, with no mention of cross-platform tools or Linux/macOS-compatible alternatives. All automation and CLI examples are Windows-centric, and there is no guidance for users on Linux or macOS platforms.
Recommendations
- Add Azure CLI examples for deploying and managing Azure-SSIS IR, as Azure CLI is cross-platform and works on Windows, Linux, and macOS.
- Mention and demonstrate how to use the Azure Portal for template deployment, which is platform-agnostic.
- Explicitly state the platform requirements for PowerShell commands, and provide links or instructions for using PowerShell Core on non-Windows systems if PowerShell must be used.
- Reorder or supplement examples so that cross-platform methods (e.g., Azure CLI, Portal) are presented before or alongside Windows-specific tools.
- Include a note or section addressing Linux/macOS users, outlining their options for performing the same tasks.
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 demonstrates a Windows bias by prioritizing Windows authentication, tools, and patterns. Windows authentication is described in detail, with examples and explicit mention of domain\username formats. Troubleshooting steps and configuration instructions exclusively reference Windows tools such as SQL Server Management Studio, SQL Server Configuration Manager, and Windows Firewall, with no mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for connecting to SQL Server from Linux environments or using Linux-based authentication methods.
Recommendations
- Add equivalent instructions and examples for Linux environments, such as using sqlcmd, Azure Data Studio, or ODBC/JDBC clients on Linux.
- Include troubleshooting steps for configuring SQL Server connectivity on Linux, such as firewall configuration using iptables/firewalld and enabling TCP/IP in Linux-based SQL Server installations.
- Provide authentication examples relevant to Linux, such as SQL authentication, Kerberos, or Azure Active Directory authentication, and clarify any limitations or differences.
- Avoid assuming Windows as the default environment; present cross-platform guidance or clearly indicate when steps are Windows-specific.
- Reference or link to official Microsoft documentation for SQL Server on Linux where appropriate.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-azure-blob-storage.md
...a-factory/connector-troubleshoot-azure-blob-storage.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates Windows bias by referencing Windows-specific tools (diawp.exe.config) and configuration steps (disabling FIPS mode on Windows VMs) without mentioning Linux equivalents or providing guidance for non-Windows environments. There are no troubleshooting steps or examples for Linux-based self-hosted integration runtimes, and the only OS-specific advice is for Windows.
Recommendations
- Include troubleshooting steps for Linux-based self-hosted integration runtimes, such as how to handle FIPS or MD5 issues on Linux.
- When referencing configuration files or tools (e.g., diawp.exe.config), specify if these are Windows-only and provide Linux equivalents or note if not applicable.
- Add examples or notes for both Windows and Linux environments where OS-specific troubleshooting may differ.
- Avoid assuming the user is on Windows; use neutral language or provide parity in instructions for all supported platforms.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-shared-self-hosted-integration-runtime-powershell.md
...eate-shared-self-hosted-integration-runtime-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples are provided exclusively using Azure PowerShell, with explicit instructions to use Windows PowerShell ISE and references to installing Azure PowerShell on Windows. There are no examples or guidance for performing these tasks using cross-platform tools such as Azure CLI, Bash, or on Linux/macOS environments. The installer instructions for the self-hosted integration runtime do not clarify Linux support or alternatives.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works on Windows, Linux, and macOS.
- Avoid referencing Windows-specific tools such as 'Windows PowerShell ISE' unless absolutely necessary; instead, use generic terms like 'terminal' or 'command line interface'.
- Clarify whether the self-hosted integration runtime installer is available for Linux/macOS, and if not, explicitly state the platform requirements.
- Include instructions or notes for users on Linux/macOS, even if only to clarify limitations or alternative approaches.
- Reorganize sections so that cross-platform solutions (e.g., Azure CLI) are presented before or alongside Windows/PowerShell-specific instructions.
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 shows a mild Windows bias. It references Windows-specific tools (WinSCP) for SFTP troubleshooting and recommends a third-party web tool for base64 encoding, but does not mention Linux-native alternatives. In the code examples for base64 encoding, both C# and Python are provided, but the Python example uses a Windows-style file path. The only explicit command-line example for checking SFTP host key fingerprints is given for Linux, but there are no corresponding Windows/PuTTY examples. There is a lack of parity in tool recommendations and examples for Linux users.
Recommendations
- When recommending tools for verifying SFTP connections, mention both Windows (e.g., WinSCP) and Linux (e.g., OpenSSH sftp, FileZilla) options.
- For base64 encoding, provide Linux-native command-line examples (e.g., 'base64' command) alongside Python and C#.
- In file path examples, use platform-neutral notation or provide both Windows and Linux path examples.
- When referencing third-party tools, suggest both web-based and command-line alternatives for different platforms.
- For SFTP host key fingerprint checking, include Windows/PuTTYgen instructions as well as the Linux ssh-keygen example.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-factory-troubleshoot-guide.md
...ticles/data-factory/data-factory-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exhibits a moderate Windows bias. Several troubleshooting steps and code examples reference Windows-specific tools (such as PowerShell and Fiddler) without providing Linux or cross-platform alternatives. For example, the Azure Batch troubleshooting section provides only PowerShell-based unzip commands, and the use of Fiddler is described in detail without mentioning Linux-compatible network tools. There are also references to Windows behaviors (e.g., Windows zip compression defaults) without equivalent Linux context. No Linux shell or tool examples are provided alongside the Windows ones.
Recommendations
- For every PowerShell example, provide an equivalent Bash or Linux shell command (e.g., using unzip or tar for extracting files).
- When recommending tools like Fiddler for network troubleshooting, mention and provide instructions for Linux alternatives such as tcpdump, Wireshark, or curl.
- Where Windows-specific behaviors are discussed (e.g., zip compression algorithms), clarify how the same scenario would appear or be handled on Linux systems.
- Ensure that any references to file paths, command syntax, or troubleshooting steps are cross-platform or include both Windows and Linux variants.
- Review all troubleshooting steps and add Linux/macOS guidance where currently only Windows is mentioned.
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 a Windows bias, particularly in the FIPS troubleshooting section, where only Windows-specific file paths (e.g., C:\Program Files\...) and configuration steps are provided. There are no equivalent instructions or examples for Linux-based environments, nor is there any mention of Linux-specific troubleshooting steps for self-hosted integration runtime scenarios. This may leave Linux users without clear guidance.
Recommendations
- Provide equivalent troubleshooting steps and file paths for Linux-based self-hosted integration runtime installations, if supported.
- Explicitly mention whether the FIPS workaround and configuration applies only to Windows or also to Linux, and offer Linux-specific instructions if applicable.
- Wherever file paths or commands are shown, include both Windows and Linux variants (e.g., C:\Program Files\... and /opt/... or /usr/local/...).
- Audit other troubleshooting steps to ensure parity for Linux environments, including references to environment variables, service restarts, and configuration file locations.
- Add a note clarifying platform support for self-hosted integration runtime and connector troubleshooting, and link to platform-specific documentation where appropriate.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-hive.md
...n/articles/data-factory/connector-troubleshoot-hive.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides troubleshooting steps that reference Windows-specific paths (e.g., C:\Program Files\MIT\Kerberos\bin) and environment variable configuration, without mentioning Linux equivalents. There are no Linux or cross-platform examples for Kerberos configuration or file locations, and the instructions assume a Windows environment.
Recommendations
- Include Linux-specific instructions for Kerberos configuration, such as referencing /etc/krb5.conf and relevant environment variables.
- Provide parallel examples for both Windows and Linux file paths and system variable settings.
- Explicitly state when steps are platform-specific, and offer alternatives for other operating systems.
- Consider using cross-platform language and tools where possible, or link to platform-specific documentation.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-factory-ux-troubleshoot-guide.md
...les/data-factory/data-factory-ux-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias in its troubleshooting instructions. For network troubleshooting, only Windows Command Prompt and the nslookup command are mentioned, with screenshots and instructions tailored to Windows users. There are no examples or guidance for performing equivalent steps on Linux or macOS systems. Additionally, browser troubleshooting steps are presented for Edge and Chrome, which are available cross-platform, but the instructions and screenshots are Windows-centric.
Recommendations
- Include equivalent troubleshooting steps for Linux and macOS users, such as using the terminal and the dig or nslookup commands.
- Provide example commands and expected outputs for Linux/macOS terminals alongside Windows Command Prompt instructions.
- Add notes or screenshots for browser settings on Linux/macOS versions of Chrome and Edge, or clarify any differences.
- Where referencing tools like Command Prompt, mention cross-platform alternatives (e.g., Terminal on macOS/Linux) and provide parallel instructions.
- Explicitly state that the troubleshooting steps apply to all platforms, or call out any platform-specific differences.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-synapse-sql.md
...les/data-factory/connector-troubleshoot-synapse-sql.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. References to 'SQL Tools' and 'SQL Server Management Studio (SSMS)' are made without mentioning cross-platform or Linux alternatives. The only explicit firewall configuration link is for Windows Firewall. No Linux-specific tools, commands, or troubleshooting steps are provided, and there are no PowerShell examples, but the absence of Linux/Unix command-line or tool references is notable.
Recommendations
- When referencing 'SQL Tools' or 'SQL Server Management Studio (SSMS)', also mention cross-platform alternatives such as Azure Data Studio, sqlcmd, or other Linux-compatible tools.
- For firewall configuration, provide links or instructions for both Windows Firewall and Linux-based firewalls (e.g., UFW, firewalld, iptables).
- Include Linux command-line examples or troubleshooting steps where relevant, especially for connectivity and firewall issues.
- Explicitly state that the troubleshooting steps apply to both Windows and Linux environments, or provide environment-specific notes where behavior may differ.
- Where possible, use neutral terminology (e.g., 'database client tool') and provide examples for both major platforms.