Exchange Online is down.Your peopleare not.
During a Microsoft 365 incident your tenant stops accepting messages. Senders retry, but nobody can read or reply. Conbool bridges exactly that window.
What actually happens during a Microsoft 365 incident
The mail is not gone. The working day is.
Service status does not help you work
The message center tells you an incident exists and is being worked on. It does not tell you how your staff answers customer requests in the meantime.
Inbound queues, outbound stops
Senders hold messages in their queue, usually for twenty-four to forty-eight hours. During that time nothing leaves your side.
Deadlines keep running
Bid deadlines, tenders and statutory deadlines do not care about a vendor status page.
There is no second channel
Phone lists are outdated, private messengers are not an option for data protection reasons, and nobody has a second mailbox.
Conbool already sits in front
As the upstream instance Conbool sees the incident at the same moment the senders do. That becomes usable access.
1. Detect the incident
If your tenant repeatedly refuses messages over a longer period, Conbool switches to emergency mode. A single hiccup deliberately does not qualify.
2. Provide access
Your people sign in with their usual Conbool account and see the messages Exchange Online did not accept.
3. Reply and keep working
Replies go out through the regular Conbool path, signed and inspected as always. Nothing looks different to your business partners.
What this means for your Microsoft 365 tenant
No change to your tenant, no app, no additional vendor.
Nothing changes in Microsoft 365
No add-in inside the tenant, no permission, no connector beyond the one MailGuard already uses.
Works during sign-in incidents too
A share of incidents does not affect mailboxes but authentication. Conbool has its own sign-in and is not affected.
Hybrid environments included
Exchange Online, on-premises Exchange or a hybrid combination makes no difference. What matters is that the next hop sits behind Conbool.
The backlog stays orderly
After the incident senders deliver as usual. Conbool only holds a read copy, so no second delivery and no duplicate occurs.
Protection stays active
Even in emergency mode every message passes the full inbound inspection. An outage is no reason to suspend protection.
Plannable for maintenance
Emergency mode can be switched on by hand before a planned migration.
The usual answers to an M365 incident
What companies do, and what it achieves.
With Conbool | Without | |
|---|---|---|
| Read messages during the incident | yes | no |
| Reply during the incident | yes | no |
| Change required in the Microsoft 365 tenant | no | none |
| Works during sign-in incidents | yes | no |
| Additional vendor in the mail path | no, Conbool already sits in front | none |
| Preparation time before the incident | one switch | none, but no effect either |
This comparison describes operation across a company. For individual users, encryption inside the client remains a workable solution.
Frequently asked questions
How do I tell whether Microsoft 365 and not my network is the cause?
Are messages lost during an incident?
Do I need additional Microsoft licences?
What about calendar and Teams?
Do my business partners see that we are in emergency mode?
Is this a second mailbox I have to maintain?
How fast does it switch over?
Does this satisfy a NIS2 requirement?
Verwandte Lösungen
E-Mail-Notfallpostfach
Lesen und antworten, waehrend das eigene Mailsystem steht.
NIS-2 Betriebskontinuitaet
Aufrechterhaltung des Betriebs nach Artikel 21 fuer den Mailkanal.
NIS-2 E-Mail-Sicherheit
Alle E-Mail-Anforderungen nach Paragraf 30 BSIG im Ueberblick.
Microsoft 365 E-Mail-Sicherheit
Warum der eingebaute Schutz von Microsoft 365 nicht ausreicht.
Rehearse the incident before it happens
We show emergency mode on your own tenant without touching your environment.