Can I Keep My Current Email Address When Moving to Microsoft 365?
Summary
This guide helps you troubleshoot and resolve: Can I Keep My Current Email Address When Moving to Microsoft 365?. Follow the steps below to fix the issue.
Quick Tip: Need immediate assistance? 💻 Open a Ticket
Common Causes
Yes. You can move your existing email addresses to Microsoft 365 without changing your domain or interrupting your client communication. This guide walks you through migrating from legacy IMAP, POP3, cPanel webmail, or shared generic logins to Microsoft Exchange Online, including how to set up shared mailboxes, signatures, calendars, and improve email deliverability.
Quick Fix Steps
- Verify you own the domain you want to use with Microsoft 365.
- Add the domain to your Microsoft 365 admin centre.
- Assign Microsoft 365 licences to all users who require a mailbox.
- Create user mailboxes and shared mailboxes for all existing addresses such as
accounts@andsales@. - Migrate existing emails and contacts from your current provider.
- Test mail flow in Microsoft 365 before changing any DNS records.
- Update MX records to point to Microsoft Exchange Online only after migration is complete.
- Configure email signatures and shared calendars.
Detailed Instructions
1. Add and Verify Your Domain
- Sign in to the Microsoft 365 admin centre at
https://admin.microsoft.com. - Go to Settings > Domains.
- Select Add domain and enter your business domain name.
- Choose how you want to verify ownership, typically by adding a TXT or MX record through your domain registrar or DNS host.
- Complete the verification steps provided by Microsoft.
Do not update your domain MX records until every user mailbox has been created, licences assigned, migration tested, and you have confirmed that mail is flowing correctly through Microsoft 365. Changing MX records too early can cause mail loss.
Keep your current email hosting active until migration is complete. Do not cancel your existing service until you have confirmed all mail is flowing through Microsoft 365.
2. Assign Licences and Create Mailboxes
- In the Microsoft 365 admin centre, go to Billing > Licences and confirm you have sufficient Microsoft 365 licences for every user who requires a mailbox.
- Go to Users > Active users.
- Select Add a user and assign the appropriate Microsoft 365 licence.
- Repeat this process for every existing email address that needs a dedicated mailbox before starting migration.
- For shared addresses such as
accounts@,sales@, orsupport@, go to Users > Active users or Teams & groups > Shared mailboxes, depending on your admin centre view. - Select Add a shared mailbox, enter the email address and name, then save.
- Add members to the shared mailbox and assign permissions such as Send as or Send on behalf as needed.
Shared mailboxes provide up to 50 GB of storage without requiring a dedicated licence for the mailbox itself. However, each user who accesses the shared mailbox must have their own Microsoft 365 licence assigned to their user account. If a shared mailbox exceeds 50 GB, a licence must be assigned to the shared mailbox to increase storage.
3. Set Up Email Coexistence and Forwarding
- Before updating MX records, configure email forwarding or coexistence settings with your current provider so messages continue to reach users during migration.
- If your source provider supports modern authentication, enable it to avoid authentication errors during the migration process.
- Use the Microsoft 365 admin centre migration tools or a third-party migration service to connect to your source email server.
- Enter the server address, port, and credentials provided by your current host.
- Select the mailboxes to migrate and schedule the migration during low-usage hours.
- Monitor migration progress in the admin centre and verify that emails, contacts, and calendar items arrive correctly.
IMAP migrations transfer email messages only. Contacts, calendars, and tasks usually need to be exported and imported separately.
4. Update MX Records
- Only after all mailboxes are created, tested, and migration is complete, go to your domain registrar or DNS hosting provider.
- Locate the MX records for your domain.
- Replace existing MX records with the Microsoft 365 values provided in the admin centre under Settings > Domains > [your domain] > DNS records.
- Save the changes and allow time for DNS propagation, which can take up to 72 hours.
5. Configure Email Signatures
- Sign in to the Exchange admin centre at
https://admin.exchange.microsoft.com. - Go to Mail flow > Rules.
- Select Add a rule > Apply disclaimers to create an organisation-wide email signature.
- Configure the rule to apply to all messages and enter your signature HTML or text.
- Users can also set personal signatures in Outlook desktop under File > Options > Mail > Signatures, or in Outlook on the web under Settings > Mail > Compose and reply.
6. Set Up Shared Calendars
- Open Outlook and go to the Calendar view.
- Right-click My Calendars and select Add Calendar > From Address Book.
- Select the shared mailbox calendar and add it to your view.
- In Outlook on the web, right-click Other calendars, select Open calendar, and enter the shared mailbox address.
7. Prevent Emails from Landing in Junk Folders
- Add SPF, DKIM, and DMARC records for your domain in your DNS settings.
- In the Microsoft 365 Defender portal, go to Email & collaboration > Policies & rules > Threat policies > Anti-spam.
- Review and adjust spam filter policies to ensure legitimate internal and client emails are not marked as junk.
- Ask clients to add your sending domain to their safe senders list if messages continue to go to junk.
Troubleshooting
Domain Verification Failures
- Confirm the TXT or MX record was added exactly as provided by Microsoft, including any required values or spacing.
- Check that you are editing the DNS zone at your domain registrar or DNS host, not your web hosting control panel, unless they are the same provider.
- Use an online DNS lookup tool to confirm the verification record is publicly visible.
- Allow time for DNS propagation; verification may not succeed immediately after record creation.
- If verification continues to fail, contact your domain registrar to confirm there are no restrictions on DNS record changes.
DNS Propagation Delays
- Use an online DNS lookup tool to check whether MX, SPF, DKIM, or DMARC records have propagated globally.
- Remember that DNS changes can take up to 72 hours to fully propagate, though they often update sooner.
- Lower TTL values on your DNS records before making changes to speed up future propagation.
Authentication Errors During Migration
- Confirm the source email server allows IMAP connections and that the credentials used are correct.
- Enable modern authentication or app passwords on the source account if required by your email provider.
- Check whether multi-factor authentication on the source account is blocking the migration connection.
- Contact your current email provider if connection errors persist.
Emails Not Received After MX Change
- Confirm DNS changes have propagated using an online DNS lookup tool.
- Verify the recipient address exists in Microsoft 365 and is assigned a licence or shared mailbox.
- Check the Microsoft 365 Message Trace tool in the admin centre under Mail flow > Message trace.
Cannot Send from Shared Mailbox
- Ensure the user has Send as or Send on behalf permissions assigned in the admin centre.
- Restart Outlook after permission changes are made.
- In Outlook on the web, the shared mailbox may need to be added manually under Folders > Add shared folder.
Migration Stuck or Slow
- Check that the source email server allows IMAP connections and that app passwords or modern authentication are enabled if required.
- Reduce the number of concurrent mailboxes being migrated.
- Contact your current email provider if connection errors persist.
If you need assistance with domain verification, DNS changes, or migration planning, Open a Ticket with our support team.
After confirming all mail is flowing correctly through Microsoft 365, contact your previous email provider to decommission the old service and avoid duplicate charges.
Still Having Issues?
Need more help? If the issue persists after trying these steps, please open a support ticket and our team will assist you.
💻 Open a Ticket
💻 Open a Ticket