Private Endpoint Batch Account and Pool With Public IP

[ghost]

In my corporate environment, we only enable service and GA features.

Since batch account private link is GA, so I would like to use the feature.
But create the pool in private vnet without public ip is in preview

Does this combination make any sense, batch account FQDN is my private endpoint, but the pool is created with public IP?
Why I need a private endpoint batch account to communicate to pool node via public ip?

[Enter feedback here]

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: ccb356b2-fb60-e833-94c0-68e7b020949e
• Version Independent ID: 06b27a8c-86c4-3f99-0393-0cc74f3e3053
• Content: Use private endpoints with Azure Batch accounts - Azure Batch
• Content Source: articles/batch/private-connectivity.md
• Service: batch
• GitHub Login: @JnHs
• Microsoft Alias: jenhayes

[psmanhas]

@RonnieQuan Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate. We will update you accordingly.

[psmanhas]

@JnHs Can you please check and add your comments on this doc update request as applicable

[JnHs]

Hi @RonnieQuan, these are separate features and that scenario is supported if it meets your needs. Of course, using private endpoints with pools that don't use public IP addresses is also a supported scenario although you are correct, pools without public IP addresses are still in public preview at this time.
I will close this issue now but let us know if there are further issues related to this document!
#please-close