Skip to content

Commit 540adac

Browse files
authored
Update data-charges.md
1 parent dfffeae commit 540adac

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/azure-vmware/includes/data-charges.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,18 +10,18 @@ ms.author: rvandenbedem
1010

1111
<!-- Used in faq.yml -->
1212

13-
Traffic in the Azure VMware Solution ExpressRoute circuit doesn't have metering. No billing for any Azure VMware Solution ExpressRoute circuit, or for Global Reach charges between Azure VMware Solution private clouds. This includes Azure VMware Solution to on-premises, other than standard egress charges for traffic from your Azure ExpressRoute circuit connection to your on-premises site from Azure. Charged according to Azure ExpressRoute pricing plans with the Metered Billing Model. If you are using the Azure ExpressRoute Unlimited Billing Model, you will not pay any egress traffic charges.
13+
Traffic in the Azure VMware Solution ExpressRoute circuit is not metered. No billing for any Azure VMware Solution ExpressRoute circuit, or for Global Reach charges between Azure VMware Solution private clouds. This includes Azure VMware Solution to on-premises, other than standard egress charges for traffic from your Azure ExpressRoute circuit connection to your on-premises site from Azure. These are charged according to Azure ExpressRoute pricing plans with the Metered Billing Model. If you are using the Azure ExpressRoute Unlimited Billing Model, egress traffic is not charged.
1414

1515
- **Azure VMware Solution to Azure Virtual Network** is through an internal ExpressRoute circuit and is free of cost, regardless of region location (same region or cross-region).
1616

1717
- **Azure VMware Solution to on-premises site** is done through Azure Virtual Network or ExpressRoute Global Reach (between the internal ExpressRoute and external ExpressRoute). It's still free aside from the standard egress charges (Metered Billing Model) from the ExpressRoute to on-premises network. For the Unlimited Billing Model, there are no data charges.
1818

1919
For example:
2020

21-
- If we connect an Azure Virtual Network in Azure West Europe to an Azure VMware Solution private cloud in West Europe, there will be no ExpressRoute charges other than the ExpressRoute gateway charges.
21+
- If we connect an Azure Virtual Network in Azure West Europe to an Azure VMware Solution private cloud in West Europe, there are no ExpressRoute charges other than the ExpressRoute gateway charges.
2222

23-
- If we connect a Azure Virtual Network in Azure North Europe to an Azure VMware Solution private cloud in West Europe, there will be no ExpressRoute charges other than the ExpressRoute gateway charges.
23+
- If we connect a Azure Virtual Network in Azure North Europe to an Azure VMware Solution private cloud in West Europe, there are no ExpressRoute charges other than the ExpressRoute gateway charges.
2424

25-
- If you connect an Azure VMware Solution private cloud in West Europe to an Azure VMware Solution private cloud in North Europe via Expressroute Global Reach you will NOT incur any ExpressRoute Global Reach data transfer (egress and ingress) charges. There will be charges when using an ExpressRoute gateway.
25+
- If you connect an Azure VMware Solution private cloud in West Europe to an Azure VMware Solution private cloud in North Europe via Expressroute Global Reach, there are no ExpressRoute Global Reach data transfer (egress and ingress) charges. There will be charges when using an ExpressRoute gateway.
2626

2727
:::image type="content" source="../media/data-transfer-charges.png" alt-text="Diagram showing Azure VMware Solution data transfer charges." border="true" lightbox="../media/data-transfer-charges.png":::

0 commit comments

Comments
 (0)