Azure Bandwidth Cost Consideration – Under the circumstances of sharing data between applications

Often, enterprises deploy applications in Hybrid mode. Or multiple applications are deployed in the cloud and in on-premises constantly talking to each other.

Who pays the bandwidth charge?

For example, mission critical SAP workload sits in Azure and the ancillary applications downloading data from SAP are sitting somewhere else (either on-premises or any other cloud but not in Azure (same region)). If that is the case, then the provider application which sends the data to the ancillary application will incur bandwidth charges. In Azure it is known as Egress.

The official documentation says,

Data transferred out of Azure data centers - Bandwidth refers to data moving in and out of Azure data centers, as well as data moving between Azure data centers; other transfers are explicitly covered by the Content Delivery Network, ExpressRoute pricing or Peering.

For more information on Azure Bandwidth pricing please visit https://azure.microsoft.com/en-in/pricing/details/bandwidth/

Take this example, when two clouds are involved.?

But when both the applications are sitting in Azure then the bandwidth is “no-charge.”

So, consider letting your consumer access the core system which supplies data out to be with the same region. Otherwise, the data source will have an inflated bill adding up to the cost of bandwidth.?