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

[kavaa]

Thanks for the swift reply, can you also comment on the link I send. What the pros and cons are?

[gockon]

Hi, tried solution #2 with editing config.xml and same is happening (only mailboxes backup in this job).
Solution #1 with kb4340 not an option for now since it's irreversible.
Waiting...

[kavaa]

@gockon

Did you follow the correct steps;

1. Stop the Veeam Backup for Microsoft 365 Service and Veeam Backup Proxy for Microsoft 365 Service
2. Go to: C:\ProgramData\Veeam\Backup365
3. Make a copy of the Config.xml file
4. Edit the Config.xml file
5. Add

Code: Select all

<Proxy SkipTeamsMessagesDataFolders="True" />

right before the </Archiver> tag
6. Start the Veeam Backup for Microsoft 365 Service and Veeam Backup Proxy for Microsoft 365 Service
7. If you have multiple Proxies; Open the Veeam Backup for Microsoft365 Console -> Go to Backup Infrastructure -> Backup Proxies -> Right Click on the other proxies -> Click Upgrade.
7.1 In the step for the credentials make sure to use: HOSTNAME\USERname and the password. > Sometimes when you just leave it default the upgrade will fail for some reason.
8. Try the backup again

[RedVision81]

@kavaa
There is another KB for enabling Teams Export Api: https://www.veeam.com/kb4322
but be careful, because the Teams Export API needs an active subscription and is not free of charge.
and when i am right you can only backup the Teams Chat Message, not Messages from 1to1 chats.

BTW:
the workaround is working here, backup is running again.

[gockon]

It works now it seems, updating proxy was not the info from support.
Will monitor and get back.

Question: Why is this happening all of a sudden and what implications does editing config.xml with this

<Proxy SkipTeamsMessagesDataFolders="True" />

on current and future backups ? Remember this job is only doing mailboxes, not teams or anything else.

Thx

[bielekovve]

Fixing the config.xml did "repair" my exchange backups... I also started a teams backup and was surprised that Veeam still reports that it processes team posts...

4/3/2024 1:48:32 PM :: Processing team posts: xyz :: 0:00:37
4/3/2024 1:48:36 PM :: Processing team posts: abc :: 0:00:37
4/3/2024 1:48:44 PM :: Processing team posts: 0815 :: 0:00:36
4/3/2024 1:48:49 PM :: Processing team posts: 4711 :: 0:00:35
4/3/2024 1:48:53 PM :: Processing team posts: 1234 :: 0:00:36

Does the proxy skipteamsmessagesdatafolders=„true“-option not prevent backing up the teamsmessagesdatafolder of the m365 groups? We don't have chat backup activated...

thx...

[xlevix10]

@PatrickPelinski just echoing other folks, tried this on our two Veeam servers and it worked for both! Thanks so much!

[kavaa]

@kavaa
There is another KB for enabling Teams Export Api: https://www.veeam.com/kb4322
but be careful, because the Teams Export API needs an active subscription and is not free of charge.
and when i am right you can only backup the Teams Chat Message, not Messages from 1to1 chats.

BTW:
the workaround is working here, backup is running again.

Yep, that's what we have seen. So don't want to enable this in a Rush.

The workaround works at this point. Still Veeam should have had a fix for this in the previous update since it was known that the EWS part was going away.

[mjr.epicfail]

Hi all,

My 2 cents here:
As @Polina already mentioned, its an old folder that is not being used anymore.

Posting here to confirm our current findings: The issue is caused by the hidden TeamsMessagesData folder that has been used in the past for journaling Teams messages. Until yesterday Microsoft has not blocked access to this folder after the access via EWS APIs was deprecated and the new paid APIs were introduced. Our RnD is working on a patch with a fix that will ignore this folder.
Top

Was it a better option to already ignore this folder beforehand, maybe.
Is there a quick workaround available, yes.
So I think that the R&D folks already gave this some thought and implemented a solution before it became a real issue.

[DarrenD]

Having now seen previous horror stories about $26k bills, 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?

The text on the dialog suggests this is the case, that only Teams Chats are billable, but would like to be 100% sure. I also can't find anything that explicitly states what is backed up in Teams if you select 'Teams' but do not select 'Teams chats' - can anyone point me to some docs?

[Polina]

@gockon and @RedVision81

Switching to Teams Export APIs does not help with the current 'non IPM' issue. To be honest, I wonder where this suggestion has come from, because it doesn't make much sense. The new APIs are used to back up messages in Teams, while the current issue occurs during Exchange mailbox backup.

@kavaa
@mjr.epicfail is right - the workaround of setting a config key was added months ago as a safety net for a situation like we face today. We could not (and should not) disable requests to the TeamsMessagesData folder even knowing that EWS will be restricted for Teams. A few organizations could (and actually were) still able to use legacy methods because changes (even deprecations) in M365 are rolled out gradually and take months until the full completion. Such transition periods are always challenging and - I'll be honest - a little bit annoying for us, because we have to support multiple scenarios including legacy ones longer than we would love to.

[DarrenD]

@polina - the Teams API suggestion in coming from your support as the first option to try ( case 07208532 ) :

"1) Enabling Veeam Backup for Microsoft 365 to backup Teams public channel posts using the Teams Export APIs."

We have done this and I wish we hadn't!

[RedVision81]

@DarrenD

have a look at these posts: https://afi.ai/blog/microsoft-teams-backup (but the cost estimation in this post is wrong imho - it should be 7,5$ for 10.000 messages not 7.500$)
and pricing overview: https://learn.microsoft.com/en-us/graph/teams-licenses

[DarrenD]

@RedVision18 - thanks, I'd already looked at those I really just wanted to check that the config options we'd selected wouldn't lead to bills that we weren't expecting.

[Pete@DPY]

Having the same issue here across a multitude of tenants, though not all tenants, will look at the proxy edit option and see how we go.

Anyone here think this may have something to do with the MSFT forced push to the "new" Teams?

[KiwiBruce]

Seems to be only affecting Exchange 365 backups, not Teams/Sharepoint/OneDrive backups.
At least not here
With that proxy config change we have had one successful backup so far, and another due to run in an hour.
Looks good here.

I used the:
1. Stop the Veeam Backup for Microsoft 365 Service and Veeam Backup Proxy for Microsoft 365 Service
2. Go to: C:\ProgramData\Veeam\Backup365
3. Make a copy of the Config.xml file
4. Edit the Config.xml file
5. Add
CODE: SELECT ALL

<Proxy SkipTeamsMessagesDataFolders="True" />
right before the </Archiver> tag
6. Start the Veeam Backup for Microsoft 365 Service and Veeam Backup Proxy for Microsoft 365 Service
7. If you have multiple Proxies; Open the Veeam Backup for Microsoft365 Console -> Go to Backup Infrastructure -> Backup Proxies -> Right Click on the other proxies -> Click Upgrade.
7.1 In the step for the credentials make sure to use: HOSTNAME\USERname and the password. > Sometimes when you just leave it default the upgrade will fail for some reason.
8. Try the backup again

[YCE]

We also have the same issue today across several sites.

[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.

[PerHolm]

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

[agrob]

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

[ACrispiels]

Same issue for me too since this night, for all tenants.
BUT it seems ok right now with the applied KB4569.

[gpar]

Same issue for me. Do we have a rough estimate when this will be fixed?

[javichumellamo]

Can anybody confirm what happens with teams contents backup after aplying KB4569?

[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

[Marcus S.]

If i get this right, MS is charging users now to do Teams Chat Backups and it will not be possible to do Teams backups anymore with EWS. This config adjustment on veeam will only skip Teams folders within an exchange mailbox and has no effect on regular teams backups.

If you want to continue to do backup of your teams chats, you will have to use the new graph backup method and pay for it


Correct me if im wrong?

[ottl05]

after the change in the config.xml, the backups are running again.
thanks

[Mildur]

Can anybody confirm what happens with teams contents backup after aplying KB4569?

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

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 ?

Yes, most likely. Your build is from December 2012 and end of support since this march.
Please upgrade to the latest version.
https://www.veeam.com/product-lifecycle.html

If i get this right, MS is charging users now to do Teams Chat Backups and it will not be possible to do Teams backups anymore with EWS. This config adjustment just will skip Teams folders within an exchange mailbox and has no effect on regular teams backups.
If you will continue to backup your teams chats, you will have to use the new graph backup method and pay for it

Correct. To continue with the paid API, manual changes must be done by the VB365 admin and M365 tenant admin. Veeam cannot enable the paid API for a customer. This is a step which has to be done by the customer and backup admins.
Configuration change on the VB365 server: https://www.veeam.com/kb4340
Configuration change on the M365 tenant: https://www.veeam.com/kb4322

Best,
Fabian

[renatorichina]

I've applied KB4569 config.xml entry on 4 customers, but it works only on one. The 3 others still get the error message on each Mailbox. All customers have the same Build 7.1.1501.

What is a bit "strange": after adding the entry, it seems to be changed by Veeam and it adds values "ServerID" and "Id" behind the "SkyipTeamsMessagesDataFolder="True".

Any ideas?

[Mildur]

Hi Renato

I'm not aware of any know issue with "ServerID" and "Id".
Best to ask support to check the config file in one customers environment. There maybe a formatting or syntax error.

Best,
Fabian

[renatorichina]

I've applied KB4569 config.xml entry on 4 customers, but it works only on one. The 3 others still get the error message on each Mailbox. All customers have the same Build 7.1.1501.

What is a bit "strange": after adding the entry, it seems to be changed by Veeam and it adds values "ServerID" and "Id" behind the "SkyipTeamsMessagesDataFolder="True".

Any ideas?

Opps, found it out - was my fault: i've updated by mistake the proxy.xml on those 3 customers, not the config.xml. Now everything works like a charm again