Document Details
Data Movement Security Considerations
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Detected Bias Types
powershell_heavy
windows_tools
windows_first
missing_linux_example
Summary
The documentation demonstrates a notable Windows bias in its coverage of hybrid scenarios and credential management for self-hosted integration runtime. It exclusively references Windows-specific technologies (such as DPAPI and Windows Firewall), PowerShell cmdlets (Set-AzDataFactoryV2LinkedService, New-AzDataFactoryV2LinkedServiceEncryptedCredential), and port requirements tied to Windows/PowerShell usage. There is no mention of Linux or macOS equivalents, nor are alternative credential encryption or firewall management approaches for non-Windows platforms provided. This may create friction or confusion for users deploying self-hosted integration runtime on Linux or macOS, or those who do not use PowerShell.
Recommendations
- Add explicit guidance for deploying and securing self-hosted integration runtime on Linux and macOS, including credential encryption and storage options.
- Provide examples using cross-platform tools (e.g., Azure CLI, REST API) for credential management, in addition to PowerShell.
- Clarify whether DPAPI and Windows Firewall requirements apply only to Windows hosts, and describe alternatives for Linux/macOS (e.g., using Gnome Keyring, libsecret, or other OS-native encryption).
- Include port and firewall configuration instructions for Linux (e.g., iptables, firewalld, ufw) and macOS (pf, application firewall).
- Indicate if any features (such as encrypted credential storage) are unavailable or different on non-Windows platforms.
Create Pull Request
Clean