Outbound data transfer from Azure
Last updated April 09, 2019
Fastly has integrated a local circuit with Microsoft Azure ExpressRoute Direct. Once you’ve signed up for Fastly services and configured them correctly, outbound data transfers from the appropriate Azure regions to Fastly will use this local circuit when configured with Fastly shielding.
To configure your Azure origin to use this direct connectivity, choose
East US as the Azure service region and then be sure to choose
Ashburn (BWI) as the shielding location when configuring your Fastly service.
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.
WARNING: 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.