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 651-675 of 1000 flagged pages
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/how-to-schedule-azure-ssis-integration-runtime.md
...tory/how-to-schedule-azure-ssis-integration-runtime.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily oriented towards Windows and PowerShell. All automation and scripting examples use PowerShell, with no mention of Bash, Azure CLI, or cross-platform scripting alternatives. The use of SQL Server Management Studio (a Windows-only tool) is recommended for verification. There are no Linux-specific instructions or examples, and the documentation assumes the use of Windows-centric tools and workflows throughout.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for starting, stopping, and monitoring Azure-SSIS IR, alongside PowerShell.
- Include instructions for verifying SSIS package execution using cross-platform tools or Azure Portal, not just SQL Server Management Studio.
- Mention and demonstrate how to use REST API calls via curl or other cross-platform tools for automation.
- Clarify that PowerShell Core is available cross-platform, but also provide Bash/CLI alternatives for Linux users.
- Review all screenshots and UI instructions to ensure they are not exclusive to Windows environments, or provide notes for Linux/macOS users where UI may differ.
Create Pull Request
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
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. PowerShell is mentioned as a primary method for monitoring pipelines, and the 'Related content' section lists PowerShell before other cross-platform options like .NET, Python, and REST. There is no mention of Linux-specific tools, shell commands, or CLI usage, and the documentation does not provide parity in examples or tool recommendations for Linux users. The focus on PowerShell and the ordering of tools suggest a Windows-first perspective.
Recommendations
- Include Azure CLI examples and references alongside or before PowerShell, as Azure CLI is cross-platform and widely used on Linux.
- Mention and link to Bash or shell scripting guides for Linux users where automation or scripting is discussed.
- Balance the order of tool references in 'Related content' by listing cross-platform options (Azure CLI, Python, REST) before or alongside PowerShell.
- Explicitly state that Azure Data Factory can be managed from Linux, macOS, and Windows, and provide links to relevant Linux/macOS quickstarts.
- Where monitoring or automation is discussed, provide examples or references for both PowerShell and Azure CLI.
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
Missing Linux Example
Windows Tools
Summary
The documentation provides only Azure PowerShell examples for creating managed virtual networks and private endpoints, with no equivalent examples for Linux/Unix users (e.g., Azure CLI, REST API, or ARM templates). The exclusive use of PowerShell and the absence of cross-platform tooling or scripting options indicate a Windows-centric bias.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell scripts to support Linux/macOS users.
- Include REST API and/or ARM template examples for automation scenarios that are platform-agnostic.
- Explicitly mention that the PowerShell examples can be run on PowerShell Core (cross-platform) if applicable, or clarify any Windows-only requirements.
- Where screenshots or UI steps are shown, ensure they are not specific to Windows-only tools.
- Review all sections for references to Windows-specific tools or terminology, and provide Linux/macOS alternatives where relevant.
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
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias, particularly in its automation and scripting sections. All command-line examples are provided exclusively in PowerShell, with explicit references to Windows file paths (e.g., C:\ADF\RunSSISPackage) and no mention of Bash, Azure CLI, or cross-platform alternatives. The PowerShell approach is presented as the only automation method, and there are no Linux/macOS-specific instructions or parity notes. The UI walkthrough is platform-agnostic, but all scripting and file management assume a Windows environment.
Recommendations
- Provide equivalent examples using Azure CLI and Bash scripts for all PowerShell automation steps, including Data Factory creation, linked service setup, pipeline deployment, and monitoring.
- Replace or supplement Windows file paths (e.g., C:\ADF\RunSSISPackage) with cross-platform or Linux/macOS-friendly paths (e.g., ~/ADF/RunSSISPackage), or clarify that the location is arbitrary.
- Explicitly state that the PowerShell approach is cross-platform if using PowerShell Core, or clarify Windows-only requirements if not.
- Add a section or callout for Linux/macOS users, outlining any prerequisites or differences in procedure.
- Where possible, link to Azure CLI documentation and provide side-by-side code samples for both PowerShell and CLI.
- Review metadata (e.g., ms.devlang: powershell) and custom tags to ensure they do not exclude or discourage non-Windows users.
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
Summary
The documentation page demonstrates a bias towards Windows by referencing Azure PowerShell as the primary or only command-line automation tool for provisioning and managing Azure-SSIS IR. There are no examples or mentions of Linux-native tools (such as Azure CLI or Bash scripting), nor are there instructions or links for performing equivalent tasks on Linux or macOS platforms. The related content and workflow examples focus on Azure PowerShell and ADF UI, both of which are more familiar to Windows users.
Recommendations
- Add parallel instructions and examples using Azure CLI (az commands), which is cross-platform and widely used on Linux and macOS.
- Include explicit references to Bash or shell scripting where automation is discussed, not just PowerShell.
- Where PowerShell is mentioned, provide equivalent Azure CLI documentation links or code snippets.
- Review related articles to ensure Linux users can follow all workflows without needing to install or use PowerShell.
- Clarify in the documentation that all major steps can be performed from Linux/macOS as well as Windows, and provide guidance for both.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/monitor-shir-in-azure.md
...ob/main/articles/data-factory/monitor-shir-in-azure.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (Event Viewer, Performance Monitor) and linking only to Windows documentation for event logs and performance counters. While Linux is briefly mentioned in the context of performance counters, no Linux-specific instructions, tools, or examples are provided. The focus is on Windows patterns and tools, with Linux support implied but not detailed.
Recommendations
- Include explicit Linux examples for viewing event logs and performance counters, such as using journalctl, syslog, or sar/vmstat.
- Provide links to Linux documentation for performance monitoring and log analysis.
- Mention Linux tools and commands alongside Windows tools, ensuring parity in instructions.
- Clarify any differences in log locations, formats, or monitoring approaches between Windows and Linux SHIR hosts.
- Add a section or callout specifically addressing Linux monitoring scenarios.
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
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based command-line examples for reconfiguring and deleting Azure-SSIS integration runtimes. There are no equivalent examples or instructions for Linux users (e.g., using Azure CLI, Bash, or cross-platform tools). PowerShell is a Windows-native tool (though available on Linux, it is less commonly used there), and no alternative command-line approaches are mentioned.
Recommendations
- Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux.
- Explicitly mention that PowerShell Core is available on Linux, and provide installation guidance if PowerShell usage is required.
- Where possible, provide Bash script examples or references for Linux users.
- Ensure that any references to tools or scripts are clearly marked as cross-platform or provide alternatives for non-Windows environments.
- Consider reordering sections or providing tabs to show both PowerShell and Azure CLI (or Bash) approaches side by side.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/monitor-integration-runtime.md
...n/articles/data-factory/monitor-integration-runtime.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 bias. All command-line examples use Azure PowerShell cmdlets, with no mention of equivalent Azure CLI or REST API methods that are cross-platform. The self-hosted integration runtime is described as being installed on 'on-premises Windows machines' only, with no mention of Linux support or alternatives. Windows-centric tools and patterns (PowerShell, SSMS, SSDT) are referenced exclusively or before any cross-platform options. There are no Linux-specific instructions or examples, and the documentation does not address monitoring or managing integration runtimes from Linux environments.
Recommendations
- Provide equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and works natively on Linux and macOS.
- Mention and document REST API options for monitoring integration runtimes, which can be used from any OS.
- Clarify whether self-hosted integration runtime can be installed or monitored from Linux machines, and if not, state this limitation explicitly.
- Include references to cross-platform tools (e.g., Azure Data Studio instead of or alongside SSMS, or mention of VS Code for pipeline authoring/monitoring).
- Rephrase sections that imply Windows exclusivity (e.g., 'Node is an on-premises Windows machine') to either clarify support or provide Linux alternatives if available.
- Add a section or note for Linux/macOS users, summarizing supported monitoring approaches and tools.
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
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing Azure PowerShell and Windows-centric tools (SSMS, SSDT, SQL Server Agent) for monitoring and managing SSIS operations, without mentioning or providing equivalent Linux-based tools or CLI examples. There are no Linux or cross-platform command-line examples, and the workflow assumes the use of Windows environments and tooling.
Recommendations
- Include Azure CLI examples alongside or instead of Azure PowerShell for checking SSIS IR operational status, as Azure CLI is cross-platform.
- Mention cross-platform alternatives to SSMS and SSDT, such as Azure Data Studio, and provide instructions or examples for their use.
- Clarify whether monitoring and querying can be performed from Linux/macOS environments, and provide guidance for those platforms.
- Ensure that all tool references (e.g., for querying logs, raising alerts) include both Windows and cross-platform options.
- Add explicit Linux/macOS command-line examples for common monitoring tasks.
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, referencing PowerShell cmdlets throughout, and omitting equivalent Linux/bash/cURL examples. Windows tools and scripting patterns (PowerShell, Write-Host, Get-Date) are used without mention of cross-platform alternatives, and Windows-centric approaches are presented before or instead of Linux-friendly options.
Recommendations
- For REST API sections, provide bash/cURL examples alongside or instead of PowerShell scripts to support Linux and macOS users.
- Explicitly mention that PowerShell examples are for Windows and provide equivalent bash or Python scripts for Linux environments.
- Where PowerShell cmdlets are referenced (e.g., Get-AzDataFactoryV2PipelineRun), note cross-platform alternatives or clarify their platform compatibility.
- Avoid using Windows-specific scripting idioms (e.g., Write-Host, Start-Sleep) without Linux equivalents; provide corresponding bash commands (e.g., echo, sleep).
- Consider reordering or parallelizing examples so that Linux-compatible approaches (bash, Python, cURL) are presented alongside Windows/PowerShell, not only after or instead of them.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/quickstart-create-data-factory-bicep.md
...s/data-factory/quickstart-create-data-factory-bicep.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment and resource management, but consistently lists PowerShell after CLI. However, in the 'Create a file' step, it references Notepad (a Windows-specific editor) without mentioning Linux alternatives. There are no explicit Linux shell or scripting examples, and the use of PowerShell is prominent. The instructions assume familiarity with Windows tools and patterns, and do not provide parity for Linux users in terms of editor or command-line environment guidance.
Recommendations
- In the 'Create a file' section, suggest cross-platform editors (e.g., VS Code, nano, vim) alongside Notepad.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and provide any necessary shell syntax (e.g., bash) if needed.
- Where PowerShell is shown, consider also showing Bash equivalents for common tasks, or clarify that Azure CLI is cross-platform.
- Add notes or tips for Linux/macOS users where file paths, editors, or command syntax may differ.
- Ensure that all steps are clearly cross-platform or provide platform-specific guidance as appropriate.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/quickstart-create-data-factory-dot-net.md
...data-factory/quickstart-create-data-factory-dot-net.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Visual Studio (a Windows-centric IDE), providing only PowerShell-based NuGet installation commands, and omitting any Linux or cross-platform development guidance. There are no instructions or examples for using .NET SDK on Linux or macOS, nor are alternative editors or shell environments (such as VS Code, JetBrains Rider, or Bash) mentioned.
Recommendations
- Include instructions for creating and running the .NET console application using cross-platform tools such as Visual Studio Code and JetBrains Rider.
- Provide alternative NuGet installation commands using the dotnet CLI (e.g., 'dotnet add package ...'), which works on Windows, Linux, and macOS.
- Mention that the .NET SDK and Azure SDK libraries are cross-platform, and provide guidance for Linux/macOS users (e.g., using Bash or zsh).
- Add a section or callout noting any platform-specific differences, such as file paths or environment setup.
- Ensure screenshots, if any, are not Windows-only, or provide equivalent steps for other operating systems.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/quickstart-create-data-factory-resource-manager-template.md
...ickstart-create-data-factory-resource-manager-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a Windows bias by referencing Windows-specific tools and paths (e.g., Notepad, C:\ paths), providing only Azure PowerShell commands for resource cleanup, and omitting Linux/macOS equivalents for file creation, path conventions, and command-line operations. There are no CLI or Bash examples, and the instructions assume a Windows environment throughout.
Recommendations
- Provide parallel instructions for Linux/macOS users, including file creation using editors like nano, vim, or touch, and using POSIX-compliant paths (e.g., /home/user/ADFv2QuickStartPSH/emp.txt).
- Include Azure CLI examples for resource cleanup (e.g., az group delete, az datafactory delete) alongside PowerShell commands.
- Avoid referencing only Windows tools (e.g., Notepad); instead, suggest cross-platform editors or provide alternatives.
- When specifying file paths, show both Windows and Linux/macOS formats.
- Explicitly state that the instructions apply to all platforms, or call out any platform-specific steps.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/quickstart-create-data-factory-python.md
.../data-factory/quickstart-create-data-factory-python.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation shows a mild Windows bias. It suggests launching Notepad to create a file, which is a Windows-specific tool, and refers to 'command prompt with administrator privileges' before 'terminal', which is a Windows-first phrasing. There are no explicit Linux/macOS examples or tool recommendations (e.g., nano, vi, or touch for file creation), and no mention of Linux-specific instructions for uploading files or running commands. The only optional tool mentioned is Azure Storage Explorer, which is cross-platform, but no Linux-native alternatives or CLI methods are discussed.
Recommendations
- When instructing users to create a text file, mention cross-platform editors (e.g., Notepad (Windows), nano/vi (Linux/macOS), or any text editor).
- Instruct users to 'open a terminal or command prompt' without specifying administrator privileges unless required, and clarify if sudo is needed on Linux/macOS.
- Provide examples for uploading files to Azure Blob Storage using Azure CLI or azcopy, which are cross-platform, in addition to Azure Storage Explorer.
- Explicitly state that all Python code and commands work on Windows, Linux, and macOS, and mention any OS-specific considerations.
- Where possible, include Linux/macOS shell commands (e.g., touch input.txt, nano input.txt) alongside Windows instructions.
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
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a strong Windows bias. All setup instructions and examples assume a Windows environment: PowerShell is used for connectivity testing, the SAP .NET Connector (Windows-only) is required, and file paths reference Windows locations. There are no Linux equivalents or guidance for non-Windows platforms, and Windows tools and patterns are mentioned exclusively.
Recommendations
- Provide equivalent instructions and examples for Linux environments, such as using curl, nc, or telnet for connectivity testing instead of PowerShell.
- Clarify whether the self-hosted integration runtime and SAP .NET Connector are supported on Linux, and if not, explicitly state this limitation.
- If Linux is supported, include Linux file paths and commands for editing the hosts file (e.g., /etc/hosts).
- Mention cross-platform alternatives or workarounds where possible, or direct users to relevant documentation for non-Windows setups.
- Structure sections so that Windows and Linux instructions are presented in parallel, or clearly label platform-specific steps.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/scenario-ssis-migration-overview.md
...icles/data-factory/scenario-ssis-migration-overview.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation demonstrates a Windows bias by exclusively referencing Windows-based tools (SSDT, SSMS, dtutil, dtexec, DMA) and workflows, without mentioning or providing Linux alternatives or examples. The migration steps and tooling assume a Windows environment, and there is no guidance for users operating from Linux or cross-platform environments.
Recommendations
- Explicitly state platform requirements for tools like SSMS, SSDT, dtutil, and DMA, and clarify if they are Windows-only.
- If possible, provide Linux-compatible alternatives or document any cross-platform command-line utilities (e.g., Azure CLI, PowerShell Core, REST APIs) that can be used for package management and migration.
- Include Linux-specific examples or workflows for common migration tasks, or acknowledge the lack of Linux support and suggest workarounds.
- Mention Azure Data Studio as a partial cross-platform alternative to SSMS, and clarify its capabilities and limitations regarding SSIS.
- Reorganize sections to avoid always listing Windows tools and approaches first; consider a neutral or platform-agnostic structure.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/scenario-ssis-migration-rules.md
...articles/data-factory/scenario-ssis-migration-rules.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows-centric bias by referencing Windows authentication, Windows environment variables, UNC paths, registry entries, and Windows-specific tools (e.g., cmdkey) without providing equivalent Linux or cross-platform guidance. There are no Linux/Unix-specific examples or mentions of how to handle these scenarios on non-Windows systems, which may leave Linux users without clear migration paths.
Recommendations
- For every mention of Windows authentication, environment variables, or registry, provide Linux/Unix equivalents or explicitly state if unsupported.
- Include examples or notes for Linux-based SSIS deployments, such as handling environment variables, file paths, and authentication.
- When referencing tools like cmdkey or UNC paths, add parallel instructions for Linux (e.g., using keyrings, mounting NFS/Samba shares, or using environment variables).
- Clarify platform limitations (e.g., if Azure-SSIS IR only supports Windows-based packages) and provide migration tips for Linux users.
- Ensure that documentation structure and examples do not assume a Windows-only environment; add cross-platform context where possible.
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 First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias in several areas. Troubleshooting steps and examples reference Windows-specific tools (e.g., PsPing.exe), and instructions for editing the hosts file are given only for Windows (C:\Windows\System32\drivers\etc), with no mention of Linux equivalents. There are no Linux/Unix command examples or file paths, and Windows tools and patterns are presented exclusively or before any cross-platform alternatives.
Recommendations
- Provide equivalent Linux/Unix command examples (e.g., use 'ping' and 'nc' or 'curl' instead of only 'psping.exe').
- Include instructions for editing the hosts file on Linux (e.g., /etc/hosts) alongside the Windows example.
- Reference cross-platform tools or note when a tool is Windows-only, and suggest alternatives for other platforms.
- Ensure that troubleshooting steps are platform-agnostic or clearly separated for Windows and Linux environments.
- Add screenshots or command snippets for both Windows and Linux where applicable.
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. All command-line examples are provided exclusively in PowerShell, which is primarily a Windows tool. There is no mention of Linux or cross-platform alternatives, nor are there any bash or shell script examples. The documentation assumes the use of the 'self-hosted integration runtime client', which is a Windows application, and does not address Linux installation, management, or monitoring scenarios. This may leave Linux users without clear guidance.
Recommendations
- Provide equivalent bash or shell script examples for all PowerShell commands, especially for querying and managing integration runtimes using the Azure CLI.
- Explicitly mention whether the self-hosted integration runtime is supported on Linux, and if so, provide Linux-specific installation and management instructions.
- Include screenshots or instructions for Linux environments where applicable.
- Clarify any platform limitations or differences in behavior between Windows and Linux hosts.
- Ensure that references to tools (such as the 'client') are accompanied by notes about their platform compatibility.
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 installation and configuration instructions, including command-line actions and authentication setup, assume a Windows environment. PowerShell is the only scripting example provided, and references to Windows-specific tools (such as Local Security Policy, NT SERVICE accounts, and Visual Studio/SSDT) are prevalent. There are no Linux or cross-platform alternatives or examples, and no mention of support for running the self-hosted IR or related tools on Linux.
Recommendations
- Clarify early in the documentation whether self-hosted IR and SSIS proxy features are supported on Linux or only on Windows. If Windows-only, state this explicitly.
- If Linux is supported, provide equivalent installation, configuration, and authentication instructions for Linux environments, including command-line examples (e.g., Bash, shell scripts) and references to Linux service accounts and security policies.
- Offer cross-platform alternatives to PowerShell scripts, such as Azure CLI or REST API examples.
- Document where logs and configuration files are located on Linux, if applicable.
- Mention any required dependencies or drivers for Linux, and provide download/installation instructions.
- If Visual Studio/SSDT is required and only available on Windows, suggest alternative cross-platform development tools if available, or clarify the limitation.
- Review all references to Windows-specific tools (e.g., Local Security Policy, NT SERVICE accounts) and provide Linux equivalents or note their absence.
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 First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias throughout. All troubleshooting steps, examples, and tool references are exclusively for Windows environments. Windows-specific tools (Event Viewer, MMC, Regedit, certutil, Process Monitor, Netmon), file paths, registry edits, and PowerShell commands are used without mention of Linux equivalents. There are no Linux-specific instructions, examples, or troubleshooting guidance, despite the potential for running self-hosted integration runtime on Linux (e.g., via Docker or Mono). Even generic troubleshooting (network, certificates, permissions) is always described using Windows paradigms.
Recommendations
- Add parallel Linux instructions and examples for all troubleshooting steps, including log collection, certificate management, service management, and environment variables.
- Include Linux equivalents for all Windows tools mentioned (e.g., use 'journalctl' or 'systemd' logs instead of Event Viewer, 'openssl' for certificate checks, 'strace' or 'lsof' for process monitoring, 'tcpdump' or 'wireshark' for network tracing).
- Provide Linux file paths and environment variable instructions alongside Windows paths.
- When referencing commands (e.g., PowerShell, certutil, regedit), also provide bash/shell alternatives for Linux.
- Explicitly state OS-specific limitations or requirements (e.g., if some features/tools are Windows-only, clarify this and suggest workarounds or alternatives for Linux).
- Reorganize sections to present Windows and Linux instructions side-by-side or in clearly labeled tabs, rather than only Windows.
- Where only Windows is supported, clearly state this at the top of the documentation.
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 Tools
Missing Linux Example
Windows First
Summary
The documentation is heavily biased towards Windows and PowerShell usage. All command-line examples use Azure PowerShell cmdlets, and there are no examples or instructions for Linux/macOS users or for using cross-platform tools like Azure CLI or curl. The prerequisite section requires Azure PowerShell, and the workflow assumes a PowerShell environment throughout. Additionally, tools like Azure Storage Explorer (a GUI tool) are mentioned, but no Linux-native or CLI alternatives are provided. This approach excludes users on Linux or macOS who may prefer or require bash, Azure CLI, or REST calls via curl/httpie.
Recommendations
- Provide equivalent examples using Azure CLI (az) commands, which are cross-platform and widely used on Linux/macOS.
- Include REST API invocation examples using curl or httpie, demonstrating how to authenticate and make requests without PowerShell.
- Explicitly mention that all PowerShell commands can be run on PowerShell Core, which is available on Linux/macOS, or clarify any Windows-only dependencies.
- In the prerequisites, offer installation instructions for both Azure PowerShell and Azure CLI, and note their cross-platform availability.
- When referencing Azure Storage Explorer, also mention az storage CLI commands or other open-source, cross-platform tools for managing Azure Storage.
- Where possible, provide bash script equivalents for automation steps.
- Add a section or callout for Linux/macOS users, outlining any differences or additional steps required.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/solution-template-delta-copy-with-control-table.md
...ory/solution-template-delta-copy-with-control-table.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a bias toward Windows environments by exclusively referencing SQL Server and Azure SQL Database (both Microsoft-centric, often Windows-based), using T-SQL syntax, and describing stored procedures and control tables only in the context of SQL Server. There are no examples or guidance for using open-source or Linux-native databases (such as PostgreSQL or MySQL), nor are there instructions for creating control tables or stored procedures in those systems. No Linux command-line or shell examples are provided, and the workflow assumes a Windows-centric database stack.
Recommendations
- Provide equivalent examples for popular Linux/open-source databases (e.g., PostgreSQL, MySQL, MariaDB), including DDL and stored procedure syntax.
- Include guidance for creating and managing control tables and high-watermark logic in non-SQL Server environments.
- Offer sample shell (bash) commands or scripts for Linux users where relevant (e.g., for interacting with databases or automating tasks).
- Clarify in the introduction that the template is compatible with multiple database systems, and link to platform-specific instructions.
- Ensure screenshots and UI references are not specific to Windows-only tools or environments.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/ssis-azure-files-file-shares.md
.../articles/data-factory/ssis-azure-files-file-shares.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows authentication, Windows-style environment variables (e.g., %TEMP%), and Windows file path conventions (e.g., C:\abc.txt, UNC paths). There are no examples or instructions for Linux-based environments, and no mention of Linux authentication methods, file paths, or tools.
Recommendations
- Include equivalent instructions and examples for Linux-based SSIS IR nodes, if supported.
- Mention and provide examples using Linux environment variables (e.g., $TMPDIR) and file paths (e.g., /tmp/abc.txt).
- Describe how to connect to file shares using Linux authentication methods (such as SMB/CIFS with Kerberos or username/password).
- Clarify whether Azure-SSIS IR supports Linux nodes, and if not, explicitly state this limitation.
- If only Windows is supported, add a note to inform users that the documentation is Windows-specific.
Data Factory
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/data-factory/source-control.md
...docs/blob/main/articles/data-factory/source-control.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias, primarily through the exclusive mention of PowerShell and the lack of Linux-specific or cross-platform command-line examples. References to updating the factory via 'PowerShell or an SDK' and the absence of any mention of Bash, CLI, or Linux tools suggest an assumption of a Windows environment. No explicit Linux or cross-platform workflows, troubleshooting, or configuration steps are provided.
Recommendations
- Add equivalent Bash/CLI examples alongside PowerShell references, especially in troubleshooting and automation sections.
- Explicitly mention cross-platform compatibility for SDKs and command-line tools, and provide links to relevant documentation for Linux/macOS users.
- Where PowerShell is referenced, add a note or example for Azure CLI or Bash to ensure Linux users are not excluded.
- Review all troubleshooting and automation guidance to ensure parity for Linux and macOS environments.
- Include a section or callout on cross-platform support, clarifying that all features and integrations are available on non-Windows systems where applicable.