Continuity Event Management

Document created by user.oxriBaJeN4 Employee on Jan 19, 2017Last modified by user.oxriBaJeN4 Employee on May 30, 2019
Version 15Show Document
  • View in full screen mode

Event NotificationThe Continuity Event Management functionality makes it easier for administrators to respond quickly to email flow disruptions. They can configure thresholds for high latency and failed deliveries in both inbound and outbound email.


If a potential issue is detected between Mimecast and your organization's email server, and one of the threshold conditions is met, an alert is issued (see right). The alert contains a link (valid for 24 hours) that provides access to a Continuity Portal, that can be used to start, extend, or stop continuity events.


Alerts are issued every hour for as long as the algorithm detects a potential issue, and one or more threshold conditions have been met. The continuity portal can also be used to suspend these notifications for a set time frame.



Continuity Event Management enables you to manage continuity events by:

  • Negating the need to create continuity events in advance.
  • Starting or extending a continuity mode.
  • Suppressing the alerts.
  • Ending a continuity mode.


What You'll Need...


To use Content Event Management, your organization must have access to:

  • A Mimecast account enabled with Continuity Event Management.
  • To notify administrators of a potential issue, either: 
    • A valid SMS number.
    • A group of external email addresses to notify administrators of a potential issue.
  • A configured Server Connection.
  • Impersonation rights to your organization's mailboxes in order for the outbound test email message to be sent.


Configuration Requirements

Mimecast for Outlook can only enter continuity mode if Microsoft Outlook has the "Use Cached Exchange Mode" option enabled in your Account Settings. If Microsoft Outlook is in non-cached mode, continuity functionality is not available.

Continuity Event Management supports:

  • Microsoft Exchange Web Services On-Premises deployments that:
    • Allow inbound HTTPS access from Mimecast to your organization’s Client Access Server (/ews/exchange.asmx).
    • Share the credentials of a mailbox with the Application Impersonation management role with Mimecast.
  • An association with Office 365 / Exchange installations or hybrid combinations. This requires you to:
    • Register Mimecast cloud synchronization as a web application.
    • Set up a secure trust relationship with it, via a certificate provided by Mimecast.
    • Grant it permissions to impersonate users over Exchange Web Services.


See Also...


1 person found this helpful