Backup Job Identifies Teams Tabs as Unsupported and Skip Them
Issue
Cause
Every tab in Microsoft Teams has an Application ID property, which is used by the backup jobs to determine which tabs are supported or unsupported.
Due to recent changes, some supported types of tabs may be assigned an Application ID that Veeam Backup for Microsoft 365 does not recognize as being supported.
Solution
Veeam Backup for Microsoft 365 7.0.0.3604 P20230512 updates the logic and the tab application IDs should be considered by Veeam Backup for Microsoft 365 as supported, and during the next run of the backup, those that were previously skipped will be processed.
Considerations and Limitations
- When you perform backup of Microsoft Teams data, Veeam Backup for Microsoft 365 does not back up data of applications added as channel tabs (such as Website, Planner, Word, Excel, PowerPoint, Visio, PDF, Document Library, OneNote, SharePoint, Stream, Forms, Power BI, Power Automate and Azure DevOps) and other 3rd party applications if their data does not reside in the SharePoint document library of the team. Thus, the fix would help to back up the tab, but the target linked source's backup must be configured via the corresponding job type.
- Should you leverage a BAAS installation (Backup as a Service for Microsoft 365) and face the following error "Tab type is not supported" within Veeam Explorer for Microsoft Teams restore operations, please, review KB4451
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
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
Thank you!
Your feedback has been received and will be reviewed.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.