removed scalable gw and ZR info

Author: MekaylaMoore

articles/expressroute/expressroute-about-virtual-network-gateways.md

@@ -83,83 +83,6 @@ The following table shows the features that each gateway type supports and the m
 
 [!INCLUDE [expressroute-gateway-preformance-include](../../includes/expressroute-gateway-performance-include.md)]
 
-### <a name="zrgw"></a>Zone-redundant gateway SKUs
-
-You can also deploy ExpressRoute gateways in Azure availability zones. Physically and logically separating the gateways into availability zones helps protect your on-premises network connectivity to Azure from zone-level failures.
-
-![Diagram that shows deployment of ExpressRoute gateways in Azure availability zones.](./media/expressroute-about-virtual-network-gateways/zone-redundant.png)
-
-Zone-redundant gateways use specific new gateway SKUs for ExpressRoute gateways:
-
-* ErGw1AZ
-* ErGw2AZ
-* ErGw3AZ
-* ErGwScale (preview)
-
-## ExpressRoute scalable gateway (preview)
-
-The ErGwScale virtual network gateway SKU enables you to achieve 40-Gbps connectivity to VMs and private endpoints in the virtual network.This SKU allows you to set a minimum and maximum scale unit for the virtual network gateway infrastructure, which autoscales based on the active bandwidth or flow count. You can also set a fixed scale unit to maintain a constant connectivity at a desired bandwidth value. ErGwScale will be zone-redundant by default in Azure Regions that support availability zones. 
-
-ErGwScale is available in most regions except the following regions:
-
-* Asia South East
-* Belgium Central
-* Chile Central
-* Europe North
-* Europe West
-* Germany West Central
-* India Central
-* India West
-* Israel North West
-* Japan East
-* Malaysia West
-* Qatar Central
-* Spain Central
-* Sweden Central
-* Switzerland North
-* Taiwan North West
-* UK South
-* US Central
-* US East 2
-* US North
-* US South
-* US South 2
-* US South East 3
-* US West
-* US West 2
-* Us West 3
-
-### Autoscaling vs. fixed scale unit
-
-The virtual network gateway infrastructure autoscales between the minimum and maximum scale unit that you configure, based on the bandwidth or flow count utilization. Scale operations might take up to 30 minutes to complete. If you want to achieve a fixed connectivity at a specific bandwidth value, you can configure a fixed scale unit by setting the minimum scale unit and the maximum scale unit to the same value.
-
-### Limitations
-
-* **Basic IP**: ErGwScale doesn't support the Basic IP SKU. You need to use a Standard IP SKU to configure ErGwScale.
-* **Minimum and maximum scale units**: You can configure the scale unit for ErGwScale between 1 and 40. The *minimum scale unit* can't be lower than 1 and the *maximum scale unit* can't be higher than 40.
-* **Migration scenarios**: You can't migrate from Standard/ErGw1Az or HighPerf/ErGw2Az/UltraPerf/ErGw3Az to ErGwScale in the preview.
-
-### Pricing
-
-ErGwScale is free of charge during the preview. For information about ExpressRoute pricing, see [Azure ExpressRoute pricing](https://azure.microsoft.com/pricing/details/expressroute/#pricing).
-
-### Supported performance per scale unit
-
-| Scale unit | Bandwidth (Gbps) | Packets per second | Connections per second | Maximum VM connections <sup>1</sup> | Maximum number of flows |
-|--|--|--|--|--|--|
-| 1-10 | 1 | 100,000 | 7,000 | 2,000 | 100,000 |
-| 11-40 | 1 | 200,000 | 7,000 | 1,000 | 100,000 |
-
-### Sample performance with scale unit
-
-| Scale unit | Bandwidth (Gbps) | Packets per second | Connections per second | Maximum VM connections <sup>1</sup> | Maximum number of flows |
-|--|--|--|--|--|--|
-| 10 | 10 | 1,000,000 | 70,000 | 20,000 | 1,000,000 |
-| 20 | 20 | 2,000,000 | 140,000 | 30,000 | 2,000,000 |
-| 40 | 40 | 8,000,000 | 280,000 | 50,000 | 4,000,000 |
-
-<sup>1</sup> Maximum VM connections scale differently beyond 10 scale units. The first 10 scale units provide capacity for 2,000 VMs per scale unit. Scale units 11 and above provide 1,000 more VM capacity per scale unit.
-
 ## Connectivity from VNet to VNet and from VNet to virtual WAN
 
 By default, VNet-to-VNet and VNet-to-virtual-WAN connectivity is disabled through an ExpressRoute circuit for all gateway SKUs. To enable this connectivity, you must configure the ExpressRoute virtual network gateway to allow this traffic. For more information, see guidance about [virtual network connectivity over ExpressRoute](virtual-network-connectivity-guidance.md). To enable this traffic, see [Enable VNet-to-VNet or VNet-to-virtual-WAN connectivity through ExpressRoute](expressroute-howto-add-gateway-portal-resource-manager.md#enable-or-disable-vnet-to-vnet-or-vnet-to-virtual-wan-traffic-through-expressroute).