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 576-600 of 1000 flagged pages
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-wait-activity.md
...in/articles/data-factory/control-flow-wait-activity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides sample PowerShell commands and references a PowerShell-based tutorial for running pipelines, with no equivalent examples or guidance for Linux or cross-platform CLI users (e.g., Azure CLI, Bash). This prioritizes Windows tooling and omits Linux-friendly alternatives.
Recommendations
- Add equivalent examples using Azure CLI commands, which are cross-platform and work on Linux, macOS, and Windows.
- Include Bash shell script examples for running pipelines, or at least mention how to accomplish the same tasks outside of PowerShell.
- Reference tutorials and quickstarts that use Azure CLI or REST API, not just PowerShell.
- Explicitly state that the Wait activity and pipeline operations can be managed from any OS, and provide links to relevant cross-platform documentation.
Create Pull Request
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-web-activity.md
...ain/articles/data-factory/control-flow-web-activity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias primarily in the authentication section, where only a PowerShell snippet is provided for base64-encoding a PFX certificate file. There are no equivalent Linux or cross-platform command examples (e.g., using OpenSSL or base64 utilities). The documentation assumes familiarity with Windows tooling and omits Linux alternatives, which may hinder users on non-Windows platforms.
Recommendations
- Provide equivalent Linux/macOS command-line examples for base64-encoding a PFX file (e.g., using 'base64' and 'openssl').
- When referencing certificate conversion or encoding, mention both Windows and Linux tools and workflows.
- Wherever possible, use cross-platform language (e.g., 'your favorite utility' could be expanded to list both Windows and Linux tools).
- Review other sections for implicit Windows assumptions and add Linux/macOS guidance as needed.
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. No Linux or cross-platform CLI (such as Azure CLI or Bash) examples are provided, and the referenced tutorials are PowerShell-specific, which is most commonly used on Windows. There are no explicit Linux or cross-platform instructions or examples, and the documentation does not mention alternative tools or approaches for non-Windows users.
Recommendations
- Include equivalent Azure CLI and/or Bash examples alongside PowerShell instructions in both the main documentation and the related tutorials.
- Reference Linux/macOS-compatible tools and workflows where appropriate, not just PowerShell.
- Ensure that links in the 'Related content' section point to both PowerShell and Azure CLI (or Bash) versions of the tutorials, or provide a clear choice for users of different platforms.
- Explicitly state when instructions are platform-agnostic or provide notes for platform-specific steps.
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
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in its examples and tooling references. In the 'Manual execution with other APIs/SDKs' section, Azure PowerShell is prominently featured with a full command-line example, while there are no equivalent CLI/bash/Linux-native examples. The PowerShell example uses Windows-style paths and conventions, and the documentation does not mention or provide examples for the Azure CLI (az), which is cross-platform and commonly used on Linux/macOS. The ordering of examples also places PowerShell before Python and REST, reinforcing a Windows-first perspective.
Recommendations
- Add Azure CLI (az) examples for running pipelines, using bash syntax and Linux-style paths where appropriate.
- Include explicit bash or shell script examples for REST API usage (e.g., using curl), not just the HTTP request.
- Reorder the 'Manual execution with other APIs/SDKs' section to present cross-platform or Linux-friendly tools (Azure CLI, Python SDK, REST API with curl) before or alongside PowerShell.
- Clarify that Azure PowerShell is available cross-platform, but also provide Linux-native command-line alternatives.
- Where file paths are referenced, use both Windows and Linux path formats, or avoid OS-specific paths.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-pipelines-activities.md
...articles/data-factory/concepts-pipelines-activities.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows/Powershell bias by consistently referencing and linking to Powershell-based tutorials and quickstarts (e.g., 'quickstart-create-data-factory-powershell.md', 'tutorial-transform-data-spark-powershell.md') as the default or only walkthroughs for pipeline creation and data transformation. There are no equivalent examples or walkthroughs for Linux, Bash, or cross-platform CLI tools. The documentation does not mention or provide parity for Linux users or alternative command-line environments.
Recommendations
- Provide equivalent walkthroughs and quickstarts using Azure CLI (az), Bash scripts, or REST API examples that are cross-platform and work natively on Linux/macOS.
- When referencing tutorials or quickstarts, include both Powershell and non-Windows (e.g., Bash, Azure CLI) links side-by-side, or clarify that alternatives exist.
- Explicitly mention that Data Factory and Synapse pipelines can be managed from Linux/macOS using cross-platform tools, and provide links to relevant documentation.
- Ensure that all code snippets and automation examples are available in both Powershell and Bash/Azure CLI formats.
- Review related content and ensure Linux-friendly resources are equally discoverable and not only present as an afterthought.
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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based configuration scripts and referencing Windows-centric tools and patterns. There are no equivalent examples or guidance for Linux users, such as Bash/CLI scripts or cross-platform alternatives. The exclusive use of PowerShell and lack of mention of Linux environments or tooling may hinder accessibility for users operating from non-Windows systems.
Recommendations
- Provide equivalent Azure CLI (az) or Bash script examples alongside PowerShell scripts to support Linux and macOS users.
- Explicitly mention cross-platform options for configuring and managing Azure-SSIS IR, clarifying which steps are platform-agnostic.
- Reference documentation or tutorials for Linux users where relevant, ensuring parity in setup and management workflows.
- Avoid language that assumes the user is on Windows or using PowerShell by default; instead, present both Windows and Linux approaches equally.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-amazon-rds-for-oracle.md
...ticles/data-factory/connector-amazon-rds-for-oracle.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a mild Windows bias, particularly in the section describing how to configure TLS/SSL truststores for the self-hosted integration runtime. File paths are shown in Windows (C:\MyTrustStoreFile) format, and there is no mention of Linux file paths or examples. The documentation also omits explicit Linux command-line or environment variable examples, and does not clarify how to perform equivalent steps on Linux-based self-hosted IR machines.
Recommendations
- Provide parallel Linux examples for file paths (e.g., /home/user/MyTrustStoreFile) wherever Windows paths are shown.
- Explicitly mention that the self-hosted integration runtime can run on both Windows and Linux, and clarify any OS-specific requirements.
- Include Linux command-line examples for openssl commands (even if the commands are the same, show Linux-style paths and shell syntax).
- Document environment variable configuration (e.g., TNS_ADMIN) for both Windows and Linux, showing how to set them in each OS.
- Add a note or table summarizing any differences or additional steps for Linux users, especially for truststore placement and permissions.
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
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation demonstrates a moderate Windows bias. It references PowerShell and SSMS (SQL Server Management Studio, a Windows-only tool) for management and scripting tasks, and the 'ms.devlang' metadata is set to PowerShell. All scripting and management examples use T-SQL and SSMS, with no mention of cross-platform tools like Azure CLI, Azure Data Studio, or Linux-based workflows. There are no explicit Linux examples or guidance for non-Windows environments, and the documentation assumes the use of Windows-centric tools for orchestration and job management.
Recommendations
- Provide equivalent examples using Azure CLI for all PowerShell-based or portal-based instructions, especially for creating and managing Azure-SSIS IR and failover groups.
- Mention and provide examples using Azure Data Studio (which is cross-platform) as an alternative to SSMS for T-SQL scripting and job management.
- Explicitly state which steps can be performed from Linux/macOS environments and provide guidance or links for those users.
- Avoid assuming the use of Windows-only tools (like SSMS) as the default; instead, present cross-platform alternatives first or alongside.
- Update metadata (e.g., ms.devlang) to reflect multi-platform support if examples are added.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-amazon-redshift.md
...ain/articles/data-factory/connector-amazon-redshift.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 only Windows versions for supported environments, linking exclusively to the Windows ODBC driver installation guide, and omitting any mention of Linux or cross-platform support. There are no Linux-specific instructions, prerequisites, or examples, and the documentation does not clarify whether Linux is supported or provide guidance for Linux users.
Recommendations
- Add explicit information about Linux support for the Amazon Redshift connector, including supported distributions and prerequisites.
- Include links to the Amazon Redshift ODBC driver installation guides for Linux and macOS, not just Windows.
- Provide Linux-specific instructions for installing and configuring the self-hosted integration runtime, if supported.
- Clarify in the prerequisites and supported capabilities sections whether Linux-based self-hosted integration runtimes are supported, and if so, provide setup examples.
- Ensure all referenced tools and workflows are described in a cross-platform manner, or provide parallel instructions for both Windows and Linux environments.
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
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows authentication, Windows-style usernames (domain\username), and Windows-specific tools and configuration steps (such as SQL Server Management Studio, SQL Server Configuration Manager, and Windows Firewall). Troubleshooting and setup instructions are written only for Windows environments, with no mention of Linux equivalents or cross-platform alternatives. There are no examples or guidance for Linux users, nor any references to Linux-compatible tools or authentication methods.
Recommendations
- Include instructions and examples for connecting from Linux environments, such as using sqlcmd, Azure Data Studio, or other cross-platform tools.
- Provide Linux-compatible authentication guidance (e.g., Kerberos, SQL authentication) and clarify any limitations or differences.
- Add troubleshooting steps for Linux, such as configuring firewalls with iptables/firewalld, and enabling TCP/IP via configuration files or command-line tools.
- Avoid assuming the use of Windows-only tools (like SQL Server Management Studio or Configuration Manager); mention cross-platform or browser-based alternatives where possible.
- When showing username formats, clarify that domain\username is a Windows convention and provide Linux/Unix equivalents if applicable.
- Explicitly state OS requirements or limitations for features that are only available on Windows, and suggest workarounds or alternatives for Linux users.
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 →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation exhibits a Windows bias in its treatment of Azure Files, especially in the legacy model sections. It uses Windows-specific UNC path syntax (\\<storage name>.file.core.windows.net\<file service name>) and user ID formats (AZURE\<storage name>), and refers to SMB (Server Message Block) without clarifying cross-platform usage. There are no Linux or macOS-specific examples or guidance for mounting or accessing Azure Files, nor is there mention of Linux tools or commands for interacting with Azure Files. The documentation assumes a Windows environment for certain configuration patterns and omits Linux parity in both examples and conceptual explanations.
Recommendations
- Add explicit Linux and macOS examples for mounting and accessing Azure Files, using native tools (e.g., mount.cifs, smbclient) and syntax relevant to those platforms.
- When describing the legacy model, clarify how Linux users should specify paths and credentials, including the correct syntax and any differences from Windows.
- Include a section or note on cross-platform compatibility, highlighting any differences or additional steps required for Linux/macOS environments.
- Provide sample commands or configuration snippets for Linux (e.g., how to mount Azure Files using CIFS in Linux, with example /etc/fstab entries or mount commands).
- Avoid presenting Windows-specific patterns (such as UNC paths and AZURE\<storage name> user IDs) as the only or primary method; instead, present both Windows and Linux approaches side by side.
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 by exclusively providing PowerShell commands for generating shared access signatures (SAS) and referencing Windows-centric tools (e.g., New-AzStorageContext). No equivalent Linux, Bash, or cross-platform CLI examples are given. The only command-line example for SAS generation is in PowerShell, with no mention of Azure CLI or REST API alternatives, which are more platform-neutral. This may hinder Linux or macOS users who do not have access to PowerShell or prefer native tools.
Recommendations
- Provide equivalent Azure CLI examples for generating SAS tokens (e.g., using 'az storage account generate-sas' or 'az storage container generate-sas').
- Mention REST API options for SAS generation for maximum platform neutrality.
- When presenting command-line examples, either show both PowerShell and Bash/Azure CLI, or default to Azure CLI for cross-platform compatibility.
- Avoid referencing only Windows tools or patterns; ensure Linux/macOS users are equally supported in all procedural steps.
- Explicitly state that all steps can be performed on any platform, and provide links or guidance for Linux/macOS users where workflows differ.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/copy-activity-performance-features.md
...les/data-factory/copy-activity-performance-features.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias, particularly in the staged copy section where firewall configuration examples reference only the Windows firewall and port requirements. There are no Linux-specific examples or mentions of Linux firewall tools (such as iptables, firewalld, or ufw), and no Linux command-line or shell examples are provided. The documentation assumes a Windows-centric environment for on-premises scenarios, which may leave Linux users without clear guidance.
Recommendations
- When discussing firewall configuration, include Linux firewall tools (e.g., iptables, firewalld, ufw) alongside Windows Firewall, and provide equivalent Linux command examples.
- Explicitly mention that the self-hosted integration runtime can be installed on both Windows and Linux, and provide links or notes for Linux installation and configuration.
- Provide example commands or configuration snippets for both Windows and Linux environments where relevant (e.g., opening ports, managing services).
- Review all examples and ensure parity by including Linux-oriented content where Windows is referenced.
- Add a note or section clarifying cross-platform support and any platform-specific considerations for performance optimization.
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
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a Windows-first and Windows-heavy bias. Windows authentication and file share patterns are mentioned and exemplified throughout, with Windows path syntax (backslashes) and Windows-specific terminology (e.g., 'Windows authentication', 'local Powershell') appearing before or instead of Linux equivalents. Linux support is only briefly mentioned (via Samba), with no Linux-specific configuration or example paths provided. All sample paths, JSON, and UI screenshots use Windows conventions, and command-line references are to Powershell, with no Linux shell or mount examples.
Recommendations
- Provide Linux-specific examples for file share setup, including sample Linux paths (e.g., /mnt/share) and Linux user authentication.
- Include step-by-step instructions for configuring a Linux file share (e.g., using Samba), with sample configuration files and mount commands.
- Offer equivalent Linux shell commands (e.g., using smbclient or mount.cifs) alongside Powershell references.
- Use both Windows and Linux path syntax in examples and tables, or clarify when each is appropriate.
- Explicitly document authentication options for Linux environments (e.g., username/password, Kerberos, etc.) and note any differences from Windows.
- Add screenshots or UI walkthroughs that show Linux shares being configured, if possible.
- Review terminology to ensure Linux is presented as a first-class scenario, not just an afterthought.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-google-bigquery-legacy.md
...icles/data-factory/connector-google-bigquery-legacy.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows support and tools (such as the supported Windows versions for the integration runtime) without mentioning Linux support or providing Linux-specific instructions or examples. There are no Linux or cross-platform examples for configuring the integration runtime or specifying file paths, and the documentation implies a Windows-centric environment for setup and operation.
Recommendations
- Explicitly state whether the Self-hosted Integration Runtime and connector support Linux, and provide a link to Linux prerequisites if available.
- Include Linux-specific instructions or examples for file paths (e.g., using /home/user/key.json instead of C:\path\to\key.json).
- If Linux is supported, add screenshots or terminal commands for Linux environments where relevant.
- Mention any differences or limitations when running on Linux versus Windows, if applicable.
- Ensure parity in troubleshooting and configuration guidance for both Windows and Linux users.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-centric bias in several areas: authentication options and configuration steps are primarily described in terms of Windows authentication and Windows domain integration; configuration commands and tools (e.g., Ksetup, netdom) are Windows-specific and provided before or instead of Linux equivalents; and there are no explicit Linux-based integration runtime setup examples, even though HDFS and Kerberos are commonly used in Linux environments. The documentation assumes or prioritizes Windows environments for self-hosted integration runtime and Kerberos configuration, with only minimal references to Linux-native approaches.
Recommendations
- Provide parallel Linux-based examples for self-hosted integration runtime setup, including Kerberos configuration using native Linux tools (e.g., kinit, krb5.conf, systemd services).
- Include Linux shell command equivalents for all Windows command-line instructions (e.g., Ksetup, netdom), or clarify if certain steps are only required on Windows.
- Explicitly document how to configure the integration runtime and HDFS connector on a Linux host, including any differences in authentication, file paths, or permissions.
- Balance the order of presentation so that Linux and Windows approaches are given equal prominence, or group them under clear OS-specific headings.
- Clarify which authentication types are supported on Linux, and provide guidance for common Linux-based HDFS/Kerberos deployments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-hive-virtual-network-portal.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-hive-virtual-network-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Azure PowerShell, instructing users to edit the Windows hosts file, and providing no Linux or cross-platform alternatives for key steps such as integration runtime installation, VM setup, or host file modification. There are no Bash, CLI, or Linux-specific instructions or screenshots, and the workflow implicitly assumes a Windows environment throughout.
Recommendations
- Add equivalent instructions for Linux-based VMs, including how to install and configure the self-hosted integration runtime on Linux.
- Provide Azure CLI and/or Bash script alternatives alongside Azure PowerShell commands for all relevant steps.
- When referencing host file modifications, include Linux paths (e.g., /etc/hosts) and editing commands (e.g., using nano or vi) as alternatives to the Windows path.
- Clarify that the self-hosted integration runtime can be installed on both Windows and Linux, and link to platform-specific installation guides.
- Ensure screenshots and UI references are not exclusively Windows-centric, or provide Linux/terminal equivalents where appropriate.
- Explicitly state cross-platform compatibility and provide troubleshooting tips for both Windows and Linux environments.
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 →
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 being supported on Windows), mentioning Windows compatibility before any Linux equivalent (with no explicit mention of Linux support), and omitting Linux-specific instructions or examples for setting up the integration runtime or connector. There are no Linux command-line or configuration examples, and the prerequisites section only links to Windows requirements.
Recommendations
- Explicitly state whether the self-hosted integration runtime and Hive connector are supported on Linux, and provide a link to Linux prerequisites if available.
- Add Linux-specific setup instructions or examples for the self-hosted integration runtime and Hive connector, including any differences in configuration or file paths.
- Include example commands or scripts for Linux environments (e.g., shell scripts, Linux service management) alongside or before Windows/Powershell examples.
- Clarify any limitations or differences in feature support between Windows and Linux environments.
- Ensure that all references to operating system requirements or compatibility are balanced and not Windows-centric.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-hubspot.md
...s/blob/main/articles/data-factory/connector-hubspot.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing only Windows versions as supported for the self-hosted integration runtime, without mentioning Linux support or providing Linux-specific instructions. There are no Linux or cross-platform examples, and the prerequisites link directs users to a Windows-centric page. No Linux tools or patterns are discussed.
Recommendations
- Explicitly state whether Linux is supported for the self-hosted integration runtime, and if so, provide a link to Linux installation instructions.
- Include Linux-specific examples or notes where relevant, such as for setting up the integration runtime or troubleshooting.
- If Linux is not supported, clearly mention this limitation early in the documentation.
- Where possible, use cross-platform language and avoid assuming a Windows-only environment.
- Add a section comparing Windows and Linux support, including any feature or performance differences.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation assumes the use of Windows environments by requiring the Microsoft Access ODBC driver (which is only available on Windows), referencing file paths in Windows format (e.g., C:\mydatabase.accdb), and omitting any mention of Linux or cross-platform alternatives. There are no Linux-specific instructions, examples, or caveats, and all tooling and configuration steps are implicitly or explicitly Windows-centric.
Recommendations
- Explicitly state that the Microsoft Access ODBC driver is only available on Windows and clarify that Linux is not supported for this connector.
- If possible, mention any workarounds or third-party solutions for accessing Access databases from Linux (e.g., mdbtools, unixODBC with alternative drivers), even if not officially supported.
- Provide a table or section comparing platform support, so Linux users are aware of the limitations up front.
- Use neutral language in file path examples or provide both Windows and Linux path formats where relevant (even if Linux is not supported, this clarifies the scope).
- Add a note in the prerequisites or introduction highlighting the Windows-only nature of the required drivers and runtime environment.
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
Summary
The documentation demonstrates a moderate Windows bias. While most of the content is platform-neutral (focused on Azure UI, REST, .NET, and Python SDKs), there are several areas where Windows/PowerShell tools and patterns are mentioned first or exclusively. For example, certificate conversion is linked to a PowerShell-based guide, and Azure PowerShell is listed as a primary automation tool. There are no explicit Linux CLI or Bash examples, and Linux-native tooling is not referenced.
Recommendations
- Provide Linux/Bash equivalents for certificate conversion (e.g., using openssl and base64 commands) alongside the PowerShell example.
- Include Azure CLI examples and tutorials (az commands) for pipeline and resource creation, not just Azure PowerShell.
- When listing tools or SDKs, present cross-platform options (e.g., Azure CLI, REST, Python SDK) before or alongside Windows-specific tools like PowerShell.
- Reference Linux-compatible automation and scripting methods where possible, and clarify that all features are available cross-platform.
- Add a note or section confirming that all steps can be performed from Linux/macOS environments using supported tools.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-odata.md
...ocs/blob/main/articles/data-factory/connector-odata.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias. Windows authentication is listed as a primary authentication method, and the only OS-specific authentication example provided is for Windows (with domain\user syntax). There is no mention of Linux-specific authentication scenarios or examples, nor is there guidance for Linux users on how to obtain or use credentials. Additionally, the use of Windows-centric patterns (such as domain\user) and the absence of Linux command-line or tool references (e.g., curl, wget, or Linux-based token retrieval) reinforce this bias.
Recommendations
- Add explicit Linux authentication examples, such as using Kerberos or NTLM from Linux environments, or clarify cross-platform support for authentication types.
- Provide equivalent Linux command-line examples for obtaining access tokens (e.g., using curl or httpie instead of only referencing Postman).
- Clarify whether Windows authentication is supported from non-Windows integration runtimes, and if so, provide Linux-specific configuration guidance.
- When listing authentication types, avoid putting 'Windows' before more cross-platform options, or clarify their applicability to different OSes.
- Include a note or section on best practices for Linux users, especially for common scenarios like service principal authentication or API key usage.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing SQL Server Management Studio (SSMS) for running SQL scripts, without mentioning cross-platform or Linux alternatives. There are no examples or instructions for Linux or macOS users, and the only tool mentioned for database interaction is a Windows-only application. No PowerShell-specific examples are present, but the workflow assumes a Windows environment for key steps.
Recommendations
- Mention and provide instructions for cross-platform SQL tools such as Azure Data Studio, sqlcmd, or DataGrip, which are available on Linux and macOS as well as Windows.
- Include example commands for running the generated SQL scripts using sqlcmd or Azure Data Studio's integrated terminal, not just SSMS.
- Rephrase step 8 to say 'Open your preferred SQL client (such as SSMS, Azure Data Studio, or sqlcmd) to connect to your control table server...' instead of only referencing SSMS.
- Add a note or section for Linux/macOS users, outlining supported tools and any differences in workflow.
- Ensure screenshots and UI walkthroughs do not assume only Windows-based tools where possible.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-postgresql-legacy.md
...n/articles/data-factory/connector-postgresql-legacy.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias in its guidance for configuring SSL verification with the ODBC driver. It exclusively references Windows file paths (e.g., C:\Windows\ServiceProfiles...) and does not provide equivalent instructions or examples for Linux-based Self-hosted Integration Runtime (SHIR) servers. There are no Linux-specific examples or mentions of Linux file locations, and the only operating system-specific guidance is for Windows.
Recommendations
- Add equivalent instructions and file paths for configuring SSL certificates on Linux-based SHIR servers (e.g., ~/.postgresql/root.crt or /etc/ssl/certs/).
- Explicitly mention that the ODBC driver and SHIR can be run on both Windows and Linux, and provide OS-agnostic or dual-platform guidance where applicable.
- Include Linux-based examples or notes wherever Windows-specific paths, tools, or procedures are mentioned.
- Review all examples and configuration steps to ensure Linux users are not excluded or left to infer the correct steps for their environment.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing 'Command Prompt' as the context for running curl, omitting Linux/macOS terminal instructions, and recommending Fiddler (a Windows-only tool) for SSL troubleshooting. No Linux-specific tools or terminal environments are mentioned, and example commands are not adapted for cross-platform usage.
Recommendations
- When suggesting command-line tools like curl, refer to 'terminal' or 'command line' generically, and provide examples for both Windows (Command Prompt/PowerShell) and Linux/macOS (bash/zsh).
- Include Linux/macOS equivalents for troubleshooting tools, such as recommending Wireshark or mitmproxy alongside Fiddler.
- Explicitly state that curl is available on Linux/macOS by default, and provide any necessary installation instructions for Windows users.
- Ensure that all example commands are cross-platform or provide platform-specific variants where syntax differs.
- Avoid referencing only Windows environments (e.g., 'Command Prompt') unless the documentation is Windows-specific.