Endpoints can accept a port range instead of entering each open open one at a time
If I have a port range it is really a pain to add endpoints if I need to add a port range between 20000 and 20010 for TCP and UDP. In this case I have to create 20 endpoints.
I’m closing this one out as completed. If you’d like to see HA Ports on public Load Balancer as well, please vote for https://feedback.azure.com/forums/217313-networking/suggestions/31874281-ha-ports-for-standard-load-balancers-with-public-i
Michel van Kessel commented
Please post an update on this matter, many thanks Microsoft. This will help out so many people
Any update on this?
We stumble on it more and more, when customers are moving from a 'test' single NVA to 'production' double NVA (for HA).
We really need your comments about this feature, how or when should we add ports in range rather than specific port. this is quite important for us, so far, we notice NSG support ports in ragne, will that extend to LB soon? if yes, please share with us ETA
GIRAUD Alexandre commented
Hi, Yes we really need that and espcially when limit is 150 rules and we need open some range using more than 150 ports.
It would also be nice to allow/block known ranges of IP addresses. For example, only allow the US block if IP ranges. This will help filter out unwanted traffic.
Sushanth Amin commented
Yes this is an issue let's say if i want to add a port range from 1123 - 1220, i cannot do the needful in Azure Endpoint, as soon as i add (-) it says does not identify anything apart from numerical. Azure needs to bring in the feature as soon as possible to enable port range in Azure Endpoint.
This basic feature should be standard out of the box, adding in multiple entries for a range is killing me - even when using Powershell as it takes so long for each entry to process.
Alleo Pineda Indong commented
will support this