Skip to content

Commit cfdedc7

Browse files
Merge pull request #239197 from brianlehr/newbranch
added routing pref internet prefix CLI instructions
2 parents 5074b68 + 33cde63 commit cfdedc7

File tree

3 files changed

+20
-7
lines changed

3 files changed

+20
-7
lines changed

articles/virtual-network/ip-services/create-public-ip-prefix-cli.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,20 @@ The removal of the **`--zone`** parameter is the default selection for standard
103103

104104
---
105105

106+
# [**Routing Preference Interent IPv4 prefix**](#tab/ipv4-routing-pref)
106107

108+
To create a IPv4 public IP prefix with routing preference Internet, enter **RoutingPreference=Internet** in the **`--ip-tags`** parameter.
109+
110+
```azurecli-interactive
111+
az network public-ip prefix create \
112+
--length 28 \
113+
--name myPublicIpPrefix-rpinternet \
114+
--resource-group QuickStartCreateIPPrefix-rg \
115+
--location eastus2 \
116+
--version IPv4
117+
--iptags 'RoutingPreference=Internet'
118+
```
119+
---
107120

108121
## IPv6
109122

articles/virtual-network/ip-services/create-public-ip-prefix-powershell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ The removal of the **`-Zone`** parameter is the default selection for standard p
111111

112112
# [**Routing Preference Internet IPv4 prefix**](#tab/ipv4-routing-pref)
113113

114-
To create a IPv4 public IP prefix, enter **IPv4** in the **`-IpAddressVersion`** parameter. Remove the **`-Zone`** parameter to create a non-zonal IP prefix.
114+
To create a IPv4 public IP prefix with routing preference Internet, create an **IpTag** with an **ipTagType** 'Routing Preference' and **Tag** 'Internet'.
115115

116116
```azurepowershell-interactive
117117
$tagproperty = @{

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -22,12 +22,12 @@ In this article, we'll discuss guidance for upgrading your Basic SKU public IPs
2222
We recommend the following approach to upgrade to Standard SKU public IP addresses.
2323

2424
1. Learn about some of the [key differences](#basic-sku-vs-standard-sku) between Basic SKU public IP and Standard SKU public IP.
25-
1. Identify the Basic SKU public IP to upgrade.
26-
1. Determine if you would need [Zone Redundancy](public-ip-addresses.md#availability-zone).
27-
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).
28-
1. If you do not need a zone redundant public IP address, use the [following upgrade options](#upgrade-using-portal-powershell-and-azure-cli).
29-
1. Create a migration plan for planned downtime.
30-
1. Depending on the resource associated with your Basic SKU public IP addresses, perform the upgrade based on the following table:
25+
2. Identify the Basic SKU public IP to upgrade.
26+
3. Determine if you would need [Zone Redundancy](public-ip-addresses.md#availability-zone).
27+
a. 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).
28+
b. If you do not need a zone redundant public IP address, use the [following upgrade options](#upgrade-using-portal-powershell-and-azure-cli).
29+
4. Create a migration plan for planned downtime.
30+
5. Depending on the resource associated with your Basic SKU public IP addresses, perform the upgrade based on the following table:
3131

3232
| Resource using Basic SKU public IP addresses | Decision path |
3333
| ------ | ------ |

0 commit comments

Comments
 (0)