Microsoft Exchange Reviews

I use this solution for my email and calendar. 

Because of this solution we have better integration with other Microsoft Office solutions. 

It's user-friendly. 

The solution needs a lot of resources to run efficiently. It would be nice if it used less resources to run on-premise.

I have been working with this solution for about five years. 

We have not had any problems with the stability of the solution. I would give it a nine out of ten. 

The solution is scalable. There are about 70 users working with it on a daily basis in our organization. 

Previously, we used Scalix. We switched to Microsoft Exchange for easier integration and better stability. 

It was a little bit complex to set up, so we had to get external help. 

A third-party did the deployment, and it took about two days. 

This is a time-saving solution. 

This solution is expensive. On a scale of one to ten, where one is the worst and ten is the best, I would rate it a four. 

Overall, I rate this solution as a seven out of ten. 

Microsoft Exchange is the main mail server of Microsoft. It's a popular mail server, so a common use case for Microsoft Exchange is for small, medium, and enterprise-scale businesses. It's a mail solution, voicemail solution, live calendar solution, etc.

What I love about Microsoft Exchange is the good integration since 2013, particularly its integration with the calendar and other software such as Zoom, TeamViewer, AnyDesk, etc.

After 2022, users of Microsoft Exchange have to migrate mailboxes to Microsoft Exchange Online, and what I'd like to improve is for Microsoft to publish more on-premise versions for customers using Microsoft Exchange. Having more security is another room for improvement in the solution, particularly for mailboxes that develop the Exchange Edge rule to protect internal mailboxes.

What I'd like to see from Microsoft Exchange in the future is for Microsoft to still update the latest, existing version which is 2022. I'd like Microsoft to still push more cumulative updates for Microsoft Exchange 2022.

I've been using Microsoft Exchange for two years.

I'm impressed with Microsoft Exchange, and I'm rating it five out of five, stability-wise.

Microsoft Exchange is a scalable solution.

Setting up Microsoft Exchange from 2016 to 2022 in an SMB environment is straightforward because Microsoft combined all the cache, hubs, and mailboxes into one server. For large enterprises, the initial setup for Microsoft Exchange isn't as straightforward because large enterprises require more sophisticated setups.

How long it takes to deploy Microsoft Exchange depends on the size of the environment. For example, if I'm going to implement the solution in a small or medium-sized customer environment, then the deployment would take approximately one to two days, but if I'm implementing Microsoft Exchange for a more complex environment that has a minimum of 10 mailboxes and multiple sites, the deployment alone can take up to one week.

My team is responsible for deploying Microsoft Exchange for customers, so the implementation is in-house. I lead the deployment team.

The ROI you get from Microsoft Exchange can be very, very broad in terms of values. The solution, particularly the on-premise version, can save you additional costs compared to deploying it on the cloud, but the downside is the maintenance cost, and during new releases or updates, you may want to schedule the downtime in advance.

I don't have enough information about the licensing costs of Microsoft Exchange, but I do know that you need two types of licenses to run it. You need the product key and the client access key to activate Microsoft Exchange. This means that apart from the standard Microsoft Exchange licensing fees, you have to pay additional costs.

I'm working in a professional service company that's implementing Microsoft Exchange on-premises for customers. I implemented the solution on-premises in 2016, 2019, and 2022. In 2016, I also performed a migration from Microsoft Exchange to Microsoft Exchange Online.

My current company has between fifty to one hundred users of Microsoft Exchange, but in terms of the number of clients my team has implemented the solution for on-premises, it's potentially five thousand.

Deploying Microsoft Exchange for SMB would require just two people, but deploying it for enterprise-scale businesses would require a minimum of three people. Maintaining Microsoft Exchange requires five to seven people for SMBs, and up to twelve in enterprise environments because maintaining the solution isn't as easy.

My advice to anyone looking into implementing or using Microsoft Exchange is the same advice I give to my team every day, which is to be more aware of new information found on the internet in terms of troubleshooting Microsoft Exchange problems. You should also keep on training about sophisticated setups for the solution because you deal with aggressive customers, so I encourage my team to learn about Microsoft Exchange designs, troubleshooting mechanisms, etc.

I'm rating Microsoft Exchange as nine out of ten.

My company is an implementer and consultant for Microsoft Exchange, not a reseller or retailer. The customer is responsible for purchasing the Microsoft Exchange license.

We use this product for emails and for meetings. I'm the IT coordinator. 

The biggest advantage of this product is that it provides us with unlimited storage for our mailbox. The availability and simplicity of getting emails is great. There's an accessible online version and you have the full Office package available at any moment beyond Outlook. The integration with OneDrive comes in very handy. The Outlook Exchange server becomes your go-to place for storing conversations and correspondence. 

The licensing could be better. There are several levels of licensing depending on the number of users and features but it lacks the breakdown of what's included in the license, and the possibility to customize what you really need. There are likely to be features included that you don't need but there's no opt out option for those.  

I've been using this solution for 10 years. 

Stability has improved tremendously. These days it requires an extraordinary set of circumstances to not be able to access your emails, to send or receive emails, or to access the Exchange server.

The solution is quite scalable. We have over 1,000 users. 

We've contacted technical support several times and they've been responsive. They're pretty good, in general. 

Positive

The initial setup is straightforward. There's really no problem with the setup of the latest Exchange servers and Exchange in general. We deployed in-house and didn't need any external partner to handle it.

Microsoft provides you with an ease of control, and management, and sets certain expectations from the software that you can't have if you implement other, cheaper solutions that are likely to be more difficult to manage or that are unable to adapt to new demands. It has a really nice scalable environment. You can start with the smallest Windows license and then just continue scaling up and upgrading, without the need to completely change and start over as your organization grows. The backbone is there on Microsoft. 

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

We are using Microsoft Exchange mainly for the email system for my company and other companies I work for.

One of the most valuable features of Microsoft Exchange is its security.

I have been using Microsoft Exchange for seven years.

Microsoft Exchange is highly stable. However, after receiving some updates it can be unstable. 

The scalability of Microsoft Exchange is good but it depends on the license.

We have approximately 4,000 users using the solution.

We had to contact support from Microsoft when there was a critical update that we needed to have which fixed some issues we were having.

I rate the support from Microsoft Exchange a five out of five.

The initial setup of Microsoft Exchange is complex. It contains a lot of components that have to be configured perfectly together. After the installation, it works well. It took us two weeks to migrate from one release to another.

I did the implementation of Microsoft Exchange in my company. We have a team of three people that do the maintenance and support for the solution.

Microsoft Exchange itself does not require a license, but users who will have mailboxes will require a license. It depends on the number of users to choose which license. If you exceed 2,000 mailboxes, it's preferable to get the enterprise license.

Many people when they upgrade their mailing system choose Microsoft Exchange.

I rate Microsoft Exchange a ten out of ten.

This solution handles all of our primary functionality including email, message delivery, message archiving and calendars.

The primary features I use are email and calendar.

In our current situation, the disappearance of sanctions would be a tangible improvement. We are basically cut off from technical support and it's very difficult to obtain any updates.

We have been using this solution for four years. 

This is a stable solution.

This is a scalable solution. We already have over 10,000 users in Microsoft Exchange and the total size of the databases exceeds several hundred terabytes.

In all large corporate installations, the first level of tech support is always the local support team. Only if they aren't able to handle the case, we contact tech support in Microsoft. For now, because of sanctions, this option is quite limited.

Neutral

We had used IBM Notes before but it is an inferior product compared to Exchange.

I barely had any issues with initial setup of Microsoft Exchange. It involves a few clicks on the initial setup dialogue and that's it.

This solution is used by many large organizations and I don't know of any viable alternatives. If there are a large amount of users in an organization, Exchange is probably the best option. If there are less than 1000 users, opensource software may be a better alternative.

I would rate this solution a nine out of ten. 

We primarily use the solution to send and receive emails.

In terms of usability, it’s pretty simple.

It’s stable.

The solution can scale well.

In terms of configuration, you definitely have to go way in depth. In terms of configuring the product, that's definitely an area in which they can make some improvements on.

The initial setup is complex.

Technical support could be more responsive.

From an on-premise standpoint, we’d like more security. I would definitely want to see some more security than Office 365 has to offer.

I’ve used the solution for a couple of years.

We’re able to do what we need to. In that sense, it’s stable and reliable. We haven’t had issues.

The solution is quite scalable.

We have about 150 people on the solution currently. Everyone is pretty much using it. Right now, we’re just sticking to the basics. I’m not sure if we have plans to increase usage.

Technical support could be improved. It takes you a while to get through to a technician, especially on the Microsoft side. They need to be more responsive.

Positive

I have utilized G Suite. The flexibility that Microsoft has to offer, especially when it comes to email, is better. Sometimes you need the ability to be able to make certain configurations and policy changes that Google might not offer.

The solution isn’t exactly straightforward. It’s pretty complex. The configuration can be difficult. It takes a while to set up, and you need to have some advanced knowledge in order to implement it correctly.

Based on who you have that is doing the deployment, it could take up to about three days or even maybe up to a week. However, in terms of a deployment plan, we need to analyze in terms of what we do internally and what outcomes we're actually seeking, and put the project plan in place with some timelines.

Internally, you might need one to two people to handle the initial setup. We had two engineers.

We had assistance from a third party.

I don’t have any details in terms of ROI.

I don’t have any information about how much the licensing is.

We didn’t really evaluate other options beyond Microsoft and Google.

I’m an end-user and a customer.

We may not be using the most updated version.

I’d advise potential users to ensure that you do your due diligence. If you're using a third-party contractor, just ensure that they're extremely qualified to actually execute the setup for you. Otherwise, you might run into problems.

I’d rate the solution an eight out of ten. It's stable. It works. Unless you probably go and mess with the configuration, then you won't have any problem. For the most part, it works. It does what it says it's going to do.

I use Microsoft Exchange for their email service for my personal use.

The price of Microsoft Exchange could improve, it is priced high.

I have been using Microsoft Exchange for approximately 10 years.

Microsoft Exchange is stable.

I have found Microsoft Exchange to be scalable.

I have not contacted Microsofts technical support.

The installation of Microsoft Exchange is easy.

Our technical team did the implementation of the solution.

There is an annual cost to use Microsoft Exchange, and the price could be less expensive.

I would recommend Microsoft Exchange to others.

I rate Microsoft Exchange an eight out of ten.

We are a consulting company. We deploy Microsoft Exchange. One of our clients has been working with a file drive endpoint with Microsoft Exchange and Microsoft 365 Exchange. We use the latest version, which is a hybrid platform with Microsoft 365. I also work with departments in the government that use the solution for email purposes.

The maximum number of users that I am working with is approximately 20,000 users at a time. 

We've been using Exchange as an email platform. Our clients require multi-country, multi-regional email collaboration with controlled mail flow. The most valuable feature is the capability of message tracking and the protection of user data.

I would like to see Microsoft Exchange improve its documentation. The legacy version of the solution had very accurate product documentation. Also, they had very good training courses. Recently, as Microsoft has been frequently adding new features, the documentation has not been as detailed. This means that we need to spend more time making use of our own experience to tackle some problems.

New users will need help from technical professionals. There are not many people in the market that have in-depth knowledge of the product. The documentation for Microsoft Exchange is scattered, poorly organized, and often incomplete.

Due to the lack of adequate documentation, users cannot determine the optimal way to operate the system and end up crashing the product. Unfortunately, many of them do not seek help as they are unwilling to pay Microsoft the high cost of professional services.

I have been working with Microsoft  Exchange for twenty-three years. 

Microsoft Exchange has been in the market for more than twenty-five years. It is a stable, mature product. Any concerns with stability usually have to do with the fact that the user is not using the product in the correct manner because Microsoft did not teach them how to operate the solution correctly.

As long as you have a good plan, Microsoft Exchange can scale very well. However, the solution does consume a lot of web resources if deployed on physical hardware or on VMware. For example, I have an organization that has 200 users and Microsoft has eaten up more than 100 gigabytes of memory.

If you use Microsoft Hyper-V, the scalability is good. 

It is not unusual that when you implement the solution and you need information, you can not find it, or it is not very detailed. You will then need to engage with the Microsoft support team. You will need to spend a lot of time making use of your own experience to tackle some problems.

Microsoft charges very expensive professional fees for support services. Unfortunately, the quality of support is very low. They are not grooming sufficient people to support the end-users.

Positive

The initial setup of Microsoft Exchange is not complicated. However, if you need to set it up to work in harmony with any other program, you need a very in-depth understanding of the platform. 

Licensing costs for Microsoft Exchange have increased, but are still fair. For some users, the cost is high considering the number of functions and features they will use. 

The advice I would give to anyone considering this solution would be to use the latest online version. It is the only way to get quality support when you encounter any type of problem.

If you are not going to use all of the functions and features and only require primitive functions, this solution may be too expensive. When you consider the cost in terms of storage when you are leveraging the online version of Microsoft Exchange, it is quite a good investment.

When considering just the product itself, I would rate Microsoft Exchange a nine out of ten.

Email is something we constantly use. 

Exchange is easy to use. It also has a built-in calendar for all the stuff I'm supposed to be looking at and doing. Exchange tells you if you have a doctor's appointment or a scheduled call. It also has a place to store and manage your contacts. If I want to add a new contact, it will put in information about that contact stored anywhere within the Microsoft Suite.

They keep making all these changes, and our system was down for four or five days. They finally got it up, but there are still lots of quirks. 

Exchange is about 90 percent stable, but they're working on it. In the next two or three weeks, they should be able to do it. I know what they're going through. 

Microsoft has teams in different countries, so they will help you depending on your problem. If you have an issue with something else, they will email you a link that puts you into contact with the team you should talk to. I gave them a lot of issues, and they're working on them. They're saying they will do everything they can to make it work.

The only issue is that the phone connection is sometimes bad because it's a foreign country. It's something you have to live with. You can repeat what they said and ask if you heard them correctly, but they're accommodating.

I rate Microsoft Exchange nine out of 10. My advice for prospective Exchange users is to have an experienced person deploy it and show you how it's done. They should give instructions on how to make it into a server. That's critical. If you set up a server and think that's the end of it, you could go down the wrong alley.

You'll want some help initially, but on the other hand, you definitely want to learn to use the solution yourself. I recommend getting a support contract with someone who knows the solution. There is so much specialization in this world. For example, a veterinarian and a cardiologist are both doctors, but would you see your vet about a heart problem?

We are using Microsoft Exchange for collaboration but mainly for email.

Microsoft Exchange could improve by being more secure. We are always looking to have more security.

I have been using Microsoft Exchange for approximately 20 years.

Microsoft Exchange is highly stable for the end-user systems. When we move to Office 365, it will be even more stable even. There's less administration required and it's very robust. We are really quite happy in using that.

The stability can depend on the user's internet speed. If the speed is good then the solution can be scalable.

We have approximately 3,000 to 4,000 users using this solution.

There are two to three people doing the maintenance of the Microsoft Exchange.

We have had an enterprise license agreement for three years. We are always seeking more value for our money, the price could be reduced.

I would recommend this solution to others.

I rate Microsoft Exchange an eight out of ten.