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 626-650 of 1000 flagged pages
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/connector-upgrade-guidance.md
...in/articles/data-factory/connector-upgrade-guidance.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides only a PowerShell script example for programmatically finding impacted objects, with no mention of Linux-compatible alternatives (such as Bash, Azure CLI, or Python). This assumes a Windows environment and omits guidance for users on Linux or macOS platforms.
Recommendations
- Provide equivalent examples using Azure CLI and/or Bash scripts for Linux/macOS users.
- Mention cross-platform scripting options (e.g., Python SDK, REST API) and link to relevant documentation.
- Clarify whether the provided PowerShell script can run on PowerShell Core (pwsh) on Linux/macOS, and provide installation guidance if so.
- Ensure that future documentation includes both Windows and Linux/macOS approaches for programmatic tasks.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples for generating and retrieving managed identities, referencing the Azure portal (which is often more familiar to Windows users), and omitting equivalent CLI (az CLI), Bash, or Linux-native examples. PowerShell is presented as the primary or only scripting interface, and there are no Linux/Unix shell or cross-platform command-line examples. This may disadvantage users working on Linux or macOS environments.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Explicitly mention that PowerShell commands can be run on any platform with PowerShell Core, or provide Bash alternatives where possible.
- When listing methods (e.g., 'using PowerShell, REST API, SDK'), include Azure CLI as a first-class option.
- For retrieving managed identities, provide az CLI commands (e.g., az datafactory show ...) alongside PowerShell.
- Balance the order of presentation so that Windows-specific tools (PowerShell) are not always listed before cross-platform tools (CLI, REST, SDK).
- Include notes or links for users on Linux/macOS about how to accomplish the same tasks in their environments.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the primary or sole automation method for working with Data Flow Script outside the UI. There are no examples or mentions of Linux or cross-platform alternatives (such as Bash, CLI, or REST API usage from non-Windows environments). The documentation assumes the user is familiar with PowerShell and Windows tooling, and does not provide parity for Linux users.
Recommendations
- Include equivalent examples using Azure CLI and/or Bash scripts for generating and submitting Data Flow Scripts, alongside the PowerShell example.
- Explicitly mention that the Data Flow Script can be used with REST APIs, and provide a sample using curl or similar Linux-native tools.
- Rephrase sections that mention PowerShell as the default or only automation method to clarify that cross-platform options exist.
- Add a 'Platform compatibility' note early in the document, highlighting that all features are available on both Windows and Linux, and link to relevant cross-platform tooling.
- Where automation is discussed, present Windows and Linux options side-by-side or in parallel sections, rather than Windows-first or Windows-only.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-spark-powershell.md
...ta-factory/tutorial-transform-data-spark-powershell.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All command-line instructions are provided exclusively using Azure PowerShell, with no mention of Azure CLI, Bash, or cross-platform alternatives. The prerequisite section specifically requires Azure PowerShell, and all deployment and monitoring steps are shown only with PowerShell scripts. There are no examples or guidance for Linux or macOS users, nor is there mention of how to perform these tasks using non-Windows tools.
Recommendations
- Add equivalent instructions using Azure CLI, which is cross-platform and works natively on Linux, macOS, and Windows.
- Provide Bash shell script examples for Linux/macOS users alongside PowerShell examples.
- In the prerequisites, mention both Azure PowerShell and Azure CLI as supported options, with links to installation guides for each.
- Clearly indicate in each step whether the instructions are for Windows/PowerShell or for Linux/Bash, and provide both where possible.
- Consider including a table or section comparing the commands in PowerShell and Bash/Azure CLI to help users choose the best fit for their environment.
- Review the use of terms like 'launch PowerShell' and replace with more inclusive language such as 'open your terminal or command prompt'.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by repeatedly specifying or implying the use of Windows machines for installing the Data Factory self-hosted integration runtime, without mentioning Linux as an alternative. All architecture diagrams and implementation instructions refer to Windows VMs, and the pricing section explicitly excludes only 'Azure Windows VM' costs, reinforcing the perception that Windows is the default or only supported platform. There are no examples or guidance for Linux-based hosts, nor any mention of Linux-specific considerations or parity.
Recommendations
- Explicitly state that the Data Factory self-hosted integration runtime can be installed on both Windows and Linux, if supported.
- Provide parallel instructions and architecture diagrams for deploying the integration runtime on Linux machines (both on-premises and in Azure).
- Include Linux-specific best practices, such as recommended VM sizes, scaling guidance, and monitoring tools.
- Update authentication and credential management sections to mention any Linux-specific configuration steps or Kerberos integration nuances.
- In pricing and implementation examples, include Linux VM cost estimates and performance considerations.
- Wherever a Windows VM is referenced, add 'or Linux VM' to ensure parity and inclusivity.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-migration-guidance-overview.md
...icles/data-factory/data-migration-guidance-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias by referencing Windows-specific tools (e.g., Windows Installer/MSI) for security integration and not mentioning Linux equivalents or alternatives. There are no command-line examples, but the only authentication mechanism mentioned is Windows-centric. Linux tools, patterns, or authentication methods are not discussed, and there is no guidance for Linux users regarding self-hosted integration runtime or credential management.
Recommendations
- Include Linux-friendly authentication and integration options, such as service principals, managed identities, or instructions for installing the self-hosted integration runtime on Linux.
- Mention cross-platform alternatives to Windows Installer (MSI), such as tarball or shell script installation methods for self-hosted IR.
- Provide parity in documentation by explicitly stating how Linux users can achieve secure service-to-service integration and credential management.
- If examples or step-by-step guides are added, ensure both Windows and Linux command-line instructions are included.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-migration-guidance-netezza-azure-sqldw.md
...factory/data-migration-guidance-netezza-azure-sqldw.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation consistently refers to installing the Azure Data Factory self-hosted integration runtime (IR) on Windows machines or VMs, both on-premises and in Azure. There is no mention of Linux support or examples, nor are Linux tools or patterns discussed. Windows is presented as the default and only supported platform for the self-hosted IR, and all scaling and configuration guidance is Windows-specific.
Recommendations
- Explicitly state platform support for the self-hosted integration runtime, including whether Linux is supported or not. If not, clarify this early in the documentation.
- If Linux is supported, provide equivalent instructions, examples, and best practices for installing and configuring the self-hosted IR on Linux systems.
- Include Linux-specific considerations for scaling, monitoring, and troubleshooting the self-hosted IR.
- If only Windows is supported, suggest possible workarounds for Linux environments (e.g., using Windows containers or VMs) and explain the rationale.
- Ensure that any references to 'machines' or 'VMs' clarify the required operating system, and avoid assuming Windows by default.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows VMs for self-hosted Integration Runtime (IR) installation and configuration. There are no examples or guidance for deploying self-hosted IR on Linux, nor is there mention of Linux compatibility or alternatives. The only recommended pattern for private network scenarios is to use a Windows VM, and all scaling and monitoring advice is Windows-specific.
Recommendations
- Explicitly state whether self-hosted Integration Runtime is supported on Linux, and if so, provide equivalent instructions for deploying and managing IR on Linux VMs.
- Include Linux-based examples and configuration guidance alongside Windows instructions, especially for scenarios involving self-hosted IR.
- If Linux is not supported, clarify this limitation early in the documentation to set expectations for cross-platform users.
- When recommending VM sizes or monitoring strategies, provide guidance for both Windows and Linux environments where applicable.
- Review all references to 'Windows VM' and consider using neutral language such as 'VM' or 'host machine', specifying OS-specific steps only when necessary.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/data-movement-security-considerations.md
.../data-factory/data-movement-security-considerations.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: it provides only PowerShell cmdlet examples for credential management, references Windows-specific tools and APIs (such as DPAPI and Windows Firewall), and omits equivalent Linux tools or instructions. The documentation assumes a Windows environment for self-hosted integration runtime, credential encryption, and firewall configuration, without mentioning or providing guidance for Linux-based deployments.
Recommendations
- Provide equivalent Linux command-line examples (e.g., Bash scripts, az CLI) alongside PowerShell cmdlets for credential management and integration runtime setup.
- Document how credential encryption and storage are handled on Linux hosts, including which APIs or mechanisms are used instead of Windows DPAPI.
- Include instructions for configuring firewalls on Linux (e.g., iptables, firewalld, ufw) in addition to Windows Firewall.
- Clarify whether the self-hosted integration runtime is supported on Linux, and if so, provide Linux-specific installation, configuration, and security guidance.
- Ensure that all references to tools, ports, and configuration steps are cross-platform or have platform-specific sections, so Linux users are not left without guidance.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/encrypt-credentials-self-hosted-integration-runtime.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/encrypt-credentials-self-hosted-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses PowerShell cmdlets (New-AzDataFactoryV2LinkedServiceEncryptedCredential, Set-AzDataFactoryV2LinkedService), which are primarily Windows-centric and require PowerShell 7.0 or higher. There are no examples or instructions for performing the same tasks on Linux or macOS, nor are cross-platform alternatives (such as Azure CLI, REST API, or Bash scripts) mentioned. The use of DPAPI for encryption is also a Windows-specific technology.
Recommendations
- Provide equivalent examples using Azure CLI or REST API, which are cross-platform and can be run on Linux and macOS.
- Clarify whether the encryption process and cmdlets are supported on non-Windows platforms, especially since PowerShell 7 is cross-platform but DPAPI is not.
- If the process is inherently Windows-only (due to DPAPI or integration runtime limitations), explicitly state this limitation early in the documentation.
- Offer guidance or workarounds for Linux users, such as running the commands in a Windows container or VM, or alternative credential management approaches.
- Reorder or supplement examples so that Linux/macOS approaches are presented alongside or before Windows-specific instructions where possible.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/tutorial-transform-data-hive-virtual-network.md
...actory/tutorial-transform-data-hive-virtual-network.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All command-line instructions are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux equivalents. Windows-specific tools and file paths (such as editing the hosts file at C:\Windows\System32\drivers\etc) are referenced without Linux alternatives. The workflow assumes the user is operating from a Windows environment, and there are no examples or guidance for users on Linux or macOS.
Recommendations
- Provide equivalent Azure CLI (az) commands for all PowerShell examples, as Azure CLI is cross-platform and works on Linux, macOS, and Windows.
- Include instructions for editing the hosts file on Linux (typically /etc/hosts) alongside the Windows path.
- Mention that the self-hosted integration runtime can be installed on Linux (if supported), or clarify platform limitations.
- Add notes or examples for users working from Linux or macOS, especially for file operations, command-line usage, and environment setup.
- Where screenshots or UI steps are shown, clarify if they are Windows-specific and provide Linux/macOS alternatives if available.
- Consider reordering sections or providing parallel instructions so that Linux/macOS users do not feel like an afterthought.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exhibits a strong Windows bias. All command-line examples use PowerShell, and there are no CLI or Bash equivalents provided. The required tooling for several steps (Microsoft Entra PowerShell, Azure PowerShell, SQL Server Management Studio) are Windows-centric, with no mention of cross-platform alternatives. Instructions for connecting to Azure SQL resources are given exclusively with SSMS, which is only available on Windows. No Linux or macOS workflows are described or referenced.
Recommendations
- Provide Azure CLI and/or Bash script equivalents for all PowerShell commands, especially for group and identity management.
- Mention and demonstrate the use of cross-platform tools such as Azure Data Studio for SQL tasks, or provide T-SQL scripts that can be run from any SQL client.
- Explicitly state which steps require Windows-only tools and offer alternatives or workarounds for Linux/macOS users.
- Reorder or parallelize examples so that cross-platform methods are presented alongside Windows-specific ones, rather than only after or not at all.
- Add a section or notes on how to perform each step from Linux/macOS environments, including installation and authentication steps.
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 →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the section on configuring Java for Self-hosted Integration Runtime. It describes the Java runtime discovery process as checking the Windows registry first, provides download links to Windows-specific JDK installers, and gives environment variable examples using Windows paths (e.g., C:\Program Files\Java\jdk-23). There are no explicit Linux or macOS instructions, examples, or path conventions, and no mention of Linux-specific installation or troubleshooting steps.
Recommendations
- Add explicit instructions for installing and configuring JRE/JDK/OpenJDK on Linux (and optionally macOS), including package manager commands (e.g., apt, yum) and typical installation paths (e.g., /usr/lib/jvm/java-23-openjdk).
- Clarify how the Self-hosted IR locates Java on Linux (e.g., does it use JAVA_HOME, PATH, or other mechanisms?).
- Provide Linux-specific examples for setting environment variables (e.g., export JAVA_HOME=/usr/lib/jvm/java-23-openjdk, export _JAVA_OPTIONS="-Xms256m -Xmx16g").
- Include troubleshooting tips for common Linux issues (e.g., permissions, library paths, service restarts).
- When mentioning download links, provide cross-platform options or clarify which links are for Windows and which are for Linux/macOS.
- Use neutral language and path examples (or provide both Windows and Linux/macOS variants) when describing configuration steps.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-clean-up-ssisdb-logs-with-elastic-jobs.md
...ctory/how-to-clean-up-ssisdb-logs-with-elastic-jobs.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-based tools (such as SQL Server Management Studio and Azure PowerShell), providing step-by-step instructions for SSMS (a Windows-only application), and omitting any guidance or examples for Linux or cross-platform alternatives. There are no examples using Azure CLI, cross-platform SQL clients, or Linux-native automation tools. The documentation assumes the user is operating in a Windows environment.
Recommendations
- Include instructions for connecting to SSISDB and configuring properties using cross-platform tools such as Azure Data Studio, Azure CLI, or sqlcmd, which are available on Linux and macOS.
- Provide examples of automating SSISDB log cleanup using bash scripts, Azure CLI, or Python, in addition to PowerShell.
- Mention and demonstrate how to perform relevant tasks using Azure Portal UI, which is OS-agnostic.
- Explicitly state that SSMS is Windows-only and suggest cross-platform alternatives for users on Linux or macOS.
- Ensure that all automation and scripting examples are provided in both PowerShell and bash/Azure CLI where possible.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-configure-azure-ssis-ir-custom-setup.md
...factory/how-to-configure-azure-ssis-ir-custom-setup.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments. All examples, tools, and scripts assume a Windows OS context (e.g., .cmd, .bat, .exe, .msi, PowerShell). Windows-specific commands (cmdkey, set, msiexec, odbcconf) and tools (Azure PowerShell, Azure Storage Explorer) are used exclusively. There are no Linux or cross-platform examples, and Linux equivalents are not mentioned. The documentation presumes the reader is operating in a Windows environment, with no guidance for Linux users.
Recommendations
- Clearly state early in the documentation that Azure-SSIS IR is Windows-based, if that is a technical limitation. If not, provide Linux support or clarify cross-platform capabilities.
- If Linux customization is possible, add equivalent Linux/bash examples and instructions (e.g., shell scripts, Linux tools, az CLI usage).
- Where Windows tools are referenced (e.g., msiexec, cmdkey, PowerShell), mention if there are Linux alternatives or explicitly state if only Windows is supported.
- For scripting, provide bash or Python examples alongside .cmd/.ps1 where feasible.
- If Azure Storage Explorer is required, mention az CLI or other cross-platform alternatives.
- Explicitly document any OS limitations or requirements up front, so non-Windows users can quickly determine applicability.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell-based instructions and examples for provisioning the Azure-SSIS Integration Runtime. It references Windows authentication and Windows-specific tools without mentioning or providing alternatives for Linux or cross-platform environments. There are no Bash, CLI, or Linux-native instructions or examples, and all setup steps assume a Windows-centric workflow.
Recommendations
- Provide equivalent instructions using Azure CLI (az commands), which is cross-platform and works on Linux, macOS, and Windows.
- Include Bash script examples for provisioning and configuring the Azure-SSIS IR.
- Clarify whether the features and setup steps are supported or possible on Linux-based environments, and if not, explicitly state the platform limitations.
- Reference cross-platform authentication methods or alternatives to Windows Authentication where possible.
- Add a section or note addressing Linux/macOS users, guiding them to appropriate tools and commands.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-configure-shir-for-log-analytics-collection.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-configure-shir-for-log-analytics-collection.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows tools and workflows (such as Event Viewer logs and Windows Performance Counters), providing links and instructions only for Windows-based Log Analytics agent installation, and omitting any mention of Linux equivalents or guidance for Linux-based SHIR hosts. There are no examples, instructions, or references for configuring log analytics collection on Linux systems.
Recommendations
- Add a section describing how to instrument Linux-based SHIR hosts for log analytics collection, including installation of the Log Analytics agent on Linux and relevant prerequisites.
- Provide equivalent examples for configuring log collection and performance counters on Linux (e.g., syslog, Linux performance counters, or custom logs).
- Include links to Azure documentation for installing and configuring the Log Analytics agent on Linux virtual machines.
- Clearly indicate in each section whether the instructions apply to Windows, Linux, or both, and provide parity in guidance and screenshots.
- Mention any limitations or differences in monitoring capabilities between Windows and Linux SHIR hosts.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-create-schedule-trigger.md
...rticles/data-factory/how-to-create-schedule-trigger.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation demonstrates a moderate Windows bias, particularly in the Azure PowerShell section. It provides explicit instructions for installing Azure PowerShell 'on Windows with PowerShellGet' and uses Windows file paths (e.g., C:\ADFv2QuickStartPSH\MyTrigger.json) in code samples. The PowerShell section appears before the Azure CLI section, and the prerequisites for PowerShell are Windows-specific, potentially excluding Linux/macOS users. However, the Azure CLI and SDK sections are cross-platform and do not show similar bias.
Recommendations
- In the Azure PowerShell section, clarify that Azure PowerShell is cross-platform and provide installation instructions for Linux and macOS, or link to the general installation guide.
- Use platform-agnostic file paths in code samples (e.g., ./MyTrigger.json or $HOME/ADFv2QuickStartPSH/MyTrigger.json), or provide both Windows and Linux/macOS examples.
- When listing command-line approaches, consider presenting Azure CLI before PowerShell, as CLI is more universally available across platforms.
- Add explicit notes or callouts that all SDK and CLI examples work on Linux, macOS, and Windows.
- Where possible, avoid language or screenshots that assume a Windows environment unless the tool is truly Windows-only.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented toward Windows environments. All examples and instructions reference Windows-specific tools and concepts, such as the Windows Registry, Windows environment variables, and Windows file paths. There are no examples or guidance for Linux environments, and the documentation assumes the use of Windows throughout.
Recommendations
- Provide equivalent instructions and examples for Linux environments, if supported by Azure-SSIS IR or self-hosted IR.
- Clarify early in the documentation whether Linux is supported or not for these scenarios. If not, state this explicitly.
- If Linux support is planned or possible, include Linux-specific paths, environment variable handling, and installation steps alongside Windows instructions.
- Where Windows Registry is referenced, suggest equivalent configuration mechanisms for Linux (such as configuration files or environment variables).
- When showing file paths or commands, provide both Windows and Linux syntax where applicable.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation demonstrates a Windows bias in several ways: the PowerShell sample is presented first and is specifically tied to Windows (with instructions to install Azure PowerShell on Windows and to create files in a Windows path, e.g., C:\ADFv2QuickStartPSH\). The CLI example is more cross-platform, but the overall structure and ordering prioritize Windows-centric tools and workflows. There are no explicit Linux shell or scripting examples, and the PowerShell instructions do not mention cross-platform compatibility.
Recommendations
- Add explicit Linux/macOS instructions for creating and managing the JSON file (e.g., use ~/ADFv2QuickStart/ or /tmp/ paths in addition to C:\).
- Clarify that Azure PowerShell is cross-platform and provide installation links for Linux/macOS, or add a note about using PowerShell Core on non-Windows systems.
- Consider presenting the Azure CLI example first, as it is natively cross-platform and more familiar to Linux users.
- Add bash shell examples for common tasks (e.g., using jq or curl with the REST API for trigger management).
- Review all file path examples and ensure both Windows and Linux/macOS formats are shown where relevant.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-azure-enabled-dtexec.md
...ory/how-to-invoke-ssis-package-azure-enabled-dtexec.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing Windows tools (SSMS, AzureDTExec.exe), providing only Windows command-line examples, and omitting any mention of Linux or cross-platform usage. The installation, configuration, and invocation instructions all assume a Windows environment, with no guidance for Linux users or alternatives for running SSIS packages outside of Windows.
Recommendations
- Explicitly state whether AzureDTExec and SSMS are available or supported on Linux or macOS. If not, clarify this early in the documentation.
- If cross-platform support exists (e.g., via .NET Core, Docker, or Azure CLI), provide equivalent Linux/macOS installation and usage instructions.
- Include Linux shell (bash) command-line examples alongside Windows examples, or clarify that only Windows is supported.
- Mention any alternative tools or workflows for Linux users who need to run SSIS packages in Azure Data Factory.
- Avoid assuming the presence of Windows-specific features (like 'Run as administrator', UAC, or UNC paths) without noting their absence or alternatives on other platforms.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-ssis-activity.md
...ta-factory/how-to-invoke-ssis-package-ssis-activity.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias by exclusively referencing Windows authentication, UNC paths, and Windows-centric tools (such as SQL Server Data Tools, SQL Server Management Studio, and the dtutil utility). All file path examples use Windows UNC syntax, and there are no Linux or cross-platform alternatives or examples. There is no mention of Linux-based authentication, file storage, or tooling, nor any guidance for users operating from non-Windows environments.
Recommendations
- Provide Linux-compatible examples for file paths (e.g., Azure Files mounted via SMB on Linux, or using Azure Blob Storage with SAS tokens).
- Mention and, where possible, demonstrate authentication mechanisms that work on Linux (such as Azure AD authentication or SAS tokens) in addition to Windows authentication.
- Reference cross-platform tools for package development and deployment, or clarify if certain steps require Windows-only tools (like SSDT or SSMS).
- Explicitly state any platform limitations (e.g., if only Windows-based Azure-SSIS IR is supported, or if Linux is not supported for certain features).
- Where possible, provide guidance or links for Linux users to set up and interact with Azure Data Factory and SSIS packages.
- Include notes or examples for managing secrets and credentials using cross-platform methods (such as Azure CLI or REST APIs) instead of only GUI-based or Windows-centric approaches.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references SQL Server Management Studio (SSMS), a Windows-only tool, for all procedures. All examples and UI walkthroughs are based on SSMS, with no mention of cross-platform or Linux alternatives. File path examples use Windows UNC paths, and authentication options reference Windows authentication. There are no instructions or guidance for users on Linux or macOS platforms.
Recommendations
- Provide equivalent instructions using cross-platform tools such as Azure Data Studio or command-line utilities (e.g., sqlcmd, Azure CLI) where possible.
- Explicitly state the platform requirements and, if SSMS is mandatory, clarify that it is Windows-only and suggest workarounds for non-Windows users (such as using a Windows VM or remote desktop).
- Include examples of file paths and authentication methods relevant to Linux environments, or clarify limitations.
- If no Linux-native options exist, acknowledge this in the documentation and provide guidance for Linux users on how to proceed.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-invoke-ssis-package-ssdt.md
...ticles/data-factory/how-to-invoke-ssis-package-ssdt.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented toward Windows environments, specifically Visual Studio and SQL Server Data Tools (SSDT), both of which are Windows-only tools. All instructions, UI references, and workflows assume the use of Windows, with no mention of Linux or cross-platform alternatives. There are no Linux-specific examples or guidance, and Windows authentication is discussed without reference to Linux-compatible authentication methods.
Recommendations
- Explicitly state that SSDT and Visual Studio are Windows-only and note the lack of Linux support up front.
- If possible, provide alternative methods for developing, deploying, or executing SSIS packages from Linux environments (e.g., using Azure Data Factory UI, Azure CLI, or REST APIs).
- Include references to cross-platform tools or document workarounds for Linux users, such as using remote Windows VMs or containers.
- Clarify authentication options for non-Windows environments, or explicitly state if only Windows authentication is supported.
- If no Linux support exists, add a section addressing this limitation and suggest feature requests or alternatives for Linux users.
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references SQL Server Management Studio (SSMS) and SQL Server Agent, both of which are Windows-only tools. All instructions, screenshots, and workflow steps assume the use of SSMS on Windows, with no mention of Linux or cross-platform alternatives. There are no examples or guidance for users on Linux or macOS, nor are command-line or platform-agnostic methods provided.
Recommendations
- Acknowledge in the prerequisites or introduction that SSMS and SQL Server Agent are Windows-only tools, and clarify if there are any supported alternatives for Linux/macOS users.
- If possible, provide guidance or references for performing similar migrations using cross-platform tools such as Azure Data Studio, Azure CLI, or PowerShell Core (which is cross-platform).
- Include a note or section addressing Linux users, outlining any available options or workarounds, or explicitly state if the migration process is only supported from Windows environments.
- Consider adding command-line examples (e.g., using Azure CLI or REST API) for steps such as ARM template deployment, to improve parity for non-Windows users.