'%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 Microsoft 365 Emails Not Sending to Gmail, Yahoo, or AOL
Question details
Users are experiencing delivery failures when attempting to send emails from their Microsoft 365 accounts to external addresses hosted by Gmail, Yahoo, or AOL.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Sending emails from a Microsoft 365 custom domain to Gmail, Yahoo, or AOL accounts.
- Observed behavior
- Messages are successfully received from Gmail, Yahoo, or AOL, but outgoing messages to these services bounce back or fail to deliver due to strict email authentication requirements.
Ensure you have administrative access to both your Microsoft 365 admin center and your domain registrar's DNS settings before attempting to configure authentication records.
Configure SPF, DKIM, and DMARC Records for Custom Domains
Set up domain authentication records in your DNS to comply with strict sender requirements enforced by major email providers.
Major email providers like Gmail, Yahoo, and AOL have introduced stricter email-authentication requirements to prevent spam and spoofing. If you use a custom domain with Microsoft 365, you must configure specific DNS records to verify your identity as a legitimate sender.
Log in to your domain registrar's website (such as GoDaddy, Cloudflare, or Namecheap) and navigate to the DNS management or DNS zone editor page.
Add a new TXT record for SPF (Sender Policy Framework) to authorize Microsoft 365 to send emails on your behalf. The standard value for Microsoft 365 is usually v=spf1 include:spf.protection.outlook.com -all.
Log in to the Microsoft 365 Defender portal, navigate to Policies & Rules > Threat policies > DomainKeys Identified Mail (DKIM). Enable DKIM for your domain and add the generated CNAME records to your domain's DNS settings.
Create a DMARC TXT record in your DNS (e.g., _dmarc.yourdomain.com) with a value like v=DMARC1; p=none; to specify how receiving servers should handle emails that fail SPF or DKIM checks.
Return to the Microsoft 365 admin center, go to Settings > Domains, select your domain, and run a health check to confirm that all DNS records are verified and active.
Contact Your IT Administrator or Domain Host
If you are using a work or school account and lack administrative privileges, you must escalate the issue to the appropriate support team.
Need a Reliable Office Suite? Try WPS Office
While you troubleshoot your Microsoft 365 email configuration, consider WPS Office as a lightweight, free alternative for your document, spreadsheet, and presentation needs. It provides robust formatting tools and a highly familiar user interface without a heavy subscription.
- 1. Download the Installer: Visit the official WPS Office website and click the free download button for your specific operating system (Windows, Mac, or Linux).
- 2. Install WPS Office: Run the downloaded installation file and follow the quick on-screen instructions to set up the software on your device.
- 3. Open Your Office Files: Launch WPS Office to easily open, edit, and save all your existing Microsoft Office documents without any formatting loss.
Frequently Asked Questions
Why did my emails to Gmail work before but fail now?
Major email providers like Gmail, Yahoo, and AOL recently updated their security policies. They now require all senders, particularly bulk senders and custom domains, to strictly authenticate their emails using SPF, DKIM, and DMARC to prevent spam and phishing.
What is an SPF record in Microsoft 365?
An SPF (Sender Policy Framework) record is a DNS TXT record that lists the IP addresses and domain names authorized to send emails on behalf of your custom domain. It tells receiving servers that Microsoft 365 is permitted to route your messages.
Where can I find the correct DNS values for my Microsoft 365 domain?
You can find the exact DNS values required for your custom domain by navigating to Settings > Domains in the Microsoft 365 admin center. Clicking on your specific domain will display the required DNS records for Exchange Online.
Will fixing these DNS records resolve bounce-back errors?
Yes, properly configuring and verifying your SPF, DKIM, and DMARC records will fully authenticate your outgoing emails. This satisfies the strict security requirements of external providers like Gmail and AOL, stopping authentication-related bounce backs.
