Skip to content

Commit 565c984

Browse files
committed
remove downgrade limitation
1 parent ed0d1f5 commit 565c984

File tree

4 files changed

+6
-10
lines changed

4 files changed

+6
-10
lines changed

articles/expressroute/expressroute-howto-circuit-arm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ New-AzExpressRouteCircuit -Name "ExpressRouteARMCircuit" -ResourceGroupName "Exp
5858

5959
Make sure that you specify the correct SKU tier and SKU family:
6060

61-
* SKU tier determines whether an ExpressRoute circuit is [Local](expressroute-faqs.md#expressroute-local), Standard, or [Premium](expressroute-faqs.md#expressroute-premium). You can specify *Local*, *Standard, or *Premium*. You can't change the SKU from *Standard/Premium* to *Local*.
61+
* SKU tier determines whether an ExpressRoute circuit is [Local](expressroute-faqs.md#expressroute-local), Standard, or [Premium](expressroute-faqs.md#expressroute-premium). You can specify *Local*, *Standard, or *Premium*.
6262
* SKU family determines the billing type. You can specify *MeteredData* for a metered data plan and *UnlimitedData* for an unlimited data plan. You can change the billing type from *MeteredData* to *UnlimitedData*, but you can't change the type from *UnlimitedData* to *MeteredData*. A *Local* circuit is always *UnlimitedData*.
6363

6464
> [!IMPORTANT]
@@ -280,7 +280,7 @@ You can modify certain properties of an ExpressRoute circuit without impacting c
280280

281281
You can do the following tasks with no downtime:
282282

283-
* Enable or disable an ExpressRoute premium add-on for your ExpressRoute circuit. Changing the SKU from *Standard/Premium* to *Local* isn't supported.
283+
* Enable or disable an ExpressRoute premium add-on for your ExpressRoute circuit.
284284
* Increase the bandwidth of your ExpressRoute circuit provided there's capacity available on the port. Downgrading the bandwidth of a circuit isn't supported.
285285
* Change the metering plan from Metered Data to Unlimited Data. Changing the metering plan from Unlimited Data to Metered Data isn't supported.
286286
* You can enable and disable *Allow Classic Operations*.

articles/expressroute/expressroute-howto-circuit-portal-resource-manager.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -56,13 +56,12 @@ From a browser, navigate to the [Azure portal](https://portal.azure.com) and sig
5656
| Create new or import from classic | Select if you're creating a new circuit or if you're migrating a classic circuit to Azure Resource Manager. |
5757
| Provider | Select the internet service provider who you'll be requesting your service from. |
5858
| Peering Location | Select the physical location where you're peering with Microsoft. |
59-
| SKU | Select the SKU for the ExpressRoute circuit. You can specify **Local** to get the local SKU, **Standard** to get the standard SKU or **Premium** for the premium add-on. You can change between Standard and Premium but not to Local once created. |
59+
| SKU | Select the SKU for the ExpressRoute circuit. You can specify **Local** to get the local SKU, **Standard** to get the standard SKU or **Premium** for the premium add-on. You can change between Local, Standard and Premium. |
6060
| Billing model | Select the billing type for egress data charge. You can specify **Metered** for a metered data plan and **Unlimited** for an unlimited data plan. You can change the billing type from **Metered** to **Unlimited**. |
6161
| Allow classic operations | Enable this option to allow classic virtual networks to link to the circuit. |
6262

6363
> [!IMPORTANT]
6464
> * The Peering Location indicates the [physical location](expressroute-locations.md) where you are peering with Microsoft. This is **not** linked to "Location" property, which refers to the geography where the Azure Network Resource Provider is located. While they're not related, it is a good practice to choose a Network Resource Provider geographically close to the Peering Location of the circuit.
65-
> * You can't change the SKU from **Standard/Premium** to **Local**.
6665
> * You can't change the type from **Unlimited** to **Metered**.
6766
6867
1. Select **Review + create** and then select **Create** to deploy the ExpressRoute circuit.
@@ -135,9 +134,6 @@ You can do the following tasks with no downtime:
135134

136135
* Enable or disable an ExpressRoute Premium add-on for your ExpressRoute circuit.
137136

138-
> [!IMPORTANT]
139-
> Changing the SKU from **Standard/Premium** to **Local** is not supported.
140-
141137
* Increase the bandwidth of your ExpressRoute circuit, provided there's capacity available on the port.
142138

143139
> [!IMPORTANT]

articles/expressroute/expressroute-howto-circuit-resource-manager-template.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ To create an ExpressRoute Circuit by deploying a template:
6060
Write-Host "Press [ENTER] to continue ..."
6161
```
6262
63-
* **SKU tier** determines whether an ExpressRoute circuit is [Local](expressroute-faqs.md#expressroute-local), Standard, or [Premium](expressroute-faqs.md#expressroute-premium). You can specify *Local*, *Standard, or *Premium*. You cannot change the SKU from *Standard/Premium* to *Local*.
63+
* **SKU tier** determines whether an ExpressRoute circuit is [Local](expressroute-faqs.md#expressroute-local), Standard, or [Premium](expressroute-faqs.md#expressroute-premium). You can specify *Local*, *Standard, or *Premium*.
6464
* **SKU family** determines the billing type. You can specify *Metereddata* for a metered data plan and *Unlimiteddata* for an unlimited data plan. You can change the billing type from *Metereddata* to *Unlimiteddata*, but you can't change the type from *Unlimiteddata* to *Metereddata*. A *Local* circuit is *Unlimiteddata* only.
6565
* **Peering Location** is the physical location where you are peering with Microsoft.
6666

articles/expressroute/howto-circuit-cli.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ The following example shows how to create a 200-Mbps ExpressRoute circuit throug
129129

130130
Make sure that you specify the correct SKU tier and SKU family:
131131

132-
* SKU tier determines whether an ExpressRoute circuit is [Local](expressroute-faqs.md#expressroute-local), Standard, or [Premium](expressroute-faqs.md#expressroute-premium). You can specify *Local*, *Standard, or *Premium*. You can't change the SKU from *Standard/Premium* to *Local*.
132+
* SKU tier determines whether an ExpressRoute circuit is [Local](expressroute-faqs.md#expressroute-local), Standard, or [Premium](expressroute-faqs.md#expressroute-premium). You can specify *Local*, *Standard, or *Premium*.
133133
* SKU family determines the billing type. You can specify *MeteredData* for a metered data plan and *UnlimitedData* for an unlimited data plan. You can change the billing type from *MeteredData* to *UnlimitedData*, but you can't change the type from *UnlimitedData* to *MeteredData*. A *Local* circuit is *UnlimitedData* only.
134134

135135

@@ -267,7 +267,7 @@ Next, link a virtual network to your ExpressRoute circuit. Use the [Linking virt
267267

268268
You can modify certain properties of an ExpressRoute circuit without impacting connectivity. You can make the following changes with no downtime:
269269

270-
* You can enable or disable an ExpressRoute premium add-on for your ExpressRoute circuit. Changing the SKU from *Standard/Premium* to *Local* isn't supported.
270+
* You can enable or disable an ExpressRoute premium add-on for your ExpressRoute circuit.
271271
* You can increase the bandwidth of your ExpressRoute circuit provided there's capacity available on the port. However, downgrading the bandwidth of a circuit isn't supported.
272272
* You can change the metering plan from Metered Data to Unlimited Data. However, changing the metering plan from Unlimited Data to Metered Data isn't supported.
273273
* You can enable and disable *Allow Classic Operations*.

0 commit comments

Comments
 (0)