In order to create an Azure Express Route connection I found myself running through the “Configure an ExpressRoute Connection” guide on Microsoft’s MSDN library.

Attempting to create a new dedicated circuit with a speed of ‘1024’ as the document suggests results in the following error:

New-AzureDedicatedCircuit -CircuitName “ExpressRoute” -ServiceProviderName “ProviderA” -Bandwidth “1024” -Location “Amsterdam”

New-AzureDedicatedCircuit : ResourceNotFound: The specified bandwidth 1024 does not exist for the provider ProviderA
At line:1 char:1
+ New-AzureDedicatedCircuit -CircuitName “ExpressRoute” -ServiceProviderName ” …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : CloseError: (:) [New-AzureDedicatedCircuit], CloudException
+ FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.ExpressRoute.NewAzureDedicatedCircuitCommand

It turns out you need to choose a bandwidth of 1000 rather than 1024. I’m not sure if you’re getting screwed out of 24mb/s here or whether this is purely cosmetic. I guess we will need to put it to the test when it’s all up and running!

The express route may be created without any linked VNets so this can be performed to get the ball rolling with your exchange provider even before you have decided upon an Azure architecture, IP addressing structure, or subnet layout. You will be given a service key which you can give to your provider.