Send with Google Workspace or Microsoft 365
Connect your Google Workspace or Microsoft 365 mailbox and send campaigns from your own business address, with no DNS setup to do first.
A sending connection lets Mailsoftly hand your campaign to your own mailbox provider instead of sending it on shared Mailsoftly infrastructure. You design the email here, and Google or Microsoft actually puts it on the wire, from your real address, with a copy landing in your own Sent folder.
It takes about two minutes and touches no DNS at all, which is exactly why it exists: it is the fastest honest way to get your first campaign out of the door. This guide covers both providers, what you give up compared with authenticating your own domain, and what to do when a connection breaks.
Choose between a connected mailbox and your own domain
Open the Integrations screen. Google Workspace and Microsoft 365 sit in the Featured section alongside the rest of the catalog, and a green check marks a connection you have already made. Before you connect anything, it is worth being clear about what you are choosing, because Mailsoftly supports both lanes and you can hold both at once.
A connected mailbox is right when you want to start today, you send to modest lists, and you care that replies land in the inbox you already watch. There is no DNS work, your mail rides your own Google or Microsoft reputation rather than a shared pool, and recipients see the address they already know. In exchange, Mailsoftly applies a daily recipient cap on that lane to keep your provider from flagging the account, only the person who connected the mailbox can send from it, and A/B tests and gradual sending stay on the domain lane.
An authenticated domain is right when you send larger campaigns, when the whole team needs to send as the same address, or when you want A/B testing and gradual sending. It costs you a few DNS records and a wait for propagation. Most accounts end up doing both: connect a mailbox now, authenticate the domain when volume asks for it.
Connect a Google Workspace account
Open the Google Workspace card. The page explains what the connection does: send your Mailsoftly designed emails straight from your Google Workspace account, track replies and engagement inside Mailsoftly, and a secure OAuth2 authentication. Press Connect Google Workspace Account and Google takes over.
On the Google permission screen, tick both boxes. One grants permission to read, compose and send email from your account, which is what actually sends your campaigns. The other grants Mailsoftly ongoing access, which is what stops the connection expiring in a day. Google lets you approve these one at a time, and a connection missing the sending box cannot send anything, so Mailsoftly refuses it and asks you to try again rather than leaving you with a connection that quietly fails.
A personal Gmail address works here too, with a lower daily sending limit. If you started on a personal Gmail and later got a Workspace account, the page offers Switch to Google Workspace: sign in again with the work account and the higher daily allowance is applied straight away.
A Google account can only be connected to one Mailsoftly workspace at a time. If you get told the account is already connected elsewhere, disconnect it there first, or connect a different account.
Connect a Microsoft 365 account
The Microsoft page works the same way. It leads with your company Microsoft 365 account and the same three promises: send straight from your Microsoft account, track opens and clicks inside Mailsoftly, and secure OAuth2 authentication. Press Connect Microsoft Account, pick the account you want on the Microsoft screen, and approve the request.
The permission that matters is the one that lets Mailsoftly send mail as you. Some company tenants trim requested permissions automatically, so if that one does not come back granted, Mailsoftly stops the connection there and tells you exactly which permission to allow. Approve it and connect again.
Personal Outlook, Hotmail and Live addresses connect too, with lower daily sending limits, and Mailsoftly labels them honestly as Outlook rather than Microsoft 365. A work or school account is recognised as Microsoft 365 from the sign in itself, not guessed from your address, and it is granted the higher daily allowance.
The connection belongs to a person, not to your workspace. If someone revokes Mailsoftly at Google or Microsoft, if an IT admin removes the grant, or if the account owner leaves the company and their mailbox is closed, the next campaign on that lane simply will not send. Nothing warns you in advance. Reconnect from this page, or move the campaign to another sender.
Send a campaign from the connected mailbox
Open a campaign in draft and click the From row on the Campaign Details tab. Once you hold both lanes the picker splits into two groups: Your verified domain first, then Your connected mailbox. That order is deliberate. A verified domain is the better default once you have one, because the whole team can use it and it carries your full sending allowance, so the mailbox stays available as an explicit choice rather than quietly taking over.
Each mailbox option shows the address, the account type in brackets, and the caption Sends through your own account, next to the real Google or Microsoft mark. Pick one and the campaign leaves through that provider. The star beside the picker sets your own personal default, so your next campaign starts on the sender you actually use.
Two things change once a mailbox is selected. The Reply To field locks to the connected address, because that is the only address the provider will accept for this send. And the Send Now button picks up the provider mark, so you can see at a glance which lane a campaign is about to leave on.
You will see a teammate’s connected mailbox in the list, but you cannot select it. Only the person who connected a mailbox can send from it, because the sign in that authorises the send is theirs. If a shared address needs to be available to everyone, put it on your authenticated domain instead.
Understand the limits and what still applies
A connected mailbox carries a daily recipient cap that is separate from your plan, and it exists to protect your account with your own provider rather than to protect us. A work account, meaning Google Workspace or Microsoft 365, is granted a noticeably higher daily allowance than a personal Gmail or personal Microsoft address. If a campaign is larger than the cap, Mailsoftly tells you the exact numbers for your account before anything is sent, along with your options: spread the send over several days, or authenticate your own domain to unlock full campaign sending. Your monthly total is one shared pool across every way you send, so a mailbox campaign and a domain campaign draw down the same monthly counter.
Everything else about a campaign works exactly as it does on the domain lane. Open and click tracking still applies, the unsubscribe footer and the one click unsubscribe headers are still added, and your suppression list and unsubscribes are still honoured before a single message goes out. Scheduling works on this lane too, and the future send fires from the stored connection. A/B testing and gradual sending do not: both stay on the domain lane, and Mailsoftly points you there when you reach for them.
Because your mail physically leaves through Google or Microsoft, your inbox placement rides your own account reputation. That is the real upside of this lane for a small sender, and the real reason for the daily cap. When you outgrow it, authenticate your sending domain and keep an eye on deliverability and reputation from there.
Review your mailboxes and disconnect one
Every connection your workspace holds is listed on the Senders screen under Connected mailboxes, below your verified domain senders. Each row shows the address, its account type, who connected it, and an Active or Inactive state. If the mailbox is yours, the row is a link: Manage takes you back to the connection page.
To disconnect, open that page and press Disconnect. Mailsoftly confirms first, then removes the stored connection and marks every sender on that mailbox inactive. You can reconnect at any time from the same page. Microsoft gives no way for an app to withdraw its own access from the outside, so if you want the grant gone from your Microsoft account as well, remove Mailsoftly from your account permissions there too.
One thing to check before you disconnect: any campaign scheduled to send from that mailbox. It will not be cancelled. It will fire at the scheduled time, fail the permission check because the connection is gone, and your workspace admins will get an email telling them the send was stopped. The campaign is still there, so open it, choose a different sender, and schedule it again.
Connect a mailbox and your first campaign can go out today, from an address your recipients already recognise. Authenticate your domain when volume asks for it, and both lanes will sit side by side in the same picker.
Ready to try it in your own account?
Free to start with your Google Workspace or Microsoft 365 account. No credit card required.
