Operations heads at logistics and freight companies rarely have time to babysit email. Dispatch inboxes, depot users on shared PCs, drivers on phones and customers chasing proofs of delivery all depend on mail working every hour of the day. This article compares Microsoft 365 Outlook setup vs in-house logistics company approaches, so you can decide whether your own IT person should configure the tenant or whether a specialist should do it. It covers shared mailboxes, branch users, multi-factor authentication, shift-worker access, DNS records and migration from old mail.
Every fleet and forwarding business is different, so treat this as a decision framework, not a promise of outcome. If you want to see how an outside team scopes this work, our Microsoft 365 and Google Workspace setup service page explains the process.
Why logistics email is different from office email
A typical office has desks, laptops and fixed hours. A logistics operation has none of those certainties, and that shapes the setup.
- Shared inboxes carry the business: dispatch, bookings, customs documents, billing and claims mail must be visible to several people without anyone sharing a password.
- Many locations: head office, depots, branches and cross-dock sites each need the right users, printers and permissions.
- Shift work: night dispatchers and warehouse staff log in at odd hours, often on shared or personal devices.
- Mobile-first staff: drivers and yard supervisors read mail on phones, not desktops.
- Time-sensitive messages: a missed delivery exception or a customs query that sits unread has an operational cost.
- Targeted fraud: payment-diversion and fake booking emails are common in freight, so authentication and spoofing protection matter.
What a proper Microsoft 365 and Outlook setup involves
"Setting up Outlook" is shorthand for several separate jobs. Looking at them individually makes the in-house versus outsourced decision much clearer.
Shared mailboxes for dispatch and operations
Dispatch, bookings and billing addresses should usually be shared mailboxes, not ordinary user accounts. Staff get access through their own sign-in, so you can see who replied to what, and removing a leaver never locks the team out of the address. You also decide who can send as the shared address and whether sent items are saved to the shared folder, which matters when a customer asks what dispatch told them last night.
Depot and branch users
Each site needs sensible groups, licences matched to the role, and distribution lists such as "all depot managers" or "night shift supervisors". A clear naming standard prevents the sprawl that appears when branches create accounts on their own.
MFA and conditional access
Multi-factor authentication is the single most useful protection for a mailbox. In logistics it needs thought, because a warehouse worker may not carry a personal phone on shift. Options include authenticator apps, hardware security keys for shared stations, and policies that treat sign-ins from the depot network differently from sign-ins abroad. Admin accounts need the strictest rules, and a documented break-glass account protects you from locking everyone out.
Mobile and shift-worker access
Drivers and floor staff need mail on their phones without exposing the whole company if a device is lost. Mobile app protection policies, remote wipe of company data and a simple enrolment guide cover most needs. Shift workers who only need mail and a few tools may fit a lighter licence than managers, so licence choice is a cost lever worth reviewing.
DNS: MX, SPF, DKIM and DMARC
These records decide whether your mail arrives and whether criminals can impersonate you.
- MX records route incoming mail to the correct service.
- SPF lists the servers allowed to send for your domain, including your TMS, tracking system or invoicing tool.
- DKIM signs outgoing mail so receivers can verify it was not altered.
- DMARC tells receivers what to do with mail that fails those checks, and sends you reports.
Logistics companies often have many systems that send mail on their behalf, such as tracking notifications, freight portals and accounting software. A hasty SPF record that forgets one of them causes lost shipment notices. A careful DMARC rollout starts in monitoring mode and tightens gradually.
Migration from old mail
Moving from an old hosted mailbox, a legacy on-premises server or a free consumer account means copying mail, calendars and contacts, then switching MX records at a planned time. Long-running shipment threads and attachments such as proofs of delivery are the content you cannot afford to lose, so a pilot group and a rollback plan are worth the effort.
Doing it in-house: where it fits
An in-house setup is reasonable when you already employ an IT administrator who has configured a Microsoft 365 tenant before, the user count is small, and you are starting fresh with little history to migrate. It also helps when your team will own the tenant long term and enjoys the control.
The hidden costs are the ones that appear later. A one-person IT function becomes a single point of failure. Security defaults get left in place because nobody has time to tune them. DNS changes are made once and never reviewed. During a migration, that same person is also answering every other helpdesk call, so the project drags. Our Outlook and Microsoft 365 setup team sees these patterns regularly in businesses that grew faster than their IT.
Using a specialist: where it fits
A specialist makes sense when you have several depots, mixed legacy mail systems, strict customer security questionnaires, or no dedicated IT person. The value is repeatable experience: a tested sequence for tenant setup, DNS, pilot, cutover and clean-up.
The risks are different. You depend on the vendor for changes unless handover is clear, and a rushed vendor can leave you with settings nobody understands. Those risks are manageable with the terms listed later in this article.
Microsoft 365 setup: in-house vs specialist comparison
| Factor | In-house IT | Specialist setup |
|---|---|---|
| Upfront cost | Looks low because it uses existing salary, but the time is taken from other work | A scoped project fee, predictable when itemised |
| Ongoing cost | Admin time, training and licence management | Optional support plan sized to your needs |
| Speed to go live | Slower when the admin is also running the helpdesk | Usually faster, with a planned cutover date |
| Shared mailbox design | Works if the admin has done it before; often ad hoc | Designed around dispatch and branch workflows |
| MFA and shift-worker access | Risk of weak policies that nobody revisits | Policies built for shared stations and mobile staff |
| DNS and email authentication | Frequently incomplete, such as SPF missing a sender | MX, SPF, DKIM and DMARC configured and tested |
| Migration risk | Higher if this is the first migration | Lower with pilot group and rollback plan |
| Key-person risk | High when one admin holds all knowledge | Lower if documentation is a deliverable |
| Control after launch | Full | Full, provided you own admin credentials and documents |
Neither route wins everywhere. In-house offers closeness to the business and no vendor dependency. A specialist offers speed, a repeatable method and less reliance on one person.
What drives the cost either way
We do not quote figures in an article, because they depend on your environment. These are the factors that move the price, whichever route you choose.
- The number of users, and how many are full users versus light shift-worker accounts.
- The number of shared mailboxes, groups and sites.
- The volume and age of mail to migrate, and the source system.
- Number of third-party systems that send mail from your domain.
- Security requirements, such as conditional access and device policies.
- Training for depot staff and the level of support after cutover.
When comparing, place a realistic estimate of internal time and disruption next to an itemised external quote. Compare like with like.
A middle path
Many logistics companies split the work. A specialist designs the tenant, configures DNS and runs the migration, then your IT person takes over daily administration with documentation and a short handover session. This keeps ownership internal while avoiding the riskiest steps being done for the first time under pressure.
Terms to insist on if you bring in outside help
- Admin ownership: your company holds the global administrator accounts and the domain registrar login.
- Documentation: a written record of mailboxes, groups, policies and DNS records.
- Pilot before cutover: a small group moves first, with a rollback plan.
- Out-of-hours cutover: the switch is planned around dispatch peaks, not during them.
- Itemised quote: users, mailboxes, migration and support shown as separate lines.
- Exit clarity: nothing that prevents you from changing provider later.
Questions to ask before you decide
- Who will manage the tenant when the person who set it up is on leave?
- Which shared mailboxes must never go unattended, and who covers them overnight?
- How will drivers and shift workers sign in securely without a personal phone?
- Which systems send mail as us, and are they all in our SPF record?
- How much old mail do we actually need to carry across?
If the answers are unclear, a short scoping call with an outside team can clarify requirements before you commit to either route.
Why Companies Choose CloudHouse for Google/Outlook Setup
Clients come to CloudHouse because we plan delivery in stages, remain available for support after launch and provide transparent, itemised quotes so you can see what each part costs. We build around your depots and shifts, not a generic template. You can read more on our Google Workspace and Outlook setup service page.
Conclusion
For a logistics company, the choice between in-house and specialist setup comes down to time, risk and continuity. Keep it in-house if you have an experienced administrator, a small footprint and little to migrate. Bring in a specialist, or split the work, if you run several sites, depend on shared dispatch mailboxes or cannot afford a failed cutover. Whichever you choose, insist on MFA that suits shift work, complete MX, SPF, DKIM and DMARC records, and written documentation. To discuss your setup and receive an itemised proposal, visit our Google and Outlook setup service page and request a quote.
