I have followed the article and setup private link, however I would like to reserve the private IP assigned to the link so that we can use this IP directly to access the SQL server and there is no chance of losing it. When I try to set the IP address to static from the virtual network, I get an error that I cannot set it to static because it is linked to a private endpoint. Is there another way that I can reserve this private IP?
Thanks,
Ojas
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@ojasp Thank you for your feedback! We will review and update as appropriate.
@mike-urnun-msft any update on this?
@mike-urnun-msft any update? I face same issue on a storage account, cannot change IP to static. I receive this message : Failed to save IP address changes for network interface 'xxxxxxprivateendpoint.nic.b34c0164-3956-4ecd-xxxxx-xxxxxxx'. Error: An error occurred.
With Private Endpoints in general, the generated network interface is read-only and managed within the life cycle of the Private Endpoint resource.
Values cannot be changed like allocation method to static, although those values will never change during the entire life of the private endpoint.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.
The reason for me wanting a static IP address for a Private Endpoint is because I like to provision an environment ...where I can say that private domain zone XXX.COM is pointing to private link Endpoint with IP Address xxx.xxx.xxx.xxx. I have seen references to FQDNs and using private Zones in the documentation but was unable to use those with terraform: https://www.terraform.io/docs/providers/azurerm/r/private_endpoint.html...and I am not completely sure if this will enable my desired scenario as well. Any help/ advice is appreciated
@jaschoen-msft @mike-urnun-msft mike-urnun-msft Do we have plans to enable updating nics to static in the future?
In many Enterprise scenarios, creating firewall holes is a painful internal process taking many days. Having the ability to assign static IPs to any particular resource helps significantly adopting these technologies.
Otherwise every time a new environment is provisioned, you would need to deploy first, find the IP addresses and then ask for firewall holes; instead of planning ahead.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.
While this isn't a documentation issue, it is actually feature that ought to be able to be set whereby a customer can configure and reserve an IP address for a private endpoint. As mentioned, if anything were to ever change with this IP address, it could take days to go through change control for firewall rules etc in enterprises.
There needs to be a way for a customer to statically allocate an IP address (or tell it what free IP address to use in a subnet) for an endpoint at create time.
Most helpful comment
With Private Endpoints in general, the generated network interface is read-only and managed within the life cycle of the Private Endpoint resource.
Values cannot be changed like allocation method to static, although those values will never change during the entire life of the private endpoint.