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

[kavaa]

***************

[UPDATE FROM 04 APR 2024]

The solution for this issue is provided in the KB4569

***************

CaseID: 07207589
Getting these errors on multiple tenants; 3-4-2024 08:20:03 :: Processing mailbox user@domain.com failed with error: Failed to get folder properties. Not allowed to access Non IPM folder.

The tenant does not use Public Folders checked with:

Code: Select all

Connect-ExchangeOnline
Get-PublicFolder -Identity \ -Recurse | Format-List Name

Get-PublicFolder \ -Recurse

Opened a case, support reply:

The error is returned from Microsoft Exchange upon an attempt to access a Non IPM folder, resulting in ErrorAccessDenied.
We have the below note in the limitations and considerations guide:


Veeam Backup for Microsoft 365 backs up public folders that are located under the IPM_SUBTREE folder only.


https://helpcenter.veeam.com/archive/vb ... tions.html


*This is also applicable for restores also.



Please check the below guide which provides the account permissions and the required checks for the folder to make sure that it is under the IPM_SUBTREE folder:
https://www.veeam.com/kb3093

Yeah Sure, but this happend out of the blue since last night, no changes on the Backup / Tenant side. Have this on about 20 tenants at the moment.

[Florian_Gu]

It's exactly the same here.
No changes have been made to the tenant or the backup software.

[PatrickPelinski]

I have the same problem (but with user and group mailboxes) an also opened a case.

[pputt]

We got the same issue since today, our support CaseID ist 07207633.

[karsten123]

same. Case #07207707

[Frank.Kuhn]

Same here. All our customers get this error since last night. Also none of them has any public folders. Seems MS has changed something in the background

[kavaa]

Thanks for reporting that you also have the issue, hope Veeam will check / provide a fix ASAP

[Sunshine]

Same issue. Thought I was going mad, as I couldn't find anything troubleshooting

[antonde]

For what is worth, here's another one.
At this point something has changed Microsoft side. Hope that veeam will profide fix ASAP.
Cheers.

[Mikael.Wessel]

Same here on two tenants

[FlorianSch]

Same here since yesterday, CaseID 07207835

[kavaa]

Veeam support response:

We have started receiving cases relating to the error: - "Processing mailbox failed with error: Failed to get folder properties. Not allowed to access Non IPM folder."
This issue seems to be impacting a large number of M365 tenants.
As we are currently collecting data relating to this issue, we would very much appreciate if you can run a Fiddler trace during the affected backup job run, this is to collect the connection details in relation to requests sent & received from MS.

They ask for Fiddler results.

[itops-shltm]

Hi all, same issue here, we opened the Case #07207899.

Thanks in advance for your support!

BR
Giandomenico Plaino
System Administrator IT Operations
SHL Telemedizin

[kberg]

We got this error as well on all mailboxes (user mailboxes, shared mailboxes, public folders) as well.
Until yesterday everything went fine.
When I came to the office this morning, I had this error in my report mail.

[m.novelli]

Got the same error this night on one customer so far

Marco

[ToxicBear]

Same issue, two different tenants and two different Veeams

[CSN-Solutions]

Same here since last night.
brgrds, Kai

[bielekovve]

same here, no public folder, last night all exchange jobs failed. #07208218

[Gostev]

There's a couple of hundreds of support cases already opened and almost all are from EMEA only, so clearly this is some breaking change on M365 backend as usual.

Our devs are on it, hopefully with your help and all the data from support cases we know enough about the issue in time before our key U.S. based M365 contacts at Microsoft wake up (in case it's not fixable from our end).

We will keep you posted.

[GregorS]

@Kay van Aarssen

Please correct the title of the topic "Failed to get folder properties. ot allowed to access Non IPM folder." --> "Failed to get folder properties. Not allowed to access Non IPM folder." if you still can or if a moderator can do it instead. Google does not find the topic if exact quote (in "") is used.

[Gostev]

Done.

[ReKe]

Same issue here

[karsten123]

Support engineer suggested to enable Export Teams API or disable processing via config.xml: proxy skipteamsmessagesdatafolders=„true“.
After setting this everything is going green again.

[PatrickPelinski]

After making thise changes and restarting the services, it works again.

2.3 Open the file 'C:\ProgramData\Veeam\Backup365\Config.xml' using any text editor (as Administrator) and add the following line into 'Veeam/Archiver/' XML tag:

- <Proxy SkipTeamsMessagesDataFolders="True" />

It should look like this:

<Veeam>
<Archiver>
<Proxy SkipTeamsMessagesDataFolders="True" />
</Archiver>
</Veeam>

[BastianR82]

@Patrick

Thank you, works for me! No Teams used.

Bastian

[Florian_Gu]

After making thise changes and restarting the services, it works again.

Works!
Thank you!

[Polina]

Hi All,

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.

[f.neumann]

Our RnD is working on a patch with a fix that will ignore this folder.

Will that have the same effect as 'SkipTeamsMessagesDataFolders="True"'-workaround? So we can already apply this for all customers?
Or is there an ETA for Hotfix within next hours or 1-2 days?

[kavaa]

Support engineer suggested to enable Export Teams API or disable processing via config.xml: proxy skipteamsmessagesdatafolders=„true“.
After setting this everything is going green again.

Right, but it also seems to happen to tenants not using Teams.
So why do we need to add this option...

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.
Since this action is irreversible for the Proxy's used.

So before enabling this, need to decide what's best.

[Polina]

@f.neumann
Correct; atm I expect the fix to work similarly. ETA is not clear yet - we still need time to create and test it before delivering it publicly.

@kavaa
This folder is part of a mailbox - i.e. Exchange protection. If you back up a mailbox, it contains this hidden folder by default.