Fix Veeam Backup for Microsoft 365 "Failed to get folder properties. Not allowed to access Non IPM folder" Error

It was nice they released a KB article for this as well - https://www.veeam.com/kb4569

Just in case anyone wants the official reference.  😎

There are some discussions at R&D Forum.

Failed to get folder properties. Not allowed to access Non IPM folder. - Page 2 (veeam.com)

When you apply the KB, the exchange backup job will exclude this hidden folder.

The folder was previously (until 1-2 years ago) used to backup Teams chat messages.
But Microsoft has introduced the new paid Teams export API which everyone has to use if he wants to protect Teams messages. The old method through the hidden folder was officially deprecated 1-2 years ago. Even if you don't apply the KB, the folder will be gone and access denied by Microsoft.

If you want to keep protecting teams messages (messages in channels --> 1:1 and group messages are not yet possible), you have to apply this kb:
https://www.veeam.com/kb4340

Did not fix for me. Same error.

Make sure you put the <Proxy SkipTeamsMessagesDataFolders="True" /> inside the <Archiver> section at the top of the Config.xml.
I put it after the </Archiver> towards the bottom of the Config.xml and it took me a while to notice the /

If you are not on the latest v7 maybe upgrade will help?  If you are then I guess next patch hopefully fixes it.

Same issue. No fix for other site, either :(

not mine but there was a script made by a forum member:

 

[xml]$xml = Get-Content "C:\ProgramData\Veeam\Backup365\Config.xml"

if ($xml.Veeam.Archiver.Proxy -eq $null) {
    Copy-Item "C:\ProgramData\Veeam\Backup365\Config.xml" "C:\Temp\Config.xml" -ErrorAction SilentlyContinue
    $proxy = $xml.CreateElement("Proxy")
    $proxy.SetAttribute("SkipTeamsMessagesDataFolders", "True")
    $xml.Veeam.Archiver.AppendChild($proxy)
    $xml.Save("C:\ProgramData\Veeam\Backup365\Config.xml")    
    Restart-Service -Name Veeam.Archiver.Proxy -ErrorAction SilentlyContinue
    Restart-Service -Name Veeam.Archiver.Service -ErrorAction SilentlyContinue
}

The minimum compatible version for this solution is Veeam Backup for Microsoft 365 6a (build 6.1.0.1015).

Yes you need to even doing it manually for the file.

I am still on 6.0 and this fix did not work. Does this mean I need to get an immediate upgrade?

So what version are you currently on?

Disappointed that my v6 license won’t let me upgrade to v6.1. Thanks, I am working on the upgrade to latest now. Hope it works.

FYI.

KB4569 updated today

KB4569: Exchange Backup Fails With: "Failed to get folder properties. Not allowed to access Non IPM folder" (veeam.com)