5.3.190: on-premises journaling to Microsoft 365 not enabled
An on-premises journal rule sends journal reports to Microsoft 365, but the organization does not have Journaling Archive turned on.
- Microsoft
- Provider
- Permanent (5xx)
- Class
- Sources checked
- Author
At a glance
- Code
- 5.3.190
- Temporary or permanent
- PermanentRefused for good: the message comes back to the sender, and resending it gets the same answer.
- Who has to act
- The sender. The fix is on the sending side: your domain, your server or your list.
- What the server says
5.3.190 Journaling on-premises messages to Microsoft 365 or Office 365 not supported when Journaling Archive…
What it means
Journaling keeps copies of messages for compliance. Microsoft 365 accepts journal reports from an on-premises Exchange organization only when Journaling Archive is enabled in the organization's settings. If an on-premises journal rule points at Microsoft 365 while that setting is off, the journal reports bounce with 5.3.190. Ordinary mail is not affected; only the journaling copies fail. To fix it, an admin turns Journaling Archive on in Microsoft 365, or points the on-premises rule at another destination.
Common causes
- An on-premises journal rule delivers journal reports to Microsoft 365.
- Journaling Archive is disabled in the Microsoft 365 organization.
How to fix it
- 01Decide whether Microsoft 365 should keep these journal reports.
- 02If it should, have the Microsoft 365 administrator enable Journaling Archive.
- 03If not, change the on-premises journal rule to deliver to a different location.
Sources
What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.
- Email nondelivery reports and SMTP errors in Exchange Onlinelearn.microsoft.com
All 111 Microsoft codesEvery code in the wikiPaste your own bounce