Microsoft connection
Connect supported Microsoft 365 mailboxes to your workspace, so your organization’s accounts can power outreach.
Built for agencies and B2B sales teams.Built for lead generation agencies and B2B sales teams. Manage contacts, automate email sequences, and handle replies in one workspace.
Start free →Connect the Microsoft 365 and supported Outlook accounts your organization controls, for outreach operations, campaign usage and reply handling, all in one workspace.
A focused set of tools that fit into the wider DevBoxy outreach platform, from the first connection to the replies that follow.
Connect supported Microsoft 365 mailboxes to your workspace, so your organization’s accounts can power outreach.
Make prepared accounts available to the campaigns that need them, with pacing and automated follow-ups managed in one place.
Make connection state and sending readiness easier to review, before an account joins a live campaign.
Bring campaign responses into a more consistent handling workflow, with the context of the campaign attached.
Once an account is connected and reviewed, assign it to the campaigns that should send from it. Manage pacing, follow-ups and replies without leaving the workspace.
| Account | Provider | Campaigns |
|---|---|---|
| [email protected] | Microsoft 365 | Q3 SaaS Agencies |
| [email protected] | Microsoft 365 | Q3 SaaS |
| [email protected] | Google Workspace | Agencies |
| [email protected] | SMTP | RevOps |
An account that looks connected is not always ready to send. Review both, so nothing half-configured reaches a live campaign.
| Account | Connection | Readiness |
|---|---|---|
| [email protected] | Connected | Ready |
| [email protected] | Connected | Ready |
| [email protected] | Connected | Review needed |
Responses are only useful if the right person sees them quickly. DevBoxy brings campaign replies into a consistent handling workflow, with the campaign, sender and contact attached.
A connected account can send, but your domain’s DNS decides how receivers treat the mail. Check SPF, DKIM and DMARC before an account joins a live campaign.
| Type | Host | Value | Status |
|---|---|---|---|
| TXT | @ | v=spf1 include:spf.protection.outlook.com -all | Pass |
| CNAME | selector1._domainkey | selector1-acme-outreach-io._domainkey… | Pass |
| CNAME | selector2._domainkey | selector2-acme-outreach-io._domainkey… | Pass |
| TXT | _dmarc | v=DMARC1; p=none; rua=mailto:… | Pass |
A few habits keep accounts healthy and outreach consistent.
Many teams send outreach from dedicated domains or subdomains, to protect the main brand domain.
Use several accounts per campaign so no single mailbox carries all of the sending.
Clean lists protect every account you connect. Verify addresses before they enter a sequence.
Once an account is connected, build on it.
It connects supported Microsoft 365 mailboxes to your DevBoxy workspace, so you can use them for outreach operations, campaign sending and reply handling alongside your other accounts.
You can connect Microsoft 365 accounts and supported Outlook sender accounts that your organization controls.
Yes. Prepared accounts can be made available to every campaign that needs them, and you can combine Microsoft 365 accounts with Google Workspace and SMTP accounts in one campaign.
Account oversight shows the connection state and sending readiness of each Microsoft account, so you can review it before you assign the account to a live campaign.
Campaign responses are brought into a consistent handling workflow with the campaign and sender attached. See the unified inbox for how supported replies are tracked.
It is strongly recommended. Authentication records help receivers trust your mail, and you can test them with the free network tools before you launch a campaign.
Yes. DevBoxy also supports Google Workspace and <a href="https://devboxy.com/smtp-email-accounts">SMTP accounts</a>, and shows them together in one account view.
Start with the tools you need today, then connect more infrastructure, campaigns and conversations over time.