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 776-800 of 1000 flagged pages
Data Factory Provision the Azure-SSIS integration runtime ...es/data-factory/tutorial-deploy-ssis-packages-azure.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools (SSDT, SSMS, dtutil, AzureDTExec) as the primary means to deploy and manage SSIS packages, without mentioning Linux/macOS alternatives or clarifying cross-platform support. Examples and instructions assume the use of Windows tools and patterns, and there are no explicit Linux/macOS usage notes or parity guidance.
Recommendations
  • Explicitly state platform requirements for SSDT, SSMS, dtutil, and AzureDTExec, and clarify if any are available or supported on Linux/macOS.
  • If possible, provide alternative instructions or tools for Linux/macOS users (e.g., Azure portal, REST API, Azure CLI, or cross-platform Data Factory features).
  • Add notes or sections addressing Linux/macOS users, including any limitations and recommended workarounds.
  • Reorder tool mentions to avoid always listing Windows tools first, or group them by platform.
  • Reference Data Factory pipeline activities and Azure portal actions as platform-neutral options where applicable.
GitHub Create Pull Request
Data Factory Copy data from SQL Server to Blob storage using Azure portal ...n/articles/data-factory/tutorial-hybrid-copy-portal.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias: all examples and instructions for setting up SQL Server use SQL Server Management Studio (SSMS), a Windows-only tool, with no mention of Linux-compatible alternatives. The integration runtime setup assumes a Windows environment, and there are no instructions for Linux or macOS users on how to perform equivalent steps (e.g., using Azure Data Studio, sqlcmd, or Linux SQL Server installations). The order and language throughout implicitly assume the user is on Windows.
Recommendations
  • Add instructions for setting up SQL Server and creating tables using cross-platform tools such as Azure Data Studio or sqlcmd.
  • Explicitly mention how to install and use the self-hosted integration runtime on Linux and macOS, including links to relevant installers and documentation.
  • Provide example commands for Linux/macOS users (e.g., shell commands, alternative editors to Notepad).
  • Clarify any platform-specific limitations or requirements for the integration runtime and Data Factory UI.
  • Reorder sections or add parallel instructions so Linux/macOS users are not forced to adapt Windows-centric steps.
GitHub Create Pull Request
Data Factory Branching in Azure Data Factory pipeline ...ob/main/articles/data-factory/tutorial-control-flow.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows development environments. All code examples and project setup instructions assume the use of Visual Studio (Windows-only), .NET Framework (not .NET Core/SDK), and NuGet Package Manager Console (typically used in Visual Studio). There are no instructions or examples for Linux or macOS users, such as using VS Code, .NET Core, or command-line tools available cross-platform. The prerequisite tools and steps (Visual Studio, Azure Storage Explorer) are presented without Linux/macOS alternatives, and Windows-centric terminology and workflows are used throughout.
Recommendations
  • Add instructions for setting up the project using .NET Core/SDK and VS Code, which are cross-platform.
  • Provide equivalent steps for Linux/macOS users, such as using the 'dotnet' CLI to create and manage projects and NuGet packages.
  • Mention and link to Azure Storage Explorer downloads for Linux/macOS, or suggest using Azure CLI for blob management.
  • Clarify that the Azure .NET SDK and Data Factory APIs can be used on Linux/macOS, and provide sample commands.
  • Reorder or parallelize instructions so that Windows and Linux/macOS workflows are presented side by side.
  • Avoid assuming Visual Studio is required; highlight alternatives like JetBrains Rider, VS Code, or plain CLI.
GitHub Create Pull Request
Data Factory Copy on-premises data using the Azure Copy Data tool ...rticles/data-factory/tutorial-hybrid-copy-data-tool.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing Windows tools such as SQL Server Management Studio (SSMS) for database setup, and by describing installation steps for the self-hosted integration runtime without clarifying Linux/macOS support or providing platform-specific instructions. There are no examples or guidance for Linux or macOS users, and Windows-centric tools and patterns are mentioned first and exclusively.
Recommendations
  • Explicitly state platform requirements and support for the self-hosted integration runtime (e.g., whether Linux/macOS are supported).
  • Provide alternative instructions for Linux/macOS users, such as using Azure Data Studio or command-line tools (sqlcmd) for SQL Server setup.
  • Include platform-specific installation steps for the integration runtime, or link to relevant cross-platform installation guides.
  • Add notes or sections clarifying any differences in experience or prerequisites for Linux/macOS users.
GitHub Create Pull Request
Data Factory Transform data using Hive in Azure Virtual Network using Azure portal ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-hive-virtual-network-portal.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows a notable Windows bias by requiring Azure PowerShell, referencing Windows file paths (e.g., hosts file at C:\Windows\System32\drivers\etc), and omitting Linux/macOS equivalents for key steps such as editing the hosts file or installing the self-hosted integration runtime. There are no Linux or macOS-specific instructions or examples, making it harder for non-Windows users to follow the tutorial.
Recommendations
  • Provide equivalent instructions for Linux/macOS environments, such as editing /etc/hosts instead of C:\Windows\System32\drivers\etc.
  • Include guidance for installing and configuring Azure CLI and the self-hosted integration runtime on Linux/macOS VMs.
  • Mention cross-platform alternatives to Azure PowerShell, such as Azure CLI, and provide example commands.
  • Clarify any platform-specific limitations or requirements for the self-hosted integration runtime.
  • Add screenshots or terminal examples for Linux/macOS where appropriate.
GitHub Create Pull Request
Data Factory Transform data using Spark in Azure Data Factory ...ta-factory/tutorial-transform-data-spark-powershell.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively uses Azure PowerShell for all deployment, management, and monitoring steps, with no mention of cross-platform alternatives such as Azure CLI, Bash, or REST API. All command-line examples are PowerShell scripts, and instructions assume the use of PowerShell, which is most commonly used on Windows. There are no Linux/macOS-specific instructions or parity examples, and the prerequisite section only references Azure PowerShell installation.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Add a note clarifying that Azure PowerShell can be installed and used on Linux/macOS, or link to installation instructions for those platforms.
  • Include Bash script examples or REST API alternatives where appropriate.
  • Reorder examples or provide tabs for PowerShell and CLI/Bash to avoid Windows-first presentation.
  • Explicitly mention cross-platform compatibility and provide troubleshooting tips for non-Windows environments.
GitHub Create Pull Request
Data Factory Roles and permissions for Azure Data Factory ...in/articles/data-factory/concepts-roles-permissions.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page mentions updating a data factory from PowerShell or the SDK as a scenario, which implicitly prioritizes Windows tooling (PowerShell) and does not mention cross-platform alternatives (e.g., Azure CLI, Bash, or Linux/macOS SDK usage). No Linux/macOS-specific examples or instructions are provided, and PowerShell is referenced as the primary automation tool, which may create friction for non-Windows users.
Recommendations
  • Explicitly mention and provide examples for Azure CLI, which is cross-platform, alongside PowerShell.
  • Clarify that SDKs (such as Python, .NET, Java) are available and supported on Linux/macOS, and provide example usage.
  • Avoid referencing PowerShell as the sole automation tool; include Bash or shell script examples where appropriate.
  • Add a note or section highlighting cross-platform support for Data Factory management tasks.
GitHub Create Pull Request
Data Factory Copy data from Netezza ...s/blob/main/articles/data-factory/connector-netezza.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page for copying data from Netezza in Azure Data Factory or Synapse Analytics shows a mild Windows bias. It references 'Windows versions' as supported platforms for the self-hosted integration runtime, but does not mention Linux or macOS support or provide instructions/examples for those platforms. There are no explicit PowerShell or Windows command-line examples, but the lack of Linux parity in prerequisites and installation guidance may create friction for non-Windows users.
Recommendations
  • Explicitly state whether the self-hosted integration runtime and Netezza ODBC driver are supported on Linux and macOS platforms.
  • If Linux is supported, provide installation instructions for the IBM Netezza ODBC driver on Linux (and macOS, if applicable), including any required dependencies or configuration steps.
  • Include links or references to Linux/macOS-specific documentation for setting up the integration runtime and ODBC drivers.
  • If Windows is the only supported platform, clearly state this early in the prerequisites section to set expectations for non-Windows users.
GitHub Create Pull Request
Data Factory Troubleshoot the Azure Blob Storage connector ...a-factory/connector-troubleshoot-azure-blob-storage.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references Windows-specific tooling (diawp.exe.config) and configuration steps for disabling FIPS mode on the VM, without mentioning Linux equivalents or providing guidance for Linux/macOS users. No Linux-specific troubleshooting steps or examples are given for self-hosted integration runtime scenarios.
Recommendations
  • Add instructions for disabling FIPS mode or handling MD5 requirements on Linux/macOS environments, including relevant config file locations and commands.
  • Clarify whether the self-hosted integration runtime is supported on Linux/macOS, and if so, provide platform-specific troubleshooting steps.
  • Include examples or notes for Linux users wherever Windows-specific tools or paths are referenced.
  • Explicitly state platform limitations if certain troubleshooting steps are Windows-only.
GitHub Create Pull Request
Data Factory Use an Azure Resource Manager template to create an integration runtime ...ure-ssis-integration-runtime-resource-manager-template.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides PowerShell commands for deploying and managing Azure-SSIS IR, with no mention of Linux/macOS-compatible alternatives (such as Azure CLI or REST API). All example commands and tooling references are Windows-centric, creating friction for users on non-Windows platforms.
Recommendations
  • Add equivalent Azure CLI examples for deploying and managing Azure-SSIS IR, as Azure CLI is cross-platform.
  • Reference REST API documentation for template deployment and IR management, which can be used from any OS.
  • Explicitly state platform requirements or limitations if certain features are only available via PowerShell.
  • Reorder examples so that cross-platform solutions (Azure CLI, REST API) are presented before or alongside PowerShell.
GitHub Create Pull Request
Data Factory Until activity ...n/articles/data-factory/control-flow-until-activity.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides extensive PowerShell command examples for running Azure Data Factory pipelines, with file paths and instructions tailored to Windows environments (e.g., C:\ADF). There are no equivalent examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or cross-platform file paths. The only automation walkthrough is Windows/PowerShell-centric, which may create friction for non-Windows users.
Recommendations
  • Add equivalent Azure CLI examples for pipeline creation, execution, and monitoring, suitable for Linux/macOS users.
  • Include Bash script samples and use cross-platform file paths (e.g., ~/ADF or ./ADF) in examples.
  • Explicitly mention that JSON pipeline definitions can be used with Azure CLI or REST API, and provide links or brief instructions.
  • Reorder or parallelize examples so that Windows/PowerShell and Linux/Azure CLI approaches are presented side-by-side or in separate sections.
  • Clarify any platform-specific requirements or limitations, if any exist.
GitHub Create Pull Request
Data Factory Web Activity ...ain/articles/data-factory/control-flow-web-activity.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in the section describing how to base64-encode a PFX certificate for client certificate authentication. Only a PowerShell snippet is provided, with no mention of Linux/macOS alternatives (such as OpenSSL or base64 CLI tools). This may create friction for users on non-Windows platforms who need to perform the same task.
Recommendations
  • Add Linux/macOS equivalent commands for base64-encoding a PFX file (e.g., using 'base64' or 'openssl').
  • Explicitly mention that the task can be performed on any OS and provide cross-platform instructions.
  • Where possible, avoid assuming the use of Windows-specific tools in generic scenarios.
GitHub Create Pull Request
Data Factory Create an Azure-SSIS integration runtime in Azure Data Factory .../data-factory/create-azure-ssis-integration-runtime.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits a moderate Windows bias. It references Windows-centric tools (SSDT, SSMS, dtutil) as 'familiar tools' for deploying and running SSIS packages, and highlights Azure PowerShell as a primary method for provisioning Azure-SSIS IR. There are no explicit Linux/macOS alternatives or parity examples for these tasks, and Windows tools are mentioned before any cross-platform or portal-based options.
Recommendations
  • Explicitly mention cross-platform alternatives for SSIS package deployment and management, such as Azure CLI, REST API, or Data Factory web portal, especially for users on Linux/macOS.
  • Provide example workflows or scripts using Azure CLI or REST API for provisioning Azure-SSIS IR, alongside PowerShell examples.
  • Clarify which tools (e.g., dtutil, SSDT, SSMS) are Windows-only and suggest platform-agnostic alternatives or remote access strategies for non-Windows users.
  • Reorder examples so that platform-neutral methods (portal, ARM templates, REST API) are presented before Windows-specific tools.
GitHub Create Pull Request
Data Factory Wait activity ...in/articles/data-factory/control-flow-wait-activity.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides sample PowerShell commands and links to a PowerShell-based tutorial for running pipelines, with no equivalent examples or walkthroughs for Linux/macOS users (e.g., using Azure CLI, Bash, or REST API). Windows/PowerShell tooling is mentioned exclusively and first, creating friction for non-Windows users.
Recommendations
  • Add equivalent examples using Azure CLI and/or REST API for pipeline creation and execution.
  • Include links to tutorials for Linux/macOS users, demonstrating pipeline management without PowerShell.
  • Present cross-platform options side-by-side, or clarify that PowerShell is just one method among several.
GitHub Create Pull Request
Data Factory Review deployed resources ...ludes/data-factory-quickstart-verify-output-cleanup.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
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 equivalent examples for Linux/macOS users, such as Azure CLI or Bash commands. This creates friction for non-Windows users who may not have access to PowerShell or prefer native Linux tools.
Recommendations
  • Add Azure CLI examples for both resource group and data factory deletion.
  • Include Bash command snippets for Linux/macOS users.
  • Clearly indicate cross-platform alternatives and usage instructions.
  • Consider presenting CLI examples before or alongside PowerShell examples to promote parity.
GitHub Create Pull Request
Data Factory How to ingest data into Fabric using the Azure Data Factory Copy activity ...how-to-ingest-data-into-fabric-from-azure-data-factory.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a notable Windows bias, especially in the authentication section. The only example for forcing a permissions refresh uses PowerShell, with no mention of Linux/macOS alternatives (such as Azure CLI, Bash, or REST API via curl). Windows tools and patterns (PowerShell modules and commands) are referenced exclusively and first, and there are no Linux/macOS equivalent instructions or examples provided. This may create friction for non-Windows users attempting to follow the guide.
Recommendations
  • Provide equivalent instructions using Azure CLI and/or REST API (e.g., curl) for Linux/macOS users to refresh permissions.
  • Explicitly mention cross-platform alternatives wherever PowerShell is referenced.
  • Add notes or sections clarifying how Linux/macOS users can perform each step, especially for authentication and admin tasks.
  • Where screenshots or UI instructions are given, clarify any OS dependencies or provide platform-agnostic guidance.
GitHub Create Pull Request
Data Factory Use Azure SQL Managed Instance with Azure-SQL Server Integration Services (SSIS) in Azure Data Factory ...ata-factory/how-to-use-sql-managed-instance-with-ir.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by exclusively referencing Windows-centric tools such as SQL Server Management Studio (SSMS) and Windows Firewall. There are no examples or guidance for Linux/macOS users, nor are cross-platform alternatives (such as Azure Data Studio or CLI-based workflows) mentioned. This may create friction for users on non-Windows platforms, especially when managing SSIS packages or troubleshooting network connectivity.
Recommendations
  • Include examples and instructions using cross-platform tools such as Azure Data Studio, Azure CLI, or REST APIs for SSIS package management and deployment.
  • Explicitly mention Linux/macOS compatibility where relevant, and provide alternative steps for tasks that currently reference Windows-only tools (e.g., SSMS, Windows Firewall).
  • Add troubleshooting guidance for Linux/macOS users, especially for network configuration and connectivity.
  • Ensure screenshots and step-by-step guides are not exclusively based on Windows UI; consider including CLI or web portal alternatives.
GitHub Create Pull Request
Data Factory Incrementally copy data from a source data store to a destination data store ...les/data-factory/tutorial-incremental-copy-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page consistently references PowerShell-based tutorials for incremental data copy scenarios, with no mention of Linux/macOS alternatives or cross-platform command-line tools. All step-by-step instructions link to PowerShell guides, implying a Windows-centric approach and leaving Linux/macOS users without clear guidance.
Recommendations
  • Provide equivalent tutorials using Azure CLI or REST API, which are cross-platform and accessible from Linux/macOS.
  • Explicitly mention platform compatibility for each tutorial and offer alternative instructions for non-Windows environments.
  • Include examples and templates using Bash scripts or other Linux-native tools where applicable.
  • Reorder or balance examples so that Windows and Linux approaches are presented equally.
GitHub Create Pull Request
Data Factory Global parameters ...main/articles/data-factory/author-global-parameters.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page references deploying global parameters via a PowerShell script as part of the CI/CD process, without mentioning Linux/macOS equivalents (such as Azure CLI, Bash, or cross-platform automation tools). This creates a bias toward Windows users and may cause friction for those on Linux or macOS platforms.
Recommendations
  • Add equivalent instructions and examples for deploying global parameters using Azure CLI, Bash scripts, or other cross-platform tools.
  • Explicitly state that PowerShell Core is available cross-platform, if relevant, and provide usage examples for Linux/macOS.
  • Where possible, present platform-neutral automation options before or alongside Windows/PowerShell-specific instructions.
  • Include notes or links to documentation for Linux/macOS users to ensure parity in CI/CD workflows.
GitHub Create Pull Request
Data Factory Applying DataOps ...-docs/blob/main/articles/data-factory/apply-dataops.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, especially in the automated testing section, where PowerShell and Visual Studio/NUnit are highlighted as primary tools for CI/CD and testing. There are no explicit Linux/macOS alternatives or examples provided for these workflows, and the use of Windows-centric tools is mentioned without parity for cross-platform equivalents. However, the majority of the page is platform-neutral, focusing on Azure portal and web UI workflows.
Recommendations
  • Include examples for automated testing and CI/CD using cross-platform tools such as Bash scripts, Python, or other Linux/macOS compatible frameworks.
  • Mention and provide sample usage of Azure CLI (az) in Bash or zsh environments, not just PowerShell.
  • Highlight that NUnit and Visual Studio are Windows-centric, and suggest alternatives like pytest, xUnit, or other cross-platform testing frameworks.
  • Add explicit notes or sections for Linux/macOS users, clarifying how to perform equivalent tasks (e.g., running test pipelines, scripting deployments) on their platforms.
  • Provide links to documentation or tutorials for setting up CI/CD pipelines using GitHub Actions, Azure Pipelines, or other tools from Linux/macOS environments.
GitHub Create Pull Request
Data Factory Configure a virtual network for express injection of Azure-SSIS integration runtime ...-integration-runtime-express-virtual-network-injection.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the 'Configure a custom DNS server' section, where only Windows-centric tools and scripts (main.cmd and setupdnsserver.ps1) are referenced, with no mention of Linux/macOS alternatives. The related content also highlights Azure PowerShell as a method for joining the integration runtime to a virtual network, without referencing CLI or Bash equivalents. There are no explicit Linux/macOS instructions or examples, which may create friction for non-Windows users.
Recommendations
  • Provide Linux/macOS-compatible setup scripts (e.g., Bash or Python alternatives to setupdnsserver.ps1 and main.cmd) and document their usage.
  • Include Azure CLI examples alongside PowerShell instructions for all relevant configuration steps.
  • Explicitly state cross-platform compatibility for all downloadable scripts, or provide separate instructions for Linux/macOS users.
  • Add references to Linux/macOS tools and patterns where applicable, such as using shell scripts for custom setup.
GitHub Create Pull Request
Data Factory Configure a virtual network for standard injection of Azure-SSIS integration runtime ...integration-runtime-standard-virtual-network-injection.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a moderate Windows bias. The only provided script example is in PowerShell, with no mention of Bash, Azure CLI, or cross-platform alternatives. The NSG configuration section references Windows firewall rules, and troubleshooting steps mention RDP (a Windows protocol). The 'CorpNetSaw' service tag is described as only available via Azure PowerShell/CLI, but the only example given is PowerShell. Windows-centric terminology and tools (PowerShell, RDP, Windows firewall) are referenced before or instead of Linux/macOS equivalents.
Recommendations
  • Provide equivalent Azure CLI and/or Bash script examples alongside PowerShell, especially for UDR and NSG configuration.
  • Clarify which steps and tools are cross-platform and which are Windows-specific.
  • Where RDP or Windows firewall is mentioned, add notes or alternatives for Linux/macOS users (e.g., SSH, iptables).
  • Explicitly state platform requirements for any step that is Windows-only.
  • Add links or references to Linux/macOS documentation for Azure networking tasks.
GitHub Create Pull Request
Data Factory Troubleshoot CI-CD, Azure DevOps, and GitHub issues ...ticles/data-factory/ci-cd-github-troubleshoot-guide.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page contains several references to PowerShell and Windows-centric tooling (e.g., 'PowerShell API', 'Azure PowerShell'), but does not provide equivalent Linux/macOS examples or mention cross-platform alternatives. There are no explicit Linux shell (bash, CLI) commands or examples, and Windows tools are referenced as the default or only method for certain operations. This creates friction for users on Linux or macOS, who may need to adapt instructions or seek additional resources.
Recommendations
  • Provide equivalent examples using Azure CLI (az) and bash scripting alongside PowerShell instructions.
  • Explicitly mention cross-platform compatibility for SDKs and automation tools (e.g., .NET, Python, REST API).
  • Add notes or sections clarifying how Linux/macOS users can perform the same tasks, including installation and usage of required tools.
  • Avoid referring to Windows tools as the only or default method; present alternatives in parallel.
  • Ensure troubleshooting steps and code snippets are platform-agnostic or include both Windows and Linux/macOS variants.
GitHub Create Pull Request
Data Factory Datasets ...cles/data-factory/concepts-datasets-linked-services.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is listed as a primary tool for creating datasets, and the quickstart/tutorial links prioritize .NET and PowerShell before REST API and portal options. There are no explicit Linux or macOS CLI examples (such as Bash, Azure CLI, or Python SDK), nor is there mention of cross-platform alternatives to PowerShell. This may create friction for Linux/macOS users who do not use PowerShell or .NET.
Recommendations
  • Add Azure CLI and Python SDK examples for dataset creation, as these are cross-platform and widely used on Linux/macOS.
  • Reorder tool lists and quickstart links to present REST API, Azure CLI, and portal options before PowerShell/.NET, or group them by platform.
  • Explicitly mention that PowerShell is primarily a Windows tool and suggest alternatives for Linux/macOS users.
  • Include sample commands for dataset creation using Azure CLI and Python SDK in relevant sections.
  • Add a note clarifying cross-platform support and linking to platform-specific guides.
GitHub Create Pull Request
Data Factory Pipeline parameters and variables ...articles/data-factory/concepts-parameters-variables.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page itself is mostly platform-neutral in its main content, focusing on UI-based steps and conceptual explanations. However, the 'Related content' section exclusively links to PowerShell-based tutorials for pipeline creation and data transformation, which are strongly associated with Windows environments. There are no equivalent Bash, Azure CLI, or Linux/macOS examples or tutorials referenced, and PowerShell is presented as the default/only automation option.
Recommendations
  • Add links to tutorials using Azure CLI, Bash, or other cross-platform tools for pipeline creation and management.
  • Explicitly mention that PowerShell is one option, and provide parity for Linux/macOS users by including examples for their platforms.
  • Reorder or balance the 'Related content' section to avoid implying PowerShell is the primary or only supported method.
  • Where automation is discussed, clarify platform requirements and alternatives.
GitHub Create Pull Request
← Previous Page 32 of 40 Next →