Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 1101-1125 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/continuous-integration-delivery.md
...ticles/data-factory/continuous-integration-delivery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a bias towards Windows environments by exclusively recommending PowerShell scripts for pre- and post-deployment tasks, referencing a .ps1 script, and instructing users to use PowerShell Core in Azure DevOps tasks. There are no examples or guidance for equivalent scripting or automation using Bash, shell scripts, or other Linux-native tools. This may create barriers for users working in Linux-based CI/CD environments.
Recommendations
- Provide equivalent Bash or shell script examples for pre- and post-deployment tasks alongside PowerShell scripts.
- Explicitly mention that PowerShell Core is cross-platform, but also offer native Linux scripting alternatives for users who prefer Bash or other shells.
- Clarify whether the provided PowerShell scripts have been tested and are supported on Linux agents in Azure Pipelines, or provide troubleshooting tips for Linux environments.
- Where possible, avoid language that assumes a Windows-first workflow (e.g., referencing only .ps1 scripts) and instead present both Windows and Linux options equally.
- Include notes or links to community resources for Linux automation in Azure Data Factory CI/CD pipelines.
Create Pull Request
Azure Docs
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 →
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 command examples, referencing Windows file paths (e.g., C:\ADF), and omitting any equivalent instructions or examples for Linux or cross-platform environments. There are no CLI (az), Bash, or platform-neutral alternatives, making it less accessible for Linux or macOS users.
Recommendations
- Add equivalent Azure CLI (az) command examples for all PowerShell scripts, as Azure CLI is cross-platform and widely used on Linux and macOS.
- Include Bash script examples and reference Unix-style file paths (e.g., /home/user/ADF) alongside Windows paths.
- Explicitly state that the instructions apply to both Windows and Linux, and provide guidance for Linux/macOS users where file system or shell differences exist.
- Consider restructuring the 'Example' and 'PowerShell commands' sections to present both PowerShell and CLI/Bash alternatives side-by-side.
- Review all documentation for references to Windows-specific tools or patterns and ensure Linux equivalents are always mentioned or linked.
Azure Docs
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exclusively provides deployment and management instructions using PowerShell commands, which are native to Windows environments. There are no examples or guidance for deploying the ARM template or managing the Azure-SSIS IR using cross-platform tools such as Azure CLI, Bash, or REST API. The only command-line examples are PowerShell-based, and related content links further emphasize PowerShell and Windows-centric workflows. This creates a Windows-first and PowerShell-heavy bias, with Linux and macOS users lacking parity in instructions.
Recommendations
- Add equivalent Azure CLI examples for deploying ARM templates and managing Azure-SSIS IR, as Azure CLI is cross-platform and works on Linux/macOS.
- Include REST API examples or references for users who may wish to automate deployments from non-Windows environments.
- Explicitly mention that PowerShell examples are for Windows, and provide alternative instructions for Linux/macOS users.
- Update related content links to include documentation for cross-platform tools (Azure CLI, REST API) where available.
- Consider adding Bash script examples for common deployment and management tasks.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/control-flow-switch-activity.md
.../articles/data-factory/control-flow-switch-activity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a clear Windows bias. All command-line examples are provided exclusively in PowerShell, with explicit references to Windows file paths (e.g., C:\ADF). There are no examples or instructions for Linux, macOS, or cross-platform tools such as Azure CLI. The only automation/walkthrough is for Azure PowerShell, and there is no mention of how to perform the same tasks on non-Windows systems.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, including pipeline creation, linked service setup, dataset creation, and pipeline execution.
- Use cross-platform file path conventions in examples, or show both Windows (C:\ADF) and Linux/macOS (~/ADF) paths.
- Explicitly mention that the steps can be performed on Linux/macOS using Azure CLI or other cross-platform tools.
- Provide links or references to Linux/macOS-specific quickstarts or tutorials where available.
- Where possible, structure the documentation so that cross-platform tools (like Azure CLI) are presented before or alongside Windows-specific tools (like PowerShell).
Azure Docs
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All command-line examples are provided exclusively using PowerShell, with explicit instructions to use the Windows PowerShell ISE. The installation instructions for the integration runtime do not mention Linux or cross-platform alternatives, and there are no Bash, Azure CLI, or Linux-specific examples or guidance. The only scripting environment referenced is Windows-based, and the documentation does not address Linux users or provide parity for non-Windows environments.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell scripts, as Azure CLI is cross-platform and commonly used on Linux and macOS.
- Include instructions for installing and registering the self-hosted integration runtime on Linux (if supported), or explicitly state platform limitations.
- Replace or supplement references to 'Windows PowerShell ISE' with cross-platform editors or terminal instructions (e.g., VS Code, standard terminal).
- Add a section or notes addressing Linux/macOS users, clarifying any differences or limitations, and providing alternative steps where possible.
- Ensure download and installation instructions for the integration runtime explicitly mention supported platforms and provide links for all OS installers.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/control-flow-until-activity.md
...//articles/data-factory/control-flow-until-activity.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a significant Windows bias. All command-line examples are provided exclusively using PowerShell, with explicit references to Windows file paths (e.g., C:\ADF). There are no examples or instructions for running the same tasks on Linux or macOS, nor are cross-platform tools like Azure CLI or Bash scripts mentioned. The documentation assumes a Windows environment throughout, which may hinder Linux or macOS users.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works on Windows, Linux, and macOS.
- Include Bash script examples for Linux/macOS users, especially for automation scenarios.
- Use platform-agnostic file paths in examples (e.g., /home/user/ADF or ~/ADF) or explain both Windows and Linux/macOS path conventions.
- Explicitly state that the examples are for Windows/PowerShell and provide links or guidance for Linux/macOS users.
- Consider adding a section or callout on cross-platform support, highlighting any differences or additional steps required for non-Windows environments.
Azure Docs
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 →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by referencing only Windows-based tools (SSDT, SSMS, dtutil, AzureDTExec) for deploying and running SSIS packages, without mentioning or providing alternatives for Linux users. There are no Linux or cross-platform command-line examples, and the documentation assumes the use of Windows-centric deployment patterns and tools.
Recommendations
- Explicitly state the platform requirements and limitations for each tool (e.g., SSDT, SSMS, dtutil, AzureDTExec), clarifying if they are Windows-only.
- If Linux or cross-platform options exist (such as Azure Data Factory UI, REST APIs, or Azure CLI), provide equivalent instructions and examples.
- If no Linux-native tools exist, suggest workarounds (e.g., using Azure Data Factory pipeline activities or REST API calls from Linux environments).
- Add a section addressing platform support and guiding Linux users on available options for deploying and running SSIS packages.
- Ensure that references to PowerShell or Windows tools are balanced with mentions of cross-platform alternatives where possible.
Azure Docs
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools (SSDT, SSMS, dtutil, PowerShell) and providing instructions and links for provisioning via Azure PowerShell, with no mention of Linux or cross-platform alternatives. There are no examples or guidance for Linux users, and Windows tools are mentioned first and exclusively throughout the article.
Recommendations
- Include examples and guidance for provisioning Azure-SSIS IR using cross-platform tools such as Azure CLI and REST API, which are available on Linux, macOS, and Windows.
- Mention and provide instructions for using Azure Data Studio, which is cross-platform, as an alternative to SSMS for managing databases and SSISDB.
- When listing tools (e.g., SSDT, SSMS, dtutil), clarify their platform support and suggest any available cross-platform equivalents.
- Add explicit Linux/macOS setup instructions or notes where relevant, especially in the prerequisites and tool installation sections.
- Ensure that PowerShell is not the only command-line example provided; include Azure CLI equivalents for all PowerShell commands.
Azure Docs
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 assumes and prescribes the use of Windows machines or VMs for installing the self-hosted integration runtime (IR), both on-premises and in Azure. There is no mention of Linux support, alternatives, or examples, and all architecture diagrams and best practices reference Windows exclusively. This creates a strong Windows bias and omits guidance for users operating in Linux environments.
Recommendations
- Explicitly state whether the self-hosted integration runtime supports Linux, and if so, provide equivalent instructions and examples for Linux installations.
- If Linux is not supported, clearly mention this limitation early in the documentation to set expectations.
- Include architecture diagrams and workflow descriptions that show Linux-based hosts where applicable.
- Provide parity in best practices and scaling recommendations for Linux environments if supported.
- Reference Linux command-line tools or patterns where relevant, not just Windows-centric approaches.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/create-azure-ssis-integration-runtime-portal.md
...actory/create-azure-ssis-integration-runtime-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Windows environments by referencing PowerShell for backup storage redundancy configuration and mentioning Windows authentication for connecting to on-premises data stores. There are no examples or guidance for equivalent Linux or cross-platform command-line tools, and no mention of Linux-specific considerations or alternatives. The only automation example referenced is via Azure PowerShell, with no mention of Azure CLI or Bash scripting.
Recommendations
- Wherever PowerShell is referenced (e.g., for configuring backup storage redundancy), provide equivalent Azure CLI or Bash examples to support Linux and cross-platform users.
- When mentioning Windows authentication or Windows-specific tools, clarify if and how similar tasks can be performed from Linux or non-Windows environments, or provide links to relevant documentation.
- In the 'Related content' section, add links to guides for creating Azure-SSIS IR via Azure CLI and/or REST API, not just PowerShell and ARM templates.
- Review all instructions and ensure that any command-line or scripting guidance is available for both Windows and Linux users.
- Explicitly state platform requirements or limitations if certain features are only available on Windows, and suggest alternatives for Linux users where possible.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/credentials.md
...e-docs/blob/main//articles/data-factory/credentials.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation consistently references Windows-centric tools and workflows (Azure portal, PowerShell) and omits explicit Linux or cross-platform command-line examples. PowerShell is mentioned as a scripting option, but there are no Bash, Azure CLI, or Linux-native instructions or screenshots. The order of tool mentions (Azure portal, SDK, PowerShell, REST API) also places Windows-preferred tools first.
Recommendations
- Add explicit Azure CLI (cross-platform) examples and instructions alongside or before PowerShell examples.
- Include screenshots or walkthroughs using CLI/Bash where possible, not just the Azure portal UI.
- Mention Linux and macOS compatibility for SDKs and REST APIs, and provide sample commands for these platforms.
- Reorder tool mentions to prioritize cross-platform tools (e.g., Azure CLI, REST API) before Windows-specific ones (PowerShell).
- If possible, provide downloadable script samples in both PowerShell and Bash.
- Clarify that all steps can be performed from Linux/macOS as well as Windows, and link to relevant platform-specific documentation.
Azure Docs
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 →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows tools (such as Command Prompt and nslookup) and omitting any Linux or macOS equivalents. Troubleshooting steps involving the command line only mention Command Prompt, with no mention of Terminal or shell commands for other operating systems. Browser instructions are cross-platform (Edge, Chrome), but all command-line guidance assumes a Windows environment.
Recommendations
- Include Linux/macOS equivalents for all command-line troubleshooting steps. For example, mention using 'Terminal' and provide the same 'nslookup' commands for Linux/macOS users.
- Replace references to 'Command Prompt' with more inclusive language such as 'Open a command-line interface (Command Prompt on Windows, Terminal on Linux/macOS)'.
- Add screenshots or example outputs from Linux/macOS terminals where relevant.
- Explicitly state that the troubleshooting steps apply to all major operating systems, and provide OS-specific instructions where necessary.
Azure Docs
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation provides a PowerShell-only example for creating an Azure Integration Runtime, which is a Windows-centric tool. There are no equivalent examples for Linux users (e.g., using Azure CLI, Bash, or REST API). The PowerShell method is presented first and exclusively as the command-line option, which may alienate or confuse Linux/macOS users. The UI instructions are platform-neutral, but the lack of Linux command-line parity is a significant bias.
Recommendations
- Add equivalent Azure CLI examples for creating and managing Azure Integration Runtime, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Include REST API example(s) for users who prefer direct API calls or automation.
- Reorder or supplement the documentation so that PowerShell and CLI/REST examples are presented together, or with CLI first to emphasize cross-platform support.
- Explicitly mention that PowerShell examples are primarily for Windows users, and provide guidance for Linux/macOS users.
- Consider adding a table summarizing all available methods (PowerShell, CLI, REST, Portal UI) with links to detailed instructions for each.
Azure Docs
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 exhibits a Windows bias by providing PowerShell-based examples for generating and retrieving managed identities, referencing the Azure portal (which is often Windows-centric in screenshots and workflows), and omitting equivalent CLI (az), Bash, or Linux-native instructions. PowerShell is presented as the primary or only scripting interface, and no Linux shell or cross-platform command-line examples are given. This may hinder Linux users or those working in cross-platform environments.
Recommendations
- Add Azure CLI (az) examples for all PowerShell-based instructions, including generating and retrieving managed identities.
- Include Bash shell command examples where applicable, especially for REST API calls (e.g., using curl).
- Present CLI/Bash examples before or alongside PowerShell to avoid the impression that Windows is the default or preferred environment.
- Clarify that all operations can be performed on Linux/macOS as well as Windows, and provide explicit cross-platform guidance.
- Where screenshots or UI flows are shown, note any differences for non-Windows users or provide alternative instructions if needed.
Azure Docs
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
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by repeatedly specifying or recommending the installation of the Data Factory self-hosted integration runtime on Windows machines or Windows VMs, without mentioning Linux as an alternative. There are no examples or guidance for deploying the integration runtime on Linux, and all architectural diagrams and best practices assume a Windows environment. The pricing section also references Azure Windows VMs exclusively. No Linux-specific tools, commands, or deployment patterns are discussed.
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 examples for deploying and managing the integration runtime on Linux machines/VMs.
- Update architectural diagrams and best practices to include both Windows and Linux deployment options.
- Include pricing examples for both Windows and Linux VMs.
- Where authentication or credential management differs between platforms, document those differences.
- If there are platform-specific limitations or recommendations, clearly outline them for both Windows and Linux.
Azure Docs
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 demonstrates a Windows bias in several areas: it relies heavily on PowerShell cmdlets for credential management, references Windows-specific technologies like DPAPI and Windows Firewall, and provides no equivalent Linux examples or guidance. The documentation assumes the use of Windows tools and patterns for on-premises integration runtime scenarios, with no mention of Linux alternatives or parity.
Recommendations
- Provide equivalent Linux-based examples for credential management, such as using Bash scripts or Linux command-line tools.
- Document how to install and operate the self-hosted integration runtime on Linux (if supported), including credential encryption and storage mechanisms.
- Reference Linux firewall configuration (e.g., iptables, firewalld, ufw) alongside Windows Firewall, and provide port configuration instructions for both platforms.
- Clarify whether DPAPI is required or if there is a cross-platform alternative for credential encryption on non-Windows hosts.
- Include Linux-specific troubleshooting and configuration steps wherever Windows-specific instructions are given.
- Where PowerShell cmdlets are used, offer REST API or CLI alternatives that are platform-agnostic.
Azure Docs
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 the self-hosted Integration Runtime (IR) and omitting any mention of Linux support or examples. All instructions for deploying self-hosted IR specify Windows, and there are no Linux-specific guidance, commands, or parity notes. This may give the impression that Linux is unsupported or not recommended, even though self-hosted IR can run on Linux (with some limitations).
Recommendations
- Explicitly mention whether self-hosted Integration Runtime supports Linux, and if so, provide equivalent instructions for deploying on Linux VMs.
- Wherever the documentation says 'install self-hosted IR on a Windows VM', add a note or section for Linux users, including prerequisites and installation steps.
- If there are limitations or differences for Linux-based IR (e.g., features not supported), clearly document them so users can make informed decisions.
- Provide example configurations and monitoring guidance for both Windows and Linux environments.
- Avoid language that implies Windows is the only or default option unless it is truly required.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/includes/data-factory-create-install-integration-runtime.md
...des/data-factory-create-install-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively provides PowerShell commands for all automation steps, references only Windows installation methods and tools (such as 'Add or Remove Programs'), and explicitly instructs users to download and install the integration runtime on a Windows machine. There are no Linux or cross-platform examples, nor any mention of Linux support or alternatives.
Recommendations
- Include equivalent command-line examples for Linux (e.g., using Azure CLI or Bash scripts) where possible.
- Clarify whether the self-hosted integration runtime supports Linux, and if not, state this explicitly at the beginning.
- If Linux is supported, provide installation instructions for Linux (e.g., using .tar.gz packages, apt/yum, or Docker containers).
- Reference cross-platform tools (such as Azure CLI) before or alongside PowerShell, and provide parity in automation examples.
- Replace Windows-specific UI instructions (like 'Add or Remove Programs') with cross-platform alternatives or note platform-specific steps.
Azure Docs
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) for log analytics collection. It provides detailed steps and references for Windows environments, with no mention of Linux-based SHIR deployments or equivalent Linux monitoring tools. All examples and screenshots are Windows-specific, and Linux scenarios are not addressed.
Recommendations
- Add a section describing how to instrument SHIR running on Linux hosts, including installation of the Log Analytics agent for Linux.
- Provide equivalent examples for collecting syslog and Linux performance counters (e.g., using collectd or sysstat) and how to configure them for Log Analytics.
- Reference Azure documentation for installing and configuring the Log Analytics agent on Linux, and link to relevant articles.
- Include screenshots or CLI examples for Linux environments (e.g., using Bash or shell commands) alongside Windows GUI instructions.
- Clarify in the prerequisites and scenario sections whether Linux-based SHIR is supported or not, and if not, explicitly state this to avoid confusion.
Azure Docs
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) and SQL Server Agent, both Windows-only tools, for all procedures. There are no examples or guidance for running or managing SSIS packages from Linux or cross-platform tools. File path examples use Windows UNC paths, and authentication options reference Windows authentication. No Linux equivalents or alternatives are mentioned.
Recommendations
- Provide instructions or references for managing SSIS packages using cross-platform tools (such as Azure Data Studio, if supported, or command-line utilities).
- Clarify whether any steps can be performed from non-Windows environments, and if not, explicitly state the Windows dependency.
- Offer file path examples using both Windows and Linux conventions where applicable, or clarify Azure Files access from Linux.
- If possible, mention or link to any REST APIs, PowerShell Core (cross-platform), or Azure CLI methods that can be used from Linux/macOS.
- Discuss authentication options available on non-Windows platforms, or clarify that Windows authentication is required.
Azure Docs
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 referencing and illustrating the use of SQL Server Management Studio (SSMS) and Object Explorer for configuration, both of which are primarily Windows tools. The instructions for configuring and managing SSISDB log clean-up rely on SSMS and do not mention cross-platform alternatives or command-line options. There are no examples or guidance for users on Linux or macOS, nor is Azure Data Studio (a cross-platform tool) mentioned. PowerShell is used for automation, but no Bash or CLI equivalents are provided.
Recommendations
- Include instructions for configuring SSISDB log clean-up properties using T-SQL scripts that can be run from any platform, not just via SSMS GUI.
- Mention and provide examples using Azure Data Studio, which is cross-platform, for connecting to and managing SSISDB.
- Provide Azure CLI and Bash script equivalents for the PowerShell automation steps, especially for Elastic Database Jobs setup.
- Explicitly state that SSMS is a Windows-only tool and suggest alternatives for non-Windows users.
- Ensure all code and configuration steps can be performed from Linux/macOS environments, and provide at least one end-to-end example using only cross-platform tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/data-factory/includes/data-factory-quickstart-prerequisites.md
...tory/includes/data-factory-quickstart-prerequisites.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and patterns (e.g., Notepad, C:\ path), omitting Linux/macOS equivalents, and providing file/folder creation instructions only in a Windows context. There are no examples or guidance for Linux or macOS users for tasks like creating files or folders, or for using cross-platform tools.
Recommendations
- Include instructions for creating the emp.txt file using Linux/macOS tools (e.g., nano, vim, or echo command).
- Provide examples of file paths using both Windows (C:\ADFv2QuickStartPSH) and Linux/macOS (/home/user/ADFv2QuickStartPSH or ~/ADFv2QuickStartPSH) conventions.
- Mention cross-platform text editors (e.g., VS Code, nano) instead of only Notepad.
- Clarify that the Azure portal steps are OS-agnostic, but local file operations may differ by platform.
- Add a note or section for Linux/macOS users to ensure parity and inclusivity.
Azure Docs
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
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation is heavily Windows-centric, with all examples, tools, and scripts tailored for Windows environments. Only Windows commands (e.g., cmdkey, set, msiexec), Windows file paths, and Windows-specific tools are mentioned. PowerShell is the only scripting interface referenced for automation, and there are no examples or guidance for Linux or cross-platform environments. The documentation assumes the underlying platform is Windows and does not acknowledge or provide alternatives for Linux users.
Recommendations
- Explicitly state that Azure-SSIS IR currently only supports Windows-based runtimes, if that is the case. If Linux support is planned or available, provide equivalent Linux/bash examples and instructions.
- Wherever Windows commands or tools are mentioned (e.g., cmdkey, set, msiexec), add notes or alternatives for Linux environments, or clarify that these steps are not applicable to Linux.
- If PowerShell is the only supported automation interface, clarify this limitation early in the documentation. If bash or other scripting options are available, provide corresponding examples.
- Review all sample scripts and setup instructions to ensure they are either cross-platform or clearly marked as Windows-only. Consider providing a table or section comparing Windows and Linux setup steps if both are supported.
- For third-party component installation, indicate whether Linux-compatible versions exist or if the components are Windows-only.
- Add a section on platform requirements and limitations, highlighting the OS support for Azure-SSIS IR and its custom setup features.
Azure Docs
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, instructions, and references are specific to Windows tools and patterns, such as the use of Windows environment variables, Windows Registry, Windows file paths, and the Global Assembly Cache (GAC). There are no Linux equivalents or cross-platform considerations mentioned, and the documentation assumes the use of Windows throughout.
Recommendations
- Provide explicit statements about platform support, clarifying whether Linux-based Azure-SSIS IR nodes are supported or not.
- If Linux support exists or is planned, add parallel instructions and examples for Linux environments, including environment variable access, file paths, and component installation.
- Mention Linux equivalents (if any) for Windows-specific concepts like the Registry and GAC, or provide alternative approaches for license storage and component registration.
- Include a section that addresses cross-platform compatibility and any limitations or differences when running on non-Windows platforms.
- If only Windows is supported, clearly state this at the beginning of the documentation to set expectations for users on other platforms.
Azure Docs
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 exclusively provides instructions and examples using Azure PowerShell, a Windows-centric tool, without mentioning or providing alternatives for Linux users (such as Azure CLI or REST API). It also references Windows Authentication for SSAS connectivity, further reinforcing a Windows-first approach. No Linux or cross-platform setup guidance is given.
Recommendations
- Add equivalent instructions and examples using Azure CLI, which is cross-platform and widely used on Linux.
- Mention REST API options for provisioning and configuring Azure-SSIS IR, providing sample requests.
- Clarify whether the Azure-SSIS IR can be provisioned and managed from Linux/macOS environments, and if so, provide guidance.
- When referencing authentication methods (such as Windows Authentication), note any Linux-compatible alternatives or limitations.
- Ensure that all tooling references (e.g., installation steps) include both Windows and Linux/macOS options where possible.