#1 Global Leader in Data Protection & Ransomware Recovery

“Failed to resolve team (ID: , name: ): Organization (ID: ) which the team (ID: ) belongs to not found” when performing Microsoft Teams backup 

KB ID: 4268
Product: Veeam Backup for Microsoft Office 365 | 5.0
Published: 2022-01-03
Last Modified: 2024-01-05
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

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

error icon

Oops! Something went wrong.

Please try again later.

Update: (January 2024) There have been several reported instances where, under specific circumstances, the issue discussed in this article has occurred while running Veeam Backup for Microsoft 365 6.x. All customers are encouraged to upgrade to the latest version of Veeam Backup for Microsoft 365 (at the time of writing: Veeam Backup for Microsoft 365 7a P20231218 - 7.1.0.1401)

Challenge

Starting January 1st, 2022 an incremental backup of Microsoft Teams objects may fail with the error:
 Failed to resolve team (ID: {%id%}, name: {%name%}): Organization (ID: {%id%}) which the team (ID: %id%) belongs to not found
This issue impacts Veeam Backup for Microsoft 365 builds 5.0.0.1061 through 5.0.3.1051 and was resolved in 5.0.3.1060. For more information about version and build numbers, see KB4106. Furthermore, this issue only occurs for backup jobs where Microsoft Teams data was backed up to a local repository using a job created in 2020 that was run in both 2020 and 2021.

Cause

The issue is related to a mismatch in the Organization ID value created for Microsoft Teams data within the backup repository database.

Solution

This issue is resolved in Veeam Backup for Microsoft 365 5d Cumulative Patch KB4270.

Please update your installation to resolve the issue.

Update: (January 2024) There have been several reported instances where, under specific circumstances, the issue discussed in this article has occurred while running Veeam Backup for Microsoft 365 6.x. All customers are encouraged to upgrade to the latest version of Veeam Backup for Microsoft 365 (at time of writing: Veeam Backup for Microsoft 365 7a P20231218 - 7.1.0.1401)

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

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

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.