- Veeam Support Knowledge Base
- Backup Jobs with Public Folders Fail
Backup Jobs with Public Folders Fail
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Challenge
When backing up public folders using Veeam Backup for Microsoft 365 the following error occurs:
Processing mailbox PublicFolderMailbox@xxxxxxxx.onmicrosoft.com failed with error: Failed to synchronize item changes in folder: FOLDERNAME.. Access is denied. Check credentials and try again., ICS synchronization failed.
Log Example:
Processing mailbox: PublicFolderMailbox@xxxxxxxx.onmicrosoft.com... Syncing folder items: FOLDERNAME... Exchange Web Services error code: ErrorAccessDenied Error: Failed to synchronize item changes in folder: FOLDERNAME. Type: Veeam.Ews.Internal.ExServerCodeException
Cause
Either of the following conditions may cause the error:
- Public folders are not located under the IPM_SUBTREE folder.
- The Veeam service account lacks permission to access public folders.
Solution
Confirm Public Folder is Located Under IPM_SUBTREE
Veeam Backup for Microsoft 365 only supports backing up public folders located under the IPM_SUBTREE folder. Other locations are not supported (e.g., NON_IPM_SUBTREE).
To check if the public folder is located under the IPM_SUBTREE folder, run the following cmdlet and specify credentials used in Veeam Backup for Microsoft 365.
Connect-ExchangeOnline
Get-PublicFolder -Identity \ -Recurse | Format-List Name
Disconnect-ExchangeOnline -Confirm:$falseAn output similar to the following must be displayed:
Name : IPM_SUBTREE Name : PublicFolderMailbox@*********.onmicrosoft.com Name : FOLDERNAME Name : Second Sub Folder Name : Third Sub Folder
- If the output shows that the public folder is located under the IPM_SUBTREE folder, no additional actions are needed.
- If the output shows that the public folder is located under an unsupported folder, it must moved be to the IPM_SUBTREE.
Confirm Veeam Service Account Has Permissions
Veeam Backup for Microsoft 365 uses the Veeam service account to back up public folders. When a public folder is created, it automatically inherits permissions from its parent folder.
Check Public Folder Permissions
Use the following PowerShell script to see the accounts with access to the public folders and their assigned permissions.
When prompted, specify the credentials used in Veeam Backup for Microsoft 365.
Connect-ExchangeOnline
Get-PublicFolder \ -Recurse |
Get-PublicFolderClientPermission |
Select-Object Identity,@{Expression={$.User};Label="User";},@{Expression={$.AccessRights};Label="AccessRights";} |
Export-Csv C:\PublicFolderClientPermission.csv
Disconnect-ExchangeOnline -Confirm:$false
Assign Service Account Permissions to Public Folders
To grant access, you will need to add your service account to public folders with the Owner permission.
To assign permissions, update the $user variable in the following script and run the script.
When prompted, specify credentials used in Veeam Backup for Microsoft 365.
# Set $user to the Veeam Backup for Microsoft 365 Service Account
$user = "VB365-Service-Account@yourdomain.onmicrosoft.com"
Connect-ExchangeOnline
$folders = get-publicfolder "\" -recurse
foreach($folder in $folders) { Add-PublicFolderClientPermission -Identity $folder.identity -user $user -AccessRights Owner }
Disconnect-ExchangeOnline -Confirm:$falseNOTE: It is recommended that PowerShell be used to assign permissions to public folders.
The following table shows an example of user permissions after the cmdlet is executed:
More Information
All PowerShell scripts provided above are intended to automatically retrieve and assign necessary permissions to ensure that no public folders are missed.
Please be aware that the commands and parameters may be altered by Microsoft in the future, which may break these scripts.
No support is provided by Veeam for these scripts. Should they fail, we ask that you please get in touch with Microsoft support.
These scripts may be updated periodically to reflect future changes in the Office 365 PowerShell Environment.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
You have selected too large block!
Please try select less.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.