Continuity · Fallback

The mail systemis down.The business is not.

Email continuity keeps the mail channel open while Microsoft 365 or your own server does not respond. Mail is still accepted, read and answered, and flows into the mailbox automatically once the outage ends.

Request a demo See continuity

Primary system unreachable

Operated in Germany

What a solution must do to hold up when it counts

Four points where preparation fails in practice.

Accept instead of reject

When the target system does not answer, an upstream instance has to accept the message anyway. Otherwise mail sits with the sender and nobody knows what is in flight.

Reading is not enough

Being able to read means being reachable, not being able to act. Replying has to work, and with the usual sender address.

Access has to exist beforehand

Anyone who signs in only through Microsoft cannot get in when that sign in service is down. This cannot be fixed after the fact.

Everything has to flow back

Without automatic delivery afterwards, the messages from the outage stay in a side channel and are later missing from the mailbox and the archive.

How continuity works

Nothing to switch, nothing to prepare during the incident.

1. A store that runs alongside

Every incoming message is stored as it passes the gateway, whether or not an outage is under way.

2. Access and reply in the browser

Your team signs in to the Conbool interface, keeps reading and replies. The sender address is checked against your own addresses before anything leaves.

3. Delivery after the outage

As soon as the target system accepts again, messages are delivered into the mailbox automatically. Nobody has to move anything by hand.

Delivery pathoutage

External sender

Conbool gateway

Microsoft 365

not accepting

Continuity

readable and answerable

As soon as the target system accepts again, everything flows into the mailbox automatically.

The path of the message

One path is closed, the other open.

The gateway sits in front of your mailbox system. When that stops responding, Conbool accepts the message anyway and makes it available in its own interface.

Acceptance instead of rejection, even during an outage

Read and reply in the browser

Sender address checked before anything leaves

Delivery afterwards starts automatically

What makes the difference

Six points that count in an emergency.

No manual step when it starts

The store runs continuously. In an emergency nobody has to find out whether the fallback actually works.

Replies from the usual address

Business partners see no difference. Foreign sender addresses are ruled out, every reply is checked against your registered addresses.

Notification through another channel

The alert deliberately avoids the mailboxes that are currently affected. A safeguard nobody hears about is not one.

History from the archive

With Conbool Archive, older correspondence is available too, not only the mail since the outage began.

Readiness visible in advance

The interface shows who would really get in during an outage and who depends on the failed sign in service.

Automatic deletion after the retention period

The fallback copy is removed on its own once the configured period ends, with no leftovers.

Preparation compared

What the usual answers to an outage achieve.

	With Conbool	Without preparation
Incoming mail accepted during the outage	yes	no
Replying during the outage	yes	no
Automatic delivery into the mailbox afterwards	yes	not applicable
Alert through an unaffected channel	yes	no
Access verifiable in advance	yes	no

The column without preparation describes the ordinary case with no upstream instance, not a specific competing product.

Frequently asked questions

What exactly does email continuity mean?

The term covers preparation for keeping the mail channel running while the mail system itself is unreachable. It includes acceptance, access and reply as well as delivery back afterwards.

Does it work with an on premises Exchange server?

Yes. Continuity sits at the gateway, not at the mailbox system. Whether Microsoft 365 or your own server sits behind it makes no difference.

How is this different from a backup?

A backup recovers lost content once it is missing. Continuity makes sure work can carry on in the meantime. They solve different problems and do not replace each other.

Will business partners notice we are on the fallback?

No. Replies leave through the regular outbound path with the usual sender address.

What has to be prepared?

Everyone who needs access during an outage requires an account that does not depend solely on the sign in service of the failed system. The interface openly shows where that is still missing.

Does this satisfy a NIS2 requirement?

Business continuity and crisis management are explicitly among the required measures, and the mail channel is the one whose outage is felt fastest.

Rehearse the incident before it happens

We demonstrate acceptance, access, reply and delivery on a test environment, without touching your systems.

Request a demo Get in touch