Microsoft Exchange Reviews

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. 

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.

I just use it for email.

The security and compliance features have impacted our organization. We use multifactor authentication with mobile authentication for the first use on any PC or device. We also have a feature that requires re-authentication if you haven't logged in for a certain amount of time.

It's very well integrated with OneDrive and Teams Calendar. We are using Microsoft 365, so the integration is very good.

Until now, I think integration with the Copilot AI would be good. 

I like its reliability. It's very stable, and it just works.

The events and meetings feature are the most beneficial for managing communications.

It is synchronized automatically with our organization's calendar, and everyone is aware of the event or meeting. We can meet in person or through Microsoft Teams.

More AI features would be good. For example, maybe AI could suggest sentences or enhancements to paragraphs while writing an email.

So, the CoPilot integrations could be further improved. 

I have been using it for about ten years now.

It is very stable.

It is scalable. Scalability is one of the powerful features of all Microsoft products.

There are about 700 users in our organization who use Exchange.

I used Mail Enable. The integration with the calendar. The other solution was a little bit hard.

The initial setup was straightforward. The setup us not complex than it needs to be. It works smoothly.

I work with the on-premises version of Exchange. It is deployed across multiple locations.

The deployment and maintenance part is covered by another team.

Overall, I would rate it an eight out of ten.

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. 

Our entire organization uses Microsoft Exchange. We are using Microsoft Exchange 2016. The solution is deployed on-premises.

This solution has improved the collaboration between our organization and our partners and contractors.

The most valuable features are that you can exchange information, tasks, attachments, and enhance the process in a short amount of time.

The security for the email technology could be improved.

For the next release, there are some features on the cloud-based Exchange that aren't included on-prem. It would be great if these features were made available in the next release. For instance, integration between Exchange and its on-prem calendar is not available for the on-prem solution.

I have been using this solution for more than 15 years.

I think Exchange is one of the most stable products from Microsoft.

The product is scalable.

Technical support is good. We're covered with the technical support maintenance agreement with Microsoft.

Most of the process is straightforward.

We used a consultant for deployment. We are working directly with Microsoft partnerships.

We renew the product license with Microsoft every three years.  The cost is included within a bundle of services. It's an enterprise agreement with Microsoft.

I would rate this solution 10 out of 10. It has enhanced the process of exchanging information between our organization and others.

I recommend this solution for others to use the auto implement. It's a good product. You can use this product through cloud, and it will be more valuable than on-prem deployment.

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.

I am a reseller of Microsoft products.

The primary use case of this solution is for email communication.

The pricing could be better, and it could have an easier implementation.

I have been selling Microsoft Exchange for approximately 12 years.

We sell various versions, it depends on the current market.

It's a stable product.

It's a scalable solution. There are approximately 100 people using this product.

90% of our customers are using it, whereas 10% are using other solutions.

We plan to continue selling this product.

Depending on the customer's requirements, it could be easy to install or it can be very complex.

If it's a new, fresh deployment, then it's very easy.

When migrating, we have to follow the restrictions of Microsoft and sometimes it can be really complex. It depends on customer scenarios.

We have a technical team who are certified with Microsoft, for deployment, migrations, maintenance, and support.

It's a little bit expensive.

Microsoft is now introducing a new pricing model which is subscription-based. Previously, it was a one-time purchase and you could use it until the product came to the end of life. Now it's subscription-based and you can use the subscription yearly. 

Customers can benefit from this new pricing model because it's expensive, and now with the subscription, they can budget for this.

This is a product that I can recommend to others.

I would rate Microsoft Exchange a nine out of ten.

We mainly use Microsoft Exchange for email communication between the users and the clients and for some other capabilities.

The most valuable feature of Microsoft Exchange is its communication capabilities. It also works really fine performance and stability-wise.

Microsoft Exchange's customer support could be faster and more knowledgeable. Also, the solution has some bugs.

I have been using Microsoft Exchange for three years.

I rate Microsoft Exchange a nine out of ten for stability. The stability of Microsoft Exchange could be better.

I rate Microsoft Exchange a ten out of ten for scalability. Approximately 2,000 users are using Microsoft Exchange in our company.

Sometimes our problems are not solved because Microsoft Exchange's customer support doesn't give the right answers.

We needed two people for the deployment and maintenance of Microsoft Exchange.

Users have to pay a yearly licensing cost for Microsoft Exchange. I rate Microsoft Exchange a four out of ten for pricing because it is quite cheap, and many companies use the solution.

Microsoft Exchange is a good and useful solution that users can use without any problem for smaller or larger companies.

Overall, I rate Microsoft Exchange a ten out of ten.