Azure VNET Gateway for Expressroute - impact if public IP changes

Chris Lhamon 0 Reputation points
2024-09-09T19:39:50.93+00:00

I have a production environment that has a VNET Gateway (type Expressroute) and it's working fine right now. However, the public IP that it has is a Basic SKU, and that's going away on September 30, 2025. On top of that, it's a dynamic Public IP.

I know that I'll have to remove the Public IP from the VNET Gateway, change it from dynamic to static, then change the SKU to Standard, and put the Public IP back on the VNET Gateway. I have heard that this will change the IP. I haven't see how that IP is actually used. It's not in any other configuration of anything that I can see.

Assuming that the IP will change, is there anything that I would need to do to keep the VNET Gateway working with the new IP? Thanks in advance for any help.

Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,408 questions
Azure ExpressRoute
Azure ExpressRoute
An Azure service that provides private connections between Azure datacenters and infrastructure, either on premises or in a colocation environment.
367 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. KapilAnanth-MSFT 44,556 Reputation points Microsoft Employee
    2024-09-10T07:21:32.6533333+00:00

    @Chris Lhamon ,

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

    I understand that you would like to upgrade your Basic Public SKU using ExpressRoute Gateway to use a Standard Public SKU.

    AFAIK, The public IP address is used for internal management only.

    See : Why is there a public IP address associated with the ExpressRoute gateway on a virtual network?

    With that said,

    • I should highlight the fact that you don't have to be concerned by this.
    • Because, to upgrade an ExR Gateway - New ExpressRoute Gateway is required anyway
    • Also, there is no requirement here that you should use the same Public IP (basic upgraded to Standard) with the new ExR Gateway - you can use a different Public IP as well.
    • Since you are creating a new ExR Gateway, you should also create new connections to ExR Circuits that were previously using the old ExR Gateway
      • While you do this, the platform will consider the new ExR Gateway with the newer IP for it's internal management
      • i.e., everything is handled by platform.

    TL:DR;

    • You are basically deleting and recreating the ExR Gateway and it's Connections
    • So it does not matter if the Public IP of the Gateway changes or not.
    • For more info, see : ExpressRoute Gateway migration guidance.

    Please let us know if we can be of any further assistance here.

    Thanks,

    Kapil


    Please Accept an answer if correct.

    Original posters help the community find answers faster by identifying the correct answer.

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.