VNET bug with az network lb address-pool address add

[mahipdeora]

Describe the bug

az network lb address-pool address add shouldn't require a VNet or subnet to be passed in. Since the Vnet can be applied at the LB's backend pool level not at the backend address level.

Related command

az network lb address-pool address add

Errors

The Vnet is added to the backend pool, so when customers try to pass in the Vnet via this command we get an NRP error. When no Vnet is applied we hit an error saying "Vnet or subnet is required" <- this limit should be removed. In addition, on docs it lists Vnet and subnet as optional parameters.

Issue script & Debug output

NA

Expected behavior

If a VNet is applied at the backend pool level then Vnet or subnet shouldn't be required via the az network lb address-pool address add command

Environment Summary

Using cloud shell

Additional context

No response

[yonzhan]

Thank you for opening this issue, we will look into it.