Microsoft Exchange Reviews

Microsoft Exchange is an email platform.

I am quite happy with this solution.

While this solution is cost-effective, in general, the price could be better. If it was the same product, and slightly cheaper, that would be amazing.

I have been working with Microsoft Exchange for 15 years.

Historically, this solution was on-premises, and now it is cloud-based.

We have no issues with the stability of Microsoft Exchange.

This is a highly scalable email platform.

We support 15,000 end-users for many different companies.

Support is very good.

The initial setup is straightforward.

Microsoft Exchange is a very well-priced solution.

Depending on their use case, they can purchase a variety of licenses.

I would definitely recommend this solution.

I would rate Microsoft Exchange a ten out of ten.

I believe I had used my previous version in 2010 or 2016. Subsequently, more people switched to Office 365, Exchange Online. 

Microsoft Exchange is exclusively an email solution and this is what we use it for. 

The performance is good.

The solution should be easier to deploy. 

I have used Microsoft Exchange for a couple of years. I'm now using Office 365, Exchange Online.

The solution is stable. 

The solution can scale up to whatever number of users one desires. This depends on one's infrastructure.

The solution is scalable. 

The technical support is fine. 

The deployment could be easier. 

I believe the installation lasted a couple of hours. However, further integration takes time and this can vary with the additional features one wants, customization which is based on the ETA, the rules and one's desire to make the solution visible to others. 

Once the solution is wholly deployed, there is not much need for further intervention. 

We pay for the license annually. We could take advantage of it throughout the course of the year, although it is now online, meaning subscription-based, by which the person can receive all the bookings, save for the mailing system. 

I'm currently using Office 365, Exchange Online.

The solution can scale up to whatever number of users one desires. This is wholly dependent on one's infrastructure.

We have approximately eight to ten thousand users making use of it in our organization. 

I would recommend the solution to others. People are gravitating towards it. 

I rate Microsoft Exchange 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. 

Microsoft Exchange can be used as an email service.

We would prefer to be able to manage the solution on the cloud.

I have been using Microsoft Exchange for approximately eight years.

I have found Microsoft Exchange to be stable.

Microsoft Exchange is scalable.

We have 600 users using this solution in our organization.

Microsoft has a very good support team.

We did the implementation ourselves.

I rate Microsoft Exchange a six out of ten.

All of Exchange's features are valuable. For example, we can configure the MAPI profile, IM profile, or mobile profile. 

Microsoft Exchange needs to improve how it handles and assigns policy and security.

I have been working with Exchange for the last 10 years.

The product is absolutely stable.

I think Exchange is somewhat scalable, but not exactly. For example, if we ever need to update our server, we have to create another server and migrate the mailboxes from one server to another. So, it's only somewhat scalable, not fully.

We are getting good technical support. We have an in-house support person, so we don't need any technical support most of the time. 

It's easy. Easy to use. Not complex.

It's reasonable. It's an affordable price.

I rate Microsoft Exchange nine out of 10. It's a good product that you can either implement on-premises or on the cloud. 

We use Microsoft Exchange mostly for corporate communication services—setting up an email box, calendar, setting appointments, etc. My organization is a very big organization. The user base is not less than 15 people. When I worked with Exchange at Starcomms on the corporate organization, we had more than 1,000. When I was at another company, we had a user base that is more than 60.

Exchange 2003 was a more closed environment, but they improved on it in 2010. The availability group settings are better, so it has inherent scalability. In 2010, they added several sensible rules.

They could continue to improve the consolidation and integration of mailbox services to make them more flexible, easier to deploy, and more manageable.

I've used it for a couple of years. I've used Exchange 2003, 2007, 2012, and 2015.

It's scalable.

When we've had issues that are beyond our ability to resolve, we've contacted Microsoft. Once we had a deep phishing outbreak that involved a lot of phishing emails, so I had to contact them and then work together to figure out how to stem that thing.

Setup is straightforward for administrators if you understand networking services and the need for an active directory service. Exchange is a site-aware service, so you must have a good grip on active directory services. You need a deeper understanding of the networking layer, internet services, and broadband before you can manage it on your own as a system administrator. These are services that an experienced administrator can handle.

I was able to do it all on my own. I have robust experience in hardware, installation and maintenance, operating systems, networking, routing and switching, security as well as database administration, and a little bit of user support too. I can also support the exchanges from the client side of it. 

In terms of deployment and maintenance, I do need a support engineer just to help with the labor. I also need maybe other system engineers as a backup. Then there's the technical team. Okay. In a corporate environment, you have people to deal with management influence, IT governance, and all the business cases underneath all that. Then you have the administrative level, including the security admin, a Windows admin for the Java site, then you have the Exchange admin. On the support level, you have user support.

When I was working in another company, it was Enterprise volume licensing.

Microsoft Exchange is the leader in corporate communication. It has been quite a good service. I rate it nine out of 10.

We primarily use the solution for emails and calendars and things like that.

It is a stable solution.

The solution is scalable.

For me, the solution is very user-friendly. I've used it a long time and I know where everything is. 

For me it's sufficient. I don't see much that can be improved.

I'm not sure if the security is enough. That said, for my purposes, it's fine. However, I am aware there are always new vulnerabilities and security threats to worry about.

For new users, it might take them some time to get used to the product.

I've used the solution for as long as I've worked with the company I'm at now. It's been a few years at this point. 

We have found the solution to be stable. There are no bugs or glitches. The performance is good. We don't worry about it crashing or freezing. 

The solution has been scalable so far. We have no problems expanding it.

In our company, we have several thousand people that use the solution.

I have never called technical support myself. Therefore, I cannot speak to how helpful or responsive they are. We have our own internal team that handles everything.

I was not personally involved in the installation process. I cannot speak to how easy or difficult the setup would have been.

I'm not sure how many support personnel we require for deployment and maintenance. 

I don't handle the licensing aspect of the solution. I cannot speak to any costs involved. 

I'm just a partner so not like I'm an administrator of IT.

It's my understanding that the solution we work with is a company installation and is not on the cloud, however, I'm not 100% sure.

I'm not sure which version of the solution we're on. I don't know the version number off-hand. 

I'd rate the solution at a nine out of ten overall. we've been very pleased with its capabilities. 

I would recommend the solution to other users and companies. 

I use it as a customer, and I also do implementations for my customers. I mostly go with hybrid deployments.

It gives me benefit in terms of integration with other services such as SharePoint, Microsoft Teams, and OneDrive. It makes my work much easier.

There are limitations in terms of the number of emails that can be sent in a minute, which makes it a little difficult for the marketing folks.

The products or the updates that come in are more frequent. If I want to move from Exchange on-prem to Exchange Online, there are prerequisites that need to be met. They always have prerequisites for the latest one, but not all customers will have the latest infra. They might have a six or three months old version, but the expectation is the latest one. This prerequisite is a little inconvenient for those customers who wish to migrate to the cloud.

The response time of their support can be improved. 

I have been using this solution for seven to eight years.

I have not contacted them recently. I used to contact them four or five years ago. I would rate them a four out of five. One point is for the delay in their response. 

It depends on the organization. If it is an SME, it is going to be straightforward. If it is an enterprise, it is going to be complex.

Its price is fair.

I will recommend others to go with the complete suite instead of going for just Exchange. If they go with Office 365, which is a bundled service, they will get more flexibility and collaborative workspace. It will enable their users to work without moving around the apps.

I would rate Microsoft Exchange an eight out of 10. Obviously, not everything is 100% satisfactory, but there are a lot of improvements happening. 

It's a very user-friendly application. The mail server is also valuable when compared to other services like SquirrelMail.

From a security point of view, Microsoft should enhance the new features. Technical support could also be better.

I have been working with Microsoft Exchange for about three or four years.

Exchange is a very good Microsoft product, and it's very stable. It's rare to face issues like mailboxes, but troubleshooting is very easy.

From a security point of view, Microsoft Edge's role is very good. This is because the Edge server is not part of an internal network. If there's a vector attack on Exchange, it will affect only the internal Exchange Edge server and not our private network or DMZ.

This product is reliable and very scalable. We have almost 5,000 users at the moment.

Technical support is average at best. Many times Microsoft engineers took a long time to support us after we logged a case. 

Microsoft Exchange is for any company with 400 to 500 people, but a mid-size company can also use this product. It's not very costly for them. The alternative many companies are using is Gmail desktop services with about 100 users. I don't know about the quantity, but many companies are using Gmail as a free service because they don't want to invest in other products like Microsoft Exchange or Microsoft Office 365.

On a scale from one to ten, I would give Microsoft Exchange a nine.

We use Microsoft Exchange Server for the users in our company.

We have found it to be a stable solution. It is scalable and easy to install.

I think it could be more scalable.

Microsoft Exchange is stable.

It is scalable. We currently have 2000 users.

It's easy to install and took about three to four hours.

We were able to install it ourselves. A team of three handled the installation and maintenance.

On a scale from one to ten, I would rate Microsoft Exchange at ten.

It is easy to install. A team of three people were able to handle the installation and maintenance.