About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
The NDR 450 4.4.317 Cannot connect to remote server [Message=UntrustedRoot] means Exchange Online could not trust the certificate that a remote mail server presented. Microsoft's cause is specific: during the TLS handshake the remote server "sends only a leaf certificate" and leaves out the certificates of the intermediate certification authorities (CAs).
Exchange Online does not go looking for the missing certificates. The fix belongs to whoever runs the remote mail server: make it send the full certificate chain. If that server is your own, the steps below show how to find the gap on a Windows server.
What the error means
Microsoft's page describes two directions in which this NDR appears.
- Exchange Online connects to a remote server to deliver a message to an external recipient. The remote server presents a leaf certificate with no intermediates. Exchange Online cannot chain it to a root CA that Microsoft trusts, so it creates the NDR for the sender.
- A remote server connects to Exchange Online to deliver to an Exchange Online recipient. The same gap exists. Exchange Online rejects the message and the remote server then generates the NDR for its own sender.
The page states the rule plainly: "Exchange Online doesn't fetch intermediate certificates on–demand. Therefore, a remote MTA that provides a certificate should include the full certificate chain." It adds that MTAs managed by Exchange Online always provide the full chain. The page applies to Exchange Online.
The page does not say whether Exchange Online keeps retrying after this code or for how long, so judge the outcome from what the sender and the recipient actually receive.
Connectors are where this meets your own configuration. When you create an outbound connector from Microsoft 365 to your own mail server, Microsoft's wizard lets you choose "Always use Transport Layer Security (TLS) to secure the connection (recommended)". If you choose it, Microsoft's connectors page says: "Choosing any one of the two options under Connect only if the recipient's email server certificate matches this criteria." The option it names is "Issue by a trusted certificate authority (CA)", and it describes a match on the subject name or subject alternative name (SAN) as optional. Microsoft adds that defining TLS settings on that page is optional, and that it depends on "whether the destination server supports TLS or not."
Work out which direction you have before you act. In the first direction the NDR arrives from Microsoft 365 for mail your staff sent out. In the second, Microsoft's page says the remote server "then generates an NDR for the sender", so the bounce is produced on the other organisation's system and your staff may never see it. In both directions the server to fix is the one whose certificate is missing its intermediates. Look at who sent the bounce to tell which one that is.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Remote server sends the leaf certificate only | NDR 450 4.4.317 ... [Message=UntrustedRoot] for mail to or from one specific domain |
Build the chain on the remote server and list its intermediates; a fresh test message shows whether it now sends them |
| Intermediate certificate never installed after a new or renewed certificate | Started on the day a certificate was replaced | Compare the install date of the current certificate with the first NDR |
| A place to look (not on Microsoft's NDR page): mail server behind a device or appliance that holds the certificate | Windows server looks correct, NDR persists | The device, not the Windows server, presents the certificate on port 25 |
| Outbound connector set to validate the certificate, remote server cannot meet it | NDR only for domains the connector routes to a smart host | Connector TLS setting in the Exchange admin center |
The last cause is a place to look, not a finding from the NDR page, which does not mention connectors. Microsoft's Set-OutboundConnector page describes the CertificateValidation setting as "TLS is used to encrypt the channel and certificate chain validation and revocation lists checks are performed."
Prove the cause before changing anything
- Read the NDR that one affected sender received. Confirm the exact code and the
[Message=UntrustedRoot]suffix, and note the recipient domain. This names the remote server to examine. - Ask the administrator of the remote mail system whether it sends the full chain. If you are that administrator, continue below.
- On a Windows mail server, open the Certificates snap-in for the computer account. In the console tree expand Personal, then Certificates. Double-click the certificate bound to SMTP and open the Certification Path tab. If there is more than one level between the leaf and the root, note each intermediate. The tab shows the path Windows can build; it does not by itself prove what the server sends during the TLS handshake, so the fresh test message in the last section is the real proof. Microsoft's own certificate steps use this same tab.
- Note the name and thumbprint of each intermediate on the Certification Path tab. Those are the certificates the server must also send during the TLS handshake.
- On Windows, if CAPI2 operational logging is already on, look for event 30 from
Microsoft-Windows-CAPI2/Operationalwith the result "A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider." Microsoft's page for a different NDR,550 5.7.64 TenantAttribution, shows this event when an on-premises server does not send the required certificate chain; the 4.4.317 page does not mention it.
Fix
Remote server is yours and runs on Windows. The 4.4.317 page gives no steps beyond "configure your remote MTA to provide the full certificate chain." Microsoft's page for a different NDR, 550 5.7.64 TenantAttribution, describes the same kind of gap (a server that does not send the intermediate certificates) and gives these Windows steps: get the intermediate certificates from the certificate issuer, export each one as DER-encoded .cer from the Certification Path tab, then import them into the server's intermediate store.
Save first: list what is already in the intermediate store and copy the output into a text file. Microsoft's Import-Certificate page uses Get-ChildItem on the Cert: drive to browse certificate stores:
Get-ChildItem -Path Cert:\LocalMachine\CA
Risk: the next command adds certificates to the machine-wide intermediate store. Every service on that server will use them. Back-out: after the import, run the same listing again and delete, in the Certificates snap-in for the computer account, in the intermediate certification authorities store (the one the import command targets, cert:\LocalMachine\CA), only the certificates whose thumbprints appear in the second listing and not in the first.
Get-ChildItem -Path c:\import\intermediateca.cer | Import-Certificate -CertStoreLocation cert:\LocalMachine\CA
Repeat for each intermediate in the path, using the path of each exported file; the page's single path c:\import\intermediateca.cer is only its example. This is the exact command on Microsoft's page, run in an elevated PowerShell session.
Save first, before any restart: find the service that presents the certificate to SMTP (the Certificates snap-in shows which certificate is bound to it; the mail server's own documentation names the service), and record its name, the number of messages queued on it and the current connections.
Disruptive step: after importing, restart that service only if it does not pick up the new store contents. Impact: mail on that service is paused while it restarts and inbound connections fail briefly. Back-out: start the service again. Microsoft's page does not say whether a restart is needed, so test first without restarting.
Remote server is a non-Windows MTA or appliance. Microsoft says the remote administrator should "configure your remote MTA to provide the full certificate chain." Microsoft's page does not give product-specific steps. Use that vendor's documentation to build a combined certificate file of leaf plus intermediates.
Save first: keep a copy of the old certificate file, and note where the mail server reads it from.
Disruptive step: replace the certificate file and reload the SMTP service. Impact: the service must reload the certificate, and a mistake in the new file can stop mail. Back-out: put the saved file back and reload the service.
Remote server belongs to a partner. Microsoft's page: "If you're an email admin in the Exchange Online organization, notify an email admin in the remote MTA's organization about the NDR." Send them the NDR text, the date and time, and the page address.
Confirm the fix
Send a new test message to or from the affected domain. A successful delivery produces no new 450 4.4.317 for that sender and recipient pair. Judge the fix by a fresh test, not by the old queue. A fresh message is the proof that the server now sends its intermediates.
Example (illustrative): fs01.contoso.com.au is an on-premises mail server that delivers about 40 messages a day to Microsoft 365 recipients, so it is the remote MTA in Microsoft's second scenario. A replacement certificate is installed on Monday, but only the leaf is added; the two intermediates stay on the old image. By Thursday morning, three working days of mail have been rejected: 40 x 3 = 120 messages, and fs01 has sent its own senders a non-delivery report for each. The administrator imports both intermediates (2 certificates) on Thursday and sends a test; delivery succeeds. Microsoft's page does not say that the rejected messages are delivered later, so the senders resend the 120.
What to watch afterwards
- Run the chain check as part of every certificate renewal, before the old certificate is retired.
- Keep a dated list of every intermediate used by each mail-facing certificate.
- Watch for new
4.4.317NDRs after each change. Microsoft's page does not say how to tell whose certificate is at fault; as a working rule, treat failures for one partner as a reason to ask that partner, and failures for many domains as a reason to check your own certificate. - Record which devices in front of the mail server hold the certificate, so renewals update all of them.
Read next
Related articles you may want next.
- TroubleshootingExchange Online NDR '5.4.14 Hop count exceeded - possible mail loop ATTR34' after a hybrid or connector change5.4.14 Hop count exceeded - possible mail loop ATTR34: check accepted domains, then hybrid connectors for DNS routing or scoping. Read-only checks first.Read article
- HostingRenew IIS TLS Certificates and Verify the Live EndpointMap TLS termination, renew the correct certificate and validate trust and hostname from real client paths before retiring the old certificate.Read article
- HostingShorter TLS certificate lifetimes: the 2026 to 2029 schedule and what to automateThe CA/Browser Forum schedule cutting TLS certificate lifetimes to 200, 100 and 47 days, and how to decide which renewals to automate first.Read article
Risks and limits
These commands have not been run or lab-tested. Microsoft's NDR page gives the cause and the remote-administrator action, but no step-by-step method for non-Windows servers and no list of which intermediates a given CA needs; those come from the certificate issuer. The page does not describe outbound-connector settings. Do not change a connector's TLS setting from CertificateValidation to EncryptionOnly to silence the NDR: Microsoft's description of EncryptionOnly is "No certificate authentication is performed", which removes the check rather than fixing the chain.
Sources
- NDR error code 450 4.4.317 Cannot connect to remote server (Message=UntrustedRoot) — Microsoft Learn, page dated 2026-08-11, accessed 20 November 2026
- 550 5.7.64 TenantAttribution when sending emails through Microsoft 365 — Microsoft Learn, page dated 2026-01-08, accessed 20 November 2026
- Set up connectors to route mail between Microsoft 365 or Office 365 and your own email servers — Microsoft Learn, page dated 2025-07-28, accessed 20 November 2026
- Set-OutboundConnector — Microsoft Learn, date not shown, accessed 20 November 2026
- Import-Certificate — Microsoft Learn, date not shown, accessed 20 November 2026
This article was originally published on .