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 676-700 of 1000 flagged pages
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/ssis-integration-runtime-ssis-activity-faq.md
...-factory/ssis-integration-runtime-ssis-activity-faq.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools, paths, and authentication patterns (e.g., SSMS, C:\ paths, NT AUTHORITY accounts, Visual C++ runtime), and by omitting Linux equivalents or cross-platform alternatives. There are no examples or troubleshooting steps for Linux-based environments, and all file path and log references use Windows conventions. The documentation assumes the use of Windows authentication and components, with no mention of Linux-compatible tools or deployment scenarios.
Recommendations
- Add troubleshooting steps and examples for Linux-based environments, including file paths, log locations, and authentication patterns.
- Reference cross-platform tools (e.g., Azure Data Studio) alongside or instead of Windows-only tools like SSMS.
- Provide both Windows and Linux file path examples and clarify when a step is OS-specific.
- Mention Linux-compatible prerequisites (e.g., Mono for SSIS, if supported) and clarify any platform limitations.
- Include guidance for setting up and troubleshooting SSIS integration runtime on Linux hosts, if supported, or explicitly state Windows-only support where applicable.
Create Pull Request
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/ssis-integration-runtime-management-troubleshoot.md
...ry/ssis-integration-runtime-management-troubleshoot.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing PowerShell cmdlets as a primary troubleshooting interface, mentioning Windows tools (e.g., SSMS) for diagnostics, and omitting Linux equivalents or cross-platform alternatives. All example troubleshooting steps and tool recommendations assume a Windows environment, with no mention of how to perform these tasks on Linux or macOS.
Recommendations
- Include Azure CLI examples alongside or instead of PowerShell cmdlets, as Azure CLI is cross-platform.
- Mention and provide steps for using cross-platform SQL management tools (e.g., Azure Data Studio) in addition to SSMS.
- When recommending testing scripts locally, clarify how to do so on both Windows (cmd, PowerShell) and Linux/macOS (bash, sh).
- Explicitly state whether SSIS IR management and troubleshooting can be performed from non-Windows environments, and provide guidance if so.
- Ensure that all tool and script references have Linux/macOS equivalents or note any limitations.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-deploy-ssis-packages-azure.md
...es/data-factory/tutorial-deploy-ssis-packages-azure.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation consistently references Windows-based tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and managing SSIS packages, with no mention of Linux alternatives or cross-platform options. All command-line and GUI examples assume a Windows environment, and PowerShell is referenced for firewall configuration without Bash/Azure CLI equivalents. There are no Linux-specific instructions or parity in tool recommendations.
Recommendations
- Include Azure CLI and Bash examples alongside PowerShell for tasks like configuring firewall rules.
- Explicitly state the platform requirements for tools like SSDT, SSMS, dtutil, and AzureDTExec, and mention if they are Windows-only.
- If Linux or cross-platform alternatives exist (e.g., Azure Data Studio, cross-platform Azure CLI), provide instructions or links.
- Clarify whether package deployment and management can be performed from non-Windows environments, and if not, note this limitation.
- Add a section or note addressing Linux/macOS users, outlining what is and isn't supported, and suggesting workarounds or alternatives where possible.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/transform-data-using-custom-activity.md
...s/data-factory/transform-data-using-custom-activity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a clear Windows bias. All command-line and scripting examples use PowerShell and Windows command patterns (e.g., 'cmd /c', '.exe' applications). There are no Linux/bash equivalents provided for creating or managing Azure Batch accounts, running pipelines, or specifying commands for custom activities. The documentation references Windows-native tools and patterns (such as .exe files and cmd commands) without mentioning or demonstrating Linux alternatives, and Windows approaches are always presented first or exclusively.
Recommendations
- Provide equivalent bash/CLI examples alongside PowerShell commands for managing Azure Batch and running pipelines.
- Include Linux-native command examples (e.g., using '/bin/bash -c' or shell scripts) in the 'command' property for custom activities.
- Demonstrate usage of Linux executables (e.g., .sh scripts, ELF binaries) in addition to .exe files.
- Clarify in the documentation that both Windows and Linux pool nodes are supported, and specify how to target each OS.
- Reference Azure CLI and REST API methods for account and pool management, not just PowerShell.
- Add a section or table comparing Windows and Linux usage patterns for custom activities.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/transform-data-using-script.md
...n/articles/data-factory/transform-data-using-script.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-specific tools and patterns (such as Self-hosted integration runtime installation instructions that implicitly assume a Windows environment), mentioning SQL Server (a Microsoft/Windows-centric database) with detailed setup instructions, and omitting explicit Linux or cross-platform examples or guidance. There are no examples or notes about running the Script activity against Linux-hosted databases, nor are there references to Linux-based integration runtime installation or usage.
Recommendations
- Add explicit instructions or notes for installing and running the Self-hosted integration runtime on Linux, including supported distributions and any differences in setup.
- Include examples or references for connecting to databases commonly hosted on Linux (e.g., PostgreSQL, MySQL) if supported, or clarify platform support.
- Balance the mention of SQL Server and Windows-centric databases with equivalent guidance for Linux-based environments and databases.
- When describing installation or configuration steps, provide both Windows and Linux command-line examples or links to relevant documentation.
- Explicitly state platform compatibility and any limitations for Script activity and integration runtime components.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-enable-remote-access-intranet-tls-ssl-certificate.md
...rial-enable-remote-access-intranet-tls-ssl-certificate.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows environments. All command-line examples use PowerShell, and certificate management instructions rely on Windows-specific tools (MMC snap-in, Windows certificate stores, and Windows service accounts). There are no examples or guidance for Linux systems, and all terminology and screenshots are Windows-centric.
Recommendations
- Provide equivalent Linux command-line examples (e.g., using openssl, hostname, or certbot for certificate generation and management).
- Include instructions for installing and trusting certificates on Linux (e.g., using update-ca-certificates or placing certs in /etc/ssl/certs).
- Mention Linux-compatible integration runtime options, if available, or clarify Windows-only support.
- Add screenshots or terminal output from Linux environments where applicable.
- Use cross-platform terminology where possible (e.g., 'machine' instead of 'Local Machine', 'certificate store' instead of 'Personal').
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/transform-data.md
...docs/blob/main/articles/data-factory/transform-data.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page is largely platform-neutral in its main content, but there are subtle signs of Windows bias. In the descriptions of HDInsight activities (Hive, Pig, MapReduce, Streaming), clusters are described as 'Windows/Linux-based', with Windows mentioned first. The 'Stored procedure activity' only references SQL Server and Azure SQL, which are Microsoft/Windows-centric technologies, without mentioning open-source or Linux-native alternatives. The custom activity section focuses on .NET, a technology historically associated with Windows, and does not provide examples for Linux-native languages or runtimes. The only tutorial linked is for Spark using PowerShell, a Windows-centric tool, with no Bash or Linux CLI equivalent provided.
Recommendations
- When describing HDInsight clusters, alternate the order of 'Windows/Linux-based' or simply state 'Linux or Windows-based' to avoid implicit prioritization.
- In the 'Stored procedure activity' section, mention support for other database engines (such as PostgreSQL or MySQL) if available, and provide examples for those platforms.
- For custom activities, include examples or references for running Python, Java, or other Linux-native workloads, not just .NET.
- Provide equivalent tutorials and code samples for Linux environments (e.g., Bash scripts, Azure CLI) alongside PowerShell examples.
- Where possible, clarify cross-platform support and highlight any differences or limitations for Linux users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-control-flow.md
...ob/main/articles/data-factory/tutorial-control-flow.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All code samples and project setup instructions are based on Visual Studio (Windows-only or Windows-first), and the .NET SDK is used exclusively. The prerequisite tools listed (Visual Studio, Azure Storage Explorer) are Windows-centric, and there are no examples or guidance for Linux or cross-platform development environments. No alternative instructions are provided for Linux users, such as using VS Code, the Azure CLI, or .NET Core on Linux/macOS.
Recommendations
- Provide equivalent instructions for Linux and macOS users, such as using VS Code or JetBrains Rider instead of Visual Studio, and .NET Core SDK instead of .NET Framework.
- Include command-line examples using Azure CLI or PowerShell Core (which is cross-platform), and show how to run the sample code on Linux/macOS.
- Mention cross-platform alternatives for Azure Storage Explorer, or clarify its availability on Linux/macOS.
- Add a section or callout at the start of the tutorial indicating that the steps can be performed on Linux/macOS, and provide links to relevant setup guides.
- Where possible, use .NET 6+ (or .NET Core) for code samples to ensure cross-platform compatibility.
- Explicitly state any Windows-only requirements, and suggest workarounds or alternatives for non-Windows users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-copy-data-portal.md
...ain/articles/data-factory/tutorial-copy-data-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a subtle Windows bias by referencing Windows-specific tools and workflows (e.g., Notepad for file creation), omitting Linux/macOS equivalents, and not providing cross-platform command-line alternatives. There are no explicit Linux or macOS instructions or examples, and the only tool mentioned for file editing is Notepad, which is Windows-specific. The documentation also references browser support but does not mention OS-specific browser nuances or alternatives for Linux users.
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 the emp.txt file').
- Provide command-line alternatives for file creation and upload, such as using 'echo' or 'cat' in a terminal, and include Azure CLI or azcopy commands for uploading files to Blob storage.
- Avoid assuming the user's operating system; use neutral language and mention steps for both Windows and Linux/macOS where relevant.
- If referencing tools like Azure Storage Explorer, clarify that it is cross-platform and provide download links for all supported OSes.
- Explicitly state that the tutorial is OS-agnostic except where the Azure portal UI is used, and provide tips for Linux/macOS users where workflows may differ.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-copy-data-dot-net.md
...in/articles/data-factory/tutorial-copy-data-dot-net.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias by exclusively using Visual Studio (a Windows-centric IDE), .NET SDK, and NuGet Package Manager Console (PowerShell-based) for all code and setup instructions. There are no examples or guidance for Linux or cross-platform development environments (e.g., VS Code, CLI, or Python SDK). All tooling and workflow steps assume a Windows environment, omitting Linux equivalents for project creation, package management, and database access/validation.
Recommendations
- Provide equivalent instructions for Linux users, such as using VS Code or JetBrains Rider for C# development, and include CLI-based project creation (dotnet CLI) instead of only Visual Studio.
- Show how to install required NuGet packages using the dotnet CLI (e.g., 'dotnet add package ...') rather than only the Package Manager Console.
- Mention and provide examples for using the Azure Data Factory Python SDK or REST API, which are cross-platform.
- Include instructions for connecting to Azure SQL Database using cross-platform tools like Azure Data Studio or sqlcmd, not just SQL Server Management Studio (SSMS) or Visual Studio.
- Add a note or section on how to run and debug the sample code on Linux or macOS, including any prerequisites or differences.
- Ensure all screenshots and UI references are either cross-platform or alternatives are provided for Linux/macOS users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-hybrid-copy-data-tool.md
...rticles/data-factory/tutorial-hybrid-copy-data-tool.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 Windows tools (SQL Server Management Studio, Notepad), omitting Linux alternatives or instructions, and implicitly assuming a Windows environment for the integration runtime installation. There are no examples or guidance for users on Linux or macOS platforms, and all setup steps and screenshots are tailored to Windows users.
Recommendations
- Include instructions for connecting to SQL Server from Linux/macOS using tools like Azure Data Studio or sqlcmd.
- Mention and provide steps for editing files using cross-platform editors (e.g., VS Code, nano) instead of only Notepad.
- Clarify whether the self-hosted integration runtime can be installed on Linux, and if so, provide installation steps for Linux (and macOS, if supported).
- Add notes or sections for Linux users wherever the process differs or additional steps are required.
- Ensure screenshots and UI references are not Windows-specific, or provide Linux/macOS equivalents where relevant.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-hybrid-copy-portal.md
...n/articles/data-factory/tutorial-hybrid-copy-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows tools (SQL Server Management Studio), using Windows-centric terminology (e.g., Notepad), and omitting any Linux-specific instructions or alternatives. There are no examples or guidance for users running SQL Server on Linux or for using Linux-based tools to accomplish the same tasks.
Recommendations
- Include instructions for connecting to SQL Server using cross-platform tools such as Azure Data Studio, which is available on Windows, macOS, and Linux.
- Provide alternative command-line examples for creating databases and tables using sqlcmd, which is available on Linux.
- Mention Linux-compatible text editors (e.g., nano, vim) alongside Notepad.
- Clarify that SQL Server can run on Linux and provide links or notes for Linux installation and management.
- Ensure that any screenshots or step-by-step instructions that are OS-specific are accompanied by Linux equivalents or notes.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-incremental-copy-change-data-capture-feature-portal.md
...al-incremental-copy-change-data-capture-feature-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows tools (SQL Server Management Studio) for database operations, omitting any mention of Linux-compatible alternatives. All instructions for interacting with the database assume the use of SSMS, and there are no examples or guidance for users on Linux or macOS platforms. No PowerShell-specific commands are present, but the overall workflow and tooling references are Windows-centric.
Recommendations
- Include instructions for connecting to Azure SQL Managed Instance using cross-platform tools such as Azure Data Studio, sqlcmd, or DataGrip, alongside or instead of SQL Server Management Studio.
- Provide command-line examples (e.g., using sqlcmd) for creating tables, enabling CDC, and modifying data, so Linux and macOS users can follow along without SSMS.
- Explicitly mention that the steps can be performed from any OS, and list the supported tools for each platform.
- Where screenshots are shown for SSMS, consider adding equivalent screenshots or terminal outputs for cross-platform tools.
- Add a section or note at the beginning of the tutorial clarifying that all database operations can be performed from Linux, macOS, or Windows, and provide tool recommendations for each.
Data Factory
Copy data from Amazon RDS for SQL Server
...es/data-factory/connector-amazon-rds-for-sql-server.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page provides several examples and troubleshooting steps that are Windows-centric, such as instructions for using SQL Server Management Studio, SQL Server Configuration Manager, and Windows Firewall. These tools and configuration patterns are specific to Windows environments and are mentioned exclusively, with no Linux or cross-platform alternatives provided. Windows authentication is described and exampled before SQL authentication, and all troubleshooting steps assume a Windows-based SQL Server instance.
Recommendations
- Add troubleshooting steps for Amazon RDS for SQL Server instances managed from Linux/macOS, such as using sqlcmd or other cross-platform tools.
- Include instructions for configuring remote access and TCP/IP on Amazon RDS for SQL Server via AWS Console or CLI, which is platform-agnostic.
- Provide guidance for managing firewall rules on Linux (e.g., using iptables or firewalld) if self-hosted integration runtime is on Linux.
- Clarify that SQL authentication is platform-neutral and may be preferable for cross-platform scenarios.
- Where possible, reference cross-platform management tools (e.g., Azure Data Studio, sqlcmd) alongside Windows-only tools.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation page for Azure Data Factory source control is generally cross-platform and focuses on Git integration via Azure Repos and GitHub, both of which are platform-agnostic. However, there are several mentions of using PowerShell and the SDK for publishing changes directly to the Data Factory service, with no equivalent Linux/macOS CLI examples or references to Azure CLI. This may create friction for non-Windows users who do not use PowerShell.
Recommendations
- Where PowerShell is mentioned for interacting with Data Factory (e.g., publishing changes, updating repoConfiguration), add equivalent Azure CLI or REST API examples and links.
- Explicitly state that PowerShell is not required and provide guidance for Linux/macOS users on how to perform these actions using platform-agnostic tools.
- Add a short section or note on cross-platform tooling for Data Factory automation, highlighting Azure CLI and REST API usage.
Data Factory
Copy data to and from Azure Table storage
...articles/data-factory/connector-azure-table-storage.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides a PowerShell-only example for generating a Shared Access Signature (SAS) token for Azure Table Storage, with no equivalent example for Linux/macOS users (such as Azure CLI or REST API). This creates friction for non-Windows users, as PowerShell is not natively available on Linux/macOS and the documentation does not mention alternative methods or tools.
Recommendations
- Add equivalent Azure CLI commands for generating SAS tokens, which work cross-platform.
- Mention REST API methods for SAS generation, with example requests.
- Explicitly note that PowerShell is Windows-centric and provide links or instructions for Linux/macOS alternatives.
- Ensure that all critical steps (such as authentication and token generation) have platform-neutral or cross-platform instructions/examples.
Data Factory
Troubleshoot the Azure Blob Storage connector
...a-factory/connector-troubleshoot-azure-blob-storage.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation references Windows-specific tools and configuration (diawp.exe.config, FIPS policy on Windows VM) without mentioning Linux/macOS equivalents or guidance. No Linux/macOS troubleshooting steps or examples are provided, which may leave non-Windows users without clear instructions for resolving similar issues.
Recommendations
- Add troubleshooting steps for Linux/macOS environments, especially for self-hosted integration runtime scenarios.
- Clarify whether FIPS-related issues apply to Linux/macOS and provide configuration guidance for those platforms if relevant.
- Include examples or notes for Linux/macOS users where Windows-specific tools (e.g., diawp.exe.config) are mentioned.
- Explicitly state platform limitations or differences if certain errors or resolutions are Windows-only.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only PowerShell scripts for programmatically finding impacted objects, with no mention of Linux/macOS alternatives (such as Azure CLI, Bash, or REST API). This creates friction for users on non-Windows platforms who may not have access to PowerShell or prefer native tools.
Recommendations
- Add equivalent examples using Azure CLI, Bash, or REST API for Linux/macOS users.
- Explicitly mention cross-platform options and clarify PowerShell Core compatibility if relevant.
- Provide guidance or links for running PowerShell scripts on Linux/macOS, if PowerShell is required.
- List Linux/macOS alternatives alongside or before Windows/PowerShell examples to ensure parity.
Data Factory
Switch activity in Azure Data Factory
.../articles/data-factory/control-flow-switch-activity.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively providing PowerShell command examples, referencing Windows file paths (C:\ADF), and linking to a PowerShell-focused tutorial. There are no CLI, Bash, or cross-platform instructions, nor are Linux/macOS equivalents or considerations mentioned. This creates friction for users on non-Windows platforms who wish to automate or script Data Factory deployments.
Recommendations
- Add Azure CLI examples for all PowerShell commands shown, with equivalent JSON file usage.
- Include Bash shell scripting examples for pipeline deployment and monitoring.
- Use cross-platform file path conventions (e.g., /home/user/ADF or ./ADF) in examples, or clarify that file paths are platform-dependent.
- Reference tutorials for Azure CLI and REST API approaches alongside PowerShell.
- Explicitly state platform requirements and alternatives for Linux/macOS users.
Data Factory
Continuous integration and delivery
...ticles/data-factory/continuous-integration-delivery.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias in its CI/CD best practices section, where PowerShell scripts are recommended and referenced exclusively for pre- and post-deployment tasks. There is no mention of Bash, shell, or cross-platform alternatives, nor are Linux/macOS usage patterns or examples provided. The guidance assumes users will use PowerShell Core, but does not clarify how Linux/macOS users should adapt or run these scripts, nor does it provide equivalent Bash scripts or instructions.
Recommendations
- Provide Bash or shell script equivalents for pre- and post-deployment tasks, or clarify how PowerShell Core scripts can be run on Linux/macOS environments.
- Explicitly mention cross-platform compatibility for scripts and tools, including installation and usage notes for Linux/macOS.
- Include Linux/macOS examples alongside Windows/PowerShell examples, especially in critical automation sections.
- Reference platform-agnostic tools (e.g., Azure CLI) where possible, or provide parity in documentation for both Windows and Linux/macOS users.
Data Factory
Migrate data from Amazon S3 to Azure Storage
...ta-factory/data-migration-guidance-s3-azure-storage.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in its guidance for deploying self-hosted Integration Runtime (IR) on Azure VMs. It explicitly instructs users to install IR on Windows VMs and provides configuration recommendations only for Windows environments, without mentioning Linux support or providing Linux-specific instructions. There are no examples or references for deploying IR on Linux VMs, nor is there any discussion of cross-platform considerations.
Recommendations
- Clarify whether self-hosted Integration Runtime supports Linux VMs. If supported, provide equivalent instructions and configuration recommendations for Linux deployments.
- Include examples or guidance for deploying and managing IR on Linux, such as installation steps, monitoring, and scaling.
- If IR is Windows-only, explicitly state this limitation and suggest alternative approaches for Linux users where possible.
- Ensure that any tooling or scripts referenced (e.g., for monitoring or automation) are available for both Windows and Linux, or provide platform-specific alternatives.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias primarily by referencing PowerShell as the main method for programmatically interacting with Data Flow Script outside the UI. Windows-centric tooling (PowerShell cmdlet) is mentioned exclusively, with no mention of Linux/macOS alternatives (such as Bash, Azure CLI, or REST API usage). The only example of external script usage is via PowerShell, and Windows tooling is referenced before any cross-platform or Linux-native options.
Recommendations
- Add examples for generating and submitting Data Flow Script using Azure CLI and REST API, which are cross-platform.
- Explicitly mention that PowerShell is just one option, and provide equivalent instructions for Linux/macOS users.
- Include Bash or shell script examples for formatting and submitting scripts.
- Clarify that the Data Flow Script can be used with any API client, not just PowerShell.
- Reorder sections so that cross-platform options are presented before or alongside Windows-specific tools.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only PowerShell commands for resource cleanup, which are primarily used on Windows. There are no examples for Linux/macOS users, such as Azure CLI or Bash equivalents. This creates friction for non-Windows users who may not have access to PowerShell or prefer native Linux tools.
Recommendations
- Add equivalent Azure CLI commands for deleting resource groups and data factories.
- Include Bash shell examples for Linux/macOS users.
- Mention cross-platform options and clarify which commands work on which operating systems.
- Consider presenting Azure CLI examples first, as it is available on all platforms.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns, such as Notepad and the C:\ADFv2QuickStartPSH folder, without providing equivalent instructions or examples for Linux or macOS users. There are no mentions of Linux/macOS text editors or file paths, and the instructions implicitly assume a Windows environment.
Recommendations
- Include instructions for creating the emp.txt file using Linux/macOS text editors (e.g., nano, vim, TextEdit).
- Provide example file paths for Linux/macOS (e.g., /home/user/ADFv2QuickStart).
- Clarify that the steps are applicable across platforms and offer platform-specific guidance where relevant.
- Avoid referencing Windows-only tools (like Notepad) without alternatives.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-v2-connector-get-started.md
...tory/includes/data-factory-v2-connector-get-started.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation lists Azure PowerShell as a primary tool for performing copy activities, which is most commonly associated with Windows environments. There is no explicit mention of Linux/macOS command-line tools (such as Azure CLI), and the order of tools places Windows-centric options (PowerShell, .NET SDK) before more cross-platform alternatives. No Linux-specific examples or tools are highlighted.
Recommendations
- Add Azure CLI as a recommended tool for copy activities, with a link to relevant quickstart documentation.
- Ensure examples and tool lists include Linux/macOS-compatible options and mention their usage explicitly.
- Reorder the list to alternate or prioritize cross-platform tools (e.g., Python SDK, REST API, Azure CLI) before Windows-centric options.
- Include notes or examples for Linux/macOS users where appropriate.