'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Cannot Receive Emails from Gmail Senders in Microsoft 365
Question details
A user is unable to receive incoming emails from Gmail accounts in Microsoft 365 after a domain migration.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- An organization is migrating its custom domain from Google Workspace to Microsoft 365, and the old Google accounts have been deleted.
- Observed behavior
- The user successfully receives messages from Microsoft 365 accounts and other external domains, but emails sent from Gmail accounts fail to deliver.
Request that the Gmail senders check their inbox for a Non-Delivery Report (NDR) or bounce-back message, as the specific error details are crucial for diagnosing exact routing or DNS failures.
Verify and Update Domain DNS and MX Records
Ensure your domain's mail exchange (MX) and SPF records point exclusively to Microsoft 365 and that old Google routing rules are removed.
When migrating from Google Workspace to Microsoft 365, residual DNS records can cause Gmail's servers to attempt internal delivery instead of routing to Microsoft 365.
Log in to the DNS management portal of your domain registrar or DNS hosting provider.
Locate the MX (Mail Exchange) records for your domain and delete any obsolete records pointing to Google, such as ASPMX.L.GOOGLE.COM.
Add or verify your Microsoft 365 MX record, which is typically formatted as yourdomain-com.mail.protection.outlook.com with a priority of 0.
Ensure your TXT record for SPF includes v=spf1 include:spf.protection.outlook.com -all and remove any old Google SPF entries.
Check Exchange Mail Flow Rules and Connectors
Investigate if leftover migration connectors or mail flow rules in Microsoft 365 are misdirecting incoming Gmail messages.
Run a Message Trace in Microsoft 365
Use the message trace tool to determine if the Gmail messages are reaching your Microsoft 365 tenant but being quarantined or filtered.
Enhance Your Productivity with WPS Office
While troubleshooting your Microsoft 365 email routing, ensure your document workflow remains uninterrupted. WPS Office is a lightweight, fully compatible, and free alternative to Microsoft Office that allows you to seamlessly open, edit, and share Word, Excel, and PowerPoint files.
- 1. Download the Installer: Visit the official WPS website to download the free installation package for your operating system.
- 2. Install WPS Office: Run the installer and follow the simple on-screen instructions to set up the suite on your device.
- 3. Open Existing Documents: Directly open your existing Microsoft Word, Excel, and PowerPoint files and resume your work without any formatting loss.
Frequently Asked Questions
Why are only Gmail emails failing to reach my Microsoft 365 inbox?
This commonly happens after a Google Workspace migration if the domain's MX records still prioritize Google's servers, or if Google's internal systems still consider the domain as active within their network and attempt internal delivery.
Where can the sender find the bounce-back error code (NDR)?
When an email fails to deliver, the sender receives an automated email from the Mail Delivery Subsystem. This email contains specific error codes and diagnostics explaining why the message was rejected or timed out.
How long does it take for MX record updates to take effect?
Changes to DNS and MX records can take anywhere from 1 to 48 hours to fully propagate globally. During this transition period, emails might be routed inconsistently.
