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 451-475 of 1000 flagged pages
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 Tools
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation is heavily biased toward Windows environments. It exclusively references Windows tools (SSMS, AzureDTExec.exe), Windows installation paths, and Windows-specific patterns (UNC paths, 'Run as administrator', UAC prompts). All examples and configuration steps assume a Windows OS, with no mention of Linux equivalents, cross-platform alternatives, or usage on non-Windows systems.
Recommendations
- Clarify whether AzureDTExec and SSMS are available or supported on Linux or macOS. If not, explicitly state this limitation.
- If cross-platform support exists, provide installation and usage instructions for Linux/macOS, including command-line examples and file paths.
- Offer alternative methods for running SSIS packages in Azure Data Factory that do not require Windows-only tools, or reference third-party cross-platform solutions if available.
- Avoid Windows-specific terminology (e.g., 'Run as administrator', UAC) or provide equivalent steps for other operating systems.
- Include Linux/macOS examples for invoking the utility, setting environment variables, and accessing files (e.g., using SMB/CIFS mounts, or Azure Files from Linux).
Create Pull Request
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 Authentication Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias throughout. It repeatedly references Windows authentication, UNC paths (Windows file system convention), and Windows-centric tools such as SQL Server Data Tools (SSDT) and SQL Server Management Studio (SSMS). There is no mention of Linux equivalents, nor any examples or guidance for Linux-based environments. All authentication, file access, and package management instructions assume Windows paradigms, and there are no alternative instructions for Linux users.
Recommendations
- Add explicit guidance for Linux-based Azure-SSIS IR scenarios, if supported, or clarify platform limitations.
- Include examples using Linux file system paths (e.g., NFS, SMB mounts) and authentication methods relevant to Linux.
- Document how to manage SSIS packages and configuration files from Linux environments, including any supported tools or command-line utilities.
- If SSDT and SSMS are required and only available on Windows, state this clearly and suggest alternatives or workarounds for Linux users.
- Provide parity in authentication examples, such as using Azure AD or other cross-platform methods, not just Windows authentication.
- Where UNC paths are referenced, explain how Linux users can access Azure Files (e.g., via SMB/CIFS mounts) and provide sample mount commands.
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 Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools and workflows, such as SQL Server Management Studio (SSMS) and SQL Server Agent, for configuring and scheduling SSISDB log clean-up. All UI walkthroughs and screenshots are based on SSMS, with no mention of Linux-native management tools or cross-platform alternatives. There are no examples or instructions for performing these tasks from Linux environments or using Linux-compatible tools. PowerShell is mentioned for Azure automation, but Bash or CLI alternatives are not provided.
Recommendations
- Add instructions and examples for managing SSISDB log clean-up using Azure CLI and Bash scripts, which are cross-platform and Linux-friendly.
- Mention and provide guidance for connecting to Azure SQL and SSISDB from Linux using tools like Azure Data Studio, sqlcmd, or other open-source SQL clients.
- Include screenshots and UI walkthroughs for Azure Data Studio or other cross-platform tools, not just SSMS.
- Clarify that all T-SQL scripts can be executed from Linux environments using sqlcmd or Azure Data Studio, and provide sample command lines.
- Where PowerShell is used, offer equivalent Bash/CLI commands for Linux users.
- Explicitly state platform requirements and alternatives for each management scenario, ensuring Linux users are not excluded.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-assess-your-azure-data-factory-to-fabric-data-factory-migration.md
...ur-azure-data-factory-to-fabric-data-factory-migration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation repeatedly references the PowerShell upgrade tool as the primary or sole method for migration, without mentioning Linux-compatible alternatives or providing cross-platform examples. There is no mention of CLI, Bash, or other Linux-native tools, and all migration tooling guidance is Windows-centric.
Recommendations
- Add instructions and examples for using Azure CLI or REST API for migration, if available.
- Explicitly mention whether the PowerShell upgrade tool can be run on Linux (via PowerShell Core), and provide installation guidance for non-Windows platforms.
- Provide parity by listing Linux/Bash alternatives alongside PowerShell, or clarify platform requirements for migration tools.
- Include a note on cross-platform support and limitations for migration tooling.
- Ensure screenshots and step-by-step guides do not assume a Windows environment unless unavoidable.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias. All command-line automation examples are provided exclusively using Azure PowerShell, with explicit references to Windows file paths (e.g., C:\ADF\RunSSISPackage), and no mention of Linux-compatible alternatives (such as Azure CLI, Bash, or cross-platform scripting). The documentation assumes the use of Windows tooling and environments, and does not provide parity for Linux or cross-platform users.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and work on Linux, macOS, and Windows.
- Replace or supplement Windows file paths (e.g., C:\ADF\RunSSISPackage) with platform-agnostic or Linux/macOS alternatives (e.g., ~/ADF/RunSSISPackage).
- Explicitly mention that the steps can be performed on Linux/macOS, and provide any necessary prerequisites or differences (such as using Bash instead of PowerShell).
- Include Bash or shell script examples for automation tasks, or at least reference how Linux users can perform the same actions.
- Clarify in the prerequisites or introduction that the PowerShell section is Windows-centric, and link to cross-platform documentation where available.
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
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation is heavily oriented toward Windows environments, with all examples, tools, and setup scripts referencing Windows-specific commands, file types, and utilities (e.g., .cmd, .bat, .exe, PowerShell, msiexec.exe, cmdkey, Windows environment variables). There is no mention of Linux equivalents, nor any guidance for users who may wish to customize Azure-SSIS IR using Linux-based tooling or scripts. The use of PowerShell is pervasive, and all component installation instructions assume a Windows runtime and ecosystem.
Recommendations
- Explicitly state that Azure-SSIS IR is Windows-only, if that is the case, to clarify the platform scope for users.
- If Linux support is possible or planned, provide equivalent instructions and examples for Linux environments, including bash scripts, Linux-compatible installers, and Linux command-line utilities.
- Where possible, mention cross-platform alternatives to Windows tools (e.g., alternatives to msiexec.exe, cmdkey, or PowerShell) and clarify any platform limitations.
- Add a section comparing Windows and Linux support for Azure-SSIS IR, outlining any differences and guiding users on what is or isn't possible on each platform.
- For Azure PowerShell instructions, offer CLI (az) equivalents if available, and clarify which steps are Windows-specific.
Data Factory
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 is heavily biased towards Windows, with all command-line examples provided in PowerShell, instructions referencing Windows-only tools (such as Add or Remove Programs), and installation steps that assume a Windows environment. There are no Linux or cross-platform examples or instructions, and the download link is specifically for a Windows installer. Linux users are not addressed or supported in the workflow.
Recommendations
- Provide equivalent command-line examples for Linux environments, such as using Azure CLI or bash scripts.
- Clarify whether the self-hosted integration runtime can be installed on Linux, and if so, provide installation instructions for Linux (e.g., using .deb or .rpm packages, or Docker).
- Include steps for uninstalling the integration runtime on Linux systems.
- Mention Linux-specific prerequisites or troubleshooting steps, if applicable.
- Ensure that all UI and tool references (such as Add or Remove Programs) have Linux equivalents or alternatives.
- Explicitly state platform support and limitations at the beginning of the documentation.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-ingest-data-into-fabric-from-azure-data-factory.md
...how-to-ingest-data-into-fabric-from-azure-data-factory.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits Windows bias primarily through its exclusive use of PowerShell for administrative tasks (such as refreshing permissions), references to Windows-centric tools (PowerShell, Power BI admin portal), and the absence of equivalent Linux or cross-platform command-line examples. There are no instructions or examples for performing these tasks using Linux-native tools, Azure CLI, or REST API calls, nor is there guidance for users on non-Windows platforms. The PowerShell example is presented as the only solution for immediate permission refresh, implicitly prioritizing Windows environments.
Recommendations
- Provide equivalent examples using Azure CLI and/or REST API for permission refresh and other administrative tasks, ensuring Linux and macOS users can follow along.
- Explicitly mention cross-platform alternatives where PowerShell is suggested, and clarify which steps are platform-agnostic.
- Add notes or sections for Linux/macOS users, including how to install and use PowerShell Core on those platforms if necessary, or how to use native tools.
- Where screenshots or instructions reference Windows-only interfaces, offer guidance for accessing the same features from web portals or cross-platform tools.
- Review all command-line instructions to ensure parity and accessibility for users on all major operating systems.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-use-sql-managed-instance-with-ir.md
...ata-factory/how-to-use-sql-managed-instance-with-ir.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias primarily through exclusive references to Windows-centric tools and patterns, such as SQL Server Management Studio (SSMS) and SQL Agent jobs, without mentioning or providing Linux alternatives. There are no examples or guidance for Linux users, nor are cross-platform tools like Azure Data Studio or CLI-based workflows highlighted. The documentation assumes a Windows environment for management and automation tasks, and does not address Linux-specific considerations or parity.
Recommendations
- Include examples using cross-platform tools such as Azure Data Studio, Azure CLI, or PowerShell Core (which runs on Linux).
- Explicitly mention Linux compatibility for SSIS package deployment and management, and provide steps for Linux users where possible.
- Add guidance for managing SSIS workloads and Azure SQL Managed Instance from Linux environments, including automation via bash scripts or other Linux-native tools.
- Reference SQL Agent alternatives or scheduling mechanisms available on Linux, such as cron jobs or Azure Automation.
- Ensure that documentation sections do not assume SSMS or Windows-only workflows, and present cross-platform options first or alongside Windows options.
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 page demonstrates Windows bias by exclusively referencing Windows-specific tools and patterns (such as Windows environment variables, Registry keys, GAC, and Windows file paths) for installing and configuring licensed SSIS components. There are no Linux or cross-platform equivalents, nor any mention of how these steps could be performed on Linux-based systems. All examples and instructions assume a Windows environment, and Windows terminology is used throughout.
Recommendations
- Provide equivalent instructions for Linux environments, if supported by Azure-SSIS IR or self-hosted IR.
- Clarify platform requirements and limitations early in the documentation (e.g., explicitly state if only Windows is supported).
- If Linux is not supported, explain why and offer guidance for users seeking cross-platform solutions.
- Include examples or notes about how environment variables, file paths, and component installation would differ on Linux.
- Reference any available cross-platform tools or patterns for SSIS component installation, or acknowledge their absence.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/pipelines-disaster-recovery.md
...n/articles/data-factory/pipelines-disaster-recovery.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 providing automation examples and references primarily using Azure PowerShell, with no mention of Linux-native tools or CLI equivalents. Windows-centric tools (PowerShell, Visio) are referenced, and automation steps (such as private endpoint approval and trigger management) are described using PowerShell scripts, without offering Bash, Azure CLI, or cross-platform alternatives. The order of presentation also favors Windows tools first, and there is a lack of explicit Linux or cross-platform guidance.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts alongside PowerShell instructions for all automation and deployment steps.
- Reference cross-platform tools for architecture diagrams (e.g., draw.io, Lucidchart) in addition to Visio.
- Explicitly mention that all steps can be performed on Linux and macOS, and provide links to relevant documentation.
- Where APIs are referenced (such as approval API), show usage via REST calls or curl, not just PowerShell.
- Ensure that automation and scripting guidance is platform-neutral, or at least offer parity between Windows and Linux approaches.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/managed-virtual-network-private-endpoint.md
...ta-factory/managed-virtual-network-private-endpoint.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides only Azure PowerShell examples for creating managed virtual networks and managed private endpoints, with no equivalent CLI or REST API examples. This assumes users are on Windows or using PowerShell, and does not mention or demonstrate Linux-friendly alternatives such as Azure CLI or ARM templates. The use of PowerShell is presented as the default or only method, which may disadvantage Linux users or those preferring cross-platform tools.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands to ensure Linux and macOS users have parity.
- Include REST API and ARM template examples for resource creation and management.
- Explicitly mention that PowerShell is only one of several options, and link to cross-platform alternatives.
- Review screenshots and UI instructions to ensure they are not Windows-specific (e.g., Azure Portal looks the same, but command-line examples should be platform-neutral).
- Add a section or note clarifying cross-platform support and best practices for Linux users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/introduction.md
...e-docs/blob/main/articles/data-factory/introduction.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias. PowerShell is mentioned as a primary monitoring and management tool, and is listed before other automation options (API, Azure Monitor logs, portal). The related content section highlights PowerShell as a quickstart option, and there is no explicit mention of Linux-specific tools or CLI examples (e.g., Bash, Azure CLI) for managing Azure Data Factory. Windows-centric tools and patterns are referenced more prominently than Linux equivalents.
Recommendations
- Add Azure CLI and Bash script examples alongside PowerShell for common tasks such as pipeline creation, monitoring, and management.
- Explicitly mention cross-platform options for automation and management (e.g., Azure CLI, REST API) in relevant sections.
- In the monitoring section, list Azure CLI and REST API before or alongside PowerShell to avoid Windows-first ordering.
- Include references to Linux-compatible tools and workflows in the related content section, such as quickstart guides for Azure CLI and Bash.
- Ensure that examples and instructions are platform-neutral or provide parity between Windows and Linux environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/monitor-data-factory.md
...lob/main/articles/data-factory/monitor-data-factory.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page mentions monitoring Azure Data Factory programmatically using .NET, PowerShell, Python, or REST API, but lists PowerShell before Linux-friendly options and does not provide any Linux-specific examples or mention Linux command-line tools. There is an implicit Windows-first approach, as PowerShell and .NET are traditionally Windows-centric technologies, and no parity is shown for Linux users (e.g., Bash, CLI, or shell scripting). No Linux-specific monitoring patterns or tools are referenced, and example commands or scripts are absent for Linux environments.
Recommendations
- Add explicit Linux/Bash/CLI examples for programmatic monitoring, such as using Azure CLI or Bash scripts.
- Mention Linux-compatible tools and workflows alongside PowerShell and .NET, such as az CLI, curl, jq, or Python scripts.
- Ensure that examples and instructions are provided for both Windows and Linux environments, ideally side-by-side.
- Avoid listing Windows-centric technologies first; alternate or group by platform.
- Reference Linux documentation or guides for monitoring Azure Data Factory where available.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/quickstart-create-data-factory-rest-api.md
...ata-factory/quickstart-create-data-factory-rest-api.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 examples use Azure PowerShell, with no mention of Linux-native tools, Bash, or cross-platform alternatives. The prerequisite steps and instructions assume the user is on Windows, and recommend Azure PowerShell and Storage Explorer (a GUI tool, but Windows-centric in context). There are no Bash, curl, or az CLI examples, nor any guidance for Linux or macOS users.
Recommendations
- Add equivalent Bash/curl examples for all REST API calls, showing how to authenticate and interact with Azure Data Factory from Linux/macOS.
- Include az CLI examples where possible, as az CLI is cross-platform and widely used.
- Explicitly mention cross-platform compatibility in prerequisites, and provide installation instructions for Linux/macOS environments.
- Reference Linux-native tools (e.g., azcopy, curl, jq) for tasks such as uploading files, monitoring pipeline runs, and cleaning up resources.
- Reorganize sections so that cross-platform methods (az CLI, REST via curl) are presented before or alongside PowerShell examples.
- Add notes or callouts for Linux/macOS users, including troubleshooting tips and environment setup guidance.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/join-azure-ssis-integration-runtime-virtual-network.md
...ttps://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/join-azure-ssis-integration-runtime-virtual-network.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 Azure PowerShell as a primary method for provisioning Azure-SSIS IR and joining it to a virtual network. There are no examples or mentions of Linux-native tools (such as Azure CLI, Bash, or cross-platform automation), and the related content lists PowerShell before any Linux-compatible alternatives. The documentation assumes familiarity with Windows-centric tooling and does not provide parity for Linux users.
Recommendations
- Add equivalent instructions and examples using Azure CLI, which is cross-platform and widely used on Linux.
- Include Bash script examples for common tasks, such as provisioning Azure-SSIS IR and joining it to a virtual network.
- Explicitly mention that Azure CLI and portal are available on Linux and macOS, and provide links to relevant documentation.
- Ensure that references to PowerShell are balanced with references to CLI or other cross-platform tools, ideally listing them together or alternating order.
- Consider a dedicated section or callout for Linux users, highlighting any differences or additional steps.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/manage-azure-ssis-integration-runtime.md
.../data-factory/manage-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 strong bias towards Windows and PowerShell. All command-line examples are provided exclusively in PowerShell, with no mention of Bash, Azure CLI, or Linux-native tooling. The PowerShell section is extensive and detailed, while there are no equivalent instructions or examples for Linux users. The documentation assumes familiarity with Windows-centric tools and patterns, and does not address cross-platform parity.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and commonly used on Linux and macOS.
- Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell must be used, and provide installation guidance.
- Where possible, provide Bash script examples or at least note how Linux users can perform the same tasks.
- Reorganize the documentation to present cross-platform or Azure CLI options before or alongside PowerShell examples, rather than only after.
- Include a section or note addressing Linux/macOS users, clarifying which tools are supported and how to use them.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/monitor-programmatically.md
...main/articles/data-factory/monitor-programmatically.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 providing REST API examples exclusively in PowerShell, which is primarily a Windows shell. There are no equivalent Linux shell (e.g., Bash, curl) examples for REST API usage. The PowerShell section is extensive and uses Windows-specific cmdlets and patterns. Windows tools and scripting approaches are mentioned and demonstrated before any Linux equivalents, which are missing entirely. This may hinder Linux users or those using cross-platform environments from easily following the documentation.
Recommendations
- Add REST API examples using Bash and curl to demonstrate how to monitor pipeline runs from Linux or macOS environments.
- Include cross-platform scripting examples (e.g., Python, Bash) alongside PowerShell to ensure parity.
- Explicitly mention that PowerShell examples can be run on Linux (if applicable) or clarify platform requirements.
- Reorder or balance example sections so that Windows-specific tools are not always presented first.
- Provide guidance or links for Linux users on installing required tools or adapting examples.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/monitor-ssis.md
...e-docs/blob/main/articles/data-factory/monitor-ssis.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools (Azure PowerShell, SSMS, SSDT, SQL Server Agent) and providing examples and invocation methods that are exclusively or primarily Windows-based. There are no Linux-specific examples, tools, or instructions for monitoring SSIS operations, nor is there mention of Linux command-line alternatives or cross-platform approaches.
Recommendations
- Include Linux-compatible monitoring instructions, such as using Azure CLI or REST API for checking SSIS IR operational status.
- Mention cross-platform SQL clients (e.g., Azure Data Studio) as alternatives to SSMS for querying SSISDB.
- Provide examples of parsing and analyzing SSIS logs using Linux tools (e.g., grep, awk, Python scripts) for CSV files stored in Azure Files.
- Clarify which steps and tools are platform-agnostic and which are Windows-specific, and offer Linux equivalents where possible.
- Add explicit guidance for users running SSIS workloads or monitoring from Linux environments, including troubleshooting and best practices.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/self-hosted-integration-runtime-troubleshoot-guide.md
...https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/self-hosted-integration-runtime-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. Troubleshooting steps, log collection, and configuration instructions almost exclusively reference Windows tools (Event Viewer, MMC, Registry Editor, Windows folders, Windows services, certutil, PowerShell, etc.). All command-line examples are for Windows (CMD, PowerShell), and there are no Linux-specific instructions or examples. Even when discussing network troubleshooting, only Windows tools (Netmon, telnet, etc.) are mentioned first or exclusively. There is no mention of Linux equivalents for log collection, service management, certificate handling, or troubleshooting, despite the possibility of running self-hosted IR on Linux (e.g., via containers or Mono).
Recommendations
- Add Linux-specific troubleshooting steps and examples for all major scenarios, including log collection, service management, and certificate handling.
- Provide Linux equivalents for Windows tools mentioned (e.g., use journalctl/syslog for logs, openssl for certificates, systemctl/service for service management, curl/wget for network tests, etc.).
- Include bash shell commands and file paths for Linux environments alongside Windows CMD/PowerShell examples.
- Explicitly state platform requirements and limitations (e.g., if self-hosted IR is Windows-only, clarify early; if Linux is supported via containers, provide relevant instructions).
- When referencing registry or Windows-specific configuration, offer alternative approaches for Linux (e.g., environment variables, config files).
- Mention Linux troubleshooting tools (e.g., Wireshark, tcpdump, lsof, netstat) and provide example usage.
- Ensure parity in screenshots and UI instructions for Linux desktop environments if applicable.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/security-and-access-control-troubleshoot-guide.md
...tory/security-and-access-control-troubleshoot-guide.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a Windows bias in several areas. Troubleshooting steps and examples frequently reference Windows-specific tools (e.g., PsPing.exe), Windows file paths (e.g., C:\Windows\System32\drivers\etc), and editors (Notepad). There are no equivalent instructions or examples for Linux environments, such as using ping, nc, or editing /etc/hosts. Windows tools and patterns are mentioned exclusively, and Linux alternatives are missing throughout, especially in sections about network troubleshooting and host file modification.
Recommendations
- Provide Linux equivalents for all Windows-specific instructions, such as using 'ping', 'nc', or 'curl' for connectivity checks, and editing '/etc/hosts' with nano or vi.
- Include examples and screenshots for Linux environments alongside Windows examples.
- Mention cross-platform tools where possible, or clarify which steps are OS-specific.
- Avoid assuming the user is on Windows; structure troubleshooting steps to address both Windows and Linux users equally.
- Explicitly state any OS limitations or requirements for the self-hosted IR and related troubleshooting.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/self-hosted-integration-runtime-proxy-ssis.md
...-factory/self-hosted-integration-runtime-proxy-ssis.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a strong Windows bias. All command-line examples are provided exclusively using PowerShell, with no mention of Linux shell equivalents. Installation instructions and troubleshooting steps reference Windows-specific tools, paths, and concepts (e.g., Local Security Policy, NT SERVICE accounts, C:\ProgramData folders, Visual Studio/SSDT, and Windows authentication). There is no guidance for deploying or operating the self-hosted IR proxy on Linux, nor any mention of Linux-compatible alternatives for key steps.
Recommendations
- Provide equivalent Linux shell (bash) commands for all PowerShell examples, or clarify platform support and limitations.
- Document installation and configuration steps for self-hosted IR on Linux, including supported distributions and prerequisites.
- Include Linux-specific instructions for driver installation, log file locations, and service account management.
- Clarify whether features such as Windows authentication, Local Security Policy, and NT SERVICE accounts are required or optional, and provide Linux alternatives or workarounds where possible.
- Explicitly state platform compatibility for all referenced tools (e.g., SSDT, Visual Studio, Integration Runtime Configuration Manager), and suggest cross-platform alternatives if available.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/self-hosted-integration-runtime-diagnostic-tool.md
...ory/self-hosted-integration-runtime-diagnostic-tool.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively references Windows-specific tools (Configuration Manager, dmgcmd.exe) and provides only Windows command-line examples. There is no mention of Linux equivalents, nor are Linux installation or troubleshooting steps discussed. The examples and screenshots are Windows-centric, indicating a strong Windows bias.
Recommendations
- Add instructions and examples for running the diagnostic tool on Linux systems, if supported.
- Include Linux-specific command-line usage (e.g., shell commands) and clarify tool compatibility across platforms.
- Provide screenshots or UI descriptions for Linux environments, if applicable.
- Explicitly state platform limitations or support in the introduction to set user expectations.
- Ensure parity in troubleshooting steps and documentation for both Windows and Linux users.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/sap-change-data-capture-shir-preparation.md
...ta-factory/sap-change-data-capture-shir-preparation.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by exclusively providing instructions and examples for Windows environments. It references Windows-specific tools (PowerShell, GAC, Windows hosts file path), omits Linux equivalents, and does not mention how to perform the same setup on Linux systems. All examples and screenshots are Windows-centric.
Recommendations
- Add Linux-specific instructions for installing the self-hosted integration runtime, including supported distributions and prerequisites.
- Provide Linux equivalents for testing connectivity (e.g., using 'nc' or 'telnet' instead of PowerShell).
- Include instructions for editing the hosts file on Linux (typically '/etc/hosts').
- Clarify whether the SAP .NET Connector and self-hosted integration runtime are supported on Linux, and if not, state this explicitly.
- If Linux is supported, provide screenshots and examples for Linux environments alongside Windows examples.
- Mention cross-platform considerations and limitations in the prerequisites section.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/self-hosted-integration-runtime-auto-update.md
...factory/self-hosted-integration-runtime-auto-update.md
High Priority
View Details →
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-based examples and instructions, referencing the 'self-hosted integration runtime client' (a Windows application), and omitting any Linux-specific guidance or CLI examples. All operational instructions and screenshots are tailored to Windows environments, with no mention of Linux installation, management, or equivalent tooling. The use of PowerShell and Windows-centric terminology is pervasive, and there is no parity for Linux users.
Recommendations
- Provide equivalent examples using Bash and Azure CLI for Linux environments.
- Clarify whether the self-hosted integration runtime client is available for Linux, and if not, offer alternative management strategies for Linux users.
- Include screenshots or instructions for managing integration runtime from Linux systems (e.g., via web portal or CLI).
- Explicitly mention platform support and limitations at the start of the documentation.
- Ensure all PowerShell commands have corresponding Azure CLI or REST API examples for cross-platform usability.