Microsoft Exchange Online Reviews

The primary use case of the solution is for email and SharePoint.

We are beginning to explore Office 365 Online Exchange and Azure, which are part of Microsoft 365. We intend to create our Active Directory and Domain Controller on Azure and integrate OnTime Active Directory with Azure Active Directory.

I haven't encountered any downtime with Exchange Online so far. Last week, the entire Azure portal experienced an outage, which caused some disruption, but thankfully, we haven't had any issues with 365 yet.

The stability of the solution has room for improvement.

I have been using the solution for over four years.

I give the stability a seven out of ten.

The solution is scalable.

We have thousands of people using Microsoft Exchange Online.

We have a limited amount of time to contact tech support, but we usually communicate with the vendor. If I have an issue, our Microsoft partner can help us with problem-solving.

We previously used Google G Suite before switching to Microsoft Exchange Online.

The initial setup is straightforward.

The implementation was completed in-house with the help of our Microsoft partner.

We have seen a return on investment since we are taking advantage of the license and Microsoft Exchange Online's useful features.

The cost of our annual license for the solution is moderate. I would give the cost a five out of ten.

I give the solution a seven out of ten. Microsoft Azure has experienced outages at times, but it can be comparable to Amazon Web Services (AWS).

I strongly suggest using Microsoft Office Exchange due to its ease of use and maintenance, as well as its increased reliability and added security features.

It's a messaging card with the assembly solutions. I manage multiple platforms and upgrade and migrate the environment on-prem to online.

It is an easy-to-use platform. It provides both browser-based and desktop versions, accessible through a single license or up to three licenses. Additionally, with enterprise plans, you can use desktop licenses. It includes mail tagging and other top-notch security measures. You can manage mailboxes and utilize many other features based on your needs. Shared mailboxes are also available and can be used freely.

The cost is very high, and not every customer can afford licenses. Many customers only require the desktop version, so they don't opt for desktop licensing. Also, Exchange lacks a tunneling system. We need to explore third-party solutions and tunneling systems.

They are improving the new version of Outlook. It's free, and we provide the desktop application. This can be quite resource-intensive on the desktop level. When you open Outlook, it heavily utilizes your internet connection, slowing down your email access. Another issue concerns security features. There have been reported bugs in Microsoft's security features where emails marked as spam may still get through, leading to concerns about spoofing.

I have been using Microsoft Exchange Online for 11 years.

The solution is stable. However, some certain limitations and issues arise, particularly with the desktop application and related functionalities. Recently, Microsoft announced an issue with email invitations not functioning correctly in Exchange Online, leading to duplication and other disruptions.

We must procure licenses and ensure we have everything required based on the requirements. However, this also depends on the network. For instance, scalability and other issues may arise if we have fifteen users and a network speed of ten Mbps from our ISP.

I experienced an issue with Microsoft Exchange Online, where creations are typically sorted out within 15-16 days.

I've worked on involved setting up Microsoft Exchange Online. We implemented DMARC, DKIM, and other essential email authentication protocols. Additionally, we focused on configuring API access to enhance security measures. We also redirected all mail services to Office 365, a standard procedure. Our approach included reconfiguring settings according to best practices for Exchange Online.

The deployment spans one month at maximum, depending on specific requirements. For me, it is crucial to meet all prerequisites, such as domain names, DMARC policies, certificates, and other necessary configurations. Once these are prepared, straightforward implementations can be completed within seven days, barring unforeseen complexities. Integration with licensing structures, email gateways, and potential hybrid environments adds further considerations. Understanding hybrid configurations is essential and tailored to meet client-specific needs for an optimal online deployment.

All of that is managed within the pipeline. The cost-saving aspect involves reducing licensing requirements. For instance, if you have fifteen licenses, you must evaluate which licenses are unnecessary for non-required production. Reducing those licenses will reduce costs.

The compliance features are crucial. We have options such as rights management, marking as confidential, and restrictions on sending emails. Additionally, we monitor tunneling systems for security threats such as malware and employ spam filtering and anti-spam measures. These practices are designed based on industry best practices and tailored to meet customer requirements, including regulatory compliance. Retention policies are also implemented online for five to ten years, depending on customer and regulatory requirements.

It can be integrated using the Graph API. Third-party tools like IronPort and Mimecast can also be integrated with Exchange Online. These integrations often utilize Azure APIs for connectivity.

It requires maintenance based on our needs. Unnecessary licensing can become an issue, especially in large environments with multiple users. Therefore, it's essential to manage licenses effectively, such as by removing licenses from groups based on usage. Regular maintenance involves disabling users, removing sync, and adjusting licensing accordingly. Security features like spam filtering should also be upgraded quarterly to ensure optimal protection.

I recommend using Microsoft Exchange Online because it offers a straightforward environment. Administrative tasks are easily manageable at the L1 and L2 levels. However, it's important to note that Exchange Online operates primarily through a UI-based control interface. If issues like data corruption occur on the backend, we lack direct control to fix them ourselves. In such cases, we must report the issue to Microsoft for resolution.

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

The product is used to create email addresses. We can also create groups and distribution lists. The product also provides email forwarding features. We can create rules, monitor the flow of emails, and trace messages. We can use connectors on the platform for email security and email signature.

Message trace is the most valuable feature of the product. We can get a customized report on what is happening in our environment. We can trace all the emails, understand what happened, and get information on how they reached the user and the hops before delivery. It is very interesting.

We can also know how many deliveries failed and are pending in the queue and customize our reports how we want them to be. The product is very easy, simple, and secure. It is available everywhere because it is cloud-based.

The solution should have a better interface. The interface is a bit confusing. It should be more simple. The product should also improve the email flow. The rules are a bit complicated compared to the previous version. The previous version was much easier, and the latest one is more complicated.

I have been using the solution for four to five years.

In my organization, 150 people use the product. I have plans to increase the usage by 10% in one or two years, depending on how much the organization will grow. The product is extensively used in our company.

I had a very good first impression of the technical support team. Technically, the team is very good, very supportive, and very friendly. The team members are well-mannered while talking to customers. They follow up very well and are with us until the case is closed and we are satisfied.

Positive

I was using Lotus Notes five to six years ago. It was centrally based in our head office. I didn’t contribute to it. Later, when I applied to have my own email solution, I chose Microsoft.

The solution is very easy to set up. We just have to enter the username and password and start using it. We can deploy emails to end users within five to ten minutes. The product is cloud-based.

In our business, everything is done by email applications, Microsoft Excel, and Microsoft Word. So, we get a 60% ROI on the solution.

We pay a yearly licensing fee for the solution. The cost depends upon the plans we choose and the types of applications we want to use. We have a three-year deal with Microsoft to get a good price for the product. They are very willing to revise the price, accompany us for the setup, and give us a framework. They are very impressive to work with. There are no additional costs associated with the product.

I am using the latest version of the solution. Most businesses and users are using Microsoft for email business. I would recommend the solution to others. Overall, I rate the solution a ten out of ten.

Microsoft Exchange Online is used for emails and it does a fantastic job. 

The only reason why you would choose an online solution is the company that you're working at is they do not want to have an onsite server. The companies that want something on-site would choose the on-premise version.

The most valuable feature of Microsoft Exchange Online is if you have people that are geographically distributed from each other is good. For example, if you have people in the United States, Europe, Africa, Asia, and Australia, having an online solution works best because then you can reach the scale of the data centers that are available by Microsoft. Additionally, if you're only going to have two to three people using the solution the cost is a lot less than having an onsite server and licensing. It is highly beneficial in these areas.

The online archiving option works well. If you have a lot of emails and you want to keep them indefinitely, then you can use the online archive. It's available permanently and you can store quite a bit of email inside it.

I have been using Microsoft Exchange Online for approximately four and a half years.

The stability of the solution is good. I've only had an issue with it once or twice, but that was due to undersea cable damage.

Microsoft Exchange Online is highly scalable.

We have a lot of users using this solution.

The support from the vendor is fine. However, it could be faster, and some of the agents could be more knowledgeable, but it is a large solution, there's a lot of information that the agents have to work with. I can't always expect when I get connected to the first-level agent that they will know absolutely everything. Sometimes there's no replacement for pure experience.

I rate the support from Microsoft Exchange Online a three out of five.

Neutral

The initial setup of the cloud version is similar to the on-premise version. You can have a straightforward or semi-complex deployment. Cloud deployments do not become as complex as the on-premise version, but they can, depending on how it is used. 

The deployment of the solution only takes five minutes. It is very useful when deploying from scratch. As soon as you have the domain up and running it is complete and ready to go.

The license for the solution is cheap, but it could be more affordable in the long term.

We have one level two or level three engineer that does the deployment and maintenance of the solution. The online version does not require a lot of people to run it.

I recommend this solution to others and they will not regret it. They should not use other solutions.

I rate Microsoft Exchange Online a nine out of ten.

We use the Microsoft email suite and we use this solution on a client basis so email can go through it. Everyone is using it currently.

We like that it is online and easy to access. We can work for everywhere. You don't have to install anything. 

It's pretty reliable. We haven't had any issues with it. 

The product is scalable.

Technical support has been very good.

We've witnessed a bit more ROI since switching to the cloud. 

The solution is expensive. 

The stability could always be better.

I've been using the solution for three years. 

I'd rate the stability eight out of ten. We haven't had any issues, however, in previous versions, a few months back, we did have an outage.

It's scalable. I'd rate it ten out of ten for ease of expansion. There are 300 users on it right now. We do not have plans to increase usage. 

We've used technical support in the past. They have been very good. We have nothing to complain about. 

We don't have to do any setup. We just have to log in and start using it. Since it's cloud-based there is no configuration necessary.

We have three people who are able to deploy and manage the solution.

We've seen an ROI. When we were on-premises we had much more trouble. The cloud makes it much better. We're saving a bit more money.

The solution is expensive. For the price, we do get value, however, it is a bit too much money.

We pay for the solution on a yearly basis. There are no extra costs on top of licenses. 

I'm always on the latest version since it is a cloud-based solution. 

I'd recommend the solution to others if they have the budget.

I would rate the solution nine out of ten.

I don't use all the features of Microsoft Exchange Online. The product helped me solve my issue related to the storage size needed for backup every time.

Microsoft Exchange Online Microsoft is a useful tool for Microsoft Teams and scrum planning.

I feel that there is a need for improvement in the product, considering that there are some concerns with the tool's integration capabilities.

I have been using Microsoft Exchange Online for three years. My company has a partnership with Microsoft.

Microsoft Exchange Online is a stable product. Stability-wise, I rate the solution a nine out of ten.

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

Around 600 people in my company use the product.

My company has not planned to increase the use of the solution.

The product's initial setup phase was straightforward.

The solution can be deployed in a week.

My company requires people with some IT knowledge to handle the product's deployment and maintenance processes.

My company's in-house team deals with the product's installation process.

My company needs to make monthly payments towards the licensing costs attached to the product. I feel that the price of the product is affordable.

My company chose Microsoft Exchange Online over other products since we have a partnership with Microsoft. For our company's business uses, Microsoft helps save costs and offers good support.

The feature of Microsoft Exchange Online I found to be the most beneficial for team collaboration stems from the integration capabilities. Microsoft Exchange Online can integrate with products like Microsoft Teams or Windows Live.

I have seen that Microsoft Exchange Online's dashboard ensures the aggregation of all the integrated items in a single interface. I think my company has to order Microsoft Teams and apply for it separately to be used on a product like Microsoft Exchange Online.

The security and compliance features of Microsoft Exchange Online have impacted our company's business operations as it is a good tool for business needs, and I haven't seen any major issues with it in any of the items provided. I have also not had any negative reviews or complaints about the product from our company's teams.

I use the solution's calendar functions for my scheduling needs. but I don't know how it offers any support.

The tool's integration capabilities were used for the benefit of the management of the areas attached to the solution from a single place.

I rate the overall tool a nine out of ten.

The solution is basically for access and it provides the ability to just receive and send emails. It also works with calendars and contacts and all of that.

The solution works very well. It's one of the best options available. The access it provides is good. 

It has an easy initial setup. 

Technical support is helpful.

It is scalable.

The solution is quite stable. 

It has okay pricing. 

We'd like to have the ability to recall emails on the web. I'm not sure if that is available yet.

I haven't used the solution for too long and need more time to see if other improvements are needed.

The cost could be a bit lower.

We've had clients complain about some aspects of Microsoft Bookings. It would be great to have an opinion platform back on Bookings. 

I've been working with the solution for six months. 

The solution is stable. The only thing that is not so stable is Microsoft Teams. However, Exchange has good reliability. It doesn't crash or freeze. 

I love the scalability. I like that I can start wherever I am and scale up or down. I love the flexibility it gives us.

We have about 50 people on the solution presently. 

Technical support is great. I've raised some requests, and they were helpful and responsive. 

We did not previously use a different solution. 

I took part in the implementation process. The initial setup is pretty straightforward and simple. 

The deployment didn't take more than an hour. 

We have two administrators that are global admins. We have one admin that is specifically for Exchange. 

The pricing is fine. I've discussed this with customers, and they have found the price point to be fair. When you compare it to others, like Google, it is competitive. If it could be lower, of course, it would be ideal.

The solution costs $12 to $16 per user per month. 

I currently support Microsoft products. I don't sell Microsoft. They also have my test environment, where I test a few things.

Everything is available in the documentation. It's a great solution. Everything you need is there.

Overall, I'd rate the solution nine out of ten. There's always room to improve still. 

I work for civil ministries, and we exclusively use Microsoft products because we get them for a low price.

I handle security with Fortinet, and I run virtualization with Citrix. Those are my main tasks.

Microsoft has many consultants who can provide support.

Some of the Microsoft implementations of protocols are far from standard. They make their own standards, and you're out if you can't convert to them. With other Unix-based solutions, we had more flexibility to react to special problems we needed to solve. We can only solve the problem now if the problem is solvable with Microsoft.

Similarly, it is tricky to integrate Microsoft Exchange Online if you are in an infrastructure provided by other vendors. We have had an alternative solution to Exchange since 2016, and if we had problems, it was never a problem with Microsoft. It was a problem with the alternative product. The problem is that Microsoft has a standard, and you need to stick to it.

Even if the reason for the problems is Microsoft, the SMTP stack in Exchange is far from the RC of SMTP. If the alternative solution makes extensions to DNS for their active directory and if you use an RC DNS server, you would have problems with some of the records that Microsoft produces. They are not replicated. If you begin with Microsoft, you make everything Microsoft. It is difficult to mix Microsoft with other vendors or with other products. And you get less support if you want to choose a solution other than Microsoft.

Moreover, Exchange Online should work on integration with other services like Teams because when they work together, you gain benefits that other companies might not be able to give you.

I have been using Microsoft Exchange Online since 2012, and we will use it in the future.

We formerly worked with Unix-based mail servers. The positive side is that you're flexible. You could use different hardware. You get limited with Microsoft.

Microsoft solutions are expensive.

I prefer to use solutions like LibreOffice since they are free and cheaper, but our partners might have problems reading our data, and we would face difficulties cooperating.

The main problem with Microsoft products is that we get very dependent on them. Until 2016, I had to make decisions for the budget for the Southwest of Germany, and when you work with Microsoft, your budget is fixed to them, and you lose your ability to work with other solutions. That was a bad situation for us.

If you don't plan to use other solutions in the future, it's a good product. Otherwise, you have to be prepared that some problems may arise. Once you get married to Microsoft, it's a fierce divorce if you want to leave. I rate the solution an eight to nine out of ten.