Let's Connect

AI powered platforms built for real-world impact.

Insights 6 min read

How to Secure Shared Mailboxes Without Gaps

Sharktech Global

Sharktech Global

Insights Team
How to Secure Shared Mailboxes Without Gaps

A shared mailbox should never be a shared password. To secure shared mailboxes, give each person access through their own work account, enforce multi-factor authentication, review permissions regularly and keep an audit trail of what happened.

That matters because mailboxes such as accounts@, payroll@, bookings@ and reception@ often hold customer records, invoices, bank-change requests and private staff information. They are useful operational tools, but they can become an easy path into the business when access is broad, unmanaged or left behind after a staff member leaves.

How do you secure shared mailboxes in Microsoft 365?

Secure a shared mailbox by assigning delegated access to named user accounts, not by sharing the mailbox password. Disable direct sign-in, require MFA on every user account, grant only the permissions each person needs and review access at least every quarter. These controls make activity traceable and reduce exposure.

In Microsoft 365, a shared mailbox normally does not need its own licence or login. Staff open it through Outlook using their own identity. This is the correct model because Microsoft can record who sent, deleted or moved a message.

Do not convert the mailbox into a regular user mailbox simply so multiple people can sign in as accounts@company.com. That removes accountability. It also means MFA may be approved on one mobile while several people know the password.

For each shared mailbox, decide whether a user needs Full Access, Send As or Send on Behalf. Full Access lets them read and manage messages. Send As lets them send as the mailbox. Send on Behalf visibly identifies the individual sender. Most customer-facing inboxes need Full Access and Send As for a small group. Finance and payroll mailboxes should be tighter.

Which shared mailbox permissions should staff receive?

Give staff the least access that lets them do their job. Reception may need to read and reply to enquiries, while a manager may only need visibility. Keep Send As limited for finance, payroll, executive and supplier-facing mailboxes, where an impersonated message can create a payment or privacy risk.

A workable permission model looks like this:

| Mailbox type | Typical access | Extra control | | --- | --- | --- | | reception@ or enquiries@ | Full Access and Send As for the service team | Review access when rosters change | | accounts@ | Full Access for accounts staff, Send As for approved staff only | Separate payment approvals from inbox access | | payroll@ or hr@ | Named HR or payroll users only | Quarterly manager review | | directors@ or executive@ | Very small delegate group | Alert on forwarding rule changes | | bookings@ | Team access tied to the role | Remove access immediately on departure |

Avoid giving everyone access because they may need it one day. Broad access makes handovers easier in the short term, but it increases the chance of an accidental deletion, a privacy mistake or an invoice scam being missed. If coverage is the concern, create a role-based group with two or three trained people instead.

Do shared mailboxes need multi-factor authentication?

Yes, but MFA belongs on every person who can open the mailbox, not on the shared mailbox itself. Shared mailboxes should not be used for direct sign-in. Conditional Access can also require stronger checks when staff access Microsoft 365 from an unmanaged device or unfamiliar location.

MFA is not a complete answer to email fraud. A criminal who takes over a staff member's session may still read the inbox or create forwarding rules. Pair MFA with phishing-resistant sign-in methods where practical, such as Microsoft Authenticator number matching or passkeys, and train staff to verify unusual requests outside email.

This is especially relevant for accounts teams. A supplier may appear to request new bank details from a genuine-looking mailbox. The safe process is not to reply to the message or use the phone number in its signature. Confirm the change using an existing, independently verified contact record.

What settings stop shared mailbox data leaking?

Block automatic external forwarding, monitor inbox rule changes, restrict mobile access where needed and apply retention rules that match your business process. These settings reduce common leakage paths without stopping staff from doing normal work.

External forwarding is a frequent issue. An employee may set it up for convenience, or an attacker may create a hidden rule after compromising an account. In either case, customer messages can be copied outside your control. Allow exceptions only when there is a documented business reason and a manager has approved it.

You should also consider whether staff need access on personal mobiles. For a general enquiries inbox, mobile Outlook with MFA may be reasonable. For payroll, legal, clinical or sensitive NDIS records, access may need stronger device management or be limited to approved work devices. The right setting depends on what the mailbox contains and how staff work.

Retention is another trade-off. Keeping every message forever can increase the amount of data exposed in an incident. Deleting messages too quickly can damage customer service, record keeping or a dispute response. Set a retention period based on your operational needs, then make sure staff know where final records should live.

How often should you review shared mailbox access?

Review access every three months, and immediately after a staff departure, role change, extended leave or contractor engagement ends. The review should be owned by the business manager responsible for the mailbox, not left as an assumed IT task.

A short review is usually enough. Export the member list, ask the mailbox owner to confirm each person still needs access, remove anyone who does not, and record the decision. Check for unusual forwarding rules and delegates with Send As permission at the same time.

Offboarding needs to happen on the employee's final working day, not at the next monthly IT check. Disable the person's work account, revoke active sessions and remove them from mailbox groups. If they used a personal mobile, remove company data through your approved mobile management process where available.

What audit logs should you keep for shared mailboxes?

Keep Microsoft 365 audit logging enabled and know who can search it. Audit records help you investigate deleted messages, unexpected forwarding rules, suspicious sends and access concerns by showing the named account behind the action.

Logs are useful only if you can act on them. Define who receives alerts for high-risk changes, such as mailbox forwarding enabled, new inbox rules, suspicious sign-in activity or a new delegate added to payroll@. For a small business, that may be the practice manager and an external IT contact.

Sharktech Global helps Australian businesses set these controls in Microsoft 365 as part of practical cybersecurity and managed IT work. The aim is not to bury an office manager in settings. It is to document who owns each mailbox, apply the right controls and make access reviews routine.

Sharktech Global is based in Liverpool, Sydney, with an office in South Yarra, Melbourne. Most work is delivered remotely, which suits businesses that need clearer Microsoft 365 security without employing an in-house IT team.

Frequently asked questions

Can several people send from one shared mailbox?

Yes. Give named users Send As permission and use their own Microsoft 365 accounts. Do not share the mailbox password or let staff sign in directly as the shared mailbox.

Should former staff emails stay in a shared mailbox?

Usually, yes, for a defined period if the messages are needed for customer service or records. Remove the former employee's access first, then set an appropriate auto-reply and delegate new messages to the right team.

Can a shared mailbox be accessed on a mobile?

Yes, if the business allows it. Require MFA and use the Outlook app. For sensitive mailboxes, consider approved and managed devices only.

Does a shared mailbox protect us from phishing?

No. It improves accountability when configured properly, but staff can still receive fraudulent messages. Use MFA, email fraud protection, forwarding controls and a clear verification process for payment or data requests.

Who should own a shared mailbox review?

The business owner or manager responsible for that function should approve access. IT can run the report and apply changes, but it cannot reliably decide who still needs payroll, finance or customer data.

Can Sharktech Global review our shared mailbox setup?

Yes. We can check permissions, MFA, forwarding, audit settings and offboarding steps, then scope and price the required work up front. Book a free 30 minute call and we will tell you whether we are the right fit.