A shared or delegated mailbox is different from your own Office 365 account — it's a second mailbox (a team inbox, a manager's calendar, a departmental address) that your Exchange admin has granted you permission to access, on top of your normal login.
Shared mailboxes are not supported
BlueMail supports individual accounts only — mailboxes you sign in to with their own email address and credentials. Shared and delegated Office 365 mailboxes, where access is granted to your personal login rather than through a sign-in of their own, cannot be added to BlueMail. There is no "add a shared mailbox" flow, and delegated permissions on your personal account do not make the shared mailbox appear in the app.
Your own Office 365 account still works as usual: BlueMail can auto-detect it as a device account, or you sign in through the Microsoft consent screen. See Adding an Exchange Account for the setup steps.
Your options instead
- Ask your admin whether the mailbox can have its own sign-in. Some organizations enable direct sign-in on a shared mailbox, giving it its own password. At that point it is effectively an individual account, and you can add it to BlueMail the normal way: Settings | Accounts | Add Account, entering the shared mailbox's own email address and credentials.
- Use Outlook or Outlook on the web for the shared mailbox. Delegated access without separate credentials is a Microsoft-side feature, and Microsoft's own apps are where it works. You can keep your personal account in BlueMail alongside.
Check with your admin
Because shared and delegated mailbox permissions are configured on the Exchange/Office 365 side, your IT admin is the best source for confirming exactly what access you have and whether the mailbox can be given its own sign-in.
