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 826-850 of 1000 flagged pages
Data Factory Copy or clone a data factory in Azure Data Factory .../main/articles/data-factory/copy-clone-data-factory.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references a PowerShell-based pattern for sharing SelfHosted Integration Runtime, but does not mention or provide equivalent guidance for Linux/macOS users. There are no explicit Linux or cross-platform CLI examples, and the only external tool referenced is PowerShell.
Recommendations
  • Provide equivalent instructions for sharing SelfHosted Integration Runtime using Azure CLI or REST API, which are cross-platform.
  • Explicitly mention that PowerShell scripts can be run on Linux/macOS via PowerShell Core, or provide alternative scripts/examples for bash.
  • Add notes or links to Linux/macOS-compatible tooling where PowerShell is referenced.
  • Ensure that all referenced patterns (such as the linked PowerShell guide) have Linux/macOS equivalents or alternatives.
GitHub Create Pull Request
Data Factory Create Azure integration runtime ...icles/data-factory/create-azure-integration-runtime.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 explicit instructions for creating Azure Integration Runtime using Azure PowerShell, which is primarily a Windows-centric tool. There are no examples or guidance for Linux/macOS users, such as using Azure CLI, Bash, or REST API. The only command-line example is PowerShell, and no Linux-native alternatives are mentioned or shown.
Recommendations
  • Add equivalent Azure CLI commands for creating and configuring Azure Integration Runtime, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API examples for users who prefer scripting or automation outside of PowerShell.
  • Clearly state platform compatibility for each method (e.g., PowerShell is available on Linux, but CLI is more common).
  • Present command-line examples for both Windows and Linux/macOS users side-by-side or in tabs.
  • Mention that the Azure Portal UI is platform-agnostic, but clarify any limitations for command-line tools.
GitHub Create Pull Request
Data Factory Create a shared self-hosted integration runtime with PowerShell ...eate-shared-self-hosted-integration-runtime-powershell.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 Windows First Missing Linux Example
Summary
The documentation page is heavily biased towards Windows and PowerShell. All command-line examples use Azure PowerShell, and instructions explicitly reference launching Windows PowerShell ISE. There is no mention of Bash, Azure CLI, or Linux/macOS equivalents for any steps. The installer instructions do not clarify cross-platform support, and the prerequisites link only to Windows installation instructions for Azure PowerShell.
Recommendations
  • Provide equivalent instructions and examples using Azure CLI, which is cross-platform and works on Linux/macOS.
  • Clarify whether the self-hosted integration runtime installer supports Linux/macOS, and provide platform-specific installation steps if available.
  • Avoid referencing Windows-specific tools like PowerShell ISE; use generic terminal instructions or note alternatives for Linux/macOS.
  • Include notes or links for installing Azure PowerShell on Linux/macOS if PowerShell is required.
  • Present cross-platform options first or side-by-side, rather than Windows-first.
GitHub Create Pull Request
Data Factory Using credentials ...re-docs/blob/main/articles/data-factory/credentials.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools (Azure portal, PowerShell) and providing screenshots of GUI workflows that are only available on Windows. While it mentions SDK and REST API as alternatives, there are no explicit Linux/macOS command-line examples (e.g., Azure CLI, Bash scripts), nor are Linux-friendly workflows shown or prioritized. PowerShell is listed as a scripting option, but Azure CLI is not mentioned at all.
Recommendations
  • Add explicit Azure CLI examples for all major steps (creating managed identities, assigning them, configuring credentials, etc.), as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include screenshots or instructions for using browser-based Azure portal on non-Windows platforms, or clarify that the portal is platform-agnostic.
  • Provide Bash script examples for REST API usage, demonstrating how Linux/macOS users can automate these tasks.
  • List Azure CLI before or alongside PowerShell in all references to scripting/automation tools.
  • Clearly state that all steps can be performed on Linux/macOS using CLI or REST API, and link to relevant cross-platform documentation.
GitHub Create Pull Request
Data Factory Create an Azure-SSIS integration runtime via Azure portal ...actory/create-azure-ssis-integration-runtime-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally platform-neutral, focusing on Azure portal UI workflows for creating Azure-SSIS integration runtimes. However, there are subtle signs of Windows bias: references to legacy SSIS package stores (historically Windows-centric), UNC paths for file system access (Windows format), and links to related content about connecting to on-premises data stores with Windows authentication. Additionally, the only explicit scripting example referenced is via Azure PowerShell, a tool most commonly used on Windows, and the file system examples use UNC paths rather than Linux/macOS equivalents.
Recommendations
  • Add explicit examples for Linux/macOS users, such as using Azure CLI or Bash scripts for automation, alongside PowerShell.
  • Clarify that UNC paths are Windows-specific and provide guidance for Linux/macOS file share mounting (e.g., SMB/CIFS commands).
  • Include references to cross-platform tools (e.g., Azure CLI) in 'Related content' and throughout the documentation.
  • Where authentication or integration methods are discussed, mention Linux/macOS alternatives or note platform limitations.
  • Ensure screenshots and UI instructions do not assume a Windows environment (e.g., file path formats, authentication dialogs).
GitHub Create Pull Request
Data Factory Azure Private Link for Azure Data Factory ...ain/articles/data-factory/data-factory-private-link.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for creating a virtual machine to host the self-hosted integration runtime (IR), but only Windows Server images are mentioned and shown in the examples. There are no references to Linux-based images or instructions for deploying the self-hosted IR on Linux VMs, even though Azure supports Linux VMs and some Data Factory components may be usable on Linux. This creates a bias toward Windows environments and may cause confusion or extra work for Linux users.
Recommendations
  • Add explicit instructions and examples for deploying the self-hosted IR on Linux virtual machines, including supported distributions and prerequisites.
  • Mention Linux VM images as alternatives to Windows Server in the VM creation steps.
  • Clarify any platform-specific limitations or requirements for the self-hosted IR (e.g., if only Windows is supported, state this clearly at the start).
  • Provide parity in screenshots and step-by-step guides for both Windows and Linux environments.
GitHub Create Pull Request
Data Factory Managed identity ...articles/data-factory/data-factory-service-identity.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 the only CLI tool shown in code examples for generating and retrieving managed identities, with no Bash, Azure CLI, or cross-platform shell alternatives. PowerShell commands are presented before REST API, ARM template, and SDK examples, and there are no Linux/macOS-specific instructions or parity notes. This may create friction for users on non-Windows platforms who do not use PowerShell.
Recommendations
  • Add equivalent Azure CLI (az) examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Provide Bash shell script samples for REST API calls, using curl, to illustrate how Linux/macOS users can perform the same operations.
  • Clarify that PowerShell examples are for Windows and recommend Azure CLI for Linux/macOS users.
  • Reorder examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside PowerShell.
  • Explicitly mention Linux/macOS compatibility and provide troubleshooting tips for those environments.
GitHub Create Pull Request
Data Factory include file ...tory/includes/data-factory-quickstart-prerequisites.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns, such as Notepad and the C:\ADFv2QuickStartPSH folder, without providing equivalent instructions for Linux or macOS users. There are no examples or guidance for creating files or folders on non-Windows platforms.
Recommendations
  • Include instructions for creating the emp.txt file using common Linux/macOS text editors (e.g., nano, vim, TextEdit).
  • Provide example file paths for Linux/macOS (e.g., /home/user/ADFv2QuickStart or ~/ADFv2QuickStart).
  • Clarify that the Azure portal steps are cross-platform and that local file creation can be performed on any OS.
  • Add a note or section explicitly addressing Linux/macOS users to ensure parity.
GitHub Create Pull Request
Data Factory General Troubleshooting ...ticles/data-factory/data-factory-troubleshoot-guide.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation is generally cross-platform, but there are notable instances of Windows bias. Specifically, troubleshooting steps for Azure Batch custom activities (Error codes 2504 and 2508) provide only PowerShell-based unzip examples, with no Linux/macOS alternatives. Additionally, the 'Unsupported compression causes files to be corrupted' section discusses Windows zip behavior and tools, without mentioning Linux equivalents or how to avoid the issue on non-Windows platforms. The use of Fiddler for network troubleshooting is also Windows-centric, with no mention of alternatives like tcpdump or Wireshark CLI for Linux/macOS.
Recommendations
  • For all PowerShell-based examples (e.g., unzipping files in Azure Batch), add equivalent bash/sh examples using unzip or tar for Linux/macOS users.
  • In sections discussing zip compression, clarify how Linux/macOS users can create compatible zip files (e.g., using 'zip -Z deflate').
  • When recommending network troubleshooting tools, mention cross-platform options such as tcpdump, Wireshark CLI, or curl for Linux/macOS.
  • Explicitly state platform requirements or limitations where Windows-only tools are referenced, and provide alternatives where possible.
GitHub Create Pull Request
Data Factory Migrate data from Amazon S3 to Azure Storage ...ta-factory/data-migration-guidance-s3-azure-storage.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a notable Windows bias in its guidance for deploying self-hosted Integration Runtime (IR) for private network migrations. It exclusively instructs users to install the IR on Azure Windows VMs, with no mention of Linux VM support or examples. All configuration and scaling recommendations are tailored to Windows environments, potentially excluding Linux users or creating friction for those preferring Linux-based infrastructure.
Recommendations
  • Explicitly state whether self-hosted Integration Runtime supports Linux VMs. If supported, provide equivalent instructions and recommendations for deploying IR on Linux (e.g., recommended VM sizes, monitoring guidance).
  • Include Linux-specific examples and configuration steps alongside Windows instructions.
  • If Linux is not supported, clarify this limitation early in the documentation and link to roadmap or alternatives.
  • Where possible, use OS-neutral language and tools, or provide parity in examples and best practices.
GitHub Create Pull Request
Data Factory Encrypt Azure Data Factory with customer-managed key ...n/articles/data-factory/enable-customer-managed-key.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references PowerShell and Azure CLI for enabling Key Vault properties, but PowerShell is mentioned first and more prominently. There are no explicit Linux/macOS command-line examples, nor are there instructions tailored for non-Windows environments. The screenshots and UI instructions are all based on the Azure portal, which is cross-platform, but command-line guidance leans toward Windows tools and patterns.
Recommendations
  • Provide explicit Linux/macOS examples for Azure CLI commands, including shell syntax and installation notes.
  • List Azure CLI instructions before or alongside PowerShell, clarifying cross-platform compatibility.
  • Include notes or links for Linux users on how to install and use Azure CLI and interact with Azure Key Vault.
  • Avoid assuming PowerShell as the default scripting environment; mention Bash or other shells where appropriate.
GitHub Create Pull Request
Data Factory Mapping data flow script ...cs/blob/main/articles/data-factory/data-flow-script.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 shows a moderate Windows bias. It references PowerShell as the primary method for programmatically generating and submitting Data Flow Scripts outside the UI, without mentioning Linux/macOS alternatives (such as Bash, Azure CLI, or REST API usage). The only external automation example is PowerShell, and Windows tooling is mentioned before any cross-platform options. There are no explicit Linux/macOS examples or guidance.
Recommendations
  • Add examples for generating and submitting Data Flow Scripts using Azure CLI and REST API, which are cross-platform.
  • Explicitly mention that PowerShell is available on Linux/macOS and provide Bash or shell script equivalents.
  • Reorder references so that cross-platform tools (Azure CLI, REST API) are mentioned before or alongside PowerShell.
  • Include notes or examples for Linux/macOS users on how to format and submit scripts.
GitHub Create Pull Request
Data Factory Migrate data from an on-premises Hadoop cluster to Azure Storage ...-factory/data-migration-guidance-hdfs-azure-storage.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias, especially in its implementation and architecture sections. It repeatedly specifies that the Data Factory self-hosted integration runtime must be installed on a Windows machine or Windows VM, with no mention of Linux support or alternatives. All example configurations and recommendations (e.g., VM sizing, scaling) are Windows-centric. There are no Linux/macOS installation instructions, nor is there any indication that the integration runtime can run on non-Windows platforms. This creates friction for users operating in Linux environments, which are common for Hadoop clusters.
Recommendations
  • Explicitly state whether the Data Factory self-hosted integration runtime supports Linux/macOS, and if so, provide installation and configuration instructions for those platforms.
  • If Linux is not supported, clarify this limitation early in the documentation and suggest possible workarounds or alternatives for Linux users.
  • Provide example architectures and best practices for Linux-based environments, especially since Hadoop clusters are often Linux-based.
  • Include parity in VM sizing recommendations for Linux VMs if supported.
  • Add troubleshooting and operational guidance for Linux/macOS users.
GitHub Create Pull Request
Data Factory Security considerations .../data-factory/data-movement-security-considerations.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 Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias in its coverage of hybrid/on-premises scenarios. It exclusively references Windows-specific technologies such as PowerShell cmdlets (Set-AzDataFactoryV2LinkedService, New-AzDataFactoryV2LinkedServiceEncryptedCredential), Windows DPAPI for credential encryption, and Windows Firewall for local firewall configuration. There are no examples or guidance for Linux/macOS environments, such as alternative credential encryption methods, firewall configuration, or command-line tooling. The documentation assumes the self-hosted integration runtime is installed on Windows, with no mention of Linux support or parity.
Recommendations
  • Provide equivalent Linux/macOS instructions for installing and configuring the self-hosted integration runtime, including credential encryption and storage.
  • Include examples using Linux command-line tools (e.g., bash, openssl) for credential management and encryption.
  • Document Linux firewall configuration (e.g., iptables, firewalld) alongside Windows Firewall.
  • Clarify whether the self-hosted integration runtime supports Linux, and if so, detail any differences in setup, encryption, and port management.
  • Offer cross-platform PowerShell alternatives (e.g., Azure CLI, REST API) for credential management and runtime configuration.
GitHub Create Pull Request
Data Factory Enable Microsoft Entra authentication for Azure SSIS integration runtime ...ata-factory/enable-aad-authentication-azure-ssis-ir.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 page demonstrates a notable Windows bias. All command-line examples use PowerShell, with no Bash, Azure CLI, or cross-platform alternatives. The instructions for database configuration rely exclusively on SQL Server Management Studio (SSMS), a Windows-only tool, with no mention of Azure Data Studio or other cross-platform clients. Steps for provisioning and managing resources are presented with Windows-centric tools first and exclusively, leaving Linux/macOS users without direct guidance.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for all PowerShell commands, especially for group and managed identity management.
  • Include instructions for using Azure Data Studio or other cross-platform SQL clients to perform database configuration tasks instead of only SSMS.
  • Explicitly state which steps can be performed via the Azure portal, and provide screenshots or guidance for non-Windows users.
  • Add a section or notes on Linux/macOS compatibility and alternatives for each major step.
  • Reorder examples or provide parallel instructions so that Windows and Linux/macOS users are equally supported.
GitHub Create Pull Request
Data Factory Assess your Azure Data Factory pipelines for migration to Fabric ...ur-azure-data-factory-to-fabric-data-factory-migration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation repeatedly references the PowerShell upgrade module/tool as the primary method for migration, without mentioning Linux/macOS alternatives (such as Azure CLI, Bash scripts, or cross-platform tools). No Linux/macOS-specific instructions or examples are provided, and PowerShell is presented as the default solution for early migration.
Recommendations
  • Add instructions and examples for using Azure CLI or REST API for migration, which are cross-platform.
  • Explicitly state whether the PowerShell upgrade module can be used on Linux/macOS (via PowerShell Core), and provide installation guidance if so.
  • If PowerShell is required, clarify cross-platform compatibility and provide alternative methods for users who prefer Bash or other Linux-native tools.
  • Present migration tool options in a neutral order (not Windows-first), and highlight parity for Linux/macOS users.
GitHub Create Pull Request
Data Factory How to clean up SSISDB logs automatically ...ctory/how-to-clean-up-ssisdb-logs-with-elastic-jobs.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing SQL Server Management Studio (SSMS), a Windows-only tool, for configuring SSISDB log clean-up properties and managing jobs. All GUI instructions are given for SSMS, with no mention of cross-platform alternatives (e.g., Azure Data Studio, command-line tools). The order of presentation puts SSMS/Windows-centric workflows first, and there are no examples or guidance for Linux/macOS users to perform equivalent tasks (such as using Azure Data Studio, sqlcmd, or REST APIs).
Recommendations
  • Add instructions for configuring SSISDB log clean-up properties using Azure Data Studio, which is cross-platform.
  • Provide examples for using sqlcmd or Azure CLI to invoke SSISDB stored procedures from Linux/macOS.
  • Mention REST API or portal-based alternatives for tasks currently described only with SSMS.
  • Clearly indicate which steps require SSMS and suggest alternatives for non-Windows environments.
  • Reorder sections or provide parallel examples so Linux/macOS users do not need to infer their own solutions.
GitHub Create Pull Request
Data Factory Provision Enterprise Edition for the Azure-SSIS Integration Runtime ...y/how-to-configure-azure-ssis-ir-enterprise-edition.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 provides only Windows/PowerShell instructions and examples for provisioning the Azure-SSIS IR Enterprise Edition. There is no mention of Linux/macOS alternatives or cross-platform CLI tools, and the use of PowerShell is assumed throughout. Windows authentication is referenced for SSAS connectivity, further reinforcing Windows-centric patterns.
Recommendations
  • Add equivalent instructions using Azure CLI, which is cross-platform and works on Linux/macOS.
  • Explicitly state platform requirements and alternatives for non-Windows users.
  • Provide examples for authentication and provisioning that do not rely solely on Windows tools.
  • Clarify whether any steps (such as installing drivers or connectors) have platform-specific limitations.
GitHub Create Pull Request
Data Factory Create tumbling window triggers .../data-factory/how-to-create-tumbling-window-trigger.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 exhibits a moderate Windows bias, especially in the Azure PowerShell section. The PowerShell sample assumes Windows usage (e.g., file paths like C:\ADFv2QuickStartPSH\), and the PowerShell installation instructions specifically reference Windows. The PowerShell example is presented before the Azure CLI example, and there is no mention of Linux/macOS-specific considerations (e.g., file path formats, shell differences, or installation instructions for Azure PowerShell on non-Windows platforms).
Recommendations
  • Add explicit instructions for running Azure PowerShell on Linux/macOS, including installation links and notes about cross-platform compatibility.
  • Use platform-neutral file paths in examples (e.g., ./MyTrigger.json or ~/ADFv2QuickStartPSH/MyTrigger.json), or provide both Windows and Linux/macOS path examples.
  • Clarify that Azure CLI is fully cross-platform and highlight its use for Linux/macOS users.
  • Present CLI and PowerShell examples in parallel, or alternate the order to avoid Windows-first bias.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, shell differences).
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
Medium Priority View Details →
Scanned: 2026-01-13 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 is heavily Windows-centric, with all examples, tools, and setup scripts referencing Windows-specific commands, file types, and utilities (e.g., .cmd, .bat, .exe, PowerShell, msiexec.exe, cmdkey, Windows environment variables). There is no mention of Linux or macOS equivalents, nor guidance for users on non-Windows platforms. The Azure-SSIS IR environment itself is Windows-based, but the documentation does not clarify this up front or provide any advice for Linux/macOS users who may need to interact with the setup process (e.g., preparing scripts, using Azure Storage Explorer, or running PowerShell).
Recommendations
  • Explicitly state at the beginning that Azure-SSIS IR is a Windows-only environment, and that all custom setups must use Windows-compatible scripts and tools.
  • Provide guidance for Linux/macOS users on how to prepare and upload setup files (e.g., using Azure CLI, azcopy, or web portal instead of Azure Storage Explorer).
  • Offer alternatives to PowerShell for provisioning/reconfiguring Azure-SSIS IR, such as Azure CLI or REST API instructions.
  • Clarify which steps must be performed on Windows and which can be done from any OS.
  • Add a section for cross-platform users, outlining workflow and tool choices for those not on Windows.
GitHub Create Pull Request
Data Factory Create schedule triggers ...rticles/data-factory/how-to-create-schedule-trigger.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 exhibits moderate Windows bias, especially in the Azure PowerShell section. PowerShell is presented as a primary automation method, with explicit instructions for installing Azure PowerShell on Windows and creating files in Windows-style paths (e.g., C:\ADFv2QuickStartPSH\). The PowerShell section precedes the Azure CLI section, and the prerequisites and examples assume a Windows environment. While Azure CLI, .NET, Python, and ARM template methods are also documented (and are cross-platform), the PowerShell and Windows-centric instructions may create friction for Linux/macOS users.
Recommendations
  • Add explicit instructions for installing and using Azure PowerShell on Linux/macOS, including alternative installation commands and notes about cross-platform compatibility.
  • When referencing file paths, use platform-agnostic examples (e.g., ./ADFv2QuickStartPSH/MyTrigger.json) or provide both Windows and Unix-style paths.
  • In the PowerShell section, clarify that Azure PowerShell is available on Linux/macOS and link to relevant installation guides.
  • Reorder CLI and PowerShell sections, or introduce CLI first, as it is more universally available and platform-neutral.
  • Where possible, provide Bash or shell script equivalents for common automation tasks.
  • Add a short note at the beginning of the automation sections highlighting cross-platform support and pointing to relevant documentation for non-Windows users.
GitHub Create Pull Request
Data Factory Run SSIS package with Stored Procedure Activity - Azure ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-stored-procedure-activity.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 provides extensive PowerShell-based instructions, assumes file paths and tooling typical of Windows environments (e.g., C:\ADF\RunSSISPackage), and does not offer equivalent examples for Linux/macOS users (such as Bash, Azure CLI, or cross-platform scripting). Windows-centric tools and patterns are presented exclusively and before any mention of alternatives, creating friction for non-Windows users.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform.
  • Include instructions for creating and managing JSON files and folders on Linux/macOS (e.g., using touch, nano, or vi, and appropriate file paths like ~/ADF/RunSSISPackage).
  • Explicitly state that PowerShell Core is available on Linux/macOS and provide guidance for installation and usage.
  • Present cross-platform alternatives (e.g., Bash scripts, CLI commands) alongside PowerShell, not only after.
  • Avoid hardcoding Windows file paths; use environment-agnostic paths or note platform differences.
  • Add a section or note for Linux/macOS users outlining any differences or caveats.
GitHub Create Pull Request
Data Factory Use the Execute SSIS Package activity from the portal ...ta-factory/how-to-invoke-ssis-package-ssis-activity.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows Authentication Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. It repeatedly references Windows authentication, Windows-specific concepts (UNC paths, domain/username/password patterns), and Windows tools (SQL Server Data Tools, SQL Server Management Studio, dtutil). There are no Linux/macOS-specific instructions, nor any mention of how non-Windows users might interact with these features. All examples and credential patterns are Windows-centric, and the documentation assumes the use of Windows-based file shares and authentication mechanisms.
Recommendations
  • Add explicit guidance for Linux/macOS users, including how to access Azure Files from non-Windows platforms (e.g., using SMB/CIFS mounts on Linux, or Azure CLI/SDKs).
  • Clarify whether Windows authentication is required or if alternatives (such as Azure AD, SAS tokens, or service principals) are supported and provide examples.
  • Include examples of mounting Azure Files or accessing SSIS packages from Linux/macOS environments.
  • Mention cross-platform tools (e.g., Azure Data Studio, Azure CLI) as alternatives to SSMS and SSDT where possible.
  • Reorder examples so that platform-neutral or cross-platform approaches are presented first, or at least alongside Windows-specific instructions.
GitHub Create Pull Request
Data Factory Schedule an Azure-SSIS integration runtime ...tory/how-to-schedule-azure-ssis-integration-runtime.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 Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias, especially in sections related to monitoring and automation. PowerShell is the only scripting language shown for automation and monitoring tasks, with no equivalent Bash, CLI, or cross-platform alternatives. The use of SQL Server Management Studio (a Windows-only tool) is recommended for package verification, and there are no examples or guidance for Linux/macOS users. The documentation assumes access to Windows tools and does not mention or prioritize Linux-compatible approaches.
Recommendations
  • Provide Azure CLI examples for monitoring pipelines and triggers, alongside PowerShell.
  • Include Bash or Python script samples for automation tasks, especially for starting/stopping IRs.
  • Mention and demonstrate cross-platform tools for SSIS package verification (e.g., Azure Data Studio, REST API calls).
  • Explicitly state platform requirements and offer alternatives for Linux/macOS users.
  • Reorder examples so that cross-platform solutions are presented before or alongside Windows-specific ones.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/includes/data-factory-v2-connector-get-started.md ...tory/includes/data-factory-v2-connector-get-started.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation lists Azure PowerShell as a primary tool for performing copy activities, which is most commonly associated with Windows environments. The list includes Windows-centric tools (PowerShell) and places them before Linux-native equivalents (e.g., CLI). There is no mention of the Azure CLI, which is the preferred cross-platform command-line tool for Azure and widely used on Linux/macOS. The ordering and selection of tools suggest a Windows-first perspective.
Recommendations
  • Add Azure CLI as a recommended tool for performing copy activities, with links to relevant quickstart guides.
  • Ensure examples and instructions are provided for both PowerShell and CLI, with clear indication of platform compatibility.
  • Consider reordering the list so that cross-platform tools (CLI, Python SDK, REST API) are presented before Windows-specific tools.
  • Explicitly mention platform compatibility for each tool to help users choose the best option for their OS.
GitHub Create Pull Request
← Previous Page 34 of 40 Next →