Microsoft Exchange Reviews

There can be occasional challenges during the product's implementation phase, making it an area where improvements are needed.

I have been using Microsoft Exchange for twenty years. I am an end user of the product.

Stability-wise, I rate the solution a nine out of ten. The product rarely has issues.

Scalability-wise, I rate the solution a ten out of ten.

The solution's technical support was very good. I rate the technical support a nine out of ten.

Positive

I have experience with Office 365 and SharePoint.

I rate the product's initial setup phase a five out of ten since it can be a challenging process.

Compared to the other options in the market, the licensing costs attached to Microsoft Exchange seem reasonable.

In my company, the product takes care of email communications as it handles all the emails and scheduling emails. Within the tool, the calendars are used extensively by our company and its customers.

The tool has improved the areas revolving around calendars and scheduling tasks since it has helped in the unification of everyone working in the company under the same system.

The most beneficial features of email management stem from the tool's ability to let its users combine the tasks and the calendar while also being able to organize emails.

The security and compliance features have impacted our organization, and it has been extremely helpful since such functionalities are needed for compliance purposes. For the customers and my company, being secure and having control of the handling of emails is extremely important.

The integration capabilities do not have a direct impact on the email portion of the product, but it does have the ability to set up meetings with the help of Microsoft Teams.

The mobile access feature provided by the product helps our company in the area of productivity.

I recommend the product to others who plan to use it. Based on the features and functionalities of the product, it would be beneficial to rule for any company where it is chosen.

The product offers good functionalities and reliability.

I rate the overall a nine out of ten.

The features I find most beneficial for my work are primarily centered around mail flow management. Mail flow rules, tracing, and the ability to set up rules and generate reports within the Mailflow section are particularly useful. Additionally, the convenience of connectors to other third-party systems and the ability to manage alert policies proves beneficial.

The product or service could be improved in terms of Microsoft Outlook client compatibility. The transition from old versions of Outlook clients to newer ones would enhance administration and maintenance processes, particularly switching to the web version.

We have been using Microsoft Exchange for four and a half years.

I rate the product's stability a nine.

We have 4500 Microsoft Exchange users in our organization. We plan to increase the number of users up to 5000. It is a scalable platform. I rate the scalability a ten out of ten.

We encountered significant challenges with response times and communication. In one instance, we had to escalate two tickets to the regional manager due to the lack of response from Microsoft engineers. It took two months to receive a resolution.

Neutral

The initial setup was straightforward and fast, taking only a few days. This swift migration to the cloud within days was particularly notable for a bank, demonstrating the efficiency and effectiveness of the deployment process.

We recently transitioned from on-premises Exchange servers to cloud Exchange, primarily for enhanced security and ease of management. In the past, we had shared mailboxes with multiple users who were accessing them simultaneously, posing security risks and management challenges. With the switch to cloud Exchange, we adopted shared mailboxes with individual user access, providing better security and accountability. This transition also streamlined our operations and reduced maintenance costs. While we still maintain a hybrid environment with Azure Active Directory, all our mailboxes are now on cloud Exchange.

It has indeed improved our email system. In the past, with on-premises Exchange servers, there was a higher risk associated with granting extensive access to Exchange admins, potentially exposing sensitive data. However, while transitioning to a cloud Exchange admin center may offer less flexibility for admins, it provides a more organized and structured approach. The preset scenarios and settings reduce the likelihood of incidents caused by manual admin actions, thereby lowering the personal impact on the overall system.

The calendar and scheduling functionality of Microsoft Exchange has been essential to my daily workflow. As a user and a manager, I rely heavily on the calendar feature to organize my tasks and appointments. I utilize color-coding for different types of events, set up repeated meetings efficiently, and sync my calendar with other planning tools seamlessly. Overall, it has had a very positive impact on my productivity and activity management. The flexibility and plethora of features, such as customizable settings for meetings and the ability to share calendars, add groups, and specify user permissions, make it an indispensable tool in my work routine.

Compared to other platforms like Google Workspace, it provides seamless connectivity between Teams, Outlook, Exchange, and other Microsoft products. Additionally, recent updates have improved connectivity between tools like Planner and Projects, allowing seamless task management across the platform.

I rate it an eight out of ten.

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. 

I use Microsoft Exchange as our mail server. Google is free, so I use it for my personal use, and for our office, we have the 365 option.

I use Exchange Server for email. That's why I am using Outlook for Exchange email. 

I do not have any notes for improvement.

I face some issues. No system is perfect, so I do face issues. They fix it and then get going.

With the cloud coming in, scalability is not an issue even for Microsoft. They probably will be able to scale up and scale down as and where it's required. Scalability probably is not proper.

I contact my technical support team, and they probably might be able to troubleshoot it on their own. If not, they'll take a ticket. I have a technical support team, the help desk, who will try to resolve it.

For my personal use, I am using Google Gmail, and I am okay with it.

Overall, I am satisfied with the product. I am used to it, and it's all good. From my experience, I would rate the product stability eight 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.

We wanted to centralize email to a specific server. We needed to manage the Exchange from one place and centralized everything. We chose Office 365 for all of our mailboxes, and the emails run through Exchange. With one click, we can access all of Microsoft's products.

Everything is good.

New features come in regularly.

It helps users communicate effectively with outside parties.

The whole Microsoft Team has created a great tool that has helped improve our capabilities and productivity. We use the solution daily.

Technical support is good.

We have witnessed an ROI.

The solution is stable.

It can scale well. 

The solution is serving the purposes we have. 

The cost could be cheaper. 

I've been using the solution for 13 or 14 years. 

The stability is fine. There have only been one or two incidents where Exchange did not work. However, for the most part, it is issue-free. There are no bugs or glitches. 

We currently have 12,000 mailboxes that leverage this solution. 

The solution is scalable. It is very easy to expand usage. 

We do not have plans to increase usage at this time. 

Technical support is fine. We haven't had issues with them. We've found them helpful. 

The initial setup of the solution is okay. It depends on the level of knowledge of the people setting it up. I found it easy since I have past experience. It needs to be implemented with people with past experience. It is easy to upgrade.

The time it takes to deploy depends on the number of mailboxes. 

We have a team that handles deployment and maintenance. We manage the solution for ourselves and sometimes for our clients. 

We are able to handle the implementation ourselves. I'm quite comfortable with the process and can do it myself. It does take a certain level of knowledge.

I have witnessed ROI while using the solution. It has good value for money. However, it depends on the use case. It's a journey for every organization. Each business might witness a different ROI across a different amount of time. 

The pricing model is a bit costly. They should work to lower the cost for the Indian market.

We pay for the solution yearly.

We're a Microsoft partner. 

We are using the latest version of the solution. I'm not sure which version number we are on. We migrated from on-premises to the cloud three or four years ago. 

We are a telecom service provider and have integrated Microsoft with a variety of products. It also integrates with mobile. It allows us to provide multiple services, including control and command centers. 

Technology is moving fast in this space, and there are more service providers out there. Many people are beginning to look at Google as an alternative. However, I've used Exchange for the last 14 years, and I am very familiar with it. Still, others are coming up fast, and more competition is on the horizon.

I'd rate the solution nine 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.

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.