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 501-525 of 1000 flagged pages
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-hdfs.md ...docs/blob/main/articles/data-factory/connector-hdfs.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
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 ways: authentication options and examples prioritize Windows (Kerberos/Windows authentication) and Windows-specific tools (Ksetup, netdom), with command-line examples and configuration steps focused on Windows environments. Linux equivalents or instructions are either missing or only briefly mentioned, and Windows terminology is used as the default throughout.
Recommendations
  • Provide equivalent Linux-based setup instructions for Kerberos authentication, including commands for joining a Linux host to a Kerberos realm and configuring krb5.conf.
  • Include Linux shell command examples (e.g., kinit, klist, editing /etc/krb5.conf) alongside or before Windows command examples.
  • Clarify that 'Windows authentication' refers to Kerberos authentication and explain how it maps to Linux/Unix environments.
  • Add explicit guidance for configuring the self-hosted integration runtime on Linux hosts, if supported.
  • Balance the order of presentation so that Linux/Unix approaches are described before or alongside Windows approaches, rather than after.
  • Reference Linux-native tools and patterns (such as MIT Kerberos utilities) wherever Windows tools (Ksetup, netdom) are mentioned.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by prioritizing Windows-centric tools and workflows, such as Azure DevOps, PowerShell, and Visual Studio/NUnit, with little to no mention of Linux or cross-platform alternatives. Examples and recommendations for CI/CD, automated testing, and scripting focus on Windows tools and environments, while Linux-native or cross-platform approaches are omitted.
Recommendations
  • Include Linux and cross-platform examples for CI/CD pipelines, such as using GitHub Actions, Azure CLI in Bash, or other popular CI/CD tools (e.g., Jenkins, GitLab CI) that are commonly used on Linux.
  • Provide sample scripts and automation steps using Bash and Azure CLI, not just PowerShell.
  • Mention and demonstrate cross-platform testing frameworks (e.g., pytest for Python, Mocha for Node.js) alongside NUnit/Visual Studio.
  • Clarify that Azure CLI and Data Factory tools are available on Linux/macOS and provide installation or usage notes for those platforms.
  • When referencing tools like PowerShell or Visual Studio, also reference their Linux/macOS equivalents or alternatives.
  • Ensure screenshots and UI walkthroughs do not assume a Windows environment exclusively.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell, SSMS (SQL Server Management Studio), and Windows-centric tooling and workflows. There are no examples or instructions for Linux users, such as using Azure CLI, cross-platform SQL tools, or alternative scripting environments. The documentation assumes the use of Windows-based tools for key operations, and does not provide parity for Linux or cross-platform users.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell instructions, ensuring cross-platform compatibility.
  • Offer examples using cross-platform SQL tools (e.g., Azure Data Studio, sqlcmd) alongside SSMS.
  • Explicitly mention when steps can be performed from Linux/macOS, and provide guidance for those environments.
  • Avoid assuming the use of Windows-only tools; where SSMS is referenced, suggest Azure Data Studio or other cross-platform alternatives.
  • Add notes or callouts for Linux users, especially for scripting, orchestration, and database management steps.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by listing PowerShell and .NET as primary tooling options for creating datasets, both in the main text and in the quickstart links. There is no mention of Linux-native tools, Bash, or cross-platform CLI examples. PowerShell is referenced before REST API or other platform-neutral options, and there are no Linux-specific instructions or parity in example tooling.
Recommendations
  • Add examples and quickstart links for using Azure CLI (az), which is cross-platform and commonly used on Linux.
  • Include Bash shell scripting examples alongside PowerShell, especially for automation scenarios.
  • Explicitly mention that REST API and Azure Resource Manager templates are platform-agnostic and suitable for Linux users.
  • Reorder tooling references so that cross-platform tools (Azure CLI, REST API) are listed before Windows-specific tools (PowerShell, .NET).
  • Consider adding a section or note for Linux/macOS users, highlighting supported tools and any differences in experience.
  • Ensure that screenshots and UI instructions do not assume a Windows environment unless necessary.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/change-data-capture-troubleshoot.md ...icles/data-factory/change-data-capture-troubleshoot.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example Windows First 🔧 Windows Tools
Summary
The documentation page focuses exclusively on SQL Server and T-SQL (Transact-SQL) queries, which are primarily associated with Windows environments. There are no examples or troubleshooting steps for Linux-based SQL sources (such as SQL Server on Linux, PostgreSQL, or MySQL), nor is there mention of command-line tools or shell environments outside of Windows-centric tools. The guidance assumes a Windows/SQL Server context, omitting Linux-native workflows or tools.
Recommendations
  • Include examples for Linux-based SQL sources, such as SQL Server on Linux, PostgreSQL, or MySQL, where CDC is supported.
  • Provide equivalent shell (bash) commands or scripts for Linux users, especially for database management and troubleshooting.
  • Mention and link to Linux-compatible tools (e.g., sqlcmd for Linux, Azure CLI) alongside or before Windows-specific tools.
  • Clarify whether the instructions apply equally to SQL Server on Linux, and note any differences in behavior or prerequisites.
  • Add troubleshooting steps or notes for common Linux-specific issues (e.g., permissions, service management, environment variables).
GitHub 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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a command-line example only for Azure PowerShell (a Windows-centric tool), with no equivalent example for Linux users (such as Azure CLI, Bash, or cross-platform scripting). The only automation example is PowerShell, and there is no mention of Linux-native or cross-platform alternatives, which may make Linux users feel unsupported or excluded.
Recommendations
  • Add Azure CLI examples for creating and configuring Azure Integration Runtime, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell must be used, and provide installation guidance.
  • Where possible, provide Bash or REST API examples for automation to ensure parity for Linux and macOS users.
  • Reorder or supplement the documentation so that cross-platform tools (like Azure CLI) are presented before or alongside Windows-specific tools.
  • Include a note clarifying that the UI steps are platform-agnostic, but that command-line automation can be performed from any OS with the appropriate tools.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits a moderate Windows bias. While most of the content is platform-neutral (focused on Azure Data Factory and Microsoft 365), there are notable areas where Windows/PowerShell tools and patterns are referenced or prioritized. Specifically, certificate conversion is demonstrated using PowerShell, and PowerShell is listed as a primary SDK/tool for pipeline creation. There are no explicit Linux or cross-platform CLI examples, and Windows-centric tools are mentioned before or instead of Linux alternatives.
Recommendations
  • Provide Linux and cross-platform alternatives for certificate conversion (e.g., using OpenSSL commands) alongside PowerShell instructions.
  • Include Azure CLI and/or Bash script examples for common tasks such as pipeline creation and certificate management.
  • When listing tools or SDKs, avoid listing Windows-specific tools (like PowerShell) first or exclusively; instead, present Azure CLI, REST API, and SDKs in a neutral order.
  • Explicitly mention that all steps can be performed from Linux/macOS environments using Azure CLI, REST API, or other cross-platform tools.
  • Add example commands and scripts for Linux environments where relevant, especially for tasks like certificate manipulation and automation.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows authentication, Windows-style usernames (domain\username), and Windows-specific tools and patterns (such as SQL Server Management Studio and Windows Firewall). Troubleshooting steps and configuration instructions are written solely for Windows environments, with no mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for Linux users, such as using sqlcmd, Azure Data Studio, or Linux firewall configuration.
Recommendations
  • Add Linux authentication guidance, including examples for Kerberos or SQL authentication from Linux hosts.
  • Provide alternative instructions for connecting to Amazon RDS for SQL Server from Linux, such as using sqlcmd or Azure Data Studio.
  • Include Linux-based troubleshooting steps, such as configuring iptables or firewalld for port access.
  • Clarify that the instructions for tools like SQL Server Management Studio and Windows Firewall are Windows-specific, and suggest cross-platform or Linux-native alternatives.
  • When giving username examples, include both Windows (domain\username) and Linux/SQL (username@hostname or just username) formats.
  • Explicitly state any platform limitations or requirements, and provide links to relevant Linux documentation where possible.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-hive.md ...docs/blob/main/articles/data-factory/connector-hive.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows support and tools (such as the self-hosted integration runtime's Windows prerequisites) without mentioning Linux equivalents or support. There are no Linux-specific instructions, examples, or clarifications about cross-platform compatibility for the integration runtime or connector. All example configurations and property descriptions are generic or reference Azure services, but the only explicit OS reference is to Windows, and there is no guidance for Linux users.
Recommendations
  • Explicitly state whether the self-hosted integration runtime and Hive connector support Linux hosts, and provide a link to Linux prerequisites if available.
  • If Linux is supported, add Linux-specific setup instructions or notes alongside Windows instructions.
  • Include examples or troubleshooting tips relevant to Linux environments (e.g., certificate paths, permissions, service management).
  • Avoid phrasing that implies Windows is the only supported or primary platform unless that is actually the case; if so, clarify this limitation up front.
  • Where referencing OS-specific features (such as the system trust store), clarify how this applies on both Windows and Linux.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-microsoft-access.md ...in/articles/data-factory/connector-microsoft-access.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Microsoft Access ODBC driver, which is only available on Windows. All example connection strings use Windows-style file paths (e.g., C:\mydatabase.accdb), and there is no mention of Linux or cross-platform alternatives for running the Integration Runtime or accessing Microsoft Access data. The prerequisites and setup instructions implicitly assume a Windows environment, and there are no examples or guidance for Linux users.
Recommendations
  • Explicitly state that the Microsoft Access ODBC driver is only available on Windows, and clarify platform limitations in the prerequisites.
  • If possible, provide guidance or workarounds for Linux users, such as using third-party ODBC drivers (e.g., MDBTools) or running the Integration Runtime in a Windows container/VM on Linux.
  • Include example connection strings and file paths for both Windows and Linux (if supported), or clearly indicate that only Windows is supported.
  • Add a section addressing cross-platform considerations and alternatives for non-Windows environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/introduction.md ...e-docs/blob/main/articles/data-factory/introduction.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias, primarily through the explicit mention and prioritization of PowerShell and Windows-centric tools in the 'Monitor' and 'Related content' sections. PowerShell is listed as a primary automation/monitoring method, and the quickstart links highlight PowerShell before cross-platform options like Python or REST. There are no explicit Linux CLI or Bash examples, nor is there mention of Linux-native tooling or parity in automation/monitoring approaches.
Recommendations
  • Add explicit examples and quickstart links for Bash/CLI usage, especially for common Linux environments.
  • When listing automation or monitoring tools (e.g., PowerShell, API), ensure cross-platform options (such as Azure CLI, Bash scripts) are mentioned alongside or before Windows-specific tools.
  • In the 'Monitor' section, include examples using Azure CLI and REST API, not just PowerShell.
  • Review the order of quickstart links to avoid implying PowerShell is the primary or preferred method; consider listing cross-platform options first or grouping by platform.
  • Where PowerShell is referenced, add a note or link to equivalent Azure CLI documentation for Linux/macOS users.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows authentication as a primary supported authentication method, omitting any mention of Linux authentication or setup. There are no Linux-specific instructions, examples, or troubleshooting steps. The documentation assumes the use of Windows-based Integration Runtime and does not address Linux environments or tools.
Recommendations
  • Add explicit instructions for setting up the Integration Runtime and Sybase data provider on Linux hosts, if supported.
  • Include Linux authentication options (such as Kerberos or other supported mechanisms) and clarify if only Windows authentication is supported.
  • Provide Linux command-line examples for installation and configuration, alongside or before Windows examples.
  • Mention any limitations or differences when using Linux as the Integration Runtime host.
  • Clarify in the prerequisites and configuration sections whether Linux is supported or not, and provide parity guidance if it is.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
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, without mentioning or providing Linux alternatives or examples. The related content also highlights Windows authentication and PowerShell usage, further reinforcing the Windows-centric approach.
Recommendations
  • Explicitly state the platform requirements and limitations for the mentioned tools (e.g., SSDT, SSMS, dtutil, AzureDTExec), clarifying if they are Windows-only.
  • If Linux support is unavailable for these tools, provide a clear note to inform users and suggest any possible workarounds (such as using Docker containers or remote Windows VMs).
  • If any cross-platform or Linux-compatible deployment options exist (e.g., Azure CLI, REST APIs, or third-party tools), include examples and instructions for those.
  • Balance the order of presentation by mentioning any available cross-platform methods before or alongside Windows-specific tools.
  • Add a section addressing Linux/macOS users, outlining their options and any current limitations.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
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 file paths and configuration steps are provided (e.g., referencing 'C:\Program Files\Microsoft Integration Runtime' and editing 'diawp.exe.config'). There are no equivalent instructions or examples for Linux environments, nor is there any mention of Linux-based Self-hosted Integration Runtime scenarios. The troubleshooting steps and environment assumptions are Windows-centric, with no parity for Linux users.
Recommendations
  • Include equivalent troubleshooting instructions for Linux-based Self-hosted Integration Runtime environments, if supported.
  • When referencing file paths or configuration files, provide both Windows and Linux examples (e.g., 'C:\Program Files\...' and '/opt/...').
  • Explicitly state if certain features or troubleshooting steps are only applicable to Windows, and provide guidance or alternatives for Linux users.
  • Review all environment-specific instructions to ensure Linux users are not excluded from critical troubleshooting guidance.
  • Add notes or links to Linux-specific documentation where appropriate.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by providing only PowerShell commands for generating a Shared Access Signature (SAS) token, with no equivalent CLI, Bash, or cross-platform examples. The exclusive mention of PowerShell and the absence of Linux/macOS command-line alternatives may hinder users on non-Windows platforms. Additionally, the documentation refers to Windows tooling first and does not acknowledge or provide parity for Linux users.
Recommendations
  • Add Azure CLI examples for generating SAS tokens, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash script examples or reference REST API calls for SAS generation to ensure Linux parity.
  • When mentioning PowerShell, always provide an equivalent Azure CLI or REST API example immediately after or before, and clarify that PowerShell is Windows-centric.
  • Audit the documentation for any other places where Windows tools or patterns are mentioned exclusively, and ensure Linux/macOS alternatives are present.
  • Explicitly state that all features and steps are supported on both Windows and Linux, or note any exceptions.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation provides only a PowerShell (Windows-specific) command for troubleshooting SAP connector connectivity, with no equivalent Linux or cross-platform example. The use of Test-NetConnection is exclusive to Windows, and there is no mention of Linux tools or commands, nor any guidance for non-Windows environments.
Recommendations
  • Add equivalent Linux troubleshooting commands, such as using 'nc' (netcat) or 'telnet' to test connectivity to the SAP server port.
  • Explicitly mention that the provided PowerShell command is for Windows, and provide parallel instructions for Linux and macOS environments.
  • Where possible, use cross-platform tools or provide guidance for both Windows and Linux users equally.
  • Review related content and troubleshooting steps to ensure Linux users are not excluded from guidance.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-azure-file-storage.md .../articles/data-factory/connector-azure-file-storage.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias, particularly in the 'Legacy model' section, where SMB path syntax (\\server\share) and user ID formats (AZURE\username) are presented in a Windows-centric way. There are no explicit Linux or cross-platform examples for mounting or accessing Azure Files, nor is there mention of Linux-specific tools or syntax. The documentation assumes familiarity with Windows conventions and omits guidance for Linux users.
Recommendations
  • Add Linux-specific examples for mounting Azure Files, such as using the 'mount.cifs' command and appropriate credential formats.
  • When showing SMB paths, provide both Windows (\\server\share) and Linux (/mnt/point with //server/share) syntax.
  • Clarify that the 'userid' and 'host' formats differ between Windows and Linux clients, and provide examples for each.
  • Mention Linux tools (e.g., cifs-utils) alongside Windows tools when discussing legacy SMB access.
  • Review all authentication and connection examples to ensure they are platform-agnostic or provide parallel Linux instructions where relevant.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-upgrade-guidance.md ...in/articles/data-factory/connector-upgrade-guidance.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell script example for programmatically identifying impacted objects, with no mention of Linux-compatible alternatives such as Bash, Azure CLI, or Python scripts. This creates a bias toward Windows users and tools, potentially excluding Linux or cross-platform users from easily following the guidance.
Recommendations
  • Provide equivalent examples using Azure CLI and/or Bash scripts for Linux and macOS users.
  • Mention cross-platform scripting options such as Python with the Azure SDK.
  • Clarify whether the PowerShell script can be run with PowerShell Core on Linux/macOS, and provide instructions if so.
  • Include notes or links to documentation for running automation tasks on non-Windows platforms.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-rest.md ...n/articles/data-factory/connector-troubleshoot-rest.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows-first bias by instructing users to use 'curl' in a 'Command Prompt window' without mentioning Linux or macOS terminals. Additionally, it recommends 'Fiddler', a Windows-only tool, for SSL troubleshooting, with no Linux or cross-platform alternatives suggested. No Linux- or macOS-specific instructions or examples are provided.
Recommendations
  • When referencing 'curl', use neutral language such as 'terminal' or 'command line' instead of 'Command Prompt window', and clarify that 'curl' is available on Windows, Linux, and macOS.
  • Provide example 'curl' commands that work on both Windows and Linux/macOS, noting any syntax differences if relevant.
  • When recommending tools like 'Fiddler', also mention cross-platform alternatives such as 'mitmproxy' or 'Charles Proxy' for Linux/macOS users.
  • Explicitly state that the troubleshooting steps apply to all major operating systems, and, where appropriate, provide OS-specific guidance.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/copy-data-tool-metadata-driven.md ...rticles/data-factory/copy-data-tool-metadata-driven.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a bias toward Windows environments by exclusively referencing SQL Server Management Studio (SSMS) for running SQL scripts, without mentioning cross-platform or Linux-compatible alternatives. There are no examples or instructions for Linux users, and the workflow assumes access to Windows tools. The documentation also refers to SQL Server-specific features (e.g., OPENJSON) without discussing parity or alternatives for other database engines commonly used on Linux.
Recommendations
  • Include instructions for running the generated SQL scripts using cross-platform tools such as Azure Data Studio, sqlcmd (available on Linux), or psql for PostgreSQL if supported.
  • Mention that SSMS is a Windows-only tool and provide Linux/macOS alternatives for connecting to SQL databases.
  • Add examples or notes for users who may be using Linux-based environments, including how to execute the scripts from the command line.
  • Clarify database engine requirements and discuss any limitations or differences for users running non-SQL Server databases, especially on Linux.
  • Review all screenshots and UI references to ensure they are not Windows-specific, or provide parallel guidance for Linux/macOS users where appropriate.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (such as SQL Server Management Studio and Windows Firewall), linking to Windows-centric configuration guides, and omitting Linux or cross-platform alternatives. There are no PowerShell scripts or command-line examples, but the troubleshooting steps and references assume a Windows environment and do not provide parity for Linux users.
Recommendations
  • When referencing tools like SQL Server Management Studio (SSMS), also mention cross-platform alternatives such as Azure Data Studio.
  • For firewall configuration, provide guidance for both Windows Firewall and common Linux firewalls (e.g., iptables, firewalld, ufw), or link to cross-platform documentation.
  • Where examples reference Windows-specific paths or tools, include equivalent instructions for Linux environments.
  • Explicitly state when a troubleshooting step is platform-agnostic, or provide separate sections/examples for Windows and Linux where necessary.
  • Audit all external documentation links to ensure Linux users are not excluded and that cross-platform resources are available.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-quickstart-prerequisites.md ...tory/includes/data-factory-quickstart-prerequisites.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools (e.g., Notepad, C:\ paths), omitting Linux/macOS equivalents, and using Windows directory conventions. There are no examples or instructions for Linux or cross-platform users for tasks like file creation or directory navigation.
Recommendations
  • Include equivalent instructions for Linux/macOS users, such as using nano, vim, or gedit as text editors.
  • Provide file path examples using both Windows (C:\...) and Unix-style (/home/user/...) conventions.
  • Mention cross-platform tools or approaches (e.g., VS Code, Azure CLI) where possible instead of only Windows-specific tools.
  • Explicitly state that the steps apply to all platforms, or provide platform-specific sections as needed.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by referencing the SAP HANA ODBC driver specifically as 'SAP HANA CLIENT for Windows' in the prerequisites, without mentioning Linux or cross-platform alternatives. No Linux installation guidance or examples are provided for setting up the ODBC driver or Integration Runtime, and authentication examples prioritize Windows authentication. There are no Linux-specific instructions or parity in tool references.
Recommendations
  • Explicitly mention and provide download links for both Windows and Linux versions of the SAP HANA ODBC client in the prerequisites.
  • Add instructions or references for installing the SAP HANA ODBC driver on Linux-based Integration Runtime hosts.
  • Include Linux-specific examples or notes where authentication or configuration differs (e.g., Kerberos or other Linux authentication methods).
  • Avoid using 'Windows authentication' as the default or primary example; instead, present both Windows and Linux authentication options equally, or clarify OS applicability.
  • Where screenshots or UI steps are shown, note any OS-specific differences or limitations.
  • Review all tool and command references to ensure Linux equivalents are mentioned and demonstrated where applicable.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows tools (Command Prompt), providing only Windows-centric troubleshooting commands (nslookup in Command Prompt), and omitting Linux/macOS equivalents. Browser troubleshooting steps are platform-agnostic, but when it comes to command-line diagnostics, only Windows is addressed, leaving out users on Linux or macOS.
Recommendations
  • Include Linux/macOS equivalents for command-line troubleshooting steps. For example, provide Terminal commands for nslookup or dig.
  • When referencing 'Command Prompt', also mention 'Terminal' for Linux/macOS users.
  • Add screenshots or example outputs from Linux/macOS terminals where relevant.
  • Use inclusive language such as 'Open Command Prompt (Windows) or Terminal (Linux/macOS)' to address all users.
  • Ensure that all troubleshooting steps are cross-platform or provide platform-specific tabs/sections.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
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 guide assumes the user is on Windows and does not mention alternatives for Linux or macOS users.
Recommendations
  • Provide equivalent instructions for Linux and macOS users, such as using cross-platform PowerShell Core or Azure CLI where possible.
  • Mention whether the SharePoint Online Management Shell can be run on PowerShell Core (which is cross-platform) or if there are REST API alternatives.
  • If no direct Linux alternative exists, explicitly state this and suggest possible workarounds (e.g., using a Windows VM, Docker container, or REST API calls).
  • List both Windows and Linux/macOS steps side by side where applicable to ensure parity and inclusivity.
GitHub Create Pull Request
← Previous Page 21 of 40 Next →