Archiving Emails from Microsoft 365 Hybrid - Revision history

Rjansen at 12:35, 20 February 2026

2026-02-20T12:35:10Z

Cstelzmann at 14:41, 18 September 2025

2025-09-18T14:41:47Z

Ltalaschus: /* Synchronizing with Microsoft 365 (recommended for most scenarios) */

2024-03-27T14:48:54Z

Synchronizing with Microsoft 365 (recommended for most scenarios)

Ltalaschus: /* Synchronizing with Microsoft 365 (recommended for most scenarios) */

2024-03-27T14:47:32Z

Synchronizing with Microsoft 365 (recommended for most scenarios)

Ltalaschus: /* Synchronizing with Microsoft 365 (recommended for most scenarios) */

2024-03-27T14:47:02Z

Synchronizing with Microsoft 365 (recommended for most scenarios)

Ltalaschus at 14:24, 27 March 2024

2024-03-27T14:24:24Z

Ltalaschus: /* Archiving Microsoft 365 Mailboxes or Public Folders */

2023-10-12T12:37:35Z

Archiving Microsoft 365 Mailboxes or Public Folders

Ltalaschus: /* Archiving Incoming and Outgoing Emails Directly */

2023-08-31T12:22:22Z

Archiving Incoming and Outgoing Emails Directly

Ltalaschus at 15:00, 30 May 2023

2023-05-30T15:00:21Z

Ltalaschus at 10:02, 17 November 2022

2022-11-17T10:02:39Z

@@ Line 37: / Line 37: @@
 * Then configure your local Exchange Server to also send their journal reports to the same Gateway mailbox. Use the manual for your matching Exchange Server version, but we recommend not creating a journal mailbox (skip step 1 in this case), but to define the external email address of your MailStore Gateway to be the recipient of these reports. This way, all reports are received at the same destination:
 ** [[Archiving_Emails_from_Microsoft_Exchange_SE#Archiving_Incoming_and_Outgoing_Emails_Directly|Exchange SE]]
-** [[Archiving_Emails_from_Microsoft_Exchange_2019#Archiving_Incoming_and_Outgoing_Emails_Directly|Exchange 2019]]
+** [[Archiving_Emails_from_Microsoft_Exchange_2019#Archiving_Incoming_and_Outgoing_Emails_Directly|Exchange 2019 (Legacy System)]]
-** [[Archiving_Emails_from_Microsoft_Exchange_2016#Archiving_Incoming_and_Outgoing_Emails_Directly|Exchange 2016]]
+** [[Archiving_Emails_from_Microsoft_Exchange_2016#Archiving_Incoming_and_Outgoing_Emails_Directly|Exchange 2016 (Legacy System)]]
 ** [[Archiving_Emails_from_Microsoft_Exchange_2013#Archiving_Incoming_and_Outgoing_Emails_Directly|Exchange 2013 (Legacy System)]]

@@ Line 36: / Line 36: @@
 * First configure the Journaling for Microsoft 365 with the MailStore Gateway: [[Archiving_Emails_from_Microsoft_365_-_Modern_Authentication#Archiving_Incoming_and_Outgoing_Emails_Directly|Archiving Incoming and Outgoing Emails Directly - Microsoft 365]]
 * Then configure your local Exchange Server to also send their journal reports to the same Gateway mailbox. Use the manual for your matching Exchange Server version, but we recommend not creating a journal mailbox (skip step 1 in this case), but to define the external email address of your MailStore Gateway to be the recipient of these reports. This way, all reports are received at the same destination:
 ** [[Archiving_Emails_from_Microsoft_Exchange_2019#Archiving_Incoming_and_Outgoing_Emails_Directly|Exchange 2019]]
 ** [[Archiving_Emails_from_Microsoft_Exchange_2016#Archiving_Incoming_and_Outgoing_Emails_Directly|Exchange 2016]]

@@ Line 8: / Line 8: @@
 === Synchronizing with Microsoft 365 (recommended for most scenarios) ===
-MailStore Server will only be synchronized with Microsoft Entra ID of your Microsoft 365 tenant. Since your local Active Directory is being synchronized with the Microsoft Entra ID via a Microsoft Entra ID Connector, all relevant users details are also present in Microsoft 365.
+MailStore Server will only be synchronized with Microsoft Entra ID of your Microsoft 365 tenant. Since your local Active Directory is being synchronized with Microsoft Entra ID via a Microsoft Entra ID Connector, all relevant users details are also present in Microsoft 365.
 The advantage is that you can use all modern authentication methods, especially MFA, in MailStore Server.
 Proceed as if you solely had a [[Synchronizing User Accounts with Microsoft 365 - Modern Authentication|Microsoft 365 environment]].

@@ Line 8: / Line 8: @@
 === Synchronizing with Microsoft 365 (recommended for most scenarios) ===
-MailStore Server will only be synchronized with Microsoft Entra ID of your Microsoft 365 tenant. Since your local Active Directory is being synchronized with the Microsoft Entra ID via an Microsoft Entra ID Connector, all relevant users details are also present in Microsoft 365.
+MailStore Server will only be synchronized with Microsoft Entra ID of your Microsoft 365 tenant. Since your local Active Directory is being synchronized with the Microsoft Entra ID via a Microsoft Entra ID Connector, all relevant users details are also present in Microsoft 365.
 The advantage is that you can use all modern authentication methods, especially MFA, in MailStore Server.
 Proceed as if you solely had a [[Synchronizing User Accounts with Microsoft 365 - Modern Authentication|Microsoft 365 environment]].

@@ Line 8: / Line 8: @@
 === Synchronizing with Microsoft 365 (recommended for most scenarios) ===
-MailStore Server will only be synchronized with the Microsoft Entra ID of your Microsoft 365 tenant. Since your local Active Directory is being synchronized with the Microsoft Entra ID via an Microsoft Entra ID Connector, all relevant users details are also present in Microsoft 365.
+MailStore Server will only be synchronized with Microsoft Entra ID of your Microsoft 365 tenant. Since your local Active Directory is being synchronized with the Microsoft Entra ID via an Microsoft Entra ID Connector, all relevant users details are also present in Microsoft 365.
 The advantage is that you can use all modern authentication methods, especially MFA, in MailStore Server.
 Proceed as if you solely had a [[Synchronizing User Accounts with Microsoft 365 - Modern Authentication|Microsoft 365 environment]].

@@ Line 8: / Line 8: @@
 === Synchronizing with Microsoft 365 (recommended for most scenarios) ===
-MailStore Server will only be synchronized with the Azure Active Directory of your Microsoft 365 tenant. Since your local Active Directory is being synchronized with the Azure Directory via an Azure AD Connector, all relevant users details are also present in Microsoft 365.
+MailStore Server will only be synchronized with the Microsoft Entra ID of your Microsoft 365 tenant. Since your local Active Directory is being synchronized with the Microsoft Entra ID via an Microsoft Entra ID Connector, all relevant users details are also present in Microsoft 365.
 The advantage is that you can use all modern authentication methods, especially MFA, in MailStore Server.
 Proceed as if you solely had a [[Synchronizing User Accounts with Microsoft 365 - Modern Authentication|Microsoft 365 environment]].
@@ Line 15: / Line 15: @@
 If you want to use Windows Authentication or Microsoft Active Directory Federation Services (ADFS) for logging in at MailStore Server you are able to synchronize MailStore Server with your local Active Directory.<br />If you want to archive user mailboxes, shared mailboxes or public folder you still have to follow the [[Synchronizing User Accounts with Microsoft 365 - Modern Authentication|user synchronization with Microsoft 365 article]] to provide proper access permissions to your Microsoft 365 tenant.<br /><br />
 Do not execute these steps:
-:* 2.4 Configuring App Authentication in Azure AD
+:* 2.4 Configuring App Authentication in Microsoft Entra ID
 :* 2.5 Configuring the Redirect URI in MailStore Server
 :* 2.7 User Database Synchronization

@@ Line 24: / Line 24: @@
 Use the manual for archiving mailboxes in Microsoft 365 as a guide. On-premise Exchange mailboxes are also being archived using Microsoft 365.
 * [[Archiving_Emails_from_Microsoft_365_-_Modern_Authentication#Archiving_Individual_Microsoft_365_Mailboxes|Archiving Individual Mailboxes]]
-* [[Archiving_Emails_from_Microsoft_365_-_Modern_Authentication#Archiving_Multiple_Microsoft_365_Mailboxes_Centrally|Archiving Multiple Exchange Mailboxes Centrally]]
+* [[Archiving_Emails_from_Microsoft_365_-_Modern_Authentication#Archiving_Multiple_Microsoft_365_Mailboxes_Centrally|Archiving Multiple Mailboxes Centrally]]
 * [[Archiving_Emails_from_Microsoft_365_-_Modern_Authentication#Including_Microsoft_365_Shared_Mailboxes|Shared Mailboxes]]
 * [[Archiving_Emails_from_Microsoft_365_-_Modern_Authentication#Public_Folders|Public Folders]]
 == Archiving Incoming and Outgoing Emails Directly ==

@@ Line 1: / Line 1: @@
 __NOTOC__
-{{Multiline Notices|Heading=Important Notices|MailStore Server supports archiving emails from a hybrid environment with Microsoft&nbsp;365 (Modern Authentication) and on-premises Exchange Server(s) only with [https://learn.microsoft.com/en-us/exchange/exchange-hybrid Microsoft's Best Practice Guides] and only with the global Microsoft Cloud.
+{{Multiline Notices|Heading=Important Notices|MailStore Server supports archiving emails from a hybrid environment with Microsoft&nbsp;365 (Modern Authentication) and on-premises Exchange Server(s) only with [https://learn.microsoft.com/en-us/exchange/exchange-hybrid Microsoft's Best Practice Guides] and only with the global Microsoft Cloud.|If you have archived emails from an Exchange server and synchronized users from an Active Directory until now, follow the article [[Changing Archiving from Microsoft Exchange Server to Microsoft 365]].
 |For better readability, the terms ''Microsoft&nbsp;365'' and ''Exchange&nbsp;Online'' are used interchangeably hereinafter instead of ''Exchange&nbsp;Online / Microsoft&nbsp;365''.
 | Please test the described configurations early, preferably in the trial phase. In case your scenario differs from Microsoft's described best practices or is in any other way more individual, questions about feasibility can be identified early and discussed with our technical support.}}