Data Factory

1123
Total Pages
968
Linux-Friendly Pages
155
Pages with Bias
13.8%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

319 issues found
Showing 26-50 of 319 flagged pages
Data Factory Continuous integration and delivery pre- and post-deployment scripts ...ctory/continuous-integration-delivery-sample-script.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 and .ps1 scripts for CI/CD pre- and post-deployment tasks, with all examples and instructions tailored to PowerShell environments. There are no Bash, shell, or Linux/macOS-specific examples or guidance. The use of Azure PowerShell tasks and references to PowerShell Core further reinforce a Windows-centric approach, making it difficult for Linux/macOS users to follow or adapt the instructions without significant effort.
Recommendations
  • Provide equivalent Bash or shell script examples for pre- and post-deployment tasks.
  • Include instructions for running deployment scripts using Azure CLI or other cross-platform tools.
  • Add guidance on configuring Azure DevOps pipelines to execute scripts on Linux/macOS agents.
  • Explicitly state platform requirements and offer alternatives for non-Windows environments.
  • List Linux/macOS steps and examples alongside or before Windows/PowerShell instructions to improve parity.
GitHub Create Pull Request
Data Factory Create a shared self-hosted integration runtime with PowerShell ...eate-shared-self-hosted-integration-runtime-powershell.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page is heavily biased towards Windows and PowerShell. All command-line examples are provided exclusively in PowerShell, with explicit instructions to use Windows PowerShell ISE and links to Windows-specific installation guides. There are no Linux/macOS CLI examples (e.g., Bash, Azure CLI), nor any mention of how to perform these tasks on non-Windows platforms. The installer instructions and prerequisites assume a Windows environment, and Windows terminology is used first and exclusively.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI (az) and Bash for Linux/macOS users.
  • Clarify whether the self-hosted integration runtime installer is available for Linux/macOS, and provide platform-specific installation steps if so.
  • Include notes or sections on how to perform all steps (authentication, resource creation, sharing, monitoring) from Linux/macOS environments.
  • Avoid recommending Windows PowerShell ISE as the default scripting environment; suggest cross-platform alternatives like VS Code or terminal.
  • Reorder examples or provide parallel instructions so that Linux/macOS users are not forced to adapt Windows-centric steps.
GitHub Create Pull Request
Data Factory Encrypt credentials in Azure Data Factory ...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/encrypt-credentials-self-hosted-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-11 06:20
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 PowerShell cmdlets and references DPAPI, a Windows-specific encryption technology. All command examples are for PowerShell, with no mention of Linux/macOS alternatives or cross-platform compatibility. Prerequisites specify PowerShell 7.0+, but do not clarify support for non-Windows platforms. There is no guidance for Linux/macOS users on how to perform credential encryption or whether the process is supported outside Windows.
Recommendations
  • Clarify whether the credential encryption process and DPAPI are supported on Linux/macOS self-hosted integration runtime nodes.
  • Provide equivalent command-line examples for Linux/macOS environments (e.g., using Bash, Azure CLI, or cross-platform PowerShell if supported).
  • Explicitly state platform limitations or requirements at the start of the documentation.
  • If only Windows is supported, suggest alternative secure credential management approaches for Linux/macOS users.
GitHub Create Pull Request
Data Factory Install licensed components for Azure-SSIS integration runtime ...ry/how-to-develop-azure-ssis-ir-licensed-components.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation is heavily oriented towards Windows environments, referencing Windows-specific tools (Registry, environment variables, GAC, Windows file paths) and providing instructions and examples that assume a Windows OS. There are no Linux/macOS equivalents or examples, and Windows terminology and patterns are used exclusively throughout the page.
Recommendations
  • Explicitly state OS requirements and clarify if Linux/macOS are unsupported or provide guidance for those platforms.
  • If Azure-SSIS IR or self-hosted IR can run on Linux, add equivalent instructions for Linux (e.g., environment variables, file paths, component installation, GAC alternatives).
  • Provide examples for Linux/macOS where possible, or note limitations for non-Windows users.
  • Mention any cross-platform compatibility considerations for ISVs developing custom components.
GitHub Create Pull Request
Data Factory Customize the setup for an Azure-SSIS Integration Runtime ...factory/how-to-configure-azure-ssis-ir-custom-setup.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is heavily Windows-centric, with all examples, tooling, and setup instructions assuming a Windows environment. All scripts, commands, and sample setups use Windows batch files (.cmd), PowerShell, and Windows-specific utilities (msiexec.exe, cmdkey, odbcconf.exe, etc.). There are no Linux or macOS equivalents, nor any mention of how to adapt the process for non-Windows platforms. The Azure-SSIS IR itself is a Windows-based runtime, but the documentation does not clarify this upfront or offer guidance for users coming from Linux/macOS backgrounds.
Recommendations
  • Explicitly state early in the documentation that Azure-SSIS IR is a Windows-only runtime, and that all customization is performed in a Windows environment.
  • Add a section for Linux/macOS users explaining the limitations and alternatives, such as using Azure Data Factory Mapping Data Flows or other cross-platform ETL tools.
  • Where possible, provide guidance on how Linux/macOS users can prepare setup scripts (e.g., using PowerShell Core on macOS/Linux, or preparing files on Windows VMs).
  • Clarify that tools like Azure Storage Explorer and Azure PowerShell are available cross-platform, but that custom setup scripts must be Windows-compatible.
  • Add a FAQ or troubleshooting section for non-Windows users, outlining what is and is not possible.
GitHub Create Pull Request
Data Factory Execute SQL Server Integration Services (SSIS) packages with the Azure-enabled dtexec utility ...ory/how-to-invoke-ssis-package-azure-enabled-dtexec.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First Powershell Heavy
Summary
The documentation is heavily Windows-centric, requiring SQL Server Management Studio (SSMS)—a Windows-only tool—to install and configure AzureDTExec. All examples use Windows paths and command prompts, with no mention of Linux/macOS alternatives or installation methods. There is no guidance for non-Windows users, making it difficult or impossible for them to follow the instructions.
Recommendations
  • Clarify whether AzureDTExec is available for Linux/macOS, and if not, state this explicitly.
  • If possible, provide cross-platform alternatives or guidance for running SSIS packages from Linux/macOS (e.g., via Azure Data Factory REST API, Azure CLI, or other supported tools).
  • Include Linux/macOS-specific installation and usage instructions if AzureDTExec or equivalent functionality is available.
  • Add examples using Linux shell commands and file paths, or note platform limitations.
  • Mention any workarounds for non-Windows users, such as using remote Windows VMs or containers.
GitHub Create Pull Request
Data Factory Create a self-hosted integration runtime ...des/data-factory-create-install-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides PowerShell commands for all CLI operations and references only Windows-specific installation and configuration steps. The integration runtime tool is described as downloadable and installable only on Windows, with no mention of Linux or macOS alternatives or instructions. All examples and screenshots are Windows-centric, and there are no cross-platform considerations.
Recommendations
  • Provide equivalent CLI examples using Bash or Azure CLI for Linux/macOS users.
  • Clarify whether the self-hosted integration runtime can be installed on Linux/macOS, and if so, provide installation and registration instructions for those platforms.
  • If the tool is Windows-only, explicitly state this limitation early in the documentation.
  • Include notes or links to cross-platform alternatives if available.
  • Reorder examples to present cross-platform options first or side-by-side, rather than Windows-first.
GitHub Create Pull Request
Data Factory Monitor integration runtime in Azure Data Factory ...n/articles/data-factory/monitor-integration-runtime.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell examples and cmdlets for monitoring integration runtimes in Azure Data Factory. All command-line instructions use PowerShell syntax, with no mention of Linux/macOS-compatible alternatives (such as Azure CLI, REST API, or Bash). The self-hosted integration runtime is described as being installed on 'on-premises Windows machines,' and there is no guidance for Linux-based nodes or cross-platform deployment. Windows tools and patterns (PowerShell, SSMS, SSDT) are referenced throughout, with no Linux/macOS equivalents or parity.
Recommendations
  • Add equivalent Azure CLI and REST API examples for all monitoring tasks, with explicit syntax for Linux/macOS terminals.
  • Clarify whether self-hosted integration runtime can be installed on Linux nodes and, if so, provide instructions and examples.
  • Include references to cross-platform tools (e.g., Azure Data Studio, VS Code) alongside Windows-only tools like SSMS and SSDT.
  • Reorder examples so that cross-platform options (CLI, REST) appear before or alongside PowerShell.
  • Explicitly state platform requirements and limitations for each integration runtime type.
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
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page consistently references PowerShell-based tutorials for incremental data copy tasks, with all step-by-step guides linked to PowerShell scripts or Windows-centric tooling. There are no examples or instructions for Linux/macOS users, nor are cross-platform alternatives (such as Azure CLI, REST API, or Python SDK) mentioned. Windows/PowerShell tools are presented as the default and only option, creating friction for users on other platforms.
Recommendations
  • Provide equivalent step-by-step tutorials using Azure CLI, REST API, or Python SDK, which are cross-platform.
  • Explicitly mention platform compatibility for each method and link to Linux/macOS-friendly instructions.
  • Add examples and templates for Linux/macOS users, ensuring parity in guidance and tooling.
  • Reorder or balance examples so that Windows and Linux/macOS approaches are presented equally.
GitHub Create Pull Request
Data Factory Set up a self-hosted integration runtime for the SAP CDC connector ...ta-factory/sap-change-data-capture-shir-preparation.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is strongly Windows-centric: all examples (PowerShell, hosts file editing) use Windows paths and tools, and only Windows installation steps are described. There are no Linux/macOS equivalents or guidance, and the SAP .NET Connector is Windows-only. This creates significant friction for non-Windows users.
Recommendations
  • Explicitly state platform requirements and limitations at the top of the page (e.g., 'Windows-only').
  • If Linux/macOS are supported, provide equivalent instructions for those platforms (e.g., using 'nc' or 'telnet' for connectivity tests, editing '/etc/hosts').
  • Clarify whether the self-hosted integration runtime and SAP .NET Connector can be installed on Linux/macOS, and provide alternatives if possible.
  • If Windows is required, recommend using a Windows VM for non-Windows users and provide setup guidance.
GitHub Create Pull Request
Data Factory Self-hosted integration runtime diagnostic tool ...ory/self-hosted-integration-runtime-diagnostic-tool.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively references Windows tools and workflows, such as the use of Configuration Manager and the dmgcmd.exe command-line tool, with no mention of Linux or macOS equivalents. All screenshots and instructions are Windows-centric, and there are no examples or guidance for running the diagnostic tool on non-Windows platforms.
Recommendations
  • Clarify whether the diagnostic tool is available for Linux/macOS or is Windows-only.
  • If Linux/macOS support exists, provide equivalent installation and usage instructions, including command-line examples for those platforms.
  • Include screenshots or descriptions of the diagnostic process on Linux/macOS, if applicable.
  • Explicitly state platform requirements and limitations at the beginning of the documentation.
GitHub Create Pull Request
Data Factory Transform data using Hive in Azure Virtual Network ...actory/tutorial-transform-data-hive-virtual-network.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell. All command-line examples use Azure PowerShell, with no mention of Azure CLI, Bash, or Linux/macOS workflows. Instructions for editing the hosts file explicitly reference the Windows path (C:\Windows\System32\drivers\etc), and the self-hosted integration runtime registration steps assume a Windows VM. There are no Linux/macOS equivalents or alternative instructions provided.
Recommendations
  • Add Azure CLI and Bash examples alongside PowerShell for all resource creation and management steps.
  • Provide instructions for editing the hosts file on Linux/macOS (e.g., /etc/hosts), not just Windows.
  • Clarify that the self-hosted integration runtime can be installed on Linux and provide installation steps for Linux VMs.
  • Explicitly state platform requirements and offer parity for Linux/macOS users throughout the tutorial.
  • Where screenshots or file paths are shown, include Linux/macOS equivalents.
GitHub Create Pull Request
Data Factory Enable remote access from intranet with TLS/SSL certificate (Advanced) ...rial-enable-remote-access-intranet-tls-ssl-certificate.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows environments, with all command-line examples provided in PowerShell, certificate management instructions referencing Windows-specific tools (MMC snap-in, cert store locations), and screenshots of Windows UI dialogs. There are no Linux or macOS equivalents or instructions, making it difficult or impossible for non-Windows users to follow the tutorial.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell commands (e.g., using openssl, hostname, etc.).
  • Include instructions for certificate installation and management using Linux tools (e.g., update-ca-certificates, keytool, or manual placement in /etc/ssl/certs).
  • Add troubleshooting steps relevant to Linux/macOS environments.
  • Clarify platform requirements and limitations at the start of the documentation.
  • If the integration runtime is Windows-only, state this explicitly; if cross-platform, ensure parity in examples and instructions.
GitHub Create Pull Request
Data Factory Copy data from SQL Server to Blob storage using PowerShell ...ticles/data-factory/tutorial-hybrid-copy-powershell.md
High Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
This documentation is heavily biased towards Windows and PowerShell. All command-line examples use PowerShell, and the installation and usage of the self-hosted integration runtime is described exclusively for Windows. There are no instructions or examples for Linux or macOS users, nor any mention of cross-platform alternatives. Windows tools (SQL Server Management Studio, PowerShell, Windows authentication) are referenced throughout, and Linux equivalents are absent.
Recommendations
  • Provide equivalent instructions and examples for Linux and macOS users, including Bash/Azure CLI commands.
  • Clarify whether the self-hosted integration runtime can be installed on Linux/macOS, and if so, provide installation steps.
  • Include guidance for using cross-platform SQL clients (e.g., Azure Data Studio, sqlcmd) for database setup.
  • List prerequisites and steps for Linux/macOS environments, including file path conventions and authentication differences.
  • If PowerShell is required, note how to install PowerShell Core on Linux/macOS and verify compatibility.
  • Explicitly state platform limitations if certain components are Windows-only, and suggest alternatives where possible.
GitHub Create Pull Request
Data Factory Applying DataOps ...-docs/blob/main/articles/data-factory/apply-dataops.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (PowerShell, Visual Studio, .NET/NUnit) for automated testing and CI/CD, and by providing examples and recommendations that assume a Windows development environment. Linux alternatives (such as Bash, shell scripts, or Linux-native CI/CD tools) are not mentioned, and Windows tools are referenced before any cross-platform or Linux options. There are no explicit Linux or macOS examples, and the documentation does not address how to perform equivalent tasks on non-Windows platforms.
Recommendations
  • Include examples using Bash, shell scripts, and Linux-native tools for CI/CD and automated testing.
  • Mention cross-platform alternatives to PowerShell, such as Azure CLI or REST API calls via curl.
  • Provide guidance for setting up automated testing environments using Python (pytest), JavaScript (Jest), or other cross-platform frameworks.
  • Add explicit instructions and screenshots for performing key steps on Linux and macOS, not just Windows.
  • Reference and link to documentation for Azure Data Factory usage from Linux environments, including deployment and testing.
  • Clarify that Azure CLI and REST API methods work on all platforms and provide sample commands for Linux/macOS.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/apply-dataops.md ...-docs/blob/main/articles/data-factory/apply-dataops.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. Examples and recommendations for CI/CD, automated testing, and deployment frequently reference PowerShell, Visual Studio, and .NET (NUnit), with no mention of Linux alternatives or cross-platform tools. The use of Azure DevOps and GitHub is described, but the examples and external references (e.g., automated testing) focus on Windows environments and tools, omitting Linux command-line equivalents or open-source alternatives. There are no Bash, Linux shell, or cross-platform scripting examples, and PowerShell is mentioned as a primary automation tool.
Recommendations
  • Include Linux/Bash shell examples for CI/CD and deployment tasks alongside PowerShell examples.
  • Mention and provide examples for running automated tests using cross-platform frameworks (e.g., pytest for Python, or JavaScript test runners) in addition to NUnit/Visual Studio.
  • Reference Azure CLI usage from Linux/macOS terminals, not just PowerShell, for pipeline management and deployment.
  • Highlight cross-platform editors (e.g., VS Code) and workflows, and clarify that Azure Data Factory and its tools can be used from Linux environments.
  • Add explicit notes or sections on how to perform key tasks (deployment, testing, artifact management) from Linux systems, including sample scripts.
  • Balance tool recommendations by listing both Windows and Linux-friendly options for automation and scripting.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/author-global-parameters.md ...main/articles/data-factory/author-global-parameters.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation references PowerShell as the deployment method for global parameters in CI/CD, without mentioning or providing equivalent examples for Linux or cross-platform tools (e.g., Azure CLI, Bash). Windows tooling is implicitly favored, and there are no Linux-specific instructions or parity examples.
Recommendations
  • Add equivalent deployment instructions using Azure CLI, which is cross-platform and works on Linux, macOS, and Windows.
  • Provide Bash script examples for deploying global parameters via ARM templates.
  • Explicitly mention that PowerShell is one option and link to cross-platform alternatives.
  • Clarify that ARM template deployment can be performed from any OS, and provide steps for Linux users.
  • Ensure screenshots and UI instructions do not assume a Windows environment.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/azure-ssis-integration-runtime-package-store.md ...actory/azure-ssis-integration-runtime-package-store.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows environments. All examples and instructions assume the use of Windows-only tools such as SQL Server Management Studio (SSMS), dtutil, and Windows command-line utilities (cmdkey, net use, batch scripts). There are no examples or guidance for performing equivalent tasks on Linux or macOS, nor is there any mention of cross-platform alternatives. The documentation also introduces Windows tools and patterns first and exclusively, with no Linux parity.
Recommendations
  • Provide equivalent instructions and examples for Linux environments, including how to interact with Azure-SSIS IR using cross-platform tools or Azure CLI.
  • Mention and demonstrate how to use Azure Data Factory portal or REST APIs for package management tasks as an alternative to SSMS.
  • If dtutil is required, clarify whether it can be run via Wine or in a container on Linux, or suggest alternative methods for Linux users.
  • Include notes or sections explicitly stating the platform limitations and suggest workarounds for non-Windows users.
  • Where possible, use cross-platform scripting languages (e.g., Python, PowerShell Core) or Azure CLI for automation examples.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/built-in-preinstalled-components-ssis-integration-runtime.md ...lt-in-preinstalled-components-ssis-integration-runtime.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily Windows-centric: it specifies Windows Server 2019 as the only OS, lists only Windows-based drivers and providers, and all built-in/preinstalled components are for Windows SSIS. There is no mention of Linux support, Linux equivalents, or cross-platform alternatives. No examples, tools, or instructions for Linux environments are provided.
Recommendations
  • Explicitly state whether Linux is supported or not for Azure-SSIS IR, and if not, provide guidance or alternatives for Linux users.
  • If Linux support is planned or available, add equivalent lists for Linux-based components, drivers, and connection managers.
  • Provide examples or documentation for deploying SSIS workloads in Linux containers or using cross-platform ETL tools.
  • Reference open-source or cross-platform alternatives where possible, and clarify any Windows-only limitations.
  • Consider adding a comparison table showing feature parity (or gaps) between Windows and Linux environments for Azure Data Factory.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-linked-services.md ...main/articles/data-factory/concepts-linked-services.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell as the only command-line scripting example and referencing it before other cross-platform or Linux-native tools. There are no explicit Linux shell (Bash/CLI) examples or references, and the quickstart/tutorial links prioritize .NET and PowerShell (both Windows-centric) before REST API or portal options. No Linux-specific tools, patterns, or examples are provided.
Recommendations
  • Add examples and quickstart links for Azure CLI (which is cross-platform and commonly used on Linux) alongside or before PowerShell.
  • Include Bash shell script examples for creating linked services, especially using the Azure CLI.
  • Ensure that REST API and portal-based instructions are presented before or alongside Windows-centric tools like PowerShell.
  • Explicitly mention Linux and macOS compatibility in tool/SDK lists and provide parity in walkthroughs.
  • Where PowerShell is referenced, also provide equivalent Azure CLI or Bash commands.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/concepts-datasets-linked-services.md ...cles/data-factory/concepts-datasets-linked-services.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by listing PowerShell as a primary tool for creating datasets, referencing PowerShell-based quickstarts and guides, and omitting Linux-specific tools or CLI examples. There are no Bash, Azure CLI, or cross-platform scripting examples, and PowerShell is mentioned before REST API or portal options. This may make Linux users feel unsupported or require extra effort to adapt instructions.
Recommendations
  • Add Azure CLI examples for creating datasets, as Azure CLI is cross-platform and widely used on Linux.
  • Include Bash shell script examples where appropriate, especially for tasks currently shown only with PowerShell.
  • Reorder tool and quickstart lists to present cross-platform or OS-neutral options (e.g., REST API, Azure CLI, portal) before Windows-specific tools like PowerShell.
  • Explicitly mention that PowerShell examples are Windows-centric and provide equivalent Linux commands or scripts.
  • Add a section or links for Linux/macOS users, highlighting supported tools and any differences in workflow.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/configure-azure-ssis-integration-runtime-performance.md ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/configure-azure-ssis-integration-runtime-performance.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based configuration examples and scripts, with no equivalent examples for Linux environments (e.g., Bash, Azure CLI). It references Windows-centric tools and patterns, such as PowerShell and Windows authentication methods, without mentioning or prioritizing cross-platform alternatives. There is no guidance for users operating from Linux or macOS environments.
Recommendations
  • Provide equivalent Azure CLI or Bash script examples for all PowerShell scripts to support Linux and macOS users.
  • Explicitly mention that configuration can be performed from non-Windows platforms and provide links or references to relevant cross-platform tools.
  • Add a section or callout discussing cross-platform support and any platform-specific considerations.
  • Where authentication is discussed, clarify options for both Windows (SQL authentication) and cross-platform (Azure AD/Entra ID) scenarios.
  • Ensure that any references to tools or commands (e.g., PowerShell) are accompanied by their cross-platform equivalents.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-amazon-redshift.md ...ain/articles/data-factory/connector-amazon-redshift.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by referencing only Windows-supported versions for the Self-hosted Integration Runtime, not mentioning Linux support or providing Linux installation/configuration instructions. All examples and prerequisites assume a Windows environment, and there are no Linux-specific examples or parity guidance. The documentation also refers to Windows support before any mention of cross-platform or Linux compatibility.
Recommendations
  • Explicitly state whether the Self-hosted Integration Runtime supports Linux, and if so, provide installation and configuration instructions for Linux environments.
  • Add Linux-specific examples or notes where relevant, such as how to configure network access, run the integration runtime, or handle permissions on Linux.
  • If Linux is not supported, clearly mention this limitation early in the documentation.
  • Ensure that any references to supported operating systems (such as in the prerequisites) mention both Windows and Linux (if applicable), or clarify the scope.
  • Provide troubleshooting tips or links for Linux users, if supported.
  • Review and update language to avoid Windows-first phrasing, and ensure parity in tool and workflow descriptions.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-azure-search.md ...b/main/articles/data-factory/connector-azure-search.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows by exclusively using Azure Portal UI screenshots and workflows, which are primarily Windows-centric. There are no examples or instructions for performing the same tasks using cross-platform tools (such as Azure CLI, REST API, or ARM templates), nor is there mention of Linux-specific workflows or command-line alternatives. The documentation assumes use of the Azure Portal, which is more familiar to Windows users, and does not provide parity for Linux users who may prefer scripting or non-GUI approaches.
Recommendations
  • Add examples for creating and configuring linked services, datasets, and copy activities using Azure CLI, PowerShell (with clear cross-platform notes), and REST API.
  • Include sample scripts or commands that can be run on Linux/macOS terminals, not just through the Azure Portal UI.
  • Mention and link to documentation for ARM/Bicep templates for users who prefer infrastructure-as-code approaches.
  • Clearly indicate which steps are platform-agnostic and which are specific to the Azure Portal, and provide alternatives where possible.
  • Ensure that any screenshots or UI walkthroughs are supplemented with equivalent command-line or code-based examples.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-azure-table-storage.md ...articles/data-factory/connector-azure-table-storage.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a Windows bias by providing only PowerShell commands for generating a Shared Access Signature (SAS) token, with no equivalent examples for Linux (e.g., Azure CLI, Bash, or cross-platform tools). Windows/PowerShell tooling is mentioned exclusively for a key authentication step, and no Linux or cross-platform alternatives are referenced or prioritized. This may hinder Linux users or those working in cross-platform environments.
Recommendations
  • Add equivalent Azure CLI examples for generating SAS tokens, as Azure CLI is cross-platform and widely used on Linux.
  • Explicitly mention cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell, and provide usage examples.
  • When referencing command-line tools, present cross-platform options first or in parallel with Windows-specific tools.
  • Review the documentation for other areas where only Windows/PowerShell tools are mentioned and ensure Linux parity.
  • Consider including a note or section on how to perform key tasks (like SAS generation) on Linux/macOS environments.
GitHub Create Pull Request
← Previous Page 2 of 13 Next →