Cannot remote Azure Batch nodes suddenly

Junjian Xia 47 Reputation points • Microsoft External Staff

Those nodes could be Remote last week, but they have not been used much recently. Today, I found that clicking Connect did not respond, and the Azure Portal showed 'Remote login is disabled for this pool.'👁 User's image
👁 User's image

  1. Junjian Xia 47 Reputation points • Microsoft External Staff

    Thank you. After updating the network configuration, it's now working.

Sign in to comment

Answer accepted by question author and recommended by moderator

Hemalatha 14,525 Reputation points • Microsoft External Staff • Moderator

Hello Junjian Xia,

Thank you for contacting Microsoft Support regarding the Azure Batch pool remote connectivity issue.

We understand that the Azure Batch pool nodes were previously accessible, but the Azure portal is now displaying the message “Remote login is disabled for this pool,” and the Connect option is no longer responding.

Based on our analysis, this behavior is related to a platform change introduced in Azure Batch networking behavior. Beginning with API version 2024-07-01, and for pools created, resized, or recreated after 30 November 2025, Azure Batch no longer automatically maps remote access ports for SSH (Linux) or RDP (Windows). As a result, pools that previously allowed remote connectivity may lose those mappings after a resize or recreation activity unless endpoint configuration is explicitly defined.

👁 User's image
The “Remote login is disabled for this pool” message, along with blank IPv4/IPv6 values in the Connect pane, is the expected behavior when the required inbound endpoint configuration is not present.

To restore remote access functionality, the pool must be configured with an Inbound NAT pool and corresponding Network Security Group (NSG) allow rules.

As part of the resolution, please follow the below steps:

  • Scale the pool down to 0 nodes. Endpoint configuration is part of the pool NetworkConfiguration and cannot be modified while compute nodes are active.
  • Update the pool endpoint configuration by adding the required Inbound NAT pool for the remote access protocol being used: SSH (Port 22) for Linux nodes and RDP (Port 3389) for Windows nodes

This can be configured using the Azure Batch Management REST API, Azure CLI, or SDK.

After the configuration update is completed successfully, scale the pool back to the required node count.

Once the nodes return to the running state, navigate to the node in the Azure portal and select Connect. The remote login IP address and port details should now populate correctly, allowing remote connectivity to the node

If modifying the existing pool is not preferred, an alternative approach would be to create a new pool with the endpoint. Configuration defined during pool creation, which avoids the need for scaling activities later.

For additional reference, please review the following documentation:

Azure Batch pool endpoint configuration: https://learn.microsoft.com/en-us/azure/batch/pool-endpoint-configuration

Azure Batch Pool Update REST API: https://learn.microsoft.com/en-us/rest/api/batchmanagement/pool/update

Microsoft Tech Community reference: https://techcommunity.microsoft.com/blog/azurepaasblog/configure-remote-access-to-compute-nodes-in-an-azure-batch-pool-using-azure-port/4368870

Hope this helps! Please let me know if you have any queries.

0 comments No comments
Sign in to comment

1 additional answer

  1. Alex Burlachenko 22,120 Reputation points • MVP • Volunteer Moderator

    Junjian Xia hi & thanks for join me here at Q&A portal,

    this is not node health, its pool config. Azure Batch only allows SSH/RDP if remote login is enabled on the pool and inbound access is allowed. Portal showing Remote login is disabled for this pool means Batch currently thinks the pool was created/updated with remote access disabled, so adding a user wont help because there is no remote endpoint/port exposed. First check pool networking and start task/pool settings, especially any recent pool update, autoscale resize, reimage, or IaC redeploy. If the pool is VM configuration with publicIPAddressConfiguration set to NoPublicIPAddresses, or inbound NAT pools are disabled/blocked, portal Connect will show exactly this kind of behavior. Since it worked last week, I would check Activity Log for Microsoft.Batch/batchAccounts/pools/write around that time to see if the pool was updated. Practical fix is usually to recreate or update the pool with remote login enabled / public IP or proper private access path, then add an admin user again. If no config changed and Activity Log is clean, open Batch support with pool ID, node ID, screenshots, and timestamp. tl dr Batch says remote login is disabled at pool level, not user level, so fix pool remote access/networking config first. But I saw u already done that issue, so u are so cool )

    rgds,

    Alex

    &

    If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal
    0 comments No comments
    Sign in to comment
Sign in to answer

Your answer