Outbound data transfer from Azure
Last updated 2021-07-15
Fastly has integrated local circuits with Microsoft Azure ExpressRoute Direct and Microsoft Routing Preference Unmetered to create private connections to Azure. If using Azure as your origin, you can take advantage of the improved reliability, faster speeds, lower latencies, and higher security that this private local circuit offers over typical public internet connections. Additionally, Fastly will include your outbound data transfer costs from Azure in your standard Fastly pricing.
To configure your Fastly service to use direct connectivity via this local circuit, enable shielding using your Azure service region to determine the shielding location. Additionally, configure the routing preference for your storage account based on the service region and shielding location combination. Our developer documentation lists the available shielding locations for the routing preference you've chosen.
You can configure a routing preference after the storage account is created.
Once you configure your Fastly service and Azure storage account correctly, outbound data transfers from the appropriate Azure regions to Fastly will use this local circuit. Because Fastly has purchased this local circuit from Microsoft, Microsoft does not apply outbound data transfer rates to traffic traveling over it. Use of this local circuit should work with Azure services like Container Instances, Functions, and Media Services, as well as Blob Storage.
We encourage you to use Microsoft Azure's Billing Tools for monitoring traffic not on the ExpressRoute Direct Local. Despite this connection to Fastly’s services being in place, in certain circumstances your data may egress from Azure over the public internet rather than the ExpressRoute Direct connection. In such cases, your traffic to the public internet will be metered according to your commercial arrangement with Microsoft.