Move Domain DNS Management to Microsoft 365 Without Disrupting Email or Websites
Question details
The user wants to move domain DNS management to Microsoft 365 while retaining a SiteGround website and avoiding disruption to Google Workspace email, then migrate nine email accounts with appropriate licensing.
- Product
- Microsoft 365, Google Workspace (formerly G Suite), and SiteGround
- Device & OS
- not provided
- Scenario
- A domain currently uses third-party DNS management. The user is considering changing nameservers and later migrating nine Google Workspace email accounts, but currently has only three Microsoft 365 Business Standard licenses.
- Observed behavior
- The desired outcome is uninterrupted website access and email delivery during the DNS change, followed by a separately planned migration to licensed Microsoft 365 mailboxes.
Open your current DNS provider’s record list and obtain the website records from SiteGround and mail records from Google Workspace. In the Microsoft 365 admin center, check Settings > Domains for the setup options available to your domain; adding Microsoft 365 does not necessarily require changing nameservers.
Prepare the DNS records needed to preserve SiteGround hosting and Google Workspace email
Use this preparation before any nameserver change so the new DNS zone preserves the services you want to keep.
Nameservers determine which provider publishes your domain’s DNS records. They do not move your website files or mailbox contents. Email delivery changes when the active MX records change, not simply because Microsoft 365 is added to the domain.
Sign in to the current DNS provider and open the domain’s DNS management page. Export or record every entry, including its name, type, value, priority where applicable, and TTL. Include website, mail, verification, subdomain, and other service records.
Open SiteGround Site Tools or contact SiteGround support to confirm the A, AAAA, or CNAME records required for the root domain, www, and any hosted subdomains. Use those provider-supplied values when preparing the destination DNS zone.
Open the Google Admin console and review the domain’s Gmail setup requirements. Keep the Google Workspace MX records active until the email cutover, and preserve the required SPF, DKIM, and DMARC records. Do not replace Google’s MX records with Microsoft 365 records during a DNS-only move.
In the Microsoft 365 admin center, go to Settings > Domains > Add domain, or select the existing domain. Follow the verification instructions and add the requested TXT record at the active DNS provider. Review service setup prompts before allowing automatic changes to mail records.
Change nameservers only when the destination DNS service is ready
Use this approach if the Microsoft 365 domain setup explicitly offers DNS hosting and supplies nameservers for your domain.
Plan the nine-user Google Workspace email migration separately
Use this solution to resolve mailbox licensing and prepare the email cutover without tying it to the DNS hosting change.
Use WPS Office to Organize Your DNS and Email Migration Plan
WPS Office is a free, lightweight alternative for preparing DNS inventories, user licensing lists, and migration checklists. Its familiar interface and Microsoft Office format compatibility make existing planning documents easy to move into WPS. It does not host DNS, provide Exchange mailboxes, or perform the Google Workspace email migration.
Frequently Asked Questions
Do I have to change nameservers to use Microsoft 365 email?
No. You can usually retain your current DNS provider and add the records supplied under Microsoft 365 admin center > Settings > Domains. Change nameservers only if you deliberately want to change DNS hosting and the destination supports all your required records.
Will changing nameservers automatically stop Google Workspace email?
Not necessarily. Incoming mail follows the MX records published by the authoritative DNS provider. Google Workspace can continue receiving mail if its required records are preserved in the new zone. Missing MX records or replacing them with Microsoft 365 MX records can disrupt or redirect delivery.
Can my website stay at SiteGround after I change DNS providers?
Yes. Website hosting and DNS hosting are separate services. Obtain the website’s required records from SiteGround Site Tools or SiteGround support, then publish them at the new DNS provider before changing nameservers. Include both the root domain and www records.
Do all nine users need Microsoft 365 Business Standard licenses?
Each user who needs an individual Microsoft 365 mailbox generally needs a license that includes Exchange Online, but it does not have to be Business Standard. With only three qualifying licenses available for nine users, you need six more suitable licenses. Review subscriptions in Billing > Your products and assign licenses under Users > Active users.
When should I replace Google Workspace MX records with Microsoft 365 MX records?
Replace them at the planned email cutover, after the destination mailboxes are licensed, migration prerequisites are complete, and mailbox readiness has been checked. Obtain the Microsoft 365 record values from Settings > Domains and apply them at whichever provider currently hosts your DNS.
