Microsoft Exchange Online Reviews

I like that Exchange Online is easy to use and that I do not need to maintain the previous Exchange Server. I also do not need to worry about the security of the Exchange Server. If there are any issues, then it will be the service provider's problem and not mine.

Microsoft needs to lower the price of the extra production add-ins for Exchange Online.

I just switched to Microsoft Exchange Online two months ago but have been using the on-premises version for a year.

It has been stable so far.

I believe that it is scalable. At present, we have three users.

It's very easy to set up. It can be done in one hour by one person. Also, one person can handle the maintenance as well.

I would rate this solution at nine on a scale from one to ten and would recommend it as well.

Our company provides software and hardware as well as Microsoft product training. I'm the company CEO. 

The solution is good for numerous deployments and helpful for many users. 

Despite being a Microsoft-certified trainer, I am lacking some information. I don't know what each product does and how it is linked to other products. I'd like to see more updated documentation which is currently lacking. I'd like to see a smoother connection between Microsoft products and integration with other companies into the Exchange environment, particularly those that fill gaps in Microsoft. It's difficult to know where to get information for testing, tuning, and so on. I'd like some centralized way of logging. 

I've been using this solution for about 11 years. 

The product is stable and provides good performance. 

I believe that the solution is not cheap but that it's a good investment. It's affordable but they've made licensing into a complex issue and it's difficult to try and follow all the changes. 

I recommend this product and rate it nine out of 10. 

Microsoft Exchange Online is used for all the emails and the software is used by all employees to send emails to others and to corroborate with other people over the email.

The most valuable feature of Microsoft Exchange Online is its performance.

There is an annual enterprise subscription could improve by having more features.

I have been using Microsoft Exchange Online for approximately 10 years.

Microsoft Exchange Online is stable.

I have found Microsoft Exchange Online to be scalable.

Microsoft Exchange Online support can be optimized further. They should put some more efficient technical engineers to support end customers.

I previously used Microsoft Exchange on-premise, and we switched because we wanted to use the cloud.

The initial setup of Microsoft Exchange Online is straightforward.

There is an annual enterprise subscription to use Microsoft Exchange Online. The price is reasonable.

I would recommend this solution to others.

I rate Microsoft Exchange Online a nine out of ten.

The most valuable feature is brand use.

Some of our clients such as banks are always concerned about storing their data in the cloud. Cloud security is always a concern and the solution can always increase their security.

I have been using the solution for six years.

The solution is stable.

The solution is scalable.

The technical support is always good.

The initial setup is straightforward and easy to configure.

We implement the solution for our clients.

I give the solution nine out of ten.

For our clients that have security concerns regarding storing their information in the cloud, I always recommend Microsoft Exchange On-Prem products.

Depending upon each project, we can have thousands of people working on this solution.

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.

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.

We completed the migration from Lotus Notes on-premise to Microsoft Office Online or Exchange Online last year.

The stability has been good. We haven't dealt with bugs or glitches. it's pretty reliable. 

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.

I haven't had any direct contact with technical support, however, I have not heard complaints as to their services.

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.

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.

We had a partner assist us with the process.

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.

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.

We use SharePoint Online for the collaboration of our team and for other desktop applications we are using in-house.

We also create technical presentations, so most of the time we are dealing with MS Word and Excel. Sometimes, we also use Visio for diagramming. Our overall experience is good.

They should tighten their cloud security. If you are using Microsoft Office 365, the responsibility of backup is not on the part of Microsoft. It is on the part of the customer. Microsoft Office should give some kind of built-in solution with the Office 365 subscription regarding the backup of their online mailboxes.

My company has been a Microsoft Gold partner for the last 12 years. As soon as we became a Gold partner, we started to use Office 365.

It's stable.

We can have different plans. If we are scaling, then obviously we can go for the enterprise plan and add an unlimited number of users to our Office 365 plan.

Overall, technical support is very good. My colleagues reached out to Microsoft technical support many times for queries. They are very responsive.

Setup was really simple. We migrated our customers from a different platform to Microsoft Office 365. There is a separate technical team. I designed the solution only.

They have raised their prices, and obviously, it hits our customers. Some of them are deciding to step back from Office 365. For customers who have bought the annual subscription, they are moving to the monthly subscription.

I would rate this solution 8 out of 10.

I would recommend Office 365. It's a global product, and overall they have a larger footprint in the world. We're a Microsoft Gold partner, so as soon as the customer moves to Office 365, obviously our business will also grow.

The primary use case of the solution is mainly used for our email conversation, specifically for minutes of meeting or to propose a solution.

The most valuable features of the solution are the security of the email flow, the primary security, having a dedicated, consultative space where if I send an email from a billing app or from a browser or anywhere, it gets stored in consultative space, and some of the end users features such as Word solution.

Technical support can be improved by shortening the response time and increasing their knowledge. The solution can improve the integration with mobile applications.

I have been using the solution for over ten years.

The solution is stable.

The solution is scalable.

The technical support is completely based on how we connect with the support team. I would say they just follow the ticketing process. I do have mixed feelings because it's completely based on the engineer allocated to my ticket. Depending on who you get some are more knowledgeable than others.

Neutral

• Technical support can be improved by shortening the response time and increasing their knowledge.

The initial setup is straightforward and is definitely easy. Anyone with basic IT knowledge should be able to do it.

I would say the solution is reasonable and affordable. Compared to the competitors, I would say it gives you a lot more functionality and is easy to integrate with other applications and tools. I give the solution ten out of ten for pricing.

I give the solution nine out of ten.

We currently have between six and seven thousand daily users.

The solution 

The solution doesn't require any maintenance. The solution is a cloud platform and everything is taken care of by Microsoft, so there is no maintenance required. It's maintenance-free.

I recommend the solution. As soon as you know what your needs are, you can go ahead with Microsoft Exchange Online. You don't need any demonstration of features, and you don't need to do any POCs.

I think the solution is pretty reasonable in what it does. In terms of mobile applications, that is Microsoft Outlook for Android and iOS integration, which can make some integration to Microsoft Teams application, which is already prospected in the desktop application. If they can have it in mobile application also, that would be good. But as a solution, I couldn't think of any new features that are required presently.

Our primary use case for this solution is as a messaging solution for our company.We use it both for internal and external messaging services.

There are two aspects to the improvement of our organization. First, is the data reliability, the ability for an administrator to provide data which has been in the user's mailbox. For example, if someone lost the email because of inadvertently deleting the emails, or anything, any object inside the inbox, whether it's a contact or a folder or an email. The admin can actually go and restore that information quite easily, rather than any other solution. 

Second, the mobility of the solution helps solve issues with information access across varied platforms. This has helped us if there are issues concerning emails that must be recovered due to legal issues, and the like.

It would be nice for SharePoint to integrate with other social media platforms like Twitter, WhatsApp and Facebook. If all of these channels could perform together, that would be great.

In addition, there should be a feature of informing a user if the video, or large file someone would like to attach is too big a file. Instead of bouncing back to the writer, it should warn the user with a message that they cannot send a file over 30, 40 or 50 MB. It could be more engaging with the user, and this will make the platform more user-friendly.

The stability has increased exponentially since 2010. It is currently not an issue. There are fewer and fewer issues regarding how the backend handles data. The reliability factor is high.

I have not encountered issues with scalability of the solution.

I have had limited interraction with tech support. Whatever experience I had was OK. I have occasionally opened cases with them. 

It is straightforward, and not complex. If you have your IT director implement it, it has to be planned because users are using it and do not have a habit of cleaning up their mail boxes.

Initially, we had issues with the licensing agreement, but we worked it out with Microsoft.