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 951-975 of 1000 flagged pages
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/credentials.md
...re-docs/blob/main/articles/data-factory/credentials.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation consistently references the Azure portal, PowerShell, and SDKs for managing credentials, but does not provide any explicit Linux or cross-platform CLI (e.g., Azure CLI) examples. PowerShell is mentioned as a scripting option, but there is no mention or example of using Bash, Azure CLI, or Linux-native tools. This creates a bias toward Windows-centric tools and workflows.
Recommendations
- Include Azure CLI (az) command examples for all credential management tasks, as Azure CLI is cross-platform and widely used on Linux.
- When listing scripting options, mention Azure CLI and Bash scripts alongside PowerShell and SDKs.
- Add screenshots or step-by-step instructions for performing tasks using Azure CLI in addition to the Azure portal and PowerShell.
- Explicitly state that all operations can be performed from Linux/macOS environments using Azure CLI, and provide links to relevant documentation.
- Ensure that REST API examples include curl or httpie commands, which are common on Linux.
Create Pull Request
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-factory-private-link.md
...ain/articles/data-factory/data-factory-private-link.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing only Windows-based virtual machine examples (specifically referencing 'Windows Server 2019 Datacenter - Gen1') for deploying the self-hosted integration runtime (IR). There are no instructions or examples for deploying the self-hosted IR on Linux-based virtual machines, nor are Linux images mentioned as options. The documentation also omits any Linux-specific configuration or troubleshooting guidance.
Recommendations
- Add parallel instructions and examples for deploying the self-hosted IR on supported Linux distributions, including recommended Linux VM images.
- Explicitly mention that the self-hosted IR can be installed on both Windows and Linux, if supported, and provide links to relevant installation guides for each OS.
- Include Linux-specific configuration steps, such as firewall rules, DNS setup, and package dependencies, where applicable.
- Ensure screenshots and UI walkthroughs are not Windows-centric, or provide Linux equivalents where the experience differs.
- Review all sections for implicit assumptions of a Windows environment and clarify cross-platform support where relevant.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-troubleshoot-dynamics-dataverse.md
...a-factory/connector-troubleshoot-dynamics-dataverse.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references the XrmToolBox, a Windows-only tool, as a troubleshooting step in multiple places. There are no Linux or cross-platform alternatives mentioned, nor are there command-line or PowerShell examples, but the exclusive mention of a Windows GUI tool introduces a Windows bias. No Linux-specific guidance or parity is provided.
Recommendations
- Where XrmToolBox is recommended, also mention cross-platform alternatives or clarify if none exist.
- If possible, provide equivalent troubleshooting steps using REST APIs, CLI tools, or scripts that are platform-agnostic.
- Explicitly state the platform requirements for XrmToolBox and suggest workarounds for Linux/macOS users, such as using Wine, or recommend alternative approaches.
- Consider including examples or links for troubleshooting Dynamics 365 connectivity and data issues using PowerShell (cross-platform), Azure CLI, or REST API calls.
- Audit the documentation for other implicit Windows dependencies and add Linux/macOS guidance where feasible.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-flow-expressions-usage.md
...n/articles/data-factory/data-flow-expressions-usage.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is generally platform-neutral, as it describes data flow functions in Azure Data Factory and Synapse Analytics, which are cloud-based and not OS-specific. However, there are a few instances where Windows-specific terminology or encodings are mentioned (e.g., 'Windows-1252' encoding in examples for fromBase64 and toBase64), and Windows time zones (e.g., 'PST') are listed before IANA/Olson equivalents. There are no PowerShell-heavy examples, nor are there Windows command-line tools or patterns. Linux-specific encodings, locales, or time zones are not mentioned, and Linux-first terminology is not used.
Recommendations
- When providing examples of character encodings (e.g., in fromBase64, toBase64), include both Windows-specific (e.g., 'Windows-1252') and common Linux/UNIX encodings (e.g., 'UTF-8', 'ISO-8859-1') to demonstrate parity.
- When listing time zones, prefer IANA/Olson time zone names (e.g., 'America/New_York', 'Europe/Berlin') and mention Windows time zone abbreviations only as secondary options.
- If referencing locale or encoding, clarify that the functions are not limited to Windows environments and work equally on Linux-based integration runtimes.
- Consider adding a note or example that demonstrates the use of these functions in a Linux context, especially where encoding or locale is relevant.
- Review all examples and terminology to ensure that neither Windows nor Linux is implicitly prioritized, and that documentation is inclusive of both environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/enable-customer-managed-key.md
...n/articles/data-factory/enable-customer-managed-key.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell and Azure CLI for enabling Key Vault properties but does not provide any command-line examples for either platform. The UI walkthroughs and screenshots are exclusively from the Azure Portal, which is platform-agnostic but often more familiar to Windows users. There are no Linux-specific instructions, shell commands, or mentions of Linux tooling. The ordering of PowerShell before Azure CLI in the prerequisites section also subtly prioritizes Windows tooling.
Recommendations
- Provide explicit command-line examples for both PowerShell (Windows) and Bash (Linux) when describing how to enable Key Vault properties such as Soft Delete and Do Not Purge.
- Include Azure CLI examples using Bash syntax, and clarify that Azure CLI is cross-platform.
- When listing options for configuration, alternate the order (e.g., mention Azure CLI before PowerShell in some sections) or present them in parallel to avoid implicit prioritization.
- Add a section or callout for Linux/macOS users, highlighting any differences or confirming that all steps are cross-platform.
- Where possible, include screenshots or terminal output from both Windows and Linux environments to reinforce parity.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/guidance-for-byod-approach.md
...in/articles/data-factory/guidance-for-byod-approach.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation assumes the use of Self-Hosted Integration Runtime (SHIR), which is only available for Windows, and provides no mention of Linux support or alternatives. There are no Linux-specific instructions, examples, or troubleshooting steps, and the guidance implicitly assumes a Windows environment for driver installation and runtime hosting.
Recommendations
- Explicitly state that SHIR is only supported on Windows, and if possible, provide guidance or links for Linux users (e.g., Azure IR or other alternatives).
- Add a section clarifying platform support and any workarounds for Linux environments.
- If Linux support is planned or available via other runtimes, include parallel instructions or examples for Linux.
- Mention any limitations or considerations for non-Windows users early in the documentation.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/sap-change-data-capture-debug-shir-logs.md
...ata-factory/sap-change-data-capture-debug-shir-logs.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively references the Microsoft Integration Runtime Configuration Manager, a Windows-only GUI tool, for sending logs. There are no instructions or examples for performing the same task on Linux systems, nor is there any mention of Linux command-line alternatives or parity.
Recommendations
- Provide equivalent instructions for Linux environments, such as using command-line tools or scripts to collect and send logs.
- Explicitly state platform requirements or limitations if the feature is only available on Windows, and suggest workarounds for Linux users.
- Include screenshots or examples for both Windows and Linux where applicable.
- Mention whether the self-hosted integration runtime supports Linux, and if so, document the log collection process for Linux deployments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/known-issues-troubleshoot-guide.md
...ticles/data-factory/known-issues-troubleshoot-guide.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation assumes the Self-hosted Integration Runtime (SHIR) is running on a machine where a user can open a browser and visit a website (whatismyipaddress.com) to determine the outbound IP. This is a Windows-centric approach, as SHIR is often run on Windows, and no Linux-specific instructions or command-line alternatives are provided. There are no Linux or cross-platform command-line examples for retrieving the IP address, and the workaround does not consider headless or Linux environments.
Recommendations
- Provide Linux-specific instructions for retrieving the outbound IP address, such as using curl or wget from the command line (e.g., curl ifconfig.me).
- Clarify whether SHIR is supported on Linux, and if so, include parity in troubleshooting steps and examples.
- Offer command-line alternatives for environments where a browser is not available, benefiting both Windows Server Core and Linux users.
- Review other workarounds and instructions to ensure they are not implicitly assuming a Windows GUI environment.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-use-sql-managed-instance-with-ir.md
...ata-factory/how-to-use-sql-managed-instance-with-ir.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by exclusively referencing Windows-centric tools and concepts such as SQL Server Management Studio (SSMS), SQL Server Agent jobs, and Windows Firewall. There are no examples or mentions of Linux-based tools, command-line utilities, or cross-platform alternatives for managing or deploying SSIS packages. Additionally, PowerShell is referenced as a method for configuring certain Azure features, with no mention of Bash, Azure CLI, or other Linux-native approaches.
Recommendations
- Include examples using Azure CLI and Bash scripts for provisioning and managing Azure-SSIS IR and related resources, alongside or instead of PowerShell.
- Mention cross-platform tools (such as Azure Data Studio) in addition to SSMS for managing SQL Managed Instance and SSISDB.
- Clarify that SSIS package deployment and management can be performed from non-Windows environments, if supported, and provide relevant instructions.
- When referencing firewall or network configuration, provide guidance for both Windows Firewall and Linux iptables/ufw where applicable.
- Explicitly state platform requirements and offer parity in instructions for both Windows and Linux users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/load-sap-bw-data.md
...cs/blob/main/articles/data-factory/load-sap-bw-data.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation assumes the use of the SAP .NET Connector 3.0, which is only available for Windows, and requires installation on the same machine as the self-hosted integration runtime. There are no instructions or examples for Linux environments, nor is there mention of alternatives for non-Windows users. All setup steps and screenshots implicitly target Windows users.
Recommendations
- Explicitly state that the SAP .NET Connector 3.0 and self-hosted integration runtime are Windows-only, and clarify platform requirements early in the prerequisites.
- If possible, provide guidance or alternatives for Linux environments, such as using the ODBC connector or other cross-platform integration runtimes.
- Include a section addressing what Linux or macOS users should do, or link to relevant documentation for non-Windows data integration scenarios.
- If no Linux support exists, clearly document this limitation to set user expectations.
- Consider adding a feature request or roadmap note if Linux support is planned for the future.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/solution-template-bulk-copy-with-control-table.md
...tory/solution-template-bulk-copy-with-control-table.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively providing SQL Server and Azure SQL Database examples for the control table, without mentioning or providing examples for Linux-based databases or environments. There are no examples or instructions for creating the control table in Oracle, Netezza, or Teradata, which are commonly run on Linux/UNIX systems. The workflow and screenshots also implicitly assume a Windows-centric environment.
Recommendations
- Add examples for creating the control table in Oracle, Netezza, and Teradata, including relevant SQL syntax and notes about platform-specific differences.
- Explicitly mention that the process applies to both Windows and Linux-based database systems, and provide guidance for users working in Linux environments.
- Include screenshots or instructions that are not specific to Windows tools or interfaces, or provide Linux/UNIX equivalents where applicable.
- Clarify any platform-specific prerequisites or steps, such as connection setup or authentication, for Linux-hosted databases.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/solution-template-migration-s3-azure.md
...s/data-factory/solution-template-migration-s3-azure.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation exclusively uses Azure SQL Database and T-SQL (SQL Server) for control tables and stored procedures, with no mention of Linux-friendly or cross-platform alternatives such as PostgreSQL, MySQL, or open-source database engines. All example code is in T-SQL, which is most commonly associated with Windows environments. There are no examples or guidance for users who may wish to use Linux-based databases or tools.
Recommendations
- Provide alternative examples using open-source databases such as PostgreSQL or MySQL, including equivalent table and stored procedure creation scripts.
- Clarify whether Azure Data Factory supports control tables and stored procedures in non-SQL Server databases, and provide guidance for those scenarios.
- Include a note or section on how to adapt the templates for users who do not use Azure SQL Database, especially those on Linux-based platforms.
- If possible, provide shell (bash) or cross-platform command-line examples for interacting with the control tables, not just T-SQL.
- Mention any limitations or requirements for using non-Windows, non-SQL Server environments with these templates.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/supported-file-formats-and-compression-codecs-legacy.md
...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/supported-file-formats-and-compression-codecs-legacy.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation shows mild Windows bias in its references to encoding names and Java runtime detection. Encoding examples reference Windows code pages (e.g., 'windows-1250'), and the process for locating Java on Self-hosted Integration Runtime checks the Windows registry first before using the cross-platform JAVA_HOME environment variable. There are no explicit Linux/POSIX shell or tool examples, and the documentation does not mention Linux-specific patterns or alternatives.
Recommendations
- When referencing encoding names, provide both Windows and common Linux/Unix encoding names (e.g., 'windows-1250' and 'ISO-8859-2').
- In instructions for Java runtime detection, clarify that JAVA_HOME is the standard on Linux/macOS and that the registry check is Windows-specific.
- Where file paths or environment variables are mentioned, show both Windows and Linux/macOS syntax (e.g., C:\path vs /path).
- If referencing external tools or APIs (such as .NET encoding names), note Linux/Unix equivalents or cross-platform considerations.
- Add examples or notes for Linux users where relevant, especially in sections discussing system configuration or environment variables.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/transform-data-using-data-lake-analytics.md
...ta-factory/transform-data-using-data-lake-analytics.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias, primarily through its use of Windows-style path separators (e.g., 'scripts\kona\SearchLogProcessing.txt') in JSON examples and U-SQL script references. There are no explicit Linux or cross-platform examples, and no mention of Linux/Unix path conventions. While the documentation does not reference Windows-specific tools or PowerShell, the implicit assumption of Windows paths may confuse or inconvenience Linux users.
Recommendations
- Provide examples using both Windows (\) and Linux (/) path separators, or use forward slashes (/) which are supported on both platforms in Azure Data Lake.
- Add a note clarifying that both path styles are supported, and recommend using forward slashes for cross-platform compatibility.
- Explicitly mention that the examples are platform-agnostic, or provide a section on cross-platform considerations.
- Review all code snippets and UI screenshots to ensure they do not reinforce a Windows-only workflow.
- If relevant, include CLI or scripting examples (such as Azure CLI or Bash) alongside any UI or JSON examples.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/transform-data-using-hadoop-streaming.md
.../data-factory/transform-data-using-hadoop-streaming.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation page provides only Windows-centric examples for Hadoop Streaming activities, specifically referencing '.exe' executables (e.g., 'MyMapper.exe', 'MyReducer.exe') in both the JSON sample and file paths. There are no examples or mentions of Linux/Unix-style scripts (e.g., Python, Bash, or shell scripts), which are more common in Hadoop Streaming scenarios. The documentation implicitly assumes Windows tools and omits Linux equivalents.
Recommendations
- Provide parallel examples using Linux/Unix-style scripts (e.g., 'MyMapper.py', 'MyReducer.sh') in the JSON sample and file paths.
- Explicitly mention that both Windows executables and Linux scripts are supported, and clarify any platform-specific considerations.
- Include a section or note on how to prepare and upload Linux-based mapper and reducer scripts to Azure Storage.
- Balance the documentation by showing both Windows and Linux usage patterns, especially in code and configuration samples.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/transform-data-using-stored-procedure.md
.../data-factory/transform-data-using-stored-procedure.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on SQL Server, Azure SQL Database, and Synapse Analytics, with instructions and examples tailored to these Microsoft-centric technologies. There is no mention of Linux-based SQL Server deployments, nor are there examples or guidance for using the Stored Procedure activity with open-source or non-Microsoft databases. Additionally, the prerequisite tutorial referenced is 'tutorial-transform-data-spark-powershell.md', which suggests a Windows/PowerShell-centric approach, with no alternative for Linux users.
Recommendations
- Include explicit mention and examples for using SQL Server on Linux, clarifying any differences in integration runtime setup or connectivity.
- Provide alternative tutorials or references for Linux users, such as using Bash or Azure CLI instead of PowerShell.
- Expand the scope to mention and, where possible, provide examples for invoking stored procedures in other supported databases (e.g., PostgreSQL, MySQL) if applicable.
- Ensure that references to tools, scripts, or runtimes are cross-platform, or provide platform-specific instructions where differences exist.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-control-flow-portal.md
.../articles/data-factory/tutorial-control-flow-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by referencing Windows-specific tools and workflows (such as Notepad) and omitting Linux/macOS equivalents. The instructions for creating files and interacting with Azure Storage do not provide cross-platform alternatives or mention command-line options suitable for Linux users. The tutorial assumes a GUI workflow and does not address Linux-native tools or scripting approaches.
Recommendations
- When instructing users to create a text file (e.g., input.txt), mention cross-platform editors such as nano, vim, or provide a generic instruction like 'use your preferred text editor' with examples for both Windows (Notepad) and Linux/macOS (nano, vim, etc.).
- For uploading files to Azure Blob Storage, in addition to Azure Storage Explorer (a GUI tool), provide CLI alternatives such as using the Azure CLI (az storage blob upload) or AzCopy, with example commands for both Windows and Linux/macOS.
- Avoid referencing only Windows-specific tools in step-by-step instructions. Where browser support is mentioned, clarify that the Azure Portal is accessible from supported browsers on any OS.
- Add a note or section on how to perform the same steps using command-line tools or scripts, which are often preferred by Linux users.
- Ensure that all screenshots and instructions are either OS-agnostic or, where necessary, provide parallel instructions for Linux/macOS environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-copy-data-portal-private.md
...cles/data-factory/tutorial-copy-data-portal-private.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by instructing users to use Notepad to create a text file, without mentioning cross-platform alternatives. No Linux- or macOS-specific instructions or examples are provided for file creation or tooling. All other steps are performed in the Azure Portal UI, which is cross-platform, but the initial file creation step assumes a Windows environment.
Recommendations
- When instructing users to create a text file, mention cross-platform editors (e.g., 'Use Notepad (Windows), TextEdit (macOS), or nano/vi (Linux) to create emp.txt').
- Explicitly state that the Azure Portal and Azure Storage Explorer are available on Windows, macOS, and Linux.
- Wherever local tools are referenced, provide alternatives or clarify that the instructions apply to all major operating systems.
- Consider including a note or section for Linux/macOS users to ensure parity and inclusivity.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-copy-data-tool.md
.../main/articles/data-factory/tutorial-copy-data-tool.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation shows subtle Windows bias by referencing Notepad as the default text editor for preparing the input file, without mentioning Linux or cross-platform alternatives. There are no explicit Linux or macOS instructions or examples for creating and uploading files, and no mention of common Linux tools or workflows. The rest of the tutorial is platform-neutral, focusing on the Azure portal UI.
Recommendations
- When instructing users to create a text file, mention cross-platform editors (e.g., 'use Notepad (Windows), TextEdit (macOS), or nano/vi (Linux)').
- Provide command-line examples for creating the input file using echo/cat (Linux/macOS) and PowerShell (Windows), so users on all platforms have clear guidance.
- When suggesting upload tools, mention cross-platform CLI tools like 'azcopy' or 'Azure CLI', and provide example commands for uploading the file from Linux/macOS terminals.
- Add a note clarifying that all steps can be performed from any OS using the Azure portal, and link to documentation for cross-platform Azure tools.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-deploy-ssis-virtual-network.md
...s/data-factory/tutorial-deploy-ssis-virtual-network.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation focuses exclusively on configuring Azure-SSIS IR using the Azure Portal and ADF UI, which are web-based and platform-agnostic, but does not provide any command-line examples or alternative approaches for Linux users. There is a reference to a separate PowerShell-based guide in the 'Related content', but no mention of Linux CLI tools (such as Azure CLI or Bash scripts), nor are any Linux-specific workflows or considerations discussed. All instructions and screenshots assume a GUI workflow, which is more common in Windows-centric documentation.
Recommendations
- Add equivalent instructions for configuring Azure-SSIS IR to join a virtual network using Azure CLI commands, which are cross-platform and commonly used on Linux.
- Include references to Bash scripting or automation for Linux users, in addition to the PowerShell guide already referenced.
- Explicitly state that the Azure Portal and ADF UI are accessible from any OS with a supported browser, and clarify any OS-specific requirements if they exist.
- Where possible, provide side-by-side examples for both PowerShell (Windows) and Azure CLI (Linux/macOS) in relevant sections.
- Mention and link to documentation on using Azure CLI for network and resource configuration, to ensure Linux users have clear guidance.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally cross-platform and references both Windows and Linux environments for HDInsight clusters and transformation activities. However, the only linked tutorial at the end is specifically for Spark transformation using PowerShell, which is Windows-centric. There is a slight tendency to mention Windows in cluster descriptions ("Windows/Linux-based HDInsight cluster") with Windows listed first. No Linux/macOS-specific examples or CLI alternatives are provided in the main page.
Recommendations
- Add tutorials or example links for transforming data using Bash, Azure CLI, or other cross-platform tools alongside PowerShell.
- When referencing environments, alternate or randomize the order of 'Windows/Linux' to avoid subtle prioritization.
- Ensure that for every PowerShell-based example or tutorial, a Linux/macOS-friendly alternative (e.g., Bash, Azure CLI, Python SDK) is provided or linked.
- Explicitly mention platform parity where applicable, reassuring users that all features are available on Linux/macOS unless otherwise noted.
Data Factory
Troubleshoot the FTP, SFTP, and HTTP connectors
...s/data-factory/connector-troubleshoot-ftp-sftp-http.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation exhibits mild Windows bias by referencing WinSCP (a popular Windows SFTP client) as a tool for credential validation, without mentioning Linux/macOS alternatives. Additionally, the link for HTTP status codes points to IIS documentation, which is Windows-centric, and Windows tools are mentioned before Linux equivalents in some troubleshooting steps. However, Linux commands (e.g., openssl, ssh-keygen) are provided for key conversion and fingerprinting, and code samples are cross-platform (C#, Python).
Recommendations
- Mention Linux/macOS SFTP clients (e.g., FileZilla, Cyberduck, command-line sftp) alongside WinSCP for credential validation.
- Provide links to platform-neutral HTTP status code documentation (e.g., MDN Web Docs) instead of IIS-specific resources.
- When referencing tools, present both Windows and Linux/macOS options, or use platform-neutral phrasing.
- Ensure troubleshooting steps and examples are presented in a cross-platform manner, with parity for Linux/macOS users.
Data Factory
Troubleshoot CI-CD, Azure DevOps, and GitHub issues
...ticles/data-factory/ci-cd-github-troubleshoot-guide.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias, primarily through references to PowerShell and Windows-centric tooling (e.g., Azure PowerShell, manual UI steps, and PowerShell API usage) without providing equivalent Linux/macOS CLI or automation examples. There is a lack of explicit Linux/macOS command-line instructions (such as Azure CLI or bash scripting), and PowerShell is mentioned as a method for certain tasks (e.g., changing integration runtime) without alternatives. No explicit Windows-first ordering is present, but Linux users may need to infer or adapt instructions.
Recommendations
- Provide Azure CLI and bash examples alongside PowerShell for tasks such as changing integration runtime and ARM template deployments.
- Explicitly mention cross-platform compatibility for SDKs and automation tools (e.g., .NET, Python, REST).
- Add notes or links for Linux/macOS users on how to perform equivalent actions (e.g., using Azure CLI, bash scripts, or platform-agnostic SDKs).
- Where PowerShell is referenced, clarify that Azure CLI or REST API can be used on any OS and provide sample commands.
- Ensure troubleshooting steps do not assume use of Windows-only tools or UI workflows.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely neutral regarding OS bias, with most examples and configuration details focusing on cloud-based services and JSON configuration. However, there are some instances of Windows bias: Windows tools such as Microsoft Azure Storage Explorer are mentioned for blob container management, and references to 'CMDLETs & APIS' (typically PowerShell terminology) are used when discussing VM sizes. Additionally, PowerShell cmdlets (New-AzBatchAccount, New-AzBatchPool) are mentioned before alternatives like the Azure portal for Azure Batch setup. No Linux-specific tools or CLI examples are provided, and Windows terminology appears first in some places.
Recommendations
- Include equivalent Linux/macOS CLI commands (e.g., Azure CLI) alongside or before PowerShell cmdlet references.
- Mention cross-platform tools for blob storage management (e.g., azcopy, Azure CLI, REST API) in addition to Microsoft Azure Storage Explorer.
- Clarify that 'CMDLETs & APIS' refers to both PowerShell and REST/CLI interfaces, and provide links to Linux/macOS-friendly documentation.
- Where Windows terminology appears first, alternate or balance with Linux-first examples, especially for SSH access and cluster management.
- Add explicit notes or examples for Linux/macOS users where relevant, such as using SSH for troubleshooting clusters.
Data Factory
Copy and transform data in Dynamics 365 (Microsoft Dataverse) or Dynamics CRM
...cles/data-factory/connector-dynamics-crm-office-365.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page displays a mild Windows bias, primarily through its reliance on Windows-centric terminology and tooling. The connector is described as being built on top of 'Dynamics XRM tooling', which is specifically for building Windows client applications. There is no mention of Linux or macOS compatibility or alternative tooling. Windows/Active Directory authentication patterns are referenced, and Windows-style domain/user patterns are used in examples. However, the actual configuration and usage examples are platform-neutral (JSON, Azure portal UI), and there are no explicit PowerShell or Windows-only command-line instructions.
Recommendations
- Explicitly state platform compatibility (Windows, Linux, macOS) for the connector and integration runtime.
- If the connector or XRM tooling is Windows-only, provide guidance or alternatives for Linux/macOS users.
- Include notes or examples for deploying and managing integration runtime on Linux/macOS, if supported.
- Clarify whether authentication patterns (Active Directory, domain, username) are supported or different on non-Windows platforms.
- Avoid referencing Windows-specific development tools unless necessary, and provide parity for other platforms.