Network charges can occur in different scenarios based on Azure resource placement as well as inter-component communication in the application. If you haven’t planned your Azure usage with these charges in mind, it could impact your monthly cloud bill significantly.There are no data transfer charges when resources that are deployed in the same VNET and availability zone communicate with each other. The same is the case when the resources communicate to an Azure public endpoint in the same region. However, the data transferred between resources in different availability zones is chargeable, even if they are deployed in the same VNET.
Not sure where is your client hosted is from Internet or expressroute?
As per Microsoft the following Availability Zone data transfer is charged:
Data transfer, ingress and egress, from a VNet resource deployed in an Availability Zone to another resource in different Availability Zone in the same VNET
Following Availability Zone data transfer is NOT charged:
- Data transfer between VNet resources located in same Availability Zone
- Data transfer between a VNet resource and a Public IP address in the same Azure Region
- Data transfer between VNet resources located in peered VNets across Availability Zones. This data transfer will be charges as per VNet peering rates.
If the traffic is flowing via the Microsoft network the below charges will apply and it doesnt matter whether it is a simple TLS Connection or a adhoc session .
Hope this helps.
Please Accept the answer if the information helped you. This will help us and others in the community as well.