Microsoft Exchange Online Reviews

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.