In the weekend I saw a few posts on StackOverflow asking how the network traffic is throttled in Azure, how much bandwidth a VM can use, etc. I am unable to find any information on this however but from monitoring with New Relic I can see that The A5 server network interface maxes out at 1.3MB/sec and we seem to max out on sending and receiving at 1000 packets/sec So if you are looking at Azure Site Recovery or any other disaster recovery replication solution, then you’re going to have to do some work to calculate your bandwidth requirements. There are some answers based on measurements or MSDN docs. In our development environment (in Azure) we are experiencing an issue which we are sure could be due to bandwidth limitations of the underlying VM. Everything seems to have gone fine but we found transmit speed is always 355 KB/s when try to copy files from office to different Azure VMs in different regions.

The Microsoft Azure global network is highly available, secure, and agile, and enables a wide range of enterprise and consumer services. What is the network speed between Azure regions connected with Virtual Network Peering? I hope this post may give a more complete picture from engineering perspective. How Does Bandwidth Throttling Work in Azure? This global backbone network supports business- and consumer-critical services, such as Azure, Skype, Office 365 and Microsoft Dynamics 365. June 29, 2018 July 5, 2018 daveberm ***Updated July 5th*** ... but suffice it to say there seems to be a reasonable amount of bandwidth available between Azure regions when using peered networks. I have a couple of Azure VMs and I believe that the network bandwidth is being throttled on them. Refer to some articles, I knew all connection to a virtual gateway will share 100Mbps bandwidth. 30 Apr 2016. One is a DS13 and the other is an A5. We're sure there is no bandwidth limitation configured in our local gateway equipment. Microsoft is radically simplifying cloud dev and ops in first-of-its-kind Azure Preview portal at portal.azure.com By scaling our App Service up a pricing level (from Basic to Standard), the issue stops occurring.