Share via

Problem with LB upon upgrade to Standard from Basic

Pawel Turyła 0 Reputation points
2025-07-30T12:52:43.6033333+00:00

We have a problem with production upon upgrade of ALB from basic to standard. We need Microsoft assistance to diagnoze the problem. Our prod application stopped working.

Azure Load Balancer
Azure Load Balancer
An Azure service that delivers high availability and network performance to applications.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ganesh Patapati 8,755 Reputation points Microsoft External Staff Moderator
    2025-07-30T16:22:08.7233333+00:00

    Hello Pawel Turyła

    1. What specific errors or symptoms are you observing in your application?
    2. Have you reviewed the Load Balancer configuration post-upgrade? If so, were there any mismatches?
    3. Are there any specific services or endpoints in your application that are particularly affected?
    4. Can you please elaborate more in detail about the issue.

    Meantime,

    We recommend the following approach for upgrading to Standard Load Balancer:

    1. Learn about some of the key differences between Basic Load Balancer and Standard Load Balancer.
    2. Identify the Basic Load Balancer to upgrade.
    3. Create a migration plan for planned downtime.
    4. Perform migration with automated PowerShell scripts for your scenario or create a new Standard Load Balancer with the Basic Load Balancer configurations.
    5. Verify your application and workloads are receiving traffic through the Standard Load Balancer. Then delete your Basic Load Balancer resource.

    Also, can you please try Upgrading a Basic to Standard public load balancer with PowerShell commands.

    please let me know results

    The latest update published today states, in regards to Basic SKU VPN Gateway:

    • Your actual IP address will not change, and connectivity will not be interrupted.
    • An automated capability to remove the Basic public IP from your gateway will be available in Sept/Oct 2025
    • Deprecation timeline of Basic IP for all VPN Gateways is moved from Sep 2025 to end of Jan 2026
    • Because Microsoft is retiring Basic public IP resources, we’re updating the Basic VPN Gateway construct. You’ll see the Basic public IP reference as an attribute on your virtual network gateway.
    • If you have scripts, ARM templates, or monitoring solutions that reference the Basic public IP resource, update them to use the IP address property of the virtual network gateway instead.

    No action needed at this time. I just wanted to give you latest info.

    I hope this has been helpful!

    If the above is unclear or you are unsure about something, please add a comment below.

    0 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.