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 876-900 of 1000 flagged pages
Data Factory Troubleshoot the Dynamics 365, Dataverse (Common Data Service), and Dynamics CRM connectors ...a-factory/connector-troubleshoot-dynamics-dataverse.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references Windows-specific tools such as XrmToolBox multiple times for troubleshooting and testing, but does not mention Linux alternatives or provide guidance for users on non-Windows platforms. There are no examples or instructions tailored for Linux or cross-platform users, which may hinder troubleshooting for those not using Windows.
Recommendations
  • Include cross-platform or Linux-compatible tools for troubleshooting Dynamics connectors, or clarify if XrmToolBox can be used on Linux (e.g., via Mono or Wine).
  • Provide troubleshooting steps and examples that are platform-agnostic, or explicitly mention how Linux/macOS users can perform equivalent tasks.
  • Add notes or links to community-supported Linux tools or scripts for interacting with Dynamics 365, Dataverse, and CRM connectors.
  • Ensure that any references to third-party tools (like XrmToolBox) include installation and usage instructions for non-Windows environments if possible.
GitHub Create Pull Request
Data Factory Copy activity ...b/main/articles/data-factory/copy-activity-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for Azure Data Factory & Synapse Copy activity does not show explicit Windows bias in terms of PowerShell-heavy examples or exclusive mention of Windows tools. However, it demonstrates 'windows_first' bias by listing SQL Server (a Windows-centric technology) as the primary example in several places, and by referencing a tutorial that uses PowerShell for hybrid copy scenarios without mentioning Linux CLI or Bash alternatives. There are no Linux-specific examples, tools, or patterns provided, and Linux equivalents (such as Bash scripting, az CLI, or Linux file systems) are not discussed or linked.
Recommendations
  • Add Linux/Bash/az CLI examples for common Copy activity scenarios, especially for hybrid and on-premises data movement.
  • Include references to Linux file systems (e.g., ext4, NFS) in examples and connector documentation, not just generic 'file system'.
  • Provide parity in tutorials: for every PowerShell/Windows-centric tutorial, offer a Linux/Bash/CLI version.
  • Mention and link to Linux-compatible tools and patterns (e.g., azcopy, shell scripts) where relevant.
  • Explicitly state cross-platform compatibility and provide guidance for both Windows and Linux users in setup and troubleshooting sections.
GitHub Create Pull Request
Data Factory Copy or clone a data factory in Azure Data Factory .../main/articles/data-factory/copy-clone-data-factory.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references a PowerShell-based pattern for sharing SelfHosted Integration Runtime, and links to a PowerShell-specific guide. There are no Linux or cross-platform CLI examples provided, nor are alternative tools (such as Azure CLI or REST API) mentioned for cloning or sharing resources. The documentation implicitly assumes use of Windows-centric tools and workflows.
Recommendations
  • Include examples using Azure CLI and REST API for cloning and sharing SelfHosted Integration Runtime, alongside PowerShell.
  • Explicitly mention that PowerShell is available cross-platform, but also provide bash/Linux shell equivalents where possible.
  • Reference documentation or guides for performing these tasks on Linux/macOS systems.
  • Add notes or links to platform-agnostic tooling and clarify that the process is not limited to Windows environments.
GitHub Create Pull Request
Data Factory Azure Private Link for Azure Data Factory ...ain/articles/data-factory/data-factory-private-link.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing explicit instructions for creating a Windows Server virtual machine to host the self-hosted integration runtime (IR), without mentioning Linux as an alternative platform. The VM creation steps and image selection are Windows-centric, and there are no examples or guidance for deploying the self-hosted IR on Linux. This may lead users to assume that only Windows is supported or recommended, despite the fact that Data Factory self-hosted IR can run on Linux (with .NET Core).
Recommendations
  • Add parallel instructions for creating a Linux virtual machine (e.g., Ubuntu) in the Azure portal, including image selection and basic configuration.
  • Include guidance or links for installing and running the self-hosted IR on Linux, referencing official documentation or prerequisites (such as .NET Core).
  • Clarify in the VM creation section that both Windows and Linux are supported platforms for self-hosted IR, and provide a comparison or decision guidance.
  • Ensure that any firewall, DNS, or networking configuration steps are platform-agnostic or include notes for both Windows and Linux environments.
GitHub Create Pull Request
Data Factory Deploy linked ARM templates with Azure DevOps Services .../data-factory/deploy-linked-arm-templates-with-vsts.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal for all resource creation and management steps, without mentioning or providing examples for equivalent operations using cross-platform tools like Azure CLI or Azure PowerShell. There are no Linux-specific instructions or command-line alternatives, and all screenshots and workflow descriptions assume GUI usage typical of Windows environments.
Recommendations
  • Add step-by-step instructions using Azure CLI for all resource creation and management tasks, alongside the Azure portal steps.
  • Include PowerShell and Bash script examples for deploying ARM templates and managing Azure resources.
  • Provide screenshots or terminal output examples for Linux/macOS environments where applicable.
  • Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and link to cross-platform tool documentation.
  • Ensure that references to Azure DevOps features clarify their accessibility from any OS, not just Windows.
GitHub Create Pull Request
Data Factory Encrypt Azure Data Factory with customer-managed key ...n/articles/data-factory/enable-customer-managed-key.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by referencing PowerShell and Azure CLI as the only command-line options for configuring Key Vault properties, without providing explicit Linux shell or cross-platform CLI examples. The UI instructions and screenshots are all based on the Azure Portal, which is platform-agnostic, but there are no examples or guidance for Linux users (e.g., Bash, Cloud Shell, or cross-platform scripting). No Linux-specific tools or commands are mentioned, and PowerShell is listed before Azure CLI, reinforcing a Windows-centric approach.
Recommendations
  • Provide explicit Bash/Azure CLI examples for all command-line steps, ensuring parity with PowerShell instructions.
  • When mentioning PowerShell, always mention Azure CLI and Bash equivalents, and consider listing Azure CLI first as it is cross-platform.
  • Include Linux shell (Bash) command examples for enabling Key Vault properties and managing permissions.
  • Clarify that Azure CLI commands can be run from any OS, including Linux, macOS, and Windows.
  • Add a note or section for Linux/macOS users, highlighting any differences or additional steps required.
  • Ensure screenshots and UI instructions are clearly marked as platform-agnostic, and provide CLI alternatives where possible.
GitHub Create Pull Request
Data Factory Quickstart: Create an Azure Data Factory using Python .../data-factory/quickstart-create-data-factory-python.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific tools and workflows before Linux alternatives. For example, it instructs users to 'Launch Notepad' to create a text file and refers to 'terminal or command prompt with administrator privileges' without clarifying Linux equivalents. The use of Azure Storage Explorer is mentioned, which is cross-platform, but no Linux-native alternatives or command-line options (such as azcopy or Azure CLI) are provided for file upload. No explicit Linux shell commands or editor suggestions (like nano, vim, or touch) are included, and there are no screenshots or instructions tailored for Linux users.
Recommendations
  • When instructing users to create a text file, mention Linux editors (e.g., nano, vim, gedit) and provide equivalent commands (e.g., 'echo ... > input.txt').
  • Clarify that 'terminal or command prompt' refers to Command Prompt/PowerShell on Windows and Terminal/bash/zsh on Linux/macOS.
  • For uploading files to Azure Blob Storage, provide CLI alternatives such as 'azcopy' or 'az storage blob upload' commands, which work on all platforms.
  • Explicitly state that Azure Storage Explorer is available for Linux and macOS, or suggest platform-specific alternatives.
  • Include notes or examples for Linux users throughout the quickstart to ensure parity and inclusivity.
GitHub Create Pull Request
Data Factory Transform data using Hadoop Streaming activity .../data-factory/transform-data-using-hadoop-streaming.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively using Windows-style executable names (e.g., MyMapper.exe, MyReducer.exe) in its JSON sample and file paths, without providing equivalent Linux examples (such as Python or shell scripts). There is no mention of Linux tools or script formats, and the only example given implies the use of Windows executables, which may not be typical for Hadoop Streaming jobs on Linux-based clusters.
Recommendations
  • Provide Linux-oriented examples alongside Windows ones, such as using Python (.py), shell (.sh), or other script files as mappers and reducers.
  • Clarify that Hadoop Streaming supports both Windows and Linux executables/scripts, and indicate any platform-specific considerations.
  • Update the JSON sample to show both Windows (.exe) and Linux (.py/.sh) file types for mapper, reducer, and combiner.
  • Add a note or section explaining how to prepare and upload Linux-compatible scripts for use in HDInsight Streaming activities.
  • Ensure that documentation does not imply Windows executables are required or preferred, and present Linux options equally.
GitHub Create Pull Request
Data Factory Transform data by using the Stored Procedure activity .../data-factory/transform-data-using-stored-procedure.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing SQL Server (traditionally a Windows-centric database) and providing instructions that implicitly assume a Windows environment (e.g., installing Self-hosted integration runtime on the same machine as SQL Server, which is most commonly Windows). There are no explicit Linux or cross-platform examples, nor is there mention of running SQL Server on Linux or using Linux-based tools for integration runtime. The tutorial referenced is 'transform data-spark-powershell', which further suggests a Windows/PowerShell-first approach, with no mention of Bash or Linux alternatives.
Recommendations
  • Include explicit instructions or examples for deploying Self-hosted integration runtime on Linux machines, especially since SQL Server is supported on Linux.
  • Reference SQL Server on Linux as a supported scenario, and provide guidance for connecting to SQL Server instances running on Linux.
  • Add Linux/Bash-based examples or tutorials alongside PowerShell, especially in introductory or tutorial links.
  • Clarify that the integration runtime and stored procedure activity are cross-platform, and provide troubleshooting or setup notes for both Windows and Linux environments.
  • Avoid assuming the reader is using Windows by default; mention both OSes when discussing installation or configuration steps.
GitHub Create Pull Request
Data Factory Tutorial to configure Azure-SSIS integration runtime to join a virtual network ...s/data-factory/tutorial-deploy-ssis-virtual-network.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal and ADF UI, which are primarily accessed via Microsoft Edge or Google Chrome on Windows. There are no examples or instructions for Linux users, such as using Azure CLI or Bash scripts. The related content mentions Azure PowerShell but does not provide parity with Linux-native tools or workflows.
Recommendations
  • Add step-by-step instructions using Azure CLI for configuring and joining Azure-SSIS IR to a virtual network, suitable for Linux and macOS users.
  • Include Bash script examples for automating the setup process.
  • Explicitly mention cross-platform compatibility for browser-based steps and clarify any OS-specific requirements.
  • Provide links to Linux-specific documentation or troubleshooting guides.
  • Ensure that any PowerShell instructions are accompanied by equivalent Azure CLI or REST API examples.
GitHub Create Pull Request
Data Factory Configure a virtual network for injection of Azure-SSIS integration runtime ...ssis-integration-runtime-virtual-network-configuration.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows environments by exclusively referencing the Azure portal UI and linking to PowerShell-based instructions, with no mention of Linux-native tools (such as Azure CLI or Bash scripting) or examples. All step-by-step instructions assume a graphical interface typical of Windows users, and related content prioritizes PowerShell over cross-platform alternatives.
Recommendations
  • Add equivalent instructions using Azure CLI, which is cross-platform and widely used on Linux.
  • Include Bash script examples for automation of network configuration tasks.
  • Explicitly mention that all steps can be performed from Linux/macOS using CLI tools, not just the Azure portal or PowerShell.
  • Provide links to documentation for joining Azure-SSIS IR to a virtual network using Azure CLI.
  • Ensure that references to PowerShell are balanced with references to CLI, and avoid listing Windows-specific tools first in related content.
GitHub Create Pull Request
Data Factory Tutorial to configure Azure-SSIS integration runtime to join a virtual network ...s/data-factory/tutorial-deploy-ssis-virtual-network.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on configuration steps via the Azure portal and ADF UI, which are web-based and platform-agnostic. However, there is a subtle Windows bias: the only command-line alternative mentioned in 'Related content' is Azure PowerShell, which is primarily a Windows tool. There are no references to Linux-native tools (such as Azure CLI) or examples for Linux users. Additionally, browser recommendations (Edge, Chrome) are neutral, but the absence of Linux-specific guidance or parity in command-line examples suggests a Windows-first approach.
Recommendations
  • Add instructions or links for performing the same configuration using Azure CLI, which is cross-platform and widely used on Linux.
  • Explicitly mention that the Azure portal and ADF UI are accessible from Linux systems and provide any caveats if applicable.
  • Include examples or references for Linux users, such as shell scripts or CLI commands, alongside PowerShell alternatives.
  • Review related articles to ensure Linux parity in tooling and examples, not just PowerShell.
GitHub Create Pull Request
Data Factory Copy and transform data in Azure SQL Managed Instance ...s/data-factory/connector-azure-sql-managed-instance.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through exclusive references to SQL Server Management Studio (SSMS) for administrative tasks such as creating logins and users, with no mention of Linux-compatible alternatives (e.g., Azure Data Studio, sqlcmd, or cross-platform CLI tools). There are no PowerShell examples, but the lack of Linux or CLI examples for database administration and connection setup means Linux users may find it harder to follow or replicate the steps.
Recommendations
  • Add instructions and examples using cross-platform tools such as Azure Data Studio, sqlcmd, or Azure CLI for administrative tasks (creating logins, users, etc.), alongside SSMS.
  • Explicitly mention that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
  • Provide sample commands for Linux environments (e.g., using sqlcmd or Azure CLI) wherever T-SQL or connection setup is required.
  • Include screenshots or walkthroughs for Azure Data Studio or web-based Azure Portal, not just SSMS.
  • Ensure all examples and prerequisites are platform-neutral or offer both Windows and Linux/macOS options.
GitHub Create Pull Request
Data Factory Copy and transform data from and to a REST endpoint ...docs/blob/main/articles/data-factory/connector-rest.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page exhibits mild Windows bias. In the 'TIP' section for testing REST requests, Windows-centric tools such as Visual Studio and PowerShell's Invoke-RestMethod are mentioned explicitly and before any cross-platform or Linux-native alternatives. No Linux-specific tools (e.g., curl, wget, httpie) are referenced, nor are examples provided for them. The rest of the documentation is platform-neutral, focusing on Azure Data Factory UI and JSON configuration, but the initial guidance for testing REST APIs assumes a Windows environment.
Recommendations
  • Mention cross-platform and Linux-native tools for testing REST APIs, such as curl, wget, or httpie, alongside or before Windows tools.
  • Provide example commands for curl or httpie to demonstrate REST API testing in addition to PowerShell examples.
  • Clarify that the REST connector and related features are usable from any OS, and avoid implying Windows is required for preparatory steps.
  • Where Visual Studio is mentioned, add alternatives such as VS Code (which is cross-platform) or other editors available on Linux.
GitHub Create Pull Request
Data Factory Troubleshoot the Dynamics 365, Dataverse (Common Data Service), and Dynamics CRM connectors ...a-factory/connector-troubleshoot-dynamics-dataverse.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively recommending XrmToolBox, a Windows-only tool, for troubleshooting and testing FetchXML queries and record counts. There are no Linux or cross-platform alternatives mentioned, nor are there command-line or script-based examples suitable for Linux environments.
Recommendations
  • Include Linux-compatible alternatives to XrmToolBox, such as open-source CLI tools (e.g., PowerShell Core scripts that run on Linux, or Python-based tools for Dynamics 365).
  • Provide examples using REST API calls or SDKs that can be executed on any platform, not just Windows.
  • Explicitly mention platform compatibility for recommended tools and suggest cross-platform options where available.
  • Add troubleshooting steps that can be performed using generic tools (e.g., curl, Postman, or other HTTP clients) available on Linux.
GitHub Create Pull Request
Data Factory Copy activity ...b/main/articles/data-factory/copy-activity-overview.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page does not provide explicit Windows or PowerShell-heavy examples, nor does it mention Windows-specific tools or patterns. However, there is subtle Windows bias in the order and selection of examples and tutorials: SQL Server (a predominantly Windows technology) is referenced before Linux-oriented equivalents, and the only hybrid/on-premises tutorial provided is PowerShell-based, which is more common on Windows. There are no Linux shell or command-line examples, nor references to Linux-specific tools or workflows for hybrid scenarios.
Recommendations
  • Add Linux-based examples for hybrid/on-premises scenarios, such as using Bash scripts or Linux integration runtime setup.
  • Include tutorials or quickstarts that demonstrate copying data from Linux file systems or using Linux-native tools.
  • Balance the order of examples and tutorials to include both Windows and Linux scenarios, avoiding implicit prioritization of Windows technologies.
  • Explicitly mention cross-platform capabilities and provide guidance for both Windows and Linux users when discussing integration runtime setup and management.
GitHub Create Pull Request
Data Factory Copy or clone a data factory in Azure Data Factory .../main/articles/data-factory/copy-clone-data-factory.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references a Powershell-based pattern for sharing SelfHosted Integration Runtime, and links to a Powershell-specific guide. There are no examples or mentions of Linux or cross-platform alternatives (such as Azure CLI, Bash, or REST API) for cloning or managing Data Factory resources. The documentation assumes use of the Azure Portal and Powershell, which are more commonly used on Windows, and does not provide parity for Linux users.
Recommendations
  • Include examples using Azure CLI and REST API for cloning and deploying Data Factory resources, alongside Powershell.
  • Reference or create equivalent guides for sharing SelfHosted Integration Runtime using Azure CLI or REST API.
  • Explicitly mention cross-platform compatibility and provide instructions for Linux/macOS users where applicable.
  • Ensure that all automation steps (such as exporting and deploying ARM templates) have both Powershell and CLI/Bash examples.
GitHub Create Pull Request
Data Factory Azure Private Link for Azure Data Factory ...ain/articles/data-factory/data-factory-private-link.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by providing explicit instructions and examples for creating a Windows Server virtual machine to host the self-hosted integration runtime (IR), without mentioning or providing equivalent steps for Linux-based VMs. The only operating system referenced for the IR host is Windows, and there are no Linux-specific instructions, examples, or considerations. This may lead users to believe that only Windows is supported or recommended, even though Data Factory self-hosted IR can run on Linux (with .NET Core).
Recommendations
  • Add instructions and examples for creating a Linux-based VM (e.g., Ubuntu) to host the self-hosted IR, including image selection and any required configuration.
  • Explicitly state OS requirements and support for self-hosted IR, clarifying that both Windows and Linux are supported.
  • Provide parity in step-by-step guides for both Windows and Linux environments, including firewall/NSG configuration and IR installation.
  • Include notes or links to Linux-specific troubleshooting and best practices.
  • Where relevant, mention cross-platform tools and commands, not just Windows-centric options.
GitHub Create Pull Request
Data Factory Deploy linked ARM templates with Azure DevOps Services .../data-factory/deploy-linked-arm-templates-with-vsts.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal for all resource creation and management steps, without mentioning or providing examples for Linux-friendly tools like Azure CLI or ARM template deployment via bash scripts. There are no PowerShell-specific commands, but the workflow assumes GUI-based, Windows-centric patterns and omits Linux command-line alternatives.
Recommendations
  • Add step-by-step instructions for creating and managing Azure Storage accounts and Key Vault secrets using Azure CLI commands, which are cross-platform and widely used on Linux.
  • Include examples of ARM template deployment using Azure CLI or bash scripts, alongside the Azure DevOps release pipeline instructions.
  • Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and provide links to relevant Azure CLI documentation.
  • Where screenshots of the Azure portal are used, supplement with equivalent CLI commands and sample output.
  • Review terminology to avoid implying that GUI or Windows-based workflows are the default or preferred method.
GitHub Create Pull Request
Data Factory Encrypt Azure Data Factory with customer-managed key ...n/articles/data-factory/enable-customer-managed-key.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 features, but does not provide explicit Linux or cross-platform command examples. The instructions and screenshots focus exclusively on the Azure Portal UI, which is platform-agnostic, but where command-line is mentioned, it implicitly prioritizes Windows tools (PowerShell) and does not provide parity for Linux users. There are no Bash or Linux-specific CLI examples, and no mention of Linux shell environments.
Recommendations
  • Provide explicit Bash/Azure CLI command examples alongside PowerShell, especially for enabling Key Vault features and permissions.
  • When referencing Azure CLI, clarify that it is cross-platform and provide both Windows (PowerShell) and Linux (Bash) command syntax where applicable.
  • Add Linux-specific notes or screenshots where command-line actions are shown, to ensure parity for users on non-Windows platforms.
  • Avoid listing PowerShell before Azure CLI, or alternate the order, to avoid the impression of Windows-first bias.
  • Explicitly state that all portal-based instructions are platform-agnostic, but supplement with CLI instructions for automation scenarios on both Windows and Linux.
GitHub Create Pull Request
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 →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Azure PowerShell as a primary tool for performing copy activities, which is predominantly used on Windows. PowerShell is mentioned explicitly, while there is no mention of Bash, CLI, or Linux-native tools. The ordering of tools places PowerShell before REST API and ARM templates, and there is no explicit Linux example or parity for command-line usage.
Recommendations
  • Include Azure CLI as a listed tool, with links to relevant quickstart guides.
  • Add examples or references for performing the same tasks using Bash or Linux shell environments.
  • Reorder the list to avoid implicit prioritization of Windows tools (e.g., group SDKs and command-line tools together, or list by popularity/platform neutrality).
  • Explicitly mention cross-platform compatibility for each tool, clarifying which are available on Linux and macOS.
GitHub Create Pull Request
Data Factory Quickstart: Create an Azure Data Factory using Python .../data-factory/quickstart-create-data-factory-python.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a subtle Windows bias by referencing Windows-specific tools and workflows first, such as Notepad for file creation and 'command prompt with administrator privileges' for installing Python packages. There are no explicit Linux or macOS alternatives provided for these steps, nor are cross-platform instructions given for file creation or terminal usage. The only tool mentioned for interacting with Azure Blob Storage is Azure Storage Explorer, which is cross-platform but is presented without alternatives. No PowerShell-specific commands or Windows-only tools are used, but the overall workflow assumes a Windows environment.
Recommendations
  • Provide cross-platform instructions for creating the input file, e.g., using 'nano', 'vim', or 'touch' on Linux/macOS.
  • Replace 'command prompt with administrator privileges' with 'terminal or command prompt' and clarify that administrator privileges are only needed if required by the user's environment.
  • Explicitly mention that Azure Storage Explorer is available on Windows, Linux, and macOS, and suggest alternatives such as the Azure CLI or azcopy for users who prefer command-line tools.
  • Add notes or examples for Linux/macOS users where workflows differ (e.g., file paths, environment setup).
  • Ensure all steps are platform-neutral or provide platform-specific instructions in parallel.
GitHub Create Pull Request
Data Factory Transform data by using the Stored Procedure activity .../data-factory/transform-data-using-stored-procedure.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on SQL Server (a Microsoft/Windows-centric database) and referencing installation of Self-hosted integration runtime on the same machine as SQL Server, which is typically a Windows environment. There are no examples or mentions of Linux-based SQL Server deployments, nor are Linux-specific instructions or parity considerations provided. The tutorial referenced is 'transform data-spark-powershell', which implies a Windows/PowerShell-first approach, with no mention of Bash or Linux CLI alternatives.
Recommendations
  • Include explicit instructions and examples for deploying Self-hosted integration runtime on Linux machines, especially for SQL Server on Linux.
  • Reference Linux-compatible tools and workflows (e.g., Bash, Azure CLI) alongside or before Windows/PowerShell examples.
  • Clarify that SQL Server can run on Linux and provide links or steps for such deployments.
  • Add parity in tutorials by offering both PowerShell and Bash/CLI walkthroughs.
  • Mention cross-platform considerations for integration runtime installation and management.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/copy-clone-data-factory.md .../main/articles/data-factory/copy-clone-data-factory.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references a Powershell-based pattern for sharing SelfHosted Integration Runtime, and does not provide equivalent Linux or cross-platform CLI examples. There is an implicit assumption of Windows tooling (Powershell) without mention of alternatives such as Azure CLI or Bash scripts, and no Linux-specific guidance is offered.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for cloning and sharing SelfHosted Integration Runtime.
  • Reference cross-platform tools and patterns before or alongside Windows/Powershell-specific methods.
  • Explicitly mention platform-agnostic approaches where possible, and clarify which steps are applicable regardless of OS.
  • Link to documentation or guides for Linux/macOS users performing similar tasks.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by using Windows-style executable names (e.g., MyMapper.exe, MyReducer.exe) in its JSON sample and file paths, without providing equivalent Linux examples (such as Python scripts or shell scripts). There is no mention of Linux-compatible formats or guidance for users who may want to use non-Windows executables, which is a common scenario in Hadoop Streaming on Linux-based clusters.
Recommendations
  • Provide examples using Linux-compatible mapper and reducer scripts (e.g., MyMapper.py, MyReducer.sh) alongside the Windows .exe examples.
  • Clarify that both Windows and Linux executables/scripts are supported, and specify any platform-specific requirements or limitations.
  • Add guidance on how to prepare and upload Linux-based scripts to Azure Storage for use in HDInsight Streaming activities.
  • Include notes or examples for common open-source languages used in Hadoop Streaming (e.g., Python, Perl, Bash) to improve parity for Linux users.
GitHub Create Pull Request
← Previous Page 36 of 40 Next →