Document Details
Connect To Node
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
windows_first
windows_tools
missing_linux_example
Summary
The documentation page provides connection instructions for both Linux and Windows nodes, but Windows-specific tools (RDP, Microsoft RDP client) and examples are mentioned explicitly and sometimes before Linux equivalents. There are detailed instructions for setting up RDP tunnels for Windows, but no equivalent examples for connecting to Linux graphical desktops (e.g., via X11 forwarding or VNC). The documentation references Microsoft RDP client for macOS and Windows, but does not mention Linux RDP clients or alternatives. Overall, the page assumes familiarity with Windows tools and workflows, and omits Linux-specific graphical connection patterns.
Recommendations
- Include examples for connecting to Linux graphical desktops, such as X11 forwarding (e.g., 'ssh -X') or VNC tunnels.
- Mention Linux-compatible RDP clients (e.g., 'remmina', 'xfreerdp') when discussing RDP connections.
- Provide parity in graphical connection instructions for both Linux and Windows nodes.
- When describing connection methods, present Linux and Windows options side-by-side, rather than focusing on Windows tools first.
- Clarify that SSH-based connections are standard for Linux nodes, and provide troubleshooting tips for common Linux SSH issues.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-12 00:00 | #99 | completed |
Biased
|
| 2026-01-11 06:20 | #98 | completed |
Biased
|
| 2026-01-10 00:00 | #92 | completed |
 Clean
|
| 2026-01-06 22:28 | #78 | completed |
Clean
|
| 2025-12-29 18:00 | #48 | cancelled |
Biased
|
| 2025-12-15 00:00 | #7 | completed |
Clean
|
| 2025-12-14 05:05 | #6 | completed |
Clean
|
Flagged Code Snippets
> [!NOTE] > CycleCloud picks an unused ephemeral port for the tunnel to the Windows VM. You can set up the `cyclecloud` command to use one bastion host for all your connections with this command:
With this directive, you can run `cyclecloud connect htcondor-scheduler` without specifying any details about the bastion server. You can also use `cyclecloud connect` to connect a Windows VM. When you run the following command, it creates an RDP connection over an SSH tunnel. It also starts the Microsoft RDP client on macOS and Windows:
This command connects to the bastion server and then immediately runs SSH again, so you get a terminal on the target VM. You might need to specify a user other than `cyclecloud` on the VM if you configured your cluster differently. The `-A` argument forwards the agent connection so your private key on your local machine is used automatically. Agent forwarding works as a chain, so the second SSH command also includes `-A` to ensure that any subsequent SSH connections initiated from the target VM also use your local private key. ### Connecting to services on the target VM You can use the SSH connection to connect to services on the target VM, such as a Remote Desktop, a database, and more. For example, if the target VM is Windows, you can create a Remote Desktop tunnel by connecting to the target VM with an SSH command similar to the following example, using the `-L` argument: