Inter-zone bandwidth charges for VMs deployed without availability zone assignment

[jeffwmiles]

According to pricing details for bandwidth, July 1 2021 marks the date when data transfer between Availability Zones will begin.

According to Issue 39091, virtual machines created with no selected availability zone will be placed without control by an "allocator" service.

❓ Question: If VMs with no availability zone selected happen to be placed in different zones by this "allocator", will we see inter-zone charges when those VMs communicate with each other?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: cca70845-100f-2cfd-aba3-34b7fa4a5264
• Version Independent ID: 475b26e5-9e23-f769-3bd5-cbc4a678dbf0
• Content: Regions and Availability Zones in Azure
• Content Source: articles/availability-zones/az-overview.md
• Service: azure
• GitHub Login: @prsandhu
• Microsoft Alias: prsandhu

[MarileeTurscak-MSFT]

@jeffwmiles
Thanks for your feedback! We will investigate and update as appropriate.

[TravisCragg-MSFT]

@jeffwmiles I have reached out to get clarity on this and will update as soon as I can.

[TravisCragg-MSFT]

@jeffwmiles These charges only happen if both machines are in specified separate Availability Zones.

This charge will not occur on VMs that are not placed in an Availability Zone.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.