MailStore Server Help - Recent changes [en]

Graph API Error Codes

Cstelzmann — Thu, 09 Apr 2026 12:18:48 GMT

text does not support structured data

EWS Migration

Ltalaschus — Thu, 09 Apr 2026 10:19:19 GMT

EWS Migration

Rjansen — Thu, 09 Apr 2026 10:13:01 GMT

MailStore Server Management Shell

Ltalaschus — Thu, 09 Apr 2026 09:59:27 GMT

Client side commands

MailStore Help

Ltalaschus — Thu, 09 Apr 2026 09:55:03 GMT

HelpTopicIds

Ltalaschus — Thu, 09 Apr 2026 09:48:20 GMT

Graph API Error Codes

Ltalaschus — Thu, 09 Apr 2026 09:46:16 GMT

Graph API Error Codes

Ltalaschus — Thu, 09 Apr 2026 09:24:14 GMT

Created page with "== ErrorMimeContentConversionFailed == '''Problem:''' While archiving email from a Microsoft Exchange server an EWS error code ErrorMimeContentConversionFailed occurs. '''Sol..."

New page

== ErrorMimeContentConversionFailed ==
'''Problem:''' While archiving email from a Microsoft Exchange server an EWS error code ErrorMimeContentConversionFailed occurs.

'''Solution:''' This kind of Exchange internal server error is caused by an internal Exchange function that is not able to convert a message from Exchange's internal MAPI format into the RFC822 compliant MIME format which is also used by MailStore Server. In nearly all cases the original MIME message received by the Exchange server already contained invalid data, such as an appointment request confirmation without references to the original appointment. Therefore it is usually safe to delete those emails.

Due to that error, the archiving profile itself terminates with a non-successful status code. This behavior can be changed since MailStore Server 8 by modifying the global property public.arcclient.skipMimeContentConversionFailed by executing the following command in [[MailStore_Server_Management_Shell|MailStore's Management Shell]]:

store-setprop --name="public.arcclient.skipMimeContentConversionFailed" --value="true"

'''Please note:''' Independent of this global property, MailStore Server is neither able to archive messages where the above error occurred nor delete them from the Exchange server.

[[de:Graph_API-Fehlermeldungen]]
[[en:Graph_API_Error_Codes]]

Microsoft 365 Profile Conversion Tool

Ltalaschus — Wed, 08 Apr 2026 15:18:48 GMT

EWS Migration

Ltalaschus — Wed, 08 Apr 2026 15:00:49 GMT

File:Ews conversion message.png

Ltalaschus — Wed, 08 Apr 2026 14:46:13 GMT

Ltalaschus uploaded File:Ews conversion message.png

New page

MailStore Help

Ltalaschus — Thu, 26 Mar 2026 08:41:37 GMT

Knowledge base

Microsoft 365 Profile Conversion Tool

Ltalaschus — Tue, 24 Mar 2026 11:00:36 GMT

Microsoft 365 Profile Conversion Tool

Rjansen — Tue, 24 Mar 2026 10:38:45 GMT

HelpTopicIds

Rjansen — Tue, 24 Mar 2026 10:04:00 GMT

Microsoft 365 Profile Conversion Tool

Rjansen — Tue, 24 Mar 2026 09:34:05 GMT

Synchronizing User Accounts with Microsoft 365 - Modern Authentication

Ltalaschus — Tue, 24 Mar 2026 09:18:49 GMT

Configuring API Permissions in Microsoft Entra ID

Microsoft 365 Export

Ltalaschus — Mon, 23 Mar 2026 16:48:40 GMT

File:ConversionTool en.png

Rjansen — Mon, 23 Mar 2026 15:09:02 GMT

Rjansen uploaded a new version of File:ConversionTool en.png

New page

Microsoft 365 Profile Conversion Tool

Rjansen — Mon, 23 Mar 2026 14:48:57 GMT

File:ConversionTool en.png

Rjansen — Mon, 23 Mar 2026 12:20:51 GMT

Rjansen uploaded File:ConversionTool en.png

New page

Microsoft 365 Profile Conversion Tool

Rjansen — Mon, 23 Mar 2026 12:19:21 GMT

Created page with "Microsoft is planning to [https://techcommunity.microsoft.com/blog/exchange/retirement-of-exchange-web-services-in-exchange-online/3924440| retire] the Exchange Web Service(EW..."

New page

Microsoft is planning to [https://techcommunity.microsoft.com/blog/exchange/retirement-of-exchange-web-services-in-exchange-online/3924440| retire] the Exchange Web Service(EWS) protocol in Exchange Online. This decision affects all companies that use EWS not just MailStore. This makes it necessary to use alternative access to Exchange Online mailboxes going into the future. We provide a conversion tool that will try to help you migrating profiles that rely on EWS and will stop working in the future.
The current Microsoft timeline for that can be followed [https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-ews-exchange-online| here].

===Accessing the conversion tool===
When your MailStore Server installation is using such a profile you should see a warning message you can click that will open the conversion tool.

Microsoft 365 Export

Rjansen — Mon, 23 Mar 2026 10:49:21 GMT

Exporting Email

Rjansen — Mon, 23 Mar 2026 10:45:37 GMT

Microsoft 365 Export

Rjansen — Mon, 23 Mar 2026 10:28:11 GMT

Microsoft 365 Export

Rjansen — Fri, 20 Mar 2026 16:03:29 GMT

Created page with "To be able to export emails to a Microsoft 365 mailbox, MailStore Server requires specific permissions on the target mailbox for an export. The more common help for exporting..."

New page

To be able to export emails to a Microsoft 365 mailbox, MailStore Server requires specific permissions on the target mailbox for an export. The more common help for exporting can be found in the article [[Exporting Email]].

'''Please note:''' Backup strategies (a backup of the entire archive) are discussed separately in the article [[Backup and Restore]].

== Steps for setting up permissions ==
The PowerShell module ''ExchangeOnlineManagement'' is required to set the permission. The presence of the module can be checked with the following command.
*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Get-Module ExchangeOnlineManagement -ListAvailable</source>
* If the output is empty, the module can be installed with the following command:
*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Install-Module -Name ExchangeOnlineManagement</source>
* If the output is not empty but the version is older than 3.8.0, the module can be updated with the following command:
*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Update-Module -Name ExchangeOnlineManagement</source>
* Then the module can be loaded:
*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Import-module ExchangeOnlineManagement</source>
* Connect with your client, use a user who has ''Role Management'' permissions:
*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Connect-ExchangeOnline -Organization <tenantID></source>

* Creating the app registration also resulted in the creation of an Enterprise App with its ''own ObjectID'' in your tenant. The next step requires the Enterprise App's ObjectID (not from the original app registration) and ApplicationID. Both can be found in the Entra ID Portal at [https://portal.azure.com/#view/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/~/AppAppsPreview this page].
* Now create a service principal for this Enterprise App:
*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">New-ServicePrincipal -AppId <appID> -ObjectId <enterpriseAppObjectID> -DisplayName "MailStore Service Principal"</source>
* The service principal must now be granted permission to send emails on behalf of a user. This user's email address must later be specified as the sender in the MailStore SMTP settings:
*;<p class=msnote>'''Important Note:''' All emails restored using this mailbox will also be saved as a copy in the mailbox's ''Sent Items'' folder. Therefore, we recommend using a dedicated shared mailbox that only authorized employees have access to.</p>

*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Add-MailboxPermission -Identity "emailAddressOf@sending.user" -User <enterpriseAppObjectID> -AccessRights FullAccess</source>
* Additionally, make sure that SMTP is allowed for this user:
*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Set-CASMailbox -Identity "emailAddressOf@sending.user" -SmtpClientAuthenticationDisabled $false</source>
* Click the … in the ''Credentials'' section and select your ''Credentials''.

Synchronizing User Accounts with Microsoft 365 - Modern Authentication

Ltalaschus — Thu, 19 Mar 2026 13:21:40 GMT

User Database Synchronization

File:Microsoft 365 sync 02.png

Ltalaschus — Thu, 19 Mar 2026 12:48:52 GMT

Ltalaschus uploaded a new version of File:Microsoft 365 sync 02.png

New page

File:Microsoft 365 sync 01.png

Ltalaschus — Thu, 19 Mar 2026 12:47:54 GMT

Ltalaschus uploaded a new version of File:Microsoft 365 sync 01.png

New page

Synchronizing User Accounts with Microsoft 365 - Modern Authentication

Ltalaschus — Thu, 19 Mar 2026 12:47:34 GMT

User Database Synchronization

Archiving Emails from Microsoft Exchange

Ltalaschus — Thu, 19 Mar 2026 12:40:08 GMT

Storage Locations

Ltalaschus — Wed, 18 Mar 2026 10:34:35 GMT

Creating an External Archive Store

@@ Line 1: / Line 1: @@
 == text does not support structured data ==
-'''Problem:''' While archiving email from a Microsoft 365 server an Graph API error code ''text does not support structured data'' occurs.
+'''Problem:''' While archiving email from Microsoft 365 a Graph API error code ''text does not support structured data'' occurs.
 '''Solution:''' This kind of server error is caused by an internal Microsoft 365 function that is not able to convert a message from its internal format into the RFC822 compliant MIME format which is also used by MailStore Server. In nearly all cases the original MIME message received by the mail server already contained invalid data, such as an appointment request confirmation without references to the original appointment. Therefore it is usually safe to delete those emails.

@@ Line 34: / Line 34: @@
 ==== June 2026 ====
-If you are an Exchange Online Kiosk, Microsoft Office 365, or Office 365 F1/F3 customer, all profiles must be migrated to Graph API and IMAP.
+If you are an Exchange Online Kiosk, Microsoft Office 365, or Office 365 F1/F3 customer, all profiles [https://techcommunity.microsoft.com/blog/exchange/update-to-ews-access-for-kiosk--frontline-worker-licensed-users/4474299 must be migrated] to Graph API and IMAP.
-Archiving Exchange Online archive mailboxes and Exchange Online Public Folders will [https://techcommunity.microsoft.com/blog/exchange/update-to-ews-access-for-kiosk--frontline-worker-licensed-users/4474299 no longer be possible].
+Archiving Exchange Online archive mailboxes and Exchange Online Public Folders will no longer be possible.
 ==== October 2026 ====

@@ Line 36: / Line 36: @@
 If you are an Exchange Online Kiosk, Microsoft Office 365, or Office 365 F1/F3 customer, all profiles must be migrated to Graph API and IMAP.
-Archiving Exchange Online archive mailboxes and Exchange Online Public Folders will no longer be possible.
+Archiving Exchange Online archive mailboxes and Exchange Online Public Folders will [https://techcommunity.microsoft.com/blog/exchange/update-to-ews-access-for-kiosk--frontline-worker-licensed-users/4474299 no longer be possible].
 ==== October 2026 ====

@@ Line 148: / Line 148: @@
 ! scope="col" bgcolor="#cccccc" | Values
 ! scope="col" bgcolor="#cccccc" | Default
 |-
 | scope="col" width="20%" align="left" valign="top" | public.arcclient.skipMimeContentConversionFailed

@@ Line 63: / Line 63: @@
 ==== Knowledge base ====
 * [[EWS Error Codes]]
 * [[Flagged Emails]]
 * [[Message Date of an Email]]

@@ Line 107: / Line 107: @@
 * cred_microsoft365 - [[Synchronizing_User_Accounts_with_Microsoft_365_(Modern_Authentication)#Creating_Credentials_in_MailStore_Server]]
 * expo_mailstorecloudbulk - [[MailStore_Cloud_Help#Migration_from_MailStore_Server_to_MailStore_Cloud]]
+* graphmimeconversionfailed - [[Graph_API_Error_Codes]]
 [[de:HelpTopicIds]]
 [[en:helpTopicIds]]

@@ Line 1: / Line 1: @@
-== ErrorMimeContentConversionFailed ==
+== text does not support structured data ==
-'''Problem:''' While archiving email from a Microsoft Exchange server an EWS error code ErrorMimeContentConversionFailed occurs.
+'''Problem:''' While archiving email from a Microsoft 365 server an Graph API error code ''text does not support structured data'' occurs.
-'''Solution:''' This kind of Exchange internal server error is caused by an internal Exchange function that is not able to convert a message from Exchange's internal MAPI format into the RFC822 compliant MIME format which is also used by MailStore Server. In nearly all cases the original MIME message received by the Exchange server already contained invalid data, such as an appointment request confirmation without references to the original appointment. Therefore it is usually safe to delete those emails.
+'''Solution:''' This kind of server error is caused by an internal Microsoft 365 function that is not able to convert a message from its internal format into the RFC822 compliant MIME format which is also used by MailStore Server. In nearly all cases the original MIME message received by the mail server already contained invalid data, such as an appointment request confirmation without references to the original appointment. Therefore it is usually safe to delete those emails.
-Due to that error, the archiving profile itself terminates with a non-successful status code. This behavior can be changed since MailStore Server 8 by modifying the global property public.arcclient.skipMimeContentConversionFailed by executing the following command in [[MailStore_Server_Management_Shell|MailStore's Management Shell]]:
+Due to that error, the archiving profile itself terminates with a non-successful status code. This behavior can be changed by modifying the global property ''public.arcclient.skipGraphContentConversionFailed'' by executing the following command in [[MailStore_Server_Management_Shell|MailStore's Management Shell]]:
-  store-setprop --name="public.arcclient.skipMimeContentConversionFailed" --value="true"
+  store-setprop --name="public.arcclient.skipGraphContentConversionFailed" --value="true"
-'''Please note:''' Independent of this global property, MailStore Server is neither able to archive messages where the above error occurred nor delete them from the Exchange server.
+'''Please note:''' Independent of this global property, MailStore Server is neither able to archive messages where the above error occurred nor delete them from the mail server.
 [[de:Graph_API-Fehlermeldungen]]
 [[en:Graph_API_Error_Codes]]

@@ Line 1: / Line 1: @@
-Microsoft is planning to [https://techcommunity.microsoft.com/blog/exchange/retirement-of-exchange-web-services-in-exchange-online/3924440 retire] the Exchange Web Service(EWS) protocol in Exchange Online. This decision affects all companies that use EWS not just MailStore. This makes it necessary to use alternative access to Exchange Online mailboxes going into the future. We provide a conversion tool that will try to help you migrating profiles that rely on EWS and will stop working in the future.
+Microsoft is planning to retire the Exchange Web Service(EWS) protocol in Exchange Online. This decision affects all companies that use EWS not just MailStore. This makes it necessary to use alternative access to Exchange Online mailboxes going into the future. Further details about the proposed discontinuation of the EWS protocol can be found in the [[EWS Migration|migration article]].
-Further details about the proposed discontinuation of the EWS protocol can be found in the [[EWS Migration]] article or you might want to follow our [https://www.mailstore.com/en/blog/microsoft-is-discontinuing-ews-for-m365/ blog].
+We provide a conversion tool that will try to help you migrating profiles that rely on EWS and will stop working in the future.
 ===Accessing the conversion tool===
-When your MailStore Server installation is using a MIcrosoft 365 profile you should see a warning message on your dashboard. Click on that will open the Microsoft 365 Profile Conversion tool.
+When your MailStore Server installation is using a Microsoft 365 profile you should see a warning message on your dashboard. Click on that will open the Microsoft 365 Profile Conversion tool.
 [[File:ConversionTool_en.png]]
@@ Line 16: / Line 15: @@
 * <b>not supported</b>
 *; Those profiles can't be supported anymore when EWS is disabled. Microsoft did not provide alternatives yet without the use of EWS.
-** <b>Public Folders</b> access will no longer be supported by Microsoft. Microsoft recommends a [https://learn.microsoft.com/en-us/exchange/collaboration/public-folders/migrate-to-microsoft-365-groups| migration] to  Microsoft 365 Groups
+** <b>Public Folders</b> access will no longer be supported by Microsoft.
-** <b>Archive mailboxes</b> or sometimes called In-Place Archives are currently only supported via EWS. A future solution has been [https://techcommunity.microsoft.com/blog/exchange/retirement-of-exchange-web-services-in-exchange-online/3924440| hinted] by Microsoft. But no actual plan has been released yet.
+** <b>Archive mailboxes</b> or sometimes called In-Place Archives are currently only supported via EWS.
 * <b>not needed</b>
 *;Those profiles are either already converted or has been created currently with a EWS replacement solution already. Those profile can be considered safe and are shown here for completeness.

@@ Line 1: / Line 1: @@
-== Microsoft Is Discontinuing Its Exchange Web Services (EWS) for Microsoft 365 ==
+__NOTOC__
-Microsoft [https://techcommunity.microsoft.com/blog/exchange/retirement-of-exchange-web-services-in-exchange-online/3924440 has announced] that it will no longer support Exchange Web Services (EWS) for Exchange Online as of October 1, 2026. This decision affects all companies that use EWS in combination with Exchange Online (Microsoft 365).
+Exchange Web Services (EWS) is a technology that was developed specifically for accessing Exchange data. The API enables access to data from Microsoft Exchange Server and Exchange Online, including emails and mailboxes. EWS has been a central interface for third-party solutions such as archiving systems.
-EWS is a technology that was developed specifically for accessing Exchange data. The API enables access to data from Microsoft Exchange Server and Exchange Online, including emails and mailboxes. EWS has been a central interface for third-party solutions such as archiving systems.
+== Microsoft is discontinuing Exchange Web Services (EWS) for Microsoft 365 ==
-What Will Happen in October?
+Microsoft will [https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361 preconfigure and potentially restrict access] to EWS based on usage starting in August 2026. Administrators can also [https://learn.microsoft.com/en-us/exchange/client-developer/exchange-web-services/how-to-control-access-to-ews-in-exchange manage the settings themselves].
-Please note: If you use Exchange Online Kiosk, Microsoft Office 365, and Office 365 F1/F3, you should make the change by June. Further information can be found [https://techcommunity.microsoft.com/blog/exchange/update-to-ews-access-for-kiosk--frontline-worker-licensed-users/4474299 here].
+For customers using Exchange Online Kiosk, Microsoft Office 365, and Office 365 F1/F3,  [https://techcommunity.microsoft.com/blog/exchange/update-to-ews-access-for-kiosk--frontline-worker-licensed-users/4474299 Microsoft will disable EWS access as early as June 2026].
-== What Will Change for MailStore Server and the MailStore SPE? ==
+== What will change for MailStore Server and MailStore SPE? ==
-The shutdown of EWS initiated by Microsoft will require adjustments to MailStore Server and the MailStore SPE, depending on your archiving strategy.
+The shutdown of EWS initiated by Microsoft will require adjustments in MailStore Server and MailStore SPE, depending on the archiving strategy. Archiving methods within MailStore Server and MailStore SPE that previously have used EWS may no longer be able to connect after October 1st and will then encounter errors.
-The following profiles are expected to be affected from October onwards, Graph API does not expose access to these and support is effectifely dropped:
+== Which protocols does MailStore use? ==
-* Importing Exchange Online archive mailboxes
+Up to and including version 25.4, MailStore exclusively created Microsoft 365 archiving and export profiles that used EWS. Starting with version 26.1, new archiving profiles for regular mailboxes use the Graph API. New archiving profiles for archive mailboxes and public folders continue to use EWS, as these are not accessible via the Graph API. New export profiles, starting with version 26.2, use the IMAP protocol, since importing complete emails into a Microsoft 365 mailbox using the Graph API is also not possible.
-Regular Exchange Online Mailboxes and Shared Mailboxes are available using Graph API. New [[Archiving_Emails_from_Microsoft_365_-_Modern_Authentication|mailbox archiving profiles]] in MailStore will use Graph API starting with version 26.1.
+=== How can MailStore support me during the migration? ===
-The [[Email_Archiving_with_MailStore_Basics|summary panel]] of the archiving or export profile tells which protocol is used. Microsoft 365 Journal archiving profiles do not typically use EWS and are therefore not affected.
+Make sure you have completed the app registration in Entra ID [[Synchronizing_User_Accounts_with_Microsoft_365_-_Modern_Authentication#Configuring_API_Permissions_in_Microsoft_Entra_ID|according to our instructions]]. In particular, the Mail.ReadWrite and IMAP.AccessAsApp permissions are now required.
 [[de:EWS Migration]]
 [[en:EWS Migration]]

@@ Line 66: / Line 66: @@
 * [[Message Date of an Email]]
 * [[Email encryption in Microsoft 365]]
 |-
 | valign="top" width="50%" |

← Older revision		Revision as of 10:38, 24 March 2026
Line 20:		Line 20:
	* <b>not needed</b>		* <b>not needed</b>
	*;Those profiles are either already converted or has been created currently with a EWS replacement solution already. Those profile can be considered safe and are shown here for completeness.		*;Those profiles are either already converted or has been created currently with a EWS replacement solution already. Those profile can be considered safe and are shown here for completeness.
		+	[[de:Microsoft_365_Profilkonvertierungstool]]

@@ Line 9: / Line 9: @@
 * arch_filepst - [[Archiving_Outlook_PST_Files_Directly]]
 * arch_gateway - [[Archiving_MailStore_Gateway_Mailbox]]
 * arch_nospamproxy - [[Archiving_Emails_from_NoSpamProxy]]
 * gateway_introduction - [[Archiving_MailStore_Gateway_Mailbox]]

@@ Line 114: / Line 114: @@
 * Enable the ''full_access_as_app'' permission in the ''Select permissions'' section.
 * '''New in 25.3''': Also enable the permission ''SMTP.SendAsApp'' in the ''SMTP'' section.
 * Click on ''Add permissions''.
-* The permissions are updated and the ''full_access_as_app'' and ''SMTP.SendAsApp'' permissions appear in the API permissions list under ''Exchange''.
+* The permissions are updated and the ''full_access_as_app'', ''SMTP.SendAsApp''  and ''IMAP.AccessAsApp'' permissions appear in the API permissions list under ''Exchange''.
 * Now click on the ''Grant admin consent for <your tenant name>'' button in the ''Configured permissions'' section.
 * Acknowledge the following notice with ''Yes''.

@@ Line 1: / Line 1: @@
 __NOTOC__
-To be able to export emails to a Microsoft 365 mailbox, MailStore Server requires specific permissions on the target mailbox for an export. The more common help for exporting can be found in the article [[Exporting Email]].
+To be able to export emails to a Microsoft 365 mailbox, MailStore Server requires specific permissions on the target mailbox for an export. This article describes how to set up these permissions. General information about setting up the export process can be found in the article [[Exporting Email]].
 == Steps for setting up needed permissions ==
 === Prerequisites in Azure Portal===
@@ Line 24: / Line 24: @@
 *; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">New-ServicePrincipal -AppId <appID> -ObjectId <enterpriseAppObjectID> -DisplayName "MailStore Service Principal"</source>
 * The service principal must now be granted full access on the target mailbox. This email address must later be specified as the export mailbox in the MailStore Export profile:
-*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Add-MailboxPermission -Identity "emailAddressOf@sending.user" -User <enterpriseAppObjectID> -AccessRights FullAccess</source>
+*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Add-MailboxPermission -Identity "emailAddressOf@target.user" -User <enterpriseAppObjectID> -AccessRights FullAccess</source>
 == Troubleshooting ==
 * If you receive a <b>Command Error. 12 (BAD).</b> when executing or testing the export profile the permission is either missing or may not yet have been distributed withing the Exchange Online Infrastructure. You can check the permission with
-*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Get-MailboxPermission -Identity "emailAddressOf@sending.user" -User <enterpriseAppObjectID></source>
+*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Get-MailboxPermission -Identity "emailAddressOf@target.user" -User <enterpriseAppObjectID></source>

@@ Line 1: / Line 1: @@
-Microsoft is planning to [https://techcommunity.microsoft.com/blog/exchange/retirement-of-exchange-web-services-in-exchange-online/3924440| retire] the Exchange Web Service(EWS) protocol in Exchange Online. This decision affects all companies that use EWS not just MailStore. This makes it necessary to use alternative access to Exchange Online mailboxes going into the future. We provide a conversion tool that will try to help you migrating profiles that rely on EWS and will stop working in the future.
+Microsoft is planning to [https://techcommunity.microsoft.com/blog/exchange/retirement-of-exchange-web-services-in-exchange-online/3924440 retire] the Exchange Web Service(EWS) protocol in Exchange Online. This decision affects all companies that use EWS not just MailStore. This makes it necessary to use alternative access to Exchange Online mailboxes going into the future. We provide a conversion tool that will try to help you migrating profiles that rely on EWS and will stop working in the future.
-The current Microsoft timeline for that can be followed [https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-ews-exchange-online| here].
+The current Microsoft timeline for that can be followed [https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-ews-exchange-online here].
 ===Accessing the conversion tool===
-When your MailStore Server installation is using such a profile you should see a warning message you can click that will open the conversion tool.
+When your MailStore Server installation is using such a profile you should see a warning message on your dashboard. Click on that will open the Microsoft 365 Profile Conversion tool.

← Older revision		Revision as of 10:49, 23 March 2026
Line 1:		Line 1:
		+	__NOTOC__
	To be able to export emails to a Microsoft 365 mailbox, MailStore Server requires specific permissions on the target mailbox for an export. The more common help for exporting can be found in the article [[Exporting Email]].		To be able to export emails to a Microsoft 365 mailbox, MailStore Server requires specific permissions on the target mailbox for an export. The more common help for exporting can be found in the article [[Exporting Email]].
	== Steps for setting up needed permissions ==		== Steps for setting up needed permissions ==

@@ Line 6: / Line 6: @@
 === Email Server ===
 *'''Microsoft&nbsp;365 Mailbox''' - A folder named ''MailStore Export'' is created in the Microsoft&nbsp;365 mailbox into which emails are copied. If the option ''Retain folder structure'' is checked, the archive's folder hierarchy will be created in the destination, otherwise all email will be stored in the same folder.
 *'''Exchange Mailbox''' - A folder named ''MailStore Export'' is created in the Exchange mailbox into which emails are copied. If the option ''Retain folder structure'' is checked, the archive's folder hierarchy will be created in the destination, otherwise all email will be stored in the same folder.
 *'''Google Workspace''' - A folder named ''MailStore Export'' is created in a Google Workspace mailbox into which emails are copied.

@@ Line 1: / Line 1: @@
 To be able to export emails to a Microsoft 365 mailbox, MailStore Server requires specific permissions on the target mailbox for an export. The more common help for exporting can be found in the article [[Exporting Email]].
+== Steps for setting up needed permissions ==
-'''Please note:''' Backup strategies (a backup of the entire archive) are discussed separately in the article [[Backup and Restore]].
+=== Prerequisites in Azure Portal===
+A registered App is needed with proper settings to be allowed to use IMAP
-== Steps for setting up permissions ==
+* Go to [https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/RegisteredApps| App Registrations] or navigate from the Azure Portal home to the <b>App registrations</b> service
-The PowerShell module ''ExchangeOnlineManagement'' is required to set the permission. The presence of the module can be checked with the following command.
+* Select your Application. If you're already using directory service synchronization or archiving from Microsoft 365, you already have such an app registration. If not creating such an app registration is described in [[Synchronizing_User_Accounts_with_Microsoft_365_-_Modern_Authentication|Synchronizing User Accounts with Microsoft 365]].
 *; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Get-Module ExchangeOnlineManagement -ListAvailable</source>
 * If the output is empty, the module can be installed with the following command:
@@ Line 12: / Line 16: @@
 * Then the module can be loaded:
 *; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Import-module ExchangeOnlineManagement</source>
 * Connect with your client, use a user who has ''Role Management'' permissions:
 *; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Connect-ExchangeOnline -Organization <tenantID></source>
+* Creating an app registration also resulted in the creation of an Enterprise App with its ''own ObjectID'' in your tenant. The next step requires the Enterprise App's ObjectID (not from the original app registration) and ApplicationID. Both can be found in the Entra ID Portal at [https://portal.azure.com/#view/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/~/AppAppsPreview this page].
-* Creating the app registration also resulted in the creation of an Enterprise App with its ''own ObjectID'' in your tenant. The next step requires the Enterprise App's ObjectID (not from the original app registration) and ApplicationID. Both can be found in the Entra ID Portal at [https://portal.azure.com/#view/Microsoft_AAD_IAM/StartboardApplicationsMenuBlade/~/AppAppsPreview this page].
+* If you haven't before create a service principal for this Enterprise App:
 *; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">New-ServicePrincipal -AppId <appID> -ObjectId <enterpriseAppObjectID> -DisplayName "MailStore Service Principal"</source>
-* The service principal must now be granted permission to send emails on behalf of a user. This user's email address must later be specified as the sender in the MailStore SMTP settings:
+* The service principal must now be granted full access on the target mailbox. This email address must later be specified as the export mailbox in the MailStore Export profile:
-*;<p class=msnote>'''Important Note:''' All emails restored using this mailbox will also be saved as a copy in the mailbox's ''Sent Items'' folder. Therefore, we recommend using a dedicated shared mailbox that only authorized employees have access to.</p>
+*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Add-MailboxPermission -Identity "emailAddressOf@sending.user" -User <enterpriseAppObjectID> -AccessRights FullAccess</source>
-*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Add-MailboxPermission -Identity "emailAddressOf@sending.user" -User <enterpriseAppObjectID> -AccessRights FullAccess</source>
+== Troubleshooting ==
-* Additionally, make sure that SMTP is allowed for this user:
+* If you receive a <b>Command Error. 12 (BAD).</b> when executing or testing the export profile the permission is either missing or may not yet have been distributed withing the Exchange Online Infrastructure. You can check the permission with
-*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Set-CASMailbox -Identity "emailAddressOf@sending.user" -SmtpClientAuthenticationDisabled $false</source>
+*; <source lang="powershell" smart-tabs="true" toolbar="false" gutter="false">Get-MailboxPermission -Identity "emailAddressOf@sending.user" -User <enterpriseAppObjectID></source>

@@ Line 128: / Line 128: @@
 *'''Synchronize enabled users only'''<br/>Only Microsoft 365 user accounts that do not have their login to Microsoft 365 blocked will be taken into account by the synchronization.
 *'''Sync only these groups'''<br/>Choose one or several Microsoft 365 security groups if you only want their members to be created as MailStore Server users. That way it's possible to exclude certain users from being synchronized to MailStore Server.
-*'''Also synchronize all Microsoft 365 Groups as MailStore users'''<br/>All [https://learn.microsoft.com/en-us/microsoftteams/office-365-groups Microsoft 365 Groups] with a configured email addresses will be synchronized as MailStore users. Since Microsoft 365 Group mailboxes cannot be accessed directly, those have to be excluded when [[Archiving_Emails_from_Microsoft_Exchange_SE#Archiving_Multiple_Exchange_Mailboxes_Centrally|archiving multiple Exchange mailboxes centrally]]. When [[Archiving_Emails_from_Microsoft_Exchange_SE#Archiving_Incoming_and_Outgoing_Emails_Directly|archiving incoming and outgoing emails directly]], emails sent from and to these Groups will archived.
+*'''Also synchronize all Microsoft 365 Groups as MailStore users'''<br/>All [https://learn.microsoft.com/en-us/microsoftteams/office-365-groups Microsoft 365 Groups] with configured email addresses will be synchronized as MailStore users. Since Microsoft 365 Group mailboxes cannot be accessed directly, those have to be excluded when [[Archiving_Emails_from_Microsoft_365_-_Modern_Authentication#Archiving_Multiple_Microsoft_365_Mailboxes_Centrally|archiving multiple Microsoft 365 mailboxes centrally]]. When [[Archiving_Emails_from_Microsoft_365_-_Modern_Authentication#Archiving_Incoming_and_Outgoing_Emails_Directly|archiving incoming and outgoing emails directly]], emails sent from and to these Groups will be archived. These users cannot login to the MailStore archive.
 {{Directory Services Options|Microsoft 365 tenant}}

@@ Line 2: / Line 2: @@
 Please select your version of Microsoft Exchange Server.
 </noinclude>
-{{Hosted_Exchange_Versions}}* [[Archiving_Emails_from_Microsoft_Exchange_2019|Microsoft Exchange 2019 (Legacy System]]
+{{Hosted_Exchange_Versions}}* [[Archiving_Emails_from_Microsoft_Exchange_2019|Microsoft Exchange 2019 (Legacy System)]]
-* [[Archiving_Emails_from_Microsoft_Exchange_2016|Microsoft Exchange 2013 (Legacy System]]
+* [[Archiving_Emails_from_Microsoft_Exchange_2016|Microsoft Exchange 2016 (Legacy System)]]
 * [[Archiving_Emails_from_Microsoft_Exchange_2013|Microsoft Exchange 2013 (Legacy System)]]
 * [[Archiving_Emails_from_Microsoft_Exchange_2010|Microsoft Exchange 2010 (Legacy System)]]

@@ Line 54: / Line 54: @@
 {{Template:SQLDeprecation}}
-External archive stores can only be created manually. Creating a new external archive store is described in chapter [[Using External Archive Stores]].
+Managing external archive stores is described in chapter [[Using External Archive Stores]].
 == Managing Archive Stores ==