Hello @Brad Farmer ,
Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
- Helix(Perforce) Core are SAAS offering from Perforce and hence the instance settings are managed by the SAAS provider on Azure Marketplace.
- Hence Perforce support team need to be engaged to advise the settings on the Helix instance
- I found once article which talks about setting up the keepalives to maintain TCP settings on Helix instance and on client side. Refer the below article.
- https://portal.perforce.com/s/article/net-keepalive-settings-don-t-always-work-with-parallel-syncs-in-Helix-Core
- Since you already mentioned that you are not running Azure Firewall or a Load Balancer or other transit device, it seems you need to tune TCP settings on instance itself.
- set-azureendpoint command is long deprecated and was useful for configuring endpoints and ACLs(Replaced by NSG), it does not directly modify TCP settings. The cmdlet was part of the Azure Service Management (ASM) model (aka "classic" deployment model), which has largely been replaced by Azure Resource Manager (ARM).
Hope the answer is able to help to reach the right support.
If the below answer addressed your query, please don’t forget to click "Accept the answer" and Up-Vote for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.
Thanks,
Ujjawal Tyagi