Hello Bryan Jesús Orosco Quispe
Thank you for reaching out to the Microsoft Q&A platform.
We noticed that you rated an answer as not helpful. We value your feedback and want to know if there is anything we can do to improve it and make this a positive experience for you. Hence, I am adding an answer to your query below. If it helps, please click "Accept as answer" as a token of appreciation and hit Yes for "was this answer helpful"
Answer:
Azure provides the option to use a static IP address with a VM, but it cannot guarantee that the static IP is brand new and has never been used before or recycled. Azure uses a pool of IP addresses, and when a static IP address is released, it goes back into the pool and can be assigned to another customer.
Also, please note, when you set the allocation method to static, you cannot specify the actual IP address assigned to the public IP address resource. Azure assigns the IP address from a pool of available IP addresses in the Azure location the resource is created in.
Another option is to use Azure Virtual Network (VNet) with a VPN Gateway. With a VPN Gateway, you can create a site-to-site VPN connection between your on-premises network and your Azure VNet. This will allow you to use your on-premises public IP address for your Azure VM.
References:
https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-addresses#ip-address-assignment
https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-network-deploy-static-pip-arm-portal
https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-addresses
--please don't forget to "[Accept the answer]" if the reply is helpful--