This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 65%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYQ%3C/text%3E%3C/svg%3E)
If my Azure instances use NAT gateway and then access the data in the data lake, will there be traffic charges for NAT gateway.
Hello @Yao, Qing ,
Apologies for the delay in response.
Virtual Network NAT simplifies outbound Internet connectivity for virtual networks. When configured on a subnet, all outbound connectivity uses the Virtual Network NAT's static public IP addresses. And it's billing starts when the resource is created.
Resource Hours - $0.045 per hour
Data Processed - $0.045 per GB
There is no charge for data transfer within a virtual network.
But any outbound traffic going via the NAT gateway will be charged as data processed.
Could you please provide more details on your setup for better clarity?
Regards,
Gita
Hello @Yao, Qing ,
Could you please provide an update on this post and more details on your setup for better clarity?
Regards,
Gita
Hello @Yao, Qing , do you have any further updates on this post?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 94%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
@Yao, Qing With the virtual network already free, you are getting charged for couple things with the NAT Gateway: the resources hours basically its UP time and the data processed (Ingress and egress).
Do you mean that after integrating NAT gateway into my instance, the NAT gateway will still incur traffic charges when I access data lake.
Is there any way to avoid the NAT Gateway Data Processing charge in this example? I think my instance and my storage are in the same region, and there should be no charge for intranet traffic.
If your instance traffic to your Data lake is not going through the NAT Gateway obviously you will not get charged for the data processed, but only for the UP time.
The data processing charges here are simple as this: No data processed by the NAT Gateway equals no charge.
It is not because they are on the same region that it is guaranteed that they are using the VNET to communicate unless you have something like Private endpoint set up.