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 76-100 of 319 flagged pages
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-if-condition-activity.md ...les/data-factory/control-flow-if-condition-activity.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 a strong Windows bias by exclusively providing PowerShell commands and referencing Windows file paths (e.g., C:\ADF). There are no examples or instructions for Linux or cross-platform CLI tools such as Azure CLI, Bash, or Cloud Shell. The only automation walkthrough is for Azure PowerShell, and no Linux or macOS equivalents are mentioned or linked.
Recommendations
  • Add equivalent examples using Azure CLI (az) commands, which are cross-platform and work on Linux, macOS, and Windows.
  • Provide Bash shell command examples for running pipelines, uploading JSON files, and monitoring pipeline runs.
  • Use platform-neutral file paths in examples (e.g., ./ADF or ~/ADF) or show both Windows and Linux/macOS path formats.
  • Explicitly mention that the PowerShell example is for Windows users and provide links or sections for Linux/macOS users.
  • Include a note or section on how to perform the same operations in the Azure Portal or with REST API calls, which are platform-independent.
  • Ensure that all step-by-step walkthroughs have parity for both PowerShell and Azure CLI users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-wait-activity.md ...in/articles/data-factory/control-flow-wait-activity.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides only PowerShell-based examples and walkthroughs for running pipelines, with no mention of Linux or cross-platform alternatives (such as Azure CLI, Bash, or REST API). The only step-by-step tutorial referenced is for Azure PowerShell, which is primarily associated with Windows environments. There are no Linux-specific or cross-platform command-line examples, nor is there guidance for users on non-Windows systems.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Include Bash shell command examples for pipeline execution, or reference REST API usage for platform-agnostic automation.
  • When referencing tutorials, provide links to both PowerShell and Azure CLI (or REST API) guides, and mention their cross-platform compatibility.
  • Explicitly state that the Wait activity and pipeline execution can be managed from any OS, and provide parity in documentation for Linux/macOS users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/control-flow-web-activity.md ...ain/articles/data-factory/control-flow-web-activity.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 provides a PowerShell snippet for base64-encoding a PFX certificate but does not offer equivalent Linux/macOS commands (e.g., using OpenSSL or base64). No Linux tools or shell examples are mentioned, and the only code for certificate conversion/encoding is Windows-specific. This may hinder users on non-Windows platforms.
Recommendations
  • Add equivalent Linux/macOS shell commands for base64-encoding a PFX file (e.g., using 'base64' or 'openssl').
  • Explicitly mention that certificate conversion and encoding can be performed on any OS, and provide cross-platform guidance.
  • Wherever PowerShell is used, provide a Bash or POSIX shell alternative.
  • Review other sections for implicit Windows-first assumptions and ensure parity in tool and example coverage.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/copy-activity-overview.md ...b/main/articles/data-factory/copy-activity-overview.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its choice of examples and tutorials. The only explicit platform-specific example is 'Copy data from a SQL Server database to Azure (tutorial-hybrid-copy-powershell.md)', which uses PowerShell, a Windows-centric tool. There are no Linux or cross-platform command-line examples, and no mention of Linux-specific tools or workflows. The documentation does not provide parity in Linux or bash scripting examples, nor does it reference Linux file systems or tools in its scenarios.
Recommendations
  • Add Linux/bash-based examples for hybrid and on-premises scenarios, such as using bash scripts or Azure CLI on Linux.
  • Include references to Linux file systems and workflows in the scenarios and examples, especially when discussing on-premises data movement.
  • Provide parity in tutorials and quickstarts by including at least one that uses Linux-native tools or environments.
  • When mentioning PowerShell or Windows tools, also mention their Linux equivalents (e.g., Azure CLI, bash) and provide links or code samples.
  • Review connector documentation to ensure Linux and cross-platform usage is equally represented and accessible.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/copy-activity-performance-features.md ...les/data-factory/copy-activity-performance-features.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 page demonstrates subtle Windows bias, particularly in the 'Staged copy' section, where firewall configuration examples reference only the Windows firewall and do not mention Linux or cross-platform equivalents. No Linux-specific examples or tools are provided, and the only OS-specific mention is Windows. There are no PowerShell or CLI examples, but the absence of Linux references and the exclusive mention of Windows tools/patterns indicates a Windows-first perspective.
Recommendations
  • When discussing firewall configuration, include Linux firewall equivalents (e.g., iptables, firewalld, ufw) alongside Windows firewall instructions.
  • Explicitly state that the guidance applies to both Windows and Linux self-hosted integration runtime nodes, and provide links to relevant Linux documentation where appropriate.
  • If referencing OS-specific requirements (such as opening ports), provide instructions or references for both Windows and Linux environments.
  • Consider adding a note or section on deploying and optimizing the self-hosted integration runtime on Linux, since it is supported.
  • Review the documentation for other implicit Windows assumptions and ensure parity in examples, terminology, and guidance for Linux users.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-integration-runtime.md ...icles/data-factory/create-azure-integration-runtime.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 provides a PowerShell-only example for creating an Azure Integration Runtime, which is a Windows-centric tool. There are no examples using cross-platform tools like Azure CLI, Bash, or REST API, nor is there mention of Linux/macOS workflows. This creates a bias towards Windows users and may hinder Linux or macOS users from following the instructions easily.
Recommendations
  • Add equivalent Azure CLI examples for creating and managing Azure Integration Runtime, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include REST API or ARM template examples for users who prefer declarative or programmatic approaches, which are OS-agnostic.
  • Explicitly mention that PowerShell examples are primarily for Windows, and provide guidance or links for Linux/macOS users.
  • Consider reordering or balancing the documentation so that cross-platform methods (CLI/REST) are presented before or alongside PowerShell.
  • Add a table or section summarizing all available methods (PowerShell, CLI, REST, Portal) with links to detailed instructions for each.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-deploy-packages.md ...ps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-deploy-packages.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 primarily references Windows-centric tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and running SSIS packages, with no mention of Linux-compatible alternatives or cross-platform methods. There are no Linux-specific instructions or examples, and the tools mentioned are traditionally Windows-only. Additionally, the related content highlights Azure PowerShell before other provisioning methods, reinforcing a Windows-first perspective.
Recommendations
  • Include information about cross-platform or Linux-compatible tools (if available) for deploying and running SSIS packages.
  • Explicitly state the platform requirements and limitations for the mentioned tools (e.g., SSDT, SSMS, dtutil, AzureDTExec), and suggest alternatives or workarounds for Linux users.
  • Provide Linux command-line examples or guidance for users who may be working in non-Windows environments.
  • Balance the order of related content to avoid prioritizing Windows-specific tools (e.g., list ARM template or CLI methods before or alongside PowerShell).
  • If no Linux support exists, clearly document this limitation and link to feature requests or roadmap items for Linux parity.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime-resource-manager-template.md ...ure-ssis-integration-runtime-resource-manager-template.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias by exclusively providing PowerShell commands for deploying and managing Azure-SSIS integration runtimes. No examples are given for Linux or cross-platform tools such as Azure CLI, and Windows-specific tools and patterns (PowerShell cmdlets) are mentioned first and exclusively. There is no mention of how to perform these tasks on Linux or macOS, nor are alternative command-line interfaces or automation approaches suggested.
Recommendations
  • Add equivalent Azure CLI examples for deploying and managing Azure-SSIS IR, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
  • Explicitly mention that PowerShell examples are Windows-centric and provide guidance for users on other platforms.
  • Include links or references to documentation for using REST API or ARM templates via Azure CLI or other cross-platform tools.
  • Where possible, provide bash script examples or instructions for Linux users.
  • Review related content and ensure Linux/cross-platform parity in referenced articles.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-azure-ssis-integration-runtime.md .../data-factory/create-azure-ssis-integration-runtime.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools (SSDT, SSMS, dtutil, PowerShell) for deploying and managing Azure-SSIS IR, without mentioning Linux or cross-platform alternatives. PowerShell is the only command-line example referenced, and there are no Linux-native instructions or examples. The order of presentation also places Windows tools and patterns before any mention of platform-agnostic or Linux-compatible options.
Recommendations
  • Include examples using Azure CLI, which is cross-platform, for provisioning and managing Azure-SSIS IR.
  • Mention and provide guidance for using Data Factory REST APIs, which are platform-agnostic.
  • Clarify whether any of the deployment tools (e.g., dtutil, AzureDTExec) are available or supported on Linux, and if not, suggest alternatives or workarounds.
  • Add explicit Linux/macOS instructions or notes where only Windows tools are referenced (e.g., for firewall rule configuration, database connection, or package deployment).
  • Reorder tool mentions to highlight cross-platform or web-based options (e.g., Azure portal, Azure CLI, REST API) before Windows-specific tools.
  • Where PowerShell is referenced, also provide equivalent Azure CLI commands.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/create-shared-self-hosted-integration-runtime-powershell.md ...eate-shared-self-hosted-integration-runtime-powershell.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 Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by providing only PowerShell-based examples and instructions, explicitly referencing Windows tools (such as Windows PowerShell ISE), and linking to PowerShell installation instructions for Windows. There are no equivalent examples or instructions for Linux or macOS users (e.g., Bash, Azure CLI, or cross-platform PowerShell Core). The UI instructions are platform-agnostic, but all command-line automation is Windows-centric.
Recommendations
  • Add equivalent examples using Azure CLI, which is cross-platform and widely used on Linux and macOS.
  • Clarify that PowerShell Core (pwsh) can be used on Linux/macOS, and provide installation instructions for non-Windows platforms.
  • Replace references to 'Windows PowerShell ISE' with more general or cross-platform editors, or note that scripts can be run in any terminal.
  • Explicitly mention and provide guidance for Linux/macOS users, including any platform-specific prerequisites or differences.
  • Include sample scripts or commands for Bash or other common Linux shells where appropriate.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-factory-service-identity.md ...articles/data-factory/data-factory-service-identity.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 exhibits a Windows bias by providing PowerShell-based examples for generating and retrieving managed identities, with no equivalent examples for Linux-native tools (e.g., Azure CLI, Bash). PowerShell is mentioned first and most frequently for command-line operations, and there are no references to Linux or cross-platform command-line usage. The documentation assumes the use of Windows tools and patterns, potentially excluding Linux users or those who prefer Azure CLI.
Recommendations
  • Add Azure CLI examples alongside PowerShell for all command-line operations (e.g., generating and retrieving managed identities).
  • When listing ways to perform tasks (e.g., 'using PowerShell, REST API, ARM template, SDK'), mention Azure CLI and Bash scripts, and do not always list PowerShell first.
  • Include explicit notes or sections for Linux/macOS users, clarifying that Azure CLI is cross-platform and providing relevant commands.
  • Where possible, provide Bash script snippets or generic REST API curl examples to ensure parity for non-Windows environments.
  • Review the documentation for other places where only Windows-centric tools are referenced and add Linux-friendly alternatives.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-factory-ux-troubleshoot-guide.md ...les/data-factory/data-factory-ux-troubleshoot-guide.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows tools (e.g., Command Prompt and nslookup) for troubleshooting network issues, without providing equivalent instructions for Linux or macOS users. All command-line examples assume a Windows environment, and there are no examples or guidance for users on other operating systems. Browser instructions are cross-platform (Edge and Chrome), but the troubleshooting steps for network issues are Windows-centric.
Recommendations
  • Add Linux and macOS equivalents for command-line troubleshooting steps, such as using the Terminal and the 'dig' or 'nslookup' commands.
  • When referencing 'Command Prompt', clarify that Linux/macOS users should use their respective terminal applications.
  • Provide example outputs for Linux/macOS commands alongside Windows examples.
  • Explicitly state that the troubleshooting steps apply to all platforms, and note any platform-specific differences.
  • Consider including a table or tabbed sections for Windows, Linux, and macOS users when describing command-line troubleshooting.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-flow-script.md ...cs/blob/main/articles/data-factory/data-flow-script.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 a Windows bias by referencing PowerShell cmdlets as the primary or sole method for programmatically interacting with Data Flow Script outside the UI. There are no examples or mentions of Linux/Unix command-line tools, shell scripting, or cross-platform alternatives. The instructions and workflow descriptions assume a Windows-centric environment, omitting Linux equivalents or guidance.
Recommendations
  • Add examples and instructions for using Data Flow Script with Linux/macOS environments, such as using Azure CLI, Bash scripts, or REST API via curl.
  • When referencing PowerShell, also mention cross-platform PowerShell Core (pwsh) and/or provide Bash equivalents.
  • Avoid assuming the use of Windows tools as the default; present cross-platform or OS-neutral approaches first, or at least in parallel.
  • Explicitly state that Data Flow Script can be used from any platform via REST API, and provide code snippets for both Windows (PowerShell) and Linux/macOS (Bash/curl).
  • Review all tool and workflow mentions to ensure Linux users are not excluded and have clear, actionable guidance.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-migration-guidance-hdfs-azure-storage.md ...-factory/data-migration-guidance-hdfs-azure-storage.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 page demonstrates a Windows bias by exclusively recommending installation of the Data Factory self-hosted integration runtime on Windows machines or Windows VMs, with no mention of Linux support or examples. Windows is presented as the default or only platform for hosting the integration runtime, and pricing estimates are based on Azure Windows VMs. There are no Linux-specific instructions, examples, or parity in tooling recommendations.
Recommendations
  • Explicitly mention and document support for installing the self-hosted integration runtime on Linux machines, if supported.
  • Provide Linux-based examples and instructions alongside Windows instructions, including VM sizing and scaling recommendations for common Linux distributions.
  • Include pricing estimates for both Windows and Linux VM scenarios.
  • Clarify any platform-specific limitations or differences in performance, monitoring, or management between Windows and Linux hosts.
  • Ensure that all references to 'Windows machine' or 'Windows VM' are accompanied by Linux alternatives where applicable.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-migration-guidance-s3-azure-storage.md ...ta-factory/data-migration-guidance-s3-azure-storage.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in its guidance for deploying self-hosted Integration Runtime (IR) on Azure VMs. It exclusively references Windows VMs for self-hosted IR installation, does not mention Linux support, and provides configuration recommendations only for Windows-based environments. No Linux equivalents or examples are given.
Recommendations
  • Explicitly state whether self-hosted Integration Runtime can be installed on Linux VMs. If supported, provide parallel instructions and recommendations for Linux deployments.
  • Include Linux-based VM sizing and configuration guidance alongside Windows examples.
  • If self-hosted IR is Windows-only, clarify this limitation early in the documentation and suggest alternative approaches for Linux-preferred environments.
  • Add Linux command-line or automation examples where relevant, ensuring parity with any Windows/PowerShell instructions.
  • Review and update diagrams and architecture sections to reflect both Windows and Linux deployment options where possible.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/deploy-linked-arm-templates-with-vsts.md .../data-factory/deploy-linked-arm-templates-with-vsts.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by primarily referencing the Azure portal (a GUI tool often associated with Windows users) for all steps, without mentioning or providing examples for command-line alternatives like Azure CLI or PowerShell scripts. While Azure CLI is briefly mentioned in the overview, no actual CLI or cross-platform command examples are given. There are no Linux-specific instructions or screenshots, and all workflows assume use of the Azure portal and Azure DevOps GUI, which are more familiar to Windows users.
Recommendations
  • Provide equivalent step-by-step instructions using Azure CLI commands for all major tasks (e.g., creating a storage account, generating SAS tokens, creating containers, managing Key Vault secrets).
  • Include PowerShell and Azure CLI script examples alongside or in place of GUI instructions, making it clear these can be run on Linux, macOS, or Windows.
  • Add screenshots or terminal output from Linux environments where appropriate.
  • Explicitly mention that all operations can be performed from Linux, macOS, or Windows, and link to relevant cross-platform tool documentation.
  • Consider reordering sections so that cross-platform (CLI/scripted) approaches are presented before or alongside portal-based (GUI) instructions.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/enable-aad-authentication-azure-ssis-ir.md ...ata-factory/enable-aad-authentication-azure-ssis-ir.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 strong Windows bias by exclusively providing PowerShell commands for scripting, referencing only Windows-based tools like SQL Server Management Studio (SSMS), and omitting any Linux or cross-platform alternatives. All automation and CLI examples use PowerShell, and there are no Bash, Azure CLI, or cross-platform instructions. The workflow assumes the use of Windows tools and patterns throughout.
Recommendations
  • Provide equivalent Azure CLI (az) or Bash examples for all PowerShell commands, especially for group and managed identity management.
  • Mention and demonstrate cross-platform tools such as Azure Data Studio for database access and T-SQL execution, in addition to SSMS.
  • Clearly indicate which steps require Windows-only tools and offer alternatives for Linux/macOS users where possible.
  • Reorder sections or provide parallel instructions so that Linux/cross-platform options are presented alongside or before Windows-specific ones.
  • Add a note about platform compatibility for all tools and scripts referenced.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/format-orc.md ...ure-docs/blob/main/articles/data-factory/format-orc.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 page demonstrates Windows bias in the 'Self-hosted Integration Runtime' section. It describes Java runtime detection by first checking the Windows registry, references the installation of Microsoft Visual C++ Redistributable (a Windows-only dependency), and provides no explicit Linux installation or configuration examples. There are no Linux-specific instructions or troubleshooting steps, and the only environment variable example (_JAVA_OPTIONS) is shown in a Windows context.
Recommendations
  • Add explicit instructions for installing and configuring the required Java runtime and dependencies on Linux-based Self-hosted IR machines, including package manager commands (e.g., apt, yum) and file paths.
  • Document how the Self-hosted IR locates the Java runtime on Linux (e.g., reliance on JAVA_HOME or standard Linux paths) and clarify any differences from Windows.
  • If Visual C++ Redistributable is not required on Linux, state this clearly; if an equivalent dependency is needed, provide Linux installation instructions.
  • Provide Linux shell command examples for setting environment variables (e.g., export _JAVA_OPTIONS='-Xms256m -Xmx16g') alongside the Windows examples.
  • Include troubleshooting steps and screenshots relevant to Linux environments where applicable.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/format-parquet.md ...docs/blob/main/articles/data-factory/format-parquet.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 page exhibits Windows bias in several ways. When describing how the Self-hosted Integration Runtime locates the Java runtime, it first references the Windows registry and provides explicit examples and download links for Windows JDK installations. The environment variable examples use Windows-style paths (e.g., C:\Program Files\Java\jdk-23), and there are no Linux-specific instructions, examples, or download links. There is no mention of Linux equivalents for registry lookup, environment variable configuration, or file paths, and no Linux screenshots or shell commands are provided.
Recommendations
  • Add explicit instructions and examples for Linux environments, including setting JAVA_HOME and PATH variables using Linux shell syntax (e.g., export JAVA_HOME=/usr/lib/jvm/java-23-openjdk).
  • Include download links and installation steps for JDK/OpenJDK on Linux, referencing popular distributions (e.g., Ubuntu, CentOS).
  • Clarify how the Self-hosted Integration Runtime locates the Java runtime on Linux (e.g., only via JAVA_HOME, as registry does not exist).
  • Provide Linux-specific troubleshooting steps for JVM heap size configuration (e.g., editing /etc/environment or using export in shell).
  • Use cross-platform file path examples, or provide both Windows and Linux variants side-by-side.
  • Add screenshots or command-line examples from Linux environments where relevant.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-create-tumbling-window-trigger.md .../data-factory/how-to-create-tumbling-window-trigger.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 Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. The PowerShell example is presented first and in detail, with explicit references to Windows paths (e.g., C:\ADFv2QuickStartPSH\MyTrigger.json) and instructions to install Azure PowerShell 'on Windows.' There are no explicit Linux/macOS shell examples (such as Bash), and the CLI section does not clarify cross-platform usage or address Linux-specific considerations. The documentation assumes a Windows environment for file paths and tool installation, and does not mention or show parity for Linux users.
Recommendations
  • Add explicit Bash/Linux shell examples for creating and managing triggers using the Azure CLI, including sample commands for common Linux distributions.
  • When referencing file paths, provide both Windows (e.g., C:\path) and Linux/macOS (e.g., ~/path or /home/user/path) equivalents.
  • Clarify in prerequisites that Azure PowerShell and Azure CLI are cross-platform, and provide installation links and instructions for Linux/macOS users.
  • Present CLI (which is cross-platform) examples before or alongside PowerShell examples to avoid the impression of Windows-first bias.
  • Where screenshots or UI instructions are given, note any platform-specific differences or confirm that the experience is the same across OSes.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-configure-azure-ssis-ir-enterprise-edition.md ...y/how-to-configure-azure-ssis-ir-enterprise-edition.md
High Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell-based instructions for provisioning, referencing Windows authentication for SSAS connectivity, and omitting any Linux or cross-platform alternatives. All setup and configuration steps assume the use of Windows tools and patterns, with no mention of Bash, Azure CLI, or Linux environments.
Recommendations
  • Add equivalent Azure CLI (cross-platform) instructions and examples for provisioning the Azure-SSIS IR Enterprise Edition.
  • Explicitly state platform requirements and clarify if any features are Windows-only, or provide Linux/macOS alternatives where possible.
  • Include Bash or shell script examples alongside PowerShell to support Linux users.
  • Reference cross-platform authentication options (such as service principals or managed identities) in addition to Windows Authentication.
  • Review and update related content to ensure Linux parity and avoid exclusive reliance on Windows tools.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-develop-azure-ssis-ir-licensed-components.md ...ry/how-to-develop-azure-ssis-ir-licensed-components.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 is heavily oriented toward Windows environments, referencing Windows-specific tools (Registry, environment variables, GAC), file paths, and setup executables. There are no Linux examples or instructions, and all technical steps assume a Windows OS. The use of Windows Registry keys, Windows environment variables, and Windows file paths is pervasive, and there is no mention of Linux equivalents or cross-platform considerations.
Recommendations
  • Add explicit statements clarifying OS support and limitations (e.g., if Azure-SSIS IR only runs on Windows, state this up front).
  • If Linux support is possible or planned, provide parallel instructions for Linux environments, including environment variable access, file system paths, and component installation.
  • Where possible, use OS-agnostic terminology or provide both Windows and Linux examples for environment variable access, file storage, and registry/configuration management.
  • Clarify whether custom components or ISV setups can be developed or installed on Linux, and provide guidance for cross-platform development.
  • If the use of Windows-specific features (Registry, GAC, etc.) is required, explain why and suggest alternatives or workarounds for non-Windows environments.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-managed-instance-agent.md ...y/how-to-invoke-ssis-package-managed-instance-agent.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 exclusively references Windows-based tools and workflows, specifically SQL Server Management Studio (SSMS) and Windows authentication, without mentioning or providing alternatives for Linux users. All examples and UI walkthroughs assume the use of SSMS, which is only available on Windows. There are no command-line or cross-platform alternatives provided, and Windows-centric patterns (e.g., UNC paths, Windows authentication) are used throughout.
Recommendations
  • Provide guidance for Linux and macOS users, such as using Azure Data Studio (if supported) or relevant cross-platform tools.
  • Include command-line examples (e.g., using sqlcmd, Azure CLI, or PowerShell Core on Linux) for creating and managing agent jobs.
  • Clarify whether any of the described workflows can be performed via the Azure Portal or REST APIs, and provide examples.
  • Explicitly state the platform requirements and limitations at the beginning of the article.
  • If SSMS is required and only available on Windows, suggest alternatives or workarounds for non-Windows users, or link to relevant resources.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-migrate-ssis-job-ssms.md .../articles/data-factory/how-to-migrate-ssis-job-ssms.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 exclusively references SQL Server Management Studio (SSMS), a Windows-only tool, and the SQL Server Agent, which is also Windows-centric. All migration steps and screenshots are based on SSMS, with no mention of Linux-compatible tools, command-line alternatives, or cross-platform approaches. There are no examples or guidance for users on Linux or macOS platforms, nor is Azure Data Studio (which is cross-platform) discussed as an alternative.
Recommendations
  • Provide guidance or alternatives for Linux and macOS users, such as using Azure Data Studio (if supported) or relevant command-line tools (e.g., sqlcmd, Azure CLI, PowerShell Core).
  • Explicitly state the Windows-only nature of the SSMS-based migration wizard and suggest any cross-platform migration strategies if available.
  • Include examples or references for performing similar migrations using cross-platform tools or APIs, if possible.
  • If no Linux alternative exists, add a note to clarify this and point users to feature requests or roadmap items for Linux support.
GitHub Create Pull Request
Data Factory https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-stored-procedure-activity.md ...tps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-stored-procedure-activity.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 Windows First Missing Linux Example
Summary
The documentation is heavily biased towards Windows and PowerShell. All command-line examples use Azure PowerShell, with explicit references to Windows file paths (e.g., C:\ADF\RunSSISPackage) and no mention of Linux or cross-platform alternatives such as Azure CLI, Bash, or automation via REST API. The use of PowerShell is assumed throughout, and there are no examples or instructions for running these steps on Linux or macOS. Windows-centric tooling and patterns are presented exclusively and before any alternatives.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, demonstrating cross-platform usage.
  • Replace or supplement Windows file paths (e.g., C:\ADF\RunSSISPackage) with Linux/macOS-friendly paths (e.g., ~/ADF/RunSSISPackage) and note cross-platform differences.
  • Explicitly mention that Azure Data Factory and SSIS can be managed from Linux/macOS environments and provide instructions for doing so.
  • Include Bash or shell script examples for file creation and command execution.
  • Reference REST API options for automation, which are platform-agnostic.
  • Add a section or callout highlighting cross-platform support and any limitations.
GitHub Create Pull Request
← Previous Page 4 of 13 Next →