Increase 150 endpoints limit for a cloud service
Today there are a hard limit of maximum 150 endpoints per Cloud Service.
When having VMs in a Cloud Service, you need to have at least two VMs in each Cloud Service to get SLA.
For each VM you add to a Cloud Service your endpoint count will double. If you've got the need for 50 endpoints or more per VM, you won't be able to run more than two VMs in a Cloud Service (since there are already two ports used by default).
We've got several cases where we need to have a lot of endpoints on our VMs. The limit of 150 endpoint is very limiting for us. Especially if we want to use automatic scaling with more than two VMs in a cloud service.
So please remove, or at least increase, the endpoint limit for a Cloud Service!
Port ranges have been introduced some time ago now, so this issue no longer is an issue.
I am in agreement to this as well please remove the limit or allow port ranges!
I would agree with this strongly. Although I can use a PIP to overcome this issue, it leaves me in a position where I cannot use an Availability Set as I have no way of load balancing (failure mode) the machines contained within that set. So I'm left with 1 machine running on its own and with the possibility of downtime due to unplanned or planned work by Microsoft.
ftp server, voip server, multiplayer game server, etc....
Limit to 150 entries in endpoints is fine, as long as we are able to enter port ranges...
It seems very silly to not being able to add multiple port addresses in range format to the azure vm endpoints. This really is a show stopper to switch over to azure, otherwise all tests came out quite good, performance etc... PLEASE ALLOW PORT RANGES