We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
Could be a good idea to add in the LB query verification of NAT rules. Right now it only checks for empty backend pools
| where type == 'microsoft.network/loadbalancers' | where properties.backendAddressPools == '[]' | where properties.inboundNatRules == '[]'
Thanks :-)
The text was updated successfully, but these errors were encountered:
Hi @kornflejk ,
First, thanks for your suggestion.
Manage inbound NAT rules for Azure Load Balancer An inbound NAT rule is used to forward traffic from a load balancer frontend to one or more instances in the backend pool.
So, if a Load balancer does not have a backendAddressPools , that is enough to identify him as orphaned Load Balancer.
Sorry, something went wrong.
No branches or pull requests
Hello,
Could be a good idea to add in the LB query verification of NAT rules.
Right now it only checks for empty backend pools
| where type == 'microsoft.network/loadbalancers'
| where properties.backendAddressPools == '[]'
| where properties.inboundNatRules == '[]'
Thanks :-)
The text was updated successfully, but these errors were encountered: