Add ability to add multiple IP configs when creating a Private Link Service with the destination IP address property #31727
Description
Preconditions
- No need to upgrade Python SDK or the Python SDK is ready.
Related command
az network private-link-service create --destination-ip-address
Resource Provider
Microsoft.Network/privateLinkServices
Description of Feature or Work Requested
Creating a Private Link Service with a destination IP address requires at least 3 SNAT IPs to be configured for high availability and security. Currently only 1 IP config is allowed in CLI and customers are getting an error that they need 3 but cannot add 3 in CLI.
The request is to add the ability to add IP configs when creating a Private Link Service with a destination IP address so customers can specify multiple IP configs and meet the deployment requirements.
Minimum API Version Required
N/A
Swagger PR link / SDK link
Request Example
No response
Target Date
07/30/2025
PM Contact
Engineer Contact
[email protected], [email protected], [email protected], [email protected]
Additional context
CRIs have been raised where customers report that they cannot add IP configs as it is hardcoded to be 1 snat IP and are getting the following error message.
IP config limitation reference
azure-cli/src/azure-cli/azure/cli/command_modules/network/custom.py at release-2.74-cm2 · Azure/azure-cli
Error message
Code: PrivateLinkServiceForUdrFeatureDoesNotMeetIpConfigurationRequirements Message: You must include a minimum of 3 IP configurations for PLS UDR in Private Link Service: /subscriptions/<subID>/resourceGroups/middle-express-feature/providers/Microsoft.Network/privateLinkServices/egress-direct-feature-service. For more information, please refer to https://aka.ms/pls-udr