Microsoft Exchange Reviews

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.

We primarily use the solution for e-mail. That's pretty much what Exchange is built for, and it's very good at what it's built for. 

If you want to have an email system that works quite well and that allows you to be able to give easy access to everything from emails to checking calendars, that's basically 365.

It is stable. 

It can scale. 

Technical support is largely helpful.

The only thing that could be improved is the pricing. They could make it more competitive. The price is a lot. That said, the product works, which means you're kind of caught between two realities. You want to pay for something that works. You just don't want to pay too much. If they could get it to be more affordable, then they will have a greater uptake in users. All the people that are using G Suite, the free version, would likely actually move over to 365.

I've been using the solution for over 15 years. 

This is a very stable product. There aren't bugs or glitches. It doesn't crash or freeze. It is reliable, and the performance is good.

I'm happy with the scalability. 

We have about ten people using the solution in our company; however, our customers that we support number in the thousands. 

If we do get additional people, we will increase usage. 

I've used Microsoft tech support quite a bit across various applications that they have available. Technical support is not bad. Once or twice you get a unique issue that's going to be difficult until you find someone that knows absolutely everything. However, for the most part, technical support is okay. It could be far worse.

The setups vary in level of difficulty. I've worked with both simple and complex setups. 

I'm not sure exactly how long it takes to deploy. The time would depend on the size of the implementation. 

I can handle the initial setup myself. 

The solution could be less expensive. 

We can do monthly payments if we like; however, usually, we do a yearly subscription. 

We've used on-premises and cloud deployments. In on-premises, we're likely one version behind. On the cloud, we are using the latest version.

I'd recommend the solution to others. Whenever, for example, I find someone using Google, I move them over to Exchange. 

I would rate the product eight out of ten. 

I just use it to retrieve my data. I'm just mostly leveraging it to retrieve some archive data, so I haven't really used it on a more advanced level.

For example, I was changing my email, so I wanted to retrieve some data I had from the previous address. That was the only time I used Microsoft Exchange to retrieve my archive information. Aside from that, I don't think I've used it for any other use cases.

I haven't really used it for something advanced. Most of my use cases are just to retrieve my information. Microsoft Exchange is just a part of your Office package, so you just have it inbuilt. I really haven't used it much.

The initial setup is easy.

I've not really gone through the application. The only time I use it is when I want to retrieve particular emails that I had.

I really have issues with updates. When an update wants to come, it should just come maybe once or twice rather than having us deal with constant updating. If I have a company constantly updating me on additional features and everything, I get to the point that I just don't read the emails or classify them as junk. However, if I get an update maybe twice, I pay more attention. They need less frequent updates and reminders. 

I've been using the solution for a year now. 

I can't speak to the stability as I haven't used it too much. 

I haven't tested the scalability. Most of my applications that I just use for my own work. 

While it's used in the company, I just use it for my own personal purposes, such as retrieving email. 

I've never reached out to support. 

When I was using Exchange, I didn't know how to initially use it when I wanted to use it to get to my data. To find out, I checked YouTube, and I got an idea of how to use it. It wasn't a problem for me.

I have not used any other similar solution previously. 

It's straightforward to set up. If you have your Office package, everything is straightforward.

I did not need the assistance of a consultant or integrator during setup.

This is a company product. I'm not in charge of licensing. I'm not sure what it would cost. 

I'm not sure if I could recommend the solution as I haven't taken a deep dive into its functionality. I haven't done any advanced work with it. I've only ever retrieved my own data. 

I'd rate it five out of ten. I was able to achieve what I needed to, however, I haven't used it much. 

I use the solution mainly for emails and arranging schedules, calendars, et cetera.

It is enterprise-friendly, and many organizations use it.

The product can scale.

It’s stable and reliable.

The solution could be more user-friendly. It could always be more scalable and have a better UI.

I’ve used the solution for many, many years.

The solution is stable and reliable. There are no bugs or glitches, and it doesn’t crash or freeze.

It is a scalable product. You can expand it.

I can’t say how many people in our organization use it.

We have our own internal support if we run into technical issues. I’ve never dealt with their technical support services.

We did not use a different solution previously.

I wasn’t a part of the installation. I can’t speak to how it goes.

Our IT handles the licensing process. I don’t have visibility into pricing.

We use an enterprise version.

I’d recommend the solution eight out of ten.

Microsoft Exchange is a user-friendly product that is easy to manage and configure. 

Some users encounter stability issues. I connect with the support team through my local partner, which takes time. 

I have been using the product for ten years. 

I rate the product's stability a seven out of ten. 

I rate Microsoft Exchange's scalability a nine out of ten. My company has around 4000 users. 

The tool's deployment is simple. 

I rate Microsoft Exchange's pricing a six out of ten. 

I rate the tool 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 Microsoft Exchange on a daily basis for our business. However, we are moving to Office 365, which means that this will be available on the cloud. This is also a part of the Microsoft enterprise agreement. We receive a lot of other support applications along with Exchange. For example, Teams is included and integrates seamlessly, and we can do many functions, such as schedule meetings.

We use Microsoft Exchange on a daily basis and it helping our business, we are able to integrate easily with many of our business applications.

Microsoft Exchange is a powerful solution. It can easily integrate with Active Directory and other business applications. It does not require any training, it is flexible and simple to use. When comparing Microsoft Exchange to other solutions, such as Lotus Note, it is more straightforward for business. 

From a reliability perspective, they need to improve the search engine, it is not very powerful.

The security is not the best, it is not able to filter some of the spam and malware emails that pass through no matter what security protocols that we have set. Recently we had two incidents where we had to stop the business for one day. I am not sure if it is a problem with our implementation, or is it a problem with something else. 

I have been using Microsoft Exchange for approximately four years.

There are some difficulties with the Microsoft Exchange application. For example, it sometimes gets frozen and we have not determined the cause. When frozen we need to close it, and then again open it again. It takes a while to reload the application if the volume is high and when I have many emails. They need to improve on stability.

Many solutions have bugs and glitches and I do not think Microsoft can help it, it is a huge package and there are updates frequently. However, if one was to implement all the standard policies the bugs would be fewer. If I do not implement a certain standard Microsoft Exchange policy, then it should stop me. It should not allow me to do certain operations that would put me at risk. There should be fewer manual controls to prevent improper configuration.

The solution is scalable. We have approximately 300 users using the solution and there are some companies that have 10,000 users.

The support for Microsoft is very good.

The installation process was straightforward. There were not that many difficulties.

We are currently using enterprise licenses for the solution. They are different pricing models available. There are individual, cloud-based, and enterprise licenses all with different pricing models. Typically, the larger the number of users, the lesser the price. For small to medium companies like us, we feel it is expensive. However, for a large company, where they have thousands of employees the cost is distributed. We do not receive this kind of benefit because of the small company size. They should provide more discounts for the small companies because we do not complain or create too many problems for Microsoft.

For large companies that have 10,000 employees, the problems are huge and different. They use a lot of Microsoft support. Small companies that have less than 300 people should get a discount, we do not qualify for their volume discount that starts at 500 people. They should not put these kinds of restrictions on giving discounts. I expect Microsoft to come up with some different options for small to mid companies in the future.

We have evaluated Microsoft Office 365.

Overall when taking into account implementation, user experience, the flexibility of the solution it has always been very good. There are more benefits than drawbacks.

I rate Microsoft Exchange a seven out of ten.

So I'm part of the team that does migration from the old version to the new version. I've done updates on all the versions up to 18.

On-premises Microsoft Exchange is good because it protects data privacy. It depends on the client because clients want to share their mailing communication with anyone, like vendors and all. So it's purchasing like on-premises server exchange email. So if they are okay with storing data to Online Exchange and all Office 365, they're buying that one. So it depends on the client's needs entirely. 

Microsoft could improve on Exchange's hybrid deployment or HCW. They need to improve on that because I was having many issues with HCW in our environment at times. And there are certain things I'm not clear about, like eDiscovery on our on-premises level. There were some features that I liked, such as Unified Messaging and Advance Search, but Microsoft removed them in 2019.

I've been working with Microsoft Exchange off and on for several years. It's not something I use daily. I work with it when I'm brought in to provide migration or implementation services. 

Microsoft Exchange's stability all depends on the environment. So when we are configuring and implementing, we're optimizing everything for performance. I've been working for 10 years in that field, so if anyone changes a configuration, we take into consideration the impact it will have on the stability. 

Microsoft Exchange is scalable, but it depends on the company and how much they're willing to pay. Scalability is only limited by the price.

When I'm migrating or implementing, and I have an issue, I check out a few things, like which applications are running. I also check the network security to discover all the basic stuff like server performance. Then, I suggest how many people are required to address these technical issues and at what level. I escalated to Microsoft two or three times. That was what the client needed, so we contacted Microsoft and got an LSA for that.

Installing and configuring Microsoft Exchange is a little bit complex. Initial installation takes around 45 minutes to 30 minutes. Then we have to do some configuration. The basic configuration takes one to two days, depending on the environment. When we are implementing in a hybrid environment, we need to make some manual adjustments. For example, there was an issue with creating multiple databases during one implementation, like active and passive copy. That was not transferring and working in that scenario. 

Often we're working with a company that has already deployed. That's where we need to understand our workflow and main flow. For example, say there is a company that already deployed version 10, and we need to upgrade to 16 or 19. So we would have to understand their needs, like if there is a hybrid configuration or some other existing requirement. 

There are different pricing tiers, and I don't remember all the costs for that. For Office 365, it depends on the license price per mailbox user. And for the on-premises version, there is a scale license. Overall, it's about average for the market. The on-premises license is a bit more costly because there is a requirement for OS-level licensing. And we offer a standard edition, so it is a little more straightforward to figure out the cost. We can also go for enterprise pricing. It depends on what the client needs.

I rate Microsoft Exchange eight out of 10.