Microsoft Exchange Reviews

Our company uses the solution as our server. We have 20 to 30 users who collaborate across the solution. We prefer the solution on our web servers for committee users. 

The email management system is very easy to set up, configure, and use. 

The integration and features are very good. 

Creating an email for one user on a different domain takes time. 

The setup is difficult so could be easier. 

Our version of the solution is legacy so is no longer supported. 

I have been using the solution for fifteen years. 

The solution is very stable but you need to keep updating it. 

The solution's old version is discontinued with no support. 

The setup is difficult because it requires specialists to create domains and activities. 

We implemented the solution in-house. It was difficult and might have taken a day or more. 

The solution is expensive to maintain because it requires frequent updates and ongoing server maintenance. 

The 365 email only costs around $8 per month, per user. 

For all 365 applications, the cost is $12 per month, per user. For comparison, Google Workplace costs $8 per month, per user for all applications. 

We are looking to other providers like Google Workspace because the solution is legacy and no longer supported. It is also very expensive to maintain. 

We are deciding if we should upgrade our server and version or move to a different server and product.  

The solution is a very, very stable product so I recommend its use if your budget can handle it. 

I rate the solution an eight out of ten. 

My deployment model for Microsoft Exchange in this moment is for a company that uses Exchange Server on-premise solution to support its infrastructure services.

Although we keep all user data in the cloud, we have some kind of hybrid solution. It's Exchange service; our installation of Microsoft Exchange service is on-premise to cloud solution from Microsoft. In this moment, we are using some hybrid solution, although that on-premise solution is mostly for supporting our company infrastructure.

The best features of Microsoft Exchange, which I have answered many times in my trainings, is that it was a very compact, still extensible environment for user communication. There was a very short moment when it included messaging and instant messaging services, similar to messenger. It was not the best, but what was the best point is that it was complex, but simple to use with a clean interface for users. This could be a very short expression of the feeling.

Areas of Microsoft Exchange that have room for improvement could use some deeper thinking. I believe there could be better communication between Exchange Online and that cloud-oriented service and this Exchange server; some more precise communication to accept it as a single point of communication.

Another point would be that I would appreciate as a lazy administrator if there were better performance and monitoring available directly to the users and to the server. I can do that, but I need to at least have some knowledge and improve the scripts and so on. I would appreciate better performance, monitoring, and availability monitoring of Microsoft Exchange available to admin.

I have more than 25 years of experience with Microsoft Exchange, as I have been working from the beginning of Exchange Server.

I would rate technical support from Microsoft Exchange as great because we also had some issues while upgrading the system and maintaining it. The response is not immediate, but we are not paying so much money. As a general customer, I was very satisfied. They were fast enough and very skilled to support our needs.

Positive

My initial setup of Microsoft Exchange was very easy, and I am still doing it frequently; it's very easy to set up the environment.

I'm not a reseller and I have a loose connection to Microsoft solutions. I was not only a user, it means I was administrator of the system, administering it, so I was not a real user; my users were clients of the server. I was indirectly, loosely connected to Microsoft because I was also Microsoft certified professional. I was evaluated as having knowledge and I was also teaching it, so I had better connection to the server information.

The protocols I most utilize with Microsoft Exchange for integration are historically linked because now there are not very many ways to use Exchange since it became a messaging service. Today's world internet is communicating through SMTP, so SMTP is most important. We can say that is the only one, but there are still some extensions for reaching this Exchange server. In this moment in a Microsoft environment, there are different protocols that are good such as EWS.

It's something more advanced or some improvement of HTTP, because HTTP communication is used to communicate to web pages. You can access Exchange mailbox in the same way, but it's not called HTTP; it's a little bit enhanced protocol called Exchange Web Services, EWS. There are still ways to connect to your mailboxes.

Data loss prevention in Microsoft Exchange is critical for me. We use only part of these services because in the past, Exchange Server served and maintained user mailboxes. Now, I'm hired for an organization that moved all user mailboxes to cloud. We are still using Microsoft environment, and it's still Exchange server, but it's not directly accessed; it's called Exchange Online.

Regarding security, we now only use security infrastructure of Microsoft Exchange. That's very important. We have protected communication to Exchange server, using HTTPS connections to communicate to Exchange server and SMTP. Although SMTP protocol was built to communicate between mail servers, and the first internet was based as a free communication without any protection, now we are more concerned about security. That's why we also use the security part of SMTP, TLS, and so on. We use it, and we evaluate it as good at least.

Regarding the price of Microsoft Exchange, I don't really know, because now I'm completely disconnected from this due to working for a big company. In the past, I remember Microsoft Exchange was not the cheapest solution, but as it was very complex, covering many features needed for common users, it was an acceptable price. The ratio of power and price was very good.

I rate Microsoft Exchange a nine out of ten.

I use Microsoft Exchange more for organizing tasks than as an email client. We have integrated Exchange with Teams for organization and communication.

The most used feature of Microsoft Exchange is the email capability, especially since it integrates with the calendar. We integrate Exchange with Teams, and the single sign-on feature is very helpful. I use Exchange to organize tasks with implemented rules, and its integration with Teams enhances our organizational abilities.

The filtering of spam needs significant improvement, as many spam emails are not getting detected. Exchange should provide higher security and better spam filtering.

I have been using Microsoft Exchange for more than ten years.

The solution has faced performance issues, especially lagging, in recent updates.

Scalability is not a major issue, as it's easy to scale up and provide Exchange access to new users.

I do not need to contact Microsoft directly as the IT department handles any support interactions for us.

Positive

The initial setup of Microsoft Exchange is straightforward. It requires simply having a user and password to initiate, and a lot of the process is automated.

Microsoft Exchange saves time by allowing users to send emails or set schedules instead of making calls or holding meetings.

I can recommend using Microsoft Exchange as it is a functional product, but users should be aware of cybersecurity issues and potential spam. It is important for users to be cautious when opening or forwarding emails. My total rating for Microsoft Exchange is eight out of ten.

I use the product to help customers build their infrastructure, support their existing operations, or troubleshoot their Exchange environment. 

My use cases span setting up on-premises solutions to configuring hybrid environments involving Office 365.

The platform has significantly streamlined communication and collaboration for my clients, offering reliable email and calendaring services. It also provides compliance features like email journaling, which is critical for legal and regulatory purposes.

The Database Availability Group (DAG) is the solution's most valuable feature. It ensures high availability and resilience, allowing seamless recovery from potential failures and making it a reliable option for business-critical operations.

The solution's hybrid deployment process could be improved, particularly for customers who initially started in the cloud and may want to return to an on-premises setup. Microsoft could make this transition more flexible.

I have been working with Microsoft Exchange since version 5.4.0, which has been approximately 27 or 28 years.

The product is stable when implemented by experienced professionals.

The platform scales well, especially with the use of hybrid cloud environments. However, to maintain performance at scale it may require careful management of resources and configurations.

Microsoft’s support for Exchange is adequate, but their shift away from partner-focused business models has caused delays in getting timely support. Their support team may not always have the depth of knowledge needed, particularly for complex on-premises or hybrid scenarios.

For someone with my level of experience, the setup is straightforward. However, for less experienced users, the complexity of configuring Exchange, especially in hybrid environments, can be challenging.

I handle the implementation in-house due to my extensive experience with Exchange. However, for those who have in-house expertise, engaging a vendor with specialized knowledge is crucial for a smooth setup.

The product pricing is reasonable if you utilize its full suite of features. However, it may feel expensive for users who only require basic email services.

Exchange was selected based on its advanced features, such as archiving, legal compliance, and multi-site support, which were not fully available in open-source alternatives.

I advise investing in proper training or expert support is essential for maximizing the product's potential.

Overall, I rate it a seven out of ten. 

The solution's most valuable feature is Outlook, as its users are comfortable using it.

There will be no next release of the tool because Microsoft already announced that Exchange will reach the end of the support phase after October 2025. The only option people will have is Microsoft Office 365 or Exchange Online. Microsoft Exchange will not be updated in the future. The last release of the tool was in 2019, and it had extended support. After October 2025, no matter what, Microsoft will not provide support or updates for the tool.

The tool is not easy to use. Every person has to have at least administration-level experience to use the tool. From an improvement perspective, the tool can be made easier to use.

I have been using Microsoft Exchange since 2003, so it has almost been twenty years. My company is a Microsoft partner and reseller.

The product is stable, but since Microsoft 10 will stop working after 2025, the majority of users are trying to move on to cloud services, like Office 365, which I think is easier for users to access. As it is a cloud tool, you have to click on the mailbox users and reset the password.

It is a very scalable solution. There are thousands of mailboxes being used by the customers, and all are happy with the tool.

It is a very easy product to use. I received support during the deployment phase. The tool is very easy, and we can find any resolutions we want on Microsoft's forums, so there has been no need to get support from Microsoft.

I don't have the technical skills of other tools. The majority of customers are using MDaemon and IBM Lotus Notes. Few customers migrated to Microsoft Office 365 and Microsoft Exchange.

My company helped our customers implement the tool, as we deployed the product as part of our after-sales services.

The solution is easy to deploy.

The solution deployment time depends upon the customer's environment, and it may sometimes take two or three days to a few months. If it's a fresh deployment, it hardly takes three to four days. If there is a migration or operation process involved, it will take four months to complete the migration process.

For migration, I have a team of five people for the post-development phase. I am also a Microsoft-certified trainer, who has been using Microsoft for thirty-five years.

The tool's setup phase was managed by the local partner or the one who supplies the tool.

I have not calculated the tool's return on investment for my customers because we don't teach the customers about Microsoft Exchange since they already know what Exchange is, and they don't ask for products from its competitors in Pakistan, so I am not talking about the whole world. In Pakistan, Microsoft Exchange is a well-known product among customers, and so they don't ask for an alternative. Customers just say that they want Microsoft Exchange because a majority of the banks, financial sectors, and multinationals use microservices.

Instead of using Microsoft Exchange, I recommend Microsoft Office 365 and Microsoft Exchange to others.

I recommend the tool to all companies, especially financial sectors and multinational companies.

In terms of the tool's security measures, the majority of things are covered already in a timely manner. Microsoft is using the security patches which offer the capability of securing Microsoft Exchange's environment.

I don't think Microsoft Exchange has AI.

I have not used the tool for any AI projects.

When dealing with most third-party products, customers have the tools they want in place. Customers mostly want to relay the emails on some services and not deal with the integration part. I have not integrated the tool with any third-party solutions.

My company has other solutions, and as far as the technical expertise is concerned, we can sell other tools. In the local market, we can find many technical people for Microsoft Exchange compared to other products. Our customer recommends we provide them with Microsoft Exchange so that they aren't stuck as far as the technical part is concerned. It is easier for Microsoft to find technical people than for other solutions.

I rate the tool a ten 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. 

We use the solution for email, calendar, and integration into Zoom.

The product works very well. Being able to access email outside the organization is a very good feature. It is very easy to set up.

The default storage capacity is too small. Though the mailbox size is one terabyte on the cloud, the default mailbox size can be increased for on-premise products.

I have been using the solution for ten years.

The tool is very stable. I rate the stability a ten out of ten.

The tool is very scalable. It is easy to add additional servers and users. I rate the scalability a nine out of ten. It is very difficult to migrate the server. If a primary Exchange server needs to be moved, it is not very easy. The service has to be shut down completely before it can be moved.

If there were a way to move it in real-time while email is still running, I would give it a ten. However, at the moment, we have to shut down the server and migrate or scale it to bigger capacity servers or the cloud. About 100 people in my organization are using the product. It is extensively used in my organization. As the organization grows, we will increase the usage.

I have used a webmail service that comes with Plesk for Linux servers.

The initial setup is moderately easy. It is neither easy nor difficult. It does require Active Directory to be set up properly. Setting it up is not difficult. It takes two days to set up an Exchange server.

We deployed the solution in-house. We need a manager, a systems engineer, and two developers to deploy the solution.

We have seen very good returns on investment. The solution is almost free. We just worry about Microsoft 365 licenses, and then Microsoft handles the deployment in the cloud. Once we set up the cloud domain, the cost is almost zero.

The licensing is integrated with Microsoft 365. Licensing is becoming easier. We can get Exchange in the cloud along with the Microsoft 365 license. We don't have to worry so much about Exchange licenses in the future. It would be deployed in the cloud.

The tool is very stable and easy to set up. However, we need Microsoft-certified engineers to manage it. Overall, I rate the solution a nine out of ten.

We use it to share information and collaborate with each other, even when we're working remotely. 

We exchange files and documents, and we also use it to store recordings and other information from meetings with our customers. 

There are some bad days or hard ways when it's tough to connect with people who don't have MS Teams products. But this is only a hard situation when we need to communicate with people outside MS Teams.

So the connectivity could be improved.

Another area of improvement is the sharing of files, the sharing part of Teams. How I can easily share information files or video files with the colleagues I'm working with? So, this is an area for valuable improvement.

Another area of improvement is support. It should be faster and more clear, and more human.

I have been using this solution for the last five years. We use the latest version.

I would rate the stability a seven out of ten. There are hard days. 

It is very easy to scale. Just add on licensing and keep working the same way.

There are around eight end users in our company. It's suitable for our current level. We're a small company, so it's quite okay.

I don't have the best impression of customer service and support. It should be faster and more clear, and more human. The support team deep dives into thousands of documentation pages, making problem-solving time-consuming without human interaction.

Neutral

The initial setup is very straightforward. It just took a minute. It is very easy. 

The deployment is a plug-and-play process. You simply need to access the administrator platform, set up the configurations easily, and share enrollment links with people. It's a very easy process.

The deployment was done in-house. However, you need an IT-oriented person, an IT manager with knowledge of Microsoft.

The license can be both monthly or yearly. It is not expensive.

It's a useful tool for remote work and communication. Start slow and educate yourself. Learn about the solution and give it a try.

Overall, I would rate the solution a nine out of ten. 

We primarily use the solution for email and passing on information between the company's user base.

The exchange functionalities are good. It helps ensure information is accessible and can move between people in the company. The exchange of email is very easy.

The integration is very good.

The Microsoft visuals are very helpful. 

We're able to work on SQL servers with no issues. 

I can't say there are any missing features. 

I'd like the archiving process to be faster. 

They could offer better performance and enhancements throughout the product. 

I've been using Microsoft for 15 years. 

The solution is stable and reliable. There are no bugs or glitches, and it doesn't crash or freeze. It is reliable. I'd rate the overall stability eight out of ten. 

It is a scalable product. A company would have no issues if it needed to expand. 

The solution is mainly used by all end-users. Everyone in the company has it. That's about 1,500 users.

I have never reached out to technical support.

I have never worked with other similar products. 

Others work on the deployment and configuration process. I did not take part in the implementation process. 

I have five colleagues that handle all aspects of Microsoft maintenance, including any needed maintenance for Exchange. One is an admin on Exchange. The others handle other Microsoft products.

I am using the latest version of the solution. 

I'm an end-user. As an end-user, the solution works well to the point I don't really know it's there. My company is a Microsoft customer. 

I'd rate the solution eight out of ten.

Exchange is an email solution. 

Exchange's best feature is single sign-on access using the Microsoft Identity framework. 

The security features could be improved. There should be a better policy management system. 

I have used Exchange for the last 12 years.

Exchange is 100% stable.

Exchange is 100% scalable. More than 100 of my customers use Microsoft Exchange, and some of the larger ones have more than 10,000 users.

We are a service provider, so we provide the first and second tiers of support. If we cannot solve the issue, we escalate to Microsoft premier support. My clients are happy with the Microsoft team. 

When I started using Microsoft Exchange, I found it to be complex. It's much easier now that I understand the architecture. Microsoft Exchange can be deployed on-premises, but it is also excellent as a cloud solution. 

The deployment time depends on the customer. A greenfield deployment typically takes around two weeks. It might take one or two months if you need to migrate accounts and data. 

I rate Microsoft Exchange 10 out of 10. I always recommended customers go with the Microsoft email solution, either on-premises Exchange or Microsoft Office 365. You can also go for the hybrid. I suggest Microsoft 365 or Microsoft Exchange for their collaboration and communication solutions.

Speaker 2: