The documentation focuses exclusively on troubleshooting TLS cipher suites for Windows Arc-enabled servers. All examples and instructions use Windows-specific tools (PowerShell, Group Policy, Registry Editor), and there is no mention of how to check or enable cipher suites on Linux or macOS Arc-enabled servers. This creates friction for non-Windows users who may encounter similar networking issues.

• Add a section for troubleshooting TLS/cipher suite issues on Linux and macOS Arc-enabled servers.
• Provide equivalent commands for checking enabled cipher suites on Linux (e.g., using 'openssl', 'nmap', or 'sslyze').
• Describe how to configure cipher suites on common Linux distributions (e.g., by editing OpenSSL configuration or using system security policies).
• Clarify whether the described issue is Windows-specific or if Linux/macOS users may also be affected.

The release notes for the Azure Connected Machine agent generally provide parity between Windows and Linux, with download links and versioning for both platforms. However, there is a mild Windows bias: Windows examples, installer instructions, and troubleshooting steps (e.g., using PowerShell, msiexec, GUI actions) are described in detail, while equivalent Linux instructions (e.g., using rpm, deb, systemctl, or shell commands) are not provided or referenced. Windows-specific issues and improvements are often listed first, and some improvements (such as PowerShell script enhancements) are only mentioned for Windows. Linux-specific troubleshooting steps and installer guidance are missing, which could create friction for Linux users.

• Provide equivalent Linux installer troubleshooting guidance (e.g., using rpm, deb, or shell commands) alongside Windows instructions.
• Include Linux-specific examples or notes where Windows PowerShell or GUI actions are described.
• When listing features, alternate or balance the order between Windows and Linux, or group by feature rather than OS.
• Add links or references to Linux agent installation and management documentation where appropriate.
• Explicitly mention Linux equivalents for Windows tools (e.g., PowerShell vs. shell scripts, msiexec vs. rpm/deb).