Microsoft 365
Your organization’s Microsoft environment: accounts, mailboxes, and tenant policies.
Microsoft 365 with MailContactDaemon
Campaigns leave from the mailboxes your company already uses. MailContactDaemon prepares, schedules, and tracks — Microsoft remains the mail service.
Exchange Online
The mail service inside Microsoft 365 — where messages are actually sent and received.
MailContactDaemon
The campaign platform: sequence, pacing, recipients, replies, and reports — connected to your mailboxes, without sending from our servers.
Two ways to connect
Pick the path that fits your team size. In both cases, no Microsoft password is stored in MailContactDaemon.
- Single mailbox: authorize once with your Microsoft account. You can revoke access anytime on the Microsoft side.
- Organization: one central connection for several sending mailboxes, including shared ones (sales@, hello@), when your plan and Microsoft permissions allow it.
- If authorization fails, the product explains why and what to do next — without unnecessary jargon day to day.
What MailContactDaemon does — and does not
Clear roles avoid surprises about reputation and limits.
- Does: campaigns, sequences, scheduling, per-sender pacing, replies, and stats.
- Does not: host your Microsoft 365 or replace Exchange Online.
- Campaign emails leave from the addresses you choose — sending reputation stays with your organization.
Pacing and limits
MailContactDaemon applies per-sender pacing limits to protect deliverability. Your Microsoft tenant policies and Exchange Online service limits still apply in parallel.
- You can set a daily pace per address in MailContactDaemon.
- Your Microsoft tenant may have its own outbound rules — that is not MailContactDaemon.
- We do not promise “unlimited Microsoft volume”: what matters is a healthy mix of MailContactDaemon pacing and your real environment policies.
Access requested on Microsoft 365
We only ask for what is needed to send and track campaigns from your mailboxes. You can revoke access anytime from your Microsoft account.
What MailContactDaemon asks for
- Identify the account (single mailbox). Know which Microsoft user authorized the connection, without storing the password.
- Send email from the mailbox. Campaigns leave from the address you choose — not from our servers.
- Read the mailbox (when inbound is enabled). Detect replies, bounces, and out-of-office for Catch Leads and stats.
- Keep the connection active. Refresh authorization without asking for the password every time.
- Organization: send and read on chosen mailboxes. One central connection can cover several mailboxes (including shared ones), only when your plan and Microsoft permissions allow it — not blanket access to every mailbox in the tenant by default.
What we do not ask for
- Your Microsoft password
- Access to files, calendar, or OneDrive
- Permission to change or delete all mail (full mailbox read/write)
- Control of your Microsoft 365 tenant or Exchange Online
What stays on the Microsoft side
Microsoft 365 and Exchange Online remain the mail service: tenant policies, outbound limits, and access revocation are managed there. MailContactDaemon orchestrates campaigns; it does not replace Microsoft.
Frequently asked questions
Do I need to change email provider?
No. You stay on Microsoft 365 / Exchange Online. MailContactDaemon connects to the mailboxes you already use.
Do you store my Microsoft password?
No. The connection uses Microsoft authorization. You can revoke access from your Microsoft account without going through us.
Can I use shared mailboxes?
Yes. Shared addresses (for example sales@) can be senders when the connection and permissions allow it.
Does MailContactDaemon send from your servers?
Not for Microsoft 365 campaigns: sending leaves from your mailboxes. MailContactDaemon orchestrates the campaign; mail stays in your Microsoft environment.
Ready to connect your first Microsoft 365 mailbox?
Start free or see how the plan scales with the number of senders.