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 726-750 of 1000 flagged pages
Data Factory Troubleshoot the REST connector ...n/articles/data-factory/connector-troubleshoot-rest.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias by instructing users to use 'curl' in a Command Prompt window, which is a Windows-specific context, and by recommending Fiddler, a Windows-only tool, for troubleshooting SSL certificate issues. There are no explicit Linux/macOS examples or tool alternatives provided, and the troubleshooting steps assume a Windows environment.
Recommendations
  • Include Linux/macOS terminal examples for 'curl', clarifying that the command works cross-platform.
  • Mention that 'curl' is available by default on most Linux/macOS systems, and provide equivalent shell instructions.
  • Suggest cross-platform alternatives to Fiddler, such as mitmproxy or Wireshark, for SSL troubleshooting.
  • Avoid referencing Windows-specific environments (e.g., 'Command Prompt window') without also mentioning Linux/macOS equivalents (e.g., 'terminal').
GitHub Create Pull Request
Data Factory Copy data from Vertica ...s/blob/main/articles/data-factory/connector-vertica.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 Windows bias in the section describing how to install the Vertica ODBC driver for version 2.0. All installation steps and screenshots exclusively reference Windows systems, with no mention of Linux or macOS procedures. The phrase 'Take Windows system setup as an example' is used, but no alternative instructions are provided for other platforms. The confirmation step references the Windows ODBC Data Source Administrator tool, which does not exist on Linux/macOS. No Linux/macOS installation commands, screenshots, or troubleshooting are included.
Recommendations
  • Add parallel instructions and screenshots for installing the Vertica ODBC driver on Linux (e.g., using .rpm or .deb packages, or tarballs).
  • Include macOS installation steps if supported, or explicitly state platform limitations.
  • Provide guidance for verifying ODBC driver installation on Linux/macOS (e.g., using `odbcinst -q -d` or editing odbc.ini/odbcinst.ini).
  • Clarify any platform-specific requirements or limitations for the self-hosted integration runtime.
  • Present Windows and Linux/macOS instructions side-by-side or in separate tabs for parity.
GitHub Create Pull Request
Data Factory Continuous integration and delivery pre- and post-deployment scripts ...ctory/continuous-integration-delivery-sample-script.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 PowerShell scripts and Azure PowerShell tasks for CI/CD scripting in Azure Data Factory. All examples, instructions, and YAML pipeline steps are centered around PowerShell (.ps1) files and the AzurePowerShell@5 task, with no mention of Bash, shell scripts, or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and Windows/PowerShell tools are referenced first and exclusively.
Recommendations
  • Provide equivalent Bash or shell script examples for pre- and post-deployment tasks.
  • Include instructions for running scripts using the AzureCLI@2 task in Azure Pipelines, which is cross-platform.
  • Clarify whether the PowerShell scripts are compatible with PowerShell Core on Linux/macOS, and provide explicit guidance for those platforms.
  • Add notes or sections highlighting how Linux/macOS users can perform the same operations, including installation steps for Azure CLI and PowerShell Core on those systems.
  • Consider offering downloadable sample scripts in both PowerShell and Bash.
GitHub Create Pull Request
Data Factory Automate continuous integration ...ntinuous-integration-delivery-automate-azure-pipelines.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 page demonstrates a notable Windows bias, primarily through exclusive use of PowerShell for automation tasks, explicit instructions to install Azure PowerShell modules, and references to .ps1 scripts. There are no Bash, CLI, or cross-platform alternatives provided for Linux/macOS users. The guidance for managing triggers and permissions is centered around PowerShell, with no mention of Azure CLI or other non-Windows tools. This creates friction for users on Linux or macOS, who may not have PowerShell installed or prefer native shell environments.
Recommendations
  • Provide equivalent Azure CLI or Bash examples for all automation steps, especially for stopping/starting triggers and managing permissions.
  • Clarify whether PowerShell Core (pwsh) is required and supported on Linux/macOS, and provide installation guidance for those platforms.
  • Include explicit notes or sections for Linux/macOS users, outlining any differences or additional steps needed.
  • Where .ps1 scripts are referenced, offer alternative scripts in Bash or Azure CLI, or link to cross-platform samples.
  • Avoid assuming PowerShell is the default automation tool; present CLI and PowerShell options side-by-side.
GitHub Create Pull Request
Data Factory If Condition activity ...les/data-factory/control-flow-if-condition-activity.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 First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples use Azure PowerShell, with file paths in Windows format (e.g., C:\ADF), and there are no CLI or bash examples for Linux/macOS users. The tutorial and walkthrough references are PowerShell-centric, and no alternative instructions for Linux environments are provided.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, using Linux/macOS-friendly file paths.
  • Include notes or sections on running these steps on Linux/macOS, such as using bash scripts or Azure CLI.
  • Present cross-platform examples side-by-side, or alternate which platform is shown first.
  • Avoid hardcoding Windows file paths; use generic or platform-agnostic paths in examples.
GitHub Create Pull Request
Data Factory Until activity ...n/articles/data-factory/control-flow-until-activity.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 First Missing Linux Example
Summary
The documentation provides detailed PowerShell commands and assumes a Windows environment (e.g., file paths like C:\ADF), with no equivalent instructions for Linux/macOS users. All CLI examples use PowerShell, and there is no mention of Bash, Azure CLI, or cross-platform alternatives. This creates friction for non-Windows users who may not have access to PowerShell or use different file path conventions.
Recommendations
  • Add Azure CLI (az) examples for pipeline creation, execution, and monitoring, alongside PowerShell.
  • Include Linux/macOS file path examples and clarify that JSON files can be stored in any directory.
  • Explicitly state cross-platform compatibility and provide instructions for running commands on Linux/macOS.
  • Mention that PowerShell Core is available on Linux/macOS, but also provide Bash/Azure CLI alternatives for broader accessibility.
GitHub Create Pull Request
Data Factory Copy activity ...b/main/articles/data-factory/copy-activity-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page does not explicitly mention Windows or Windows-specific tools, but there is evidence of subtle Windows bias. In the 'Related content' section, the only hybrid/on-premises example provided is 'Copy data from a SQL Server database to Azure' using PowerShell, which is typically associated with Windows environments. There are no Linux/macOS-specific examples, nor are Linux tools or shell scripts referenced. The examples and tutorials do not demonstrate parity for Linux users, and the documentation does not clarify cross-platform setup or usage for self-hosted integration runtime.
Recommendations
  • Add Linux/macOS-specific examples, such as copying data from a Linux file system or using bash scripts.
  • Provide explicit instructions or links for setting up self-hosted integration runtime on Linux, including troubleshooting and service management.
  • Include parity in tutorials, e.g., a walkthrough for copying data from a Linux server to Azure.
  • Reference Linux tools and commands where appropriate, not just PowerShell.
  • Clarify any platform-specific limitations or requirements for self-hosted integration runtime.
GitHub Create Pull Request
Data Factory Copy or clone a data factory in Azure Data Factory .../main/articles/data-factory/copy-clone-data-factory.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation references a pattern for sharing SelfHosted Integration Runtime that is published specifically for PowerShell, a Windows-centric tool. No equivalent Linux/macOS CLI or scripting guidance is provided, and the link for sharing SelfHosted IR points to a PowerShell-based solution. There are no explicit Linux or cross-platform examples for deployment, and the documentation implicitly assumes use of Windows tools for key steps.
Recommendations
  • Provide equivalent instructions for sharing SelfHosted Integration Runtime using Azure CLI or REST API, which are cross-platform.
  • Include examples for exporting and deploying Resource Manager templates using Azure CLI or Bash scripts, not just portal or PowerShell.
  • Explicitly mention that steps can be performed on Linux/macOS and link to relevant cross-platform documentation.
  • Add notes or sections clarifying platform neutrality where applicable.
GitHub Create Pull Request
Data Factory Wait activity ...in/articles/data-factory/control-flow-wait-activity.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 First Missing Linux Example
Summary
The documentation page provides JSON definitions and sample PowerShell commands, with explicit reference to a walkthrough using Azure PowerShell. There are no equivalent examples or instructions for Linux/macOS users (e.g., using Azure CLI, Bash, or REST API), and PowerShell is presented as the primary method for pipeline creation and execution.
Recommendations
  • Add equivalent examples using Azure CLI, Bash, or REST API to demonstrate pipeline creation and execution on Linux/macOS.
  • Include cross-platform instructions and clarify that PowerShell is not required, highlighting alternatives for non-Windows users.
  • Present examples for different platforms side-by-side or indicate platform-specific steps clearly.
  • Link to tutorials for Linux/macOS users where available.
GitHub Create Pull Request
Data Factory Web Activity ...ain/articles/data-factory/control-flow-web-activity.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias primarily in the authentication section, where only a PowerShell snippet is provided for base64-encoding a PFX certificate file. No Linux/macOS equivalent (such as OpenSSL or shell commands) is mentioned. The use of PowerShell and reference to .pfx files (commonly used in Windows environments) further reinforces the bias. The rest of the documentation is platform-neutral, focusing on Azure service configuration and JSON syntax.
Recommendations
  • Add Linux/macOS equivalent commands for base64-encoding PFX files, such as using OpenSSL and base64 utilities.
  • Explicitly mention cross-platform tools and approaches for certificate conversion and encoding.
  • Provide example snippets for both Windows (PowerShell) and Linux/macOS (shell/OpenSSL) users.
  • Clarify that .pfx files can be created and encoded on any OS, and link to relevant cross-platform instructions.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a command-line example only for Azure PowerShell (Set-AzDataFactoryV2IntegrationRuntime), which is primarily a Windows tool. There are no equivalent examples for Linux/macOS users, such as Azure CLI or REST API usage. This creates friction for non-Windows users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Add Azure CLI examples for creating Azure Integration Runtime, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API example for advanced users who may want to automate via HTTP requests.
  • Explicitly mention platform compatibility for each method (PowerShell, CLI, UI) and recommend alternatives for Linux/macOS users.
  • Consider listing cross-platform methods (CLI, REST) before or alongside PowerShell to avoid Windows-first perception.
GitHub Create Pull Request
Data Factory Deploy SSIS packages ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-deploy-packages.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) without mentioning Linux/macOS alternatives or clarifying cross-platform support. There are no explicit Linux/macOS examples or guidance, and Windows tools are presented as the default option.
Recommendations
  • Clarify whether SSDT, SSMS, dtutil, and AzureDTExec are available or supported on Linux/macOS, and provide alternatives if not.
  • Include examples or instructions for deploying SSIS packages from Linux/macOS environments, if possible.
  • Mention cross-platform command-line utilities (if any) and provide parity in examples.
  • Explicitly state platform requirements and limitations for each tool mentioned.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools (SSDT, SSMS, dtutil, PowerShell) as the 'familiar tools' for deploying and running SSIS packages, and provides explicit instructions and links for using Azure PowerShell to provision resources. Linux/macOS alternatives (such as Azure CLI or cross-platform database tools) are not mentioned, and Windows tools are presented first and exclusively.
Recommendations
  • Include Azure CLI instructions for provisioning Azure-SSIS IR, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Mention cross-platform database management tools (e.g., Azure Data Studio) alongside SSMS.
  • Clarify which steps and tools are available on Linux/macOS, and provide links or examples for those platforms.
  • Add notes or sections for deploying SSIS packages from non-Windows environments, if supported.
  • Where PowerShell is referenced, also provide equivalent Azure CLI commands.
GitHub Create Pull Request
Data Factory Using credentials ...re-docs/blob/main/articles/data-factory/credentials.md
Medium Priority View Details →
Scanned: 2026-01-14 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 (Azure portal, PowerShell) and providing screenshots and workflow examples exclusively using the Azure portal UI, which is most commonly accessed from Windows environments. While SDK and REST API options are mentioned, there are no explicit Linux/macOS CLI examples (such as Azure CLI), nor are Linux-specific workflows or screenshots provided. PowerShell is listed as a primary scripting option, with no parity for Bash or Azure CLI. This may create friction for Linux/macOS users who prefer or require command-line or non-GUI approaches.
Recommendations
  • Add explicit Azure CLI examples for all major steps (creating managed identities, associating them, managing credentials, etc.), as Azure CLI is cross-platform.
  • Include screenshots or workflow descriptions for non-Windows environments, such as using Azure CLI or REST API from Linux/macOS.
  • Reference Bash scripting alongside PowerShell in the 'Managing credentials with scripts' section.
  • Order tool references to mention cross-platform options (Azure CLI, REST API) before Windows-specific ones (PowerShell).
  • Clarify that all steps can be performed from Linux/macOS using CLI or REST API, and provide links to relevant documentation.
GitHub Create Pull Request
Data Factory Managed identity ...articles/data-factory/data-factory-service-identity.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 First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. PowerShell is the only CLI example provided for generating and retrieving managed identities, with no Bash, Azure CLI, or Linux/macOS shell equivalents. PowerShell commands are presented before REST API, ARM template, and SDK examples, and there is no mention of cross-platform alternatives. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Explicitly mention that PowerShell commands are Windows-centric and provide equivalent Bash/Azure CLI instructions.
  • Reorder examples so that REST API, ARM template, and SDK instructions are presented before or alongside PowerShell, to avoid Windows-first impression.
  • Include notes or links for Linux/macOS users on how to perform these operations without PowerShell.
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-14 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 alternatives such as Azure CLI, Bash, or REST API. This creates friction for users on non-Windows platforms, as PowerShell is not the default shell and may require additional setup. The examples and instructions assume a Windows-centric workflow.
Recommendations
  • Add equivalent Azure CLI commands for deploying and managing Azure-SSIS IR, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Include REST API examples for template deployment and IR management, which are platform-agnostic.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and provide installation guidance if PowerShell must be used.
  • Present examples for both Windows (PowerShell) and Linux/macOS (Azure CLI/Bash) side by side, or indicate which commands are platform-specific.
  • Update related content links to include documentation for Azure CLI and REST API usage where available.
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-14 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 strong Windows bias by providing only PowerShell-based instructions for scripting and automation, explicitly referencing Windows PowerShell ISE, and linking to Windows-centric installation guides. There are no equivalent examples for Linux/macOS users (e.g., Bash, Azure CLI), nor is there guidance for installing or using the integration runtime on non-Windows platforms.
Recommendations
  • Add Azure CLI examples for all PowerShell commands, ensuring Linux/macOS users can follow along.
  • Clarify whether the self-hosted integration runtime installer is available for Linux/macOS, and provide installation steps for those platforms if supported.
  • Replace references to 'Windows PowerShell ISE' with more cross-platform tools (e.g., VS Code, terminal) or mention alternatives.
  • Reorder or parallelize examples so that Linux/macOS instructions are presented alongside Windows instructions.
  • Explicitly state platform requirements and limitations for the integration runtime, including any OS restrictions.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides detailed instructions for creating a Windows Server virtual machine to host the self-hosted integration runtime (IR), with no mention of Linux-based alternatives or examples. The only OS-specific guidance is for Windows, and the VM image selection is explicitly Windows-centric. This creates friction for Linux users who may wish to host the IR on a Linux VM.
Recommendations
  • Add instructions and examples for creating a Linux VM (e.g., Ubuntu, CentOS) for hosting the self-hosted IR, if supported.
  • Clarify whether the self-hosted IR can be installed on Linux, and if not, state this limitation explicitly.
  • If Linux is supported, provide parity in step-by-step guidance for Linux VM creation and IR installation.
  • Include cross-platform notes or links to OS-specific installation guides for the self-hosted IR.
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-14 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 details and architecture recommendations. It repeatedly specifies installing the Data Factory self-hosted integration runtime on Windows machines or Windows VMs, without mentioning Linux as a supported or recommended platform. All example architectures and pricing calculations assume Windows VMs. There are no examples or instructions for Linux-based integration runtime hosts, nor is there guidance for Linux users wishing to perform the same migration tasks.
Recommendations
  • Explicitly state whether the Data Factory self-hosted integration runtime supports Linux hosts, and provide setup instructions for Linux if supported.
  • Include Linux VM examples alongside Windows VM examples in architecture diagrams and pricing scenarios.
  • Clarify any platform-specific limitations or requirements for both Windows and Linux users.
  • Provide parity in best practices and troubleshooting for Linux environments.
  • If Linux is not supported, clearly document this limitation and suggest alternatives for Linux users.
GitHub Create Pull Request
Data Factory General Troubleshooting ...ticles/data-factory/data-factory-troubleshoot-guide.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 Windows First
Summary
The documentation contains several instances of Windows bias, notably in the Custom section for Azure Batch, where troubleshooting and file extraction examples use PowerShell commands and reference 'powershell.exe'. Windows tools like Fiddler are recommended for network troubleshooting, with no mention of Linux alternatives. In the section on unsupported compression, Windows is referenced as the default environment for creating zip files, and the behavior of Windows compression tools is described before mentioning third-party alternatives. These examples and tool recommendations are given without Linux/macOS equivalents or alternatives, and Windows-centric instructions appear first or exclusively.
Recommendations
  • Provide equivalent Linux/macOS commands for file extraction (e.g., 'unzip', 'tar', or '7z') alongside PowerShell examples.
  • Mention cross-platform or Linux-native troubleshooting tools (e.g., tcpdump, Wireshark, curl) when discussing network diagnostics, not just Fiddler.
  • When discussing compression issues, include guidance for Linux/macOS users (e.g., how to create zip files with 'deflate' using 'zip' CLI or other tools).
  • Ensure that examples and instructions are not Windows-first; present cross-platform solutions or alternate between platforms.
  • Explicitly state platform requirements or limitations where relevant, so users on Linux/macOS are aware of possible issues.
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-14 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 (SQL Server Management Studio, SSMS), Windows patterns (Object Explorer, right-click menus), and does not mention or provide parity for Linux/macOS alternatives (e.g., Azure Data Studio, command-line SQL tools). All configuration and management examples are shown using SSMS, with no guidance for users on non-Windows platforms. While PowerShell is used for Azure automation, it is cross-platform, but the overall workflow assumes Windows-based tooling and UI patterns.
Recommendations
  • Add instructions for configuring SSISDB log clean-up properties using Azure Data Studio, which is available on Linux/macOS.
  • Include examples using sqlcmd or Azure CLI for tasks currently described with SSMS UI steps.
  • Explicitly mention cross-platform alternatives to SSMS and provide links or steps for Linux/macOS users.
  • Reorder sections so that cross-platform or web-based approaches (Azure portal, T-SQL scripts, Azure CLI) are presented before or alongside Windows-specific tools.
  • Clarify which steps require Windows-only tools and suggest alternatives where possible.
GitHub Create Pull Request
Data Factory Security considerations .../data-factory/data-movement-security-considerations.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 Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias, especially in the hybrid/on-premises scenarios. It references Windows-specific tools (PowerShell cmdlets, DPAPI, Windows Firewall) exclusively for credential encryption and management, and does not provide equivalent instructions or examples for Linux/macOS environments. The port requirements and firewall configuration sections also focus on Windows Firewall and PowerShell, with no mention of Linux firewall tools (e.g., iptables, firewalld) or cross-platform alternatives.
Recommendations
  • Provide Linux/macOS equivalents for credential encryption and management, such as using OpenSSL or platform-agnostic encryption libraries.
  • Include examples using bash scripts, Azure CLI, or REST API for tasks currently shown only with PowerShell cmdlets.
  • Document Linux firewall configuration steps (e.g., using iptables, ufw, firewalld) alongside Windows Firewall instructions.
  • Clarify whether self-hosted integration runtime supports Linux, and if so, provide setup and security instructions for those platforms.
  • Explicitly state any platform limitations or requirements for self-hosted integration runtime and related security features.
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-14 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 Windows bias by referencing PowerShell and Azure CLI as the main methods for configuring Azure Key Vault properties, with PowerShell mentioned first. There are no explicit Linux/macOS command examples, nor is there mention of bash or shell scripting alternatives. The instructions and screenshots are focused on the Azure Portal UI, which is cross-platform, but command-line guidance is Windows-centric.
Recommendations
  • Add explicit bash/Azure CLI examples for enabling Key Vault properties, with clear instructions for Linux/macOS users.
  • Where PowerShell is mentioned, provide equivalent bash or shell commands.
  • Clarify that Azure CLI is cross-platform and provide installation links for Linux/macOS.
  • Ensure that any references to command-line tools do not assume a Windows environment.
  • Consider including screenshots or terminal output from Linux/macOS environments where relevant.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation repeatedly references the PowerShell upgrade tool as the primary method for migration, without mentioning Linux/macOS alternatives or cross-platform tools. There are no Bash, CLI, or platform-neutral examples, and PowerShell is suggested in both the main flow and FAQ as the go-to solution. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native tools.
Recommendations
  • Include Azure CLI or REST API alternatives for migration steps, with examples.
  • Explicitly state PowerShell's cross-platform availability, or provide installation guidance for Linux/macOS.
  • Add Bash or shell script examples for exporting and processing assessment results.
  • Mention any GUI or portal-based migration options for users who prefer not to use PowerShell.
  • Clarify tool compatibility and limitations for non-Windows platforms.
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-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 provides instructions using Azure PowerShell, a tool most commonly used on Windows, and does not mention or provide examples for Linux/macOS users (e.g., Azure CLI or REST API). Windows authentication is referenced for SSAS connectivity, further reinforcing a Windows-centric approach. No Linux or cross-platform alternatives are discussed, making it difficult for non-Windows users to follow the provisioning steps.
Recommendations
  • Add equivalent instructions and examples using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Mention REST API options for provisioning the Azure-SSIS IR Enterprise Edition.
  • Clarify any platform-specific requirements or limitations, and provide guidance for Linux/macOS users where Windows authentication is referenced.
  • Present cross-platform tools and examples before or alongside PowerShell instructions to avoid Windows-first bias.
GitHub Create Pull Request
← Previous Page 30 of 40 Next →