Microsoft Exchange Reviews

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:

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.

We are a consulting company. We deploy Microsoft Exchange. One of our clients has been working with a file drive endpoint with Microsoft Exchange and Microsoft 365 Exchange. We use the latest version, which is a hybrid platform with Microsoft 365. I also work with departments in the government that use the solution for email purposes.

The maximum number of users that I am working with is approximately 20,000 users at a time. 

We've been using Exchange as an email platform. Our clients require multi-country, multi-regional email collaboration with controlled mail flow. The most valuable feature is the capability of message tracking and the protection of user data.

I would like to see Microsoft Exchange improve its documentation. The legacy version of the solution had very accurate product documentation. Also, they had very good training courses. Recently, as Microsoft has been frequently adding new features, the documentation has not been as detailed. This means that we need to spend more time making use of our own experience to tackle some problems.

New users will need help from technical professionals. There are not many people in the market that have in-depth knowledge of the product. The documentation for Microsoft Exchange is scattered, poorly organized, and often incomplete.

Due to the lack of adequate documentation, users cannot determine the optimal way to operate the system and end up crashing the product. Unfortunately, many of them do not seek help as they are unwilling to pay Microsoft the high cost of professional services.

I have been working with Microsoft  Exchange for twenty-three years. 

Microsoft Exchange has been in the market for more than twenty-five years. It is a stable, mature product. Any concerns with stability usually have to do with the fact that the user is not using the product in the correct manner because Microsoft did not teach them how to operate the solution correctly.

As long as you have a good plan, Microsoft Exchange can scale very well. However, the solution does consume a lot of web resources if deployed on physical hardware or on VMware. For example, I have an organization that has 200 users and Microsoft has eaten up more than 100 gigabytes of memory.

If you use Microsoft Hyper-V, the scalability is good. 

It is not unusual that when you implement the solution and you need information, you can not find it, or it is not very detailed. You will then need to engage with the Microsoft support team. You will need to spend a lot of time making use of your own experience to tackle some problems.

Microsoft charges very expensive professional fees for support services. Unfortunately, the quality of support is very low. They are not grooming sufficient people to support the end-users.

Positive

The initial setup of Microsoft Exchange is not complicated. However, if you need to set it up to work in harmony with any other program, you need a very in-depth understanding of the platform. 

Licensing costs for Microsoft Exchange have increased, but are still fair. For some users, the cost is high considering the number of functions and features they will use. 

The advice I would give to anyone considering this solution would be to use the latest online version. It is the only way to get quality support when you encounter any type of problem.

If you are not going to use all of the functions and features and only require primitive functions, this solution may be too expensive. When you consider the cost in terms of storage when you are leveraging the online version of Microsoft Exchange, it is quite a good investment.

When considering just the product itself, I would rate Microsoft Exchange a nine out of ten.

It is to run our mail server.

It's really just been the same for a decade now. I don't think they've really updated anything in a long time.

I like that we can still use it on-premise. Then, we don't have to pay the extra subscription fees for the cloud.

It integrates with anything really, to be honest, besides other Microsoft products.

There are AI-based features, but we don't use it.

We don't use Exchange for a lot of stuff, so there's not a lot to improve.

The interface could look a little more nicer, but other than that, it's fine. 

I have been using it for more than ten years. 

I haven't had to scale it at all. We've been running about the same amount of people for a long time.

It is used by around 100 end users. Just one person is required to maintain it for a hundred users, so we outsource that to an MSP.

They're helpful and easy to deal with.

We bought it years ago.  

I would recommend Microsoft Exchange to others because it's pretty easy to manage. However, it is costly, so it depends on how much you want to pay.

Overall, I would rate it a nine out of ten.

We mainly use the solution for our company email communications.

The platform is easy to use as it is integrated with Microsoft. We can easily share work files with other employees. 

We are not able to use Microsoft Teams due to connection issues. Thus, the product integration with Teams could be improved.

We have been using Microsoft Exchange for about seven months.

The product is stable. 

We have 73 Microsoft Exchange users in our organization. It is scalable. 

We contacted the technical support team for the migration. They responded immediately to our concerns and were knowledgeable.

We used Google Workspace before migrating to Exchange. We switched to Exchange as it was already integrated with Microsoft Office and didn't require paying for a separate license.

The setup was not very complex. It took about one to two weeks to migrate all our end-user accounts.

The platform's calendar-sharing capability is useful. It integrates well with other tools. 

I recommend it to others. It has many security features and is integrated with Microsoft Office, making it cost-effective. I rate it a nine out of ten.

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.

We use the solution in our company for emails, calendars, requests, and tasks.

The exchange of emails is its most valuable feature.

I'm a user for the time being. I'm not an administrator who is managing the server. I was an administrator fifteen years ago. But today, I'm just a simple user using the solution for emails.

We had an antivirus like Sophos to secure our network. In terms of Microsoft Exchange, I think maybe what can be done is to make it more user-friendly. Also, Microsoft should make it more like a web version.

I have been using Microsoft Exchange for a very long time. Currently, we are on the cloud version.

It is a very stable tool.

It is a very scalable tool. In my last company, the solution had more than five thousand users. Now, thirty users use the solution. Considering the upcoming year, there are no plans to increase its usage.

I am not seeking any help from technical support because we speak with our own technical staff.

As a user, we don't get involved in the setup process. We need to connect it using the email address. It takes a minute to deploy it. I can do the deployment by myself.

Since my company is on Microsoft Cloud, we pay for the licenses per user. Compared to volume licensing, I would say the present licensing cost is not expensive.

I recommend others planning to use the solution to use it. I rate the overall solution a ten out of ten.