Is sharing email passwords a security risk for my business?
Summary
This guide helps you troubleshoot and resolve: Is sharing email passwords a security risk for my business?. Follow the steps below to fix the issue.
Common Causes
Sharing a single email password for general addresses like accounts@ or sales@ is a common practice in small businesses, but it introduces serious security and accountability risks. When multiple staff members use the same credentials, you cannot track who sent or deleted a message, access cannot be quickly revoked when someone leaves the organisation, and a single compromised password puts every shared mailbox at risk. Moving to Microsoft Exchange Online shared mailboxes with individual user accounts and multi-factor authentication (MFA) removes these vulnerabilities while keeping your general enquiry addresses accessible to the right people.
Before beginning migration, small businesses should review their Australian Privacy Act obligations regarding the handling and storage of email data, particularly where personal information is involved. Consider data residency requirements and ensure your Microsoft 365 tenant is configured appropriately for your organisation's needs.
Quick Fix Steps
- Assign Microsoft 365 licences with Exchange Online to every staff member who needs email access. Individual users require licences; shared mailboxes do not require their own licence.
- Create individual user mailboxes for each employee instead of sharing one login.
- Set up shared mailboxes for
accounts@,sales@, and other general addresses. - Grant Send As or Send on Behalf permissions to relevant staff.
- Enable multi-factor authentication for every individual user account.
- Remove old shared account credentials from mobile phones and email clients. Disable or delete the old shared password and block legacy IMAP/POP3 authentication where possible.
Detailed Instructions
Create individual user accounts
- Sign in to the Microsoft 365 admin centre with an administrator account.
- Go to Users > Active users.
- Select Add a user and complete the details for each staff member.
- Assign an Exchange Online licence to each user during creation.
- Instruct each user to set up their own password and register for multi-factor authentication at
https://account.microsoft.com/securityor through their Microsoft account security settings.
j.smith@yourdomain.com.au) rather than logging into a shared generic address.Create shared mailboxes
- In the Microsoft 365 admin centre, go to Teams & groups > Shared mailboxes.
- Select Add a shared mailbox.
- Enter the name and email address (for example,
sales@yourdomain.com.au). - Select Save changes.
- Once created, select the shared mailbox to manage members and permissions.
Convert existing shared mailbox data
- If you already have shared mailboxes in Exchange Online that contain data from a previous system, use the Exchange admin centre or a third-party migration tool to import existing mail, contacts, and calendar items.
- Map legacy mail folders to the corresponding folders in the Exchange Online shared mailbox to preserve message history.
- Verify that all data has migrated successfully before decommissioning the source mailbox.
Assign access and send permissions
- Open the shared mailbox you created.
- Under Members, select Edit to add the staff members who need to view the mailbox.
- Under Send as or Send on behalf, select Edit to add users who should be able to send email from the shared address.
- Send as makes the email appear as though it came directly from the shared mailbox.
- Send on behalf shows
User on behalf of sales@yourdomain.com.auin the From field. - Select Save changes.
Enable multi-factor authentication
- In the Microsoft 365 admin centre, go to Users > Active users.
- Select Multi-factor authentication.
- Select each user and enable MFA.
- Users will be prompted to register their phone or authenticator app at next sign-in.
Migrate existing email and stop using shared logins
- Export mail, contacts, and calendars from the old shared IMAP/POP3 or cPanel webmail account.
- Import the data into the corresponding shared mailbox or individual user mailboxes in Exchange Online.
- Update DNS MX records to point to Microsoft Exchange Online so new mail is delivered to the new platform.
- Change the password on the old shared account and disable it, or decommission the legacy mailbox entirely.
- Tell staff to remove the old shared account from their mobile phones and email clients, and add their individual Exchange Online account instead.
Additional Recommendations
- Use centralised email signatures through Exchange Online transport rules or a third-party signature manager so all staff, including those sending from shared mailboxes, present a consistent brand.
- Share calendars from the shared mailbox or individual calendars so teams can coordinate appointments without sharing login credentials.
- Configure SPF, DKIM, and DMARC records for your domain to reduce the chance of your emails landing in recipients' junk folders.
- Review shared mailbox membership quarterly and remove access for staff who no longer need it.
- Block legacy authentication protocols (IMAP, POP3, SMTP AUTH) in Exchange Online to prevent older apps from bypassing MFA.
Troubleshooting
Staff cannot see the shared mailbox in Outlook
- Ensure the user has been added as a member of the shared mailbox and that permissions have had time to replicate (this can take up to 60 minutes).
- Ask the user to restart Outlook or Outlook on the web.
- In Outlook for Windows, check File > Account Settings > Account Settings and confirm the correct Exchange profile is loaded.
Emails sent from the shared mailbox are going to junk
- Verify that SPF, DKIM, and DMARC are correctly configured for your domain.
- Ensure the sending user has Send as or Send on behalf permission, not just folder access.
- Ask recipients to add your domain to their safe senders list if the issue persists.
A former employee can still access the shared mailbox
- Remove the former employee's user account from the shared mailbox Members list immediately.
- Disable or delete the former employee's individual Microsoft 365 account.
- If the former employee knew the old shared password, change it and ensure no one is logging into the shared mailbox directly.
Sent items from shared mailbox not saved in shared Sent Items folder
- By default, messages sent with Send as permissions are saved in the sender's personal Sent Items folder, not the shared mailbox's Sent Items folder.
- To change this behaviour, an administrator must enable the MessageCopyForSentAsEnabled or MessageCopyForSendOnBehalfEnabled setting on the shared mailbox using Exchange Online PowerShell.
- After enabling the setting, it may take up to 24 hours for newly sent items to appear in the shared mailbox Sent Items folder.
Users have send permissions but cannot send from shared mailbox
- Confirm the user has both Full access and Send as or Send on behalf permissions assigned. Full access alone does not grant sending rights.
- Ask the user to restart Outlook or Outlook on the web to refresh permissions.
- Check whether the user's account is blocked from sending mail in the Microsoft 365 admin centre under Users > Active users.
- Verify there are no transport rules or mail flow policies blocking messages sent from the shared mailbox address.
If you need assistance migrating from shared logins, cPanel webmail, or legacy IMAP/POP3 to Microsoft Exchange Online shared mailboxes, Open a Ticket and our team will help you get it sorted.
Still Having Issues?
💻 Open a Ticket