Participate in the management of a project where we migrated the datacenter to azuree and implemented the Azure expressroute for the quick and secure way to access the information in the cloud.
High transmission speeds available (50 Mbps, 100 Mbps, 200 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5 Gbps, 10 Gbps).
The implementation was quite simple and we had the support of the provider at all times to clarify the doubts we had.
High levels of service SLA.
Reduce the latency of transactions when searching for information or uploading to azure, example in the project we had a core application that sales executives consulted customer information and that application was uploaded and before using azure expressroute the latency for consulting the info was almost 10 seconds and with the implementation of azure expressroute we managed to lower it to 3 seconds, helping to avoid that specific problem that had generated a lot of noise.
It has a very high cost, but depending on the type of information in our case it was for core applications of the company turned out to be the best solution.
Services are limited for MS Azure & Office 365
If they have latency problems, or secure access to the information they have in azure, it is an expensive solution but it gives us the peace of mind to accelerate the times by improving the performance and security of the private connection to avoid losing data.
Have a private connection between the company and Azure that gives us speed and security of the connection and data.
The connections are redundant, which means that we have high availability.
Azure expressroute has a limit of simultaneous circuits (10 in total) more than enough, I take it as a non-extraordinary benefit since we can have several circuits with a single subscription and if it requires more than 10 I think you can ask the provider an extension.