At GSX we work with a lot of customers that have moved, are moving, or plan to move to Office 365.
We help them assess their Office 365 environment before, during and after the migration, as well as make them understand the end-user experience that they really deliver to their end-users.
In one of our “business stories” we mentioned how migrating to the cloud could directly impact the Outlook performance.In this graph, we compare the timetable between end-user actions performed on Exchange servers and their Office 365 tenant.
This example, done for a large bank in North America, shows that simply monitoring an “open mailbox” is not sufficient. Each action matters and has its own “user threshold”; when exceeded you will have to deal with an influx of complaints and open tickets.
Office 365 has been built to enforce capable security and high availability and we can say that it was a huge success.
The downside, of course, is that these two main concerns impact performance.
Even if the cloud provides a service a bit slower than former on-premises servers, it would be a mistake to believe that the cloud services themselves are responsible for the rise of end-user complaints.
After dozens of projects with our customers, we’ve realized that 9 times out of 10, end-user experience issues were related to the hybrid network and server components necessary to run a cloud service.
The main issue was that, before the deployment of GSX, there was nothing to measure end-user experience and correlate that with independent network and hybrid components metrics.
So, in order to provide data and feedback, we decided to run a few experiments in our distributed environment and share our findings with you.
We deployed a few GSX Robot Users at critical locations, to mimic customer activity, and started to measure the standard end-user experience; action per action as well as critical network metrics to have an idea on their impact on end-user experience.
We operated with two tenants: One in the USA and one in Europe.
We deployed Robot Users in the following locations:
► Three in Philadelphia (USA)
► One in Nice (France)
► One in Bangalore (India)
► One in Boston (USA)
► One in Microsoft Azure Cloud
On each of them, we ran the same tests but applied multiple configurations:
► With or without proxy
► With packet loss or not
► With a flapping router
► With or without ExpressRoute
► With connection to Office 365 through a headquarter or connection directly through the Internet
► With regional DNS resolution and out of the country DNS resolution
To know more about how a Robot User works please read this article >>
To know more about to interpret the data we display in PowerBI dashboards please read this article >>
To read more about Exchange Online performance, please follow this link>>
Those articles are organized by topics and describe the results of our findings. They provide you with important information that are here to be shared with the community.