Description
As recommended by Microsoft, Backup Exec (BE) uses Graph Export API to back up the Teams post data.
Notes:
- There is a cost associated with usage of Graph Export API but Effective August 25, 2025, usage of Microsoft Graph Export APIs for Teams backup will no longer incur charges.
Graph APIs and Cost prior to August 25, 2025
- Microsoft typically charges for download of a single post. Reference - Costing and Licensing details.
- As recommended by Microsoft, Backup Exec (BE) will use model B licensing to back up the Teams posts data.
- This cost should be kept in mind while backing up the Teams channel posts. Select the date range-based backup option to limit the cost of full backups.
- BE does not support group chat or 1:1 chat backup. The cost will be limited to backing up posts only on public channels and private channels.
Backup Exec Install Scenarios
Use Cases :
- New installation of Backup Exec 22.x
If BE is installed freshly and the user adds the M365 tenant in BE, the user has to carry out manual steps once the M365 Tenant is added. Refer to the Additional Steps section.
- Upgrade from Backup Exec 22 to Backup Exec 22.x
If BE is upgraded, the user needs to run the Update Tenant wizard. This will update the currently added tenant in BE with all the permissions needed to backup the MS Teams posts. After the Update Tenant wizard is run, users should follow the manual steps described in the Additional Steps section to ensure the backups run successfully.
Additional Steps
1. Open BE Console.
2. Double click on the M365 tenant added under Backup and Restore tab.
3. Click on Fetch Details.
4. Make a note of the first Application ID. Run the required Azure CLI/PowerShell command as suggested by Microsoft.
Note: It is a pre-requisite to have an active Azure Subscription attached to the tenant, in order to use a metered API.
Note - Backup Exec jobs protecting MS Teams components will fail with the following error if the additional steps are not performed.
SaaS Connector Framework error: resource: Error code: 67113864/106. HTTP error occurred for the operation. [402] To call this API, the app must be associated with an Azure subscription.
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.