Why is the new public IP not showing after Express Route Virtual Network Gateway migrtation

Dwight Thompson 30 Reputation points
2025-07-25T13:54:59.15+00:00

I performed the Express Route migration for the basic public IP to Standard public IP. After the migration completed, I no longer see the public IP on the Express Route Virtual Network Gateway overview page.

Azure ExpressRoute
Azure ExpressRoute
An Azure service that provides private connections between Azure datacenters and infrastructure, either on premises or in a colocation environment.
{count} vote

Accepted answer
  1. Raed Boshmaf 80 Reputation points Microsoft Employee
    2025-08-02T13:15:04.81+00:00

    If you are moving to AZ ExRGW it is expected that you will not see the PIP anymore, the reason for that is the use of Hosted On Behalf Of (HOBO) IP assignment

    So with the migration tool that option will not be visable anymore and we will update our document for that

    image.png

    And when you create new ExRGW the wizard will tell you that
    image.png

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. G Sree Vidya 4,005 Reputation points Microsoft External Staff Moderator
    2025-07-25T19:59:12.8266667+00:00

    Hello Dwight Thompson

    We understand that you are encountering an issue where the new public IP isn’t visible on your ExpressRoute Virtual Network Gateway after migrating from a Basic public IP to a Standard public IP. This can sometimes happen during the migration process.

    1. During the migration, Azure may deploy a new gateway behind the scenes, especially if you're moving to a Standard SKU or enabling availability zones.
    2. This new gateway might have a different resource ID and configuration, which can cause the public IP to not show up immediately in the overview pane.
    3. Try refreshing your portal page or logging out and back in to see if the public IP appears.
    4. Sometimes, the Azure portal takes time to reflect changes. The public IP might be correctly associated but not yet visible due to UI caching or sync delays.
    5. If the migration wasn't fully completed or if there was a misstep, the Standard public IP might not have been correctly associated with the gateway.

    Please validate and check below details:

    • Go to the Public IP resource in the Azure portal and verify its association. It should be linked to the new gateway.
    • Navigate to the ExpressRoute Gateway settings and check the configuration under the "Gateway SKU Migration" section.
    • Run commands to list the public IPs associated with the gateway to confirm the linkage:
        az network public-ip show --name <your-ip-name> --resource-group <your-rg>
      
    • You can check the Activity Log in the Azure portal for any errors or warnings during the migration.

    I hope this helps! If these answers your query, do click the "Upvote" of which might be beneficial to other community members reading this thread.

    Please let us know if you have any questions or concerns. We are happy to assist you.


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.