What is most valuable?
The experience has been rather good. We've had nothing major happen to us. We've had no major downtimes. We haven't lost mail so far, which is good.
I enjoy not having to maintain the local infrastructure, local servers, local whatever. You use the software and don't have to worry about the details. You're not concerned with administration tasks other than managing users, which, of course, our team does on a daily basis, basically.
The pricing is okay.
The solution is stable.
The product scales well.
The user interface isn't too bad.
What needs improvement?
There were a few short outages where mail delivery was flaky.
I don't really like the response time of the web GUI for administration. All this seems a bit slow and not responsive enough. They should provide a far simpler solution for sending mail from machines as this is not really intuitive.
Due to the restrictions that Azure and Microsoft impose on sending mail, for example, if you have an Azure-deployed server that is sending out mails (for a shop system or something like that) it's not really simple. Also, it is not really scalable to use Office 365 as a relay server.
There's not really a useful backup tool that comes along with Exchange Online. You have lots and lots of storage for each user, yet you have to buy extra backup tools just to back it up with an Exchange on-premise. You could do this just with onboard tools, however, there's no such thing in cloud deployment.
For how long have I used the solution?
We completed the migration from Lotus Notes on-premise to Microsoft Office Online or Exchange Online last year.
What do I think about the stability of the solution?
The stability has been good. We haven't dealt with bugs or glitches. it's pretty reliable.
What do I think about the scalability of the solution?
I expect the product to scale well. That is what we are paying Microsoft quite a bit of money for. They have to address scalability, reliability, and things like that. We have the service-level agreement and it's their business to do it. That's what they get the money for.
We have about 3,500 physical users currently using Exchange. There are 1,500 more that are not interactive (for example, service accounts, group mailboxes, and accounts for machines that send mail and things like that). That makes the total number of users 3,500 persons and about 1,200-1,500 users that are not necessarily people.
How are customer service and support?
I haven't had any direct contact with technical support, however, I have not heard complaints as to their services.
Which solution did I use previously and why did I switch?
We used to have an on-premise deployment of Lotus Notes, however, we discontinued using this and swapped over to Microsoft Exchange Online with the help of an external consultant as there was a lot of mailbox migration to do. That was a quite lengthy process due to the fact that we had several terabytes of mail storage that had to be migrated.
How was the initial setup?
We had a partner help us migrate everything over.
The deployment times depend on a few factors. From the first start to the last migrated mailbox, for us, the deployment took over half a year. That said, actually, it wasn't that long, as we deployed in several waves taking one user group at a time and migrating them over.
Therefore, the real transfer time was much less than the seven months. In total, if you take the net time, it might have only been one month of actual migration. However, we made a point of migrating only on weekends to keep user satisfaction high and disturbance to daily business low.
What about the implementation team?
We had a partner assist us with the process.
What's my experience with pricing, setup cost, and licensing?
Pricing is good. However, it's also not exactly cheap.
It's my understanding that we have a contract that runs for two or three years with an enterprise agreement backing all this up. We do not buy on a yearly basis. That would be unusual for our company to buy for such short term.
What other advice do I have?
Since the project was finished, I'm no longer in an administrative role with Exchange Online. I have passed it on to other colleagues. The administration part is no longer in my hands, for which I'm quite grateful. I don't have to do the daily tasks anymore. My main job is to be the principal cloud architect for the company. I'm, to a lesser extent, concerned with daily administration tasks.
I'd recommend potential new users just go ahead and do it. It reduces the on-site administration chores by quite a bit. It's reliable enough to be used without second thoughts for business if you can handle the cost that comes with it, as Exchange or the whole Office 365 is not exactly cheap, especially when you count in the cost for security-related services that come with Office 365 if you pay for them.
I'd rate the solution at an eight out of ten. It works well, just not perfectly.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.