In the section "Option 1: Leveraging ExpressRoute", there is a statement mentioning there is no cost associated with the traffic going to/from the Spoke VNETs when leveraging ExpressRoute.
Here it is: "this traffic is specifically identified within Azure and does not trigger any VNET peering costs, so it is completely free to the customer.".
In the section "Option 1: Leveraging ExpressRoute", there is a statement mentioning there is no cost associated with the traffic going to/from the Spoke VNETs when leveraging ExpressRoute. Here it is: "this traffic is specifically identified within Azure and does not trigger any VNET peering costs, so it is completely free to the customer.".
Based on the article about vnet peering overview, it looks like it is not correct. It is explained that traffic to the gateway (ingress or egress) in the peered virtual network incurs virtual network peering charges on the spoke VNET (https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/virtual-network/virtual-network-peering-overview.md).
Could you therefore update this article accordingly?