Validate Firewall Rules priority conflicts before starting deployment
When creating a new VM and a new network with inbound firewall rules, if you add two rules with the same priority it will pass validation (see attached screenshot). It will however later fail the deployment with an obscure error message.
Firewall rule priority conflict detection should happen instantly as you type in the rule textbox. That green checkmark should have been red and saying "there is already another rule with this priority"
Kirill Osenkov
shared this idea
Hi Kirill, thanks for the feedback. This seems like an issue with Portal validation. We will look into fixing this and update the status as appropriate.
1 comment
-
Kirill Osenkov
commented
{
"error": {
"code": "SecurityRuleConflict",
"message": "Security rule ElasticSearch conflicts with rule HTTP. Rules cannot have the same Priority and Direction.",
"details": []
}
}