License & Subscription Issues

Use Microsoft 365 Shared Mailboxes in Compliance With Licensing

Algirdas JasaitisAlgirdas Jasaitis Nov 20, 2026 868 views

Question details

Determine how to use converted or existing shared mailboxes in compliance with Microsoft 365 licensing requirements.

Use Microsoft 365 Shared Mailboxes in Compliance With Licensing
Product
Microsoft 365 and Exchange Online
Device & OS
not provided
Scenario
An organization wants staff to access departmental or converted mailboxes without using shared mailboxes as substitutes for licensed user accounts.
Observed behavior
A converted mailbox may remain technically accessible as a shared mailbox, but access alone does not establish licensing compliance.
Before you start

Identify the users who need access, their assigned licenses, and the purpose and size of each shared mailbox. Check whether any shared mailbox uses features such as an online archive that may require its own license.

Solution 1Recommended

Use licensed accounts and delegated access for shared mailboxes

Use this approach for reception, support, or departmental addresses accessed by multiple staff members.

1
Check user licenses

In the Microsoft 365 admin center, go to Users > Active users. Select each person who needs access and review Licenses and apps to confirm they have an appropriate Exchange Online license.

2
Review the shared mailbox

In the Exchange admin center, go to Recipients > Mailboxes and select the shared mailbox. Confirm that it serves a shared purpose rather than replacing an individual user's licensed mailbox.

3
Assign mailbox permissions

Open the shared mailbox's delegation settings and add the appropriate users under Read and manage and, if needed, Send as or Send on behalf.

4
Access through delegation

Have each user sign in with their own licensed account and open the shared mailbox in Outlook. Do not rely on direct access to an unlicensed converted account as a way to avoid user licensing.

Check mailbox-specific licensing: A shared mailbox generally does not need its own license if it stays within applicable limits and does not use features that require one. Additional licensing may be needed for a mailbox over 50 GB or for certain features, such as an online archive. Check current Microsoft licensing terms for your plan.
Free Microsoft Office alternative

Work with shared mailbox attachments in WPS Office

WPS Office is a free, lightweight alternative for working with documents received through a shared mailbox. Its familiar interface and Microsoft Office format support make it easier to move existing files into your workflow. WPS does not replace Exchange Online or resolve Microsoft 365 licensing requirements.

Edit documents and spreadsheets received as shared mailbox attachments.Compatible with Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTX.Familiar interface makes it easier to transition from Microsoft Office.Free, lightweight tools for everyday document work.
microsoft office alternative - wps office

Frequently Asked Questions

Does a shared mailbox need its own Microsoft 365 license?

Generally, a shared mailbox does not need its own license if it remains within applicable limits and does not use features requiring one. A mailbox over 50 GB or one using an online archive may require additional licensing; check Microsoft's current terms for your plan.

Do people who access a shared mailbox need licenses?

Yes. Users accessing an Exchange Online shared mailbox need appropriate licenses. In the Microsoft 365 admin center, check each user's assignment under Users > Active users > Licenses and apps.

Can I use a converted shared mailbox as an individual's unlicensed mailbox?

No. Continued technical access does not make that use compliant. Assign the individual an appropriate license and use shared mailboxes for shared functions through delegated access.

How do I give someone access to a shared mailbox?

In the Exchange admin center, go to Recipients > Mailboxes, select the shared mailbox, and use its delegation settings to add the user. Assign Read and manage and any required sending permissions.