Skip to content

Commit 2e8b28c

Browse files
v-regandownerv-regandowner
authored
Merge pull request #210595 from mbender-ms/lb-basic-upgrade
Load Balancer - New Docs - Basic IP & LB
2 parents 9aabd55 + 592d7ab commit 2e8b28c

File tree

5 files changed

+139
-2
lines changed

5 files changed

+139
-2
lines changed

‎articles/load-balancer/TOC.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -198,6 +198,8 @@
198198
href: configure-vm-scale-set-cli.md
199199
- name: Upgrade from a basic to standard load balancer
200200
items:
201+
- name: Upgrade options and guidance
202+
href: load-balancer-basic-upgrade-guidance.md
201203
- name: Upgrade a basic public load balancer
202204
href: upgrade-basic-standard.md
203205
- name: Upgrade an internal load balancer - Outbound connections not required
@@ -214,9 +216,9 @@
214216
href: load-balancer-multiple-ip-powershell.md
215217
- name: Move across regions
216218
items:
217-
- name: Public Load Balancer - Portal
219+
- name: Public load balancer - Portal
218220
href: move-across-regions-external-load-balancer-portal.md
219-
- name: Public Load Balancer - PowerShell
221+
- name: Public load balancer - PowerShell
220222
href: move-across-regions-external-load-balancer-powershell.md
221223
- name: Internal load balancer - Portal
222224
href: move-across-regions-internal-load-balancer-portal.md

‎articles/load-balancer/index.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,8 @@ landingContent:
3434
url: https://azure.microsoft.com/updates/?category=networking&query=load%20balancer
3535
- text: Load Balancer SKUs
3636
url: skus.md
37+
- text: Upgrade guidance from basic to standard Load Balancer
38+
url: load-balancer-basic-upgrade-guidance.md
3739
- linkListType: learn
3840
links:
3941
- text: Introduction to Azure Load Balancer

‎articles/load-balancer/load-balancer-basic-upgrade-guidance.md

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
title: Upgrading from basic Load Balancer - Guidance
3+
description: Upgrade guidance for migrating basic Load Balancer to standard Load Balancer
4+
author: mbender-ms
5+
ms.service: load-balancer
6+
ms.author: mbender
7+
ms.topic: overview
8+
ms.date: 09/19/2022
9+
#customer-intent: As an cloud engineer with basic Load Balancer services, I need guidance and direction on migrating my workloads off basic to standard SKUs
10+
---
11+
12+
# Upgrading from basic Load Balancer - Guidance
13+
14+
In this article, we'll discuss guidance for upgrading your Basic Load Balancer instances to Standard Load Balancer. Standard Load Balancer is recommended for all production instances and provides many [key differences](#basic-load-balancer-sku-vs-standard-load-balancer-sku) to your infrastructure.
15+
## Steps to complete the upgrade
16+
17+
We recommend the following approach for upgrading to Standard Load Balancer:
18+
19+
1. Learn about some of the [key differences](#basic-load-balancer-sku-vs-standard-load-balancer-sku) between Basic Load Balancer and Standard Load Balancer.
20+
1. Identify the Basic Load Balancer to upgrade.
21+
1. Create a migration plan for planned downtime.
22+
1. Perform migration with [automated PowerShell scripts](#upgrade-using-automated-scripts) for your scenario or create a new Standard Load Balancer with the Basic Load Balancer configurations.
23+
1. Verify your application and workloads are receiving traffic through the Standard Load Balancer. Then delete your Basic Load Balancer resource.
24+
25+
## Basic Load Balancer SKU vs. standard Load Balancer SKU
26+
27+
This section lists out some key differences between these two Load Balancer SKUs.
28+
29+
| Feature | Standard Load Balancer SKU | Basic Load Balancer SKU |
30+
| ---- | ---- | ---- |
31+
| **Backend type** | IP based, NIC based | NIC based |
32+
| **Protocol** | TCP, UDP | TCP, UDP |
33+
| **[Frontend IP configurations](../azure-resource-manager/management/azure-subscription-service-limits.md#load-balancer)** | Supports up to 600 configurations | Supports up to 200 configurations |
34+
| **[Backend pool size](../azure-resource-manager/management/azure-subscription-service-limits.md#load-balancer)** | Supports up to 1000 instances | Supports up to 300 instances |
35+
| **Backend pool endpoints** | Any virtual machines or virtual machine scale sets in a single virtual network | Virtual machines in a single availability set or virtual machine scale set |
36+
| **[Health probe types](load-balancer-custom-probe-overview.md#probe-types)** | TCP, HTTP, HTTPS | TCP, HTTP |
37+
| **[Health probe down behavior](load-balancer-custom-probe-overview.md#probe-down-behavior)** | TCP connections stay alive on an instance probe down and on all probes down | TCP connections stay alive on an instance probe down. All TCP connections end when all probes are down |
38+
| **Availability zones** | Zone-redundant and zonal frontends for inbound and outbound traffic | Not available |
39+
| **Diagnostics** | [Azure Monitor multi-dimensional metrics](load-balancer-standard-diagnostics.md) | Not supported |
40+
| **HA Ports** | [Available for Internal Load Balancer](load-balancer-ha-ports-overview.md) | Not available |
41+
| **Secure by default** | Closed to inbound flows unless allowed by a network security group. Internal traffic from the virtual network to the internal load balancer is allowed. | Open by default. Network security group optional. |
42+
| **Outbound Rules** | [Declarative outbound NAT configuration](load-balancer-outbound-connections.md#outboundrules) | Not available |
43+
| **TCP Reset on Idle** | Available on any rule | Not available |
44+
| **[Multiple front ends](load-balancer-multivip-overview.md)** | Inbound and [outbound](load-balancer-outbound-connections.md) | Inbound only |
45+
| **Management Operations** | Most operations < 30 seconds | Most operations 60-90+ seconds |
46+
| **SLA** | [99.99%](https://azure.microsoft.com/support/legal/sla/load-balancer/v1_0/) | Not available |
47+
| **Global VNet Peering Support** | Standard ILB is supported via Global VNet Peering | Not supported |
48+
| **[NAT Gateway Support](../virtual-network/nat-gateway/nat-overview.md)** | Both Standard ILB and Standard Public Load Balancer are supported via Nat Gateway | Not supported |
49+
| **[Private Link Support](../private-link/private-link-overview.md)** | Standard ILB is supported via Private Link | Not supported |
50+
| **[Global tier (Preview)](cross-region-overview.md)** | Standard Load Balancer supports the Global tier for Public LBs enabling cross-region load balancing | Not supported |
51+
52+
For information on limits, see [Load Balancer limits](../azure-resource-manager/management/azure-subscription-service-limits.md#load-balancer).
53+
54+
## Upgrade using automated scripts
55+
56+
Use these PowerShell scripts to help with upgrading from Basic to Standard SKU:
57+
58+
- [Upgrading a basic to standard public load balancer](upgrade-basic-standard.md)
59+
- [Upgrade from Basic Internal to Standard Internal](upgrade-basicInternal-standard.md)
60+
- [Upgrade an internal basic load balancer - Outbound connections required](upgrade-internalbasic-to-publicstandard.md)
61+
62+
## Next Steps
63+
64+
For guidance on upgrading basic Public IP addresses to Standard SKUs, see:
65+
66+
> [!div class="nextstepaction"]
67+
> [Upgrading a Basic Public IP to Standard Public IP - Guidance](../virtual-network/ip-services/public-ip-basic-upgrade-guidance.md)

‎articles/virtual-network/ip-services/public-ip-basic-upgrade-guidance.md

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
---
2+
3+
title: Upgrading a basic public IP address to standard SKU - Guidance
4+
description: Overview of upgrade options and guidance for migrating basic public IP to standard public IP for future basic public IP address retirement
5+
author: mbender-ms
6+
ms.service: load-balancer
7+
ms.author: mbender
8+
ms.topic: overview
9+
ms.date: 09/19/2022
10+
#customer-intent: As an cloud engineer with Basic public IP services, I need guidance and direction on migrating my workloads off basic to Standard SKUs
11+
---
12+
13+
# Upgrading a basic public IP address to standard SKU - Guidance
14+
15+
In this article, we'll discuss guidance for upgrading your Basic SKU public IPs to Standard SKU. Standard public IPs are recommended for all production instances and provide many [key differences](#basic-sku-vs-standard-sku) to your infrastructure.
16+
## Steps to complete the upgrade
17+
18+
We recommend the following approach to upgrade to Standard SKU public IP addresses.
19+
20+
1. Learn about some of the [key differences](#basic-sku-vs-standard-sku) between Basic SKU public IP and Standard SKU public IP.
21+
1. Identify the Basic SKU public IP to upgrade.
22+
1. Determine if you would need [Zone Redundancy](public-ip-addresses.md#availability-zone).
23+
1. If you need a zone redundant public IP address, create a new Standard SKU public IP address using [Portal](create-public-ip-portal.md), [PowerShell](create-public-ip-powershell.md), [CLI](create-public-ip-cli.md), or [ARM template](create-public-ip-template.md).
24+
1. If you do not need a zone redundant public IP address, use the [following upgrade options](#upgrade-using-portal-powershell-and-azure-cli).
25+
1. Create a migration plan for planned downtime.
26+
1. Depending on the resource associated with your Basic SKU public IP addresses, perform the upgrade based on the following table:
27+
28+
| Resource using Basic SKU public IP addresses | Decision path |
29+
| ------ | ------ |
30+
| Virtual Machine or Virtual Machine Scale Sets | use the [following upgrade options](#upgrade-using-portal-powershell-and-azure-cli). |
31+
| Load Balancer (Basic) | use the [following upgrade options](#upgrade-using-portal-powershell-and-azure-cli). |
32+
| VPN Gateway (Basic) | Cannot dissociate and upgrade. Create a [new VPN gateway with a SKU type other than Basic](../../vpn-gateway/tutorial-create-gateway-portal.md). |
33+
| Application Gateway (v1) | Cannot dissociate and upgrade. Use this [migration script to migrate from v1 to v2](../../application-gateway/migrate-v1-v2.md). |
34+
1. Verify your application and workloads are receiving traffic through the Standard SKU public IP address. Then delete your Basic SKU public IP address resource.
35+
36+
## Basic SKU vs. standard SKU
37+
38+
This section lists out some key differences between these two SKUs.
39+
40+
|""| Standard SKU public IP | Basic SKU public IP |
41+
|---------|---------|---------|
42+
| **Allocation method** | Static. | For IPv4: Dynamic or Static; For IPv6: Dynamic. |
43+
| **Security** | Secure by default model and be closed to inbound traffic when used as a frontend. Allow traffic with [network security group](../network-security-groups-overview.md#network-security-groups) is required (for example, on the NIC of a virtual machine with a Standard SKU public IP attached). | Open by default. Network security groups are recommended but optional for restricting inbound or outbound traffic. |
44+
| **[Availability zones](../../availability-zones/az-overview.md)** | Supported. Standard IPs can be non-zonal, zonal, or zone-redundant. Zone redundant IPs can only be created in [regions where three availability zones](../../availability-zones/az-region.md) are live. IPs created before zones are live won't be zone redundant. | Not supported |
45+
| **[Routing preference](routing-preference-overview.md)** | Supported to enable more granular control of how traffic is routed between Azure and the Internet. | Not supported. |
46+
| **Global tier** | Supported via [cross-region load balancers](../../load-balancer/cross-region-overview.md)| Not supported |
47+
| **[Standard Load Balancer Support](../../load-balancer/skus.md)** | Both IPv4 and IPv6 are supported | Not supported |
48+
| **[NAT Gateway Support](../nat-gateway/nat-overview.md)** | IPv4 is supported | Not supported |
49+
| **[Azure Firewall Support](../nat-gateway/nat-overview.md)** | IPv4 is supported | Not supported |
50+
51+
## Upgrade using Portal, PowerShell, and Azure CLI
52+
53+
Use the Azure portal, Azure PowerShell, or Azure CLI to help upgrade from Basic to Standard SKU.
54+
55+
- [Upgrade a public IP address - Azure portal](public-ip-upgrade-portal.md)
56+
- [Upgrade a public IP address - Azure PowerShell](public-ip-upgrade-powershell.md)
57+
- [Upgrade a public IP address - Azure CLI](public-ip-upgrade-cli.md)
58+
59+
## Next steps
60+
61+
For guidance on upgrading Basic Load Balancer to Standard SKUs, see:
62+
63+
> [!div class="nextstepaction"]
64+
> [Upgrading from Basic Load Balancer - Guidance](../../load-balancer/load-balancer-basic-upgrade-guidance.md)

‎articles/virtual-network/ip-services/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -98,6 +98,8 @@ items:
9898
href: configure-public-ip-bastion.md
9999
- name: Upgrade a public IP address
100100
items:
101+
- name: Upgrade guidance for Basic SKU public IP addresses
102+
href: public-ip-basic-upgrade-guidance.md
101103
- name: Upgrade a public IP address - Portal
102104
href: public-ip-upgrade-portal.md
103105
- name: Upgrade a public IP address - PowerShell

0 commit comments

Comments
 (0)