KeyVaultNetworkRuleSetBase IpAddressRange limit of 127, KeyVault Doc IPV4 limit is 1000

[eugenecp]

I'm passing more than 127 IP addresses to Update-AzKeyVaultNetworkRuleSet -IpAddressRange and get the error:

Cannot validate argument on parameter 'IpAddressRange'. The parameter requires at least 0 value(s) and no more than 127 value(s) - 135 value(s) were provided.

Checking the code, at https://github.com/Azure/azure-powershell/blob/main/src/KeyVault/KeyVault/Commands/VirtualNetworkRuleSet/KeyVaultNetworkRuleSetBase.cs#L32, there's a constraint to limit to 127.

`[Parameter(Mandatory = false, HelpMessage = "Specifies allowed network IP address range of network rule.")]

[ValidateCount(0, 127)]
public string[] IpAddressRange { get; set; }
`

KeyVault documentation https://learn.microsoft.com/en-us/azure/key-vault/general/network-security states the limit is 1000 IPv4 rules are allowed

Be aware of the following configuration limitations:
A maximum of 200 virtual network rules and 1000 IPv4 rules are allowed.
IP network rules are only allowed for public IP addresses. IP address ranges reserved for private networks (as defined in RFC 1918) are not allowed in IP rules. Private networks include addresses that start with 10., 172.16-31, and 192.168..
Only IPv4 addresses are supported at this time.

Can I request a fix for this?

Thanks.

[dolauli]

The ValidateCount is there for five years, maybe outdated.
@BethanyZhou, would you confirm whether we could set IpAddressRange with an array with elements between [128, 1000] with the restful API.

[BethanyZhou]

Same issue with #22137, please expect the fix available on 2023-08-01.

[isra-fel]

Please update to Az 10.2.0: https://www.powershellgallery.com/packages/Az/10.2.0