Bias Analysis
Detected Bias Types
windows_only
powershell_heavy
windows_tools
missing_linux_example
windows_first
Summary
The documentation is heavily biased toward Windows environments. All installation instructions, prerequisites, and examples assume a Windows OS, with explicit references to Windows versions, Windows-only tools (PowerShell, registry edits, Windows Firewall, NT SERVICE accounts), and Windows-specific configuration steps. There is no mention of Linux or macOS support, nor any examples or guidance for non-Windows platforms. The use of Windows Data Protection API (DPAPI) for credential encryption further cements the Windows-only approach. All automation and scripting examples use PowerShell, and the installer is distributed as a Windows MSI. The documentation does not clarify whether Linux/macOS are unsupported or simply omitted.
Recommendations
- Explicitly state OS support: If self-hosted integration runtime is Windows-only, clarify this early in the documentation. If Linux/macOS support is planned or available, provide equivalent instructions.
- Provide Linux/macOS installation guidance: If supported, add sections for installing and configuring on Linux/macOS, including prerequisites, service management, and credential storage.
- Offer cross-platform automation examples: Include Bash/shell scripts and CLI instructions alongside PowerShell for automation.
- Reference Linux/macOS equivalents for configuration: For steps involving Windows tools (e.g., registry edits, Windows Firewall), provide Linux/macOS alternatives or note their absence.
- Clarify tool requirements: If only Windows tools are supported (e.g., dmgcmd.exe, Configuration Manager), state this and suggest alternatives or workarounds for other platforms.
Create Pull Request