Microsoft Exchange Reviews

We use the platform to facilitate email traffic, file transfer, security services, and rule policies.

Microsoft Exchange is a user-friendly product with efficient features for mail services and DNS registration.

The platform could be more user-friendly.

We have been using Microsoft Exchange for three years.

The service is stable. I rate the stability a nine out of ten.

We have 132 Microsoft Exchange users in our organization. It has a good scalability.

The technical support services are good. The team answers the tickets immediately.

The product is easy to install and deploy. The development steps included creating DNS records, followed by synchronizing with the Active Directory and facilitating user logins.

We implemented the platform with the help of our in-house team.

Microsoft Exchange is an inexpensive application.

The product, Microsoft Exchange, has significantly impacted our team's collaboration by utilizing hybrid directory functionality. We can integrate it with Teams, Calendar, and SharePoint providing simultaneous access for the users. It has effective calendar functionality improving scheduling efficiency. It offers various security-level templates, allowing administrators to tailor security policies based on specific organizational needs.

It is a stable service. It has a knowledgeable technical support team as well. I rate it a nine out of ten.

At the moment, our primary use case is mostly for mailing, but in the near future we will be more focused on collaboration, as well.

There is nothing special that I like with Exchange. They made a system that works in business. It is quite normal that companies use Exchange.

In terms of what should be improved, they should probably move to a cloud option like Office 365. We would like to get this functionality without the need to deploy complex hardware and software solutions. This should be the next thing, making Exchange more related to Office products, which are more cloud-oriented, less on-premise or desktop-oriented solutions, like the direction Google is strongly moving towards.

I have been using Microsoft Exchange for about five years.

In terms of stability, if you are a user or if you have a number of users, especially a big number of users, there will occasionally be some bugs in the product. That is a normal situation.

In terms of current users, I think we have about 3,000 or 4,000.

They are not dedicated solely to the Exchange. They are also supporting other software technology solutions.

My experience with tech support is that they are mostly good enough.

The initial setup is quite a straightforward process. I don't think it is a very complicated solution. Plenty of things could be more complex, but the ordinary, general settings are quite simple.

My personal preference would be a Google solution. It is not a big difference. My advice to anyone considering Microsoft Exchange would be, stay with your product because switching to another product can be costly and a complicated task.

On a scale from 1 to 10, I would rate Microsoft Exchange a 6.

It may be that some nice features are missing.

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.

Microsoft Exchange can be deployed on-premise and in the cloud.

We are using Microsoft Exchange for general sending and receiving emails in the office to customers.

The most valuable feature of Microsoft Exchange is the email storage is on the cloud. We don't have to delete emails often.

Microsoft Exchange could improve the archiving of emails and the performance.

I have been using Microsoft Exchange for approximately 10 years.

Microsoft Exchange is stable.

Everyone in the company is using Microsoft Exchange.

We have our own technical team for support of Microsoft Exchange.

We have been using Microsoft Exchange for a long time. Prior to this, we were using a solution called Thunderbird.

Our internal team does the maintenance of Microsoft Exchange, such as managing the group policy.

I recommend this solution to others.

I rate Microsoft Exchange a ten out of ten.

Exchange is an email solution. It is widely used in our organization.

Exchange is a robust system that is well suited for an enterprise environment. It's always up, and we hardly face any technical issues. Exchange has a web interface and integrates perfectly with Microsoft Outlook. This web interface can be easily used to change the passwords from the domain controllers. 

Microsoft needs to make some modifications to meet the current needs of the environment. For example, they need to add more cell service features because people work from home during the pandemic, and certain elements should be available as a mobile service.

I've been using Exchange for many years now. 

Microsoft Exchange is highly stable.

You can scale it horizontally by adding several servers behind the load balancer if you want. We have more than 20,000 users.

We contacted Microsoft about an issue a while back, but it was so long ago, I can't remember what the problem was.

Installing Microsoft Exchange is straightforward. The conversion takes time, but the installation itself takes less than two hours. The total deployment time depends on what you want to do, i.e., how many servers you want to configure, the structure of your domain controllers, etc. We have four team members for deployment and maintenance. 

We have an enterprise agreement with a five-year contract.

I rate Microsoft Exchange eight out of 10. Exchange has a cloud solution also, so depending on the count of users, you can decide whether to use the on-premise or cloud version.

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. 

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.