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 901-925 of 1000 flagged pages
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 →
Scanned: 2026-01-09 00:34
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 focusing exclusively on configuration steps via the Azure portal and ADF UI, which are browser-based and platform-agnostic but typically associated with Windows workflows. There are no Linux-specific instructions, command-line examples, or references to Linux tools. While a related link mentions Azure PowerShell, there is no mention of Azure CLI or Bash examples, which are more common in Linux environments. The tutorial assumes usage of Microsoft Edge or Google Chrome, but does not address Linux-specific browser or tool considerations.
Recommendations
  • Add parallel instructions using Azure CLI, including Bash examples for Linux users.
  • Reference and link to Linux-friendly tools and workflows (e.g., Azure CLI, Bash scripts) alongside PowerShell.
  • Explicitly state platform compatibility for browser-based steps, and mention Linux support for Azure portal and ADF UI.
  • Include troubleshooting notes or tips for Linux users where relevant (e.g., browser support, file paths, permissions).
  • Ensure related content includes links to Linux command-line configuration guides, not just PowerShell.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-virtual-network-configuration.md ...ssis-integration-runtime-virtual-network-configuration.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 UI and linking to a PowerShell-based workflow for joining Azure-SSIS IR to a virtual network, without providing equivalent Linux CLI (Azure CLI, Bash) examples or mentioning cross-platform command-line alternatives. All step-by-step instructions are tailored to the Azure portal, which is most commonly used on Windows, and the related content prioritizes PowerShell over Azure CLI or Bash scripts.
Recommendations
  • Add equivalent instructions for configuring virtual network injection using Azure CLI (cross-platform) and Bash scripts, making it clear these can be run on Linux, macOS, and Windows.
  • In the 'Related content' section, provide links to documentation for joining Azure-SSIS IR to a virtual network via Azure CLI and REST API, not just PowerShell.
  • When listing command-line options, mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
  • Include explicit notes or examples for users on Linux/macOS, highlighting any differences or considerations when performing these tasks outside Windows environments.
  • Where screenshots or UI steps are shown, consider referencing the Azure Cloud Shell (which supports Bash and PowerShell) as a cross-platform alternative.
GitHub Create Pull Request
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 →
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 demonstrates a Windows bias by recommending and referencing XrmToolBox, a Windows-only tool, for troubleshooting Dynamics 365 connectors. There are no equivalent Linux or cross-platform troubleshooting tools or methods mentioned, and no command-line or script-based examples for non-Windows environments are provided.
Recommendations
  • Include alternative, cross-platform tools (such as command-line utilities or REST API examples) for troubleshooting Dynamics 365 connectors.
  • Provide Linux/macOS-compatible troubleshooting steps, such as using curl, PowerShell Core (pwsh), or Python scripts to test connectivity and API responses.
  • Clearly indicate when a recommended tool (e.g., XrmToolBox) is Windows-only, and suggest equivalent approaches for users on other operating systems.
  • Add explicit Linux and macOS examples or notes in troubleshooting sections, especially where tool usage is recommended.
GitHub 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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides detailed instructions for setting up Azure Private Link for Azure Data Factory, but when describing the creation of a virtual machine for the self-hosted integration runtime (IR), it only references Windows Server images and does not mention or provide examples for Linux-based setups. There are no PowerShell-specific commands or Windows-only tools mentioned, but the explicit reference to Windows images and the absence of Linux guidance indicates a Windows-first and missing Linux example bias.
Recommendations
  • Include instructions and examples for deploying the self-hosted IR on Linux virtual machines, such as Ubuntu or CentOS, alongside the Windows example.
  • Mention supported Linux distributions for self-hosted IR, if applicable, and provide guidance for their configuration.
  • Clarify in the prerequisites or setup sections whether Linux is supported for self-hosted IR, and if not, explicitly state this to avoid ambiguity.
  • Where VM creation steps are shown, provide parallel steps for both Windows and Linux images, including any OS-specific configuration notes.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/deploy-linked-arm-templates-with-vsts.md .../data-factory/deploy-linked-arm-templates-with-vsts.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 UI for all resource creation and configuration steps, without mentioning or providing examples for equivalent operations using cross-platform tools such as Azure CLI or ARM templates via command line. There are no Linux or macOS-specific instructions or examples, and no PowerShell scripts are present, but the reliance on GUI-based workflows implicitly favors Windows users. The absence of CLI-based steps makes it harder for Linux users or those working in headless environments to follow the guide.
Recommendations
  • Add step-by-step instructions for creating Azure Storage accounts, containers, and Key Vault secrets using Azure CLI commands.
  • Provide examples for linking Azure Key Vault to Azure DevOps Services using CLI or REST API where possible.
  • Include ARM template deployment examples using Azure CLI and/or PowerShell, making clear which commands work cross-platform.
  • Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and highlight any platform-specific differences.
  • Consider adding a table or section comparing GUI and CLI approaches for each major step.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/join-azure-ssis-integration-runtime-virtual-network-ui.md ...join-azure-ssis-integration-runtime-virtual-network-ui.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows-centric tools and workflows, such as the Azure portal UI, Microsoft Edge, and Google Chrome, without mentioning Linux alternatives or command-line options. There are no examples or instructions for Linux users (e.g., using CLI, Bash, or Linux browsers), and the only related content for automation is via Azure PowerShell, which is primarily a Windows/PowerShell tool. No Linux-native tools or patterns are discussed.
Recommendations
  • Add equivalent instructions for using Azure CLI (az commands) to perform the same operations, with example commands and outputs.
  • Include Linux-friendly browser options (such as Firefox) if supported, or clarify browser requirements for Linux users.
  • Provide links or references to Linux-specific documentation or workflows for joining Azure-SSIS IR to a virtual network.
  • Ensure parity in automation examples by including Bash scripts or CLI instructions alongside PowerShell examples.
  • Explicitly state platform requirements and limitations, and offer guidance for Linux users where the Azure portal or certain features may have platform-specific behaviors.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/quickstart-create-data-factory-python.md .../data-factory/quickstart-create-data-factory-python.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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-centric tools and workflows first. For example, it instructs users to 'Launch Notepad' to create a text file, which is a Windows-specific application, and mentions 'command prompt with administrator privileges' before 'terminal', implying a Windows-first approach. The optional tool Azure Storage Explorer is cross-platform, but no Linux-specific alternatives or instructions (such as using nano, vim, or touch for file creation, or specifying Linux terminal commands) are provided. There are no explicit PowerShell or Windows-only tools, but the examples and instructions assume a Windows environment and omit Linux/macOS equivalents.
Recommendations
  • Include instructions for creating files using Linux/macOS tools (e.g., 'Use nano, vim, or touch to create input.txt').
  • Clarify that 'terminal or command prompt' can refer to Bash, Zsh, or other shells on Linux/macOS, and that administrator privileges may not be required or are achieved differently.
  • Provide explicit Linux/macOS command examples where relevant, such as using 'echo' or text editors to create files.
  • Add notes or sections for Linux/macOS users, ensuring parity in setup and troubleshooting steps.
  • Avoid referencing Windows-specific applications (like Notepad) without offering cross-platform alternatives.
GitHub Create Pull Request
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 →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias by referencing SQL Server (traditionally a Windows-centric database) and providing instructions for installing the Self-hosted integration runtime on the same machine as SQL Server, which implicitly assumes a Windows environment. There are no explicit Linux or cross-platform examples, nor is there mention of running SQL Server or the integration runtime on Linux. The tutorial referenced in the note is 'tutorial-transform-data-spark-powershell.md', which suggests a Windows-first approach by highlighting PowerShell, a Windows-native tool, without mentioning Bash or other Linux-native alternatives.
Recommendations
  • Include explicit instructions or examples for deploying SQL Server and the Self-hosted integration runtime on Linux environments.
  • Reference Linux-native tools (e.g., Bash) in tutorials alongside PowerShell, or provide links to equivalent Linux tutorials.
  • Clarify that Azure SQL Database and Azure Synapse Analytics are cross-platform and can be accessed from both Windows and Linux environments.
  • Add notes or sections on how to configure the integration runtime and stored procedure activities from Linux-based systems.
  • Ensure connector documentation and examples cover both Windows and Linux scenarios equally.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/deploy-linked-arm-templates-with-vsts.md .../data-factory/deploy-linked-arm-templates-with-vsts.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 (a GUI tool commonly used on Windows) for all resource creation and management steps, without mentioning or providing examples for equivalent operations using cross-platform tools like Azure CLI or PowerShell Core. There are no Linux-specific instructions or command-line examples, which may hinder parity for users working on Linux or macOS environments.
Recommendations
  • Add command-line examples using Azure CLI for all resource creation and management steps (e.g., creating storage accounts, containers, and Key Vault secrets).
  • Include PowerShell Core examples where appropriate, ensuring they work on both Windows and Linux.
  • Explicitly mention that Azure DevOps and ARM template deployments can be performed from Linux/macOS environments, and provide relevant instructions.
  • Where GUI steps are described, offer parallel CLI alternatives to ensure accessibility for non-Windows users.
  • Review screenshots and instructions to ensure they do not assume a Windows-only workflow.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-virtual-network-configuration.md ...ssis-integration-runtime-virtual-network-configuration.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 UI and linking to a PowerShell-based guide for joining Azure-SSIS IR to a virtual network, without mentioning or providing equivalent Linux CLI (Azure CLI, Bash) instructions. All step-by-step examples are based on GUI interactions typical of Windows environments, and no Linux-oriented tools or workflows are described.
Recommendations
  • Add equivalent instructions using Azure CLI (cross-platform) for all configuration steps, including resource provider registration, subnet delegation, and RBAC permissions.
  • Explicitly mention that the Azure CLI can be used from Linux, macOS, and Windows, and provide sample commands.
  • Include links to documentation or tutorials for performing these tasks via Bash scripts or other Linux-native tools.
  • Ensure parity in examples by presenting both PowerShell and Azure CLI/Bash alternatives side-by-side where applicable.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-http.md ...docs/blob/main/articles/data-factory/connector-http.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page shows evidence of Windows bias in two main areas. First, Windows-specific tools (Visual Studio, PowerShell's Invoke-RestMethod, MMC for certificate management) are mentioned as primary or sole examples for testing HTTP requests and managing certificates. Second, instructions for certificate permissions and installation are exclusively described using Windows tools and terminology, with no mention of Linux equivalents or cross-platform alternatives.
Recommendations
  • Include Linux and cross-platform tools for testing HTTP requests, such as curl, wget, or httpie, alongside PowerShell and Visual Studio.
  • Add instructions for managing client certificates on Linux systems, such as using openssl, certutil, or updating permissions in /etc/ssl/certs.
  • When describing authentication types (e.g., Windows authentication), clarify platform applicability and provide alternatives for Linux environments.
  • Ensure that examples and troubleshooting steps are provided for both Windows and Linux self-hosted Integration Runtime hosts.
  • Where possible, use neutral, cross-platform terminology and tools first, or present Windows and Linux options side-by-side.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-azure-sql-managed-instance.md ...s/data-factory/connector-azure-sql-managed-instance.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a bias toward Windows environments by exclusively referencing SQL Server Management Studio (SSMS) for administrative tasks such as creating logins and users. There are no examples or mentions of Linux-native tools (e.g., sqlcmd, Azure Data Studio on Linux) for these operations. All T-SQL examples assume the use of SSMS, which is primarily a Windows application. No PowerShell examples are present, but the lack of Linux CLI or cross-platform tool references indicates a Windows-centric approach.
Recommendations
  • Include instructions and examples for performing administrative tasks (e.g., creating logins, users) using cross-platform tools such as sqlcmd or Azure Data Studio, which are available on Linux and macOS.
  • Explicitly mention that T-SQL commands can be executed from any SQL client, not just SSMS, and provide sample command-line invocations for Linux environments.
  • Add screenshots or walkthroughs for Azure Data Studio or command-line tools on Linux where UI steps are shown for SSMS.
  • Review all sections for references to Windows-only tools and ensure Linux equivalents are provided or referenced.
  • Where possible, use generic terminology (e.g., 'SQL client') instead of tool-specific instructions unless parity is provided.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references XrmToolBox, a Windows-only tool, as a troubleshooting method for Dynamics 365 connectors, without providing Linux or cross-platform alternatives. There are no command-line or platform-agnostic examples, and no mention of Linux-compatible tools or workflows.
Recommendations
  • Provide equivalent troubleshooting steps using cross-platform or Linux-compatible tools (e.g., using curl, Postman, or PowerShell Core on Linux).
  • Mention and link to any available Linux or web-based alternatives to XrmToolBox, or clarify if none exist.
  • Include examples or guidance for users working from Linux environments, such as using REST APIs directly.
  • When recommending third-party tools, specify their platform compatibility and suggest alternatives where possible.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page references a PowerShell-based pattern for sharing SelfHosted Integration Runtime, and links to a PowerShell-specific guide. No equivalent Linux or cross-platform CLI examples or alternatives are provided, and there is no mention of using Azure CLI, Bash, or other non-Windows tools for cloning or managing Data Factory resources.
Recommendations
  • Add examples and links for using Azure CLI and Bash scripts to clone or manage Data Factory resources, especially for sharing SelfHosted Integration Runtime.
  • Reference cross-platform tools and patterns before or alongside PowerShell-specific solutions.
  • Explicitly state which steps can be performed on Linux/macOS and provide parity in instructions.
  • Where PowerShell is mentioned, include equivalent Azure CLI commands or scripts for Linux users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/copy-activity-overview.md ...b/main/articles/data-factory/copy-activity-overview.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 tooling or PowerShell-heavy examples, but it does display subtle Windows-first bias. The only concrete example of hybrid/on-premises data movement is 'Copy data from a SQL Server database to Azure' (with a PowerShell tutorial), and there are no Linux-specific or cross-platform examples. There is no mention of Linux tools, shell commands, or Linux file system scenarios, and the quickstart/tutorial links focus on Windows-centric technologies (SQL Server, PowerShell).
Recommendations
  • Add Linux-based examples, such as copying data from a Linux file system (e.g., ext4, NFS) to Azure Blob Storage.
  • Include tutorials or quickstarts for hybrid scenarios using Linux hosts, e.g., copying data from a PostgreSQL/MySQL database running on Linux.
  • Provide cross-platform command-line examples (e.g., Bash, CLI) alongside any PowerShell samples.
  • Mention Linux-specific considerations for self-hosted integration runtime installation and configuration.
  • Ensure parity in documentation for both Windows and Linux environments, especially in hybrid/on-premises scenarios.
GitHub 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 →
Scanned: 2026-01-08 00:53
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 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 virtual machines. There are no Linux-specific instructions, examples, or clarifications about support for Linux hosts, which may lead Linux users to believe that only Windows is supported or recommended.
Recommendations
  • Add parallel instructions for creating a Linux-based virtual machine (e.g., Ubuntu) for hosting the self-hosted IR, including supported distributions and any prerequisites.
  • Clarify whether the self-hosted IR is supported on Linux, and if so, provide links to installation guides or scripts for Linux environments.
  • Include notes or tables comparing Windows and Linux support for self-hosted IR, highlighting any differences or limitations.
  • Ensure that all example steps (such as VM creation, firewall configuration, and DNS setup) are presented for both Windows and Linux environments, or explicitly state if only Windows is supported.
  • Mention relevant Linux tools or commands where applicable (e.g., for DNS configuration or firewall rules), not just portal-based or Windows-centric approaches.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-migration-guidance-s3-azure-storage.md ...ta-factory/data-migration-guidance-s3-azure-storage.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively recommending and describing installation of self-hosted Integration Runtime on Azure Windows VMs for private link scenarios, without mentioning Linux VM support or providing Linux-based instructions. All VM configuration examples and scaling recommendations are Windows-centric, and there are no Linux alternatives or parity in guidance.
Recommendations
  • Explicitly state whether self-hosted Integration Runtime supports Linux VMs. If supported, provide equivalent instructions and configuration recommendations for Linux VM deployments.
  • Include Linux VM sizing examples and monitoring guidance alongside Windows VM recommendations.
  • Add notes or sections clarifying platform requirements and limitations for self-hosted Integration Runtime, ensuring users on Linux are aware of their options.
  • Where VM configuration is discussed, present both Windows and Linux options, or explain why only Windows is supported if that is the case.
  • Ensure parity in troubleshooting, scaling, and best practices guidance for both Windows and Linux environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/quickstart-create-data-factory-bicep.md ...s/data-factory/quickstart-create-data-factory-bicep.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation shows mild Windows bias. The text editor example suggests Notepad, a Windows tool, without mentioning Linux alternatives. While deployment and resource management examples use both Azure CLI and PowerShell, the CLI commands are cross-platform, but PowerShell is typically associated with Windows. There are no explicit Linux-specific instructions or examples (e.g., using Vim, nano, or Linux file paths), and the documentation does not mention Linux shell scripting or tools. The portal instructions are platform-neutral.
Recommendations
  • When suggesting a text editor, mention cross-platform or Linux editors (e.g., Vim, nano, gedit) alongside Notepad.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and consider adding Linux-specific notes (e.g., file path formats, shell usage).
  • If PowerShell is mentioned, note that it is available on Linux and macOS, or provide Bash equivalents for common tasks.
  • Add a brief section or note confirming that all steps are applicable on Linux and macOS, and highlight any platform-specific considerations.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/quickstart-create-data-factory-python.md .../data-factory/quickstart-create-data-factory-python.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exhibits mild 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 cross-platform alternatives provided for these steps. The only tool mentioned for interacting with Azure Storage is Azure Storage Explorer, which is cross-platform but is introduced without alternatives. No Linux-specific commands, editors, or shell instructions are given.
Recommendations
  • When instructing users to create a text file, suggest cross-platform editors (e.g., 'Use Notepad (Windows), nano/vim (Linux), or TextEdit (macOS) to create input.txt').
  • For terminal instructions, use 'Open a terminal or command prompt' rather than specifying 'with administrator privileges', and clarify that 'sudo' may be needed on Linux/macOS.
  • Explicitly mention that Azure Storage Explorer is available on Windows, Linux, and macOS, and suggest alternatives such as the Azure CLI or azcopy for command-line users.
  • Include Linux/macOS shell commands (e.g., 'pip install ...' in bash/zsh) and note any OS-specific considerations for authentication or environment setup.
  • Add a note that the Python code and SDKs are cross-platform and can be run on Windows, Linux, or macOS, provided Python is installed.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on SQL Server, Azure SQL Database, and Azure Synapse Analytics, which are traditionally Windows-centric technologies. There are no examples or mentions of Linux-based database engines (e.g., PostgreSQL, MySQL), nor is there any discussion of running the integration runtime or related activities on Linux systems. The tutorial and introductory links reference PowerShell, a Windows-first tool, without offering Bash or Linux CLI alternatives.
Recommendations
  • Add examples and guidance for invoking stored procedures on Linux-supported databases such as PostgreSQL and MySQL, if supported by Data Factory.
  • Include instructions for installing and running the Self-hosted integration runtime on Linux, and clarify cross-platform support.
  • Provide Bash or Azure CLI equivalents for any PowerShell-based tutorials or commands.
  • Explicitly mention platform compatibility (Windows/Linux) for all components and activities discussed.
  • Add links to documentation or tutorials for Linux users where relevant.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates bias toward Windows by exclusively using Windows-style executable names (e.g., MyMapper.exe, MyReducer.exe) in its JSON sample and file paths. There are no examples or mentions of Linux-style scripts (e.g., Python, Bash, or .sh files), which are commonly used in Hadoop Streaming jobs on Linux-based clusters. This may mislead users into thinking only Windows executables are supported or preferred, despite HDInsight and Hadoop Streaming being primarily Linux-based.
Recommendations
  • Provide examples using Linux-compatible scripts, such as Python (.py), Bash (.sh), or other common Linux executables, in addition to or instead of Windows .exe files.
  • Clarify in the documentation that both Windows and Linux executables/scripts are supported, and specify any platform limitations.
  • Add a section or note explaining how users can prepare and upload Linux-based mapper and reducer scripts to Azure Storage for use in Hadoop Streaming activities.
  • Ensure that sample file paths and command environment variables are platform-neutral or include both Windows and Linux variants.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation focuses exclusively on configuration via the Azure portal and ADF UI, which are web-based and platform-agnostic, but there is a subtle Windows bias: browser recommendations (Edge and Chrome) are listed, which are more commonly associated with Windows environments. There are no command-line examples, and no mention of Linux-specific tools or patterns. The only reference to PowerShell (a Windows-centric tool) is in the 'Related content' section, where joining via Azure PowerShell is listed, but there is no equivalent mention of Bash, Azure CLI, or Linux-native approaches. The documentation does not provide parity for Linux users who may prefer CLI or scripting approaches.
Recommendations
  • Add examples for joining Azure-SSIS IR to a virtual network using Azure CLI or Bash scripts, which are more common in Linux environments.
  • Explicitly mention cross-platform compatibility for all steps, including browser support on Linux and macOS.
  • In the 'Related content' section, include links to tutorials or documentation for performing these tasks using Azure CLI or REST API, not just PowerShell.
  • Clarify that the Azure portal and ADF UI are accessible from any OS with a supported browser, and list browser options available on Linux.
  • If PowerShell is mentioned, also mention PowerShell Core (cross-platform) or provide equivalent Bash/CLI instructions.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-square.md ...cs/blob/main/articles/data-factory/connector-square.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references Windows support explicitly for the self-hosted integration runtime and links to Windows prerequisites, but does not mention Linux support or provide Linux-specific instructions or examples. No Linux or cross-platform guidance is present for self-hosted runtime setup or compatibility.
Recommendations
  • Explicitly state whether Linux is supported for the self-hosted integration runtime in this connector scenario.
  • If Linux is supported, provide a link to Linux installation/prerequisite documentation alongside the Windows link.
  • Include Linux-specific instructions or examples for setting up the self-hosted integration runtime, if applicable.
  • If Linux is not supported, clearly state this limitation to avoid ambiguity.
  • Ensure parity in documentation structure and examples for both Windows and Linux environments where possible.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists Azure PowerShell as a primary tool for performing the Copy activity, but does not mention Linux-specific tools or provide Bash/CLI examples. PowerShell, which is traditionally associated with Windows, is highlighted, and there is no explicit mention of cross-platform command-line tools like Azure CLI or Linux shell scripting.
Recommendations
  • Include Azure CLI as a recommended tool alongside PowerShell, with a corresponding quickstart link.
  • Provide explicit examples or links for performing the Copy activity using Bash or Linux shell environments.
  • Ensure that PowerShell is not listed before more cross-platform tools like Azure CLI to avoid the appearance of Windows-first bias.
  • Add a note clarifying the cross-platform availability of tools where applicable.
GitHub Create Pull Request
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 →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias by recommending the use of XrmToolBox, a Windows-only tool, for troubleshooting Dynamics 365 connectors. No equivalent Linux tools or cross-platform alternatives are mentioned, and there are no command-line or script examples for Linux environments. The documentation assumes access to Windows-based utilities, which may exclude Linux or macOS users.
Recommendations
  • Provide cross-platform alternatives to XrmToolBox, such as open-source FetchXML testers or REST API usage examples that work on Linux and macOS.
  • Include troubleshooting steps or examples using command-line tools available on Linux (e.g., curl, wget, PowerShell Core, or REST API calls).
  • Explicitly state when a recommended tool is Windows-only and suggest equivalent approaches for non-Windows users.
  • Where possible, link to documentation or community tools that support Linux/macOS for Dynamics 365 troubleshooting.
GitHub Create Pull Request
← Previous Page 37 of 40 Next →