Your sales mailbox fits within 50 GB and has no separate Exchange Online licence. That does not mean it automatically receives every Defender for Office 365 entitlement. Planning protection requires two inventories: protected shared mailboxes and the individual people accessing protected mailboxes. Counting email addresses alone is not enough.
Content reviewed on 18 November 2026, using the current Microsoft Defender service description and licensing FAQs. The model concerns Defender for Office 365 Plan 1, not endpoint protection licensing or every requirement of other security services.
What an unlicensed shared mailbox actually means
Exchange Online limits allow a shared mailbox up to 50 GB without its own Exchange licence when it does not use features requiring additional rights. Accessing users need their own licensed Exchange Online mailboxes. The same documentation explicitly states that advanced features, including Defender for Office 365, require the shared mailbox to be licensed for those features.
There are two separate questions: whether the basic shared mailbox needs its own Exchange licence, and whether you hold rights for specific security features. An automatic recommendation to “add Exchange Online Plan 2” may not answer the second question: that licence alone is not a substitute for Defender for Office 365.
| Requirement | What to record | Insufficient evidence |
|---|---|---|
| Basic shared mailbox up to 50 GB | Size, usage and accessing users' licences | Its address merely exists in the admin centre |
| MDO protection for the shared mailbox | Appropriate entitlement for the protected mailbox | No basic Exchange licence is required |
| A person accessing a protected mailbox | That user's own appropriate entitlement | Another delegate's licence |
| Plan 2 functionality | Scope of advanced features and rights | Plan 1 has been purchased somewhere in the tenant |
Microsoft's Defender requirements
The current Microsoft Defender service description names both groups: users accessing mailboxes benefiting from protection, and shared mailboxes benefiting from protection. Delegates' licences do not automatically cover the shared mailbox, and the reverse is also true.
Microsoft's licensing FAQ also separates creating a basic shared mailbox from obtaining advanced feature rights. “Defender” alone is not a sufficient product name on an order: Defender for Business, Defender for Endpoint and Defender for Office 365 are different products. This article concerns Defender for Office 365, not the antivirus on an employee's computer.
Plan 1 includes Safe Links and Safe Attachments, among other capabilities. Plan 2 adds investigation and automation capabilities. The Defender for Office 365 overview provides the comparison. Determine the need for Plan 2 from actual feature use, rather than assuming every shared mailbox requires the highest plan.
Enabled protection is not a purchased entitlement count
A tenant can provide protection to more recipients than an administrator expects. A mailbox's absence from a custom security policy does not necessarily mean it is unprotected. The preset security policy documentation describes Built-in protection as default Safe Links and Safe Attachments coverage for recipients who are not excluded or covered by higher-precedence policies.
There is an important qualification: for automatically enabled Built-in protection, Microsoft explicitly says customers need not worry about violating licensing terms merely because it is enabled by default. It also recommends purchasing enough licences to continue protection for all users. The presence of a default policy therefore does not justify a categorical conclusion that the customer is in breach.
For planned, documented coverage, still use the service description requirements and establish the actual scope. Default product behaviour does not prove the company purchased the necessary rights. Resolve differences between visible functionality and purchasing records through an inventory and confirmation of the specific SKU, rather than disabling protection to make the spreadsheet smaller.

Model: 30 people and four mailboxes
A hypothetical company has 30 distinct people accessing four shared mailboxes protected by Plan 1 features. Ten have Microsoft 365 Business Premium and twenty have Microsoft 365 Business Standard. The shared mailboxes have no MDO entitlement of their own. The company holds no other licences or trials that change this assessment.
Business Premium covers Plan 1 for those ten users in this model. Business Standard alone does not provide the corresponding Plan 1 right. The four protected shared mailboxes are four further entries. The gap is 20 user entitlements plus four shared-mailbox entitlements, making 24 missing MDO Plan 1 entitlements under the stated assumptions.
| Group | Count | Appropriate Plan 1 right already included | Missing rights in this model |
|---|---|---|---|
| Business Premium users | 10 | Yes, for these users | 0 |
| Business Standard users | 20 | No | 20 |
| Protected shared mailboxes | 4 | No | 4 |
| Total | 30 people + 4 mailboxes | No other subscriptions | 24 |
This table is an entitlement inventory, not a universal purchase order. Before buying, check available standalone SKUs, offer prerequisites, assignment arrangements and existing subscriptions. The same entitlement may be part of a wider suite, in which case it should not be purchased twice.
Do not count access relationships as people. One employee accessing all four mailboxes remains one user. Twenty distinct people accessing one mailbox are twenty people in the user inventory. Multiple aliases for the same mailbox are not separate shared mailboxes.

Check the rights you already own
Before ordering, map invoice product names to actual service plans. The current service description lists Plan 1 not only under Business Premium but also, for example, under Microsoft 365 E3 and Office 365 E3. Older internet advice that “E3 never includes Defender” is therefore not a sound purchasing basis in November 2026.
Do not transfer a user's bundled rights to a separate shared mailbox. In this model, ten Business Premium licences do not cover four additional mailbox entries merely because their holders have Full Access. Nor should the audit stop at Full Access: review actual delegation and how applications and people use the mailbox.
| Check | Evidence | Decision output |
|---|---|---|
| Which mailboxes benefit from MDO | Effective Safe Links / Safe Attachments policies and exclusions | Protected mailbox inventory |
| Who accesses them | Delegation, groups and operational use | Distinct user inventory |
| Which rights already exist | Specific SKUs and service plans | Covered entries without duplicate purchases |
| What extends beyond email | SharePoint, OneDrive, Teams and app protection | Separately assessed additional scope |
| How coverage is evidenced | Purchase records, assignments and review date | Reproducible record, not just a feature screenshot |
Where Safe Attachments also protects SharePoint, OneDrive or Teams, the service description expressly expands requirements to users accessing those services. It similarly addresses Safe Links in Microsoft 365 apps and Teams. The 30-delegate example is therefore not a complete company audit when protection extends elsewhere.
A process that preserves security
- Inventory protected shared mailboxes and effective policies, including Built-in protection, Standard, Strict and custom rules.
- Build a deduplicated list of accessing users. Check group membership and accounts used by integrations.
- Map each mailbox and user to an existing appropriate entitlement. Distinguish Plan 1, Plan 2 and other Defender products.
- Assess other protected services. Confirm missing SKUs, commercial terms and assignment with the licensing supplier.
- Retain the date, evidence and responsible owner. Recalculate after package, delegation or security policy changes.
For size, archiving and employee departures, see our article on shared mailbox licences and archiving. Keep those requirements alongside the security inventory. This avoids purchasing a licence that expands capacity but does not provide the protection you need.
Frequently asked questions
Does a shared mailbox under 50 GB need a Defender licence?
If it benefits from Defender for Office 365 features, the current service description requires an appropriate entitlement. The exemption from a basic Exchange licence up to 50 GB is not an exemption for every advanced feature.
Are the delegates' licences sufficient?
Do not merge the two groups. Microsoft names both accessing users and protected shared mailboxes. Your records need appropriate coverage for every relevant entry, taking account of rights already included.
Does automatic Built-in protection mean a licensing breach?
That conclusion cannot be drawn simply from default enablement. The policy documentation explicitly reassures customers while recommending sufficient licences for continued protection. Check current licensing requirements and purchasing records for the planned scope.
Must I buy Exchange Online Plan 2 or the entire E5 suite?
Not automatically. It depends on the features and offer. For an MDO Plan 1 entitlement, check an appropriate standalone licence or suite containing it. Exchange capacity and archiving are separate decisions.
Is one delegate counted four times for four mailboxes?
No. Deduplicate people in the user inventory. Four separate protected shared mailboxes are four mailbox entries, but one person with four access relationships remains one user.








