Please raise the maximum number of Endpoint ACL limitation so we can set over 50 rules.
As you know, we can set 400 rules in NSG.
エンドポイント ACL の最大数を 50 個以上設定できるようにしてほしい16 votes
Unfortunately, we will not be able to support a higher number of rules on endpoint ACLs. NSGs could be used in place of endpoint ACLs for easier management of ACLs as well as higher scalability. Would NSGs work for your scenario?
Adding an IP-adress to allow connections, which will be removed after 24hrs for instance.6 votes
we will not be doing a time based ACL.
Virtual machine scale sets (VMSS) do not have any feature which can allow blocking certain IP addresses from accessing it via load balancer. It would be great to have network security group support for VMSS to allow blocking unwanted traffic from the internet.3 votes
Thanks for the feedback!, this feature is already in place, for VMSS you can assign an NSG at the subnet level, this will enable you to control the traffic on your VMSS.
Network Security Groups only allow us to use specific resources, tags, and IP ranges. Many APIs and other tools add/remove/change IP ranges regularly, given that clients are expected to point to the domain endpoint (e.g. smtp.gmail.com, Slack API webhooks, etc.).
If we have to get new IP ranges and add them to NSGs, it creates an extra task. We should be able to use domain names/FQDNs/etc. with wildcards (e.g. *.gmail.com, *.slack.com) for NSG allow or deny rules so we have one less administrative task.3 votes
Thanks for the feedback, we are currently supporting this capability with Azure Firewall to complete the scenario.
- Don't see your idea?