Does a PHP Script Need a License to Access an Exchange Online Shared Mailbox?
Question details
Determine whether a PHP script that sorts incoming mail in an Exchange Online shared mailbox needs an additional license.

- Product
- Exchange Online shared mailbox
- Device & OS
- not provided
- Scenario
- A company server runs a PHP script that manages incoming messages in a shared mailbox. Users already have licensed personal mailboxes.
- Observed behavior
- The user wants to know whether the script or its access to the shared mailbox requires a separate license.
Identify how the script connects to Exchange Online, including its API and whether it uses a user account or an application identity. Check the shared mailbox size and whether it uses features such as archiving or litigation hold.
Check Shared Mailbox Licensing and the Script's Access Method
Use this approach to determine whether the mailbox, an accessing account, or a required feature needs a license.
The PHP language itself does not determine Exchange Online licensing. A shared mailbox generally does not need its own license for basic use within Microsoft's published limits, but the applicable requirements depend on its features and how the script accesses it.
Licenses assigned to users' personal mailboxes do not automatically answer whether the shared mailbox or the script's access method has additional requirements.
Inspect the PHP script's configuration or ask the developer which API it uses and whether it authenticates as a user or as an application.
In the Exchange admin center, open Recipients > Mailboxes and select the shared mailbox. Check its size and whether it uses features such as an archive or litigation hold.
Review Microsoft's current Exchange Online shared mailbox licensing documentation. Check the requirements for the mailbox's size and enabled features; for example, a shared mailbox generally needs a license if it exceeds the unlicensed 50 GB limit.
Ask your Exchange administrator or Microsoft support to verify licensing and permissions for the specific authentication method. If the script uses Microsoft Graph, review its delegated or application permissions and any required administrator consent.

Use WPS Office for Everyday Office Documents
WPS Office is a free, lightweight alternative for working with Office documents in a familiar interface, making it easy to move existing files. It does not replace Exchange Online or resolve shared mailbox licensing.

Frequently Asked Questions
Does writing the automation in PHP create a separate Exchange license requirement?
Not by itself. Review the shared mailbox's features and the account or application identity used by the script to determine the applicable licensing and access requirements.
Does a shared mailbox always need its own license?
No. A shared mailbox generally does not need its own license for basic use within Microsoft's published limits. Check current Microsoft documentation if it exceeds 50 GB or uses additional features such as archiving or litigation hold.
Are licensed users enough to authorize the script?
Not necessarily. The script also needs appropriate access permissions. Ask an Exchange administrator to review its user or application identity and the permissions for its connection method.
Where can I get help with the script's authentication?
Start with your Exchange administrator and the Microsoft documentation for the API used by the script. For implementation questions, consult Microsoft developer support or the relevant Microsoft developer community.




