An integrated threat protection solution designed to detect, investigate, and respond to cyber threats across Microsoft 365 services.
The university’s central Microsoft 365 administrators must investigate and remediate this issue because the NDR shows that Exchange Online transferred the message successfully but Gmail rejected it based on the sending domain’s reputation.^1^
This is not something a mailbox user can correct through Outlook, and the error by itself does not establish a Microsoft 365 outbound-infrastructure fault.
What to send to the university administrators
Provide the administrator with:
- The complete non-delivery report (NDR), including Diagnostic information for administrators.
- Sender and recipient addresses, redacted where appropriate.
- Date and time, including time zone.
- Message ID or Network Message ID, if shown.
- Confirmation of whether all Gmail/Google Workspace recipients are affected or only particular institutions.
- A recent rejected message sent without attachments or links, if available.
Ask the administrator to perform these checks.
1. Confirm the rejection in Message trace
In the Exchange admin center, run Mail flow → Message trace for the sender, recipient, and failure time. Message trace identifies whether Exchange Online delivered, deferred, or rejected the message and records the events leading to its final status.^2^
The expected result in this case is an outbound message handed to Google, followed by Google’s remote 550 5.7.1 reputation rejection. If trace instead shows a Microsoft restriction or outbound-spam action, investigate that separate tenant-side condition.
An administrator can also retrieve trace details through Exchange Online PowerShell:
$sender = "[Email]"
$start = (Get-Date).AddDays(-2)
$end = Get-Date
Get-MessageTraceV2 -SenderAddress $sender -StartDate $start -EndDate $end |
Get-MessageTraceDetailV2
2. Validate authentication for the exact sending subdomain
SPF being present is not sufficient. Microsoft recommends configuring SPF, DKIM, and DMARC, in that order, for every custom domain and subdomain used to send mail.^3^
For the exact domain appearing after @ in the From address, the administrator should:
- SPF: Verify that there is only one SPF TXT record and that it authorizes every legitimate sending service. Each defined sending subdomain requires its own SPF record; a parent domain’s SPF record does not cover it.^4^
- DKIM: Obtain the two domain-specific CNAME values from Microsoft 365, publish them in DNS, and enable DKIM signing for the custom domain. The signing domain should align with the domain in the visible From address.^5^
- DMARC: Publish DMARC only after SPF and DKIM are configured. Start with
p=noneand reporting, review legitimate sources and alignment failures, and then move gradually top=quarantineand ultimatelyp=reject; applying enforcement without testing can reject legitimate mail.^6^ - Inspect the receiving copy or test-message headers for
Authentication-Results. At least SPF or DKIM must both pass and align with the From domain for DMARC to pass.
These DNS and tenant changes require the university’s DNS and Microsoft 365 administrative access.
3. Check for activity that damaged domain reputation
The administrators should review:
- Unusual outbound volume or messages the faculty member did not send.
- Compromised accounts, suspicious inbox/forwarding rules, and unauthorized applications.
- Tenant alerts named Suspicious email sending patterns detected, Email sending limit exceeded, and User restricted from sending email.
- Exchange mail-flow reports and message traces for other accounts sending through the same domain.
- Bulk-mail systems, websites, laboratory applications, or third-party platforms using the university domain without aligned SPF/DKIM.
Microsoft documents these reports and alerts as the tools for detecting abnormal outbound activity.^7^
If bulk or newsletter mail is being sent from the university’s primary domain, it should be stopped temporarily and later isolated on a properly authenticated subdomain. Microsoft 365 does not support bulk email beyond best effort, and bulk activity on a primary domain can affect ordinary mail delivery.^8^
Immediate workaround
For urgent correspondence, contact the recipient another way and ask their Google Workspace administrator to allow the specific sender or university domain. This can restore delivery to that institution, but it does not repair the domain’s general Gmail reputation.^1^
Escalation to Microsoft
If authentication passes, no compromised or bulk-sending activity is found, and Message trace suggests a Microsoft-side routing or outbound-pool problem, a university Microsoft 365 administrator should open a service request:
- Microsoft 365 admin center → Help & support.
- Enter the error and affected domain.
- Select Contact Support.
- Attach the full NDR, message-trace results, timestamps, message IDs, and authentication headers.
Only an administrator for the organization’s business subscription can use this support route. If the university purchased Microsoft 365 through a partner, that partner is the support contact.^9^
References
- Email send receive issue - Microsoft Q&A
- Trace an email message in Exchange Online
- Get started with Microsoft Defender for Office 365
- Set up SPF to identify valid email sources for your custom cloud domains
- Set up DKIM to sign mail from your cloud domain
- Set up DMARC to validate the From address domain for cloud senders
- Troubleshoot outbound sending limits and blocked users in Exchange Online
- Outbound spam protection for cloud mailboxes
- Get support for Microsoft 365 for business