Add to Preferred Sources
Microsoft 365 shared mailbox setup lets multiple staff members read, reply to, and send from a single email address — such as info@yourcompany.co.za or support@yourcompany.co.za — without sharing a password or buying an extra licence. If you are building out your business's professional online infrastructure alongside a website for your South African business, a shared mailbox is one of the most practical tools to deploy first.
It routes customer enquiries to whoever is available and keeps every reply visible to the team. This guide covers the exact steps from the Microsoft 365 admin centre, which permission level to assign each team member, post-creation settings that most admins miss, and the POPIA access-control requirements that apply once customer emails live in a shared inbox.
A shared mailbox is not a separate account you log into — it is a mailbox your team members access through their own Outlook licences. When you set up shared mailbox Microsoft 365 accounts correctly, each member keeps their existing login and licence; the shared inbox simply appears as an additional folder.
No extra licence is required for the shared mailbox itself (up to 50 GB of storage), which makes it the most cost-efficient way to manage a team email address in a small or medium South African business.
Quick Answer
A microsoft 365 shared mailbox setup is straightforward in the Microsoft 365 admin centre: navigate to Teams & Groups → Shared mailboxes → Add, name the mailbox, add members, and assign Full Access plus Send As permissions. No additional licence is required for the shared mailbox itself (up to 50 GB); every member who accesses it needs their own licensed Exchange Online mailbox. A Business Basic, Standard, or Premium plan all qualify — but Microsoft 365 Apps for Business does not include email and will not work.
Jump to a Section
What a Team Inbox Is and When You Need One
Plan Requirements and Licensing
Which Permission Level to Grant
Not sure whether a shared mailbox or an alias is right for your setup?
Send us your current email structure and we will map out which option fits your team size and workflow — no obligation.
Get a Free Setup ReviewWhat a Team Inbox Is and When Your Business Needs One
A Microsoft 365 shared mailbox is a single email address managed collectively by a defined group of staff, where every team member sees the same messages and replies using the shared address rather than their personal one.
It solves a specific problem: customers who email info@yourbusiness.co.za should reach someone, and that someone's reply should look like it came from the business, not from an individual employee's address. Common use cases for South African businesses include:
- Customer enquiries — info@, hello@, or enquiries@
- Support and helpdesk — support@, help@, or service@
- Accounts and invoicing — accounts@, invoices@, or finance@
- Reception and bookings — bookings@, reservations@, or reception@
Every shared mailbox also comes with a shared calendar, which your team can use to log appointments and client visits visible to all members.
Key point: A shared mailbox is for internal teams only. External users — anyone with a Gmail, Outlook personal, or non-company email address — cannot be granted access. If you need external collaborators in the same inbox, a Microsoft 365 Group is the correct alternative.
Plan Requirements and Licensing — Before You Begin
You need a Microsoft 365 plan that includes Exchange Online to create a shared mailbox — and the shared mailbox itself requires no additional licence for storage up to 50 GB.
Note on "Office 365": Microsoft rebranded Office 365 to Microsoft 365 in 2020, but many South African admins and resellers still use the old name. If you are searching how to create shared mailbox Office 365, the process is identical — the admin centre path and options are the same under both names.
The most common plan confusion for South African SMEs: Microsoft 365 Apps for Business does not include email. It provides desktop Office apps and OneDrive but not Exchange Online. If your team is on Apps for Business and you try to create a shared mailbox, the option will not appear. You need Business Basic, Standard, or Premium.
| Plan | USD/user/mo (annual, July 2026) | ~ZAR/user/mo* | ~ZAR incl. 15% VAT | Shared Mailbox |
|---|---|---|---|---|
| Apps for Business | See microsoft.com/en-za | — | — | ✗ No email included |
| Business Basic | $7.00 | ~R115 | ~R132 | ✓ Yes |
| Business Standard | $14.00 | ~R230 | ~R264 | ✓ Yes |
| Business Premium | $22.00 | ~R361 | ~R415 | ✓ Yes |
*ZAR figures converted at the SA Digital Cost Index (SADCI) rate of R16.42/USD (Aug 2026 index assumption), not a live market rate. The prevailing ZAR/USD rate at your time of purchase will differ, and actual rand costs are likely to be higher than these figures suggest. Microsoft publishes pricing in USD; your Cloud Solution Provider partner converts at the prevailing rate, and 15% VAT applies to South African invoices. Treat these as a directional floor and request a current quote from your CSP for the exact rand amount.
The shared mailbox's own storage is free up to 50 GB. If your team archives heavily and crosses that threshold, you will need to assign an Exchange Online Plan 2 licence to the mailbox to expand it to 100 GB. Litigation hold and in-place archiving also require Plan 2 or Plan 1 with the Exchange Online Archiving add-on.
Who can create a shared mailbox? You need the Exchange Admin role in Microsoft 365. The Global Admin role also has this permission. A standard user or even a Teams admin cannot create one — you need to confirm your role in the admin centre before starting.
How to Complete a Microsoft 365 Shared Mailbox Setup in Six Steps
Setting up a shared mailbox in the microsoft 365 shared mailbox setup flow takes six steps in the admin centre: create the mailbox, add members, assign Full Access and Send As permissions, then configure sent-items visibility, automatic replies, and forwarding before going live. The steps below follow Microsoft's official admin documentation, updated February 2026.
Sign in to the admin centre. Go to admin.microsoft.com and sign in with your Exchange Admin or Global Admin account. If you see "You don't have permission to access this page," your account does not have the required admin role.
Navigate to Shared mailboxes. In the left navigation, select Teams & Groups → Shared mailboxes. If you do not see Teams & Groups, select Show all first to expand the navigation.
Create the mailbox. Select + Add a shared mailbox. Enter a display name (for example, "Customer Support" or "Accounts"). Microsoft will suggest an email address based on the name — edit it if needed, then select Save changes. Allow a few minutes for the system to provision the mailbox before you can add members.
Add members. Under Next steps, select Add members to this mailbox, then Add members. Search for and select each staff member who should access the inbox. Select Add, then close the panel. Members are the people who will read incoming mail and send replies from this address.
Assign permissions. By default, adding members grants Full Access. If you also want team members to send mail as the shared address (rather than on behalf of it), go to the Exchange admin centre → Recipients → Mailboxes → select the shared mailbox → Manage mailbox delegation → add Send As permission for each member. Both Full Access and Send As are required for most shared inbox use cases.
Open in Outlook. With automapping on by default, team members simply close and restart Outlook — the shared mailbox appears automatically in their left sidebar. If automapping is disabled in your organisation, members open Outlook → File → Account Settings → Account Settings → Change → More Settings → Advanced → Add, and enter the shared mailbox email address.
Sign-in is blocked by default. Every new shared mailbox has a system-generated password and direct sign-in disabled. Do not attempt to sign in directly with the shared mailbox address — it is not intended for that purpose and keeping sign-in blocked is the correct security configuration.
Which Permission Level Should You Grant Each Team Member?
For most shared inboxes, assign Full Access plus Send As to every team member — Full Access opens the inbox and lets members read, move, and delete messages; Send As lets them reply as the shared address rather than their personal one. Getting Microsoft 365 shared mailbox permissions wrong is the most common setup mistake, and it leads directly to replies landing in the wrong sent folder or appearing from an individual's name instead of the shared address.
| Permission | What It Allows | How Replies Appear | Best For |
|---|---|---|---|
| Full Access | Open the mailbox, read/delete/move emails, create calendar items | Cannot send email on its own | Read-only monitors; agents who reply through Send As |
| Send As | Send email that appears to come directly from the shared address | "From: support@company.co.za" | Customer-facing teams where branding consistency matters |
| Send on Behalf | Send email showing both the agent and the shared address | "Thabo on behalf of support@company.co.za" | Teams where individual accountability is important (e.g., accounts) |
For most South African customer service or enquiries inboxes, assign both Full Access and Send As to every team member. Full Access alone lets them read email but not reply from the shared address. Send As alone grants no inbox access. Together, they create a complete shared inbox experience.
Practical scenario: Your reception team at a Johannesburg property agency handles all bookings@ emails. Assign Full Access + Send As. Clients see replies from "bookings@agencyname.co.za" — the individual agent's name never appears. The team shares accountability without exposing personal addresses.
Common mistake: Granting only Full Access and assuming team members can reply. They can read every email but clicking Reply will default to their personal address. Clients then receive replies from a personal name@company.co.za, defeating the purpose of the shared inbox entirely.
Note on automapping and security groups: Microsoft's automapping feature (which adds the shared mailbox to Outlook automatically) works only when permissions are assigned to individual users, not to security groups. If you grant Full Access to a security group for easier management, members will need to add the shared mailbox manually.
Post-Creation Admin Settings to Configure Before Going Live
Four Microsoft 365 shared mailbox settings — sent-items visibility, automatic replies, email forwarding, and global address list appearance — are off or misconfigured by default and must be reviewed before the shared mailbox goes live. All four sit one level deeper in the admin centre than the creation flow, which is why most first-time setups miss them.
1. Sent items visibility. By default, replies sent from the shared mailbox are saved to the individual sender's Sent Items folder, not to the shared mailbox. This means no other team member can see what was already replied to. Go to Admin centre → Teams & Groups → Shared mailboxes → select the mailbox → Edit under "Sent items" → enable saving to the shared mailbox's Sent Items. This single setting prevents duplicate replies to the same customer.
2. Automatic replies. Set an out-of-office or business-hours acknowledgement: Shared mailboxes → select the mailbox → Edit under "Automatic replies" → enable and enter your message. You can configure different replies for senders inside and outside your organisation. Text only — images are not supported in this interface.
3. Email forwarding. If your team needs notifications in a separate tool (a WhatsApp group, a CRM, or a personal address for after-hours cover), configure forwarding: Edit under "Email forwarding" → enter the destination address or distribution group. No additional licence is required to forward from a shared mailbox.
4. Global address list visibility. By default, the shared mailbox appears in your organisation's global address list (GAL), which means staff can find it when composing internal emails. If you want to keep it internal-only and hide it from the GAL, edit the "Show in global address list" setting. Be aware: hiding it also prevents new members from adding it to Outlook via the address book — they will need the exact email address instead.
Setting up M365 for a growing team and need the configuration done correctly the first time?
Share your team size and workflow with us — we will give you a timeline and fit assessment for a full Microsoft 365 setup including shared mailboxes, DNS configuration, and email migration.
Get a Timeline AssessmentPOPIA and Access Control — What SA Businesses Must Know
A shared mailbox that handles customer enquiries processes personal information, which means your configuration choices carry direct obligations under the Protection of Personal Information Act (POPIA).
POPIA's accountability principle makes your business — as the responsible party — accountable for personal information held in your mailboxes, regardless of where the data is physically stored. Microsoft holds data processing agreements with Microsoft 365 customers, which satisfies the operator-agreement requirement under POPIA section 21. Microsoft has established data centres in Johannesburg and Cape Town for Exchange Online. To confirm your tenant's actual data location before relying on data residency for POPIA section 72 compliance, check Settings → Org settings → Organisation profile → Data location in your Microsoft 365 admin centre.
What this does not resolve is your own access-control discipline. The checklist below captures the access-control requirements that apply specifically to shared mailboxes:
POPIA Access-Control Checklist for Shared Mailboxes
- ☐ Limit membership to authorised staff only. Every member can read all messages in the inbox, including those containing ID numbers, payment details, or health information. Grant access on a need-to-know basis.
- ☐ Remove access immediately when a staff member leaves. In the admin centre, removing a departed employee's user licence also removes their access to any shared mailboxes they belonged to — but verify this in the shared mailbox member list, since orphaned permissions have been found in M365 environments.
- ☐ Document who has access and why. POPIA's accountability principle requires you to be able to demonstrate that access controls were in place. A simple spreadsheet — member name, role, date granted, date removed — is sufficient for most SMEs.
- ☐ Do not use the shared mailbox account to sign in. The system-generated password and blocked sign-in status are a security control. Resetting the password and signing in directly bypasses your audit trail.
- ☐ Note the encryption limitation. Microsoft's own documentation confirms that email sent from a shared mailbox cannot be encrypted using per-user keys, because the mailbox has no individual security context. If your shared inbox handles sensitive personal information that requires end-to-end encryption, a standard shared mailbox is not the right tool — consider Microsoft Purview Information Protection with appropriate licensing.
For a broader look at how email migration to Microsoft 365 works in the South African context, the IMAP migration guide for South African businesses covers DNS configuration, MX record cutover, and what to test before going live.
Why South African Businesses Choose Growth Pulse Media
Growth Pulse Media was built out of firsthand experience running and scaling a South African ecommerce business — which means the team understands what it actually costs to configure business tools wrong and fix them under time pressure. Shared mailbox setup is one of those tasks that looks simple and becomes complicated the moment you hit a DNS record conflict, a permissions replication delay, or an employee's laptop that didn't get the new Outlook profile.
We handle Microsoft 365 configuration as part of the broader digital infrastructure work we do for South African businesses: website design, email setup, and the integrations that make a professional online presence work as a system rather than a collection of disconnected tools.
If you are evaluating whether a custom-built or professionally designed website should sit alongside your Microsoft 365 environment, our team works both sides of that equation. All work is executed in-house — no offshore contractors, no junior handoffs — and we keep a limited client roster so that senior attention stays on every project.
The email alias vs shared mailbox comparison is also worth reading if you are still deciding which structure fits your team — it covers the decision criteria in detail, including the cases where an alias is the simpler and more practical choice for a solo operator or very small team.
Who This Is NOT For
Teams of more than 25 concurrent users. Microsoft's documentation states that a shared mailbox supports a maximum of 25 users accessing it simultaneously; above that threshold, members may experience connection failures or duplicated messages. If your customer support team exceeds this, a Microsoft 365 Group or a dedicated helpdesk platform is the better structure.
Businesses on Microsoft 365 Apps for Business only. This plan provides desktop Office apps and OneDrive but does not include Exchange Online, which means the shared mailbox option does not exist in your admin centre. You need to upgrade to Business Basic, Standard, or Premium before proceeding.
Teams that need external collaborators in the same inbox. Only people inside your organisation — those with a licensed seat on your Microsoft 365 tenant — can be added as shared mailbox members. A freelancer, agency partner, or supplier with a Gmail or external address cannot access it. A Microsoft 365 Group or a tool like Freshdesk is the alternative for external collaboration on a shared inbox.
High-volume support operations needing ticket tracking. A shared mailbox has no native ticketing, SLA tracking, or routing rules beyond basic email rules. If your team receives hundreds of customer emails a day and needs accountability at the ticket level, a dedicated customer support platform — Zendesk, Freshdesk, or Zoho Desk — is a better investment than configuring Microsoft 365 to approximate that functionality.
Not sure whether your current email setup is costing you customer enquiries?
Send us your current inbox structure and we will audit it for gaps — routing failures, reply delays, access-control risks — at no cost.
Request a Free Email AuditFrequently Asked Questions
Does a shared mailbox in Microsoft 365 need a separate licence?
No — a shared mailbox does not require its own licence for storage up to 50 GB, according to Microsoft's official documentation. Every team member who accesses the shared mailbox must have their own licensed Exchange Online mailbox (any Business plan that includes email qualifies). An Exchange Online Plan 2 licence is only needed if the shared mailbox's storage exceeds 50 GB, if you need in-place archiving, or if the mailbox is placed on litigation hold.
How many people can use a Microsoft 365 shared mailbox?
Microsoft's documentation states that a shared mailbox works reliably for up to 25 concurrent users; above that number, members may encounter connection failures or see duplicated messages. You can add more than 25 members, but simultaneous access beyond that limit is where performance degrades. For larger teams, Microsoft recommends using a Microsoft 365 Group instead.
Why can't my team members send email from the shared mailbox address?
Full Access permission alone lets users read and manage email in the shared mailbox, but it does not grant the ability to send from the shared address. To send as the shared mailbox (so replies appear from info@yourcompany.co.za rather than the individual's address), you need to add Send As permission separately in the Exchange admin centre under Recipients → Mailboxes → the shared mailbox → Manage mailbox delegation.
Will the shared mailbox appear automatically in Outlook after I add a member?
Yes — with automapping enabled (the default in most Microsoft 365 organisations), the shared mailbox appears in the team member's Outlook left sidebar after they close and reopen Outlook. Automapping only works when permissions are assigned to individual users directly, not to a security group. If your organisation has disabled automapping, members need to add the mailbox manually via File → Account Settings → [select the account] → Change → More Settings → Advanced → Add, and enter the shared mailbox email address.
Can I create a shared mailbox if my business uses Google Workspace instead of Microsoft 365?
No — Microsoft 365 shared mailboxes are specific to Microsoft's Exchange Online platform. Google Workspace has its own equivalent called a Collaborative Inbox (in Google Groups), which provides similar functionality within the Google ecosystem. If you are weighing which platform suits your SA business, the Google Workspace vs Microsoft 365 comparison covers the decision factors including pricing and local support.
Get Your Microsoft 365 Environment Set Up Correctly the First Time
Growth Pulse Media configures Microsoft 365 environments for South African businesses — shared mailboxes, DNS records, email migration, and the integrations that make it all work together. All work is executed in-house by senior operators with hands-on experience in SA business infrastructure. No obligation — we will get back to you within 24 hours.
Book a Free Consultation