Operational Defect Database
BugZero found this defect 61 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb4569
Exchange Backup Fails With: "Failed to get folder properties. Not allowed to access Non IPM folder"
Last update date:
4/9/2024
Affected products:
Veeam Backup for Microsoft 365
Affected releases:
ALL
Fixed releases:
No fixed releases provided.
Description:
Challenge
A backup job in Veeam Backup for Microsoft 365 processing Exchange data fails with the error: Failed to get folder properties. Not allowed to access Non IPM folder
Cause
During Exchange backup, Veeam Backup for Microsoft 365 requests the properties of all mailbox folders, including the properties of hidden and legacy folders (e.g., ‘TeamsMessagesData’). Due to a recent change in Microsoft 365, the properties of the ‘TeamsMessagesData’ folder cannot be retrieved using the EWS API, which is used by Veeam Backup for Microsoft 365 to process Exchange data backup.
Solution
To resolve this issue, Veeam Backup for Microsoft 365 must be configured to skip processing the ‘TeamsMessagesData’ folder. There are three options to achieve this, choose only one: All three options have the same effect: the TeamsMessagesData folder will be skipped during the Exchange data backup. Option 1: PowerShell Script to Automate Modification of the Config.xml file. — (Recommended Solution) The new fully automated and recommended solution. Option 2: Manually modify the Config.xml file to enable a setting that causes the folder to be skipped. The original hands-on solution that was provided by this article. Option 3: Install a hotfix to change the software default behavior to skip the folder. While modification of the Config.xml is the simplest and best solution, we understand that some customers may not wish to make configuration modifications or be able to access PowerShell. For those customers, a hotfix has been made available for build 7.1.0.1501 that will modify the default hardcoded value of the SkipTeamsMessagesDataFolders setting from False to True. Essentially, doing the same thing as the Config.xml setting, but at the program code level.
