Microsoft Exchange Online Reviews

We are primarily using the solution for Office 365 and various other Microsoft products. It's used for any integration of any applications. Multiple company domains have been configured on a single exchange. It helps us standardize and consolidate connectivity. 

We like the standardization we can get across all of our companies. We can put all domains on one exchange. The user can then have one single ID instead of creating five emails for one user. 

It scales well.

Technical support is helpful.

It's not hard to set up.

The solution is stable.

The product offers good value for money. After a few years, we have seen an ROI. 

There are no features that are missing.

We'd like to see more integration with other platforms. We'd like to explore the feature of SSO and Artemis. 

I've used the solution for more than three years. 

The solution is stable and reliable. There are no bugs or glitches. It's very stable. 

The solution can scale well. It's cloud-based, which makes it very simple. We just have to approach our reseller and add on more licenses. You can have 50 users or 50,000 users, and it will work just as well. 

We have about 1,000 or more users on the product currently. We do have plans to increase it to 1,500 by the end of the year. 

We may have used technical support previously and were able to resolve any issues within a week. They are very good. They are helpful.

I did not previously use a different solution. Past colleagues may have used something else. 

The initial setup takes two to four weeks. It's pretty straightforward. We take each domain and consolidate everything on the exchange. We can migrate everything in one go, and usually, we migrate each company each week and migrate one by one, so that end users are not disturbed. 

We have experienced an ROI after three to four years. 

We pay for the solution annually. The price is a bit expensive. However, it offers good value for money. The implementation cost is minimal. Also, now it is on the cloud, we don't have to worry about storage, maintenance, or hardware. The cloud is highly secure, and it helps save us money in the long run. 

This is the latest version. We are using the cloud version, and it is constantly updated. We are using all of the standard features that come with the cloud-based product. 

This is a very user-friendly enterprise solution. Everything is very secure according to GDPR needs. The product is scalable, and its offering good value for money. Everyone can use it. It's a great product.

I'd rate the solution nine out of ten. 

The primary use case of Microsoft Exchange Online is for emailing.

The most valuable feature is the cloud environment.

The deployment is complex and has room for improvement.

I have been using the solution for five years.

The solution is stable.

The solution is scalable.

The technical support is good.

The initial setup is straightforward.

The deployment takes some time because it is complex.

We required 14 people for the deployment.

We have a three-year license for $25,000.

I give the solution a nine out of ten.

We have 700 people using the solution.

I recommend Microsoft Exchange Online to other users.

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 use cases involve reporting the number of completed tasks and saving contact information.

A valuable feature of the solution is its global usability, particularly in facilitating actions within the sourcing department. It proves to be highly useful in this regard.

There is room for improvement in terms of optimization. Moreover, the pricing could be improved.

I have been using the solution for the past nine years.

The solution is stable.

The solution is scalable. It is currently being used by ten people in my sourcing department.

The initial setup was straightforward. It took a few minutes to deploy the solution. Three persons are required for deployment and maintenance.

Initially, the solution is useful. However, I recommend exploring alternative propositions that are easier and more efficient. Conducting periodic tests could be beneficial in making informed choices.

I rate Microsoft Exchange Online 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.

We use Microsoft Exchange Online to send and receive emails through user and application mailboxes.

The product’s most valuable feature is the online archive.

From an IT perspective, we need clearer documentation to understand the product’s configuration process. It will be helpful if any precise and clear troubleshooting guides are available on the internet.

We have been using Microsoft Exchange Online for 11 years.

I rate the product’s stability a seven out of ten. It could be improved.

We have 65,000 Microsoft Exchange Online users in our organization. We plan to increase the usage as our company keeps acquiring new companies, and then we merge the users from the acquired companies. I rate its scalability a nine out of ten.

It is challenging to make the front-line technical support team understand the issues. The quality of support needs enhancement.

Neutral

I rate the initial setup process an eight out of ten. It takes around a couple of weeks for complete deployment.

We have an enterprise agreement with Microsoft. Since the last renewal, we have had one more 100% increase in the license due to new acquisitions. We asked Microsoft to provide some discount. Instead, they increase the license cost. The price is not competitive.

We only pay for an enterprise agreement, which includes on-site engagement activities from successful engineers, training sessions, vouchers for exams, etc.

It is important to do homework on exact business requirements and then make a purchase decision. It is not a cost-effective solution in some cases. I rate Microsoft Exchange Online a seven out of ten.

We primarily use it for email authentication, and I believe we've adopted nearly all the associated features and updates that have been implemented.

The most valuable feature as it encompasses all aspects of collaboration, communication, reporting, and storage.

There is room for improvement in terms of security, as it could be better. Enhancing end-user knowledge is crucial, as it often requires multiple steps and can become intricate when trying to meet our expectations.

I have been working with it for ten years.

The system has maintained a high level of stability, although managing licenses and testing can be a bit challenging, especially for large organizations like ours. The downtime occurrences have been relatively rare, with any issues that arise being promptly and effectively resolved.

It's highly scalable and you can easily expand your licenses and integrate new capabilities and modules. We can also tap into other solutions by simply using plug-ins, which provide the capabilities we need, and scalability remains a straightforward process.

We occasionally rely on tech support, and while they often meet our expectations, there are instances where our anticipated resolution timelines are not met. This can be attributed to the prolonged engagement period. On a positive note, the overall experience with support has been satisfactory, with most interactions going smoothly. I would rate it eight out of ten.

Positive

The initial setup is quite straightforward and not overly complex

The deployment process doesn't differ significantly from other solutions. It involves integrating with our online domain controllers for authentication and setting up the system. It's a straightforward process without complex steps or unique challenges, we collaborate directly with the OEM, without involving external consultants.

I find it reasonably priced.

Overall, I would rate it eight out of ten.