Failed to get folder properties. Not allowed to access Non IPM folder.

[jasonede]

We have the same issue last night. Backups failing on One Drive, Teams, Mailboxes across the board. Will try the config file change and won't log (unless it is needed) if a fix is already in the pipeline.

[chi-ltd]

Getting:

failed with error: Failed to get folder properties. Not allowed to access Non IPM folder.

[RalfH]

@chi-ltd
Probably you made the same mistake I did - IMHO the description "Add the following line under the <Archiver> node and save the file" of the fix in the KB article may be misleading:
Actually it has to be added under the first appearance of the "<Archiver>" - not under the second "<Archiver>" at the end of the config.xml.

[Puschl]

Hello

I have also had this error since 02.04.2024 and in CASE we were told to activate the Graph API. As a second point we also received the customization of the XML file.

However, I am concerned that I will not be able to activate this option for any of my customers.
It would also be interesting to know whether I can simply copy the XML file back again or whether this will not work. Does anyone have any experience with this?

Br Mario

[richcolsell]

We've added the config.xml line in, but Veeam now seems not to be backing up user mailboxes - only SharePoint sites and shared boxes. Is this to be expected?

[storton]

Hello,

I've applied KB4569 on my config.xml ... but it still does not work, even after rebooting.

Do you think it's due to my Veeam Backup for MS365 version 5.0.3.1063 ?

Thanks for your replies.

[oscarm]

The config.xml file is as far as I know not generic, and should not be copied across multiple customers. I have edited every environment that suffered with this so far by hand and noticed the differences in the config file.

regards,
Oscar

[nathano]

This has just started happening for me on a few tenants in APAC. made the config file change and seems to be running ok now.

[Mildur]

Do you think it's due to my Veeam Backup for MS365 version 5.0.3.1063 ?

The version you are running is 2 years old. The new protected Teams API was not even released back then by Microsoft.
Therefore we hadn't this parameter in version 5.

Please update to the most recent version:
https://www.veeam.com/kb4106

Best,
Fabian

[gico]

Hello,
I'm experiencing same issue on many V365 setup, the "patch" worked fine only on one of three installation:
7.1.0.1501 p24240123 worked
6.1.0.438 p 20221215 failed on 2 installation

Is there a minimun version required to this fix to work correctly?

Thanks!
Giulio

[Polina]

Wow, a lot happened here since the last evening, and it seems I shouldn't have slept for so long today...
I will try to address some of your questions; if I miss any, be so kind as to repost and remind me.

@PerHolm

Is KB4569 a permanent solution or a workaround until a fix is ready: https://www.veeam.com/kb4569

The solution provided in the KB4569will be included as a default in the next patch.

Also, looking through your comments above, I see that a few notes and updates to this KB are needed - those will be published ASAP.

@bholthe

We have Veeam Backup for Microsoft 365 v. 6.1.0.438 and I have implemented the change in config.xml and rebooted.
I still have the same issue, do we need to Upgrade to newest version for the fix to work ?

If you're running VB365 v5 or v6, please update your installation to the latest version first. Both v5 and v6 are End of Fix already.

@javichumellamo

Will this fix have any impact in backup of teams sites content? I'm getting the error while backing up Teams
04/04/2024 1:01:06 :: Failed to process team: XXXXXXXXX. Failed to get folder properties. Not allowed to access Non IPM folder.

Teams site content is not impacted (i.e. protection of teams files located in a Team SharePoint site). The error you get might be related to backup of team chats. I believe you haven't switched to using the new paid Teams Export APIs, and that is causing the issue.

@kavaa

Veeam Support also send over this link; https://www.veeam.com/kb4340
Anyone know what the Pro's and Cons are of enabling the Teams Chat backup.

Pros - you get channel messages protected. Cons - you have to pay Microsoft for it (i.e. pay for using the specific APIs).
Using these paid APIs will remain the only possible way to back up teams messages, and it will become the default in our next product version. However, if you don't need these messages being protected or you want to avoid extra costs, you can simply make a corresponding configuration in your organization settings and backup jobs settings.

@agrob

Have the same issue and also wondering if there are maybe negativ impacts if we activate KB4569 regarding to Teams Messages?

There's no impact on team messages backup. If you're backing up channel messages using the paid APIs, everything will continue to work as expected. If you're not using the new APIs, most likely you're not protecting any messages already.

@DarrenD

can someone confirm that if we enable the Teams API ( Set-VBOServer -EnableTeamsGraphAPIBackup:$true ) but do *not* tick 'Teams chats' in the Org configuration ( we have ticked Microsoft Teams ), then it won't use the chargeable Teams APIs, and so now bills will accrue?

That's correct. There are corresponding settings both on the organization and backup jobs levels. If 'Teams chats' are not selected for your organization, there won't be even a technical possibility to back them up with such a configuration.

[bholthe]

We have Veeam Backup for Microsoft 365 v. 6.1.0.438 and I have implemented the change in config.xml and rebooted.
I still have the same issue, do we need to Upgrade to newest version for the fix to work ?

Bård

After succesfully updated to latest version (about 1 hour) and did the change, the error is gone and everything works perfectly.
Thanks for your support

Bård

[agrob]

@agrob

There's no impact on team messages backup. If you're backing up channel messages using the paid APIs, everything will continue to work as expected. If you're not using the new APIs, most likely you're not protecting any messages already.

Thanks Polina, we already use the paid API. I implemented the change in the KB and it is working fine again.

[gico]

[...]
6.1.0.438 p 20221215 failed on 2 installation
Is there a minimun version required to this fix to work correctly?

Updated to latest version one of the two 6.0 build, now some mailbox started to work, other changed error to "Processing mailbox xxx@yyy failed with error: Unable to process the Exchange Web Services item.. Invalid serialized stream, unknown opcode found: 4 ::"

About the "fix" maybe it would be better to add the version compatibility requirement...

[gico]

Update: the version that V365 fetch and install when "checking for updates" isn't the latest (even if the latest patch was release 3 months ago), so you need to manually download the 7.1a iso (7.1.0.1501). Now also "Invalid serialized stream.." error has been solved.. wow!

[stevepogue]

'SkipTeamsMessagesDataFolders="True"'-workaround not working for us

[Polina]

@stevepogue

Please ake sure you're on VB365 v7 or v7a; check if edits were applied to the correct config file; if the issue remains, report this to our support via a ticket.

[gpar]

[...]

The solution provided in the KB4569will be included as a default in the next patch.
[...]

thanks for the comprehensive update.

- is there a estimated release date for the next patch?
- if i do the workaround regarding the .xml file, do i have to reverse all changes bevor applying the upcoming patch?

[Polina]

- ETA is not available yet
- No, there shouldn't be any conflicts

[DE&C]

Same here. Most of our customers are affected.

Thank you for documenting the workaround

[pdn-andrek]

@stevepogue

Please ake sure you're on VB365 v7 or v7a; check if edits were applied to the correct config file; if the issue remains, report this to our support via a ticket.

Hi, can VB365 be updated separately or do we have to update our whole Veeam Backup&Replication Suite (including VB365) to latest version? We are currently also struggling with mailbox backups running on v6.1.0, but for "reasons" we cant update to latest version at the moment.. thx!

[Polina]

Hi @pdn-andrek

VB365 is independent of VBR, but if you use the two solutions together (i.e. in a Cloud Connect scenario), you need to check versions compatibility before doing an upgrade.

[gpar]

- ETA is not available yet
- No, there shouldn't be any conflicts

thank you!

[matthew_st]

We have the same problem, how to get alerted when the fix is available?

[Polina]

It may take about a week before the patch is released (there're a few more fixes to include => more thorough testing is required).
I'd suggest you follow the instructions from https://www.veeam.com/kb4569 to have the problem resolved faster.

[chtn]

I'll add myself to the "me too" list. I didn't open a ticket since the workaround KB4569 was already posted here. After applying the workaround, I'm getting successful backups once again. FWIW, my backup at 1PM Eastern time yesterday (April 3) was fine, but mailbox backups were failing as of my 2PM backup yesterday (I run backups hourly).

[pmarsh]

This was a lovely surprise this morning. Work around worked; backup is happy happy once again.

[Bas20200909]

Same here, I'm gonna open a case too

[abarbanel]

I'm using the solution found at this link: https://www.veeam.com/kb4569. I hope that there is information in the future regarding whether or not we need to remove this entry in the configuration file.

[Andrew Murphy]

I have the same problem I tried the fix KB4569 but it didn't work same error.